gtpm4m0i | Messages (System Error and Offline) |
Program: CSYN
Explanation: The ECB had an I/O pending when a SYNCC macro was issued.
System Action: The ECB is exited unless the ERRTN option was coded on the SYNCC macro.
User Response: Make sure that all I/Os are completed before issuing a SYNCC macro.
Program: CSYN
Explanation: The ECB tried to lock at a synchronizable global when it was already holding a record.
System Action: The ECB exited unless the the ERRTN option was coded on the SYNCC macro.
User Response: An ECB cannot hold a record at the time a SYNCC macro with the LOCK option specified is processed.
Program: CSYN
Explanation: The following error conditions may have occurred:
System Action: In all cases, the ECB is exited unless the ERRTN option was coded in the SYNCC macro.
User Response: Do one of the following (these actions correspond to the previous explanations):
Program: CSYN
Explanation: There was FIND error while trying to find the file copy for the synchronizable global.
System Action: The subsystem is cycled to the 1052 state and the ECB is exited.
User Response: Ensure that the record ID on the record is correct.
Program: CSYN, CPNU
Explanation: One or more I-streams did not complete the synchronization process within the allowed 15 seconds.
System Action: The system issues the 6A4 dump and initiates an IPL.
User Response: Check for a problem in the load of the active I-streams. Deadlock, overload, and so on are possible reasons for an I-stream not completing the synchronization in the allowable time.
Program: CSYN
Explanation: Subsystem user ID in SGFR and SIGT do not match.
System Action: ECB is exited unless the ERRTN option is coded on the SYNCC macro.
User Response: Verify that the correct SSU SIGT item and SGFR were used. If so, then correct whichever one is not correct.
Program: CSYN
Explanation: The ECB tried to unlock a global it did not have.
System Action: The ECB is exited unless the ERRTN option was coded on the SYNCC macro.
User Response: Verify that the synchronizable global being locked is the same as the one being unlocked or synchronized.
Program: CSYN
Explanation: The ECB tried to unlock a global when it did not have a global locked.
System Action: The ECB is exited unless the ERRTN option on the SYNCC macro was coded.
User Response: Verify that a SYNCC LOCK is done before a SYNCC UNLOCK or SYNC is issued.
Program: CSYN
Explanation: There was a FILE error when filing the synchronizable global record.
System Action: The subsystem is cycled to 1052 state and the ECB is exited.
User Response: Do the following:
Program: CSYN
Explanation: The following error conditions may have occurred:
The dump produced by this error includes the entire SIGT for the associated subsystem, printed as a User Specified Area. In addition, R0 contains a value that further clarifies the cause of the error. The values contained in R0 and their meanings are as follows:
System Action: The subsystem is cycled to 1052 state and the ECB is exited.
User Response: IPL the system at a convenient time.
Program: CNPU
Error Message: INVALID SSU ID INPUT TO SIPCC
Explanation: The SSU Name Input in the SIPCC item was not found in the subsystem users table or it does not match the SSU two-character ID (SSU ID) also passed in the SIPCC input.
System Action: The SERRC macro is issued with the exit option.
User Response: The problem is likely caused by corruption of SIPCC data. If the SSU name and ID passed by SIPCC are valid and correspond, the SIGT table was incorrectly generated by CNPR for this SS. Check the SSU names, user-defined to the system initialization program (SIP) (through GLSYNC) for creating the SIGT table.
Program: CNPU
Error Message: INVALID GLOBAL SYNC REQUEST
Explanation: The SIPCC time requested update of a Global field (or record) but this SS has no synchronizable Global fields (or records) defined.
System Action: A system error is issued and is exited.
User Response: The SS processing the global synchronization request initiated by the SIPCC item has no fields/records defined in the SIGT table. Ensure that user correctly coded the GLSYNC macro to the system initialization program (SIP) for all synchronized global fields/records.
Program: CNPU
Error Message: GLOBAL INDEX OUT OF RANGE
Explanation: The Global Index for the SIPCC item is out of range.
System Action: A system error is issued and exited.
User Response: This error should not occur. It is a symptom of incompatibility with the SYNLST macro and the SIGT table used for global synchronization. Ensure that the SYNLST contains the global records-fields, user-defined by the system initialization program (SIP) GLSYNC macro, and contained in the SIGT table.
Program: CNPS
Error Message: INVALID SI1GT ENTRY ENCOUNTERED - CHECK OFFLINE SIGT
Explanation: The entry in the SI1GT table has a displacement value of 0, which is not valid.
System Action: A system error is issued and the entry control block (ECB) exits.
User Response: Verify that the SIGT table was built properly by the offline process.
Program: CNPR/GOGO
Error Message: ERROR PROCESSING SIGT IN BSS -- RESTART TERMINATED
Error Message: ERROR IN BSS GLOBAL LOAD -- RESTART TERMINATED
Explanation: This error is issued when an error occurred during BSS global processing that caused the BSS to go dormant. This may have happened during Global Loading (GOGO) or during SIGT building (CNPR).
System Action: The 0006AF system error is issued and restart processing is exited.
User Response: Check the previous console error messages that indicate which type of error occurred in BSS global processing. This message should never be issued by itself.
Program: CMV0
Error Message: ERROR ON ENQUEUE OF SESSION PACING QUEUE
Explanation: This message occurs when the Queue Manager (CMX0) indicates there was an error during the enqueue of a message on the session pacing queue.
System Action: The entry control block (ECB) exits. If there is an I/O error, the queue is purged.
User Response: Review the system error dump to determine why the enqueue failed.
Program: CMV0
Error Message: ERROR ON GET MESSAGE FROM SESSION PACING QUEUE
Explanation: This message occurs when the Queue Manager (CMX0) indicates there was an error during a get of a message from the session pacing queue.
System Action: The entry control block (ECB) exits and the queue is purged.
User Response: Review the system error dump to determine why the get failed.
Program: CMW3
Error Message: LU62 -- FIND ERROR ON SCB PIU QUEUE
Explanation: An error occurred during an attempt to find (FINWC) a record on the OMT queue for this SCB.
System Action: The entire queue is purged.
User Response: Review the system error dump to determine the cause of the error and to correct it. Ensure that the queue pointers in the session control block (SCB) are not corrupted.
Program: Displayed on the console and in the dump.
Error Message: ERR -- SENDT Q INFO RCD INIT
Explanation: The program found an error return from the file address compute program (FACE) or retrieval error while attempting to initialize SENDT queue information records.
System Action: A system error is issued with the explanatory message appended. The program continues the initialization process for all allocate SENDT Q information records.
User Response: Review the system error dump to determine the cause of the error and to correct it. FACE must be able to return the correct file address. Inspection of detail and gross error indications will determine the reason for retrieval failure.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO Q SENDT MESSAGE
Explanation: This error occurs when the system is unable to retrieve fixed-file SENDT Q information records or the large long term pool records referenced within the fixed-file Q information record.
System Action: A system error is issued with the explanatory appended message. If the error is on the fixed-file record segment, XHA3 exits and the SENDT message is lost.
If the error occurred on the pool record segment, XHA3 tries to save as much of the file address chain as possible. Some SENDT traffic may be lost, and the current message is queued.
User Response: The detail and gross error indicators will determine the reason for the retrieval error.
Program: Displayed on the console and in the dump.
Error Message: ERR -- SENDT DEQUEUE PROCESS
Explanation: The system is unable to dequeue SENDT messages due to retrieval errors on the fixed-file SENDT queue information record or the large long term pool records referenced within the fixed-file Q information record or the SENDT message itself.
System Action: A system error is issued with the explanatory appended message and the SENDT traffic dequeue process continues until all retrievable messages are dequeued. Traffic queued to any record that could not be retrieved is lost.
User Response: The detail and gross error indicators will determine the reason for the retrieval error.
Program: Displayed on the console and in the dump.
Error Message: SENSE COMMAND YIELDS IMPROPER PATHID ON CU xxxx
Explanation: This message is from the CLMF segment.
A Sense command chained from a Read Locks command obtained a sense byte containing the path ID over which the locks were read. The path ID is not equal to the expected path ID as shown in the header of the processor table.
System Action: A SERRC macro is issued with the R option, which specifies a return to the next sequential instruction (NSI).
User Response: Determine why the path IDs differ. Check that the path ID in the processor table is set correctly. The ECB work area contains the expected and the actual path IDs. The header of the processor table contains the expected path ID, which the program moved to its ECB work area.
Program: CLMF, CLM3
Error Message: READ LOCK ERROR DURING LOCK MANAGEMENT ON CU xxxx
Explanation: I/O errors were discovered by the program following an FDCTC macro to read the locks.
System Action: Issue the SERRC macro with the C or R option.
User Response: Try to find out the type of error. The dump contains diagnostic information in symbolic location CE1SUx of the ECB work area.
Program: CLMF, CLM3
Error Message: UNLOCK ERROR DURING LOCK MANAGEMENT on CU xxxx
Explanation: I/O errors were discovered by the program following an FDCTC macro to Unlock the locks. At least one CCW in the chain of unlock CCWs failed.
System Action: The TPF system issues the SERRC macro with the E option.
User Response: Try to find out the type of error. The dump contains diagnostic information in symbolic location CE1SUx of the ECB work area.
Program: Displayed on the console and in the dump.
Error Message: MOVELOCK LOGIC ERROR, UNEXPECTED RESPONSE
Explanation: A response was received from another processor in a loosely coupled complex but the action that caused the response from that processor was not received by this processor, for example, a movelock request was lost.
System Action: A catastrophic system error is issued, and the TPF system is re-IPLed because the database configuration may have changed.
User Response: Determine whether a movelock request should have been received and if yes, determine what occurred to prevent the request from being received by this processor.
Program: Displayed on the console and in the dump.
Error Message: MOVELOCK TIMEOUT, MISSING RESPONSE
Explanation: The movelock function moved the locks from one control unit to another and was waiting for the other processors in a complex to do the same and respond. At least one other processor did not send a response acknowledging completion of its lock movement.
System Action: The SERRC macro is issued, which resulted in a catastrophic system error with this message.
User Response: Determine why the response was not received. The CBRW for level 0, byte 1 will have the mask for the missing processors.
Program: CPAC
Error Message: KEYPOINT 0 READ ERROR
Explanation: Because of a request to mount a module, the system attempted to initialize the control unit. For some reason the initialization routine was unable to read keypoint 0.
System Action: The system issues a SERRC macro resulting in dump with this message and the ECB is exited.
User Response: Determine why the system was unable to read keypoint 0.
Program: CBPK
Error Message: INVALID BPKD PARAMETER LIST PASSED ON CALL
Explanation: The BPKD pointed to on the call does not contain a correct format.
System Action: None.
User Response: None.
Error Message: TEXT COUNT ZERO AND NO EOM FOUND
Explanation: CBPK scanned all the input characters but did not find the end-of-message complete (EOM) character that signifies the end of the message data.
System Action: None.
User Response: None.
Error Message: LOGIC ERROR, TEXT POINTER NOT POINTING AT KEYWORD
Explanation: CBPK was processing a keyword but when the character scan was resumed it was not pointing to a keyword identifier.
System Action: The ECB is exited.
User Response: Your system programmer should try to determine why the error occurred by using the associated dump. Then, correct the error.
Program: CPAF
Error Message: DASD MOUNT/DISMOUNT LOGIC ERROR. DEVICE IS NOT A VALID DASD MOUNTED TO CIO.
Explanation: An illogical condition occurred during DASD mount/dismount processing. DASD mount/dismount processing should not be in the CPAF segment when the device is not a valid DASD mounted in CIO.
System Action: Return to the next sequential instruction in the CPAF segment.
User Response: Your system programmer should determine why the error occurred by using the associated dump. Then, correct the error.
Program: CLHV, CCSTOR
Error Message: DOUBLE RELEASE OF STORAGE BLOCK
Explanation: A user tried to release a storage block that is not in use.
System Action: The storage block is not returned to the list. A SERRC macro is issued with an exit.
User Response: None.
Program: CLHV, CCSTOR
Error Message: INVALID STORAGE BLOCK ADDRESS
Explanation: A user tried to release a storage block whose address does not fall within the valid range of storage block addresses or does not fall on a block boundary.
If the appended message indicates that this error came from the $RSWBC or $RCOMC macros, R1 will contain the block address that is not valid. Otherwise, R1 points to the frame control table entry for the block address that is not valid. R3 contains an index to the slot table (see IDSFCT for details) and can be used to get the ECB virtual address (EVA) of the block. Otherwise, R0 contains the block address.
System Action: The storage block is not returned to the list. A SERRC macro is issued with an exit.
User Response: None.
Program: CLHV, CCSTOR
Error Message: GNAVC -- PRIVATE AREA STORAGE EXHAUSTED
Explanation: A user tried to get a storage block when no virtual addresses are available in the private area of the ECB virtual memory (EVM).
System Action: The entry is exited and error recovery is initiated.
User Response: Check the failing ECB to determine whether the application program is using blocks in an efficient manner.
Program: CLHV, CCSTOR
Error Message: GNAVC -- CANNOT USE REQUIRED EVM ADDRESS
Explanation: The ECB virtual address (EVA) pointer to the next available virtual address, which is located in the ECB, does not contain a valid ECB virtual memory (EVM) address.
System Action: The entry is exited and error recovery is initiated.
User Response: Check the failing ECB to determine whether corruption caused the address to no longer be valid. Do not access or update the next available virtual address pointer in the ECB.
Program: CLHL, CCCLHR
Error Message: POST INTERRUPT ADDRESS IS ZERO
Explanation: A $CRISC, $ADPC, ADDLC, or ADDFC was issued with a post interrupt address of zero.
System Action: If the error is determined during the processing of an ADDLC or ADDFC SVC call, the entry exits and error recovery is initiated.
In all other cases, a catastrophic error recovery is initiated with no associated ECB.
User Response: Ensure that the previously mentioned macros are called with a valid post interrupt address in the specified register (which is the new format) or at a displacement of 6 bytes into the block specified by the BLOCK parameter (which is the old format).
Program: Displayed on the console and in the dump.
Error Message: ADSPACE MASK SPECIFIED IS INVALID
Explanation: The ADSPACE parameter on the $SWSPC call indicates that a register contains the address space mask and this mask is not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: Ensure that the ADSPACE register contains a valid mask that can be X'00' (which indicates EVM) or X'03' (which indicates SVM).
Program: Displayed on the console and in the dump.
Error Message: $GIOBC -- NO AVAILABLE IOBS
Explanation: There are no input/output blocks (IOBs) available in the system.
System Action: Catastrophic system error recovery is initiated with no associated ECB.
User Response: None.
Program: CLHV, CCSTOR; $RMNBC processing
Error Message: RMNBC -- INVALID INPUT PARAMETERS
Explanation: The input values for either the base address or the number of pages is not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: Ensure that the parameters used for the $RMNBC call are consistent with the returned values from a prior $GMNBC call.
Program: CICS, CCNUCL; ADDLC or ADDFC processing
Error Message: INVALID LIST TYPE SPECIFIED
Explanation: The list type equate found in the LIST parameter for an ADDLC or ADDFC macro call is not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: Ensure that the LIST parameter for an ADDLC or ADDFC macro call is valid. The valid equates are:
#CLHCRS is not a valid equate for ADDLC or ADDFC macro calls.
Program: CCSONP (member GRFS), GETFC processing, CCNUCL (member CICR) GETCC processing.
Error Message: None.
Explanation: A GETFC or GETCC macro is issued with a record ID that does not exist in the record identifier attribute table (RIAT); or a GETFC/GETCC macro is issued with a record ID for which the specified record attributes cannot be found.
System Action: If the GETFC macro was issued, the system action depends on how the ERROR parameter was specified:
User Response: None.
Program: CCSONP (member GRFS), GETFC processing.
Error Message: None.
Explanation: A GETFC macro was issued for an entry control block (ECB) data level or data event control block (DECB) that is already holding a block.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CCSONP (member GRFS), GETFC processing.
Error Message: None.
Explanation: A GETFC macro was issued with a record ID that has record identifier attribute table (RIAT) attributes that are not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CICR/CCNUCL, GETCC processing.
Error Message: GETCC -- INVALID BLOCK TYPE
Explanation: A GETCC macro is issued with a block type that is not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: Code the GETCC macro with a valid block type as defined in CLHEQ.
Program: CICR, CCNUCL; GETCC processing.
Error Message: GETCC -- BLOCK SIZE REQUESTED TOO LARGE
Explanation: A GETCC macro is issued using the size option and no block type is large enough to satisfy the request.
System Action: The entry is exited and error recovery is initiated.
User Response: Code the macro by using a size value that is 4095 or less.
Program: CICR, CCNUCL; GETCC processing
Error Message: GETCC -- INVALID FORMAT DESCRIPTOR INDEX
Explanation: A GETCC macro expansion was issued with a format that is not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: Correct the offending segment so that it uses a valid format for the GETCC macro call.
Program: CICR, CCNUCL; GETCC processing.
Error Message: GETCC -- BLOCK ALREADY HELD
Explanation: A GETCC macro is issued for an entry control block (ECB) data level or data event control block (DECB) that is already holding a block.
System Action: The entry is exited and error recovery is initiated.
User Response: Ensure that the desired data level or DECB is free before you issue the GETCC macro.
Program: CLHL/CCCLHR, $ADPC processing.
Error Message: $ADPC -- INVALID CPU LIST PARAMETER
Explanation: An $ADPC macro is issued requesting a CPU list other than #CLHRDY, #CLHINP, or #CLHDEF.
System Action: Catastrophic error recovery is initiated.
User Response: Examine the dump to determine why an incorrect CPU list parameter was passed to the $ADPC macro. At the time of the dump R2 contains the incorrect CPU list value and R14 points to the $ADPC macro expansion that passed the incorrect CPU list parameter to the $ADPC macro service routine.
Program: CCNUCL (member CICR), GETCC processing.
Error Message: None.
Explanation: A GETCC macro was issued and a storage block type and size mismatch was found.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CICS, CCNUCL; MOVEC processing
Error Message: MOVEC -- INVALID MOVE TO ADDRESS, OR BAD LENGTH
Explanation: The TO= address could not be converted to a system virtual memory (SVM) address or the TO= address plus the length was beyond the end of storage.
System Action: The entry is exited and error recovery is initiated.
User Response: Check the TO= address specified in the MOVEC call to determine the cause of failure.
Program: CICS, CCNUCL; MOVEC processing
Error Message: MOVEC -- INVALID MOVE FROM ADDRESS, OR BAD LENGTH
Explanation: The FROM= address could not be converted to a system virtual memory (SVM) address or the FROM= address plus the length was beyond the end of storage.
System Action: The entry is exited and error recovery is initiated.
User Response: Check the FROM= address specified in the MOVEC call to determine the cause of failure.
Program: CICS, CCNUCL
Error Message: CLHSC -- UNSUPPORTED INDEX FOR CLH SVC
Explanation: The CLHSC SVC call was made with an index that is not valid or is not supported.
System Action: A SNAPC dump is is issued, the entry is exited, and error recovery is initiated.
User Response: Do not use CLHSC for user SVCs.