gtpm4m0aMessages (System Error and Offline)

000100-0001FF


000101

Program: CCSNA1(CS01, CS07, CSX4)

Error Message: CONDITION CODE 1 RETURN TO SIOSC

Explanation: An SIOSC macro was issued and a condition code 1 that was not valid was received from CIO. The SIOSC macro processor in IPLB segment CCIO should only be returning a condition code of:

System Action: A catastrophic system error is issued. The TPF system performs an IPL.

User Response: See your system programmer to check the problem. The problem may be a logic error in CIO.


000108

Program: CCSNA1(CS01,CS07,CSX4,CS0G), CC3705 (CRNM, CRNI)

Error Message: One of the following:

Explanation: CCSNA1 or CC3705 issued the SIOSC macro but the macro was already issued.

System Action: The lost terminal interface routine is activated, which deactivates the device. If CS0G issued this message, a catastrophic system error occurs.

User Response: See your system programmer to check the problem. The problem may be a logic error in CCSNA1.

Error Message: One of the following:

Where:

nnn
The symbolic device address (SDA).

Explanation: CCSNA1 or CC3705 issued the SIOSC macro but the device is not mounted and cannot be accessed.

System Action: The lost terminal interface routine is activated.

User Response: Mount and reactivate the device.


000109

Program: CCCCP1(CLYE)

Error Message: SIOSC ERROR -- CONDITION CODE 1 RECEIVED

Explanation: An SIOSC was issued and a condition code (1) that is not valid was received from CIO. The SIOSC macro processor in IPLB segment CCIO should only be returning a condition code of:

System Action: A catastrophic system error is issued.

User Response: The problem may be a logic error in CIO. See your system programmer to check the problem.


00010A

Program: CCNUCL(CICR)

Error Message: INVALID CIOSC FUNCTION CODE

Explanation: The CIOSC macro that was processing was given control with a CIOSC function code that is not valid.

System Action: The entry control block (ECB) is ended.

User Response: Have your system programmer review the system error dump.


000110

Program: Displayed on the console and in the dump.

Error Message: RDLR RETRIEVAL ERROR

Explanation: An error occurred during an attempt to FIND and HOLD the root dynamic load record (RDLR).

System Action: A system error dump is taken and processing is exited.

User Response: Review the system error dump to determine the cause of the FIND error.


000111

Program: CDL6

Error Message: ERROR READING OSTG TAPE

Explanation: An error occurred during an attempt to read from the OSTG tape.

System Action: A system error dump is issued, the RRT section being loaded is marked not in use, and processing is exited.

User Response: Review the system error dump to determine the cause of the error. You can run the load operation again.


000112

Program: CDL2

Error Message: NCB RETRIEVAL ERROR

Explanation: An error occurred during an attempt to retrieve the NCB of a resource.

System Action: A system error dump is issued. Processing continues with the assumption that the resource to be interrogated is active.

User Response: Review the system error dump to determine the cause of the error.


000113

Program: CDL2

Error Message: RRT RETRIEVAL ERROR

Explanation: An error occurred during an attempt to FIND an online resource resolution table (RRT) record. This occurred during the update processing of a dynamic load operation.

System Action: A system error dump is issued, update required is indicated, and processing is exited.

User Response: Review the system error dump to determine the cause of the error. You can run the update operation again.


000114

Program: Displayed on the console and in the dump.

Error Message: FACS ERROR

Explanation: An error occurred while computing a file address.

System Action: A system error dump is issued. If the error occurs during load processing the resource resolution table (RRT) section is marked not in use. If the error occurred during an update or fallback, fallback required is indicated.

User Response: Review the system error dump to determine the probable cause of the error. You can run the failing operation again.


000115

Program: CDL6

Error Message: ERROR READING GDS

Explanation: An error occurred while calculating the file address of the input general data set (GDS) or reading a record from the GDS.

System Action: A system error dump is issued, the RRT section being loaded is marked not in use, and processing is exited.

User Response: Do the following:

  1. Review the system error dump to determine the cause of the error. The load operation must start from the beginning once the GDS error is corrected.
  2. Enter the ZNOPL Load command to restart the load operation.


000116

Program: CDL2

Error Message: RID RETRIEVAL ERROR.

Explanation: An error occurred during an attempt to find an available resource identifier (RID) to assign to an added resource.

System Action: A system error dump is issued, fallback required is indicated, and processing is exited.

User Response: Do the following:

  1. Review the system error dump to determine the cause of the error.
  2. Enter the ZNOPL Update or ZNOPL Fallback commands again to resynchronize the node control blocks (NCBs) with the current network definitions.


