gtpo1mhcOperations

Messages

This section provides information about the DOF error messages.

Error Messages

USER ABEND 1111

Explanation: This is an input parameter error that can occur when you specify TV or RS in the JCL EXEC statement. See Specifying DOF Options in the JCL EXEC Statement for more information.

USER ABEND 1112

Explanation: This is an input parameter error that can occur when you specify whether or not you want STPP options (Y or N) in the JCL EXEC statement. See Specifying DOF Options in the JCL EXEC Statement for more information.

USER ABEND 1113

Explanation: This is an input parameter error that can occur when you specify the processing options in the JCL EXEC statement. See Specifying DOF Options in the JCL EXEC Statement for more information.

USER ABEND 2000

Explanation: This error occurs when the trace control table or the trace count output table contains an incorrect logical record length.

The logical record length specified determines how real-time trace (RTT) output is formatted, based on the TPF model or release number, to account for SVC mnemonic differences between TPF releases.

USER ABEND 2222

Explanation: There is a permanent I/O error on the tape. The SYNAD error analysis routine is entered.

USER ABEND 2999

Explanation: A volume sequence error was detected while postprocessing a multivolume dump. An error message is written to the system printer before the ABEND occurred. See Messages (System Error and Offline) and Messages (Online) for more information about specific errors.

USER ABEND 3333

Explanation: A bad communication control program (CCP) trace record was encountered. The record contains the CT record identifier, but there is no data in the record. The CCP trace cannot be post processed. Run the post processor without the CCP trace (CP) option to process other records that may be on the tape.

USER ABEND 3999

Explanation: An SVC index is not valid. A CFISVC macro could not decode an SVC index. This may be caused by a back-level macro table in CCMCDC.

Note:
To receive standard MVS dumps for all ABENDs, code the SYSUDUMP or SYSABEND data definition cards for the JCL; for example:
//SYSUDUMP  DD  SYSOUT=A