gtpm4m0v | Messages (System Error and Offline) |
Program: CL20
Error Message: WLOGC DATALIST EXCEEDS MAXIMUM SIZE
Appended Message: None.
Explanation: A WLOGC macro request passed a DATALIST containing more than 32 KB of data.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why a logic error occurred.
Program: CCEB
Error Message: EXIT REQUESTED, TRANSACTION NOT COMMITTED
Appended Message: None.
Explanation: You attempted to exit while in a commit scope.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Modify the program to commit the database changes.
Program: CL11
Error Message: RECOVERY LOG ESFAC ERROR ENCOUNTERED
Appended Message: None.
Explanation: An error condition was returned from ESFAC when accessing record 0 of the recovery log during log takeover processing.
System Action: Log takeover processing ends abnormally. The processor log is not recovered.
User Response: Review the system error dump to determine the cause of the error. You may need to recover or initialize the recovery log of the other processor again.
Program: CL11
Error Message: INSUFFICIENT STORAGE TO PROCESS RECOVERY LOG TAKEOVER
Appended Message: None.
Explanation: An error condition was returned from the GSYSC macro when requesting storage for the tables that are required for recovery log takeover processing.
System Action: Log takeover processing ends abnormally. The processor log is not recovered.
User Response: Review the system error dump to determine the cause of the error. You may need to recover or initialize the recovery log of the other processor again.
Program: CL21
Error Message: VALIDATION ERROR ON RECOVERY LOG CHECK POINT RECORD
Appended Message: None.
Explanation: The checkpoint record points to the track that is to be read first during recovery. The data in this record did not verify the data in the checkpoint record.
System Action: The validity of the start point data in the checkpoint record is compromised. The entire log is reviewed to discover the recovery point. If no other problems occur, the log has been recovered successfully.
User Response: Review the system error dump and determine why the validation error occurred. The information displayed contains the data from the checkpoint record and the track header.
Program: CEFJ, CEFL
Error Message: FNSPC NOT ALLOWED IN ACTIVE COMMIT SCOPE
Error Message: FLSPC NOT ALLOWED IN ACTIVE COMMIT SCOPE
Appended Message: None.
Explanation: You attempted to use the FNSPC or FLSPC macro while a commit scope was active.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Do one of the following:
Program: CL20
Error Message: ILLOGICAL BUFFER BLOCKED CONDITION DETECTED
Appended Message: None.
Explanation: A buffer blocked condition was raised while splitting a WLOGC macro request across a buffer boundary. This indicates that the WLOGC request was partially processed and there is not enough room in the buffer area to complete the request.
System Action: The integrity of the transaction log is compromised if processing continues. This is a catastrophic dump.
User Response: Do the following:
Program: CL20
Error Message: UNABLE TO FIND TMCR FOR LSN UPDATE
Appended Message: None.
Explanation: Processing of TANCC LOCATE returned a not found condition. WLOGC processing is attempting to update the transaction manager control record (TMCR) with the assigned log sequence number.
System Action: The TMCR is not updated and control returns to the mainline path, where normal processing continues. This is a logic error and may cause the recovery log activity pointers to be incorrectly updated, resulting in a log full condition.
User Response: Review the system error dump to determine why the logic error occurred.
Register 14 contains the return code from the TANCC macro. The dump also contains the contents of the recovery log header, which could contain an exchange identification (XID) that is not valid.
Program: CL30
Error Message: $GETRC ERROR - INVALID TID DETECTED
Appended Message: None.
Explanation: A transaction manager logic error occurred while using the TANCC macro to add the passed transaction ID to the transaction anchor table.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Do the following:
Program: CL30
Error Message: $GETRC ERROR - INVALID RMID DETECTED
Appended Message: None.
Explanation: A resource manager logic error occurred. The passed resource manager ID (RMID) was reviewed and found to be outside of the permitted range.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CL30
Error Message: $RETRC ERROR - INVALID RMID DETECTED
Appended Message: None.
Explanation: A resource manager logic error occurred. The passed resource manager ID (RMID) was reviewed and found to be outside of the permitted range.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CL30
Error Message: $RELRC ERROR - INVALID TMCR ADDRESS DETECTED
Appended Message: None.
Explanation: A transaction manager logic error occurred while attempting to delete the current transaction manager control record (TMCR) from the transaction anchor table.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CL21
Error Message: RECOVERY LOG FACE ERROR ENCOUNTERED
Error Message: RECOVERY LOG FIND ERROR ENCOUNTERED
Appended Message: None.
Explanation: An error condition was returned while accessing a recovery log record. This error indicates a FACE table (FCTB) or hardware error.
System Action: The recovery log cannot be processed. If the host log is being processed, the dump exits the restart entry control block (ECB) and the system cycle is inhibited. If another processor log is being processed (that is, a log takeover), processing ends abnormally and the log is not run.
User Response: Review the system error dump and determine why the error occurred.
Program: CL21
Error Message: TRACK READ/VALIDATION ERROR ENCOUNTERED
Appended Message: None.
Explanation: A validation error occurred while reading the log back to the recovery point. A validation error is detected if there is a break in log sequence numbers between tracks or between records on a track. This dump is issued by the CL21 program, but the validation error is detected by the CL24 program.
System Action: The recovery log cannot be processed. Processing is the same for the host log and the takeover log; a system error is issued and the recovery log is initialized again.
User Response: Review the system error dump to determine why the error occurred. A validation error can indicate corruption of the track buffer area.
Program: CL24
Error Message: RECOVERY LOG FACE ERROR ENCOUNTERED
Appended Message: None.
Explanation: An error condition was returned from the file address compute program (FACE) while accessing a recovery log record.
System Action: The following actions occur:
User Response: Review the system error dump and determine why the FACE error occurred.
Program: CL21
Error Message: FIND ERROR ON RECOVERY LOG CHECK POINT RECORD
Appended Message: None.
Explanation: An error condition was returned while accessing the recovery log checkpoint record.
System Action: A dump is issued and processing continues. The validity of the start point data in the checkpoint record is compromised. The entire log is reviewed to determine the recovery point. If no other problems occur, the log has been recovered successfully.
User Response: Review the system error dump to determine why the error occurred.
Program: CXAOPN, CXASTR, CXAEND, CXAPRP, CXACMT, CXARLB, CXARCV, CXPCMT, CXPRLB, or CXPRCV in CTAL.
Error Message: INVALID PARAMETER IS DETECTED BY XA FUNCTION
Appended Message: None.
Explanation: A transaction manager logic error occurred. An incorrect parameter was passed to one of the following functions in CTAL: xa_open, xa_start, xa_end, xa_prepare, xa_commit, xa_rollback, xa_recover, xa_cmt_pool, xa_rlb_pool, or xa_rcv_pool.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CXAOPN, CXASTR, CXAEND, CXAPRP, CXACMT, CXARLB, CXARCV, CXPCMT, CXPRLB, or CXPRCV in CTAL.
Error Message: XA PROTOCOL VIOLATION IS DETECTED BY RM
Appended Message: None.
Explanation: A transaction manager logic error occurred. A protocol violation was detected by the resource manager (RM) when one of the following functions is called: xa_open, xa_start, xa_end, xa_prepare, xa_commit, xa_rollback, xa_recover, xa_cmt_pool, xa_rlb_pool, or xa_rcv_pool.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CXACMP, CXAFGT, or CAXCLS in CTAL
Error Message: UNSUPPORTED XA FUNCTION IS CALLED
Appended Message: None.
Explanation: A transaction manager logic error occurred. One of the following unsupported XA functions was called: xa_complete, xa_forget, or xa_close.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CCOMIC in CTAL
Error Message: TX_RESUME_TPF IS ISSUED WITHOUT A PRIOR TX_SUSPEND_TPF CALL
Appended Message: None.
Explanation: The application program did not call the tx_suspend_tpf function before calling the tx_resume_tpf function.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CL12
Error Message: ERROR OCCURRED WHEN OPEN RESOURCE MANAGERS, CYCLE IS INHIBITED
Appended Message: None.
Explanation: One of the defined resource managers cannot complete the xa_open function successfully at system restart time.
System Action: Restart continues but the state change is disabled.
User Response: Review the system error dump to determine why the logic error occurred.
Program: CL22
Error Message: RECOVERY LOG I/O ERROR ENCOUNTERED
Appended Message: None.
Explanation: An input/output (I/O) error occurred on both the prime and duplicate copies while writing a track to the recovery log.
System Action: The integrity of the log is compromised if processing continues. One of the following occurs depending on the state of the TPF system when the error occurs:
User Response: Review the system error dump to determine why both writes failed.
Program: CL22
Error Message: RECOVERY LOG FACE ERROR ENCOUNTERED
Appended Message: None.
Explanation: An error condition was returned from the file address compute program (FACE) when accessing a recovery log record.
System Action: The integrity of the log is compromised if processing continues. One of the following occurs depending on the state of the TPF system when the error occurs:
User Response: Review the system error dump to determine why the FACE error occurred.
Program: CL22
Error Message: RECOVERY LOG IS FULL
Appended Message: None.
Explanation: The recovery log is in danger of overwriting itself and there is not enough room left in it to survive an IPL or recovery.
System Action: The integrity of the log recovery is compromised if processing continues.The integrity of the log is compromised if processing continues. One of the following occurs depending on the state of the TPF system when the error occurs:
User Response: Review the system error dump to determine why the error occurred. The recovery log may be too small and may need to be reallocated. You can IPL the TPF system to recover and empty the log.
Program: CL21
Error Message: INSUFFICIENT STORAGE TO RECOVER DATA FROM LOG
Appended Message: None.
Explanation: An error condition was returned from MALOC when requesting storage for a log record.
System Action: The recovery log cannot be processed. The dump exits the restart entry control block (ECB) and system cycle is inhibited.
User Response: Review the system error dump and determine why the MALOC error occurred.
Program: CL21
Error Message: CONFIGURATION ERROR - RECOVERY LOG LOST
Error Message: VALIDATION ERROR ON FIRST LOG RECORD - RECOVERY LOG LOST
Appended Message: None.
Explanation: Changes to the allocation and configuration of the recovery log can cause the following error conditions to be detected:
This condition can also occur if the checkpoint record is corrupted.
System Action: The recovery log cannot be processed if its allocation characteristics have been changed. The recovery log is initialized again and system restart continues.
User Response: If this system error dump is unexpected, examine it to determine if it was caused by checkpoint record corruption.
Program: CL30
Error Message: $RELRC ERROR - TMCR RELEASE WITH RMCR STILL ACTIVE
Appended Message: None.
Explanation: A transaction manager control record (TMCR) is being released and an associated resource manager control record (RMCR) is still active.
System Action: The associated RMCR is released and processing continues.
User Response: Review the system error dump to determine why the resource manager (RM) did not release the TMCR. The system error dump contains a copy of both the TMCR and the RMCR.
Program: CEFH
Error Message: LOGIC ERROR - CCR HAS BAD RHT POINTER
Appended Message: None.
Explanation: The record hold table (RHT) indicates that a record is held at the commit scope level by the entry control block (ECB) that is active at the time of the dump. The commit control records (CCRs) that are attached to the ECB do not contain an entry pointing to this RHT entry.
System Action: The ECB exits and the RHT lock is released.
User Response: See your IBM service representative.
Program: CEFH
Error Message: HOLD OF RECORD IN SUSPENDED COMMIT SCOPE
Appended Message: None.
Explanation: You attempted to hold a record that is part of a suspended commit scope.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the requirement for the hold locks.
Program: CEFH
Error Message: UNHOLD OF RECORD IN SUSPENDED COMMIT SCOPE
Appended Message: None.
Explanation: You attempted to unhold a record that is part of a suspended commit scope.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Review the requirement for the hold locks.
Program: CEFH
Error Message: INVALID RECORD HOLD COUNT IN ECB RESET
Appended Message: None.
Explanation: During rollback processing, records that are held by the application in the commit scope are released and the record hold count in the entry control block (ECB) is adjusted. The record hold count in the ECB should never be negative; this dump is taken during rollback processing when the TPF system detects a negative record hold count.
System Action: Rollback processing continues. Indicators are set to force cleanup of the record hold table during exit processing. Control returns to the ECB. This dump may be followed by an 0000FC system error indicating that the user ECB may have tried to hold more than 256 records.
User Response: See your IBM service representative.
Program: CVF3
Error Message: ATTEMPTED ACCESS OF SUSPENDED RECORD
Appended Message: None.
Explanation: You attempted to access a record that is part of a suspended commit scope set.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Determine why the program was trying to access a record in a suspended commit scope.
Program: CVF3
Error Message: FINSC P/D IN ACTIVE COMMIT SCOPE
Error Message: FILSC P/D IN ACTIVE COMMIT SCOPE
Appended Message: None.
Explanation: You attempted to use the FINSC or FILSC macros while a commit scope was active.
System Action: The entry control block (ECB) exits and the commit scope ends as if a TXRBC macro or tx_rollback C function was called. If the entry was activated from an online workstation, the operator is notified.
User Response: Do one of the following:
Program: CVF3
Error Message: NO AVAILABLE VFA BUFFER
Appended Message: None.
Explanation: This is an out-of-resource error that indicates one of the following application problems:
When an entry control block (ECB) writes a record in a commit scope, the data is saved in a commit buffer. Commit buffers are taken from virtual file access (VFA) as needed. This system error occurs during record file processing when the TPF system is not able to find an available VFA buffer to use as a commit buffer.
System Action: The ECB exits.
User Response: Do one of the following to determine the cause of the out-of-VFA buffer condition:
If a single ECB used too many VFA buffers as commit buffers, enter the ZCTKA ALTER command with the MCMTB parameter specified to set the maximum commit buffers allowed per ECB. If the spontaneous load on the system is higher than can be supported with the amount of VFA storage available, do one of the following:
See TPF Operations for more information about the ZVFAC INDICATE, ZVFAC DISPLAY, ZCTKA ALTER, ZDCLV, and ZACLV commands.
Program: CL31
Error Message: INSUFFICIENT STORAGE FOR DASD RESOURCE MANAGER RECOVERY PROCESS
Appended Message: None.
Explanation: The DASD resource manager (RM) recovery program (CL31) cannot get enough storage for its process.
System Action: The entry control block (ECB) exits and state change is disabled.
User Response: Review the system error dump to determine why storage is not available.
Program: CL31
Error Message: DUPLICATE DASD RM HARDEN RECORDS ARE FOUND
Appended Message: None.
Explanation: The DASD resource manager (RM) restart program (CL31) detected duplicate hardened records for a transaction.
System Action: Resume the restart process after the dump is taken.
User Response: Review the system error dump to determine why duplicate hardened records exist.
Program: CL14
Error Message: INSUFFICIENT STORAGE FOR TRANSACTION MANAGER RECOVERY PROCESS
Appended Message: None.
Explanation: The transaction manager recovery program (CL14) cannot get enough storage for its process.
System Action: The entry control block (ECB) exits after the dump is taken.
User Response: Review the system error dump to determine why storage is not available.
Program: CXARCV (CTAL)
Error Message: TMSTARTSCAN FLAG IS NOT SET WHEN CALLING XA_RECOVER FUNCTION
Appended Message: None.
Explanation: The xa_recover function of the DASD resource manager requires that the flag parameter be set to TMSTARTSCAN.
System Action: The entry control block (ECB) exits and state change is inhibited.
User Response: Ensure that any program calling the xa_recover function of the DASD resource manager sets the TMSTARTSCAN flag when issuing the function call.
Program: CXARCV (CTAL)
Error Message: XID OVERFLOWED IN XA_RECOVER FUNCTION
Appended Message: None.
Explanation: The program calling the xa_recover function of the DASD resource manager does not provide enough space in the XIDS parameter to hold transaction branches that need to be recovered.
System Action: Return to the caller after the dump is taken.
User Response: Ensure that any program calling the xa_recover function of the DASD resource manager provides enough storage to hold all of the transaction branches that need to be recovered.
Program: CL40
Error Message: NOT ENOUGH SYSTEM HEAP STORAGE
Appended Message: None.
Explanation: The GSYSC macro is not able to allocate the requested storage.
System Action: Deadlock detection continues.
User Response: Review the system error dump to determine why the error occurred.
Program: CLXA
Error Message: ROUTC IS ISSUED WITHIN A COMMIT SCOPE
Appended Message: None.
Explanation: A ROUTC or SENDC macro with CLASS A, B, C, or L is called in a commit scope.
System Action: The entry control block (ECB) exits after the SERRC is taken.
User Response: Change the program so it does not call a ROUTC or SENDC macro with CLASS A, B, C, or L in a commit scope.
Program: CVIA
Error Message: CHAIN MESSAGE IS SENT WITHIN A COMMIT SCOPE
Appended Message: None.
Explanation: A chain message is sent in a commit scope from the CVIx package.
System Action: The entry control block (ECB) exits after the SERRC is taken.
User Response: Change the program so that the chain message is not sent in a commit
scope.
Program: CVF3
Error Message: USER MAXIMUM RECORDS IN COMMIT SCOPE EXCEEDED
Appended Message: None.
Explanation: The number of records in the commit scope is about to exceed the limit set for
your TPF system.
System Action: The entry control block (ECB) exits and the commit scope is rolled
back.
User Response: Do the following:
See TPF Operations for more information about the
ZCTKA ALTER command.
Program: CCNUCL(CICR)
Error Message: DEFRC WITH LOCKS HELD AT COMMIT SCOPE LEVEL
Appended Message: None
Explanation: The DEFRC macro was called in a commit scope while locks were held at the commit scope level.
System Action: The entry control block (ECB) exits after the SERRC is taken.
User Response: Change the program so that the DEFRC macro is not called with locks held at the commit scope level. Determine whether it is appropriate to commit all updates (using the TXCMC macro or tx_commit C function) before calling the DEFRC macro.
Program: CLM1
Error Message: INCORRECT ATTEMPT TO LOCK FENCE PROCESSOR
Appended Message: None
Explanation: You tried to lock fence a processor using an obsolete interface. In the TPF transaction services environment, lock fencing is no longer an appropriate recovery action for unresponsive processors during lock movement, copy end-of-job (EOJ), and other similar functions. Locks associated with a failed processor must remain held until log recovery has been completed.
System Action: The entry control block (ECB) exits.
User Response: Correct the program that is trying to use the obsolete lock fencing interface.
Program: CCEB
Error Message: COMMIT SCOPE CLEANUP FAILURE
Appended Message: None.
Explanation: System error processing called exit processing, which detected a system integrity problem. This catastrophic dump was caused by one of the following:
The integrity of the recovery log and the application database could be compromised if processing continues.
System Action: A catastrophic dump is issued and processing stops.
User Response: See your IBM service representative.
Program: CL40
Error Message: MERGED FILE ADDRESS TABLE FOR DEADLOCK DETECTION IS FULL
Appended Message: None.
Explanation: In a loosely coupled processor complex, the deadlock detection process allocates storage for a merged file address table that is used to merge records in the record hold table for all active processors. The merged file address table filled up before the merge process completed. Because the merged file address table is full, there will be missing record hold table entries and some deadlock conditions may not be detected.
System Action: Deadlock detection takes a SNAP dump and continues.
User Response: Because the size of the merged address file table is limited to 35% of the entry control block (ECB) heap storage area, enter the ZCTKA ALTER command with the EMPS and MMHS parameters specified to increase the size of the ECB heap storage.
See TPF Operations for more information about the ZCTKA ALTER command.
Program: CUPT
Error Message: POSITIVE FEEDBACK LOG ERROR ON DATA RECORD
Appended Message: None
Explanation: The finwc function was issued to get the current ordinal record in the positive feedback database, but finwc function processing was not successful.
System Action: The following occurs:
User Response: Do the following:
Program: CUPT
Error Message: POSITIVE FEEDBACK LOG ERROR ON CONTROL RECORD
Appended Message: None
Explanation: The control record, ordinal 0, in the positive feedback database could not be accessed.
System Action: The following occurs:
User Response: Do the following:
Program: CUPH
Error Message: ERROR CHANGING THE HFS DIRECTORY
Appended Message: None
Explanation: The chdir function was issued to change to the tpf.va directory, but the chdir function did not complete successfully. If the directory did not exist, the positive feedback code would have created it.
System Action: The following occurs:
User Response: Do the following:
Program: CUPH
Error Message: ERROR ISSUING MKDIR ON THE HFS DIRECTORY
Appended Message: None
Explanation: The mkdir function was issued to make the tpf.va directory, but the mkdir function did not complete successfully. The mkdir function was issued after the return code from the chdir function indicated that the required directory did not exist.
System Action: The following occurs:
User Response: Do the following:
Program: CUPH
Error Message: ERROR OPENING THE HFS FILE FOR COPY
Appended Message: None
Explanation: The open function was issued to open the hierarchical file system (HFS) file named in the fileName variable in the CUPT segment, but the open function did not complete successfully. If the file did not exist, the function would have created it.
System Action: The following occurs:
User Response: Ensure that the proper authorizations exist for the HFS file named in the CUPT segment.
Program: CUPH
Error Message: ERROR POSITIONING TO CORRECT OFFSET IN THE HFS
Appended Message: None
Explanation: The fseek function was issued to position the correct offset in the hierarchical file system (HFS) to start copying new data from the TPF database. The fseek function did not complete successfully.
System Action: The following occurs:
User Response: Check the integrity of the file listed for the HFS file named in the CUPT segment.
Program: CUPH
Error Message: ERROR POSITIONING TO BYTE 0 IN THE HFS
Appended Message: None
Explanation: The fseek function was issued to position to the beginning of the hierarchical file system (HFS) in order to start copying new data from the TPF database. The fseek function did not complete successfully.
System Action: The following occurs:
User Response: Check the integrity of the file listed for the HFS file named in the CUPT segment.
Program: CUPH
Error Message: ERROR OPENING OR CREATING THE HFS
Appended Message: None
Explanation: The open function was issued with the option to create the file if the file does not exist. The open function did not complete successfully.
System Action: The following occurs:
User Response: Do the following: