Appendix A Intrinsic Result Codes

CAUSE: This is an MPE V message, not an SNA IMF message.

ACTION: Look up the absolute value of the result code under "GENMESSAGE" in the MPE V Intrinsics Reference Manual.

CAUSE: The intrinsic completed successfully.

ACTION: None.

CAUSE: An intrinsic other than OPEN3270 was called without first having opened the device.

ACTION: Call the OPEN3270 intrinsic to open the device before attempting to use it.

CAUSE: The OPEN3270 intrinsic could not FOPEN the specified IMF configuration file.

ACTION: Check that the IMF configuration file name is syntactically correct. Make sure the IMF configuration file exists as an old, permanent file.

CAUSE: This error is returned to the OPEN3270 intrinsic, indicating that an inappropriate devicenum parameter value was specified.

ACTION: This error is returned to the OPEN3270 intrinsic, indicating that an inappropriate devicenum parameter value was specified.

CAUSE: The host has modified the screen since the last call to RECV3270.

ACTION: Because any attempt to change or send the screen at this point would be based on old information, issue a call to the RECV3270 intrinsic to clear the error and receive the latest screen. Call the READFIELD or READSCREEN intrinsic to give you the new contents of the screen.

CAUSE: You cannot change the contents of a protected field.

ACTION: Call the SCREENATTR or FIELDATTR intrinsic to find the unprotected fields of your screen and make the changes again.

CAUSE: The field number specified in a call to the FIELDATTR, READFIELD, or WRITEFIELD intrinsic does not exist in the screen.

ACTION: Call the SCREENATTR intrinsic to find the numbers of the fields.

CAUSE: At least one character in the field or data stream was outside the range of allowable characters.

ACTION: See the descriptions of the outbuf parameter in the WRITEFIELD and STREAM3270 intrinsics. Make sure that every character is within the range specified.

CAUSE: The field length specified in the call to the WRITEFIELD intrinsic is longer than the field length in the screen.

ACTION: Call the FIELDATTR intrinsic to find the current field length. Specify a field length less than or equal to the current field length.

CAUSE: You have opened an LU.T3 printer. You are not allowed to change the contents of any field or to transmit from an LU.T3 printer.

ACTION: Open an LU.T2 or LU.T1 session. Only LU.T1 sessions support printer key entry.

CAUSE: The aid parameter specified in the TRAN3270 intrinsic is invalid.

ACTION: See the TRAN3270 intrinsic description for a list of valid aid codes. Note that the valid codes differ depending on the type of LU session.

CAUSE: The cursorrow or cursorcolumn parameter of the TRAN3270 or STREAM3270 intrinsic is invalid. The row address must be less than the number of rows on the screen. The column address must be less than the number of columns on the screen. (SNA IMF starts with 0 when counting rows and columns.)

ACTION: See the TRAN3270 and STREAM3270 intrinsic descriptions for valid cursor address values

CAUSE: You called the WRITEFIELD, STREAM3270, or TRAN3270 intrinsic while input was inhibited by the host.

ACTION: Either wait for the host to reenable input by issuing another call to the RECV3270 intrinsic or call the RESET3270 or STREAM3270 intrinsic to emulate pressing the [RESET] key.

CAUSE: The specified offset value was outside the field length.

ACTION: Call the FIELDATTR intrinsic to find the length of the field. Be sure to specify an offset that is within the field length, and make sure that the offset for the WRITESTREAM and READSTREAM intrinsics is valid.

CAUSE: An error was detected in the BASIC calling sequence.

ACTION: Make sure the parameters of the intrinsic call from BASIC are in the correct order.

CAUSE: The host failed to enable the keyboard within the time limit specified in the timeout parameter of the OPEN3270 intrinsic.

ACTION: Use the RESET3270 intrinsic to reset the keyboard for key entry. This response may be host application specific.

CAUSE: The host is possibly waiting for data from the user application or failed to send data to a device within the transmit/receive time limit set in the timeout parameter of the OPEN3270 intrinsic.

ACTION: If this message was expected, no action is required; the host may be expecting input from the user application. If the message was not expected, either the timer value given in the OPEN3270 intrinsic was not long enough to allow the host enough time to send data, or communications with the host have been disrupted. If the timer value was not long enough, use a longer timer value. If communications with the host have been disrupted, call the CLOSE3270 intrinsic to close the session.

