gtpm4m0qMessages (System Error and Offline)

005000-005FFF


005001

Program: CFCM, CFCE

Error Message: CF MESSAGE ROUTINE LOGIC ERROR

Explanation: The control program (CP) tried to perform a coupling facility (CF) operation, but a logic error, storage corruption, or a hardware failure occurred.

System Action: A catastrophic system error is issued.

User Response: Review the system error dump for possible storage corruption, particularly in the CCCFCC control program or the CF control blocks and tables.

See TPF Database Reference for more information about CF control blocks and tables.


005002

Program: CFCE

Error Message: CF LIST NOTIFICATION VECTOR ERROR

Explanation: The control program (CP) tried to modify a list notification vector, but a logic error or storage corruption occurred.

System Action: A catastrophic system error is issued.

User Response: Review the system error dump for possible storage corruption, particularly in the CCCFCC control program or the CF control blocks and tables.

See TPF Database Reference for more information about CF control blocks and tables.


005003

Program: CFCR

Error Message: UNEXPECTED CF RETURN CODE FROM SETLOCK

Explanation: The CFRQC macro with the REQUEST parameter set to SETLOCK was issued, but an error occurred because an unexpected return code was received. Either the return code received is not logical for the lock type or it does not exist for the command.

System Action: A SNAP dump is issued and control returns to the caller.

User Response: Do the following:

  1. Review the SNAP dump to determine the cause of the error.
  2. See your IBM service representative for an explanation of the coupling facility (CF) return code and provide the following information from the SNAP dump:


005004

Program: CFCR

Error Message: INVALID REQUEST VALUE FOR CFRQC MACRO

Explanation: The service routine for the CFRQC macro determined that the specified request value was not valid.

System Action: A SNAP dump is issued and the entry control block (ECB) exits.

User Response: Do the following:

  1. Review the SNAP dump to determine the cause of the error error. Verify that the value meets the following conditions:
  2. Correct the error.


005005

Program: CFCR

Error Message: MESSAGE SUBCHANNEL CONFIGURATION ERROR

System Action: A SNAP dump is issued, the message subchannel is not activated and processing continues.

Explanation: The service routine for the CFRQC ACTSDA macro determined that not all channel paths for the message subchannel are connected to the same device.

User Response: Do the following:

  1. Review the SNAP system error to determine the message subchannel in error.
  2. Check for cabling errors or an incorrect definition in the I/O configuration data set (IOCDS).
  3. Correct the problem.


005006

Program: CFCE

Error Message: CF SUPPORT LOGIC ERROR

Appended Message: STRUCTURE ALLOCATION INCOMPLETE

Explanation: A coupling facility (CF) command was issued to a CF structure before the structure completed the storage allocation process.

System Action: A catastrophic system error is issued.

User Response: Do the following:

  1. Determine why the CF command was issued before the storage allocation process was completed.
  2. Correct the error.

Program: CFCE

Error Message: CF SUPPORT LOGIC ERROR

Appended Message: STRUCTURE DEALLOCATION INCOMPLETE

Explanation: A coupling facility (CF) command was issued to a CF structure before the structure completed the storage deallocation process.

System Action: A catastrophic system error is issued.

User Response: Do the following:

  1. Determine why the CF command was issued before the storage deallocation process was completed.
  2. Correct the error.

Program: CFCE

Error Message: CF SUPPORT LOGIC ERROR

Appended Message: INCORRECT FACILITY STATE

Explanation: A coupling facility (CF) command was issued that requires the CF to be in a managed state, but the CF was not in that managed state. It is possible that an unsupported host connected to the CF and placed it in the nonmanaged state.

System Action: A catastrophic system error is issued.

User Response: Do the following:

  1. Determine why the command was issued when the CF was in a nonmanaged state.
  2. Correct the error.

Program: CFCE

Error Message: CF SUPPORT LOGIC ERROR

Appended Message: UNRECOGNIZED ERROR

Explanation: An error condition was detected by the coupling facility (CF), but the meaning of the error was not determined.

