gtpm5m2o | Messages (Online) |
XID20000I | SDA sda NODE NAME nodename SUCCESSFUL XID COMPLETED |
Where:
Explanation: This is an informational message that indicates the write exchange ID (XID), read XID, channel contact sequence with an adjacent node completed successfully.
System Action: None.
User Response: None.
XID20002I | SDA sda NODE NAME nodename NCP IN SLOWDOWN DURING XID |
Where:
Explanation: Unit exception is received at write exchange ID (XID) completion. This message is sent to the operator.
System Action: None.
User Response: None.
XID20050E | SDA sda NODE NAME nodename XID I-FIELD WITH ERROR INDICATOR RECEIVED |
Where:
Explanation: During exchange ID (XID) processing, an XID was received from an adjacent node with error status set.
System Action: The channel contact sequence is ended.
User Response: None.
XID20051E | SDA sda NODE NAME nodename XID FAILURE SENSE sense RECEIVED |
Where:
Explanation: During exchange ID (XID) processing, sense code of command reject, intervention required, not initialized, abort or data check is received. This message is sent to the operator.
System Action: None.
User Response: None.
XID20055E | SDA sda NODE NAME nodename LOST INTERRUPT TIMEOUT DURING XID |
Where:
Segment Reference: CS01 (CS0H) in CCSNA1 and CSX5
Explanation: This message is sent to the operator when a lost interrupt is detected during exchange ID (XID) processing. Since the node name is not available until XID processing is completed, no node name will be provided in the message.
System Action: None.
User Response: None.
XID20056E | SDA sda NODE NAME nodename INVALID XID EXCHANGE DATA RECEIVED |
Where:
Explanation: An exchange ID (XID) protocol violation occurred.
System Action: XID processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
XID20057E | SDA sda NODE NAME nodename XID REQUEST FOR SDA HAS FAILED |
Where:
Explanation: The exchange ID (XID) request for the symbolic device address (SDA) failed.
System Action: XID processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
XID20058E | NULL XID RECEIVED. ACTIVATE REMOTE LINK STATION. |
Explanation: The local TPF system initiated exchange ID (XID) processing. A null XID input field (I-field) was received by the TPF system This indicates that the remote link station is not active.
System Action: XID processing resumes when the TPF system is notified (through an asynchronous interrupt) that the remote link station is active.
User Response: Activate the remote link station.
XID30060I | SDA-sda ALS-alsname TG-tgn CP-netid.cpname SUCCESSFUL NEGOTIATION PROC XID COMPLETED |
Where:
Explanation: The negotiation proceeding exchange ID (XID) completed successfully.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
XID30061I | SDA-sda ALS-alsname TG-tgn CP-netid.cpname SUCCESSFUL NON-ACTIVATION XID HAS COMPLETED |
Where:
Explanation: The non-activation exchange ID (XID) completed successfully.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
XID30062I | SDA-sda ALS-alsname TG-tgn CP-netid.cpname DISCONTACT COMPLETE |
Where:
Explanation: The disconnect completed successfully.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
XID30070E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname XID I-FIELD WITH CONTROL VECTOR 22 RECEIVED |
Where:
Explanation: An exchange ID (XID) was received from the Network Control Program (NCP) with an error in the input field (I-field).
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
XID30071E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname CONTACT FAILURE |
Where:
Explanation: A contact exchange ID (XID) failed.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
XID30072E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname PRE-NEGOTIATION XID FAILURE cause |
Where:
Explanation: A pre-negotiation exchange ID (XID) failed.
System Action: XID3 exchange processing is ended.
User Response: Review the explanation about the problem specified in the message. Several different problems may have caused this error. A few of these problems follow here:
See TPF ACF/SNA Data Communications Reference for more information.
XID30073E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname NEGOTIATION PROCEEDING XID FAILURE cause |
Where:
Explanation: A negotiation proceeding exchange ID (XID) failed.
System Action: XID3 exchange processing is ended.
User Response: Review the explanation about the problem specified in the message. Several different problems may have caused this error. A few of these problems follow here:
See TPF ACF/SNA Data Communications Reference for more information.
XID30074E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname NON-ACTIVATION XID FAILURE cause |
Where:
Explanation: A non-activation exchange ID (XID) failed.
System Action: The TPF system issues a DISCONTACT and the ALS link is deactivated.
User Response: Review the explanation about the problem specified in the message. Several different problems may have caused this error. A few of these problems follow here:
See TPF ACF/SNA Data Communications Reference for more information.
XID30075E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname LOST INTERRUPT TIMEOUT DURING XID |
Where:
Explanation: A lost interrupt time-out occurred during the exchange ID (XID) operation.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
XID30076E | SDA-sda ALS-alsname TG-tgn CP-netid.cpname XID3 FAILURE SENSE sense RECEIVED |
Where:
Explanation: During exchange ID (XID) processing, sense code of command reject, intervention required, not initialized, abort, or data check is received. This message is sent to the operator.
System Action: None.
User Response: Review the sense data and the channel status word (CSW) to determine the type of error.
See TPF ACF/SNA Data Communications Reference for more information. Also see the appropriate NCP EP reference publications for information about the sense data and the corrective action you should take.
XLMA0099A | LMT FAILURE TO FSC ON lniata -- QUEUE HELD |
Where:
Explanation: The LMT timed out for the device with the LNIATA referenced in the message. The device that timed out is currently defined as a functional support console (FSC).
System Action: No further transmission to the device is attempted by the LMT. The queue is held. All messages subsequently sent to the device are placed on the queue.
User Response: To prevent a build up of messages on the queue, you can enter the ZACRS command to delete the FSC assignments for the device (which will swing the queue to the RO) or assign a new FSC to replace the failing device (which will swing the queue to the new FSC). Enter the ZDCRS CONS command to display the current FSC assignments.
Check the hardware configuration to ensure that the device is operational. If the device is not operational, the number of time out intervals in the XLMT assembly area (XS0AA) record for the device (XS0OTM field) may be too small.
See TPF Database Reference for more information about computer room agent set (CRAS) support.
XXFF0000I | recordnum type RCDS COPIED |
Where:
Explanation: The number of indicated records have been copied to the copy file used by the message switching error correction program.
System Action: None.
User Response: None.