CAUSE: An intrinsic was called while in split stack mode.

ACTION: Make sure that DB is pointing to your own stack before you call SNA IMF intrinsics.

CAUSE: A parameter address was either less than DL or greater than S when you called this intrinsic. You also could have passed an out of range parameter. A byte address may have been used instead of a word address.

ACTION: Check the call parameters and make sure they are being passed by reference and not by value.

CAUSE: There was insufficient virtual memory to allocate the extra data segment to contain the screen.

ACTION: Not enough virtual memory was available for system load, or too many processes are functioning at once. Have your system administrator configure more virtual memory.

CAUSE: There was not enough room in the PCBX of your process to allocate a file control entry for the device.

ACTION: Allocate more space for process using the MPE PREP command parameter DL = dlsize.

CAUSE: You were in no-wait I/O and called the RECV3270 or TRAN3270 intrinsic while a previous request to one of these intrinsics was outstanding.

ACTION: Call the IOWAIT or IODONTWAIT intrinsic to complete the request before issuing any new SNA IMF intrinsic calls, or call ABORT3270 to abort the previous request.

CAUSE: An internal software error has occurred in an SNA IMF intrinsic.

ACTION: A file named IMFDUMxx was probably 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.

CAUSE: The stream data you supplied positioned the cursor on top of an attribute byte. You may not write over an attribute character.

ACTION: Use the ATTRLIST intrinsic to locate the attribute bytes.

CAUSE: You specified a maxinbuflen value that extends beyond the end of the screen. maxinbuflen does not wrap to the beginning of the screen.

ACTION: Make sure values for the offset and maxinbuflen parameters are less than the screen size.

CAUSE: You specified a devicenum of -1 in your OPEN3270 intrinsic call without setting bit 14 of the OPEN3270 flags parameter to one.

ACTION: Set bit 14 of the OPEN3270 flags parameter to one and be sure to call only those intrinsics that are valid for transparent mode.

CAUSE: The WRITESTREAM intrinsic was called during an LU.T1 session.

ACTION: The WRITESTREAM intrinsic cannot be called during an LU.T1 session. The only data that may be sent to the PLU are the printer keys, which are sent using the TRAN3270 intrinsic.

CAUSE: The size of the data stream received from the host is larger than the size of the inbuf parameter. This result code applies to the READSTREAM intrinsic.

ACTION: Modify the maxinbuflen parameter of the READSTREAM intrinsic so the inbuf parameter can hold the entire data stream and issue a call to the READSTREAM intrinsic.

CAUSE: The RECV3270 intrinsic must be issued to receive host data before the READSTREAM intrinsic can be called.

ACTION: Issue a call to the RECV3270 intrinsic to accept host data. Then call the READSTREAM intrinsic to obtain the data from the extra data segment. This result code applies only to transparent mode.

CAUSE: The buffer was not filled before trying to transmit.

ACTION: Put the data you want to send to the host in the extra data segment by calling the WRITESTREAM intrinsic before you call the TRAN3270 intrinsic. This result code applies only to transparent mode.

CAUSE: The size of the data stream is larger than the maximum allowable size.

ACTION: For 480-character screens, 540 bytes is the maximum size. For 1920-character screens, 2160 bytes is the maximum size. For 3440-character screens, 3870 bytes is the maximum size. If this error occurs when the RECV3270 intrinsic is called, only the first 540, 2160, or 3870 bytes of the data stream will be buffered in the extra data segment. This result code applies only to transparent mode.

CAUSE: An intrinsic was issued that cannot be called while in transparent mode.

ACTION: Do not use an intrinsic such as READFIELD or STREAM3270 in transparent mode. Because there is no internal screen image in transparent mode, do not use any intrinsic that reads from or writes to an internal screen image.

CAUSE: You may not use the data stream intrinsics READSTREAM or WRITESTREAM, because you did not specify transparent mode in the flags parameter of your call to the OPEN3270 intrinsic.

ACTION: Request transparent mode by setting bit 14 of the OPEN3270 flags parameter to one.

CAUSE: A spool file priority other than a value from 1 through 13 was specified.

