Introduction to Messages

This section describes the various printer, console, and TSO messages that may be output by BMC’s FDR product line and the various abend codes that the programs may terminate with.

Message

Description

FDR message format

Except for FDRREORG and FDRCPK, messages from all components of FDR have this format:

FDRnnn[**]

message-text

Explanation: Where “nnn” is a 3-digit message number. When “FDRnnn” is followed by a double asterisk (**), the message usually indicates some error that may result in an abend or a non-zero return code. Messages without the asterisks are usually informational. These messages are described in:

Messages directed specifically to the z/OS console or TSO user will have this format:

FDRWnn

message-text

Explanation: Some of these messages require replies by the z/OS operator or TSO user. See FDR-Console-Messages-and-TSO-Terminal-Messages. However, other “FDRnnn” messages may also be sent to the z/OS console or TSO user.

CPK message format

The general format of COMPAKTOR messages is as follows:

CPKnnns

message-text

Explanation: Where “nnn” is a 3-digit message number and “s” is a severity code:

  • I - Informative message.
  • A - Action required message.
  • W - Warning message. May result in abnormal termination.
  • E - Error message. Always results in abnormal termination.

Some of these messages may also be issued to the z/OS console. COMPAKTOR also produces “FDRnnn” messages for some conditions. See COMPAKTOR Messages (CPKnnnxx).

FDRREORG message format

The general format of FDRREORG messages is:

FDRRnn[*|**]

message-text

FDRSnn[*|**]

message-text

Explanation: Where “nn” is a 2-digit message number. If the message number is followed by a single asterisk (*) this is a warning message, while if it is followed by a double asterisk (**) it is an error message. See Messages (FDRRnn & FDRSnn).

Return codes

FDR sets a return code at the end of the step, unless it abends:

00

Normal completion.

Any other return code

Explanation: Errors of some kind have occurred during this execution. Check the listing for the error messages. This usually indicates that errors occurred that were not severe enough to terminate the FDR operation, yet the program wants to call attention to the error messages at the end of processing. Severe errors usually result in an immediate abend.

You can control whether FDR programs set a return code or issue an U0888 abend for non-terminating errors. See the options FDRCC, CPKCC, and ABRCC. By default, FDR and COMPAKTOR issue an U0888 abend and ABR sets a return code 12.

Abend Codes

FDR user abend codes range from U0100 to U0999. See ABEND-Codes. Most user abends are preceded by an FDR error message.

Important

User abend U0888 is a special case. It is issued by FDR programs to indicate that errors occurred that were not severe enough to terminate the FDR operation, yet the program wants to call attention to the error messages at the end of processing. Severe errors usually result in an immediate abend.

You can control whether FDR programs set a return code or issue an U0888 abend for non-terminating errors;  See the options FDRCC, CPKCC, and ABRCC. By default, FDR and COMPAKTOR issue an U0888 abend and ABR sets a return code 12.

Wait state codes

The Stand Alone Restore (SAR) program may put the CPU in a WAIT STATE if errors occur and it is not able to display a message to the operator, for example, errors that occur before the console has been initialized. SAR loads a meaningful code in the instruction address field of the PSW (last four digits); these codes are documented in Wait-State-Codes-from-SAR. The procedures for displaying the PSW vary by CPU type; consult the hardware documentation for your CPU for details.

Mini-dump

In many cases, an error message is followed by a set of diagnostic displays, called an FDR mini-dump. Each message description indicates if a mini-dump is printed. The mini-dump includes:

  • The general registers at the time of the mini-dump. These may or may not be significant, depending on the error.
  • Blocks of storage identified by the FDR program requesting the mini-dump. These usually have a title above them for identification. The storage displayed varies depending on the error message.
  • For I/O errors, it displays the DCB, UCB, and IOB. The IOB contains:

Bytes 2-3

Sense bytes 0-1.

Byte 4

I/O termination post code (7F = normal termination).

Bytes 8-15

Hardware-generated Channel Status Word (CSW), see the IBM z/Architecture Principles of Operation (SA22-7832) manual, consisting of:

Bytes 8-11

Address of last CCW executed +8.

Bytes 12-13

Channel status flags.

Bytes 14-15

Remaining length in last CCW (CCW length field minus this gives bytes transferred).

  • It also formats the CCW chain executed. CCW(-0) identifies the last CCW executed.

I/O errors and traces

For most I/O errors, FDR formats information about the error in a condensed format that includes:

  • The I/O request Block (IOB) as described above.
  • The CCW chain (four CCWs per line in most cases).
  • Up to eight bytes of data associated with each CCW (16 or 20 bytes for certain CCWs). The lines containing the data alternate with the lines containing the CCWs, so that the data for each CCW is immediately below the CCW itself.

BMC Support may request that you add operands to your control statements that trace all I/Os issued by FDR. This same format is used for those traces.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*