Chapter 94 SNAX (SNAX/APN and SNAX/XF) Messages

The line handler has detected a fatal error condition on a logical device used by SNAX/XF or SNAX/APN.

The specific cause of the condition reported in this message, the resulting effect on the system, and the recommended recovery action depend on the displayed cause text, as described in the following paragraphs. This message applies to D-series RVUs only.

CAUSE: allocate-segment

Cause  There was a failure in the allocation of a memory segment. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough resources for the service-manager process or the line-handler process, then retry the operation. See Appendix E, for information on the specified error.

CAUSE: An Interrupt Handler was specified for SNAX/XF over token ring, which has no Interrupt Handler

Cause  The INTERRUPT modifier was specified in the SYSGEN configuration file for a Token Ring line. INTERRUPT is not a valid modifier for Token Ring lines. This message is generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  If SYSGEN was used for configuration, delete the INTERRUPT modifier in the SYSGEN configuration file and reexecute the SYSGEN phase of installation.

CAUSE: An Interrupt Handler was specified for SNAX/XF over X25, which has no Interrupt Handler

Cause  The INTERRUPT modifier was specified in the SYSGEN configuration file for a SNAX/XF line over an X.25 line. INTERRUPT is not a valid modifier for such a line. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  If SYSGEN was used for configuration, delete the INTERRUPT modifier in the SYSGEN configuration file and rerun the SYSGEN phase of installation.

CAUSE: An invalid device subtype was specified

Cause  An invalid device subtype was specified. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  If SYSGEN was used for configuration, correct the SUBTYPE modifier in the SYSGEN configuration file and reexecute the SYSGEN phase of installation.

CAUSE: CSM-timeout

Cause  The Communications Subsystem Manager (CSM) process has timed out. CSM did not process a request within the allotted amount of time. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

CAUSE: define-pool

Cause  A failure occurred when SNAX/XF or SNAX/APN issued a call to the DEFINEPOOL procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the line-handler process.

CAUSE: device-type-invalid

Cause  An incorrect device type for the line was specified in the SYSGEN configuration file. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  If SYSGEN was used for configuration, verify the validity of the SYSGEN configuration file and reexecute the SYSGEN phase of installation after correcting the device type.

CAUSE: Failure to allocate system resources

Cause  A failure to allocate system resources has occurred.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough system resources available.

CAUSE: Failure to obtain system information from the DCT table

Cause  SNAX/XF or SNAX/APN failed to obtain system information from the destination control table (DCT).

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

CAUSE: get-pool

Cause  A failure occurred when SNAX/XF or SNAX/APN issued a call to the GETPOOL procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the service-manager process or the line-handler process.

CAUSE: interrupt-invalid

Cause  The specified interrupt handler was not correct. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  If SYSGEN was used for configuration, verify the validity of the SYSGEN configuration file and reexecute the SYSGEN phase of installation after correcting the INTERRUPT type.

CAUSE: IO-get

Cause  SNAX/XF or SNAX/APN received an error while calling the IOGET internal procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

CAUSE: IO-put

Cause  SNAX/XF or SNAX/APN received an error code while calling the IOPUT internal procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

CAUSE: link-to-CSM

Cause  SNAX/XF or SNAX/APN could not link to the Communications Subsystem Manager (CSM) process. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify the validity of the SYSGEN configuration file. If the problem cannot be corrected by correcting the configuration file, contact your service provider and provide all relevant information as follows:

CAUSE: lock-memory

Cause  A failure occurred when SNAX/XF or SNAX/APN issued a call to the LOCKMEMORY procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the service-manager process or the line-handler process.

CAUSE: subdevice-type-invalid

Cause  An incorrect subdevice type was specified in the SYSGEN configuration file. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  If SYSGEN was used for configuration, verify the validity of the SYSGEN configuration file and reexecute the SYSGEN phase of installation after correcting the subdevice type.

If the Configuration Utility Program (COUP) was used for configuration, use the COUP to specify the correct subdevice type.

CAUSE: Unable to obtain extended buffer space during initialization

Cause  SNAX/XF or SNAX/APN could not obtain extended buffer space during initialization. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are sufficient memory resources for the line-handler process.

CAUSE: units-invalid

Cause  The number of I/O units provided to SNAX/XF or SNAX/APN is invalid. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify the validity of the SNAX/XF or SNAX/APN configuration and correct the faulty specification.

CAUSE: usesegment

Cause  A failure occurred when SNAX/XF or SNAX/APN used a memory segment. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the line-handler process.

The line handler has detected a fatal error condition on a logical device used by SNAX/XF or SNAX/APN.

The specific cause of the condition reported in this message, the resulting effect on the system, and the recommended recovery action depend on the displayed cause text, as described in the following paragraphs. This message applies to G-series RVUs only.

CAUSE: allocate-segment

Cause  There was a failure in the allocation of a memory segment. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough resources for the service-manager process or the line-handler process, then retry the operation. See Appendix E, for information on the specified error.

CAUSE: An invalid device subtype was specified

Cause  An invalid device subtype was specified. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Correct the SUBTYPE modifier in the SNAX/XF or SMAX/APN configuration.

CAUSE: ConMgr-timeout

Cause  The concentrator manager (ConMgr) process has timed out. The ConMgr did not process a request within the allotted amount of time. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

CAUSE: define-pool

Cause  A failure occurred when SNAX/XF or SNAX/APN issued a call to the DEFINEPOOL procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the line-handler process.

CAUSE: device-type-invalid

Cause  An incorrect device type for the line was specified in the SNAX/XF or SNAX/APN configuration. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Change the value of the device type for the line in your SNAX/XF or SNAX/APN configuration.

CAUSE: Failure to allocate system resources

Cause  A failure to allocate system resources has occurred.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough system resources available.

CAUSE: Failure to obtain system information from the DCT table

Cause  SNAX/XF or SNAX/APN failed to obtain system information from the destination control table (DCT).

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

CAUSE: get-pool

Cause  A failure occurred when SNAX/XF or SNAX/APN issued a call to the GETPOOL procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the service-manager process or the line-handler process.

CAUSE: WANSD_IO-get

Cause  SNAX/XF or SNAX/APN received an error while calling the WANSD_IOGET internal procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

CAUSE: link-to-ConMgr

Cause  SNAX/XF or SNAX/APN could not link to the concentrator manager (ConMgr) process. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify the validity of the SNAX/XF or SNAX/APN configuration. If the problem cannot be corrected by correcting the configuration file, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

CAUSE: lock-memory

Cause  A failure occurred when SNAX/XF or SNAX/APN issued a call to the LOCKMEMORY procedure. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the service-manager process or the line-handler process.

CAUSE: subdevice-type-invalid

Cause  An incorrect subdevice type was specified in the SNAX/XF or SNAX/APN configuration. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Change the subdevice type in your SNAX line configuration.

CAUSE: Unable to obtain extended buffer space during initialization

Cause  SNAX/XF or SNAX/APN could not obtain extended buffer space during initialization. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are sufficient memory resources for the line-handler process.

CAUSE: usesegment

Cause  A failure occurred when SNAX/XF or SNAX/APN used a memory segment. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN terminates.

Recovery  Verify that there are enough memory resources for the line-handler process.

Cause  SNAX/XF or SNAX/APN received an invalid state-machine error or detected a protocol violation.

Effect  The operation aborts. The finite state machine goes into the reset or recovery state.

Recovery  If the I/O process can recover from the internal error, SNAX/XF or SNAX/APN continues to run. If not, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  No extended buffer pool space is available to complete the current request.

Effect  The current request is not finished.

Recovery  Increase the XPAGES attribute value by using an ADD LINE or ALTER LINE command. If this does not correct the problem, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A path-control request other than RESET or DISCONNECT was issued while the physical unit (PU) address table was not initialized.

Effect  The request is ignored.

Recovery  If the I/O process can recover from the internal error, SNAX/XF or SNAX/APN continues to run. If not, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error has occurred in an internal line-handler component.

Effect  The system reports the problem and continues processing.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The processor pair running the luname’s service-manager process failed.

Effect  All the added lines are quiesced and deleted.

Recovery  On a subsequent reload of the failed processors, add the SNAX/APN configuration.

Cause  The CONMGR process was not started when the SNAX line‑handler tried to communicate with it. This message applies to G-series RVUs only.

Effect  If the above message is displayed as a result of an SCF START LINE request on a SNAX line, the line is not started. If the above message is displayed as a result of a STOP DEVICE request on a SNAX line, the message is informational only. The device is stopped if there are no further errors.

Recovery  Start the CONMGR process using SCF. In case the message is observed as a result of an SCF START LINE request, abort and restart the line.

Cause  The primary SNAX line‑handler or service‑manager process is unable to start its backup process. This message applies to G-series RVUs only.

Effect  The SNAX device does not have NonStop capabilities at this time.

Recovery  If the backup processor is not up, the backup process is created when that process is reloaded. If the backup processor is already up, this device cannot start its backup process due to a system error. To restore NonStop capabilities, the device has to be stopped and restarted using SCF STOP DEVICE and START DEVICE requests to the WAN Manager (WANMGR).

Cause  The service manager received a link INOP message from a line handler because of a link-related connect or contact failure.

Effect  The line becomes inoperative.

Recovery  Abort the line, then restart it. Because a switched line has only one physical unit (PU), you can safely use the ABORT command rather than the STOP command.

Cause  Local and remote direct-connect line handlers have exchanged reset sequences, and the line is ready to accept network requests.

Effect  A connection is successfully established with a remote device.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator has brought down a line, or an error has occurred that brought it down. For X.21, this message occurs when an attempt to disconnect a switched line fails.

Effect  The line is inoperative; all devices attached to the line are disconnected.

Recovery  Abort the line, then restart it. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  An attempt to disconnect a switched line failed. This message is generated by the service-manager process.

This message is displayed with SNAX/XF or SNAX/APN operator message 42, which is also described in this chapter.

Effect  SNAX/XF or SNAX/APN line linename is not available.

Recovery  Abort the line, then restart it. Because a switched line has only one subordinate physical unit (PU), you can safely use the ABORT command rather than the STOP command. See Appendix B, for information on errnum.

SNAX/XF or SNAX/APN detected a nonfatal error (warning condition) in the configuration of a line.

The specific cause of the condition reported in this message, the resulting effect on the system, and the recommended recovery action depend on the displayed cause-num and cause-text, as described in the following paragraphs.

These causes apply to D-series RVUs only:

Cause: 1, The SYSGEN modifier CSMLDEV is obsolete

Cause  The CSMLDEV modifier was specified in the SYSGEN configuration file, but the CSMLDEV modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the CSMLDEV modifier from the SYSGEN configuration file.

Cause: 2, The SYSGEN modifier SMLDEV is obsolete

Cause  The SMLDEV modifier was specified in the SYSGEN configuration file, but the SMLDEV modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the SMLDEV modifier from the SYSGEN configuration file.

Cause: 3, The SYSGEN modifier SHMRETRIES is obsolete

Cause  The SHMRETRIES modifier was specified in the SYSGEN configuration file, but the SHMRETRIES modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the SHMRETRIES modifier from the SYSGEN configuration file.

Cause: 4, The SYSGEN modifier DIALOUTRETRIES is obsolete

Cause  The DIALOUTRETRIES modifier was specified in the SYSGEN configuration file, but the DIALOUTRETRIES modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the DIALOUTRETRIES modifier from the SYSGEN configuration file.

Cause: 5, The SYSGEN modifier REDIALINT is obsolete

Cause  The REDIALINT modifier was specified in the SYSGEN configuration file, but the REDIALINT modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the REDIALINT modifier from the SYSGEN configuration file.

Cause: 6, The SYSGEN modifier KMLDEV is obsolete

Cause  The KMLDEV modifier was specified in the SYSGEN configuration file, but the KMLDEV modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the KMLDEV modifier from the SYSGEN configuration file.

Cause: 7, The SYSGEN modifier LUNSTIMEOUT is obsolete

Cause  The LUNSTIMEOUT modifier was specified in the SYSGEN configuration file, but the LUNSTIMEOUT modifier is no longer used by SNAX/XF or SNAX/APN. This message was generated by the service manager.

Effect  Normal processing continues.

Recovery  Delete the LUNSTIMEOUT modifier from the SYSGEN configuration file.

Cause: 8, The value of the SYSGEN modifier FRAMESIZE is invalid for 6203/6204 controller

Cause  The value specified for the FRAMESIZE modifier is outside the range allowed for lines that use 3604, 6203, and 6204 controllers. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Specify FRAMESIZE with a value in the range 75 through 4107 bytes.

Cause: 9, The value of the SYSGEN modifier FRAMESIZE is invalid for CSS-type Lines

Cause  The value specified for the FRAMESIZE modifier is outside the range allowed for lines that use 3605 and 3650 controllers. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Specify FRAMESIZE with a value in the range 75 through 2036 bytes.

Cause: 10, The value of the SYSGEN modifier FRAMESIZE is invalid for X.21 interface

Cause  The value specified for the FRAMESIZE modifier is outside the range allowed for SNAX/XF or SNAX/APN lines that use an X.21 interface. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  Specify FRAMESIZE with a value in the range 75 through 1792 bytes.

Cause: 13, The SYSGEN modifier RNRTIMER is invalid when used with SNAX/XF over X.25 Lines

Cause  The RNRTIMER modifier was specified for an X.25 line. This modifier is invalid for X.25 lines, and SNAX/XF or SNAX/APN ignored the specification. This message is generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the RNRTIMER modifier from the SYSGEN configuration file.

Cause: 15, The value of the SYSGEN modifier COUNTRY is invalid

Cause  The value specified for the COUNTRY modifier is invalid. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN uses the default value, U.S. and Canada (American). Normal processing continues.

Recovery  Specify a valid value for the COUNTRY modifier in the SYSGEN configuration file.

Cause: 16, The value of the SYSGEN modifier L2WINDOW is invalid

Cause  The value specified for the L2WINDOW modifier is outside the permissible range. This message was generated by the line handler.

Effect  Normal processing continues.

Recovery  For the L2WINDOW modifier, specify a value from 1 through 7 in the SYSGEN configuration file.

Cause: 18, The value of the SYSGEN modifier INTERRUPT is invalid for the 3605/3650 controller

Cause  The value specified for the INTERRUPT modifier is invalid for lines that use 3605 and 3650 controllers. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN uses SNA^CSS^INTERRUPT as the interrupt handler. Normal processing continues.

Recovery  Specify SNA^CSS^INTERRUPT for the INTERRUPT modifier in the SYSGEN configuration file.

Cause: 19, The SYSGEN modifier RNRTIMER is invalid when used with SNAX/XF over Token-Ring Lines

Cause  The RNRTIMER modifier was specified for a Token Ring line. This modifier is invalid for Token Ring lines, and SNAX/XF or SNAX/APN ignored the specification. This message is generated by the line handler.

Effect  Normal processing continues.

Recovery  Delete the RNRTIMER modifier from the SYSGEN configuration file.

This cause applies to G-Series RVUs only:

Cause: 15, The value of the SCF modifier COUNTRY is invalid

Cause  The value specified for the COUNTRY modifier is invalid. This message was generated by the line handler.

Effect  SNAX/XF or SNAX/APN uses the default value, U.S. and Canada (American). Normal processing continues.

Recovery  Specify a valid value for the COUNTRY modifier in the SCF configuration file.

linename	is the name of the line.
condition	is one of the following text messages indicating the degree or severity of the memory congestion: ENTERING MODERATE ENTERING CRITICAL EXITING NOTE: This message represents a critical event only when ENTERING CRITICAL is displayed.

Cause  During SNAX/APN operation, the memory manager in the line-handler process detected a memory congestion condition (if ENTERING MODERATE or ENTERING CRITICAL is displayed) or exited a previously existing memory congestion condition (if EXITING is displayed).

Effect  The effect depends on the value displayed for condition:

Recovery  If EXITING is displayed, this is an informational message only; no corrective action is needed. If ENTERING MODERATE or ENTERING CRITICAL is displayed, do one of the following:

Cause  Too many lines specifying the MULTI attribute were configured within a single line-handler process.

Effect  The specified line was not added.

Recovery  Reassign some of the lines that use the multiline feature to another line-handler process.

Cause  SNAX/XF or SNAX/APN PU puname sent an unnumbered acknowledgment (UA), indicating a successful exchange of control signals.

Effect  The system waits for the next command.

Recovery  Informational message only; no corrective action is needed.

Cause  A failure has occurred in an attempt to contact or activate a PU, or a PU was successfully disconnected by a deactivate request.

This message is displayed with SNAX/XF or SNAX/APN message 24, which is also described in this chapter.

Effect  SNAX/XF or SNAX/APN PU puname is no longer available for use. The line may be operational, but the caller is disconnected.

Recovery  If errnum is not 400 or 401, see Appendix B, for a definition of the specified error. For more detailed information on file‑system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  A failure occurred when SNAX/XF or SNAX/APN attempted to contact or activate a switched PU (for SNAX/XF, either a permanently subordinated PU or a switched floating PU).

Effect  SNAX/XF PU puname is not available for use.

Recovery  Abort the line, and then restart it. Because a switched line has only one subordinate PU, you can safely use the ABORT command rather than the STOP command. Recovery depends on the error received, as follows:

Cause  An error occurred when SNAX/XF or SNAX/APN attempted to add or contact a switched PU (for SNAX/XF, either a permanently subordinated PU or a switched floating PU).

Effect  The specified PU cannot be used.

Recovery  If error is 400, abort the PU, and then abort and restart the line. If error is 401, abort the line and then restart it. Any other value of error is a file‑system error. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  A PU was successfully connected with an activate request or was reconnected after a previous error.

Effect  The PU is available for use, and the system waits for the next command.

Recovery  Informational message only; no corrective action is needed.

Cause  A dial-in connection attempt from a remote physical unit (PU) failed for one of the following reasons:

Effect  SNAX/XF or SNAX/APN rejects the connection and continues processing.

Recovery  Verify that the attempt to connect is valid. Check the PUIDBLK and PUIDNUM of the caller and the PU to determine the cause of the mismatch, then take appropriate action.

Cause  SNAX/XF or SNAX/APN rejected a dial-in connection attempt from a remote PU because its PUIDBLK and PUIDNUM, contained in the XID response, do not match the PUIDBLK and PUIDNUM values of the permanently subordinated PU or SNAX/APN PU configured under the line.

Effect  SNAX/XF or SNAX/APN rejects the connection and continues processing.

Recovery  Verify that the attempt to connect is valid. Check the PUIDBLK and PUIDNUM of the caller and the PU to determine the cause of the mismatch, then take appropriate action.

Cause  During an XID (Format 3) exchange, SNAX/APN detected an error. The error, displayed in sense, is one of the sense data values whose meanings are given in Table 94-1.

Effect  The XID exchange is terminated, and the PU is not started.

Recovery  Analyze the sense code and the XID frame bit and byte offsets, and reconfigure so that the configuration parameters of the two link stations are no longer in conflict.

Cause  An application failed after a connection was made.

Effect  The PU is still connected, but no current session exists on the connection; that is, no LU-LU session has existed for the interval indicated.

Recovery  There are three alternatives:

Cause  A system services control point-logical unit (SSCP-LU) session became active.

Effect  Logical unit luname is available for use. The system waits for the next command.

Recovery  Informational message only; no corrective action is needed.

Cause  A system services control point-logical unit (SSCP-LU) session became inactive, or an ACTLU response is pending. An ACTLU command is sent from the SSCP to the LU to activate a session.

Effect  The LU is no longer available for use, and the system waits for the next command.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt to add or activate a switched floating LU failed. Possible causes for the failure are as follows:

Effect  A switched floating LU is not available for use.

Recovery  Abort the physical unit (PU) and restart the PU and LU. Recovery depends on the type of error received, as follows:

Cause  The number of bytes sent by the LU exceeded the file-system limit, indicating a possible error in the hardware for the LU.

Effect  The LU is not available for use.

Recovery  Abort the LU and restart it.

Cause   The number of bytes sent by the LU exceeded the file-system limit, indicating a possible error in the hardware for the LU.

Effect  The SNAX/XF or SNAX/APN buffer could be depleted, and applications could begin receiving file-system error number 31.

Recovery  Abort and restart the LU, and then begin a trace on the line. If the message appears again, stop the trace, contact your service provider, and submit the trace file. When you finish the trace, abort the LU and do not restart it until the hardware is tested.

When contacting your service provider, provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An SNA request unit (RU) error occurred on a session with a SNAX/APN remote LU using the CRT1, CRT2 (also specified as CRT), CRT3, or ITI protocol. Some of the possible errors are listed below:

The message display identifies the type of RU on which the error occurred: BIND, CANCEL, FMD, LUSTAT, RTR, SDT, or UNBIND.

Effect  The session is deactivated if it was previously activated. Any outstanding requests are finished with file-system error 66 (device down).

