Chapter 133 X25 (X25 Access Method) Messages

Cause  The operator successfully brought up X25 through the Peripheral Utility Program (PUP) UP command.

The state of the link between the host system and the packet network is described in X25 operator message 44 or 45.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator has removed the device or device path from the system, or the system has detected a hardware failure.

For D-series I/O processes, the operator has issued one of the following commands:

Or the process has brought itself down because it found an error.

For G-series I/O processes, the operator has issued either the Subsystem Control Facility (SCF) ABORT or SCF STOP command, or the process has brought itself down because it found an error.

Effect  All activity on the line stops.

Recovery  If an operator command did not cause this message, contact your support representative 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  X25 reported a change in the line quality. This report occurs whenever a change greater than or equal to 5 percent occurs.

Effect  The system reports the problem, then continues processing.

Recovery  If val is less than 95, examine the transmission quality of the communications lines and correct the cause of the transmission errors.

Cause  The line is ready to accept network requests. The frame level (level 2) is successfully initialized.

Effect  A connection is successfully established with a remote device.

Recovery  Informational message only; no corrective action is needed.

Cause  The modem or frame level (level 2) is not ready.

Effect  Communication with the remote line is not possible.

Recovery  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 error occurred at code location p-reg.

Effect  Application requests are aborted, and X25 recovers.

Recovery  Contact your support representative 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  See the error codes listed in Table 133-3 and Table 133-4. Message 90 indicates a more severe error. The error code accompanying this message is in decimal.

Effect  The input/output (I/O) process abends. Message 74 always precedes message 90.

Recovery  See the recovery actions described in Table 133-3. Additional information to help in troubleshooting can be found in the Event Management Service (EMS) log for message 74. See Table 133-4 for information on the X25‑specific error codes. Contact your support representative 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 CLEAR REQUEST packet has been received on the Virtual Circuit.

Effect  The Switched Virtual Circuit (SVC) is disconnected.

Recovery  Reconfigure the SVC.

Cause  A CLEAR REQUEST packet is transmitted on a particular Virtual Circuit.

Effect  Clears the Virtual Circuit.

Recovery  Call establishment must be done to reconfigure the SVC.

Cause  A multiple path failure, or CONMGR returns a fatal error.

Effect  Any read or write operation on the line fails.

Recovery  In most cases, the line tries to recover by initiating an Activate Path Sequence.

Cause  The link state is down.

Effect  When the line is in the STARTED state, any I/O operation on it fails.

Recovery  The link state is updated and made READY as soon as the link is up.

Cause  A START LINE command is issued, or a line tries to recover from any type of failure.

Effect  Gives the status of the activate path request.

Recovery  Informational message only; no corrective action is needed.

Cause  An FRMR is transmitted or received.

Effect  A line reset occurs.

Recovery  Line recovers automatically, but all SVCs have to be reconfigured manually.

Cause  X25 detected an error and reset the specified logical circuit.

Effect  User requests are aborted, and X25 resets the LCN. The application should do an end-to-end recovery.

Recovery  If the problem persists or occurs often, examine a trace and fix the problem (most likely a remote error or configuration problem).

Cause  A RESTART packet has been sent R20 or R10 times without receiving an appropriate response. Level 2 is functioning properly, but level 3 is not.

Effect  The line remains in state R2 or R3.

Recovery  Issue either the Subsystem Control Facility (SCF) STOP LINE and START LINE commands (on G-series RVUs) or the Peripheral Utility Program (PUP) DOWN and UP commands (on D-series RVUs). If the problem persists, inform the system manager at the remote site that the remote site system or network does not respond.

Cause  A RESET packet was sent R22 or R12 times on the specified logical circuit without receiving an appropriate response. Level 2 is functioning properly, but level 3 is not.

In cases of multiple circuits, this message may indicate that the link is down. In such cases, all of the logical circuits on the line are affected and the application itself may not be involved in the error.

Effect  If the logical circuit is a permanent virtual circuit (PVC), that circuit is placed in an out-of-order state and X25 message 225 is displayed. The circuit cannot be used.

If the logical circuit is a switched virtual circuit (SVC), the call is cleared.