000117

Program: CSG4

Error Message: NO NA AVAILABLE TO ASSIGN TO LOCAL RESOURCE, BITMAP CORRUPTED

Explanation: The bitmap used to dispense network addresses to dynamically add resources is corrupted. Restart is unable to assign a network address to a local resource.

System Action: A system error dump is issued.

User Response: Review the system error dump to determine the cause of the error.


000137

Program: CBI0 -- Identify and Directory Maintenance

Error Message: GFND CORRUPTION HAS OCCURRED

Explanation: The count of available entries in the global function name table (GFND) does not match the number of entries available. The DSECT name for the GFND is DCTGFN.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed. The re-IPL process clears this condition.

User Response: None.


000138

Program: CBI0 -- Identify and Directory Maintenance

Error Message: RFND CORRUPTION HAS OCCURRED

Explanation: The count of available entries in the resident function name table (RFND) does not match the number of entries available. The DSECT name for the RFND is DCTRFN.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed. The re-IPL process clears this condition.

User Response: None.


000139

Program: CBI0 -- Identify and Directory Maintenance

Error Message: SSCT CORRUPTION HAS OCCURRED

Explanation: An entry in the system-to-system control table (SSCT) cannot be found for a TPF system that has MPIF users contained in the Global Function Name Directory (GFND). The DSECT names for the SSCT and the GFND are DCTSCT and DCTGFN, respectively.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed. The re-IPL clears the condition.

User Response: None.


00013A

Program: CBK0, CBP0, CBO0, CBO1

Error Message: One of the following:

Explanation: The FACE program detected an error or CBK0 experienced an error while attempting to retrieve a PDR/HDW record. This is a catastrophic system error.

System Action: None.

User Response: Have your system programmer review the system error dump for possible main storage corruption.


00013B

Program: CBH0 -- Directory Management

Error Message: INVALID INPUT TO CBH0

Explanation: Path activation notification or directory update notification was not specified in EBX004.

System Action: The ECB is exited.

User Response: Correct the calling program error.


00013C

Program: CBRS, CBR0 -- MPIF Restart

Error Message: EVENT NOT FOUND

Explanation: The event created by CBRS was not found either by CBR0 trying to post it or by CBRS trying to wait on it.

System Action: A catastrophic system error is issued.

User Response: The problem may be a logic error. See your system programmer to check the error.


00013E

Program: CBX0 -- MPIF Canned Message Driver

Error Message: INVALID CANNED MESSAGE NUMBER PASSED TO CBX0.

Explanation: A canned message number that is not valid was passed to CBX0 by a calling program.

System Action: CBX0 exits.

User Response: Correct the error in CBX0 or the calling program.


00013F

Program: CBH0 -- Directory Management

Error Message: INVALID PARAMETER VALUE INDICATED BY SEND MACRO. CORE CORRUPTION ASSUMED.

Explanation: The return code from the MPIFC SEND macro indicates that parameters that were not valid were passed to it. Storage corruption is assumed.

System Action: A casatrophic system error is issued. The TPF system is re-IPLed. The re-IPL clears the condition.

User Response: None.


000140

Program: CBJ0 -- MPIFC Query Processing

Error Message: ALL MPIF DNT/PAN SLOTS ARE FULL

Explanation: The MPIFC QUERY macro was issued with a request to activate a directory update exit when the requested TPF system or user identifies itself to MPIF or a path activated exit when the requested TPF system connects to this TPF system, thereby providing a logical path between TPF systems. However, the directory update notification table (DNT), when the request was to activate the directory update exit, or the path activated notification table (PAN), when the request was to activate a path activated exit, is full. For example, there are no slots available to add the new exit. The DSECT names for the DNT and the PAN are DCTDNT and DCTPAN, respectively.

System Action: The ECB is exited.

User Response: Do the following:

  1. Review the DNT/PAN.
  2. Increase the DNT/PAN table or update the Multi-Processor Interconnect Facility (MPIF) users not to request as many concurrent notification exits.


000142

Program: CBB0, CBB1

Error Message: NO PACING CREDITS AVAILABLE FOR BROADCAST FUNCTION

Explanation: Broadcast messages are sent across Multi-Processor Interconnect Facility (MPIF) connections that do not use pacing. A MPIFC SEND, however, indicated no available pacing credits for the MPIF connection. Storage corruption is assumed.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed.

User Response: Have your system programmer review the system error dump for possible storage corruption.


000143

Program: CBB0, CBB1, CBW0

Error Message: INVALID PARAMETER VALUE INDICATED BY SEND MACRO. CORE CORRUPTION ASSUMED.