Recovery  Examine the SNA sense code in sense. See Appendix B, for information on the specified error. See the IBM Systems Network Architecture Network Product Formats manual for recovery action.

If the problem can be corrected, close, reopen, and restart the remote LU.

Cause  An error occurred on the specified service-manager component.

Effect  The system recovers.

Recovery  Informational message only; no corrective action is needed.

Cause  A version mismatch exists between the line handler and the service manager objects.

Effect  The error message displays the versions of the service manager and the line handler, as well as the name of the service manager that owns the line.

Recovery  Either issue an SCF INFO LINE command with the DETAIL option on the specified LINE object or assumed LINE object and an SCF INFO SUBSYS command with the DETAIL option, or run the VPROC utility program on the SNATSOBJ and SVMOBJ object modules. Compare the two versions.

If the service manager for the line is "UNKNOWN," the line is not currently added to any service manager. First, issue a SETMANAGER command to specify a service manager using the same IPM or release version as the line handler, then add the line.

If the service manager for the line is a valid process name, the line is already added to that service manager. Issue a SETMANAGER command to that service manager, then add the line again.

If the service manager for the line is specified as "????????," the line handler uses an older version of the service manager. Select a service manager that uses the same IPM or release version as the line handler, issue a SETMANAGER command to that service manager, then add the line.

Use SCF DEVICE commands to configure service-manager and line-handler object modules from the same IPM or release

Cause  The service manager could not find buffer space from the extended buffer pool.

Effect  The service manager is unable to perform or complete the task.

Recovery  On D-series RVUs, use SYSGEN to reconfigure the service manager, employing a larger value for EXTPOOLPAGES.

On G-series RVUs, reconfigure the service manager, employing a larger value for EXTPOOLPAGES.

If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

This error message is sent when the LU Network Services (LUNS) component of the service manager detects an error. It has the following general format:

In an individual display, the codes and names that appear in the memory-addr, errnum, object-1-name, object-2-name, and info fields depend on the LUNS error code lerr, contained in the first field. The following pages show all displays generated by LUNS. They are ordered according to their LUNS error code number. The LUNS error code numbers range from 2305 through 2341

Cause  LU Network Services (LUNS) was processing an Enhanced System Services Command (ESSCMD) record in the terminal’s Enhanced System Services (ESS) table, and that record contains SENDHOST Y and either a GATELINE, GATEPU, or GATELU specification.

In attempting to establish a pass-through session with a host application, LU Network Services (LUNS) could not find object-1-name for the reason indicated by%info1. The variable %info1 can have the following octal values:

Effect  The request that was being processed is rejected.

Recovery  Depending on the nature of the failure, perform one or more of the following steps:

Cause  LU Network Services (LUNS) could not get %word-size of buffer space when processing a request on behalf of the LU named linename.luname.

Effect  The request that was being processed is rejected.

Recovery  Try the request again. If the terminal is locked up, have the operator abort and restart the LU through the SCF. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal error occurred when an internal message was being sent from the LU Network Services (LUNS) service manager to the line handler that services the LU named linename.luname.

Effect  The request that was being processed is rejected.

Recovery  Try the request again. If the terminal is locked up, have the operator abort and restart the LU through the SCF. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  LU Network Services (LUNS) received the ALLOCATESEGMENT error errnum when attempting to allocate an extended-memory segment for table-name (that is, the object disk file for table-name was to become a virtual-memory swap file). This error occurs whenever a table is specified whose object disk file does not exist or resides on another system, but it can occur for other reasons.

If table-name is SVM^SEG, it is the service manager’s control-block segment swap file and not a table. In this case, the error can be fatal to SNAX/XF or SNAX/APN.

Effect  The named table is not placed in use.

Recovery   See Appendix E, for information on the specific cause of the ALLOCATESEGMENT error. If errnum indicates that the object file for table-name does not exist and table-name is the name of an ESS table, verify that the table’s object-file name specification in the currently active SET table is correct. If so, verify that the table’s object file exists on this system. (The ALLOCATESEGMENT procedure creates a null file of the same name when it does not find the file specified in the ALLOCATESEGMENT procedure call.)

Cause  LU Network Services (LUNS) received a USESEGMENT error when attempting to place table-name in use through a USESEGMENT call.

If table-name is SVM^SEG, it is the service manager’s control-block segment swap file and not a table. In this case, the error can be fatal to SNAX/XF or SNAX/APN.

Effect  The named table is not placed in use.

Recovery  Try the request again. If the terminal is locked up, have the operator abort and restart the LU through the SCF. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The table named table-name has an invalid object file name. The table’s object-file-name does not match the object-file name stored in the first record of the object file.

	NOTE: This error (LU Network Services (LUNS) error 2312) might be the result of using a RENAME command to change the object-file name of a LUNS table. When you use this method to rename a table’s object file, the first record in the file (the descriptor record) remains unchanged. For example, if you rename table SET1O (table SET1’s object file) with the new name SET2O, the first record in file SET2O still contains the table’s old file name SET1O. You must use the SNAXUTL SELECTFILE command to change a table’s object-file name. Note also that the volume and subvolume elements of the table’s fully qualified file name are stored in the descriptor record, but are not used in the validity check that produces LUNS error 2312.

Effect  The named table is not placed in use. If the named table is a SET table, LU Network Services (LUNS) is not enabled.

Recovery  Check the SNAXUTL output from the creation of table-name. The name specified in the SELECTFILE command, with the letter O appended, is the name that is stored in the first record of table-name’s object file.

Either rename the existing table object file to its original object-file name or rebuild the table using a new SELECTFILE command. If the latter is done, the LUNS pointer to the table’s object file must be changed as follows:

Cause  A command from, or on behalf of, the terminal LU named luname referenced an Enhanced System Services (ESS) table named table-name that is not defined in the currently active SET table.

Effect  The named table is not placed in use.

Recovery  If table-name is the correct name of a valid ESS table, use SNAXUTL to add table-name’s definition to the currently active SET table.

If table-name is incorrect, you must locate its incorrect specification and correct it. The problem might be in the SCF definition of the LU. Using the SCF command INFO LU luname, determine if table-name is displayed for the ESSTABLE attribute.

If so, a temporary correction can be made using the SCF STOP LU, ALTER LU, and START LU commands. A permanent correction might be necessary to the SCF ADD LU command that created the LU. If line or PU default values are employed for the ESSTABLE attribute of the LU, check the ADD PU and ADD LINE commands that create the LU’s PU and line and correct them if necessary.

Cause  LU Network Services (LUNS) was searching for the record named record‑name in the table named table-name and could not find it. The end of an Enhanced System Services (ESS) table was reached before the desired record was found. This error indicates that the table’s object file has been corrupted.

Effect  The request that was being processed is rejected.

Recovery  Save table-name’s corrupted object file by renaming it and noting its new name. The value for table-name’s object-file name is table-name with the letter O appended (for example, ESSTAB1’s object-file name is ESSTAB1O).

Rebuild table-name using SNAXUTL and retry the command. If the problem persists with a new table object file, the table’s corruption is a persistent problem and requires immediate attention. In either case, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  LU Network Services (LUNS) could not find message-name in the terminal’s Enhanced System Services (ESS) table named ess-table-name.

