gtpm5m0i | Messages (Online) |
CBOT0001E | UNABLE TO INITIALIZE FILE SYSTEM |
Explanation: File system initialization was not completed successfully because a record code check (RCC) was not received while reading #INODE fixed file record 0. Most likely, the file system is already initialized. If you initialize the file system again, the file system will remove all files and directories.
System Action: File system initialization was rejected.
User Response: None.
See TPF Operations for more information about the ZFINT command.
CBOT0002E | ERROR INITIALIZING FILE SYSTEM |
Explanation: File system initialization was not completed successfully because you entered the ZFINT command after installing both file system support and TPF collection support (TPFCS) on your TPF system. If you are installing both file system support and TPFCS at the same time, you must enter the ZOODB INIT command, which makes it unnecessary for you to enter the ZFINT command.
System Action: The initialization request was rejected.
User Response: See your IBM representative to determine the cause of the error.
See TPF Operations for more information about the ZFINT and ZOODB INIT commands.
CBOT0004I | FILE SYSTEM INITIALIZATION COMPLETE |
Explanation: File system initialization was completed successfully.
System Action: None.
User Response: None.
CBOT0005E | NO INODE OR FLOCK RECORDS AVAILABLE |
Explanation: The file system has been installed, but no #INODE or #FLOCK fixed file records have been allocated.
System Action: None.
User Response: Load a new file address compute program (FACE) table containing the new records.
See TPF System Generation for more information about #INODE and #FLOCK fixed file records.
CBOT0006I | i OF j INODE AND FLOCK RECORDS AND m OF n IZERO RECORDS WILL BE INITIALIZED |
Where:
Explanation: Not all of the requested #INODE and #FLOCK fixed file records were allocated because the ratio of #INODE and #FLOCK fixed file records to the number of #IZERO fixed file records is not correct.
System Action: Some #INODE and #IZERO fixed file records are initialized.
User Response: Do the following:
See TPF Operations for more information about the ZFINT command.
CBOT0007E | FILE SYSTEM NOT INITIALIZED. TOO FEW INODE RECORDS AVAILABLE. |
Explanation: There are not enough #INODE fixed file records (the minimum is 1000) to fit into 1 #IZERO fixed file record.
System Action: The file system is not initialized.
User Response: Load a new file address compute program (FACE) table with at least the minimum of 1000 #INODE and #FLOCK fixed file records.
CBOT0008E | NO IZERO RECORDS AVAILABLE |
Explanation: No #IZERO records were allocated on the TPF system.
System Action: The file system is not initialized.
User Response: Do the following:
CBOT0009I | FILE SYSTEM INITIALIZATION COMPLETED WITH i INODE/FLOCK RECORDS ALLOCATED |
Where:
Explanation: The file system has completed initialization. The number of #INODE and #FLOCK fixed file records indicated in the message are available for use.
System Action: None.
User Response: None.
CBR00001E | MPIF RESTART FAILED -- reason |
Where:
Explanation: The following reason text can be given:
System Action: MPIF restart is ended. TPF system restart is allowed to continue to 1052 state.
User Response: Correct the error condition by entering the appropriate command.
See TPF Operations for more information about the MPIF commands.
CBR00002E | MPIF RESTART ERROR - reason |
Where:
Explanation: The following reason text can be given:
System Action: Multi-Processor Interconnect Facility (MPIF) restart continues with the portion of the initialization that was successful.
User Response: Enter the appropriate command to correct the problem. Changes become effective on the next hardware IPL.
CBR00006A | MPIF RESTART DETECTS BUFFER SIZE MISMATCH. HARD-IPL REQUIRED TO CONTINUE. |
Explanation: Multi-Processor Interconnect Facility (MPIF) buffer pool size is insufficient to satisfy the buffer requirements for the number of defined paths. This error may be caused because of an increase in size of a system work block (SWB) entry. Since storage for MPIF buffers are allocated taking the size of an SWB into account, a prior SWB size (saved in keypoint E) may cause an insufficient amount of storage to be allocated.
System Action: TPF restart is exited.
User Response: Perform a hard initial program load (IPL).
Where:
Explanation: The path definition records (PDRs) or hardware table records (HDWs) were not initialized with the correct record identification.
System Action: Restart is suspended pending an operator response. The System Action for the Explanations discussed with the Explanations.
User Response: Do the following:
Notes:
See TPF Operations for more information about the ZMPIF PDR or ZMPIF HDW command.
CBR10002E | MPIF RESTART FAILED - reason |
Where:
Explanation: The following reason text can be given:
The MPIF data contained in the PDRs must be created by entering the ZMPIF SET and the ZMPIF DEFIND commands.
The MPIF data contained in the HDWs must be created by entering the ZMPIF DEFINE DEVICE command.
System Action: MPIF restart is ended. TPF system restart is allowed to continue to 1052 state.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF PDR or ZMPIF HDW command.
CBR10003I | FILE COPY CONVERSION OF MPIF HARDWARE TABLE RECORDS SUCCESSFUL |
Explanation: Multi-Processor Interconnect Facility (MPIF) restart conversion of the MPIF hardware table records from #CB8HD records to #HDREC records was completed successfully.
System Action: TPF restart continues.
User Response: None.
See TPF Multi-Processor Interconnect Facility Reference for more information about MPIF.
CBR10004I | FILE COPY CONVERSION OF MPIF PATH DEFINITION RECORDS SUCCESSFUL |
Explanation: Multi-Processor Interconnect Facility (MPIF) restart conversion of the MPIF processor unique path definition records from #PDREC records to #PDREU records was completed successfully.
System Action: TPF restart continues.
User Response: None.
See TPF Multi-Processor Interconnect Facility Reference for more information about MPIF.
CBR20002E | FACE ERROR ON PATH DEFINITION RECORD -- ORDINAL 1 -- MPIF RESTART ABORTED |
Explanation: While trying to rebuild data in keypoint E, CBR2 was unable to acquire a valid file address for the path definition record (PDR), ordinal 1. Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next initial program load (IPL) may not be correct.
System Action: MPIF restart is aborted. The TPF system continues to 1052 state.
User Response: Have your system programmer determine the cause of the error and correct it. MPIF data in keypoint E may need to be reinitialized by using MPIF commands. Check the 00156 system error dump for the cause of the error.
The recovery may have been necessary because of:
If corruption is suspected, the cause should be determined.
CBR20003E | FIND ERROR ON PATH DEFINITION RECORD -- F.A. address -- ORDINAL 1 -- MPIF RESTART ABORTED |
Where:
Explanation: While trying to rebuild data in keypoint E, CBR2 was unable to retrieve the Path Definition record (PDR), Ordinal 1. Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next IPL may not be correct.
System Action: MPIF restart is aborted. The TPF system continues to 1052 state.
User Response: Have your system programmer determine the cause of the error and correct it using the system error dump (00156). MPIF data in keypoint E may need to be reinitialized by using MPIF commands.
The recovery may have been necessary because of:
CBR20004E | KEYPOINT CTKE CANNOT BE RETRIEVED - MPIF RESTART ABORTED |
Explanation: While trying to rebuild data in keypoint E, CBR2 was unable to retrieve the Path Definition record (PDR), Ordinal 1. Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next IPL may not be correct.
System Action: MPIF restart is aborted. The TPF system continues to 1052 state.
User Response: Have your system programmer determine the cause of the error and correct it using the system error dump (00156). MPIF data in keypoint E may need to be reinitialized by using MPIF commands.
The recovery may have been necessary because of:
CBR20005E | KEYPOINT CTKE CANNOT BE FILED - MPIF RESTART ABORTED |
Explanation: While trying to rebuild data in keypoint E, CBR2 was unable to file the updated keypoint (error returned from the CYYB segment). Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next initial program load (IPL) may not be correct.
System Action: MPIF restart is aborted. The TPF system continues to 1052 state.
User Response: Have your system programmer determine the cause of the error and correct it using the 00156 system error dump. MPIF data in keypoint E may need to be reinitialized by using MPIF commands.
The recovery may have been necessary because of:
CBR20006A | MPIF DATA IN KEYPOINT E CANNOT BE VALIDATED SPECIFY OPTION: TO REPLACE MPIF DATA IN CTKE -- ENTER: ZMPIF KPE REP IPL TO REBUILD MPIF CONTROL TABLES TO BYPASS THE REPLACE: ZMPIF KPE BYPASS |
Explanation: The Multi-Processor Interconnect Facility (MPIF) data in keypoint CTKE (CK6KE) is earlier than the data contained in path definition record (PDR) ordinal 1, and the slot for this processor ID.
This indicates the following:
System Action: Restart is suspended pending the operator response. The System Action for the Explanation is discussed with the Explanations.
User Response: To replace the MPIF data in CTKE with data in the PDR, respond by entering the ZMPIF KPE REP command. The TPF system then continues through restart to 1052 state but must be re-IPLed to have the new MPIF data in CTKA used to rebuild the MPIF tables.
To continue to 1052 state without replacing CTKE, respond by entering the ZMPIF KPE BYPASS command.
CBT10001I | MPIF PATH STARTUP FAILED -- reason MRBFUNC= function RSDA -- yyyy WSDA -- zzzz |
Where:
Explanation: The following reason text can be given:
System Action: The path is ended with a halt device to the read and write sides of the path.
User Response: Do one of the following:
CBT10002W | MPIF BROADCAST EXCEEDS 4K BLOCK |
Explanation: During cross system startup, the number of Multi-Processor Interconnect Facility (MPIF) users to be sent to another TPF system exceeds the 4K interface requirement to CBB0.
System Action: The first 520 MPIF user names are sent.
User Response: None.
CBT10003I | MPIF PATH path ESTABLISHED TO SYSTEM -- sys CLASS -- cl VIA -- dev RSDA -- sda WSDA -- sda |
Where:
Explanation: The Multi-Processor Interconnect Facility (MPIF) path referenced in the message permits communication with the TPF system named in the message.
System Action: The specified path can now be used for connections. MPIF users waiting for path activation to the TPF system are notified through the MPIFC QUERY user exits.
User Response: None.
CBT10004W | MPIF BROADCAST FAILED TO SYSTEM sys |
Explanation: The update of the broadcast sequence number to TPF system named in the message failed.
System Action: Processing is continued.
User Response: None.
CBT10005E | MPIF STARTUP SEND FAILED ON PATH path RC--retcode |
Where:
Explanation: A MPIFC SEND macro produced a return code of retcode during path startup processing for the path.
System Action: The path is stopped if it is not already stopping.
User Response: Review the console for other error messages associated with the path and take action on these messages.
CBY00040E | MISMATCH BETWEEN THE NUMBER OF CCWAS GENED VIA CTKE AND MPIF HARDWARE DEFINITION RECORD -- MPIF RESTART EXITED |
Explanation: There are not enough CCWA areas allocated by CTIN (based on CTKE) for the number of CTC links defined in Multi-Processor Interconnect Facility (MPIF) Hardware Definition record (HDW), #HDREC.
System Action: MPIF restart exits.
User Response: Have your system programmer resolve any differences between CTKE and the MPIF HDW.
CBY00050E | MPIF HARDWARE DEFINITION RECORD FIND ERROR |
Explanation: The program was not able to obtain a #HDREC record through the FIWHC macro.
System Action: Multi-Processor Interconnect Facility (MPIF) restart exits.
User Response: Have your system programmer determine the cause of the error and correct it.
CBY00060E | MPIF HARDWARE DEFINITION RECORD FACE ERROR. MPIF RESTART EXITED |
Explanation: An error condition was returned from FACS when attempting to access a #HDREC record.
System Action: Multi-Processor Interconnect Facility (MPIF) restart exits.
User Response: Have your system programmer to ensure that the ordinal number and the file address compute program (FACE) ID are correct.
CBY10002W | MPIF DEVICE -- dev -- DISCONNECTED ON RANGE -- sda-sda |
Where:
Explanation: The device name referenced in the message has no prime paths on the range indicated.
System Action: None.
User Response: Attach the range to the TPF system, if needed.
CBY10003I | MPIF DEVICE -- dev -- TURNED OFF FOR RANGE -- sda-sda |
Where:
Explanation: The specified device (dev) is turned off.
System Action: None.
User Response: None.
CBY10004A | INTERCONNECT PRIMING ERROR. NO RANGES PRIMED |
Explanation: No paths were primed using the Multi-Processor Interconnect Facility (MPIF) device.
System Action: None.
User Response: Have system programmer must use the other messages generated by the MPIF restart process to determine the cause of the error and correct it.
CBY10005W | CIOSC MOUNT ERROR -- UNDEFINED SDA(S): sda sda ... |
Where:
Explanation: The symbolic device addresses (SDAs) indicated are not in the IOCP generation.
System Action: None.
User Response: Have your system programmer must add the indicated addresses to the input/output configuration program (IOCP) generation.
CBY10006I | SDA(S) UNAVAILABLE to MPIF: sda sda ... |
Where:
Explanation: The symbolic device addresses (SDAs) referenced in the message were not defined for Multi-Processor Interconnect Facility (MPIF) and SNA channel-to-channel (CTC) support. The TPF system gives SNA precedence when a conflicting definition exists. MPIF does not process any input/output (I/O) operations for these SDAs.
System Action: None.
User Response: None.
CBY10050E | LOST INTERRUPT FOR MPIF I/O DURING PRIMING ON SDA sda |
Where:
Explanation: An interrupt was not received from the indicated symbolic device address (SDA) in a timely manner.
System Action: The future interrupt for this SDA is ignored.
User Response: Check the hardware.
CBY30002W | MPIF MTOM PATH path NOT ESTABLISHED |
Where:
Explanation: The MTOM path name referenced in the message was not made operational because the path destination TPF system name is not the same as the local TPF system name.
System Action: None.
User Response: The path should be displayed and redefined with the correct TPF system name.
CBY30003I | MPIF PATH path ESTABLISHED TO SYSTEM -- sys CLASS -- cl VIA -- MTOM RSDA -- sda WSDA -- sda |
Where:
Explanation: The MTOM path referenced in the message is operational and communication through the path was established. The generic device name, class of path and SDAs are also referenced in the message.
System Action: The specified path can now be used for connections. Multi-Processor Interconnect Facility (MPIF) users waiting for path activation to the TPF system are notified through the MPIFC QUERY user exits.
User Response: None.
CCEB0001E | STATIC CTL BLK CORRUPTED, REFERENCE PRIOR DUMPS |
Explanation: During ISO-C cleanup processing, a field in the static control block was corrupted, which resulted in a system error. After processing the system error, the TPF system returns to ISO-C cleanup processing. To prevent a recurring dump loop, this message is issued and static control block cleanup processing is bypassed.
System Action: The corrupted static control block field is ignored and ISO-C cleanup processing continues.
User Response: Do the following:
CCIM0003I | THE LINK TO CTC NAME ctcname ON CTC SDA sda IS NOW INACTIVE. |
Where:
Explanation: This message indicates that the TPF system received an attention interrupt from the CTC. This can occur when a CTC connection is inactivated by the IBM Virtual Telecommunications Access Method (VTAM) or another TPF system. This is a normal condition during the inactivation.
System Action: The TPF system resets the control blocks associated with the CTC control unit. The control blocks associated with all of the logical units (LUs) that had a session through this CTC are also reset.
User Response: For normal inactivation, no action is necessary. Otherwise, check why the link was inactivated.
CCIM0020A | AN ASYNCHRONOUS INTERRUPT WAS RECEIVED ON 37X5 SDA sda. ISSUE A 'ZNETW ACT' MESSAGE. |
Where:
Explanation: This message may be issued for the following reasons:
System Action: When a device end with unit check is received and the NCP is active, TPF NCP control blocks are reset and all the sessions through the NCP are ended.
User Response: When an asynchronous device end without unit check is received for an inactive NCP, you can enter the ZNETW ACT command to activate the NCP or to begin PU5 communication.
If the NCP is active and this message is received, it indicates an error condition. Correct the error condition and reactivate the TPF-to-NCP connection.
CCIM0071E | AN ERROR OCCURRED DURING I/O OPERATION op ON 37X5 SDA sda. THE CSW IS statusword [AND THE SENSE DATA IS sense]. |
Where:
Explanation: This message occurs for one of the following reasons:
The sense data, if displayed, indicates the type of error. If the sense data is not displayed, the displayed channel status word (CSW) device and subchannel status bytes indicate the type of error.
System Action: The TPF system resets the control blocks associated with the Network Control Program (NCP) to their original state. The control blocks associated with all of the logical units (LUs) that had a session through this NCP are also reset.
User Response: Review the sense data, if present, and the CSW to determine the type of error.
See System/370 Reference Summary for more information.
CCIM0072E | AN ERROR OCCURRED DURING CONTROL OPERATION op ON 37X5 SDA sda. THE CSW IS statusword [AND THE SENSE DATA IS sense]. |
Where:
Explanation: One of the following channel commands received an error during an input/output (I/O) operation with a 37X5 communications controller:
The sense data, if present, indicates the type of error. Otherwise, the channel status word (CSW) device and subchannel status bytes indicate the type of error.
System Action: The TPF system resets all of the control blocks associated with the Network Control Program (NCP) or the emulator program (EP) that is associated with the 37X5 communications controller.
User Response: Review the sense data, if present, and the CSW to determine the type of error.
See System/370 Reference Summary for more information.
CCIM0075E | AN ERROR OCCURRED DURING IPL OPERATION op ON 3705 SDA sda. THE CSW IS statusword [AND THE SENSE DATA IS sense]. |
Where:
Explanation: This message occurs because the IPL operation indicated by the CCW operation code did not complete successfully. The sense data, if displayed, indicates the type of error. If the sense data is not displayed, the displayed channel status word (CSW) device and subchannel status bytes indicate the type of error.
System Action: The TPF system resets the control blocks associated with the Network Control Program (NCP) to their original state. The control blocks associated with all of the logical units (LUs) that had a session through this NCP are also reset.
User Response: Review the sense data, if present, and the CSW to determine the type of error.
See System/370 Reference Summary for more information.
CCIM0076E | TPF CODE REQUESTED INVALID INTERNAL MESSAGE NUMBER nnn DURING OPERATION op ON 37X5/CTC sda. THE CSW IS statusword [AND THE SENSE DATA IS sense]. |
Where:
Explanation: An input/output (I/O) error occurred, and due to a software error, an internal message number that was not valid was requested when a CXFRC was issued from CCSNA1 or CC3705 to CCIM (the 37X5/CTC error message segment).
System Action: The TPF NCP or CTC (or 3705 emulator program (EP)) control blocks are reset along with the control blocks of all the logical units (LUs) that had a session through this NCP or CTC.
User Response: Do one of the following:
See System/370 Reference Summary for more information.
CCIM0077E | A PERMANENT LOST INTERRUPT OCCURRED DURING OPERATION op ON 37X5/CTC sda. |
Where:
Explanation: The TPF system is not communicating with the CTC control unit or the 37X5 communications controller. Possible reasons for the loss of communications in a Network Control Program (NCP) are:
The NCP throws away the data that was sent and waits for the correct read or write start command.
For a CTC, the possible cause might be one of the TPF system on a TPF-to-TPF CTC connection is not up. One of the TPF systems might be issuing a dump or its input list is shut down.
For an NCP, the TPF system issues the CCIM0078W message after the first occurrence of a lost interrupt and then tries the operation again. If the problem occurs again, the CCIM0077E message is issued.
System Action: The TPF system resets the control blocks associated with the CTC or 37X5 communication controller. The control blocks associated with all of the logical units (LUs) that had a session through this NCP or CTC are also reset.
User Response: For an NCP, check the status of the 37X5. If there is no hardware error, have your system programmer determine the cause of the error and correct it.
For a CTC connection, check the status of the connection, as well as the TPF system at the other end. Correct the problem before activating the CTC connection again.
CCIM0078W | A LOST INTERRUPT OCCURRED DURING OPERATION op ON 37X5 sda. THE OPERATION WILL BE TRIED AGAIN. |
Where:
Explanation: The TPF system issues this message when an interrupt is not received within 5 seconds during any attempt to perform an input/output (I/O) operation with a 37X5 communication controller.
System Action: The TPF system tries the operation again. If the lost interrupt condition occurs again, the CCIM0077E message is issued.
User Response: If the CCIM0077E message is issued, refer to its description for the appropriate action. If the CCIM0077E message is not issued, the problem was temporary and can be ignored.
CCIM0079E | INTERRUPT IS LOST DURING OPERATION op ON CTC sda DUE TO UNSUPPORTED COMMAND ON THE OTHER SIDE |
Where:
Explanation: The TPF system did not receive the interrupt from the CTC control unit for the CCW it issued because the other side of the CTC channel adapter has a channel command that is not supported by CTC.
A possible cause is that CTC uses the SDA on one side of the CTC channel adapter in a TPF-to-TPF CTC connection while Multi-Processor Interconnect Facility (MPIF) uses the SDA on the other side. MPIF issues a CTL command of X'07' that completes when the CTC side issues a sense command byte (SCB). The SCB command is chained with read commands. After the CTL command on the MPIF side is completed, no write command issued on the MPIF side satisfies the read command on the CTC side. Therefore, the interrupt for the CTC CCW chain is lost.
System Action: the TPF system resets the control blocks associated with the CTC communication controller. The PSEUDO CCW area used by the CTC CCW chain is cleared. CTC XID processing ends without trying again.
User Response: Check the configuration for the CTC communication controller to make sure that the SDAs on each end of the CTC channel adapter are one of the following:
CCIM0080E | AN ERROR OCCURRED DURING I/O OPERATION op ON CTC SDA sda. THE CSW IS statusword [AND THE SENSE DATA IS sense]. |
Where:
Explanation: This message occurs for one of the following reasons:
The sense data, if displayed, indicates the type of error. If the sense data is not displayed, the displayed channel status word (CSW) device and subchannel status bytes indicate the type of error.
System Action: The TPF system resets the control blocks associated with the CTC to their original state. The control blocks associated with all of the logical units (LUs) that had a session through this CTC are also reset.
User Response: Review the sense data, if present, and the CSW to determine the type of error.
See System/370 Reference Summary for more information. See ESA/390 ESCON Channel-to-Channel Adapter for detailed information and the appropriate action to take.
CCIM0081W | A CHANNEL ERROR OCCURRED DURING OPERATION op ON 37X5 sda. THE CSW IS statusword. THE OPERATION WILL BE TRIED AGAIN. |
Where:
Explanation: This message occurs because a channel hardware error occurred during an input/output (I/O) operation with a 37X5 communications controller. Possible channel errors are:
System Action: The TPF system tries the operation 15 times for a channel-data check, and 3 times for interface-control or channel-control checks.
If the problems persist, the TPF system issues the CCIM0087E message.
User Response: If this error occurs only one time, no action is necessary. However, if the TPF system issues the CCIM0087E message, this indicates a hardware problem. In this case you should see your IBM service representative.
See System/370 Reference Summary to determine the type of channel error from the CSW.
CCIM0083E | A CHANNEL ERROR OCCURRED DURING OPERATION op ON CTC sda THE CSW IS statusword |
Where:
Explanation: This message occurs because a channel program error occurred during an input/output (I/O) operation with a CTC control unit. If the displayed operation is 00, an asynchronous channel error occurred.
Possible software channel program errors are:
Possible channel hardware errors are:
System Action: The TPF system resets the control blocks associated with the CTC control unit. The control blocks associated with all of the logical units (LUs) that had a session through this CTC are also reset.
User Response: For a channel program error, have your system programmer determine the cause of the error and correct it. Have your system programmer display and review the CCWs.
If the error is a channel hardware error, see your IBM service representative.
See System/370 Reference Summary to determine the type of channel error from the CSW.
CCIM0086E | 37X5/CTC SDA sda WAS FOUND INOPERATIVE (CONDITION CODE 03) DURING OPERATION op. INTERVENTION IS REQUIRED. |
Where:
Explanation: A deferred condition code 3 or an immediate condition code 3 occurred during an input/output (I/O) operation with a CTC or 37X5 communications controller. This message indicates a hardware error.
System Action: The TPF system resets the control blocks associated with the CTC or 37X5 communications controller. The control blocks associated with all of the logical units (LUs) in session through this device are also reset.
User Response: Check the status of the device. If the problem cannot be immediately corrected, see your IBM service representative.
When the problem is corrected, bring the device online and reactivate it.
CCIM0087E | AN UNRECOVERABLE ERROR OCCURRED DURING OPERATION op ON 37X5/CTC SDA sda THE CSW IS statusword. INTERVENTION IS REQUIRED. |
Where:
Explanation: For CTC, an unrecoverable error occurred during an input/output (I/O) operation with this CTC device. The CSW device and subchannel status bytes indicate the type of error.
For the Network Control Program (NCP), an unrecoverable error occurred during an I/O operation with a 37X5 device. The channel program was retried several times. Example of unrecoverable errors are channel errors such as:
For CTC or NCP, possible channel hardware errors are:
System Action: For CTC, the TPF system resets the control blocks associated with the CTC, as well as the control blocks associated with the logical units (LUs) that had a session through this CTC.
For NCP, TPF system resets the control blocks associated with the NCP, as well as the control blocks associated with the LUs that had a session through this NCP.
User Response: Review the CSW to determine the type of error. If the error is a channel hardware error, see your IBM service representative.
See System/370 Reference Summary and 370/XA Principles of Operation for more detailed information about the CSW.
CCIM0088W | AUTO NETWORK SHUTDOWN OCCURRED AFTER OPERATION op ON 37X5 SDA sda THE CSW IS statusword [AND THE SENSE DATA IS sense]. |
Where:
Explanation: This message occurs due to one of the following reasons:
System Action: The TPF system resets the control blocks associated with the NCP, as well as the control blocks associated with the logical units (LUs) that had a session through this NCP.
User Response: Review the sense data and the CSW to determine the type of error.
See System/370 Reference Summary for more information about the sense data and the appropriate action to take.
CCIM0089E | THE LINK TO NETID netid ALS NAME alsname ON 37X5 SDA sda IS NOW INACTIVE. |
Where:
Explanation: An ABORT sense was received from the adjacent link station (ALS).
When an ALS is inactivated by IBM Virtual Telecommunications Access Method (VTAM), the TPF system receives a notification from VTAM of UNIT CHECK with ABORT status, which is Sense 01. This is a normal condition during the inactivation.
System Action: The TPF ALS control blocks are reset along with the control blocks of all the logical units (LUs) that had a session through this Network Control Program (NCP).
User Response: For an unexpected inactivation, check the status of the NCP from VTAM. Correct the problem, and then reactivate the TPF-to-NCP connection. However, for normal inactivation of the link, no action is necessary.
See the appropriate IBM Virtual Telecommunications Access Method (VTAM) publications for more information.
CCIM0090E | RESTART SENSE COULD NOT BE INITIATED TO CTC SDA sda DUE TO BUFFER ALLOCATION ERROR |
Where:
Explanation: During SNA restart and after a software IPL, a sense is initiated to each active CTC link to determine whether the link is still active. In order to initiate the sense, a write buffer area and two read buffer areas must be allocated. Insufficient 4K pages were available from the SNA buffer pool for the allocation of all the required 2K buffers.
System Action: The TPF system returns any acquired pages to the SNA buffer pool.
User Response: Check the shortage of 4 K pages in the SNA buffer pool. If necessary, have your system programmer determine the cause of the error and correct it.
CCIM0091W | AUTO NETWORK SHUTDOWN OCCURRED ON SDA sda DUE TO VR BLOCKED TIME-OUT. |
Where:
Explanation: An ANS was issued to the NCP/CTC (ALS) when a VR blocked time-out occurred.
System Action: The TPF system resets the control blocks associated with the NCP/CTC, as well as the control blocks associated with the logical units (LUs) that had a session through this NCP/CTC.
User Response: Check the VR between the TPF system and NCP/CTC as to why the VR block took place and hit the time out.
See TPF ACF/SNA Data Communications Reference for more information about network flow control.
CCIM0092W | AUTO NETWORK SHUTDOWN OCCURRED ON SDA sda DUE TO SLOWDOWN TIME-OUT |
Where:
Explanation: An SNA link was in slowdown for a period of time that exceeded the time-out limit specified by the SLOWTIME parameter in the SNAKEY macro in keypoint record 2 (CTK2).
System Action: The TPF system breaks this link connection.
User Response: Do the following:
See TPF ACF/SNA Data Communications Reference for more information about network flow control.
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
See TPF Operations for more information about the ZNKEY command.
CCIM0093W | AUTO NETWORK SHUTDOWN OCCURRED ON SDA sda DUE TO INPUT LIST SHUTDOWN AND NCP SLOWDOWN |
Where:
Explanation: An NCP/CTC link had a virtual route (VR) block condition and the TPF system was in input list shutdown for a period of time that exceeded the time-out limit specified by the VRILTO parameter for this link.
System Action: The TPF system breaks this NCP or CTC link connection.
User Response: Do the following:
See TPF ACF/SNA Data Communications Reference for more information about network flow control.
See TPF ACF/SNA Network Generation for more information about the OSTG process.