Explanation: The return code from the MPIFC SEND macro indicates that parameters that were not valid were passed to it. Storage corruption is assumed.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed.

User Response: Have your system programmer review the system error dump for possible main storage corruption.


000144

Program: CBB1 -- MPIF Broadcast Update

Error Message: EXCESSIVE NUMBER OF MPIF SEND RETRIES NEEDED.

Explanation: An excessive number of TPF systems cannot be contacted by the Broadcast Update function.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed.

User Response: Have your system programmer review the system error dump.


000146

Program: CBL0, CBL1

Error Message: BAD SDA ADDRESS GIVEN WHEN TRYING TO HALT DEVICE.

Explanation: A halt device was initiated by a MPIF ECB program with a bad SDA.

System Action: Informational dump. Processing is continued in CBLO or CBL1.

User Response: Have your system programmer review the system error dump.


000147

Program: CBU2 -- MPIF Interrupt Processor

Error Message: SDA NOT MOUNTED

Explanation: A symbolic device address (SDA) was deactivated following an I/O or the matching SDA of a pair is inactive.

System Action: Mark the pair of lines as unusable (until the next IPL).

User Response: Have your system programmer review the system error dump.


000148

Program: CBU2 -- MPIF Interrupt Processor

Error Message: NO MPIF PATH FOR MPIF READ OR WRITE

Explanation: Multi-Processor Interconnect Facility (MPIF) post-interrupt is indicated but no logical path is associated with this subchannel.

System Action: Mark the pair of lines as unusable (until the next IPL).

User Response: Have your system programmer review the system error dump.


000149

Program: CBU2 -- MPIF Interrupt Processor

Error Message: MPIF BUFFER ERROR

Explanation: A Multi-Processor Interconnect Facility (MPIF) staging buffer is indicated but the address does not match the MPIF buffers assigned to this link.

System Action: Mark the pair of links as unusable (until the next IPL).

User Response: Have your system programmer review the system error dump.


00014A

Program: CBU0, CBU1, CBU2

Error Message: SDA BUSY -- LOGIC ERROR

Explanation: A command was issued on a link that was already busy.

System Action: Mark the pair of links as unusable (until the next IPL).

User Response: Have your system programmer review the system error dump.


00014B

Program: CBU0, CBU2

Error Message: SIOFC HAS RETURNED CC-1 TO MPIF: LOGIC ERROR

Explanation: Condition code 1 is undefined for SIOFC.

System Action: A catastrophic system error is issued. The TPF system is re-IPLed.

User Response: Have your system programmer review the system error dump.


00014D

Program: CBT1 -- Cross System Startup

Error Message: None.

Explanation: CBT1 received a non T1, T2 or T3 message or a failure occurred on a MPIFC or MSPIC macro.

System Action: CBT1 exits.

User Response: Determine why the CC3088 CSECT is passing an MSRB that is not valid to CBT1 or the cause of the macro failure.


00014F

Program: CBH1 -- Directory Management

Error Message: None.

Explanation: This module was entered with a function code other that SNTU.

System Action: The program is exited.

User Response: Check the interface from the MPIF CSECT for possible MSBR corruption.


000150

Program: CBH1 -- Directory Management

Error Message: None.

Explanation: Directory update or replace message received from a TPF system that is not defined in the system-to-system control table (SSCT). The DSECT name for the SSCT is DCTSCT.

System Action: The program exits.

User Response: Check the SSCT definition, which was initialized from the path definition records (PDR), for possible corruption. The DSECT name for the PDR is CB9PD.


000152

Program: CBM5 -- MPIF Read Post-Interrupt Routine

Error Message: NO CORE BLOCKS AVAILABLE FOR MPIF DEBLOCKING

Explanation: CBM5 copies cross machine messages from the input buffer into MPIF Multisystem request blocks (MSRBs). CBM5 detected that no core blocks were available for Multi-Processor Interconnect Facility (MPIF) to deblock the input buffer.

System Action: After the TPF system issues the system error dump, the disk queues are processed. Then the TPF system performs a software IPL and cycles to 1052 state.

User Response: Review the system error dump to determine why there are no core blocks available.


000156

Program: CBP1, CBG2, CBR2

Error Message: MPIF KEYPOINT E DATA CANNOT BE RECONSTRUCTED

Explanation: The dump is issued after previous messages from CBR2 were issued to further identify the problems.

System Action: MPIF restart is aborted. Multi-Processor Interconnect Facility (MPIF) will not be operational. The TPF system will reach 1052 state with state change disabled

User Response: The messages from CBR2 and the dump must be checked and the cause of the error corrected.


000157

Program: CBR2 -- MPIF Keypoint Recovery

Error Message: MPIF KEYPOINT E DATA RECOVERY COMPLETED

Explanation: The Multi-Processor Interconnect Facility (MPIF) data in keypoint E was reconstructed and an IPL is required to rebuild MPIF control tables by using the update keypoint information.

System Action: The software IPL occurs and CTIN rebuilds the MPIF control tables.

User Response: No action is required at this time. The recovery may have been required due to:


000158

Program: CBM5

Error Message: INVALID MPIF INPUT DATA

Explanation: A data block with a length that was not valid was received by Multi-Processor Interconnect Facility (MPIF).

System Action: The data block is released and the entry is exited.

User Response: Review the system error dump to determine the cause of the error and to correct it.


000180

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: PKST init -- FACE return error

System Action: Skip this record.

User Response: None.


000181

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: PKST Init -- FINW error CCP Table Initialization

System Action: Skip this record.

User Response: None.


000182

Program: Displayed on the console and in the dump.

Error Message: CWAL FACE RETURN ERR FOR SCK

Explanation: SCK FACE Error

System Action: Skip this record.

User Response: The halfword at EBW022 of the ECB in the dump contains the ordinal number in error.


000183

Program: Displayed on the console and in the dump.

Error Message: CWAL FIWH RETURN ERR FOR SCK

Explanation: A SCK FIWHC error occurred.

System Action: The record is skipped.

User Response: The halfword at EBW022 of the ECB in the dump contains the ordinal number in error.


0001A0

Program: CCCCP1(CLWA)

Error Message: None.

Explanation: A communication keypoint error was detected at macro time.

System Action: The program is exited.

User Response: None.


0001A1

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: A communication keypoint error was detected at update time.

System Action: The request is ignored and the program is continued.

User Response: None.


0001A2

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: An illegal communication keypoint intersystem control message was received.

System Action: The program is exited.

User Response: None.


0001C2

Program: Displayed on the console and in the dump.

Error Message: INPUT DATA ERROR -- PROGRAM EXIT

Explanation: There was an error in the input data because of:

System Action: A system error is issued with a return.

User Response: None.


0001C5

Program: CVMA, CWCJ, CWCK, CWCL

Error Message: One of the following:

Explanation: There was a file address compute program (FACE) FIND error while locating a SCK record (or AI Link Error Counts Record -- CVMA, CWCL only).

System Action: A system error is issued with a return.

User Response: None.


0001C6

Program: CVMA

Error Message: INVALID SCK

Explanation: An SCK record that is not valid was found.

System Action: A system error is issued with a return.

User Response: None.


0001C7

Program: CWCL

Error Message: INCORRECT AI ERROR COUNTS RECORD

Explanation: The content of the AI Link Error Counts Record was found to be incorrect. The content of this record may not correspond with the TPF system configuration.

System Action: A system error is issued with a return.

User Response: Do the following:

  1. Check the content of the AI link error counts record.
  2. Make any necessary changes.
  3. Reload.


0001CA

Program: CCDBAF(DBAS)

Error Message: ALTERNATE DISPENSE MODE FILE ADDRESS DECODED

Explanation: A file address was decoded for a record type uniqueness group that had the dump bit set to dump and the file address that was decoded was not in the current dispense format.

System Action: The address is decoded and the dump is issued to inform the user of the condition.

User Response: The dump includes the MIOB (DCTMIO), which contains the name of the program that issued the decode request.


0001D0

Program: CCURSP(CMUE)

Error Message: U/R INVALID ACTIVE IOCB

Explanation: The IOCB address returned is not the active one.

System Action: A catastrophic system error is issued.

User Response: Review the system error dump and the device queue anchored in the unit record status table to determine what the active unit record device should be.


0001D2

Program: CCURSP(CMUE)

Error Message: U/R I/O PROGRAM ERROR

Explanation: An I/O program error (any of bits 40, 41, 42, 43, and 47 of CSW set) occurred for Unit Record (U/R) I/O macros other than the URCTC.

System Action: The entry control block (ECB) is ended.

User Response: Review the system error dump and I/O trace to determine why the channel program ended in error.


0001D3

Program: Displayed on the console and in the dump.

Error Message: ERROR IN FINDING BUFFER TABLE

Explanation: An error occurred while finding the UCSB table.

System Action: The program is exited.

User Response: Review the system error dump and the entry control block (ECB) SUD/SUG fields to determine what error occurred while attempting to read the USCB table segments CUAH(1403) or CUAI(3211).


0001D4

Program: Displayed on the console and in the dump.