Effect  If the error occurs while LUNS is processing a character-coded request from a device, LUNS builds a message and sends it to the device. When displayed, this message informs the user that LUNS could not find the system message named message-name. If a formatted request is being processed, a System Network Architecture (SNA) sense code of 0801 is returned to the device.

Recovery  Use SNAXUTL and its ADD ESSMSG command to add the message to the terminal’s ESS table.

Cause  In the Enhanced System Services (ESS) table named ess-table-name, either the record-length or the message-length of the ESSMSG record named message-name is invalid.

The values for %record-length must be less than 4124 bytes, and the value for %message-length less than 4042 bytes.

Effect  If the error occurs while LU Network Services (LUNS) is processing a character-coded request from a device, LUNS builds a message and sends it to the device. When displayed, this message informs the user that the system message named message-name was not found. If a formatted request is being processed, an SNA sense code of 0801 is returned to the device.

Recovery  Use SNAXUTL and its DELETE and ADD ESSMSG commands to correct the message in error.

Cause  LU Network Services (LUNS) attempted to send an Enhanced System Services (ESS) message to a terminal, but no ESS table had been specified for the terminal’s LU named luname by means of an SCF ADD LINE, PU, or LU command, nor is a default ESS table specified in the currently active SET table. Therefore, no ESS table was assigned to the terminal, and LUNS could not locate the ESS message in an ESS table.

Effect  If the error occurs while LUNS is processing a character-coded request from a device, LUNS builds a message and sends it to the device. When displayed, this message informs the user that the system message named Snnnn was not found. If a formatted request is being processed, an SNA sense code of 0801 is returned to the device.

Recovery  Specify an ESS table name for the LU using the SCF ALTER LU command, or specify a default ESS table in a new active SET table. (You can use the SETTAB attribute of the SCF ALTER SUBSYS command to specify the new SET table.) If ALTER LU is used for temporary recovery, a permanent solution is required to prevent a future occurrence of this error; for example, specify the ESSTABLE attribute in the SCF ADD LU command for that LU.

Cause  An unsolicited logoff has been received for luname, and LU Network Services (LUNS) must inform creator-name. LUNS, however, cannot find creator-name.

Effect  The unsolicited logoff is finished.

Recovery  If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  During processing of a command from terminal-luname, which directed a logon to the host, LU Network Services (LUNS) could not find terminal‑luname after it had established the static path between terminal‑luname and gateway‑luname.

Effect  The logon process for this request is discontinued.

Recovery  Issue another logon. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An associated object (line, PU, or LU), named in assoc-name, is not in the proper state.

Effect  The request that was being processed is rejected.

Recovery  Check the state of the object using the SCF STATUS assoc-name command, and correct it if possible. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A FINDDCT error occurred during an attempt to communicate with the remote LU named assoc-luname through the remote service-manager process named in sscp-name.

Effect  The request that was being processed is rejected.

Recovery  Issue another logon or logoff. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  LU Network Services (LUNS) received a character-coded command from the terminal LU named in terminal-luname. The command matched the command name of an ESSCMD record in the terminal’s Enhanced System Services (ESS) table, and that record directed either a pass-through session with an application in the remote host or the establishment of a static path to the remote host’s system services control point (SSCP). A message was sent to a remote LUNS to assign a remote gateway LU, and the remote LUNS returned an error. The error is indicated by %info1, as follows:

Effect  The request that was being processed is rejected.

Recovery  Depending on the nature of the failure, perform one or more of the following steps in the following order:

Cause  LU Network Services (LUNS) received a character-coded command from the terminal LU named in terminal-luname. The command matched the command name of an ESSCMD record in the terminal’s Enhanced System Services (ESS) table. That record indicated either a pass-through session with an application in the remote host or an SSCP-LU session with the remote host’s SSCP. After the gateway LU named assigned‑remote‑gateway‑lu had been assigned, LUNS could not find terminal-luname.

Effect  The processing of the original request from terminal-luname is terminated.

Recovery  If the named terminal is now active, reissue the command. If the named terminal is inactive, use the SCF to activate the terminal and reissue the command.

If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  LU Network Services (LUNS) received, from a device, an SNA INIT-SELF request whose device logical unit (DLU)-name field matched the command name of an ESSCMD record, cmd-name, in the terminal’s Enhanced System Services (ESS) table, table-name. However, the cmd-name record in the ESS table is not an INITSELF‑RECEIVED type record.

Effect  The INIT-SELF request is rejected with SNA sense code 0806.

Recovery  Check if table-name is the correct ESS table for this terminal. If not, a temporary correction can be made using the SCF STOP LU, ALTER LU, and START LU commands. (Use the ESSTABLE attribute with the ALTER LU command.) A permanent correction might be necessary to the SCF ADD LU command that created the LU. If LINE or PU default values are employed for the ESSTABLE attribute of the LU, check the ADD PU and LINE commands that create the LU’s PU and line and correct them if necessary.

If the correct ESS table is assigned to the terminal, do one of the following:

Cause  LU Network Services (LUNS) received, from a terminal, an SNA INIT-SELF request whose DLU-name field matched the command name of an ESSCMD record, cmd-name, in the terminal’s Enhanced System Services (ESS) table, ess‑table‑name. The information in this record was used to build a new INIT-SELF request; however, the length of the new INIT-SELF request was greater than 256 bytes.

Effect  The INIT-SELF request is rejected with SNA sense code 0801.

Recovery  Use SNAXUTL and its DELETE and ADD ESSCMD commands to correct the cmd-name record in ess-table-name.

Cause  A SNAX/XF or SNAX/APN internal error occurred when a READLINK operation was performed on the LU named linename.luname.

Effect  The request that was being processed is rejected.

Recovery  Try the request again. If the terminal is locked up, have the operator abort and restart its LU through the SCF. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  SNAXUTL is updating the table named table-name.

Effect  All requests for this table are rejected until SNAXUTL finishes updating the table.

Recovery  Wait for SNAXUTL to complete the update; retry the command.

If this error is recorded while SNAXUTL is not running, issue an SCF ALTER SUBSYS command to change the SETTAB attribute to the name of the current set table. If the error continues to be recorded while SNAXUTL is not running, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The SET table referenced in an SCF ALTER SUBSYS command is not present in the specified subvolume.

Effect  The request that was being processed is rejected.

Recovery  Determine why the SET table is not present and perform the appropriate corrective action.

Cause  A remote logon attempt or an attempt to acquire a remote 3270 device, using the extended logon facility (XLF) of SNAX/APN, failed. Possible causes for the failure are shown in Table 94-2.

Effect  The device logon or device acquire fails.

Recovery  If LOGON FAILED = CREATOR NOT STARTED, start a Creator application and retry. If LOGON FAILED = ERROR CODE, recovery depends on the value of error, as shown in Table 94-2.

Error number 14

Cause  The subdevice name configured in the CREATOR attribute for the TLOGMGR LU did not match the subdevice name for the SNAX Creator-2 APPL object.

Effect  The BIND command fails.

Recovery  Ensure that the subdevice name in the CREATOR attribute for the TLOGMGR LU matches the subdevice-name portion of the SNAX Creator-2 APPL object name.