System Action: A catastrophic system error is issued.

User Response: See your IBM service representative.

Program: CFCE

Error Message: CF SUPPORT LOGIC ERROR

Appended Message: PROGRAM CHECK

Explanation: A program check condition was found by the coupling facility (CF), probably because of corrupted or failing storage in or around the message command block (MCB) or message response block (MRB).

System Action: A catastrophic system error is issued.

User Response: Review the system error dump for possible storage corruption, particularly in the CCCFCC control program (CP), the CF control blocks and tables, the MCB, and the MRB.

See TPF Database Reference for more information about the control blocks and tables.

Program: CFCE

Error Message: CF SUPPORT LOGIC ERROR

Appended Message: REQUEST EXCEPTION

Explanation: A coupling facility (CF) command was issued, but the request operand was specified improperly or an unassigned command code was specified.

System Action: A system error is issued.

User Response: Review the system error dump for possible storage corruption, particularly in the CCCFCC control program, the CF control blocks and tables, the message command block (MCB), and the message response block (MRB).

See TPF Database Reference for more information about the control blocks and tables.


005007

Program: CFCR

Error Message: CF LIST NOTIFICATION VECTOR RELEASE ERROR

Explanation: A request to release a list notification vector was not successful because it is not assigned.

System Action: A SNAP dump is issued, control returns to the caller, and processing continues.

User Response: Do the following:

  1. Determine the source of the list notification token corruption.
  2. Correct the error.


005008

Program: CFCR

Error Message: SETLOCK DETECTED CORRUPT CF LOCK DATA

Explanation: An error occurred because the coupling facility (CF) lock data could not be determined or was not logical.

System Action: A SNAP dump is issued and control returns to the caller.

User Response: Determine the cause of the corruption and correct the error.


005009

Program: CFCR

Error Message: SETLOCK INPUT REQUEST NOT VALID

Explanation: The CFRQC macro with the REQUEST parameter set to SETLOCK was issued and was unable to modify the coupling facility (CF) lock because the content of the request indicator in the SETLOCK block is not valid or is corrupted.

System Action: A SNAP dump is issued and control returns to the caller.

User Response: Do the following:

  1. Correct the content of the request indicator in the SETLOCK block so it is valid and not corrupted.
  2. Issue the CFRQC macro again with the REQUEST parameter set to SETLOCK.


00500A

Program: CFSBFL, CLM6

Error Message: CFSB FILE RECORD CORRUPTION

Explanation: An error occurred because the file copy of the coupling facility structure block (CFSB) record is corrupted.

System Action: A SNAP dump is issued and control returns to the caller.

User Response: Determine the cause of the corruption using the image of the record that was dumped.


005100

Program: CVZ6

Error Message: ZKPTR CANCEL ENTERED

Appended Message: KEYPOINT POINTER RECORD IS NOT VALID

Explanation: During system restart it was determined that the keypoint pointer record was corrupted or did not match the #KEYPT definition in the FACE table (FCTB). The ZKPTR command with the CANCEL parameter specified was entered to cancel the IPL. The rebuilt or updated pointer record created by the system restart was not filed.

System Action: The system restart entry control block (ECB) exits.

User Response: Do one of the following

See TPF Operations for more information about the ZKPTR command.


005101

Program: CYYF

Error Message: MALOC UNABLE TO ALLOCATE REQUESTED STORAGE

Explanation: The MALOC macro was unable to allocate heap storage for the retrieval of one or all of the subsystem state table ordinals of record type #CN1ST.

System Action: The entry control block (ECB) exits after processing the dump.

User Response: Do the following

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and IPL the TPF system.

See TPF General Macros for more information about the MALOC macro.


005102

Program: CYYF, CYYH

Error Message: CTKI FIND ERROR

Explanation: Module CYYM reported an error while doing a find for keypoint record I.

System Action: One of the following occurs:

User Response: Do the following

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and IPL the TPF system.

Error Message: CTKI FILE ERROR