Other logical circuits on the line are not affected.

In cases of multiple circuits, all of the circuits go down.

Recovery  Recovery depends on the application. There may be a configuration error; verify the LCN assignments.

Cause  A CLEAR packet was sent R23 or R13 times on the specified logical circuit without receiving an appropriate response.

In cases of multiple circuits, this message may indicate that the link is down. In such cases, all of the logical circuits on the line are affected and the application itself may not be involved in the error.

Effect  The logical circuit is placed in an out-of-order state and cannot be used. Other logical circuits on the line are not affected.

In cases of multiple circuits, all of the circuits go down.

Recovery  Recovery depends on the application. There may be a configuration error; verify LCN assignments.

Cause  The 3650/6100 communications subsystem (CSS) hardware failed while attempting to download the CLIP or the communications interface unit (CIU).

This message usually appears with EMS message 154 or 155, or with a file‑system error message.

Effect  The object is not downloaded but remains in the “starting” and “boot” states.

Recovery  Analyze the failure by looking at the CSM error code in #param3 and the accompanying message. Then issue a Subsystem Control Facility (SCF) (on G-series RVUs) or a Communications Management Interface (CMI) (for D-series RVUs) STOP command against the object before trying to start it again.

Cause  The 3650/6100 communications subsystem (CSS) or input/output (I/O) process received a status-probe response from the CLIP. The probe indicates that the CLIP is in the boot state instead of in the run state.

Effect  X25 attempts to download the CLIP again. If it cannot download the primary path, X25 attempts to download on another path.

Recovery  Decode the status byte to determine which error occurred. Note the error for your support representative. See Appendix A, for information on the specified error. If the CLIP does not restart automatically, try to restart it manually.

Figure 133-1 Format of CLIP Status Byte for X25 Message 147

Cause  The break-out board (BOB) of the 3650/6100 communications subsystem (CSS) was not properly synchronized with the host. This message normally appears when the BOB is powered on or off, or when processors are switched.

Effect  In most cases, the BOB and the host recover (become synchronized).

Recovery  If the error persists, contact your support representative 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 CLIP did not respond to a periodic I/O-process probe of the CLIP by the 3650/6100 communications subsystem (CSS), and a NO RESPONSE message was received.

Effect  In most cases, the affected I/O process tries to recover.

Recovery  See Appendix B, for information on the specified error. Contact your support representative 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 invalid frame was received. These errors normally occur during a path switch.

Effect  Generally, the system recovers automatically.

Recovery  If this error does not occur during a path switch, contact your support representative 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 communications line interface processor (CLIP) of the 3650/6100 communications subsystem (CSS) hit an unexpected breakpoint.

Effect  The CLIP stops.

Recovery  Contact your support representative 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 communications line interface processor (CLIP) of the 3650/6100 communications subsystem (CSS) received a line configuration different from that in the I/O process.

Effect  The line does not come up.

Recovery  Contact your support representative 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 remote system did not respond to a call request.

Effect  X25 tries to clear the LCN. If X25 cannot clear the LCN, it issues X25 message 116.

Recovery  Try the call request again, and check the LCN assignments.

Cause  The SVC could not be cleared. This message is usually caused by a logical circuit assignment problem. X25 messages 115 and 116 may precede this message.

Effect  The system ignores the LCN.

Recovery  Verify the LCN assignments. If they are correct, check the remote system.

Cause  The PVC could not be reset.

If X25 message 115 precedes this message, there is probably a logical channel number (LCN) assignment problem. If X25 message 115 does not precede this message, the remote system reset the PVC with an out-of-order cause.

Effect  X25 monitors for operational status.

Recovery  Verify the LCN assignments. If the assignments are incorrect, change the assignments; otherwise, check the remote system.

Cause  A problem reported by X25 message 224 or 225 has been solved.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  X25 cannot allocate packet buffers.

Effect  If the error occurs on a virtual call, the call is cleared. If the error occurs on a permanent virtual circuit (PVC), data is lost. In both cases, the line stays up.

Recovery  Recovery is site-dependent and application-dependent. If you want to eliminate the problem, use SYSGEN to configure more EXTENDEDPOOLPAGES.