Error number 160

Cause  Creator-2 has not opened the service manager and issued a Connect.

Effect  The BIND fails.

Recovery  Start Creator-2 and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Any other value for error indicates a file-system error code. For more information about file‑system error codes, see Appendix B.

The above display is the format for RECFMS and basic alerts.

pu	is the fully qualified name of the physical unit (PU) that generated the alert.
alert-cause	is a text string describing the general cause of the alert condition (for example, hardware, external power failure, microcode, and so on).
alert-component	is a text string describing the type of component that generated the alert condition (for example, printer, disk drive, and so on).
piu	is the path information unit (PIU) displayed in hexadecimal digits.
param4	is a text string contained in the Embedded Text vector of the RECFMS or in the Text Message (X’00’) MS Common Subvector of the basic alert.
param5	is one of the following text strings explaining why some data received in the RECFMS alert or basic alert cannot be displayed in one or more of the parameters. param5 can have the following values: TRANSLATION INCOMPLETE DUE TO EMS BUFFER OVERFLOW TRANSLATION INCOMPLETE DUE TO UNRECOGNIZED RU FIELD NOTE: This message represents a critical event only when the IBM alert type is X’01’ (permanent loss of availability). Otherwise, this is a noncritical event.

Cause  The service manager generates this message when a communications network management server (CNMS) associated with a physical unit (PU) sends an RECFMS or basic alert to its communications network management application (CNMA). The ability of the PU to perform its intended functions is affected.

Effect  The effect of this error is given in the parameters of the message.

Recovery  See the IBM Systems Network Architecture: Formats manual for corrective action or required intervention based upon the information presented in the display or contained in the path information unit (PIU).

The above display is the format for generic alerts.

pu	is the fully qualified name of the physical unit (PU) that generated the alert.
alert-cause	is a text string describing the general cause of the alert condition (for example, hardware, external power failure, microcode, and so on).
alert-component	is a text string describing the type of component that generated the alert condition (for example, printer, disk drive, and so on).
piu	is the path information unit (PIU) displayed in hexadecimal digits.
param4	is a code point, in hexadecimal notation, indicating the general cause of the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Generic Alert Data (X’92’) Alert MS Subvector.
param5	is a code point, in hexadecimal notation, indicating the general cause of the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Probable Causes (X’93’) Alert MS Subvector.
param6	is a code point, in hexadecimal notation, indicating the user cause of the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the User Causes (X’01’) User Causes Subfield included in the User Causes (X’94’) Alert MS Subvector.
param7	is a code point, in hexadecimal notation, indicating the recommended action for the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Recommended Action (X’81’) Network Alert Common Subvector.
param8	is a code point, in hexadecimal notation, indicating the installation cause of the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Install Causes (X’01’) Install Causes Subfield included in the Install Causes (X’95’) Alert MS Subvector.
param9	is a code point, in hexadecimal notation, indicating the recommended action for the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Recommended Action (X’81’) Network Alert Common Subvector.
param10	is a code point, in hexadecimal notation, indicating the failure cause of the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Failure Causes (X’01’) Failure Causes Subfield included in the Failure Causes (X’96’) Alert MS Subvector.
param11	is a code point, in hexadecimal notation, indicating the recommended action for the alert condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Recommended Action (X’81’) Network Alert Common Subvector.
param12	is a code point, in hexadecimal notation, indicating the recommended action for an alert condition whose cause cannot be determined. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and find the description of the Recommended Action (X’81’) Network Alert Common Subvector. NOTE: UNDETERMINED CAUSE; ACTION=param12 is always displayed alone and never in conjunction with other CAUSE and ACTION parameters.
param13	is a text string obtained from the Text Message (X’30’) Self-Defining Text Message Subfield within a Self-Defining Text Message (X’31’) MS Common Subvector.
param14	is one of the following text strings explaining why some data received in the generic alert NMVT cannot be displayed in one or more of the parameters. The param14 variable can have one of the following values: TRANSLATION INCOMPLETE DUE TO EMS BUFFER OVERFLOW TRANSLATION INCOMPLETE DUE TO UNRECOGNIZED RU FIELD NOTE: This message represents a critical event only when the IBM alert type is X’01’ (permanent loss of availability). Otherwise, this is a noncritical event.

Cause  The service manager generates this message when a communications network management server (CNMS) associated with a physical unit (PU) sends a generic alert to its communications network management application (CNMA). The ability of the PU to perform its intended functions is affected.

Effect  The effect of this error is given in the parameters of the message.

Recovery  See the IBM Systems Network Architecture: Formats manual for corrective action and required intervention based upon the information presented in the display or contained in the path information unit (PIU).

When alert data cannot be presented in readable form, the following default alert format is displayed:

The above display is the default alert format.

pu	is the fully qualified name of the physical unit (PU) that generated the alert.
piu	is the path information unit (PIU) displayed in hexadecimal digits.
note	is one of the following text strings explaining why the received RECFMS or NMVT alert is unreadable and, therefore, must be displayed as a series of hexadecimal digits: TRANSLATION INCOMPLETE DUE TO UNRECOGNIZED RU FIELD NO TRANSLATION DUE TO EMS BUFFER OVERFLOW NO TRANSLATION DUE TO UNRECOGNIZED RU FIELD NOTE: This message represents a critical event only when the IBM alert type is X’01’ (permanent loss of availability). When note contains the text TRANSLATION INCOMPLETE DUE TO UNRECOGNIZED RU FIELD, you can view critical fields with the OSM or TSM Event Viewer (on G-series RVUs) or look at the critical field on the ViewPoint screen (on D-series RVUs) to determine whether the event is critical. When note contains another text, you must examine the path information unit (PIU) to find the IBM alert type and determine whether the event is critical.

Cause  The service manager generates this message when a communications network management server (CNMS) associated with a physical unit (PU) sends an alert to its communications network management application (CNMA). The ability of the PU to perform its intended functions is affected.

Effect  The effect is provided in the PIU of the message in hexadecimal digits.

Recovery  See the IBM Systems Network Architecture: Formats manual for corrective action and required intervention based upon the information contained in the PIU.

Cause  The service manager generates this message when the communications network management (CNM) component receives a Network Management Vector Transport (NMVT) message containing solicited or unsolicited Response Time Monitor (RTM) data. RTM data includes collected response time data and the current RTM status. See the IBM Systems Network Architecture: Formats manual for a complete description of the RTM (X’0080’) Management Services (MS) Major Vector.

Effect  None; processing continues.

Recovery  Informational message only; no corrective action is needed.

	CAUTION: Do not forward RTM data to NetView or NET/MASTER on an IBM host.

Cause  A line statistics counter reached the limit set by the communications network application (CNMA) in a CNM SET STATISTICS LIMIT command.

Effect  The application should issue a CNM REQUEST STATISTICS command with the reset bit set to 1 so that the command resets the limit values.

Recovery  If the application does not issue a CNM REQUEST STATISTICS command, issue the command to reset the limit values.

Cause  An error occurred during a call to SSGET.

Effect  None