Error Message: ERROR ON BUFFER LOAD

Explanation: An error occurred while loading the forms control buffer (FCB) for a 3211 printer.

System Action: The program is ended.

User Response: Review the system error dump and the I/O trace information to determine what error occurred while attempting to load the FCB to the printer.


0001D5

Program: Displayed on the console and in the dump.

Error Message: INVALID ENTRY PARAMETERS

Explanation: A parameter that is not valid was passed to the program.

System Action: The program is ended.

User Response: Review the system error dump and the entry control block (ECB) interface parameters to determine which parameters that were not valid were passed by the calling program.


0001D6

Program: CCURSP(CMUC)

Error Message: U/R $GSVAC CONVERSION ERROR

Explanation: There was an error return taken on $GSVAC while attempting to convert an ECB virtual memory (EVM) address to a system virtual address (SVA).

System Action: The U/R macro request is ended.

User Response: Review the system error dump to determine why the ECB virtual address (EVA) was unable to be successfully converted to a system virtual address (SVA).


0001D7

Program: CCURSP(CMUC)

Error Message: URCTC -- INVALID USER CCW

User Response: Review the system error dump and CCW translation work area information to determine why the CCW translator was unable to translate the user channel program successfully.

Explanation: An error was returned by the CCW translator CCCWTN(CCW11) during URCTC macro processing.

System Action: The U/R macro request is ended.


0001E0

Program: Displayed on the console and in the dump.

Error Message: FACE ERROR ON 3705 RECORD TYPE

Explanation: File address compute program (FACE) error on 3705 records.

System Action: If the record is the 3705 keypoint or the error occurs during a 3705 IPL, the ECB is exited. Otherwise, the record is skipped and processing continues.

User Response: It may be necessary to allocate more file space for 3705 support or the user did not delete previously obsoleted file references.


0001E1

Program: CC3705(CRNP)

Error Message: UNRECOVERABLE I/O ERROR ON 3705

Explanation: CP was detected.

System Action: An error indication is returned to the caller; normally the entry is exited.

User Response: Check the status of the 3705 control unit and correct as necessary; for example, reset or load.


0001E2

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: Received an interrupt from a 3705 control unit not in the 3705 keypoint control unit table. The 3705 keypoint and the 3705 CP status table do not match.

System Action: The entry is exited.

User Response: Correct the table in error.


0001E3

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: FINWC error on 3705 dump programs.

System Action: The entry is exited.

User Response: None.


0001E4

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: There was an unrecognizable use of a dump slot in the 3705 keypoint.

System Action: The slot in error is skipped and processing is continued with the next slot.

User Response: None.


0001E5

Program: Displayed on the console and in the dump.

Error Message: None.

Explanation: There was an FINWC error on dump record during a purge operation.

System Action: The purge of the dump in error is ended.

User Response: None.


0001E6

Program: Displayed on the console and in the dump.

Error Message: TRC REQST I/O ERROR

Explanation: A hardware error or some unusual condition occurred during the execution of a channel program addressed to the 3705 controller over its native subchannel.

System Action: After the dump is taken, control is returned to the interrupt handler.

User Response: None.


0001E7

Program: Displayed on the console and in the dump.

Error Message: TRC REQST TAPE ERROR

Explanation: A hardware error or some unusual condition occurred during the writing of dynamic trace data to the DYN tape.

System Action: Dynamic trace is stopped, and the DYN tape is closed and dismounted.

User Response: Enter End or a new option.


0001E8

Program: Displayed on the console and in the dump.

Error Message: LEID xxxxxx IS UNKNOWN

Explanation: This error occurs when the Logical End-Point Identifier (LEID) is unknown to the WGTA table during the processing of NEF, AX.25, or non data messages.

System Action: The following actions occur based on the type of message:

User Response: Review the TPF outbound path information units (PIUs).


0001F0

Program: CNAH

Error Message: None.

Explanation: CNAH entered CSSB to file the module verification table and found an error.

System Action: A catastrophic system error is issued.

User Response: Check the cause of the file error.

Program: CSSB

Error Message: MVT RETRIEVAL ERROR

Explanation: This message is issued when an error occurs while CSSB is attempting to retrieve the module verification table (MVT). This can be due to:

System Action: A system error dump is issued and processing continues.

User Response: Verify the parameter setup in the call to CSSB for the FIND function. If the error is due to an I/O problem, see your system programmer or your IBM service representative.

Error Message: MVT FILE ERROR

Explanation: This message is issued when an error occurs while CSSB is attempting to file the module verification table (MVT). This can be due to:

System Action: A system error dump is issued and processing continues.

