IBM MQ for z/OS messages, completion, and reason codes

Use this topic to interpret and understand the messages and codes issued by IBM® MQ for z/OS®.

The information in this topic can be used to understand a message or code produced by the IBM MQ for z/OS product. The topic is divided into the following parts:

Messages for IBM MQ for z/OS

Describes all IBM MQ messages in alphanumeric order.

All IBM MQ message identifiers are eight characters long. The first three characters are always CSQ. If you get a message with a different prefix, find out which product issued the message. See Messages from other products.

The fourth character is the component identifier; this identifies the component of IBM MQ that issued the message. These are shown in IBM MQ component identifiers. The fifth through seventh characters represent the numeric identifier, which is unique within the component. The last character is the message type code; this indicates the type of response that the message requires. Table 1 shows the four type codes used by IBM MQ for z/OS.

Table 1. Message type codes
Type code	Response type	Response required
A	Immediate action	System operator action is required immediately. The associated task does not continue until the requested action has been taken.
D	Immediate decision	System operator decision or action is required immediately. The operator is requested to select from specific options, such as retry or cancel. The associated task does not continue until the requested decision has been made or action has been taken.
E	Eventual action	System operator action will be required; however, the associated task continues independently of system operator action.
I	Information only	No operator action is required. However, certain messages may be significant - please review Console message monitoring for further information.

In messages issued by the queue manager itself and the mover, the message identifier is normally followed by the command prefix (CPF); this indicates which IBM MQ queue manager issued the message. These messages have prefixes starting CSQE, CSQH, CSQI, CSQM, CSQN, CSQP, CSQR, CSQV, CSQX, CSQY, CSQ2, CSQ3, CSQ5, and CSQ9; some messages with prefixes CSQJ and CSQW also have the CPF. In certain exceptional cases, the CPF might show as blank.

Messages from CICS®-related components (CSQC) show the CICS application ID or transaction ID if applicable.

Messages from other components, that is messages with prefixes CSQO, CSQQ, CSQU, and CSQ1 (and some with prefixes CSQJ and CSQW) have no indicator.

IBM MQ for z/OS codes

Describes all IBM MQ abend reason codes, and subsystem termination reason codes, in alphanumeric order.

The codes are four bytes long. The first byte is always 00; this is the high-order byte. The second byte is the hexadecimal identifier (Hex ID) of the IBM MQ component. These are shown in IBM MQ component identifiers. The last two bytes are the numeric identifier, which is unique within the component.

IBM MQ CICS adapter abend codes and IBM MQ CICS bridge abend codes

Describe the CICS abend codes issued by the IBM MQ CICS adapter, and the IBM MQ CICS bridge.

Accompanying each message and code is the following information, when applicable:

Explanation:

This section tells what the message or code means, why it occurred, and what caused it.

Severity:

Severity values have the following meanings:

0: An information message. No error has occurred.
4: A warning message. A condition has been detected of which the user should be aware. The user might need to take further action.
8: An error message. An error has been detected and processing could not continue.
12: A severe error message. A severe error has been detected and processing could not continue.

System action:

This part tells what is happening as a result of the condition causing the message or code. If this information is not shown, no system action is taken.

User response:

If a response by the user is necessary, this section tells what the appropriate responses are, and what their effect is. If this information is not shown, no user response is required.

Operator response:

If an operator response is necessary, this section tells what the appropriate responses are, and what their effect is. If this information is not shown, no operator response is required.

System programmer response:

If a response by the system programmer is required, this part tells what the appropriate responses are, and what their effect is. If this information is not shown, no system programmer response is required.

Programmer response:

If a programmer response is necessary, this part tells what the appropriate responses are, and what their effect is. If this information is not shown, no programmer response is required.

Problem determination:

This section lists the actions that can be performed to obtain adequate data for support personnel to diagnose the cause of the error. If this information is not shown, no problem determination is required.