Recovery  Informational message only; no corrective action is needed. However, if the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred during a call to SSINIT.

Effect  None

Recovery  Informational message only; no corrective action is needed. However, if the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred during a call to SSNULL.

Effect  None

Recovery  Informational message only; no corrective action is needed. However, if the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred during a call to SSPUT.

Effect  None

Recovery  Informational message only; no corrective action is needed. However, if the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The EXTPOOLPAGES value specified during system generation is greater than the maximum allowed.

Effect  SNAX/XF or SNAX/APN automatically resizes EXTPOOLPAGES to the allowed maximum.

Recovery  Informational message only; no corrective action is needed. At your convenience, reconfigure the service manager with a value for EXTPOOLPAGES that is less than or equal to the allowed maximum.

Cause  Inconsistent passthrough session counts exist because an internal error has occurred in the service-manager process. If the value of veri-pthru is less than the value of cur-pthru, the value of cur-pthru is adjusted to match the value of veri-pthru.

Effect  None; the process continues.

Recovery  If this message occurs repeatedly, start a trace of the service manager at the time the error occurs. Then contact the Global Mission Critical Solution Center (GMCSC).

When contacting the Global Mission Critical Solution Center (GMCSC), provide all relevant information as follows:

Cause  An SNA ACTPU command failed for the PU. The PU has encountered a hardware problem.

Effect  The PU is no longer available for use. No PUs or logical units (LUs) subordinate to the line are available.

Recovery  See the IBM Systems Network Architecture Reference Summary or the IBM Systems Network Architecture: Formats manual for sense code information.

Cause  An SNA ACTLINK command has failed. This message indicates a hardware problem.

Effect  The line named line is no longer available for use. No physical units (PUs) or logical units (LUs) subordinate to the line are available.

Recovery  See the IBM Systems Network Architecture Reference Summary or the IBM Systems Network Architecture: Formats manual for sense code information.

Cause  The service-manager process could not communicate with a line-handler process because of multiple occurrences of file-system error 31 (no buffer space). The line‑handler line was overloaded with user messages or system messages, either temporarily (if the message does not occur repeatedly) or permanently (if it does occur repeatedly).

Effect  If the message appears only once, there probably are no noticeable effects on the Systems Network Architecture (SNA) environment. If the message repeats, line probably is not successfully processing messages to or from its devices. However, the SNAX/XF or SNAX/APN service‑manager process should continue servicing other SNAX lines.

Recovery  If the message recurs, perform a memory dump for each of the pair of processors in which the line-handler process is running. Then contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The service manager received a Systems Network Architecture (SNA) request or response that is not supported by SNAX/XF or SNAX/APN. The request or response could be either a valid SNA request code that is not supported by SNAX/XF or SNAX/APN or a valid request code that was corrupted by a communications line error.

Effect  The service manager rejects the PIU and continues processing.

Recovery  Verify that the request code is a valid SNA request code. If the request code is valid, then this request is not supported by HP. If the request code is not valid, the message could indicate a communications line error. If the error persists, check your communications hardware.

Cause  The service manager received a Systems Network Architecture (SNA) request or response from a resource that is unknown to the service manager. This message could indicate an inconsistency between the line-handler process and the service-manager process.

Effect  At the occurrence of this error, the service manager rejects the PIU and continues processing.

Recovery  If this error persists, start a service-manager trace and take a memory dump of the primary processor for the service manager. Then contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

An alternative to bringing down the processor is to abort and delete the entire configuration and then restart the subsystem.

Cause  The service manager received a PIU from a PU on a primary line, or a gateway PU received a PIU from a host system. The PU is not in the correct mode to send or receive this kind of PIU.

For example, the service manager might have received an ACTPU request from an outboard PU, or it might have received a response to an ACTPU request from an inboard physical unit.

This error might be caused by an inconsistency between the service-manager process and the line-handler process.

Effect   When this error occurs, the service manager rejects the PIU and continues processing.

Recovery  Abort and delete the PU, then add the PU and its configuration.

Cause  A communications-line error or inconsistency occurred between the line handler and the service manager. (If SNAX/APN is being used, note that SNAX/APN supports only formatted System Network Architecture (SNA) requests; it does not support character-coded requests.)

Effect  The service manager rejects the PIU and continues processing.

Recovery  Abort and delete the physical unit (PU), then add the PU and its configuration.

Cause  In a system in which the service manager was running as a NonStop process pair, an attempt was made to add or alter a SNAX/XF or SNAX/APN object. Because of a lack of memory, the backup service manager could not process a checkpoint from the primary service manager. Consequently, the primary service manager could no longer checkpoint to the backup service manager, and the backup service manager became unable to perform its backup function.

Effect  The backup service-manager process is unable to perform its backup function. If the primary service-manager process fails after this error occurs, the backup service-manager process deletes the primary service-manager resources, enters a quiescent state, and replies to all requests with file-system error 66; and the SNAX/XF or SNAX/APN subsystem stops.

Recovery  If you do not need the service manager to have NonStop capability, no corrective action is needed. If you require NonStop capability, use the DIVER program to take down the backup processor for the service manager and reload it using TACL. Try not to start too many processes on the backup processor so that the backup service manager can have enough memory to process all checkpoints from the primary service manager. If the problem persists, add more memory to the backup processor and reload it. See Appendix B, for information on the specified error.

Cause  Checkpointing from the primary service-manager process to its backup process was incomplete because one of the following situations occurred:

In both cases, the backup service manager did not precisely mirror the primary service manager.

Effect  The backup service-manager process is unable to take over from the primary process. The SNAX/XF or SNAX/APN subsystem stops.

Recovery  Perform a system load.

Cause  A line-handler or service-manager trace stopped unexpectedly while writing trace data to the extended data segment. The trace collector returned either one of its own error codes (if a text message is displayed for Cause) or a file-system error.

If a text message is displayed, it has the following meaning:

Trace not active The trace was no longer active (that is, the segment ID was set to a nonzero value) at the time the trace collector attempted to write the trace data to the extended segment.

Trace segment overflowed A segment overflow error occurred on a call to the MOVEX internal procedure made by the trace collector during transfer of data to the extended segment.

Trace segment allocation error A call to the USESEGMENT procedure failed. The call was made by the trace collector before writing trace data to the extended segment.

Trace collector failed The trace collector failed. If file-error is displayed, see Appendix B, for a description of the specified error.

Effect  Trace data is no longer being collected for the specified line-handler or service‑manager process.

Recovery  Check the parameters for the TRACE command that started this trace. If the SCF TRACE parameters COUNT and PAGES were specified, ensure that the specified values are large enough to prevent the trace from stopping prematurely.

If file-error is displayed, see Appendix B, for a description of the specified error. For more detailed information including recovery actions, see Guardian Procedure Errors and Messages Manual.

Cause   SNAX/APN sent a REGISTER request to its Network Node Server and it was rejected.

Effect  The LU is not registered.

Recovery  Take the recovery action suggested by the Sense Code. Stop and restart the LU to force another registration attempt.

Cause   If this message is displayed for session-state ACTIVE or PENDING, the message is informational. For session-state INACTIVE, the message indicates that the CP-CP session was lost for the reason indicated by sense-code.