ACTION: Make sure the priority parameter of the PRINT3270 intrinsic is from 1 through 13. The priority parameter is passed on to the FOPEN intrinsic, which is described in the MPE V Intrinsics Reference Manual and the MPE XL Intrinsics Reference Manual.

CAUSE: Your attempt to open the spool file for the PRINT3270 intrinsic failed when the FOPEN intrinsic was called.

ACTION: The PRINT3270 intrinsic leaves the fileid parameter set to zero so that you may call the file system intrinsic FCHECK to determine the specific reason for FOPEN's failure. Use FCHECK to determine the cause of the error.

CAUSE: The PRINT3270 intrinsic attempted to call the file system intrinsic FWRITE to write to the spool file identified by fileid; however, the call to FWRITE failed.

ACTION: Make sure the fileid value is correct. Insufficient disk space may also cause this error. Call the file system intrinsic FCHECK to determine the specific reason for FWRITE's failure.

CAUSE: An invalid value was specified for the action parameter.

ACTION: Make sure the value of the action parameter in the PRINT3270 intrinsic is an integer from 0 through 4.

CAUSE: The FILE command you used to override the formal designator LOGIMF, which PRINT3270 uses, is incompatible with the requirements of PRINT3270 for a spooled output file.

ACTION: Exit the application and reissue the FILE command for LOGIMF. If you equate the LOGIMF file to another file, you must observe the following restrictions: the file must have a record size of 133 bytes and contain ASCII data. The equated file may not be a KSAM file.

CAUSE: The PRINT3270 intrinsic attempted to call the file system intrinsic FCLOSE to close the file specified by fileid; this attempt failed.

ACTION: Make sure you supplied the proper value for fileid in your call to the PRINT3270 intrinsic. If you used a file equation for the LOGIMF file, be sure you did not equate it to an existing file. Call the file system intrinsic FCHECK to determine the specific reason for FCLOSE's failure.

CAUSE: The file CATIMF.PUB.SYS, which is the message catalog for SNA IMF, could not be opened.

ACTION: Make sure the CATIMF.PUB.SYS file is present.

CAUSE: The MPE intrinsic GENMESSAGE did not execute properly.

ACTION: Check to see that CATIMF.PUB.SYS and GENMESSAGE are properly installed.

CAUSE: The MPE intrinsic CATREAD did not execute properly.

ACTION: Check to see that CATIMF.PUB.SYS and CATREAD are properly installed.

CAUSE: There was insufficient stack space to print the screen.

ACTION: Increase the maximum size of the data area using the MPE PREP command parameter MAXDATA = segsize.

CAUSE: You entered the node name and the separator #, but you did not enter anything after the separator.

ACTION: Enter at least one alphabetic character after the separator # to identify the snaclassname.

CAUSE: You specified an incorrect value for the ldev, or the ldev is being used by another process.

ACTION: Verify that you used the correct value for ldev. Also, determine whether another process is using the same ldev.

CAUSE: An invalid value was specified for the enhance parameter.

ACTION: Make sure the enhance parameter value is an integer from 0 through 3.

CAUSE: An invalid value was specified for the priority parameter.

ACTION: Make sure the priority parameter value is an integer from 1 through 13.

CAUSE: An invalid value was specified for the blanks parameter.

ACTION: Make sure the blanks parameter value is either 0 or 1.

CAUSE: An invalid value was specified for the format parameter.

ACTION: Make sure the format parameter value is an integer from 1 through 4.

CAUSE: An invalid value was specified for the flags parameter of the ACQUIRE3270 intrinsic.

ACTION: Determine the correct value for the flags parameter by checking the description of the ACQUIRE3270 intrinsic in Chapter 3 “Intrinsics Used with Standard MPE I/O” of this manual.

CAUSE: Your HP 3000 could not find the Pass Thru program file, TTSSON.PUB.SYS.

ACTION: Make sure that TTSSON.PUB.SYS is installed. Also, make sure that this file was loaded into the correct group and account.

CAUSE: You began an HP LAN node name with either a numeric or a special character.

ACTION: Modify your node name so that it begins with an alphabetic character. See the HP SNA Server/Access User's Guide for more information.

CAUSE: You entered a node name to either route printer output to another node on the LAN or to acquire other terminals and printers on the LAN, but the SNA Server cannot provide service because it is not properly installed.

ACTION: Check with your HP representative to make sure the SNA Server is installed properly. See the HP SNA Server/Access User's Guide for more information.

