Abnormal Condition Messages

ESF995

CHKPTDSx - I/O-ERROR - *** error message ***

Reason:

CA Spool has detected a permanent I/O error on the CHKPTDSx checkpoint data set. *** error message *** is the error description provided by the MVS SYNAD routines. CA Spool is terminated with an error-reason code.

Action:

Save the dump output, then restart CA Spool.

ESF996

I/O-ERROR - *** error message ***

Reason:

CA Spool has detected a permanent I/O error on one of its spool data sets. *** error message *** is the error description provided by the MVS SYNAD routines. CA Spool is terminated with an error-reason code.

Action:

Save the dump output, then restart CA Spool.

ESF997

CHECKPOINT WAS IN PROCESS, CHECKPOINT DATA MAY BE INVALID

Reason:

CA Spool has abended, but the termination routines detected that a checkpoint was in process, and the information in the checkpoint data set may therefore be invalid. Termination continues.

Action:

If CA Spool rejects a restart, notify the systems programmer.

ESF998

CATASTROPHIC ERROR, ESTAE IN CONTROL

Reason:

A system abend has occurred in CA Spool. CA Spool has entered its recovery routines, and will initiate a termination of the system, and produce a dump.

Action:

Restart ESF if possible, or notify the systems programmer. Report the failure and save the dump output.

ESF999

DISASTROUS ERROR, ERROR-CODE = xxxx

Reason:

CA Spool has discovered an incorrectable error in the system.

The following error codes may occur:

ABND—An ABEND command has been entered
ACT1—A disastrous error occurred during activity process
ALL0—The track-allocation routine has detected an invalid track‑allocation‑map control block
ASM0—No message sequence number could be assigned to a command buffer
BFR0—A getbuf request failed. Invalid buffer type specified
BFR1—A freebuf request failed. Invalid buffer type specified
BFR2—A freebuf request failed. Buffer already on free buffer queue
CCW0—A request to build a channel program has been rejected because the extent in the MTTR address is invalid
CCW1—A request to build a channel program has been rejected because the request was not valid
CKP0—A checkpoint request is being processed, but the requester did not have exclusive access to the file queue
CH00—Unexpected I/O interrupt (ESFUNC). The checkpoint data set lock is held by an unknown system (ESFCKPT)
CH01—Permanent I/O error on checkpoint data set
CH02—Unable to find checkpoint-processor PCB to be dispatched
CH03—The checkpoint-processor PCB was not on the wait queue
CH04—The checkpoint-processor PCB was not on the I/O wait queue
CH05—A checkpoint I/O request has been rejected because the checkpoint data set SCB is in the BUSY state; that is, a previous checkpoint has not been completed
CH06—The warm start routine in the checkpoint processor has detected an open-file count below zero
CH07—Unable to start because the file queue could not be rebuilt
DISP—PCB must complete, support failed
ESTA—The VTAM interface subtask was unable to establish an ESTAE recovery environment
FREM—A FREEMAIN of virtual storage request failed
GENA—The VTAM interface subtask was unable to generate an VTAM ACB
GETM—An unconditional GETMAIN of virtual storage request failed
IDX1—The name index initialization failed
IDX2—The name index termination failed
INT1—Duplicate node or alias name found during initialization of table index
INT2—Allocated FBA checkpoint data set too small for the current setup
INT3—Internal error, invalid #ICEREQ call
INT4—Initialization of the node name index failed
IO01—An attempt to start a channel program has been rejected because the extent value was not valid
IO02—Unexpected I/O interrupt
IO03—Unable to determine the cause of the I/O interrupt
IO04—Permanent I/O error on a spool data set
IO05—Unable to find PCB to be dispatched
IO06—PCB to be dispatched for the I/O interrupt was not waiting for I/O to complete
IVSQ—An undefined security request code was passed to the ESFSECU5 security user exit
LKN1—Invalid $IQLKPNM request received.
NET1—The active-session-count field dropped below zero
NET2—A disastrous error has occurred in the network interface
NET3—The outstanding receive-request-count field dropped below zero
NET4—The getbuffer routine returned a buffer already on receive-any-queue
NJE1—Duplicate NJE node name found during initialization
NJE2—An undefined function code was passed to the #NJEINIT routine
PR01—An internal error has occurred in a printer node's command-request handler
PRG0—A track-allocation-map control block has been detected in error by the purge processor
SAF1—An unrecoverable error has occurred in the SAF interface
SAV1—Subtask save area invalid
SAV2—No room in save area
TRK0—An invalid UTAM spool block was passed to $TRACK
UCH1—A user ID index release failed
UIX1—Add user ID to user index failed
UIX2—Remove user ID from user index failed
UIX3—Find user ID in user index failed
WAI1—An internal #WAIT request was issued where R13 did not contain the address of the current processor control block
XEQ0—A track-allocation map-control block has been detected invalid
XEQ1 —The open file count has been reduced to a negative value
XEQ2—A user track-allocation map-control block has been detected invalid during an output (write) operation
XEQ3—XEQ processor could not obtain storage
XES1—Read of CKPT Master record from Coupling Facility failed
XES2—Write of CKPT Master record to Coupling Facility failed
XES3—Disconnect from Coupling Facility failed
XFQ1—Internal error in the file-index look-up routine #XFQELKUP
XFQ2—Internal error in the file-index update routine #XFQEUPDT
XFR1—An invalid FQE address has been passed to the file-transfer completion routine

CA Spool will initiate a termination with a user abend 0001 and a dump.

Action:

Restart ESF if possible, or notify the systems programmer. Report the failure and save the dump output.