gtpm5m0n | Messages (Online) |
CGTB0001E | LNIATA NOT IN WGTA |
Explanation: The 6-character line number, interchange address, and terminal address (LNIATA) was not found in the WGTA table for the CPU ID specified on the ZDWTG command.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZDWGT command.
CGTB0002I |
Explanation: This is the normal response to the ZDWGT command with the ENTRY parameter specified. This message is followed by a display of information from the WGTA table entry matching the line number, interchange address, and terminal address (LNIATA) and CPU ID specified on the ZDWGT command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDWGT command and for an example of the informational display.
CGTB0003E | PARAMETER INCORRECT |
Explanation: The format of the ZDWGT command is not correct because one of the following errors occurred:
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDWGT command.
CGT00002I | WGTA CORE COPY REUSED |
Explanation: The core copy of the WGTA was valid across the software IPL and was reused.
System Action: None.
User Response: None.
CGT10011I | WGTA TABLES INITIALIZED |
Explanation: The core copy of the WGTA has been rebuilt from the UAT records.
System Action: None.
User Response: None.
CGT10012E | UAT FACE ERROR |
Explanation: This message is followed by the 00047A system error. See Messages (System Error and Offline) for a description of this error.
System Action: None.
User Response: None.
CGT10013E | UAT READ I/O ERROR |
Explanation: A hardware error was found while reading the UAT(UA1UA) records from file.
System Action: WGTA initialization is unable to continue and the restart process is ended.
User Response: Determine whether this is a hardware problem and then correct it.
CGT10014E | UAT RECORD ID/CODE CHECK FAILURE |
Explanation: This message is followed by the 00047A system error. See Messages (System Error and Offline) for a description of this error.
System Action: None.
User Response: None.
CGT10015E | WGTA TABLE TOO SMALL, CHANGE AND REIPL |
Explanation: This message is followed by the 00047A system error. See Messages (System Error and Offline) for a description of this error.
System Action: None.
User Response: None.
CGT10016I | WGTA TABLE INITIALIZATION STARTED |
Explanation: The core copy of the WGTA is being rebuilt from the UAT records.
System Action: None.
User Response: None.
CGT20021I | WGTA RECORDS WRITTEN TO FILE |
Explanation: The main storage copy of the WGTA was written to file.
System Action: None.
User Response: None.
CGT20022E | FACE ERROR ON WGTA RECORD |
Explanation: This message is followed by the 00047A system error. See Messages (System Error and Offline) for a description of this error.
System Action: None.
User Response: None.
CGT20023E | ERROR ON FILING WGTA RECORD |
Explanation: A hardware error was found while writing the WGTA from main storage to file.
System Action: WGTA write processing is ended. The WGTA indicator is set on in keypoint C and system restart is continued.
User Response: Determine whether this is a hardware problem and correct it.
CGT30031I | HASH TABLE DISTRIBUTION |
Explanation: This message is output after WGTA initialization completes.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDWGT command for a full description of this message.
CGT40001E | UNABLE TO PROCESS - KEYPOINT C RETRIEVAL ERROR |
Explanation: An error occurred while retrieving keypoint C.
System Action: None.
User Response: Verify that keypoint C is loaded into the TPF system.
See TPF Operations for more information about the ZDWGT command.
CGT40002E | INVALID NUMERIC FIELD |
Explanation: The parameter specified in the ZDWGT command is not valid.
System Action: None.
User Response: Enter the ZDWGT command again and specify a valid parameter.
See TPF Operations for more information about the ZDWGT command.
CGT40003E | INVALID REQUEST |
Explanation: The parameter specified with the command is not correct.
System Action: None.
User Response: Enter the ZDWGT command again by using the correct format.
See TPF Operations for more information about the ZDWGT command.
CGT40004E | HASH VALUE MUST BE ODD ... RE-ENTER REQUEST |
Explanation: An error was found because the hash value must be ODD.
System Action: None.
User Response: Enter the command again and specify a hash value of ODD.
See TPF Operations for more information about the ZDWGT command.
CGT40005E | WGTA VALUE MUST BE 2 OR MORE |
Explanation: An error occurred because the WGTA value must be two or more and it is not.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDWGT command.
CGT40006E | REQUEST REJECTED -- NOT VALID ON GENERAL FILE |
Explanation: The request is rejected because it is not valid for a general file.
System Action: None.
User Response: None.
See TPF Operations for more information in the ZDWGT command.
CGT40007I | REQUEST COMPLETE |
Explanation: This is the normal response to the ZDWGT command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDWGT command.
CGT40099I | NUMBER OF HASH TABLE ENTRIES mmmmmm NUMBER OF WGTA TABLE ENTRIES nnnnnn |
Where:
Explanation: This is the normal response to the ZDWGT command. This message displays the number of entries in the hash and WGTA tables.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDWGT command.
CGT50052I | RETRIEVAL ERROR ON KEYPOINTED WGTA -- ALL RIDS LOST |
Explanation: During the WGTA build process, the nonzero resource identifier (RID) values are copied from the keypointed old WGTA to the newly-built WGTA. A file address compute program (FACE) or FIND error occurred on a WGTA record, which aborted this RID copy process.
System Action: The following occurs:
User Response: None.
CGT50053W | nnnnnn PSEUDO LNIATA(s) NOT FOUND IN THE WGTA |
Where:
Explanation: During WGTA initialization, when the WGTA slot is retrieved and updated for each pseudo LNIATA found in the RVT, it is detected that some pseudo LNIATAs are not found in the WGTA.
System Action: A SNAPC dump is issued with the 02A system error number. This dump contains a list of the RVT LNIATAs that are not found in the WGTA. Up to 1000 LNIATAs are recorded in the dump. However, the count field in the message may indicate that more mismatches exist.
After the SNAPC is issued, processing is continued.
User Response: Review the system error dump and verify the validity of the pseudo LNIATAs that are flagged.
If they are valid, add them to the UAT and initialize the WGTA again.
If they are not valid, correct the RVT information, run OSTG again, and IPL the TPF system again.
CGT80001I | WGTA RELOADED FROM FILE |
Explanation: The main storage copy of the WGTA was loaded from file.
System Action: None.
User Response: None.
CGT80003E | WGTA READ I/O ERROR |
Explanation: An input/output (I/O) error condition is found while retrieving a WGTA record from file into core.
System Action: The WGTA main storage area is cleared and the restart is continued by initializing the WGTA again from the UAT(UA1UA) records.
User Response: None.
CHEB0001I | ACTIVE CONVERSATIONS -- nnnnnn |
Where:
Explanation: During TPF system restart, this message is displayed to show the number of active conversations in the TPF system.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKB0001I | SCB1 BUILT AND FILED |
Explanation: During a fresh load of the SNA tables, this message is displayed after the session control block part 1 (SCB1) table is built and filed.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKB0002I | SCB2 BUILT AND FILED |
Explanation: During a fresh load of the SNA tables, this message is displayed after the session control block part 2 (SCB2) table is built and filed.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKC0001I | CCB BUILT AND FILED |
Explanation: During a fresh load of the SNA tables, this message is displayed after the conversation control block (CCB) table is built and filed.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKD0001I | CCB CORE COPY REUSED |
Explanation: During a non-fresh load of the SNA tables, the core copy of the conversation control block (CCB) table is valid and will be used again.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKD0002I | CCB RELOADED FROM FILE |
Explanation: During a non-fresh load of the SNA tables, the conversation control block (CCB) table was loaded again from file.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKR0001I | SCB1 CORE COPY REUSED |
Explanation: During a non-fresh load of the SNA tables, the core copy of the session control block part 1 (SCB1) table is valid and will be used again.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKR0002I | SCB1 RELOADED FROM FILE |
Explanation: During a non-fresh load of the SNA tables, the session control block part 1 (SCB1) table was loaded again from file.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKR0003I | SCB2 CORE COPY REUSED |
Explanation: During a non-fresh load of the SNA tables, the core copy of the session control block part 2 (SCB2) table is valid and will be used again.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHKR0004I | SCB2 RELOADED FROM FILE |
Explanation: During a non-fresh load of the SNA tables, the session control block part 2 (SCB2) table was loaded again from file.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHIO0001E |
Explanation: Refer to the CSIO line error messages for any message with a CHIO header.
System Action: None.
User Response: None.
CHKT0001I | TPICB TABLE BUILT |
Explanation: During SNA restart, this message displays when the transaction program instance control block (TPICB) table was built.
System Action: None.
User Response: None.
See TPF ACF/SNA Data Communications Reference for more information.
CHNX0001I | CNOS verb RECEIVED, MODENAME - modename, REMOTE LU - rluname, LOCAL LU - luname, SESSION LIMIT - totsess, MIN CONWINER - yyyyyyy, MIN CONLOSER - xxxxxx |
Where:
Explanation: A change number of sessions (CNOS) INITIALIZE, CHANGE, or RESET request for a logical unit (LU) and mode name pair was received from a remote LU.
System Action: The new session limits are displayed for an initialize or change request. The session limit is set to 0 for a reset request.
User Response: None.
CIJH0001E | CIJH ERROR DURING LOAD -- INSUFFICIENT SPACE IN GL2 |
Explanation: There is insufficient space in GL2.
System Action: The restart procedure is continued.
User Response: None.
CIJH0002E | CIJH ERROR - INSUFFICIENT SLOTS ALLOCATED IN GLOBY |
Explanation: There are insufficient slots allocated in GLOBY.
System Action: The restart procedure is continued.
User Response: None.
CIJH0003E | CIJH ERROR FINDING RECORD WITH PROGRAM NAME progname FILE ADDRESS address |
Where:
Explanation: None.
System Action: The restart procedure is continued.
User Response: None.
CIJH0004I | CIJH LOAD SUCCESSFUL |
Explanation: After the message is issued, control is returned to the TPF system restart program.
System Action: The system action is identical for all errors found during CIJH processing.
User Response: None.
CIJH0005E | CIJH ERROR -- RECORD rrrr HAS AN INVALID LENGTH COUNT |
Where:
Explanation: None.
System Action: The restart procedure is continues.
User Response: None.
CIJS0001I | CCP TRACE STARTED |
Explanation: This message is used when the input command was accepted without error.
System Action: None.
User Response: None.
See TPF Non-SNA Data Communications Reference for more information about the communications control program trace (CCTRUG).
CIJS0002E | INVALID SYMBOLIC LINE NUMBER -- CCP TRACE NOT STARTED |
Explanation: The input command was rejected because of a symbolic line number that is not valid or a symbolic line number range that is not valid for the line type specified.
System Action: None.
User Response: None.
See TPF Non-SNA Data Communications Reference for more information about the communications control program trace (CCTRUG).
CIJS0003I | CCP TRACE STOPPED |
Explanation: The input ZLTRF command was accepted and the communications control program (CCP) was deactivated successfully.
System Action: None.
User Response: None.
See TPF Non-SNA Data Communications Reference for more information about the communications control program trace (CCTRUG). See TPF Operations for more information about the ZLTRF command.
CIJS0004E | ZLTRF REJECTED -- CCP TRACE NOT ACTIVE |
Explanation: The input ZLTRF command was rejected because the communications control program (CCP) was not active.
System Action: None.
User Response: None.
See TPF Non-SNA Data Communications Reference for more information about the communications control program trace (CCTRUG). See TPF Operations for more information about the ZLTRF command.
CIJS0005E | INVALID OPTION -- xxx NOT ON LINE 00 OR 01 |
Where:
Explanation: The PRC option was specified when the PRC was not on line 01 or the RO option was specified when the RO was not on line 00 or 01.
System Action: The communications control program (CCP) trace is not started.
User Response: None.
See TPF Non-SNA Data Communications Reference for more information about the communications control program trace (CCTRUG).
CILC0101E | UNABLE TO INITIALIZE MASTER XPRG RECORD |
Explanation: A detailed message of why the master XPRG was unable to be initialized precedes this message.
System Action: The load ends abnormally.
User Response: Do the following:
CILC0119W | UNABLE TO INITIALIZE MASTER APRG RECORD |
Explanation: A detailed message of why the master APRG record was unable to be initialized precedes this message.
System Action: The online loader load function ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CILD0104E | LIBRARY cccc CANNOT BE LOADED TO NON-BSS SUBSYSTEM. |
Where:
Explanation: There was a request to load library cccc to a non-BSS subsystem. Libraries are only allowed in the BSS subsystem.
System Action: The library specified in the message was not loaded.
User Response: Load the library in the BSS subsystem.
CILD0105E | UNABLE TO DETERMINE CURRENT PROGRAM TYPE FOR PROGRAM cccc - PROGRAM NOT LOADED |
Where:
Explanation: An error occurred while obtaining the #PVR records to determine the program type of the existing version of the C load module.
System Action: The load ends abnormally.
User Response: See the preceding message for details about the cause of the problem.
CILD0106E | UNABLE TO FIND PROGRAM cccc ONLINE |
Where:
Explanation: Unable to find the existing copy of the #PROGn record for the program being loaded.
System Action: The program will not be loaded. The load continues.
User Response: Verify that the program is allocated.
CILE0102E | NO MORE EXTRA PROGRAM RECORDS AVAILABLE |
Explanation: There are no more extra program records #XPRGn available in the TPF system.
System Action: The load continues.
User Response: Do one of the following:
CILE0103W | THE NUMBER OF EXTRA PROGRAM RECORDS AVAILABLE IS nnnn AND BELOW THE THRESHOLD VALUE OF nnnn |
Where:
Explanation: The number of available extra program records (#XPRGn) is now below the threshold value.
System Action: The auxiliary loader load function or E-type loader accept function continues.
User Response: Do one of the following:
CILE0115W | NUMBER OF ADATA RECORDS AVAILABLE IS recnum AND BELOW THE THRESHOLD VALUE OF threshold |
Where:
Explanation: The number of available #APRGn records has fallen below the threshold value.
System Action: The load process continues. ADATA files will continue to be loaded until there are not enough files available to load a single ADATA file. At that time, message LDRM0114W will be displayed.
User Response: If necessary, allocate additional #APRGn records.
See TPF System Installation Support Reference for more information about the online loader functions. See TPF System Generation for more information about changing record allocations.
CILF0107E | UNABLE TO FIND TEXT/ACRL RECORD FOR MODULE cccc ONLINE |
Where:
Explanation: Either the online auxiliary loader or the E-type loader accept function was unable to find a text or ADCON relocation record (ACRL) for the specified program module. A detailed message of why the loader was unable to find this record precedes this message.
System Action: The online auxiliary loader load function or E-type loader accept function ends abnormally. If the E-type loader accept function was processing, the E-type loader policing routine tries again to accept the loadset.
User Response: See the preceding message for more information.
CILF0108E | UNABLE TO FIND ORDINAL RECORD FOR MODULE cccc ONLINE |
Where:
Explanation: The online auxiliary loader or the E-type loader accept function issued a find of the ordinal record for the program module specified in the message but was unable to do the find.
System Action: The online auxiliary loader load function or E-type loader accept function ends abnormally. If the E-type loader accept function was processing, the E-type loader policing routine tries again to accept the loadset.
User Response: See the previous message for details about why the loader was unable to do the find.
CILF0109W | MODULE cccc IS SKIPPED |
Where:
Explanation: The online loader tried to obtain a new record for the requested module, but failed.
System Action: The load of this module is skipped. The load process continues.
User Response: See the preceding message for more information.
CILF0110E | UNABLE TO UPDATE PRIMARY ORDINAL RECORD FOR MODULE cccc |
Where:
Explanation: The total number of ordinals required for this program needs to change because of one of the following:
However, the loader was unable to update the primary ordinal with the correct number.
System Action: The online auxiliary load or E-type loader accept function ends abnormally. If the E-type loader accept function was processing, the E-type loader policing routine tries again to accept the loadset.
User Response: Do the following:
CILF0111E | REQUEST ABORTED - INVALID RECORD ID xx FOUND IN INPUT FILE |
Where:
Explanation: While processing an E-type program or program load module, an unexpected record was read from the input medium.
System Action: The TPF system ends the online loader load function.
User Response: Do the following:
CILF0112E | ERROR READING FROM DDNAME xxxxxxxxxxxxxxxx |
Where:
Explanation: The record read from the specified DDNAME was not in the expected format. The TPF system expected one of the program records.
System Action: The TPF system ends the online loader load function.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the online loader functions and the offline job routine.
CILG0111E | REQUEST ABORTED - INVALID RECORD ID xx FOUND IN INPUT FILE |
Where:
Explanation: While processing an E-type program or program load module, an unexpected record was read from the input medium.
System Action: The online loader load function ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the online and offline loader functions.
CILG0112E | ERROR READING FROM DDNAME input |
Where:
Explanation: The record that was read from the specified data definition name was not in the expected format. The TPF system expected one of the program records.
System Action: The online loader load function ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the online and offline loader functions.
CILH0111E | REQUEST ABORTED - INVALID RECORD ID xx FOUND IN DDNAME xxxxxxxxxxxxxxxx |
Where:
Explanation: While processing an E-type program or program load module, an unexpected record was read from the input medium.
System Action: The TPF system ends the online loader load function.
User Response: Do the following:
CILH0112E | ERROR READING FROM DDNAME xxxxxxxxxxxxxxxx |
Where:
Explanation: The record read from the specified DDNAME was not in the expected format. The TPF system was expecting one of the program records.
System Action: The TPF system ends the online loader load function.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the online loader functions and the offline job routine.
CILO0113E | UNABLE TO FIND ADATA ORDINAL RECORD FOR MODULE nnnn ONLINE |
Where:
Explanation: An error occurred while trying to read an existing ADATA file for the specified program.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CILO0114W | NO MORE ADATA RECORDS AVAILABLE - ADATA FILES WILL NOT BE LOADED FOR ALL PROGRAMS |
Explanation: The loader attempted to load one or more ADATA files for a real-time program and determined that there were not enough #APRGn records available.
System Action: The load process continues; however, the loader does not attempt to load ADATA files for any real-time programs after the error occurred.
User Response: To load real-time programs with ADATA files after this error occurs, do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions. See TPF System Generation for more information about changing record allocations.
CILO0117W | ERROR READING BASE ADATA RECORD FOR PROGRAM nnnn - ADATA NOT LOADED |
Where:
Explanation: The loader attempted to load a real-time program with an ADATA file, but an error occurred while trying to read an existing ADATA record for the specified program.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CILO0118W | UNABLE TO UPDATE PRIMARY ADATA ORDINAL RECORD FOR MODULE nnnn |
Where:
Explanation: The loader attempted to load a real-time program with an ADATA file, but an error occurred while trying to write to the ADATA ordinal record for the specified program.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CILO0120E | UNABLE TO FIND ADATA RECORD FOR MODULE nnnn ONLINE |
Where:
Explanation: An error occurred while trying to find an #APRGn record that is needed to write the ADATA file for the program being loaded.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CILX0116W | ERROR READING PVR RECORD FOR PROGRAM nnnn - ADATA NOT LOADED |
Where:
Explanation: The loader attempted to load a real-time program with an ADATA file, but an error occurred while trying to read the #PVRn record containing the program version record (PVR) entry for the specified program.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Determine the cause of the error by examining the #PVRn records.
See TPF System Installation Support Reference for more information about the online loader functions.
CILX0117W | ERROR READING BASE ADATA RECORD FOR PROGRAM nnnn - ADATA NOT LOADED |
Where:
Explanation: The loader attempted to load a real-time program with an ADATA file, but an error occurred while trying to read an existing ADATA record for the specified program.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CIL60111E | REQUEST ABORTED - INVALID RECORD ID xx FOUND IN DDNAME xxxxxxxxxxxxxxxx |
Where:
Explanation: While processing an E-type program or program load module, an unexpected record was read from the input medium.
System Action: The TPF system ends the online loader load function.
User Response: Do the following:
CIL60121W | UNABLE TO UPDATE PVR RECORD FOR PROGRAM nnnn - ADATA MAY NOT BE USABLE |
Where:
Explanation: An error occurred while trying to update the program version record (PVR) entry in the #PVRn record, which indicates whether an ADATA file was loaded for the specified program.
System Action: The load process continues; however, the ADATA file for the specified program will not be loaded.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the online loader functions.
CINP0001E |
Explanation: Refer to the CSIO line error messages for any message with a CINP header.
System Action: None.
User Response: None.
CJ040001I | TO2 RESTARTED |
Explanation: This is the normal response during a TPF system IPL when TPF collection support has been initialized.
System Action: None.
User Response: None.
CJ040002I | TO2 NOT INITIALIZED, TO2 RESTART BYPASSED |
Explanation: TPF collection support was not restarted during a TPF system IPL because it was never initialized.
System Action: TPF collection support restart is bypassed and the TPFCS database remains unavailable.
User Response: Enter the ZOODB INIT command to access the TPFCS database.
CJ040003I | TO2 CYCLED UP |
Explanation: This is the normal response during a system cycle up to NORM state from TPF collection support (TPFCS).
System Action: None.
User Response: None.
CJ040004I | TO2 NOT INITIALIZED, TO2 CYCLE BYPASSED |
Explanation: TPF collection support (TPFCS) could not be cycled because it has not been initialized or the TPFCS anchor and shadow records have been corrupted.
System Action: TPFCS cycle processing is bypassed. TPFCS remains unavailable for application use.
User Response: Do one of the following:
CJ040005I | TO2 CYCLED DOWN |
Explanation: This is the normal response during a system cycle down from NORM state from TPF collection support (TPFCS).
System Action: None.
User Response: None.
CJ040051E | ERROR ON TO2 RESTART |
Explanation: TPF collection support could not be initialized during a TPF systemIPL because an internal logic error occurred.
System Action: TPF collection support initialization is not completed successfully and the TPFCS database remains unavailable.
User Response: See your IBM service representative.
CJ040052E | ERROR ON TO2 CYCLE UP |
Explanation: TPF collection support (TPFCS) was not cycled because of an internal error.
System Action: TPFCS cycle processing ends. TPFCS is available for application use.
User Response: See your IBM service representative.
CJ040099E | TO2 INTERNAL ERROR, ERROR CODE errcode errtext |
Where:
Explanation: An internal error occurred during a TPF system IPL.
System Action: TPF collection support initialization is not completed successfully and the TPFCS database remains unavailable.
User Response: See your IBM service representative.
CJ160001E | TO2 FUNCTIONAL MESSAGE IS NOT VALID |
Explanation: A ZRECP TO2 command was entered with an incorrect parameter or incorrect syntax.
System Action: The command is rejected.
User Response: Do the following:
CJIW0002I | I/O COMPLETION FOR xxxx IS LATE, NO RECOVERY REQUESTED. |
Where:
Explanation: The input/output (I/O) request was not completed within a fixed time period. The I/O is allowed to continue with the time period reset. The current fixed period of time is 5 seconds.
System Action: None.
User Response: None.
CJIW0003I | DEVICE RESET AND QUEUE RESTARTED AFTER TIME OUT FOR xxxx |
Where:
Explanation: The input/output (I/O) request was not completed within a fixed amount of time.
System Action: The I/O request is halted and restarted with a new time period.
User Response: None.
CJIW0006W | CHPID id REMOVED FROM DEVICE ccud DUE TO PERMANENT ERROR |
Where:
Explanation: The channel path indicated in the message is receiving device errors that do not occur on the device's other paths.
System Action: The channel path is removed from the path mask associated with the device and is no longer used for input/output (I/O) operations to the device.
User Response: This is a hardware error. See your IBM service representative.
CJIW0007W | CHPID id REMOVED FROM DEVICE ccud PATH INOPERATIVE |
Where:
Explanation: The channel path indicated in the message was found to be inoperative when accessed.
System Action: The channel path is removed from the path mask associated with the device and is no longer used for input/output (I/O) operations to the device.
User Response: This is probably an interface switch that was not turned on. Otherwise this is considered a hardware error. See your IBM service representative.
CJIW0008W | CHPID id REMOVED FROM DEVICE ccud CC-3 ON PATH |
Where:
Explanation: The channel path indicated in the message returned a CC-3 when the TPF system attempted to use it to access the device.
System Action: The channel path is removed from the path mask associated with the device and is no longer used for input/output (I/O) operations to the device.
User Response: This is probably an interface switch that was not turned on. Otherwise this is considered a hardware error. See your IBM service representative.