User Response: Verify the parameter setup in the call to CSSB for the FILE function. If the error is due to an I/O problem, see your system programmer or your IBM service representative.

Error Message: FACS ERROR ON MVT PROCESSING

Explanation: This message is issued when an error occurs while CSSB is computing the MVT file address.

System Action: A system error dump is issued and processing continues.

User Response: Verify the parameter setup in the call to CSSB for the FILE/FIND functions on the MVT.

Error Message: INVALID RELATIVE MODULE NUMBER

Explanation: This message is issued when the relative module number used during a FILE or FIND function is not valid.

System Action: A system error dump is issued and processing continues.

User Response: Verify the parameter setup in the call to CSSB for the FILE/FIND functions on the MVT.

Error Message: INVALID DATA LEVEL

Explanation: This message is issued when the data level used during a FILE or FIND function is not valid.

System Action: A system error dump is issued and processing continues.

User Response: Verify the parameter setup in the call to CSSB for the FILE/FIND functions on the MVT.


0001F1

Program: Displayed on the console and in the dump.

Note:
The following messages have the same System Action and User Response.

Error Message: RCSSC RETRIEVAL ERROR

Explanation: The ZBUFC command routines found an error attempting to retrieve the record cache subsystem status table (SSST) header or entry record from file.

Error Message: RCS MOUNT -- RCSSC RETRIEVAL ERROR

Explanation: DASD mount routine CPAB found an error attempting to retrieve the record cache subsystem status table (SSST) header record from file.

Error Message: RCS DISMOUNT -- RCSSC RETRIEVAL ERROR

Explanation: DASD dismount routine CPAI found an error attempting to retrieve the record cache subsystem status table (SSST) header or entry record from file.

Error Message: BAD PARAMETER LIST. NO SSID PASSED OR POINTER TO CURRENT SSID CORRUPTED DURING SEQ SEARCH.

Explanation: The RCSSC macro service routine detected a zero RCS SSID value or an SSST entry address that is not valid in the IDSCS0 parameter list.

System Action: If the error is reported through the RCSSC macro, return is made to the caller with the appropriate return code set in the RCSSC macro parameter list (IDSCS0). If the error is reported through the callers of the RCSSC macro, processing is ended.

User Response: See your IBM service representative to help you determine the cause of the error.


0001F2

Program: Displayed on the console and in the dump.

Note:
The following messages have the same System Action and User Response.

Error Message: RETURN CODE n ON SSST HEADER RETRIEVAL - RESTART ABORTED

Explanation: The RCS restart segment CSS0 found an error while trying to retrieve the record cache subsystem status table (SSST) header record from file. See the RCSSC parameter list for the meaning of the return code n.

Error Message: RETURN CODE n ON FILE OF SSST HEADER - RESTART ABORTED

Explanation: The RCS restart segment CSS0 found an error while trying to file the record cache subsystem status table (SSST) header record. See the RCSSC parameter list for the meaning of the return code n.

Error Message: RETURN CODE n ON SSST FILE BLOCK RETRIEVAL - RESTART ABORTED

