 |
» |
|
|
|
The following warning and fatal error messages can appear
on Pass Thru devices when problems occur. MESSAGE: Device not open. (PTERR 1) | CAUSE: An internal error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Host modified screen since
last receive request. (PTERR 9) | CAUSE: An internal screen error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; attempt made
to update protected field. (PTERR 10) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; non-existent
field number specified. (PTERR 11) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: One or more fields with exclamation
marks contained invalid character(s). Please correct and reenter.
(PTWARN 12) | CAUSE: One or more fields with exclamation marks contained
one or more invalid characters. ACTION: Change the contents of the field and reenter it. |
MESSAGE: Internal error; field length
specified for WRITEFIELD is too long. (PTERR 13) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; attempt made
to update a field or transmit from a printer. (PTERR 14) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid program function key
number. Please reenter. (PTWARN 15) | CAUSE: You entered an invalid program function key number
(less than 0 or greater than 24). ACTION: Reenter a valid number (an integer from 0 through
24). |
MESSAGE: Incorrect cursor address;
reposition cursor and reenter. (PTWARN 16) | CAUSE: The cursor was not located within a valid portion
of the screen when you pressed the [ENTER] key or some other special function key. ACTION: Reposition the cursor and reenter the key. |
MESSAGE: Internal error; attempt made
to write to a field where input is inhibited. (PTERR 17) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; field offset
out of range. (PTERR 21) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Keyboard enable timeout has
occurred. (PTERR 23) | CAUSE: The host failed to enable the keyboard within
the time limit specified in the timeout parameter of the OPEN3270 intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Response timeout has occurred.
(PTERR 24) | CAUSE: The host failed to send data to a device within
the transmit/receive time limit set by the timeout parameter of the OPEN3270 intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; intrinsic
call made in split stack mode. (PTERR 25) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; intrinsic
call made with parameter value out of bounds. (PTERR 26) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; could not
open device. Insufficient virtual memory was available. (PTERR 27) | CAUSE: An internal software error has occurred. ACTION: Before trying to open the device again, check
with the system manager to be sure there is enough virtual memory
on your system. Note the circumstances and report them to your HP
representative. |
MESSAGE: Internal error; could not
open device. Insufficient real memory was available. (PTERR 28) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; called an
intrinsic with a request already outstanding. (PTERR 29) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; IMF intrinsic
error occurred. (PTERR 30) | CAUSE: An internal software error has occurred in SNA
IMF. ACTION: A file named IMFDUMxx was created in your group and account or in the
PUB group of the SYS account. Save this file for your HP representative.
Note the circumstances and report them to your HP representative. |
MESSAGE: Internal error; specified
MAXINBUFLEN is too large. (PTERR 42) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; transparent
mode not requested for LU.T1 emulation. (PTERR 43) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; WRITESTREAM
called during an LU.T1 session. (PTERR 44) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal error; value specified
for the INBUF parameter is too small to hold the entire data stream.
(PTERR 49) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Attempt to open file on terminal
failed. (PTERR 100) | CAUSE: Your attempt to open a file on the terminal has
failed. Refer to the file system error message that follows this
message for the reason why the FOPEN command of the terminal failed. ACTION: Correct the problem and try again. |
MESSAGE: Call to FGETINFO failed. (PTERR
101) | CAUSE: The file system was unable to return information.
Refer to the file system error message that follows this message
for more information about the error. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Emulation attempted on non-terminal
device. (PTERR 102) | CAUSE: You may emulate only display station functions
using an HP 239x, 262x, or 264x terminal. The device you
chose was not a terminal. ACTION: Choose another logical device number and try again. |
MESSAGE: Attempt to allocate terminal
failed. (PTERR 103) | CAUSE: The terminal allocation request (call to FCONTROL) failed. Refer to the file system error message
that follows this message for more information about the error. ACTION: Correct the problem and try again. |
MESSAGE: Call to FWRITE failed. (PTERR
104) | CAUSE: Refer to the file system error message that follows
this message for more information about the problem. ACTION: Correct the problem and try again. |
MESSAGE: 239x, 262x, or 264x terminal
needed for emulation. (PTERR 105) | |
MESSAGE: 2640 terminal must be strapped
for page mode. (PTERR 106) | CAUSE: Your terminal is an HP 2640; it must be strapped
for page mode to operate correctly. The D strap must be out (open). ACTION: Remove the D strap, do a hard terminal reset,
and try again. |
MESSAGE: 2640 or 2645 terminals must
have the H strap in. (PTERR 107) | CAUSE: Your HP 2640 or 2645 terminal must be strapped
for the proper handshaking mode. ACTION: Replace the H strap (in or closed), do a hard
terminal reset, and try again. |
MESSAGE: An expected DC2 was not received
from the terminal. (PTERR 108) | CAUSE: An expected DC2 was not received during the handshaking
that is required to send a screen of data from the HP 264x to the
HP 3000. Most likely, the terminal [RESET] key was pressed while a screen was displayed, or the protected
fields of the screen were modified. ACTION: Try again without disturbing any fields other
than unprotected fields. |
MESSAGE: Too many data overruns from
the terminal. (PTERR 109) | CAUSE: After four retries, the program still could not
read the screen of data without data overruns occurring on the HP
3000. Most likely, the HP 3000 is severely overloaded. ACTION: If this happens again, note the circumstances
and report them to your HP representative. |
MESSAGE: Too many data errors from
the terminal. (PTERR 110) | CAUSE: After four retries, the program could not read
the screen of data without data errors. ACTION: Have your system operator check the communications
line between the HP 3000 and your terminal because of data
errors. |
MESSAGE: Too many timeouts from the
terminal. (PTERR 111) | CAUSE: After four retries, Pass Thru could not read the
screen of data without timing out on its call to the FREAD intrinsic. Because the timeout value is about
20 seconds, the HP 3000 is probably overloaded. ACTION: If this happens again, note the circumstances
and report them to your HP representative. |
MESSAGE: Call to FREAD failed. (PTERR
112) | CAUSE: Refer to the file system error that follows this
message for an explanation of why FREAD failed. ACTION: Correct the problem and try again. |
MESSAGE: Terminal needs at least 8K
of memory for emulation. (PTERR 113) | CAUSE: The terminal does not have a minimum of 8K memory.
Your terminal needs at least 8K of configured memory to work properly
with Pass Thru. ACTION: Make sure the terminal you are using for Pass
Thru has at least 8K of memory. |
MESSAGE: This terminal may not be used
for IMF Pass Thru. (PTERR 114) | |
MESSAGE: 2640B terminal must have the
F strap out. (PTERR 115) | CAUSE: An HP 2640B terminal does not have the F strap
out. ACTION: If you are using an HP 2640B terminal, make sure
the F strap is out (open). After removing the F strap, do a hard
terminal reset, and try again. |
MESSAGE: Call to FFILEINFO failed.
(PTERR 116) | CAUSE: The file system was unable to return information.
Refer to the file system error message that follows this message
for more information about the error. ACTION: Correct the problem and try again. |
MESSAGE: Missing user and account for
3287 printer emulation. (PTERR 117) | CAUSE: The user and account specification is missing
from your info string. ACTION: Enter the user and account in brackets after the
node name in your info string when invoking a printer on a LAN.
Refer to the HP SNA Server/Access User's
Guide for more information. |
MESSAGE: Session terminated, no input
received. (PTERR 118) | CAUSE: The TIMEOUT input timer in the PTCONFIG file has expired. The
Pass Thru session was automatically terminated. ACTION: None. The timeout feature is working as configured.
See Chapter 2 “Configuring Pass Thru” of this manual for a description
of the TIMEOUT input timer. |
MESSAGE: Host application did not receive
requested key input from operator for nau. (PTERR 122) | CAUSE: The host application requested that the [PA1] or [PA2] key be entered for the Network Addressable Unit identified.
The printer's request for this input from the console operator
failed. ACTION: Restart the printer for the NAU identified and
respond to the host application's request when queried. |
MESSAGE: The Host was notified intervention
is required. (PTWARN 123) | CAUSE: The emulated [HOLD PRINT] key was sent to the Pass Thru printer, and more than 10
minutes have expired without activity. ACTION: Resume printing when you are ready by sending
the emulated [ENABLE PRINT] key to the printer identified by the nau shown in the message that precedes this message on
your display screen. |
MESSAGE: MPE XL HPCIGETVAR or HPCIPUTVAR
intrinsic error. (PTERR 128) | CAUSE: MPE XL HPCIGETVAR or HPCIPUTVAR intrinsic returned a status code other than zero.
(Zero means successful completion.) ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Could not open emulating device.
(PTERR 150) | CAUSE: Refer to the file system error message that follows
this message for the reason the FOPEN request failed. ACTION: Correct the problem and try again. |
MESSAGE: Internal error; buffer sizes
larger than 3440 are not allowed. (PTERR 151) | CAUSE: An internal software error has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Could not receive mail from
spawning process. (PTERR 152) | CAUSE: No info string was specified in the RUN command, or an internal software error has occurred. ACTION: Make sure a valid info string was specified in
the RUN command. See Chapter 3 “Starting Pass Thru” of this manual
for information about preparing a valid info string. If the info
string is not the problem, note the circumstances and report them
to your HP representative. |
MESSAGE: Unsuccessful write to terminal
device. (PTERR 153) | CAUSE: Refer to the file system error message that follows
this message for the reason the FWRITE failed. ACTION: Correct the problem and try again. |
MESSAGE: Emulating device is not a
terminal or printer. (PTERR 154) | CAUSE: You must use either an HP 3000 printer or terminal
to emulate an IBM printer. You have specified some other device
type. ACTION: Determine the correct logical device number and
try again. |
MESSAGE: Incompatible software - versions
do not match. (PTWARN 155) | CAUSE: Incompatible software; mismatched versions. Fixes
have been made to your SNA IMF Pass Thru software. ACTION: Check with your system manager to verify that
this is a normal message for your patch level. |
MESSAGE: Missing message catalog, CATIMF.PUB.SYS.
(PTERR 200) | CAUSE: The message catalog, CATIMF.PUB.SYS, was not found. ACTION: Check with your system manager to ensure the message catalog
has the correct name and resides in the PUB group of the SYS account.
If the message catalog is missing, PTERR 201 reports the error. |
MESSAGE: GENMESSAGE failed, internal
error. (PTERR 201) xx yy zz (MPE V and releases of MPE XL prior to 2.1) | CAUSE: If the message catalog CATIMF.PUB.SYS is missing, all fatal errors are reported in this
format. xx is the Pass Thru error number (PTERR xx); yy is the file system error message number (zero if
no file system error was involved); and zz is the reason the GENMESSAGE intrinsic failed. ACTION: Make sure SNA IMF is installed on your system.
If SNA IMF is installed, make sure the message catalog, CATIMF.PUB.SYS, is installed properly and is a valid catalog.
If any changes have been made to the catalog (such as customizing
the unowned screen), the MAKECAT utility must be run again. |
MESSAGE: CATREAD failed, internal error.
(PTERR 201) xx yy zz (MPE XL, release 2.1 or later) | CAUSE: If the message catalog CATIMF.PUB.SYS is missing, all fatal errors are reported in this
format. xx is the Pass Thru error number (PTERR xx); yy is the file system error message number (zero if
no file system error was involved); and zz is the reason the CATREAD intrinsic failed. ACTION: Make sure SNA IMF is installed on your system.
If SNA IMF is installed, make sure the message catalog, CATIMF.PUB.SYS, is installed properly and is a valid catalog.
If any changes have been made to the catalog (such as customizing
the unowned screen), the GENCAT utility must be run again. |
MESSAGE: Please press the block mode
key. (PTWARN 202) | CAUSE: You failed to press the [BLOCK MODE] key. ACTION: With an HP 2640B, you must press the [BLOCK MODE] key to continue. This message repeats every two seconds.
An audible beep sounds between messages. |
MESSAGE: Unsuccessful write to printer
device. (PTERR 209) | CAUSE: Call to FWRITE failed. ACTION: Refer to the file system error message that follows
this message for an explanation of the problem. Correct the problem
and try again. |
MESSAGE: Unable to open PRINT3270 spool
file. (PTERR 210) | CAUSE: You attempted to use the Pass Thru function. However,
SNA IMF could not open the output spool file LOGIMF. ACTION: Check for other errors at the printer or with
the spooler. If the error cannot be corrected, contact your HP representative. |
MESSAGE: Unable to write to PRINT3270
spool file. (PTERR 212) | CAUSE: You attempted to use the Pass Thru PRINT function. However, SNA IMF could not write to
the output spool file LOGIMF. ACTION: Check the file size (the file may be full). If
using a file equation, make sure the file is equated properly. |
MESSAGE: Unable to close PRINT3270
spool file. (PTERR 214) | CAUSE: After using the Pass Thru PRINT function, SNA IMF attempted to close the output
spool file LOGIMF. However, the file could not be closed. ACTION: Refer to the file system error message that follows
this message for an explanation of the problem. Correct the problem
and try again. |
MESSAGE: SCREEN IN RECEIVE MODE: Data
may not be sent to the host because your SNA session is in receive
state. (PTWARN 216) | CAUSE: The host has not finished sending data to your
session, so SNA IMF is not in a send state. ACTION: Wait for the host to finish sending data and then
try again. If you still continue to receive this error message,
note the circumstances and contact your HP representative. |
MESSAGE: SCREEN UNOWNED: Data may not
be sent because your screen is unowned. Press the System Request
key to enter logon. (PTERR 217) | CAUSE: The screen is unowned and a key other than the [SYSTEM REQUEST] key was pressed. No other program function or program
attention keys (or the [ENTER] key) can be used while the screen is unowned. ACTION: Use the [SYSTEM REQUEST] key to toggle the screen to the LU-SSCP session. You can
then enter your logon and transmit it to the host. |
MESSAGE: SESSION NOT ACTIVE: Your SNA
session has not been activated, or it has been deactivated. Try
again when it is active. (PTWARN 219) | CAUSE: Session not active. Your SNA session has not been
activated, or it has been deactivated. ACTION: Check with your system administrator or IBM operator
to make sure the NAUs on the HP 3000 have been properly activated, then
try again. |
MESSAGE: PTCONFIG evaluation failed.
(PTERR 220) | CAUSE: One or more syntax errors were detected when parsing
your specified PTCONFIG file. ACTION: Refer to specific error messages reported before
this message for an explanation of the problem. Correct the problems
indicated by those messages. |
MESSAGE: Unable to open PTCONFIG file.
(PTERR 221) | CAUSE: The FOPEN has failed for reasons other than file not found. ACTION: If you specified the PTCONFIG file, make sure
you specified the proper file equation for it. |
MESSAGE: Invalid AID option or positive
integer. (PTERR 222) | CAUSE: Unrecognizable data was present after a colon,
or you specified an invalid keyboard enable timer value. ACTION: Check the PTCONFIG file line listed for syntax
errors or illegal option values. See Chapter 2 “Configuring Pass Thru” of
this manual for PTCONFIG file syntax and valid option values. Correct your
file and try again. |
MESSAGE: Invalid PF key value. (PTERR
223) | CAUSE: An invalid program function (PF) key value was
specified. For IBM 3278 display stations, PF values between PF1
and PF24 are valid (PF10 for example). ACTION: Use a valid PF key value: PF1 through PF24. |
MESSAGE: Invalid PA key value. (PTERR
224) | CAUSE: Expecting the [PA1], [PA2] or [PA3] key. Any other value following "PA" will
generate this error. ACTION: Use a valid PA key value: PA1, PA2, or PA3. |
MESSAGE: Invalid keyboard enable timer
value. (PTERR 225) | CAUSE: The keyboard enable timer value was expected after
the colon. ACTION: The value must be a positive integer from 0 through
28800. See the PTCONFIG file discussion in Chapter 2 “Configuring Pass Thru” for
additional information about the keyboard enable timer. |
MESSAGE: Found end of record. Data
was expected. (PTERR 226) | CAUSE: Found no data following the colon. ACTION: Check the PTCONFIG file for function key definition. |
MESSAGE: Missing colon in statement.
(PTERR 227) | CAUSE: Expected to find a colon separating the function
key specification from the softkey function (AID). ACTION: Add a colon to the statement. |
MESSAGE: Read of PTCONFIG file failed.
(PTERR 228) | CAUSE: The FREAD to the PTCONFIG file failed. ACTION: Make sure the PTCONFIG file contains data in the
correct format with no non-display characters. If you used a file
equation, make sure your PTCONFIG file was equated to the proper
file. |
MESSAGE: Invalid entry. Please reenter.
(PTWARN 229) | |
MESSAGE: Invalid function key specification.
(PTWARN 231) | CAUSE: The text after "PF" is invalid.
The number must be from 1 through 24 for IBM 3278 display stations. ACTION: Correct text and try again. |
MESSAGE: In CONSTRUCT'FIELD: newfldptr
bounds violation. (PTERR 233) | CAUSE: Internal software error. Pass Thru will terminate
if this message is generated. ACTION: Note the circumstances and report them to your
HP representative. If you are using an HP 2624 terminal, take a
trace of the problem using the TRACE keyword in the info string. If you have a 2645,
2626, or any other terminal that does not support Transmit Only Fields
(MDTs), attempt to reproduce the problem that occurred on the 2624
and print the internal screen image by pressing the PRINT softkey with the FORMAT parameter in the info string set to 1. |
MESSAGE: In CONSTRUCT'FIELD: old'fld'start'ptr
bounds violation. (PTERR 234) | CAUSE: Internal software error. Pass Thru will terminate
if this message is generated. ACTION: Note the circumstances and report them to your
HP representative. See PTERR 233 for more explanation. |
MESSAGE: Missing BEGIN statement. (PTERR
236) | CAUSE: You must have a BEGIN statement at the beginning of each level in your
PTCONFIG file. See Chapter 2 “Configuring Pass Thru” of this manual. ACTION: Add the missing BEGIN statement to your PTCONFIG file and try again. |
MESSAGE: Number of legal levels exceeded.
(PTERR 237) | CAUSE: The number of function key levels allowed in your
PTCONFIG file was exceeded. A maximum of 6 levels is allowed for
a terminal with 16 function keys. A maximum of 12 levels is allowed
for a terminal with 8 function keys. ACTION: Reduce the number of levels specified so the number
falls within the accepted range. |
MESSAGE: Invalid function key indicator.
(PTERR 238) | |
MESSAGE: No shifted function key assignment
allowed. (PTERR 239) | CAUSE: Invalid use of [SHIFT] function key. ACTION: Do not use the SF assignment in your PTCONFIG file because your
terminal does not support shifted function keys. |
MESSAGE: Invalid assignment separator/delimiter.
(PTERR 240) | CAUSE: An invalid assignment separator or delimiter was
specified in the PTCONFIG file. ACTION: Be sure to use the correct delimiter within the
assignment syntax. See Chapter 2 “Configuring Pass Thru” of this manual
for more information. |
MESSAGE: Too many parameters. (PTERR
241) | CAUSE: Too many parameters were specified in the PTCONFIG
file. ACTION: Check the syntax of the PTCONFIG file to find
out which parameters are extraneous. See Chapter 2 “Configuring Pass Thru” in this
manual for more information. |
MESSAGE: Invalid option assignment.
(PTERR 242) | |
MESSAGE: Missing option assignment.
(PTERR 243) | |
MESSAGE: Invalid token assignment.
(PTERR 244) | CAUSE: A softkey function assignment in the PTCONFIG
file was not a valid softkey function. ACTION: Make sure all softkey function assignments are
valid. See Chapter 2 “Configuring Pass Thru” for valid softkey functions. |
MESSAGE: Not a valid number for option.
(PTERR 245) | CAUSE: Invalid keyboard enable timer value. ACTION: Make sure the keyboard enable timer is a positive
integer from 1 through 28800 seconds. Thirty seconds is the recommended time. |
MESSAGE: Invalid PTCONFIG record for
parsing. (PTERR 246) | CAUSE: This type of PTCONFIG record cannot be parsed. ACTION: See Chapter 2 “Configuring Pass Thru” in this manual. Check
the syntax of the PTCONFIG file and try again. |
MESSAGE: Missing END statement. (PTERR
247) | CAUSE: You must have a corresponding END statement for every BEGIN statement. An END statement marks the end of a level of softkeys
in the PTCONFIG file. ACTION: Add an END statement to your PTCONFIG file and try again. |
MESSAGE: Invalid label description
length. (PTERR 248) | CAUSE: Softkey label description length exceeds eight
characters. ACTION: The label defining the function key is optional.
If you specify a label, its length cannot exceed eight characters. |
MESSAGE: Invalid program function key
number. (PTERR 249) | CAUSE: The program function (PF) key number specified
is invalid. ACTION: Make sure the function key indicator is from function
key 1 through function key 8 or shifted function key 1 through shifted function
key 8. |
MESSAGE: Missing message catalog, CATIMF.PUB.SYS.
Could not format requested SNA status information. (PTWARN 250) | CAUSE: The STATUS softkey was pressed, but SNA IMF could not find the
message catalog, CATIMF.PUB.SYS, which is used to format the status display screen. ACTION: Check with your system manager to ensure the message catalog
has the correct name and resides in the PUB group of the SYS account.
If the message catalog is missing, PTERR 201 reports the error. |
MESSAGE: Could not open NMCONFIG.PUB.SYS.
(PTERR 251) (MPE XL only) | CAUSE: The configuration file could not be opened because
either it doesn't exist or something is wrong with the file. ACTION: Check with your system manager to ensure the configuration file
has the name NMCONFIG and resides in the PUB group of the SYS account. |
MESSAGE: Could not read from NMCONFIG.PUB.SYS.
(PTERR 252) (MPE XL only) | CAUSE: An unexpected error occurred while attempting
to read from the configuration file. ACTION: Check the configuration file with the validation
option in the NMMGR program. If NMMGR does not reveal the problem,
then note the circumstances and report them to your HP representative. |
MESSAGE: Could not close NMCONFIG.PUB.SYS.
(PTERR 253) (MPE XL only) | CAUSE: An error occurred while attempting to close the
configuration file. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid SNAnode name. (PTERR
254) (MPE XL only) | CAUSE: The node name passed in the snalnkinfo parameter of the OPEN3270 or ACQUIRE3270 intrinsic is not configured under SNANODE or IMF
in the file NMCONFIG.PUB.SYS. ACTION: Add the node to the configuration file or use
another node that is currently configured. |
MESSAGE: Invalid security class name.
(PTERR 255) (MPE XL only) | CAUSE: The security class name passed in the snalnkinfo parameter of the OPEN3270 or ACQUIRE3270 intrinsic is not configured under SNANODE or IMF
in the file NMCONFIG.PUB.SYS. ACTION: Add the security class to the configuration file
or use another security class that is currently configured. |
MESSAGE: Security class not properly
configured. (PTERR 256) (MPE XL only) | CAUSE: No LUs were found in the configuration file for
the specified security class. ACTION: Add LUs to the security class or use a security
class that is properly configured. |
MESSAGE: Program not authorized to
use this security class. (PTERR 257) (MPE XL only) | CAUSE: Your program is not included in the PGMLIST for
the security class specified. ACTION: Add your program to the PGMLIST for the security
class or use another security class that is already configured properly
for use with your program. |
MESSAGE: User is not authorized to
use this security class. (PTERR 258) (MPE XL only) | CAUSE: The user trying to run the program is not included
in the USERLIST for the security class specified. ACTION: Add the user's name to the USERLIST for
the security class, or use a security class that is already configured
for use by that user. |
MESSAGE: 16-bit data is not allowed
in this field. (PTERR 259) | CAUSE: You attempted to enter 16-bit data in a field
that has been defined by the host to allow only 8-bit data. ACTION: Check and modify the data to contain only 8-bit
characters. Enter the data again. |
MESSAGE: 8-bit data is not allowed
in this field. (PTERR 260) | CAUSE: You attempted to enter 8-bit data in a field that
has been defined by the host to allow only 16-bit data. ACTION: Check and modify the data to contain only 16-bit
characters. Enter the data again. |
MESSAGE: Exceeding the maximum length
of the field. (PTERR 261) | CAUSE: Shifts between 8-bit and 16-bit characters are
signaled by SO/SI control characters. These control characters take
up space in the field and are displayed as blanks. Pass Thru needs
to insert SO/SI characters if they do not already exist, and they
can cause the data to exceed the maximum length of the field. ACTION: Check and modify the data. Enter the data again. |
MESSAGE: 16-bit data is not allowed
at the location specified. (PTERR 262) | CAUSE: You may not write a 16-bit character between two
8-bit characters. You may only write a 16-bit character next to
another 16-bit character. ACTION: Check and modify the data. Enter the data again. |
MESSAGE: CREATEPROCESS intrinsic error:
Attempt to allocate MPE XL CI son process failed. (PTWARN 272) | CAUSE: MPE XL CREATEPROCESS intrinsic failed. ACTION: Note the circumstances and report them to your
HP representative. |
|