CAUSE: You did not enter enough characters to specify the snanodename#snaclassname.

ACTION: Enter at least one alphabetic character for the snanodename, enter the pound sign (#) for the separator, and enter at least one alphabetic character for the snaclassname.

CAUSE: A screen in receive mode cannot send data.

ACTION: The host controls who can send data at any particular time. Right now, you can only receive data. Check the host application.

CAUSE: Your screen is in the unowned state.

ACTION: Use the TRAN3270 intrinsic to enter the [SYS REQ] key. Then log on to your system.

CAUSE: You entered a colon (:) in the netinfo parameter of the ACQUIRE3270 intrinsic, but you did not enter a node name after the colon.

ACTION: Enter a node name after the colon. It may be from one through eight alphanumeric characters and must begin with an alphabetic character. See the HP SNA Server/Access User's Guide for more information.

CAUSE: Your node name was more than eight characters in length.

ACTION: Modify your node name so that it is from one through eight characters in length. See the HP SNA Server/Access User's Guide for more information.

CAUSE: You forgot to enter the right bracket after your user and account logon in the netinfo parameter of the ACQUIRE3270 intrinsic ([user.account]).

ACTION: Modify your netinfo parameter so that your user.account logon is fully bracketed ([user.account]). See the HP SNA Server/Access User's Guide for more information.

CAUSE: You began your node name with either a numeric or a special character.

ACTION: Modify your node name so that it begins with an alphabetic character.

CAUSE: You began your class name with either a numeric or a special character.

ACTION: Modify your class name so that it begins with an alphabetic character.

CAUSE: You did not enter a user and account after your node name in the netinfo parameter of the ACQUIRE3270 intrinsic.

ACTION: Modify your netinfo parameter so that you enter the needed logon for printer emulation as part of your ldev specification. Be sure that your user and account is enclosed in brackets. See the HP SNA Server/Access User's Guide for more information.

CAUSE: You did not enter enough characters to specify the user and account.

ACTION: Enter at least one alphabetic character for the user, enter the period for the separator, and enter at least one alphabetic character for the account. See the HP SNA Server/Access User's Guide for more information.

CAUSE: Bit 12 of the OPEN3270 flags parameter was set to one to allow either LU.T1 or LU.T3 emulation. The secondary LU (the HP 3000) has received a BIND from the primary LU (the IBM host) to begin an SNA LU.T1 session. This message also implies that a transparent mode extra data segment (XDS) has been established for LU.T1 emulation.

ACTION: Issue a call to the RECV3270 intrinsic to begin LU.T1 printer emulation.

CAUSE: Bit 12 of the OPEN3270 flags parameter was set to one to allow either LU.T1 or LU.T3 emulation. The secondary LU (the HP 3000) has received an UNBIND from the primary LU (the IBM host).

ACTION: Issue a call to the RECV3270 intrinsic to receive the next LU.T1 or LU.T3 BIND from the host, or call the CLOSE3270 intrinsic to stop printer emulation.

CAUSE: Bit 12 of the OPEN3270 flags parameter was set to one to allow either LU.T1 or LU.T3 emulation. The secondary LU (the HP 3000) has received a BIND from the primary LU (the IBM host) to begin an SNA LU.T3 session. This message also implies that a non-transparent (screen) mode extra data segment (XDS) has been established for LU.T3 emulation.

ACTION: Issue a call to the RECV3270 intrinsic to begin LU.T3 printer emulation.

CAUSE: The printer has notified the IBM host that intervention is required. The HOLDPRINT timer has expired and you must use the TRAN3270 intrinsic to emulate pressing the [ENABLE PRINT] printer key to reenable printing from the IBM host (LU.T1 only).

ACTION: When the LU.T1 device is ready to receive, use the TRAN3270 intrinsic to either send the [ENABLE] key, or precede the [ENABLE] key with the [PA1], [PA2], or [CANCEL] key.

CAUSE: It is the printer's turn to send data.

ACTION: Use the TRAN3270 intrinsic to enter the [PA1] or [PA2] key for an LU.T1 printer.

CAUSE: The field is defined by the host to contain 8-bit characters only. Writing the Shift-Out (SO) control character is not allowed.

ACTION: Use the EXTFIELDATTR intrinsic to find the dbcsattr value defined for this field. Check and modify the data.

CAUSE: The field is defined by the host to contain 16-bit characters only. Writing the Shift-Out (SO) control character is not allowed.

ACTION: Use the EXTFIELDATTR intrinsic to find the dbcsattr value defined for this field. Check and modify the data.

CAUSE: You may not use the EXTFIELDATTR intrinsic because you did not specify the DBCS option in the flags parameter of your call to the OPEN3270 intrinsic.

ACTION: Specify the DBCS option by setting bit 10 of the OPEN3270 flags parameter to one.

CAUSE: When the DBCS option is set, the offset parameter must be zero. The affected intrinsics are ATTRLIST, READFIELD, WRITEFIELD, READSCREEN, READSTREAM, and WRITESTREAM.

ACTION: Specify the offset to be zero.

CAUSE: NLS procedures are used to perform the translation between EBCDIC and ASCII. An error is returned by the NLS routines.

ACTION: Use NLS utilities to verify that the proper conversion tables and NLS are installed correctly.

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.

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.

CAUSE: An error occurred while attempting to close the configuration file.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The node name passed in snalnkinfo to OPEN3270 or ACQUIRE3270 is not configured under SNANODE (for MPE V) or IMF (for MPE XL) in the file NMCONFIG.PUB.SYS.

ACTION: Add the node to the configuration file, or use another node that is currently configured.

CAUSE: The security class name passed in snalnkinfo to OPEN3270 or ACQUIRE3270 is not configured under SNANODE in the file NMCONFIG.PUB.SYS.

ACTION: Add the security class to the configuration file, or use another security class that is currently configured.

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.

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.

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.

CAUSE: The DB register was pointing to an extra data segment on a call to an SNA link intrinsic.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: You probably passed an invalid terminal identifier (terminalid) to an SNA IMF intrinsic.

ACTION: Be sure you used the terminal identifier returned by OPEN3270.

CAUSE: The parameter was omitted on a call to an SNA link intrinsic.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: The SNA completer was activated with an invalid Cstation, Xfercount, or TargetFlag parameter.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: Your user name or program is not authorized to use this LU class.

ACTION: Check the SNA configuration for your SNA node.

CAUSE: SNA IMF passed the SNA link product an out-of-bounds parameter.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: SNA IMF passed an invalid flag parameter to an SNA link intrinsic.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: The NAU has been activated.

ACTION: None.

CAUSE: The SNA link product was unable to expand the PXFILE portion of your program's stack in order to set up an additional AFT entry to accommodate the SNA session you requested.

ACTION: Too many files have been opened by your program. Try again.

CAUSE: Invalid Pacing Indicator in Request/Response Header.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: Invalid Begin Chain Indicator in Request/Response Header.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: Invalid End Chain Indicator in Request/Response Header.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: Invalid Enciphered Data Indicator in Request/Response Header.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: SNA IMF failed to initialize reserved bits in the Request/Response Header.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The SNA link product detected an internal error in the SNA Transport subsystem.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: SNA IMF passed to an SNA link intrinsic an RU that exceeded the allowable size for this session.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The NAU is not active.

ACTION: Ensure that the NAU has been activated on the host side.

CAUSE: SNA IMF passed an invalid Plabel to the SNAcontrol intrinsic.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: A message on the LU-SSCP session is pending and must be completed before proceeding further.

ACTION: Issue a call to RECV3270 before proceeding.

CAUSE: The RU size used by SNA IMF is too small to contain the data to be returned by the SNA link product.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The snaclassname specified in the snalnkinfo parameter of the OPEN3270 intrinsic is invalid for this node.

ACTION: Ask the network manager to check the SNA configuration and provide you with a valid SNA LU class.

CAUSE: The securityclass specified in the snalnkinfo parameter of the OPEN3270 intrinsic is invalid for this node.

ACTION: Ask the network manager to check the SNA IMF configuration and provide you with a valid SNA IMF security class name.

CAUSE: An invalid session type parameter was passed to the SNA link product.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: A negative response occurred on the LU-SSCP session.

ACTION: Make sure the host application that you are trying to access is operational. If it is, note the circumstances and contact your HP representative.

CAUSE: The node manager (NMMGR) configuration file name (NMCONFIG) is incorrect, or the file is corrupt or missing.

ACTION: Check the node manager configuration file (NMCONFIG); it should not contain errors.

CAUSE: A request is already pending.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The SNA link product determined that there were no free NAUs in the specified SNA class name.

ACTION: Ask the system manager to check the SNA configuration for other valid snaclassname values you can use.

CAUSE: A previous I/O request has not been completed.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: SNA IMF passed the SNA link product an invalid function code parameter.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The SNA link product detected either an inactive SNA node or an invalid SNA nodename.

ACTION: Check the SNA nodename you requested. Either it is incorrect or you must start the node by using the SNACONTROL START command.

CAUSE: SNA IMF and the SNA link product are not synchronized with respect to the type of session established.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: SNA IMF passed SNAErrMsg an invalid error code parameter.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: An SNA link intrinsic was called which required Privilege Mode (PM) capability.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: SNA IMF passed SNASessInfo an invalid InfoWanted parameter.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: There are no requests pending.

ACTION: None.

CAUSE: The SNA node has been shutdown.

ACTION: Call the CLOSE3270 intrinsic.

CAUSE: The SNA link product is processing a protocol shutdown. The SNA node is being shutdown.

ACTION: Finish current processing, then call the CLOSE3270 intrinsic.

CAUSE: The SNA link product has requested line quiesce. The SNA node is being restrained from starting new jobs. As the current jobs finish, the SNA system gradually winds down until jobs are no longer running.

ACTION: Call the CLOSE3270 intrinsic.

CAUSE: The message catalog CATSNA.PUB.SYS is invalid.

ACTION: Inform your system manager

CAUSE: The SNA Transport message catalog file (CATSNA.PUB.SYS) is missing, invalid, or locked by another process.

ACTION: Inform your system manager.

CAUSE: The SNA link product could not process a request made by the SNA IMF Pass Thru process due to insufficient stack space.

ACTION: Try running or preparing your program again, but specify a larger stack size in the stack parameter of the PREP or RUN command.

CAUSE: SNA IMF passed the SNA link product an invalid data offset parameter. It was probably negative or longer than the length of the message.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The SNA link product detected a link failure. The link for the SNA node has gone down.

ACTION: Call the CLOSE3270 intrinsic.

CAUSE: The SNA link product is processing an internal shutdown. The SNA nodes are being shutdown.

ACTION: Call the CLOSE3270 intrinsic.

CAUSE: The SNA link product is processing a hierarchical shutdown (the host has deactivated your session). The LU is being shutdown.

ACTION: Call the CLOSE3270 intrinsic.

CAUSE: SNA IMF passed the SNA link product an invalid MaxInfoLength parameter.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: A buffer too small to hold the error message from the SNA Transport message catalog file was passed in a call to the HPSNAErrmsg or SNAErrmsg intrinsic. The message was truncated to fit into the buffer that was passed.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: An expedited response is pending and must be completed before proceeding.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The host has not sent the necessary command sequence to activate your session.

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.

CAUSE: The host has not sent the necessary command sequence to activate your session.

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.

CAUSE: An internal error has occurred in the SNA link subsystem, or an illegal request was received from the host.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: SNA IMF has requested recovery for the session.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: There is no STSN pending.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: The primary requested an unsupported function. The SNA link product does not support Cryptography Verification (CRV).

ACTION: Change the host application's BIND to turn off cryptography.

CAUSE: An unsupported session control request was attempted.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: An unsupported session control response was detected by the SNA link product.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: An SNA service is trying to send a response to a deactivation request (UNBIND, DACTLU, DACTPU), but no such deactivation request has been received.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: An SNA service is trying to send a response to an activation request (BIND, ACTLU, ACTPU), but no such activation request has been received.

ACTION: Ensure that the NAU has been activated on the host.

CAUSE: The primary session control has not sent a Clear.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: Internal error in SNA Transport's IOWAIT intrinsic.

ACTION: Contact your HP representative.

CAUSE: When changing from compatibility mode (CM) to native mode (NM), an error occurred when an SNA compatibility mode intrinsic was called.

ACTION: Note the circumstances and contact your HP representative.

CAUSE: Internal SNA Transport error.

ACTION: Contact your HP representative.

CAUSE: Internal SNA Transport error.

ACTION: Contact your HP representative.