Explanation: Module CYYA reported an error while writing keypoint record I to the file.

System Action: One of the following occurs:

User Response: Do the following

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and IPL the TPF system.


005103

Program: CYYF

Error Message: DATA LEVEL PASSED TO CYYF EXCEEDS VALID RANGE

Explanation: A data level greater than DE(14) was passed to CYYF as an input parameter in entry control block (ECB) field EBCM02. The data level was to be used for CTKI.

System Action: The ECB exits after the dump is processed.

User Response: Correct the application program calling CYYF so that a data level of DE(14) or lower is specified.

Error Message: REGISTER INDEX PASSED TO CYYF EXCEEDS VALID RANGE

Explanation: A register index value equal to register 0 (R0) or greater that register 7 (R7) was passed to CYYF as an input parameter in ECB field EBCM03. This register value contains a pointer to the data area containing the data to be filed or to the data being retrieved.

System Action: The ECB exits after the dump is processed.

User Response: Correct the application program calling CYYF so that a register value in the range R1 - R7 is specified.


005104

Program: CVZ6

Error Message: CTKX VS FACE KEYPT FILE ADDRESS MISMATCH

Appended Message: KEYPOINT c FILE ADDRESS MISMATCH CTKX-fileadr1 FACS-fileadr2

Where:

c
The keypoint that was changed.

fileadr1
The keypoint file address stored in CTKX.

fileadr2
The keypoint file address returned from FACS.

Explanation: During system restart, it was determined that the keypoint pointer record (KPTR) was corrupted or did not match the #KEYPT definition in the FACE table (FCTB). The ZKPTR command with the REPLACE parameter specified was entered to update the KPTR and, the rebuilt or updated KPTR created by system restart was filed. While validating that the keypoint file addresses in CTKX had not change, it was determined that the file address for at least one keypoint had changed.

System Action: This is a catastrophic system error. The TPF system will automatically re-IPL itself causing any changed keypoint file address to be corrected in CTKX.

User Response: None.


005105

Program: CVZ5

Error Message: KEYPT PNTR REC FACE OR FIND ERROR

Appended Message: KEYPOINT POINTER RECORD function ERROR - rectype.0 - error

Where:

function
The system function returning a FACE_FACS or FIND error condition.

rectype
The record type whose keypoint pointer record (KPTR) was being processed. (Ordinal zero of the record type is the KPTR.)

error
Error text explaining the error returned. For FACE _FACS errors, descriptve text is generated. For FIND errors, the detail data level error indicator byte (CE1SUD) is displayed in hexadecimal.

Explanation: While a command was processing a keypoint pointer record (KPTR), the specified function returned an error condition.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and reissue the failing command.

See the TPF C/C++ Language Support User's Guide for more information about errors returned by the FACE_FACS function and TPF General Macros for more information about the values returned in the detail data level error indicator byte.


005106

Program: CVZ8

Error Message: KEYPT PNTR REC BUILD FACE OR ESFAC ERROR

Appended Message: KEYPOINT POINTER RECORD EXTENT TABLE BUILD function ERROR - rectype.ord - error

Where:

function
The system function returning a FACS or ESFAC error condition.

rectype
The record type whose keypoint pointer record (KPTR) extent table was being built.

ord
The record ordinal being processed when the error occurred.

error
For FACS errors: R7-hexdata R6-hexdata.

hexdata
The hexadecimal data returned in R7 and R6.

For ESFAC errors: FA-fileaddr

fileaddr
The file address that ESFAC was unable to process.

Explanation: While a command was building a keypoint pointer record (KPTR) extent table, the specified function returned an error condition.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and reissue the failing command.

See TPF Application Programming for more information about errors returned by the FACS function, TPF General Macros for more information about the ESFAC macro, and the TPF C/C++ Language Support User's Guide for information about the tpf_esfac function.


005107

Program: CVZ5

Error Message: KEYPT PNTR REC READ OR VALIDATE ERROR