Explanation: The RCS restart segment CSS1 found an error while trying to retrieve the record cache subsystem status table (SSST) file ordinal record (#IBMM4). See the RCSSC parameter list for the meaning of the return code n.

Error Message: RETURN CODE n ON SSST HEADER RESTRIEVAL - RESTART ABORTED

Explanation: The RCS restart segment CSS1 found an error while trying to retrieve the record cache subsystem status table (SSST) file ordinal record (#IBMM4) See the RCSSC parameter list for the meaning of the return code n.

Error Message: IEF ERROR -- EVNTC DUPNAM OR EVINC NFOUND BRANCH TAKEN - RESTART ABORTED

Explanation: RCS restart segment CSS1 passed an event name that is not valid on the EVNTC or EVINC marco request.

Error Message: ONE OR MORE DEVICE QUERY ECBs TIMED OUT -- PROCESSING TO CONTINUE

Explanation: RCS restart segment CSS1 has timed out waiting for one or more device query (CSS2) tasks to complete processing.

Error Message: RETURN CODE n ON SSST ENTRY SCAN -- RESTART ABORTED

Explanation: The RCS restart segment CSS1 found an error while trying to scan record cache subsystem status table (SSST) structure. See the RCSSC parameter list for the meaning of the return code n.

Error Message: UNABLE TO RETRIEVE SSST HEADER

Explanation: RCS service routine CSS2, CSS5, CSS6, or CCS7 found an error attempting to retrieve the record cache subsystem status table (SSST) header record from file.

Error Message: UNABLE TO LOCATE SSST ENTRY IN MEMORY

Explanation: The RCS service routine CSS2 found an unrecoverable error while trying to locate an SSST entry in memory.

Error Message: IEF ERROR -- POSTC NFOUND BRANCH TAKEN AGAINST EVENT NAME SUPPLIED BY CALLING PROGRAM

Explanation: The RCS service routine CSS2 passed an event name that is not valid as part of a POSTC macro request.

Error Message: PERMANENT I/O ERROR ON SENSE SUBSYSTEM STATUS FOR DEVICE dddd RCS SSID ssss

Where:

dddd
The device name.

ssss
The RCS device name.

Explanation: The RCS service routine CSS2 found an I/O error while trying to read the status information for an RCS device. If this was the first time the device was sensed by the TPF system, the device is taken offline since the TPF system is unable to determine required RCS control information.

Error Message: ERROR ATTEMPTING TO UPDATE SSST FILE ENTRY

Explanation: RCS service routine CSS2 found an error attempting to update the record cache subsystem status table (SSST) entry record on file.

Error Message: STATUS COMPARE ERROR -- INVALID STATUS OR STATUS LIST OVERFLOW

Explanation: RCS service routine CSS2 found an error attempting to determine the RCS subsystem/device status difference as requested by the RCS state change routine CYEA.

Error Message: INVALID BRANCH VECTOR IN R3

Explanation: A service request vector that is not valid was passed to one of the following:

Error Message: UNABLE TO UPDATE SSST FILE ENTRY

Explanation: The RCS service routine CSS5 found an error while trying to update a record cache subsystem status table (SSST) entry record on file.

Error Message: UNABLE TO RETRIEVE SSST ENTRY FROM FILE

Explanation: The RCS service routine CSS5 found an error while trying to retrieve a record cache subsystem status table (SSST) entry record from file.

Error Message: PERMANENT I/O ERROR ON PERFORM SUBSYSTEM FUNCTION FOR DEVICE dddd RCS SSID ssss

Explanation: The RCS service routine CSS5 found an I/O error while trying to read the cache fast write ID (CFWID) or cache allocation data from RCS subsystem ssss addresses by device dddd.

Error Message: UNABLE TO LOCATE SSST ENTRY IN MAIN STORAGE

Explanation: RCS service routine CSS6 encountered an unrecoverable error while trying to locate an SSST entry in memory.

Error Message: CSS6SCAN ERROR -- RETURN AREA OVERFLOW

Explanation: The RCS service routine CSS6 determined that no room was left to return the message ID information in order to report down-level RCS subsystem or device status conditions.

Error Message: ERROR OCCURRED DURING SEQUENTIAL PROCESSING OF SSST ENTRIES IN MAIN STORAGE

Explanation: The RCS service routine CSS6 found an error while trying to scan the record cache subsystem status table (SSST) structure.

Error Message: ERROR DURING MVT VALIDATION -- RCSSC ERROR ON SSST ENTRY LOOKUP

Explanation: The RCS service routine CSS6 found an error while trying to access the record cache subsystem status table (SSST) during MVT validation request processing.

Error Message: UNABLE TO ACTIVATE CACHING FOR DEVICE dddd RCS SSID ssss

Explanation: The RCS service routine CSS7 encountered an I/O error while trying to activate caching for device dddd attached to RCS subsystem ID ssss.

Error Message: UNABLE TO ACTIVATE DASD FAST WRITE FOR DEVICE dddd RCS SSID ssss

Explanation: The RCS service routine CSS7 found an I/O error while trying to activate DASD fast write for device dddd attached to RCS subsystem ID ssss.

Error Message: UNABLE TO ALLOW ECKD RECORD MODE FOR DEVICE dddd RCS SSID ssss

Explanation: The RCS service routine CSS7 found an I/O error attempting to activate record mode for device dddd attached to RCS subsystem ID ssss.

Error Message: UNABLE TO UPDATE SLOT ALLOCATIONS ON RCS SSID ssss - ERROR ON "MAKE SUBSYSTEM STORAGE UNAVAILABLE"

Explanation: The RCS service routine CSS7 found an I/O error on the make subsystem storage unavailable request while trying to update the cache allocations for RCS subsystem ID ssss.

Error Message: UNABLE TO UPDATE SLOT ALLOCATIONS ON RCS SSID ssss - ERROR ON "SET CACHE SLOT ALLOCATION VALUES"

Explanation: The RCS service routine CSS7 found an error on the Set Cache Slot Allocation Values request while attempting to update the cache allocations for RSC subsystem ID ssss

Error Message: ERROR UPDATING SLOT ALLOCATIONS ON RCS SSID ssss - UNABLE TO MAKE SUBSYSTEM STORAGE AVAILABLE

Explanation: The RCS service routine CSS7 found an I/O error on the Make Subsystem Storage Available request while trying to update the cache allocations for RCS subsystem ID ssss.

Error Message: UNABLE TO ACTIVATE CACHE FAST WRITE ON RCS SSID ssss DUE TO SUBSYSTEM STORAGE MALFUNCTION

Explanation: The RCS service routine CSS7 found an I/O error while trying to activate cache fast write for RCS subsystem ID ssss

Error Message: UNABLE TO ACTIVATE NONVOLATILE STORAGE ON RCS SSID ssss DUE TO NONVOLATILE CACHE MALFUNCTION

Explanation: The RCS service routine CSS7 found an I/O error while trying to activate nonvolatile storage for RCS subsystem ID ssss

Error Message: UNABLE TO MAKE SUBSYSTEM AVAILABLE ON RCS SSID ssss DUE TO SUBSYSTEM STORAGE MALFUNCTION

Explanation: The RCS service routine CSS7 found an I/O error while trying to make subsystem storage available for RCS subsystem ID ssss.

Error Message: ASYNCHRONOUS EVENT TIMEOUT ON RCS SSID ssss - ERROR ON "MAKE SUBSYSTEM STORAGE UNAVAILABLE"

Explanation: The RCS service routine CSS7 found a timeout waiting for an asynchronous event completion notification on the Make Subsystem Storage Unavailable request while trying to update the cache allocations for RCS subsystem ID ssss. Processing continues although the final completion status of the asynchronous request is unknown.

Error Message: ASYNCHRONOUS EVENT TIMEOUT ON RCS SSID ssss - ERROR ON "MAKE SUBSYSTEM STORAGE AVAILABLE"

Explanation: The RCS service routine CSS7 found a timeout waiting for an asynchronous event completion notification on the Make Subsystem Storage Available request while trying to update the cache allocations for RCS subsystem ID ssss. Processing continues although the final completion status of the asynchronous request is unknown.

Error Message: MALOC ERROR ALLOCATING AN SSST CONFLICT CHAIN ELEMENT - RESTART ABORTED

Explanation: RCS Restart processing encountered an SSID entry conflict between the memory and file SSST structures. The system is not the first or only processor in the complex, so RCS Restart attempts to rebuild the memory copy of the SSST structure to be in the same entry sequence as the file structure. The conflict recovery process requires the use of the MALOC service to acquire storage to hold SSST entries temporarily. The MALOC request service call returned an error allocating a storage area. RCS Restart is unable to complete Restart since it is unable to validate the RCS complex. Restart is aborted.

System Action: If the error occurred during processing of an individual RCS or DASD, processing continues on the next RCS. If a hardware error occurred during an attempt to read or write the subsystem status table or if a logic error is detected, the TPF restart scheduler is exited. Portions of the RCS restart program are also activated to service ZBUFC commands. If the error occurred during ZBUFC processing, the ZBUFC command ECB is exited.

User Response: See your IBM service representative to help you determine the cause of the error.


0001F3

Program: Displayed on the console and in the dump.

Note:
The following messages have the same System Action and User Response.

Error Message: ERROR RETURN FROM QASNC MACRO

Explanation: The ZBUFC segment of CACA found an error while trying to create an asynchronous event through the QASNC macro service.

Error Message: ERROR ON QASNC CREATE

Explanation: The RCS service routine CSS7 found an error while trying to create an asynchronous event through the QASNC macro services.

Error Message: ERROR ON QASNC QUERY

Explanation: The RCS service routine CSS7 found an error while trying to query the status of its asynchronous I/O operations through the QASNC macro service.

Error Message: ERROR ON QASNC CLOSE

Explanation: The RCS service routine CSS7 encountered an error while trying to close an asynchronous event through the QASNC macro service.

System Action: The ECB program processing is ended.

User Response: See your IBM service representative to help you determine the cause of the error.


0001F4

Program: CYPO, CYPT

Error Message: None.

Explanation: A ZMCPY function was running but there was an error retrieving keypoint V.

System Action: The ZMCPY function that was running fails.

User Response: See your IBM service representative to help you determine the cause of the error.

See TPF Operations for more information about the ZMCPY commands.


0001F5

Program: CYPO, CYPT

Error Message: None.

Explanation: A ZMCPY function was running but the file status table (FSTB) did not contain the expected information.

System Action: The ZMCPY function fails.

User Response: See your IBM service representative to help you determine the cause of the error.

See TPF Operations for more information about the ZMCPY commands.