Effect  For session-state INACTIVE, the message indicates that SNAX/APN End Node does not have a CP-CP session with its Network Node Server.

Recovery  For session-state INACTIVE, take the recovery action suggested by the Sense Code.

In most cases an ELF EMS message will indicate that the attempted logon request from a terminal has failed. Logon requests arrive in the form of a LOCATE(CDINIT) request from a network node. If an error occurs, the reply to the LOCATE(CDINIT) request will contain sense code 08010000 (resource not available), unless otherwise indicated.

Reason Code 00000002

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate the LOCATE(CDINIT) reply.

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000003

Cause  The SNALU application (APPL NAME) has not opened its LU, an indication that the application may not be running or that it is defective.

Effect  The logon request is rejected.

Recovery  Start or correct the SNALU application (APPL NAME) and retry the logon.

Reason Code 00000004

Cause  The user is attempting to logon to an ITI, CRT or SNALU application whose template LU was not defined with PROTOCOL ITI, PROTOCOL CRT, or PROTOCOL SNALU.

Effect  The logon request is rejected.

Recovery  SCF ALTER the PROTOCOL for the template LU to CRT, ITI or SNALU and retry.

Reason Code 00000005

Cause  A Template LU with a PROTOCOL of ITI or CRT has been opened by an application and cannot be used to create dynamic LUs.

Effect  The logon request is rejected.

Recovery  Template LUs should not be opened. Identify the application that opened the template LU and correct the application. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000006

Cause  An LU or its PU is not started.

Effect  The logon request is rejected.

Recovery  Check the status of the system for PU outages. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000007

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate a logon request buffer for delivery to Creator-2.

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000008

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate a control block for the dynamic LU.

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000009

Cause  Internal error in the Service Manager Process.

Effect  The logon request is rejected.

Recovery  Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000000A

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate a buffer containing a request to a Line Handler Process to add a dynamic LU.

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000000B

Cause  A file-system error occurred. A message from the Service Manager Process to a Line Handler Process requesting the Line Handler to add a dynamic LU failed.

Effect  The logon request is rejected.

Recovery  Check for a downed CPU or for other reasons for an inoperable Line Handler Process. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000000C

Cause  An invalid LOCATE(CDINIT) was received. A LOCATE(CDINIT) received from a network node did not contain key X'12C4' in the first GDS variable.

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000000D

Cause  A LOCATE(CDINIT) received from a network node did not contain key X'12C5'.

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000000E

Cause  A LOCATE(CDINIT) received from a network node did not contain a FQPCID vector.

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000000F

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate a LOCATE(CDINIT) reply buffer

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000010

Cause  An invalid LOCATE(CDINIT) was received. Any one of the following control vectors was found in the LOCATE(CDINIT), but the vector has an invalid length.

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000011

Cause  An Invalid LOCATE(CDINIT) was received. A Resource Identifier Control Vector was not found in the LOCATE(CDINIT).

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000012

Cause  An invalid LOCATE(CDINIT) was received. The Bind Image Control Vector was too small in the LOCATE(CDINIT).

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000013

Cause  An invalid LOCATE(CDINIT) was received. The Bind Image Control Vector was not found in the LOCATE(CDINIT).

Effect  The logon request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000014

Cause  An invalid LOCATE(CDINIT) was received. The Resource Identifier Control Vector was not found in the LOCATE(CDINIT).

Effect  The log on request is rejected.

Recovery  Check the network nodes for possible malfunctions. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000015

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate a CINIT buffer to send to an application.

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000016

Cause  A file-system error occurred. A message from the Service Manager Process to a Line Handler Process containing a CINIT destined for an application failed. The CINIT was accepted, but subsequently rejected.

Effect  The logon request is rejected.

Recovery  Check for a downed CPU or other reasons for an inoperable Line Handler Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000017

Cause  The Creator-2 APPL, specified in the template LU's CREATOR attribute, has been disconnected. The logon LU has been deleted before a session could be established.

Effect  The logon request is rejected.

Recovery  Reconnect the APPL by restarting the Creator-2 process and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000018

Cause  Temporary memory shortage in the Service Manager Process while an attempt was made to allocate a message buffer containing a CINIT to be sent to a Line Handler Process.

Effect  The logon request is rejected.

Recovery  Increase the XPAGES attribute of the Service Manager Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000019

Cause  A file-system error. A message containing a CINIT from the Service Manager Process to a Line Handler Process was not sent.

Effect  The logon request is rejected.

Recovery  Check for a downed CPU or other reasons for an inoperable Line Handler Process. Correct the problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000001A

Cause  Creator-2 has not opened the service manager and issued a Connect.

Effect  The logon request is rejected.

Recovery  Start Creator-2 and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000001B

Cause  An ABORT LU command has been received for an LU which has a LOCATE(CDINIT) reply queued.

Effect  The logon request is rejected.

Recovery  Restart the LU and its superior objects. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000001C

Cause  An LU was closed before an LU-LU session was established.

Effect  The logon request is rejected.

Recovery  This may be part of normal operation, or it may indicate an application which may have ABENDed or is otherwise malfunctioning. Correct any problem and retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000001D

Cause  Internal error in a Line Handler Process.

Effect  The logon request is rejected.

Recovery  Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000001E

Cause  Internal error in a Line Handler Process.

Effect  The logon request is rejected.

Recovery  Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 0000001F

Cause  Temporary memory shortage in a Line Handler Process while an attempt was made to send a BIND request to a requesting terminal.

Effect  The logon request is rejected.

Recovery  Increase the NT21BPAGES device modifier (SCF ALTER DEVICE) of the Line Handler Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000020

Cause  Temporary memory shortage in a Line Handler Process while an attempt was made to allocate storage for outbound data or a control block.

Effect  The logon request is rejected.

Recovery  Increase the NT21BPAGES device modifier (SCF ALTER DEVICE) of the Line Handler Process. Retry the logon. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Reason Code 00000021

Cause  A logon request has been rejected by Creator-2, Pathmon, or the user‑supplied Creator-2 server process.

Effect  The logon request is rejected.

Recovery  This message should be proceeded, in the EMS log, by a message that was issued by Creator-2, Pathmon, or the user-supplied Creator-2 server process. The first message should identify the reason for the failure. Correct that problem and retry the logon.

Reason Code 00000022

Cause  The Creator-2 application has not been added with SCF.

Effect  The logon request is rejected.

Recovery  Use SCF to ADD an APPL object which the Creator-2 process can open (ADD APPL $sscpname.#applname).

Reason Code 00000023

Cause  A SNALU application returned a negative response to a CINIT.

Effect  The logon request is rejected.

Recovery  Retry the logon. If the problem persists, check the coding and/or configuration of the SNALU application.

Reason Code 00000024

Cause  A negative response was received for a BIND sent by a SNALU application.

Effect  The logon request is rejected.

Recovery  Retry the logon. If the problem persists, check the coding and/or configuration of the SNALU application.

Reason Code 00000025

Cause  While waiting for a response to a BIND sent by a SNALU application, SNAX/APN received an UNBIND from the SNALU application.