Appended Message: rectype KEYPOINT POINTER RECORD error

Where:

rectype
The record type whose keypoint pointer record (KPTR) is being read.

error
The error condition existing in the KPTR, which is either CORRUPTED or OUT OF SYNC.

Explanation: While a command or system process was finding a KPTR, the cvz5_find_kptr function returned the specified error condition.

System Action: A SNAP dump is taken and processing continues on the command's error path for a FACE error on a keypoint record.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem. Enter the ZKPTR command with the DISPLAY parameter specified to gather additional data to assist in the analysis.
  2. Correct the problem and reissue the failing command.

See TPF Operations for more information about the ZKPTR command.


005108

Program: CVZ8

Error Message: KEYPT CNTRL REC EXTENT TABLE BUILD ERROR

Appended Message: rectype KPTR EXTENT TABLE BUILD ERROR - error

Where:

rectype
The record type whose keypoint pointer record (KPTR) extent table is being built.

error
The error condition found while building the extent table. Possible values are: RECORD TYPE NOT DEFINED, TOO MANY EXTENTS, and RECORD TYPE NOT VALID

Explanation: While a command or system process was building a keypoint pointer record (KPTR) extent table, the cvz8_build_extent_table function returned one of the following error conditions:

System Action: A SNAP dump is taken and processing continues on the command's error path for a FACE error on a keypoint record.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and reissue the failing command.

See TPF System Generation for more information about the RAMFIL statements and the FCTB.


005109

Program: CVZ4

Error Message: KEYPOINT ORDINAL MAPPING ERROR

Appended Message: KEYPOINT ORDINAL MAPPING ERROR - INPUT ORDINAL TOO HIGH

Explanation: The input ordinal specified in register 0 (R0) is too high for the keypoint extents defined in the keypoint pointer record (IKPTR).

Appended Message: KEYPOINT ORDINAL MAPPING ERROR - INPUT ORDINAL TOO LOW

Explanation: The input ordinal specified in R0 is too low. Ordinal 0 is not mapped because it would map to 0 and negative ordinals are not allowed.

Appended Message: KEYPOINT ORDINAL MAPPING ERROR - MODULE OFFSET NEGATIVE

Explanation: The module offset in R6 is negative. Module offsets that are used to calculate the FACE ordinal on a module other than system prime modules must be zero or a positive value.

Appended Message: KEYPOINT ORDINAL MAPPING ERROR - IKPTR EXTENT ITEM COUNT NOT VALID

Explanation: The count of items in the keypoint pointer record (IKPTR) is negative, 0, or greater than the possible number of items. The keypoint pointer record is corrupted.

System Action: A SNAP dump is taken and processing continues on the command's error path for a FACE error on a keypoint record.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and reissue the failing command.


00510A

Program: Varied: displayed in the dump and the dump message

Error Message: MALOC, CALOC, MALLOC, CALLOC ERROR

Explanation: A MALOC or CALOC macro or malloc or calloc function was called to allocate storage. No storage was returned.

System Action: A system error dump is taken and processing of the command ends.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and reissue the failing command.


00510B

Program: CYYJ

Error Message: CTKC FIND ERROR

Explanation: Module CYYM reported an error while doing a FIND for keypoint record C.

System Action: The ECB exits.

User Response: Do the following

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and IPL the TPF system.

Error Message: CTKC FILE ERROR

Explanation: Module CYYA reported an error while writing keypoint record C to the file.

System Action: The ECB exits.

User Response: Do the following

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and IPL the TPF system.


00510C

Program: CIKZ

Error Message: ZMIGR KEYPOINT PARAMETER LOGIC ERROR

Appended Message: ZMIGR KEYPOINT - ACTION INDEX IS NOT VALID

Explanation: An action parameter index value that is not a multiple of 4 was found.

System Action: A SNAP dump is taken and processing of command ends with message MIGR0015T.

User Response: Do the following:

  1. Analyze the dump to determine the cause of the problem.
  2. Correct the problem and reissue the failing command.