IBM MQ messages on Multiplatforms

IBM MQ diagnostic messages are listed in this section in numerical order, grouped according to the part of IBM MQ from which they originate.

Note: If a message is specific to a single platform, this is indicated after the message identifier. Although some messages are listed several times, each instance relates to a different platform. If present, the version common to a number of platforms is listed first, followed by versions for individual platforms. Ensure that you read the appropriate version.

• AMQ3xxx: Utilities and tools
• AMQ4xxx: User interface messages (Windows and Linux systems)
• AMQ5xxx: Installable services
• AMQ6xxx: Common services
• AMQ7xxx: IBM MQ product
• AMQ8xxx: Administration
• AMQ9xxx: Remote

Reading a message

The following information is provided for each message:

Message identifier

The message identifier is in three parts:

1. The characters "AMQ", which identify the message as being from IBM MQ
2. A four-digit decimal code
3. A suffix letter, indicating the severity of the message (I, W, E, S or T). See the following severity list.

   For more information about message suffix letters, see AMQ_DIAGNOSTIC_MSG_SEVERITY.

For Long Term Support, and for Continuous Delivery releases earlier than Version 9.0.3, the message identifiers do not show the suffix letter when displayed in the product.

Message text

A summary of the message

Severity

0: Informational
10: Warning
20: Error
30: Error
40: Severe
50: Terminating


Explanation

An explanation of the message giving further information.

Response

The response required from the user. In some cases, particularly for information messages, this might be "No action is required".

Message variables

Some messages display text or numbers that vary according to the circumstances giving rise to the message; these are known as message variables. The message variables are indicated as <insert_1>, <insert_2>, and so on.

In some cases a message might have variables in the Explanation or Response. Find the values of the message variables by looking in the error log. The complete message, including the Explanation and the Response, is recorded there.