About this book

 

This book lists all the user messages and abend reason codes returned by WebSphere MQ for z/OS, with explanations and suggested responses. It is designed for use as a quick reference, and is linked with the WebSphere MQ for z/OS Problem Determination Guide, which you should also consult if a message indicates that there is a WebSphere MQ problem.

 

Who this book is for

This book is for system operators, system programmers, and anybody else who needs to understand and respond to WebSphere MQ user messages.

 

What we need to know to understand this book

We can refer to this book for the meaning of a message without understanding the book as a whole. However, you should understand the types of message WebSphere MQ produces, the different places to which it sends these messages, and the different audiences they are intended to reach.

 

Terms used in this book

In this book, CICS means both Transaction Server for z/OS and CICS for MVS/ESA, and IMS means IMS/ESA, unless otherwise stated.

In this book, z/OS means any release of z/OS or OS/390 that supports the current version of WebSphere MQ.

Only WebSphere MQ Script (MQSC) commands are normally mentioned in this book. The equivalent PCF command can be used instead of an MQSC command. See the WebSphere MQ Programmable Command Formats and Administration Interface book.

 

How to use this book

When you are using WebSphere MQ and we need to understand a message or code, use this book as a reference. The book is divided into the following parts:

Messages

Describes all WebSphere MQ messages in alphanumeric order.

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

The fourth character is the component identifier; this identifies the component of WebSphere MQ that issued the message. These are shown in Appendix C. WebSphere 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 WebSphere MQ for z/OS.

Table 1. Message type codes
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.

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 WebSphere 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.

Codes

Describes all WebSphere 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 WebSphere MQ component. These are shown in Appendix C. WebSphere MQ component identifiers. The last two bytes are the numeric identifier, which is unique within the component.

WebSphere MQ CICS abend codes

Describes the CICS abend codes issued by the WebSphere MQ CICS adapter, and the WebSphere 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.

The book also contains the following information in appendixes:

 

WebSphere MQ system completion codes

WebSphere MQ uses two system completion codes:

X'5C6'

This code indicates that WebSphere MQ has detected an internal error, and has terminated a WebSphere MQ internal task, or a user-connected task, abnormally. Errors associated with an X'5C6' system completion code might be preceded by a z/OS system code, or by internal errors.

To determine the source of the error that resulted in a subsequent task or queue manager termination, examine the diagnostic material generated by the X'5C6' abend.

X'6C6'

This code indicates that WebSphere MQ has detected a severe error, and has terminated the entire WebSphere MQ queue manager abnormally. During such termination, a user task with an active WebSphere MQ connection can be ended abnormally with an X'6C6' system completion code; in rare instances, the entire connected address space might end abnormally.

When this abend code is issued, WebSphere MQ has determined continued operation could result in the loss of data integrity. Errors associated with an X'6C6' abend completion code might be preceded by a z/OS system error, or by one or more WebSphere MQ X'5C6' abend completion codes.

For information about the system actions, and diagnostic information available to WebSphere MQ following one of these completion codes, refer to the description of the reason code associated with the system completion code in Codes, starting on page Codes. This reason code is shown in the various messages that appear on the z/OS console in connection with the abnormal termination; for example an X'6C6' completion code is usually accompanied by message CSQV086E. In many cases, you will be advised to contact your IBM Support Center to report the problem; see the WebSphere MQ for z/OS Problem Determination Guide for information about how to do this.

Note:
If the queue manager has terminated, we can restart it, even if there is a problem to be reported to the IBM Support Center. Similarly, if a component of the queue manager (such as the channel initiator) has terminated, we can restart that component.

 

Message routing codes

The majority of WebSphere MQ messages sent to the console have routing codes determined by the ROUTCDE parameter of the CSQ6SYSP macro. (See the WebSphere MQ for z/OS System Setup Guide for information about using this macro.) However, some WebSphere MQ messages are issued with a fixed routing code. These include messages that require an immediate response and messages issued by early initialization procedures. Messages sent in direct response to commands (other than START QMGR and STOP QMGR) are sent to the console or program that issued the command.

Messages issued by the WebSphere MQ CICS adapter and the CICS distributed queuing component use the default route code of your CICS system.

Most messages issued by the security manager are routed back to the person who issued the command (provided that they have the correct authority).