Amqzao05 PDF

WebSphere MQ
Messages
GC34-6601-00
WebSphere MQ
Messages
GC34-6601-00
Note!
Before using this information and the product it supports, be sure to read the general information under “Notices,” on page
361.
First edition (May 2005)

This edition of the book applies to the following products:
v IBM WebSphere MQ for AIX, Version 6.0
v IBM WebSphere MQ for HP-UX, Version 6.0
v IBM WebSphere MQ for iSeries™, Version 6.0
v IBM WebSphere MQ for Linux for Intel, Version 6.0
v IBM WebSphere MQ for Linux for zSeries, Version 6.0
v IBM WebSphere MQ for Solaris, Version 6.0
v IBM WebSphere MQ for Windows, Version 6.0
and to any subsequent releases and modifications until otherwise indicated in new editions.
This book is based on the Messages book for WebSphere MQ Version 5.3, GC34-6057-01.
© Copyright International Business Machines Corporation 1997, 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this book . . . . . . . . . . . v Chapter 5. 7000-7999 - MQSeries
UNIX systems . . . . . . . . . . . . . . v product . . . . . . . . . . . . . . 79
Who this book is for . . . . . . . . . . . . v
How to use this book . . . . . . . . . . . v Chapter 6. 8000-8999 - Administration 133
Summary of changes . . . . . . . . vii Chapter 7. 9000-9999 - Remote . . . . 203
Chapter 1. Finding and reading a Chapter 8. API completion and reason
message . . . . . . . . . . . . . . 1 codes . . . . . . . . . . . . . . . 253
Finding a message . . . . . . . . . . . . 1
Completion codes . . . . . . . . . . . . 253
Reading a message . . . . . . . . . . . . 1
Reason codes . . . . . . . . . . . . . 253
Message information. . . . . . . . . . . 1
Reason code list . . . . . . . . . . . 254
Message variables . . . . . . . . . . . 2
Reason code cross reference . . . . . . . 321
Chapter 2. 4000-4999 - User interface Chapter 9. PCF reason codes . . . . 329

messages (WebSphere MQ for Windows Reason codes . . . . . . . . . . . . . 329
and Linux systems) . . . . . . . . . . 3 Reason code cross reference . . . . . . . 354
WebSphere MQ Explorer messages . . . . . . . 3
Other user interface messages . . . . . . . . 23 Chapter 10. Secure Sockets Layer
4200-4217 - WebSphere MQ Default
(SSL) return codes . . . . . . . . . 359
Configuration . . . . . . . . . . . . 23
4235-4238 - Prepare WebSphere MQ Wizard . . 25
4250-4274 - ’Postcard’ messages . . . . . . . 26 Appendix. Notices . . . . . . . . . 361
4300-4309 - WebSphere MQ API Exerciser . . . 29 Trademarks . . . . . . . . . . . . . . 363
4350-4764 - Installation messages . . . . . . 30
Sending your comments to IBM . . . 365
Chapter 3. 5000-5999 - Installable
services . . . . . . . . . . . . . . 37
Chapter 4. 6000-6999 - Common

services . . . . . . . . . . . . . . 63
© Copyright IBM Corp. 1997, 2005 iii

iv WebSphere MQ Messages
About this book
This book describes the user messages returned by WebSphere® MQ, with
explanations and suggested actions. It is designed for use as a quick reference.
UNIX systems
In this book, references to “UNIX systems” include:
AIX®
HP-UX
Linux™
Solaris
References to WebSphere MQ for UNIX® systems include:

WebSphere MQ for AIX, V5.3
WebSphere MQ for HP-UX, V5.3
WebSphere MQ for Linux for Intel™, V5.3
WebSphere MQ for Linux for zSeries®, V5.3
WebSphere MQ for Solaris, V5.3
Who this book is for

The information is intended for system operators, system programmers, and
anyone who needs to understand and take action in response to WebSphere MQ
user messages.
How to use this book

See Chapter 1, “Finding and reading a message,” on page 1.
© Copyright IBM Corp. 1997, 2005 v

vi WebSphere MQ Messages
Summary of changes
Changes for this edition (GC34-6601-00) of WebSphere MQ Messages:
v New messages have been included for functions added for WebSphere MQ V6.0
v Existing messages have been updated to include new functions, and information
added for existing functions.
© Copyright IBM Corp. 1997, 2005 vii

Changes
viii WebSphere MQ Messages

Chapter 1. Finding and reading a message
WebSphere MQ user messages are numbered AMQ4000 through AMQ9999, and
they are listed in this book in numeric order. However, not all numbers have been
used, and therefore the list is not continuous.
Finding a message
WebSphere MQ messages are grouped according to the part of WebSphere MQ
from which they originate:
Chapter 2, “4000-4999 - User interface messages (WebSphere MQ for Windows
and Linux systems),” on page 3
Chapter 3, “5000-5999 - Installable services,” on page 37
Chapter 4, “6000-6999 - Common services,” on page 63
Chapter 5, “7000-7999 - MQSeries product,” on page 79
Chapter 6, “8000-8999 - Administration,” on page 133
Chapter 7, “9000-9999 - Remote,” on page 203
The return codes for the WebSphere MQ programming interface, the MQI, are
shown in tabular form in Chapter 8, “API completion and reason codes,” on page
253.
Reading a message
The format of a WebSphere MQ user message is:
v The message identifier, in two parts:
1. The characters ‘AMQ’ which identify the message as being from WebSphere
MQ
2. A four-digit decimal code
If a message is specific to a single platform, this is indicated after the message
identifier. In some cases, an identifier might be listed several times, but each
instance will relate to a different platform. Ensure that you read the appropriate
version.
If there is a version of the message common to all the remaining platforms, this
is listed first, followed by the platform-specific versions.
v The text of the message
Message information
For each message, this information is provided:
Severity
The level of severity of this message.
Explanation
Further explanation of why the message was issued.
Response
Actions that you should take in response to the situation that caused the
message.
© Copyright IBM Corp. 1997, 2005 1

Finding and reading
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 in this book 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.
2 WebSphere MQ Messages
Chapter 2. 4000-4999 - User interface messages (WebSphere
MQ for Windows and Linux systems)
See “Reading a message” on page 1 for an explanation of how to interpret these
messages.
The majority of messages in this numerical range come from WebSphere MQ

Explorer. These are listed in the section which follows. Several other groups of
messages are listed separately at the end:
v “4200-4217 - WebSphere MQ Default Configuration” on page 23
v “4235-4238 - Prepare WebSphere MQ Wizard” on page 25
v “4250-4274 - ’Postcard’ messages” on page 26
v “4300-4309 - WebSphere MQ API Exerciser” on page 29
v “4350-4764 - Installation messages” on page 30
WebSphere MQ Explorer messages
AMQ4000 New object not created because the AMQ4003 WebSphere MQ system objects are used
default object for the object type could internally by WebSphere MQ. You are
not be found. advised not to delete them. Do you
want to keep the WebSphere MQ
Severity: 10 : Warning
system object?
Explanation: The creation of an object requires a
Severity: 0 : Information
default template for each object type. The required
default template for this object type could not be Explanation: A confirmation is required before an
found. internal WebSphere MQ system object (for example
SYSTEM.DEFAULT.LOCAL.QUEUE) is deleted.
Response: Determine why the default object is not
available, or create a new one. Then try the request Response: Continue only if you want to permanently
again. delete the system object.
AMQ4001 The queue manager specified is already AMQ4004 Clear all messages from the queue?
shown in the console.
Explanation: The removal of the messages from the
Response: Message for information only. queue is an irreversible action. If the command is
allowed to proceed the action cannot be undone.
AMQ4002 Are you sure you want to delete the Response: Continue only if you want to permanently
<insert_0> named <insert_1>? delete the messages.
AMQ4005 The object has been replaced or deleted.
Explanation: A confirmation is required before the
The properties could not be applied.
specified object is deleted. The type of object and name
are provided in the message. Severity: 10 : Warning
Response: Continue only if you want to permanently Explanation: During the process of updating the
delete the object. properties of the object, it was determined that the
object has either been deleted or replaced by another
instance. The properties have not been applied.
AMQ4006 WebSphere MQ successfully sent data

to the remote queue manager and

4000-4999 - User interface messages
received the data returned.

AMQ4012 The object was created successfully but
Severity: 0 : Information it is not visible with the current settings
for visible objects.
Explanation: An open channel has been successfully
verified by WebSphere MQ as the result of a user Severity: 0 : Information
request.
Response: Message for information only.
AMQ4014 The character <insert_0> is not valid.
AMQ4007 The message sequence number for the
channel was reset.
AMQ4015 Supply a non-blank name.
Explanation: A channel has had its sequence number
successfully reset by WebSphere MQ as the result of a
user request. Response: Enter a valid name.
AMQ4016 The test message was put successfully.
AMQ4008 The request to start the channel was Severity: 0 : Information
accepted.
Explanation: The request to place a message on the
Severity: 0 : Information target queue has completed successfully. The queue
now contains the message.
Explanation: A channel has been started successfully
by WebSphere MQ as the result of a user request. Response: Message for information only.
AMQ4019 An object called <insert_0> already
exists. Do you want to replace the
AMQ4009 The request to stop the channel was
definition of the existing object?
accepted.
Response: Confirm that you want to replace the
Explanation: A channel has been stopped successfully
definition.
by WebSphere MQ as the result of a user request.
AMQ4020 The changes you are making to the
attributes of page ″<insert_0>″ will affect
AMQ4010 The ’in-doubt’ state was resolved. the operation of the queue manager or
another program currently using the
Severity: 0 : Information object. Do you want to force the change
Explanation: A channel has had its ’in-doubt’ state to the object’s attributes?
resolved successfully by WebSphere MQ as the result of Severity: 10 : Warning
a user request.
Explanation: You are trying to change a object that
Response: Message for information only cannot be changed because the object is in use, or the
change will affect other programs or queue managers.
AMQ4011 The queue has been cleared of Some changes can be forced anyway.
messages. Response: Select Yes to try forcing the changes, or No
Severity: 0 : Information to abandon the change.
Explanation: The CLEAR command completed

successfully and has removed all messages from the AMQ4021 Failed to access one or more WebSphere
target queue. If the CLEAR was performed using the MQ objects.
MQGET API command, uncommitted messages might Severity: 10 : Warning
still be on the queue.
Explanation: The objects’ icons have been marked to
indicate the objects in error.
be resolved later. Select No if you want to correct the

AMQ4022 The name specified for the initiation
problem now and try again.
queue is the same as the name of the
queue itself.
AMQ4028 Platform not supported. This queue
manager cannot be administered by the
Response: Specify a different name to that of the WebSphere MQ Explorer because it is
object being created or altered. running on an unsupported platform.
The value <insert_0> for the Platform
attribute of the queue manager is not
AMQ4023 The queue manager <insert_0> does not
supported by the WebSphere MQ
exist on this computer.
Explorer.
Severity: 20 : Error
AMQ4029 Command level too low. This queue
AMQ4024 The object cannot be replaced. manager cannot be administered by the
WebSphere MQ Explorer because the
Severity: 0 : Information command level of the queue manager is
Explanation: The request to replace the object was less than <insert_0>.
unsuccessful. Severity: 20 : Error
Response: To define this object, delete the existing Response: If you want to administer this queue
object and try the operation again. manager, you must upgrade it to a newer version of
WebSphere MQ.
AMQ4025 The changes made to the cluster
attributes of the queue will take effect AMQ4030 Queue manager cannot be administered
once they have propagated across the because codepage conversion table not
network. found.
Severity: 0 : Information Severity: 20 : Error
Response: Refresh any views containing the cluster Explanation: This queue manager cannot be
queues in the affected clusters to show the changes. administered by the WebSphere MQ Explorer because a
codepage conversion table was not found.
AMQ4026 You have created a queue which is Response: Install a codepage conversion table from
shared in one or more clusters. The CCSID <insert_0> to CCSID <insert_1> on the computer
queue will be available as a cluster on which the WebSphere MQ Explorer is running.
queue once its definition has
propagated across the network.
AMQ4031 Queue manager cannot be administered
Severity: 0 : Information because CCSID not found.
Response: Refresh any views containing the cluster Severity: 20 : Error
queues in the affected clusters to show the cluster
queue. Explanation: This queue manager cannot be
administered by the WebSphere MQ Explorer because
CCSID <insert_0> cannot be found in the CCSID table.
AMQ4027 An error occurred connecting to the The WebSphere MQ Explorer cannot convert character
queue manager. Are you sure you want data to or from the unrecognized CCSID.
to show this queue manager in the
folder anyway?
AMQ4032 Command server not responding within
Severity: 10 : Warning timeout period.
Explanation: A connection could not be made to the Severity: 10 : Warning
specified remote queue manager.
Response: Ensure that the command server is running
Response: Ensure that the named queue manager is and that the queue called
running on the host and port specified, and has a ’SYSTEM.ADMIN.COMMAND.QUEUE’ is configured
channel corresponding to the specified name. Ensure to enable programs to get messages from it.
that you have the authority to connect to the remote
queue manager, and ensure that the network is
running. Select Yes if you believe that the problem can
Chapter 2. 4000-4999 - User interface messages (WebSphere MQ for Windows and Linux systems) 5
AMQ4033 Cannot get messages from the queue. AMQ4038 Object damaged.
Severity: 0 : Information Severity: 10 : Warning
Explanation: A reason code returned when the object Explanation: The object is damaged and cannot be
was opened for input indicated that the queue is accessed.
disabled for MQGET request.
Response: The object should be deleted. Alternatively,
Response: To get messages from this queue, enable it it might be possible to recover it from a media image
for GET requests. or backup.
AMQ4034 Message too long. You tried to put a AMQ4039 Object in use. The object is already
message on a queue that was bigger opened by another application.
than the maximum allowed for the
queue or queue manager.
Explanation: An MQOPEN call was issued, but the
object in question has already been opened by this or
Explanation: The request to put a message on a queue another application with options that conflict with
returned a reason code indicating that the data length those specified in the Options parameter. This arises if
of the message exceeds the maximum allowed in the the request is for shared input, but the object is already
definition of the queue. open for exclusive input. It also arises if the request is
for exclusive input, but the object is already open for
Response: Either change the MAXMSGL attribute of
input (of any sort).
the queue so that it is equal to or greater than the
length of the message, or reduce the length of the Response: To change the attributes of an object,
message being put on the queue. specify the Force option as ’Yes’ to apply the changes.
If you do this, any applications using the object must
close and reopen the object to proceed.
AMQ4035 No message available. The response
message did not arrive within a
reasonable amount of time. AMQ4040 Cannot put messages on this queue.
Severity: 0 : Information Severity: 0 : Information
Explanation: The request to get a message from a Explanation: MQPUT and MQPUT1 calls are currently
queue returned a reason code indicating that there are inhibited for the queue, or for the queue to which this
currently no messages on the queue that meet the queue resolves.
selection criteria specified on the GET request.
AMQ4042 Queue full. The queue contains the
AMQ4036 Access not permitted. You are not maximum number of messages.
authorized to perform this operation.
Explanation: On an MQPUT or MQPUT1 call, the call
Explanation: The queue manager’s security failed because the queue is full; that is, it already
mechanism has indicated that the userid associated contains the maximum number of messages possible.
with this request is not authorized to access the object.
AMQ4043 Queue manager not available for
AMQ4037 Object definition changed since it was connection.
opened.
Response: Ensure that the queue manager is running.
Explanation: Object definitions that affect this object If the queue manager is running on another computer,
have been changed since the Hobj handle used on this ensure it is configured to accept remote connections.
call was returned by the MQOPEN call.
Response: Issue an MQCLOSE call to return the AMQ4044 Queue manager stopping.
handle to the system. It is then usually sufficient to
reopen the object and try the operation again.
Explanation: An MQI call was issued, but the call
failed because the queue manager is shutting down. If
the call was an MQGET call with the MQGMO_WAIT
option, the wait has been canceled.
Response: You cannot issue any more MQI calls.

AMQ4052 Coded character-set ID error. Cannot
convert a command message to the
AMQ4045 Queue not empty. The queue contains CCSID of the target queue manager.
one or more messages or uncommitted
PUT or GET requests.
AMQ4053 Channel in doubt. Operation not
Explanation: An operation that requires the queue to completed.
be empty has failed because the queue either contains
messages or has uncommitted PUT or GET requests
outstanding. Explanation: The operation could not complete
because the channel was in doubt.
AMQ4046 Insufficient system resources available.
AMQ4054 Channel in use.
AMQ4047 Insufficient storage available. Explanation: An attempt was made to perform an
operation on a channel, but the channel is currently
active.
AMQ4048 The request received an unexpected

AMQ4055 Channel status not found.
reason code from an underlying API or
command request. The reason code was Severity: 10 : Warning
<insert_0>
Explanation: No channel status is available for this
Severity: 20 : Error channel. This might indicate that the channel has not
been used.
Explanation: While executing the requested operation,
an unexpected return code was received. This has
resulted in the operation not completing as expected. AMQ4056 Command failed.
Response: Use the appropriate documentation to Severity: 10 : Warning
determine why the reason code was returned.
AMQ4057 Configuration error in the channel
AMQ4049 Unknown object name. definition or communication subsystem.
Severity: 10 : Warning Severity: 10 : Warning
Explanation: A command or API request was issued, Explanation: Allocation of a conversation is not
but the object cannot be found. possible.
AMQ4050 Allocation failed. An attempt to allocate AMQ4058 Connection closed.

a conversation to a remote system failed.
Explanation: The connection to a remote system has
Explanation: The error might be due to an incorrect unexpectedly broken while receiving data.
entry in the channel definition or it might be that the
listening program on the remote system was not
AMQ4059 Could not establish a connection to the
running.
queue manager.
AMQ4051 Bind failed. The bind to a remote
system during session negotiation Explanation: The attempt to connect to the queue
failed. manager failed. This could be because the queue
manager is incorrectly configured to allow a connection
from this system, or the connection has been broken.
Response: Try the operation again. If the error
persists, examine the problem determination
information to see if any information has been
recorded.
AMQ4060 Dynamic queue scope error. AMQ4068 Queue is not a transmission queue.
Explanation: The Scope attribute of the queue was set Explanation: The queue specified in the channel
to MQSCO_CELL but this is not allowed for a dynamic definition was not a transmission queue.
queue.
AMQ4069 Object already exists.
AMQ4061 Remote system not available. Could not
allocate a conversation to a remote
system. Explanation: Could not create object because the
object already existed.
Response: The error might be transitory; try again
AMQ4070 Object is open.
later.
AMQ4062 An MQINQ call failed when the queue Explanation: An attempt was made to delete, change
manager inquired about a WebSphere or clear an object that is in use.
MQ object.
Response: Wait until the object is not in use, then try
Severity: 10 : Warning again.
Response: Check the queue manager’s error log for
more information about the error. AMQ4071 Object has wrong type. Could not
replace a queue object of a different
type.
AMQ4063 An MQOPEN call failed when the
queue manager tried to open a Severity: 10 : Warning
WebSphere MQ object.
Severity: 10 : Warning AMQ4072 Queue already exists in cell.
Response: Check the queue manager’s error log for Severity: 10 : Warning
more information about the error.
Explanation: Cannot define a queue with cell scope or
change the scope of an existing queue from
AMQ4064 An MQSET call failed when the queue queue-manager scope to cell scope, because a queue
manager tried to set the values of the with that name already exists in the cell.
attributes of a WebSphere MQ object.
Severity: 10 : Warning AMQ4073 Ping error. You can only ping a sender
or server channel. If the local channel is
Response: Check the queue manager’s error log for
a receiver channel, ping from the remote
more information about the error.
queue manager.
AMQ4065 Message sequence number error.
AMQ4074 Receive failed, possibly due to a
Explanation: The message sequence number communications failure.
parameter was not valid.
AMQ4066 Message truncated because it is larger

AMQ4075 Error while receiving data from a remote
than the command server’s maximum
system, possibly due to a
valid message size.
communications failure.
AMQ4067 Communications manager not available.

AMQ4076 Remote queue manager terminating.
Explanation: The communications subsystem is not
Explanation: The channel stopped because the remote
available.
queue manager was terminating.
AMQ4077 Remote queue manager not available. AMQ4085 No name supplied for transmission
queue.
Explanation: The channel could not be started because
the remote queue manager was not available. Response: Supply a non-blank transmission queue
name for this channel type.
Response: Ensure that the remote queue manager is
started, and that it is configured to accept incoming
communication requests. AMQ4086 No connection name supplied.
AMQ4078 Send failed. An error occurred while
Response: Supply a non-blank connection name for
sending data to a remote system,
this channel type.
possibly due to a communications
failure.
AMQ4087 An error occurred while trying to use a
cluster resource.
AMQ4079 Channel closed by security exit.
Response: Check that the queues whose names start
with ’SYSTEM.CLUSTER.’ are not full and that
messages are allowed to be put on them.
AMQ4080 Remote channel not known.
Severity: 10 : Warning AMQ4088 Cannot share transmission queue in
cluster.
Explanation: There is no definition of this channel on
the remote system. Severity: 10 : Warning
Explanation: The queue is a transmission queue and
AMQ4081 User exit not available. cannot be shared in a cluster.
AMQ4089 PUT commands inhibited for system
Explanation: The channel was closed because the user
command queue called
exit specified does not exist.
’SYSTEM.ADMIN.COMMAND.QUEUE’.
AMQ4082 Unexpected WebSphere MQ error
(<insert_0>).
AMQ4090 Are you sure you want to inhibit PUT
and GET commands for the queue
called
AMQ4083 Queue manager name not known. ’SYSTEM.ADMIN.COMMAND.QUEUE’?
If you do, you will no longer be able to
Severity: 10 : Warning administer the queue manager using the
Explanation: If the queue manager is remote, this WebSphere MQ Explorer.
might indicate that another queue manager is Severity: 10 : Warning
incorrectly using the same connection name. Queue
managers using TCP/IP on the same computer must Explanation: WebSphere MQ Explorer uses the queue
listen on different port numbers. This means that they called ’SYSTEM.ADMIN.COMMAND.QUEUE’ to
will also have different connection names. administer the queue manager.
Response: Continue only if you really want to inhibit
AMQ4084 Cell directory is not available. PUT or GET commands for this queue and stop using
the WebSphere MQ Explorer to administer the queue
Severity: 10 : Warning manager.
Explanation: The Scope attribute of the queue was set
to MQSCO_CELL but no name service supporting a AMQ4091 Cannot connect to remote queue
cell directory has been configured. manager.
Response: Configure a name service to support the Severity: 10 : Warning
cell directory.
Explanation: The remote queue manager is using an
unsupported protocol for connections. The WebSphere
MQ Explorer only supports connections to remote mark within an attribute, use two together with no
queue managers using the TCP/IP protocol. space between.)
AMQ4092 The queue manager could not be AMQ4098 Incorrect list format.
removed from the cluster because its
membership of the cluster is defined
using namelist <insert_0>. Explanation: The attribute can contain a list of values
which must be separated by a space or a comma. Each
value in the list can be enclosed in a pair of single or
Response: To remove the queue manager from the double quotation marks. (Only required for values
cluster, remove it from the namelist. Ensure that you do which contain spaces, commas or quotation marks.)
not inadvertently affect the definitions of other objects
Response: Check that values are separated by a space
using the namelist.
or a comma, and that all opening and closing quotation
marks are in pairs. (To include a quotation mark within
AMQ4093 The cluster specified is already shown an attribute, use two together with no space between.)
in the console.
Severity: 0 : Information AMQ4099 Cannot communicate with one or more
repository queue managers. Cluster
<insert_0> is configured to use one or
AMQ4094 An error occurred adding this cluster to
more repository queue managers which
the console. Are you sure you want to
communicate using a protocol other
show this cluster in the console
than TCP/IP.
anyway?
Explanation: The WebSphere MQ Explorer can only
Response: Select Yes if you believe that the problem
establish connections to remote queue managers using
can be resolved later. Select No if you want to correct
TCP/IP.
the problem now and try again.
Response: To complete removal of the queue manager
from the cluster, issue the RESET CLUSTER
AMQ4095 Queue manager <insert_0> is not a
ACTION(FORCEREMOVE) command from the
repository queue manager for cluster
repository queue manager.
<insert_1>.
AMQ4103 An error occurred connecting to the
Explanation: To administer a cluster, the WebSphere queue manager. Are you sure you want
MQ Explorer needs a connection to the repository to show this queue manager in the
queue manager. folder?
AMQ4096 Are you sure you want to clear the
Explanation: A connection could not be made to the
password for this channel?
Response: Ensure that the named queue manager is
Response: Check with the user before clearing the running on the machine specified in the selected
password from the channel. Continue only if you really channel definition table. Ensure that you have the
want to clear the password. authority to connect to the remote queue manager, and
ensure that the network is up and running. Select Yes if
you believe that the problem can be resolved later.
AMQ4097 Unmatched quotation mark. Select No if you want to correct the problem now and
Severity: 10 : Warning try again.
Explanation: An unmatched quotation mark has been

found in a list of attributes. Each value in the list can AMQ4104 The specified file <insert_0> does not
be enclosed in a pair of single or double quotation contain a client definition table in the
marks. (Only required for values which contain spaces, correct format.
commas or quotation marks.) Severity: 10 : Warning
Response: Check that all opening and closing Explanation: The given channel definition table is not
quotation marks are in pairs. (To include a quotation in the correct format.
Response: Specify a file in the correct format.

AMQ4124 The MQOPEN request received an
unexpected reason code of <insert_0>.
AMQ4105 The remote queue manager has not been
removed because it is still required by
other plug-ins. Explanation: An unexpected reason code was returned
from an MQOPEN API request. The queue has not
been opened.
Explanation: Other plug-ins have responded to the
Response: Use the reason code to determine the
attempted removal of this queue manager by indicating
underlying reason for the failure.
that they are still using it.
Response: Ensure that the other plug-ins have
AMQ4125 Putting a test message on the queue
finished using the queue manager before trying to
received an unexpected reason code
delete it again.
<insert_0>.
AMQ4117 This action cannot be undone. Are you
sure you want to delete the WebSphere Explanation: One of the underlying API requests was
MQ queue manager <insert_0> from unsuccessful. The test message was not placed on the
your system? queue.
AMQ4126 The value of one of the properties
Explanation: A confirmation is required before the
specified is not valid. The request was
queue manager is deleted.
not processed.
Response: Continue only if you want to permanently
delete the queue manager.
Response: Specify a different value.
AMQ4121 The MQGET request received an
unexpected reason code of <insert_0>. AMQ4127 WebSphere MQ failed to read queue
manager information from disk because
the file format is not valid. The request
Explanation: An unexpected reason code was returned was not processed.
from a MQGET API request. Use the reason code to
determine the underlying reason why the request
failed. Explanation: The format of the WebSphere
MQ_Handles file is incorrect. This file has been backed
Response: The MQGET request was not successful.
up and removed, meaning that any remote queue
Some messages might not have been retrieved.
manager definitions are lost. All local queue managers
should be detected automatically and displayed in the
AMQ4122 The MQPUT request received an WebSphere MQ Explorer.
unexpected reason code of <insert_0>.
Response: Ensure that the Eclipse workspace has not
Severity: 10 : Warning been corrupted.
Explanation: An unexpected reason code was returned
from a MQPUT API request. Use the reason code to AMQ4128 Could not start the iKeyMan program.
determine the underlying reason why the request
Severity: 30 : Severe error
failed.
Explanation: An error was encountered when trying
Response: MQPUT processing was unsuccessful. No
to execute the iKeyMan program.
message was placed on the queue.
Response: Try again, and if symptoms persist contact
the System Administrator.
AMQ4123 The <insert_0> <insert_1> was deleted
successfully.
AMQ4129 Could not query the user ID from Java.
Explanation: The object of the specified type and
name has been successfully deleted. Explanation: The Java API
System.getProperty(″user.id″) threw a
Response: none.
SecurityException.
Response: Configure your Java security environment

AMQ4135 The default channel used by remote
using the ’policytool’ to allow WebSphere MQ Explorer
queue managers to administer this
to query the ’user.id’.
queue manager is
SYSTEM.ADMIN.SVRCONN.
AMQ4130 A Browser Control could not be opened. Do you want to delete this channel to
Make sure Mozilla has been installed. prevent the queue manager being
administered by other queue managers?
Explanation: The SWT Browser control depends on
Mozilla being installed. Response: Select Yes to delete the channel.
Response: Ensure that the Mozilla browser is correctly

installed. AMQ4136 Are you sure you want to clear all FFSTs
and Trace from this machine? This
operation cannot be undone.
AMQ4131 A Browser Control could not be opened.
Explanation: Deleting all FFSTs and Trace from this
Explanation: The SWT Browser control depends on machine means that any historical error logs and trace
the system browser being installed. will be lost.
Response: Ensure that the system browser is correctly Response: Select Yes to clear FFSTs and Trace
installed.
AMQ4137 The default remote administration

AMQ4132 Are you sure you want to stop the channel SYSTEM.ADMIN.SVRCONN
<insert_0> named ″<insert_1>″? has been deleted successfully.
Severity: 10 : Warning Severity: 0 : Information
Explanation: A confirmation is required before the Response: Message for information only.
specified object is stopped. The type of object and name
are provided in the message.
AMQ4138 Are you sure you want to import new
Response: Continue only if you want to stop the settings that will overwrite the current
object. settings? This operation cannot be
undone.
AMQ4133 When a queue manager is removed, Severity: 10 : Warning
WebSphere MQ Explorer destroys the
connection information for that queue Explanation: Importing settings into the WebSphere
manager. MQ Explorer will overwrite the current settings.
To see the queue manager at a later date
Response: Continue only if you want to overwrite the
use the Add Queue Manager wizard.
current settings.
Remove the queue manager <insert_0> ?
Response: Continue only if you want to remove the channel SYSTEM.ADMIN.SVRCONN
queue manager. was created successfully.
AMQ4134 The default channel used by remote
queue managers to administer this
queue manager does not exist.
Do you want to create the default AMQ4140 The custom CipherSpec is not valid.
remote administration channel
SYSTEM.ADMIN.SVRCONN to allow
this queue manager to be administered
by other queue managers? AMQ4141 The Distinguished Names specification
is not valid.
Response: Select Yes to create the channel.
AMQ4142 The default remote administration AMQ4146 Eclipse cannot create or read the
channel SYSTEM.ADMIN.SVRCONN workspace for WebSphere MQ Explorer.
could not be created.
Severity: 40 : Stop Error
Explanation: To load the WebSphere MQ Explorer, a
Explanation: A problem has occurred when issuing a valid workspace is required.
command to the command server to create the channel.
Response: Ensure that you can write to the Eclipse
Response: Try again, and if symptoms persist contact workspace.
the Systems Administrator.
AMQ4147 Eclipse cannot write to the workspace
AMQ4143 The default remote administration for WebSphere MQ Explorer in
channel SYSTEM.ADMIN.SVRCONN <insert_0>.
Explanation: To load the WebSphere MQ Explorer,
Explanation: A problem has occurred with the write access to the workspace is required.
underlying data model, and the channel could not be
Response: Ensure that you can write to the Eclipse
created.
workspace.
Response: Try again, and if symptoms persist contact
the Systems Administrator.
AMQ4148 The object was created successfully.
channel SYSTEM.ADMIN.SVRCONN Response: Message for information only.
could not be deleted.
Severity: 10 : Warning AMQ4149 The request to start the listener was
accepted.
Explanation: A problem has occurred issuing a
command to the command server to delete the channel. Severity: 0 : Information
Response: Ensure that the channel is not in use and Explanation: A user request to start the listener was
try again. If symptoms persist, contact the Systems accepted by WebSphere MQ.
Administrator.
AMQ4145 An error occurred connecting to the

remote queue manager using the AMQ4150 The request to stop the listener was
intermediate queue manager. Are you accepted.
sure you want to show this queue Severity: 0 : Information
manager in the folder anyway?
Explanation: A user request to stop the listener was
Severity: 10 : Warning accepted by WebSphere MQ.
Explanation: A connection could not be made to the Response: Message for information only.
Response: Ensure that the intermediate queue AMQ4151 The request to start the service was
manager is available and that the named remote queue accepted.
manager is running, and is accessible from the
intermediate queue manager. Ensure that you have the Severity: 0 : Information
authority to connect to the remote queue manager, and Explanation: A user request to start the service was
ensure that the network is up and running. Select Yes if accepted by WebSphere MQ.
you believe that the problem can be resolved later.
Select No if you want to correct the problem now and Response: Message for information only.
try again.
AMQ4152 The request to stop the service was
accepted.
Explanation: A user request to stop the service was
accepted by WebSphere MQ.
Response: Message for information only. The WebSphere MQ user does not have sufficient
access to execute the program.
If StdOut or StdErr are defined for the program, the
AMQ4153 WebSphere MQ cannot stop the listener
WebSphere MQ user does not have sufficient access to
because it is not running.
the locations specified.
Response: Check the Queue Manager error logs for
further details on the cause of the failure, correct the
AMQ4154 WebSphere MQ cannot start the service problem and try again.
because no start command has been
specified.
AMQ4161 The parameter specified is not valid.
Response: Ensure that the service has a start
Explanation: The parameter specified when trying to
command specified.
create or alter an object is not valid.
Response: Ensure that valid parameters are specified,
AMQ4155 WebSphere MQ cannot stop the service
then try again.
because no stop command has been
specified.
AMQ4162 The password cannot be cleared.
Response: Ensure that the service has a stop
command specified. Response: Try to clear the password again later.
AMQ4156 WebSphere MQ cannot stop the service AMQ4163 The password cannot be changed.
because the service is not running.
Explanation: The attempt to change the password
failed because of an error.
AMQ4157 WebSphere MQ cannot start the service
Response: Try a different password
because the services is already running.
AMQ4164 The password was successfully changed.
AMQ4158 WebSphere MQ cannot start the listener
because it is already running. Response: Message for information only.
AMQ4165 No password entered in the new
password field. No change applied.
AMQ4159 WebSphere MQ cannot start the client
connection channel because one or more Severity: 10 : Warning
of the properties are incorrectly
specified. Explanation: You must enter a new password in both
the new and confirm password fields.
Response: Enter a new password in the new
Response: Ensure that the client connection has the password field.
correct queue manager name and connection name
before trying to start.
AMQ4166 No password entered in the confirm
new password field. No change applied.
AMQ4160 WebSphere MQ cannot process the
request because the executable specified Severity: 10 : Warning
cannot be started. Explanation: You must enter a new password in both
Severity: 10 : Warning the new and confirm password fields.
Explanation: The requested was unsuccessful because Response: Re-enter the new password in the confirm
the program which was defined to be run to complete new password field.
the action could not be started.
Reasons why the program could not be started are :-
The program does not exist at the specified location.
or inconsistent attributes when trying create or update

AMQ4167 Passwords do not match. No change
an object.
applied.
Response: If this error occurred during object creation
or modification, ensure that the attributes specified are
Explanation: You must enter the same new password correct for this type of object. If the error persists,
in both the new and confirm password fields. examine the problem determination information to see
if any details have been recorded.
Response: Ensure that the passwords in the new and
confirm fields match.
AMQ4173 WebSphere MQ cannot clear one or
more Trace and FFST files.
AMQ4168 WebSphere MQ failed to start listening
for objects. Severity: 10 : Warning
Severity: 20 : Error Explanation: WebSphere MQ cannot clear some files,
possibly because these files are currently in use, or the
Explanation: No objects will be displayed in the
WebSphere MQ Explorer does not have the appropriate
currently selected view.
access permission.
Response: Check the problem determination
Response: Check that tracing is disabled, and that the
information, and ensure that WebSphere MQ and the
WebSphere MQ Explorer has appropriate access
queue manager in question are both running correctly.
permission to delete the Trace and FFST files.
AMQ4169 WebSphere MQ failed to set the object

AMQ4174 FFSTs and Trace were cleared
filter.
successfully.
Explanation: The WebSphere MQ Explorer cannot
listen for objects, so no objects will be displayed in the
currently selected view.
AMQ4175 WebSphere MQ cannot process your
Response: Check the problem determination
request because the value specified is
information, and ensure that WebSphere MQ and the
not valid.
queue manager in question are both running correctly.
AMQ4170 The object name specified is not valid. Explanation: Only certain combinations and values
are valid for the object your are trying to alter or create.
Please check the values and try again.
Explanation: The object name specified when trying to
Response: Specify a valid value and try again.
create or alter an object is not valid.
Response: Ensure that a valid object name is specified,
then try again.
request because the object name
specified is not valid.
AMQ4171 There was an error when
communicating with the queue manager.
Explanation: Only certain combinations and values
are valid for the object your are trying to alter or create.
Explanation: A request for information from the You might also see this message if you have specified
queue manager failed. an invalid QSG disposition.
Response: Try the operation again. If the error Response: Check all values are valid for this type of
persists, examine the problem determination object and try again. If you have altered the disposition
information to see if any details have been recorded. of this object, check that the value is correct.
AMQ4172 There was an error when trying to set or AMQ4177 The WebSphere MQ Explorer cannot
retrieve information. process your request because the
connection to WebSphere MQ is
Severity: 20 : Error quiescing.
Explanation: There was an error when trying to set or Severity: 20 : Error
retrieve information from the queue manager. This
might have happened because you specified incorrect Explanation: The connection to WebSphere MQ is
quiescing, so no new information can be queried. check the problem determination information, and
ensure that WebSphere MQ and the queue manager in
Response: Wait for the connection to end, then try
question are both running correctly.
reconnecting.
AMQ4183 Query failed because the queue

manager is not in a queue-sharing
request because there was a disposition
group.
conflict detected.
Explanation: WebSphere MQ issued a query that
Explanation: A disposition conflict was detected.
required the queue manager to be a member of a
Please ensure that all disposition related fields are
queue-sharing group.
correct for this type of object.
Response: Try the operation again, if the problem
Response: Ensure that all disposition related fields are
persists check the problem determination information
correct for this type of object and try again.
for more details.

AMQ4184 WebSphere MQ is unable to perform
request because the string provided was
your request because the channel is not
of an incorrect length.
active.
Explanation: A string value has been modified or
supplied that is too long when creating or modifying
AMQ4185 WebSphere MQ failed to import your
an object.
settings.
Response: Check the values being supplied and try
again.
Response: Try again. If the error persists, examine the
problem determination information to see if any details
have been recorded.
request because there was a parameter
conflict.
AMQ4186 WebSphere MQ failed to export your
settings.
Explanation: When creating or modifying an object,
the combination of parameters specified is not valid.
Response: Try again. If the error persists, examine the
Response: Check that the combination specified is
problem determination information to see if any details
valid for the object and try again.
have been recorded.
AMQ4181 WebSphere MQ is not responding. Do

AMQ4187 WebSphere MQ has succesfully
you want to continue waiting?
imported your settings. (You must
Severity: 10 : Warning restart WebSphere MQ Explorer to
apply the imported settings.)
Explanation: WebSphere MQ does not appear to be
responding. This could be because of a heavily loaded Severity: 0 : Information
remote system, or a slow network connection. However
Response: Restart WebSphere MQ explorer to apply
there could have been a system failure. Choosing not to
the imported settings
continue could leave the WebSphere MQ Explorer in an
unknown state, so you should restart it.
AMQ4188 Are you sure you want to remove queue
Response: If you choose not to continue waiting,
manager <insert_0> from cluster
restart the WebSphere MQ Explorer, if the problem
<insert_1>?
persists check for problem determination information.
AMQ4182 No objects were found. Explanation: A confirmation is required before the
queue manager is removed from the cluster.
Response: Continue only if you want to permanently
Explanation: The query did not find any objects.
remove the queue manger from the cluster.
Response: If you were expecting objects to be found,
AMQ4189 The queue manager could not be AMQ4193 The information supplied could not be
suspended from the cluster. The correctly converted to the required code
operation failed with error <insert_0>. page.
Severity: 20 : Error Severity: 20 : Error
Explanation: The queue manager has not been Explanation: All or part of the information entered
removed from the cluster. required conversion to a different code page. One or
more characters could not be converted to an
equivalent character in the new code page.
information to see if any information has been Response: Change the characters used, then try the
recorded. operation again.
AMQ4190 An error occurred when clearing the AMQ4194 Request failed because the queue
queue manager’s REPOS field. The manager attempted to use a default
operation failed with error <insert_0>. transmission queue which is not valid.
Explanation: The queue manager has only partially Explanation: An MQOPEN or MQPUT1 call specified
been removed from the cluster. The queue manager has a remote queue as the destination. The queue manager
been suspended from the cluster. The REPOS field of used the default transmission queue, as there is no
the queue manager and the CLUSTER fields of the queue defined with the same name as the destination
associated cluster channels have not been cleared. queue manager, but the attempt failed because the
default transmission queue is not a valid local queue.
persists, examine the problem determination Response: Check that the queue manager’s default
information to see if any information has been transmission queue property (DefXmitQName) specifies
recorded. a valid local queue.
AMQ4191 An error occurred when clearing the AMQ4195 WebSphere MQ Explorer is now in an
CLUSTER field of channel <insert_0>. unknown state and should be restarted.
The operation failed with error Do you want to restart WebSphere MQ
<insert_1>. Explorer?
Severity: 20 : Error Severity: 10 : Warning
Explanation: The queue manager has only partially Explanation: You have chosen not to wait for
been removed from the cluster. The queue manager has WebSphere MQ to respond to a request. WebSphere
been suspended from the cluster and the queue MQ Explorer is therefore in an unknown state and
manager’s REPOS field has been cleared. Some of the should be restarted.
CLUSTER fields of other associated cluster channels
Response: Restart the WebSphere MQ Explorer and
might also have been cleared.
try the operation again. If the problem persists check
Response: To completely remove the queue manager, for problem determination information.
ensure that all the CLUSTER fields of associated cluster
channels are cleared.
AMQ4196 The command or operation is not valid
against the type of object or queue
AMQ4192 The queue manager could not be specified
removed from a cluster because channel
<insert_0> is using cluster namelist
<insert_1>. Explanation: You have attempted a command or
operation against an object or queue whose type is not
valid for the operation specified. For instance: browsing
Response: Remove the cluster channel from the a remote queue; issuing the clear command against a
cluster namelist. Ensure that you do not inadvertently queue whose type is not QLOCAL; clearing by API
affect the definitions of other objects using the namelist. calls, a queue who type cannot be opened for input.
Then try removing the queue manager again.
Response: Retry the command or operation against an
object or queue whose type is valid for the operation
requested.
deleted and cannot be removed from the cluster in the

AMQ4197 An MQOPEN or MQPUT1 call was
normal way. A confirmation is required before the
issued specifying an alias queue as the
queue manager is forcibly removed.
target, but the BaseQName in the alias
queue attributes is not recognized as a Response: Continue only if you want to forcibly
queue name. remove the queue manager.
AMQ4501 The queue manager was successfully
Explanation: An MQOPEN or MQPUT1 call was
removed from the cluster.
issued specifying an alias queue as the target, but the
BaseQName in the alias queue attributes is not Severity: 0 : Information
recognized as a queue name. This reason code can also
occur when BaseQName is the name of a cluster queue Explanation: The queue manager will still appear as a
that cannot be resolved successfully. member of the cluster until the configuration changes
have been sent across the network and the cluster
Response: Correct the queue definitions. channels to the queue manager have become inactive.
This might take a long time.
AMQ4207 The path specified is not valid.
AMQ4502 You have shared the queue in cluster
<insert_0>. The queue manager is not a
Response: Check the path specified and try again. member of this cluster.
AMQ4400 Explorer cannot administer the queue
Response: To make the queue available to the
manager because the queue <insert_0> is
members of this cluster, you must join the queue
not defined.
manager to the cluster.
Explanation: Explorer uses the queue <insert_0> to AMQ4503 The list of values is too long.
administer queue managers.
Response: Define the queue <insert_0> and retry.
Explanation: The list of values that you have entered
is too long. The maximum number of characters
AMQ4401 Explorer cannot administer the queue allowed for this value is <insert_0>.
manager because the user is not
authorised to open the queue <insert_0>.
AMQ4504 The value is too long.
Explanation: Explorer uses the queue <insert_0> to
Explanation: You have entered a value containing too
administer this queue manager.
many characters. The maximum number of characters
Response: Allow Explorer to open the queue allowed for each value of this attribute is <insert_0>.
<insert_0> and retry.
AMQ4505 There are too many entries in the list.
AMQ4402 The queue <insert_0> could not be
opened for reason <insert_1>.
Explanation: You have entered too many values in the
list. The maximum number of values is <insert_0>.
Explanation: Explorer uses the queue <insert_0> to
administer this queue manager.
AMQ4506 Cannot connect to queue manager
Response: Allow Explorer to open the queue <insert_0>. It cannot be removed from
<insert_0> and retry. the cluster in the normal way.
AMQ4500 Are you sure you want to forcibly
Response: Try the operation again when the queue
remove queue manager <insert_0> from
manager is available. If the queue manager no longer
cluster <insert_1>?
exists, you can choose to forcibly remove the queue
Severity: 10 : Warning manager from the cluster.
Explanation: You should only forcibly remove a queue
manager from a cluster when it has already been
AMQ4507 The remote queue manager is not using AMQ4515 The repository queue manager for
TCP/IP. cluster <insert_0> is not available for
connection.
Explanation: The connection information available for
the remote queue manager uses a communication Explanation: Views showing cluster queues in this
protocol other than TCP/IP. The WebSphere MQ cluster might not be complete.
Explorer cannot connect to the queue manager to
remove it from the cluster in the normal way.
AMQ4516 Cluster workload exit error.
Response: If the queue manager no longer exists, you
can choose to forcibly remove the queue manager from
the cluster. Explanation: The queue manager’s cluster workload
exit failed unexpectedly or did not respond in time.
AMQ4508 The queue manager successfully left the
cluster. AMQ4517 Cluster resolution error.
Explanation: The queue manager will still appear as a Explanation: The definition of the cluster queue could
member of the cluster until the configuration changes not be resolved correctly because a response from a
have been sent across the network and the cluster repository queue manager was not available.
channels to the queue manager have become inactive.
This might take a long time.
AMQ4518 AMQ4518=A call was stopped by the
cluster exit.
AMQ4509 The request to suspend membership of
the cluster has been accepted. Severity: 10 : Warning
Severity: 0 : Information Explanation: The queue manager’s cluster workload

exit rejected a call to open or put a message onto a
Response: Message for information only. cluster queue.
AMQ4510 The request to resume membership of AMQ4519 No destinations are available.

the cluster has been accepted.
Explanation: At the time that the message was put,
Response: Message for information only. there were no longer any instances of the queue in the
cluster.
AMQ4511 The queue manager is not a member of
the cluster. AMQ4520 The WebSphere MQ Explorer could not
initialize TCP/IP. Administration of
remote queue managers and clusters is
Response: Message for information only. not possible.
AMQ4513 The request to refresh the information
about the cluster has been accepted.
AMQ4521 The text you entered contained a comma
Severity: 0 : Information (,) which is used as a list separator
character.
AMQ4514 The queue manager is not a member of Explanation: This value does not accept lists.
cluster <insert_0>.
Response: If you want to use a comma as part of a
Severity: 10 : Warning value, enclose the value in double quotes.
Explanation: The object that you have shared in the
cluster will not be available to other members of the
cluster until you make this queue manager a member
of the cluster.
AMQ4522 The wizard was unable to add the AMQ4577 An error occurred initializing the
queue manager to the cluster. process.
All changes will be rolled back.
Explanation: A problem occurred while defining AMQ4578 An error occurred loading the messages
objects or modifying the queue manager’s properties. file <insert_0>.
Response: Ensure that the default objects exist for the Severity: 30 : Severe error
queue manager.
AMQ4579 An error occurred loading the system
AMQ4523 The wizard was unable to add one of libraries.
the queue managers to the cluster.
All changes will be rolled back.
AMQ4580 An internal method detected an
Explanation: A problem occurred while defining unexpected system return code. The
objects or modifying one of the queue managers’ method <insert_0> returned <insert_1>.
properties.
Response: Ensure that the default objects exist for the
Response: Examine the problem determination
queue manager.
information on this computer to establish the cause of
the error.
AMQ4571 Are you sure you want to change the
location of the Key Repository for
AMQ4581 Parameter check failed on the internal
queue manager <insert_0>?
function <insert_0>. The error was
Severity: 10 : Warning <insert_1>.
Explanation: You might prevent the queue manager Severity: 30 : Severe error
from starting if you change the Key Repository field to
Response: Examine the problem determination
a location which is not valid.
information on this computer to establish the cause of
Response: Ensure that the location specified is correct the error.
before continuing.
AMQ4582 Queue manager <insert_0> is not
AMQ4572 The request to refresh the information available for client connection.
about all clusters has been accepted.
Response: Ensure the queue manager is running and
Response: Message for information only. is configured to accept remote connections.
AMQ4574 IBM WebSphere Explorer is already AMQ4583 Queue manager <insert_0> is not
running. available for connection.
Severity: 30 : Severe error Severity: 30 : Severe error
Response: Ensure the queue manager is running.
AMQ4575 An error occurred initializing the data
model.
AMQ4584 Queue manager <insert_0> is not
Severity: 30 : Severe error available for cluster connection.
AMQ4576 The working directory <insert_0> is not
Response: Ensure that the queue manager is running.
valid.
If the queue manager has been deleted it might
Severity: 30 : Severe error continue to be displayed as a member of a cluster for
up to 30 days.
AMQ4585 An internal method <insert_0> AMQ4591 The command server for <insert_0> is
encountered an unexpected error. not running.
Response: Examine the problem determination Explanation: The command server has stopped for
information on this computer to establish the cause of some reason, so the request cannot be processed.
the error.
Response: Start the command server. If the error
AMQ4586 The attempt to create the URL for file information to see if any details have been recorded.
<insert_0> failed.
Severity: 30 : Severe error AMQ4592 The connection was closed successfully.
Explanation: The file name specified was not Severity: 0 : Information
recognized.
Explanation: The request to close the connection to an
Response: Ensure that the file exists at the specified application was successful.
location and can be read.
AMQ4587 The attempt to read from URL

AMQ4593 Do you really want to stop the
<insert_0> failed.
connection to application ″<insert_0>″
Explanation: There was an error when the system
Explanation: WebSphere MQ explorer is about to stop
tried to read the Client channel definition table.
a connection, stopping the connection will prevent
Response: Ensure that the file exists at the specified further communication between MQ and the
location and can be read. application in question.
Response: Select yes if you want to stop the
AMQ4588 The attempt to read from URL connection.
<insert_0> failed.
Severity: 30 : Severe error AMQ4700 PCF command identifier (<insert_0>) not
valid for queue manager <insert_1>.
Explanation: There was an error when the system
tried to read the file. Severity: 10 : Warning
Response: Ensure that the file exists at the specified Explanation: The specified PCF command is not
location and can be read. supported by this queue manager.
AMQ4589 No connection was found to application AMQ4800 Error initializing <insert_0>.

<insert_0>.
Explanation: An error occurred while starting this
Explanation: The connection was not found. Possibly application.
the connection was closed before the command was
Response: Check that the WebSphere MQ runtime
issued.
libraries are available.
Response: Check that the application connection has Check that the PATH system environment variable
not been closed in the background. includes the directory for these runtime libraries.)
AMQ4590 The queue manager connection to AMQ4801 Error getting the location of the help
application <insert_0> could not be system.
closed.
Explanation: To launch the standalone Eclipse help
Explanation: The connection could not be closed due system, the WebSphere MQ file transfer application
to a PCF error. needs to know where it is installed.
Response: Check for FFSTs. Response: Check that Eclipse has been installed with
WebSphere MQ.
AMQ4802 Error launching the help system.

Explanation: The WebSphere MQ file transfer
application failed to create an instance of the Eclipse
standalone help system.
Response: Check that Eclipse has been installed with
WebSphere MQ.
AMQ4803 Error starting the help system.

application failed to start the standalone Eclipse
system.
Response: Check that Eclipse has been installed with
WebSphere MQ.
AMQ4805 Error saving the history log file.

application could not read the history log file. This file
is called com.ibm.mq.fta.log.ser and is in your home
directory.
On Windows, this is %APPDATA%\IBM\WebSphere
MQ FileTransferApp
On Unix, this is $HOME/.mqdata
Response: Check that the read/write properties on
this file allow you to write to it.
AMQ4806 Error reading the history log.

application could not read the history log file. This file
is called com.ibm.mq.fta.log.ser and is in your home
directory.
On Windows, this is %APPDATA%\IBM\WebSphere
MQ FileTransferApp
On Unix, this is $HOME/.mqdata
Response: Check that the read/write properties on
this file allow you to write to it.
AMQ4807 The message size specified (<insert_0>)

is outside the permitted range.
Response: Specify a value of 1000 to 100 000 000.
Other user interface messages
4200-4217 - WebSphere MQ Default Configuration

Response: Retry the operation. If the problem persists,
AMQ4200 There is a problem with the default
use the ’Details>>’ and ’Print’ buttons to record further
configuration. Unable to display the
details about the problem and contact your systems
Default Configuration window.
administrator.
Explanation: There is a problem with WebSphere MQ.
Response: Use the ’Details>>’ button to show further AMQ4206 Unable to prevent remote administration
details about the problem and contact your systems of the queue manager.
administrator.
Explanation: WebSphere MQ was unable change the
configuration of your queue manager to prevent it from
AMQ4201 Unable to check if the computer exists. being remotely administered. This error may occur if
WebSphere MQ is busy with another operation.
Explanation: WebSphere MQ was unable to check if
the computer name you entered exists on your Response: Retry the operation. If the problem persists,
computer’s domain. use the ’Details>>’ and ’Print’ buttons to record further
details about the problem and contact your systems
Response: Retry the operation, if the problem persists
administrator.
contact your systems administrator.
AMQ4208 Show this panel again the next time the

AMQ4202 Unable to contact the computer ’%1’.
queue manager is started?
Explanation: WebSphere MQ was unable to locate a
Explanation: You can choose whether you want the
computer with this name on your computer’s TCP/IP
same panel to be shown the next time this queue
domain.
manager is started, and the default configuration is not
Response: Enter a different computer name. complete.
Response: Select whether you want the panel to be
AMQ4203 Unable to set up the default shown next time.
configuration.
Explanation: WebSphere MQ was unable to set up the AMQ4209 The TCP/IP name of the remote
default configuration. This error may occur if computer must not be your own
WebSphere MQ is busy with another operation. computer name.
Response: Retry the operation. If the problem persists, Explanation: You have selected that the repository
use the ’Details>>’ and ’Print’ buttons to record further queue manager is on another computer, but you have
details about the problem and contact your systems entered the name of your own computer.
administrator.
Response: Enter the correct name of the repository
queue manager.
AMQ4204 Unable to join the default cluster.
Explanation: WebSphere MQ was unable to join your AMQ4210 The command server must be active to
computer to the default cluster. This error may occur if complete this operation. Use the
WebSphere MQ is busy with another operation. WebSphere MQ Services to start it, then
retry the operation.
Response: Retry the operation. If the problem persists,
use the ’Details>>’ and ’Print’ buttons to record further Explanation: The operation you requested needs the
details about the problem and contact your systems command server to be running.
administrator.
Response: Use WebSphere MQ Services to start the
command server, then retry the operation.
AMQ4205 Unable to allow remote administration
of the queue manager.
AMQ4211 The computer name entered must be on
Explanation: WebSphere MQ was unable change the your local domain (’%1’).
configuration of your queue manager to allow it to be
remotely administered. This error may occur if
WebSphere MQ is busy with another operation.
4200-4217 - Default Configuration
AMQ4212 Unable to complete this task because

you do not have authority to administer
WebSphere MQ. You must be in the
Administrators group, in the mqm
group or logged in with the SYSTEM ID
to administer WebSphere MQ.
Explanation: Your userid is not authorized to carry
out the operation you requested.
Response: Retry the operation on a userid with the
required authority, or contact your systems
administrator.
AMQ4213 Unable to delete the queue manager

’%1’ because it is being used by another
program. Close any program using the
queue manager, then click ’Retry’.
Explanation: WebSphere MQ was unable to delete the
old default configuration queue manager because
another program is using the queue manager.
Response: Close the programs that are using the
queue manager, and click Retry.
AMQ4214 The computer ’%1’ is not known on the

network.
Explanation: WebSphere MQ is unable to locate a
computer with this name on your network.
Response: Enter a different computer name.
AMQ4215 Upgrade of the default configuration

was cancelled.
Explanation: You pressed ’Cancel’ while running the
default configuration wizard to upgrade the default
configuration.
Response: None
AMQ4216 The WebSphere MQ services component

does not have the authority it requires.
AMQ4217 The MQSeriesServices component does

not have the authority to create the
default configuration.
4235-4238 - Prepare Wizard
4235-4238 - Prepare WebSphere MQ Wizard

AMQ4235 WebSphere MQ running on this
computer was unable to retrieve group
membership information for user ’%1’

computer can now retrieve group
membership information for user ’%1’.

computer is still unable to retrieve
group membership information for user
’%1’.
AMQ4238 You are not authorized to run the

Prepare WebSphere MQ Wizard. To run
this wizard, you must be in the in the
’Administrators’ group.
4250-4274 - ’Postcard’ messages

AMQ4250 No nickname supplied - Please supply AMQ4257 The call MQCONN failed while
one. preparing for a Put operation, with
Completion Code [%s (%ld)], Reason
Code [%s (%ld)].
AMQ4251 Cannot Initialise WinSock - TCP/IP may
not be installed. Please install TCP/IP Explanation: An error occurred when Postcard tried to
and try again. connect to the queue manager in order to send the
postcard. This error may occur if WebSphere MQ is
Explanation: Postcard was not able to initialize the
busy with another operation.
interface to TCP/IP.
Response: Try to send the postcard again. If the
Response: Check that TCP/IP has been installed
problem persists contact your systems administrator.
successfully. If the problem persists, refer to your
systems administrator.
AMQ4258 The call MQOPEN failed while
preparing for a Put operation, with
AMQ4252 Cannot Find WinSock - TCP/IP may not
be installed. Please install TCP/IP and
Code [%s (%ld)].
try again.
Explanation: An error occurred when Postcard tried to
Explanation: Postcard was not able to find the
open a queue in order to send the postcard. This error
interface to TCP/IP.
may occur if WebSphere MQ is busy with another
Response: Check that TCP/IP has been installed operation.
successfully. If the problem persists, refer to your
AMQ4253 Cannot get fully qualified TCP/IP

AMQ4259 The call MQCLOSE failed while
domain name - Please ensure that the
preparing for a Put operation, with
TCP/IP protocol is configured.
Explanation: Postcard was not able to determine the Code [%s (%ld)].
TCP/IP domain name for your computer.
Response: Check that TCP/IP has been installed close the queue after sending the postcard. This error
successfully. If the problem persists, refer to your may occur if WebSphere MQ is busy with another
systems administrator. operation.
Response: If the problem persists contact your
AMQ4254 Failed to Allocate System Memory - systems administrator.
Please contact your system
administrator.
AMQ4260 The call MQDISC failed while
Explanation: Postcard was not able to allocate enough preparing for a Put operation, with
memory to run correctly. Completion Code [%s (%ld)], Reason
Code [%s (%ld)].
Response: Close other programs to release system
memory. If the problem persists, refer to your systems Explanation: An error occurred when Postcard tried to
administrator. disconnect from the queue manager after sending the
postcard. This error may occur if WebSphere MQ is
AMQ4255 Please supply a user name with which
you wish to communicate. Response: If the problem persists contact your
AMQ4256 Please supply %s’s computer name (this
must be a TCP/IP name). Please supply AMQ4261 The call MQPUT failed with
%s’s computer name (this must be a Completion Code [%s (%ld)], Reason
TCP/IP name). Code [%s (%ld)].
send the postcard by putting its data to the queue. This
error may occur if WebSphere MQ is busy with another
operation.

AMQ4267 The call MQGET failed with
Code [%s (%ld)].
AMQ4262 The call MQCONN failed while
preparing for a Get operation, with
receive a postcards by getting its data from the queue.
This error may occur if WebSphere MQ is busy with
Code [%s (%ld)].
another operation.
Response: Restart Postcard. If the problem persists
connect to the queue manager in order to receive
postcards. This error may occur if WebSphere MQ is
AMQ4268 MQI Postcard is unable to contact the
Response: Restart Postcard. If the problem persists
queue manager on the remote computer.
Verify that the default configuration is
up and running on the remote computer.
AMQ4263 The call MQOPEN failed while
AMQ4269 Unable to run MQI Postcard because
you do not have authority to use
Code [%s (%ld)].
WebSphere MQ. You must be in the
Explanation: An error occurred when Postcard tried to Administators group, in the mqm group,
open a queue in order to send the postcard. This error or logged in with the SYSTEM ID to
may occur if WebSphere MQ is busy with another use WebSphere MQ.
operation.
Explanation: Your user Id is not authorized to use
Response: Restart Postcard. If the problem persists Postcard. You must be in the Administrator’s group, in
contact your systems administrator. the mqm group, or logged in with the SYSTEM ID to
use WebSphere MQ.
AMQ4264 The call MQCLOSE failed while Response: Use Postcard on a user Id with the required
preparing for a Get operation, with authority, or contact your systems administrator.
Code [%s (%ld)].
AMQ4270 MQI Postcard is unable to send
Explanation: An error occurred when Postcard tried to messages to the remote computer. MQI
close the queue after receiving postcards. This error Postcard can only exchange messages
may occur if WebSphere MQ is busy with another with computers that are on the same
operation. TCP/IP domain as this computer (%1).
Response: If the problem persists contact your
systems administrator. AMQ4271 Unable to open a local queue called ’%1’
on the mailbox queue manager ’%2’.
Use WebSphere MQ Explorer to create
AMQ4265 The call MQDISC failed while the queue, then restart MQI Postcard.
Completion Code [%s (%ld)], Reason Explanation: Postcard was unable to automatically
Code [%s (%ld)]. create the queue it uses on the queue manager.
Explanation: An error occurred when Postcard tried to Response: Use WebSphere MQ Explorer to create the
disconnect from the queue manager after receiving queue, and restart Postcard.
postcards. This error may occur if WebSphere MQ is
AMQ4272 The mailbox queue manager ’%1’ does
Response: If the problem persists contact your not exist on this computer.
Explanation: The mailbox queue manager name
specified after the ’-m’ parameter to Postcard does not
AMQ4266 Please type in a message that you wish exist on this computer.
to send to %s.
Response: Restart Postcard specifying the name of a
queue manager that does exist on this computer.
AMQ4273 Unable to contact the target mailbox

’%1’.
Explanation: Postcard was unable send the message as
it could not contact the target mailbox.
Response: Click ’Retry’ to attempt to send the
message again, otherwise click ’Cancel’.
AMQ4274 MQI Postcard has detected that ’%1’ is

the name of a computer and a queue
manager.
Explanation: Postcard has detected that the
destination mailbox name is the name of a computer
and of a queue manager.
Response: Select whether you want to send the
message to the computer or the queue manager with
this name, then click OK.
4300-4309 - API Exerciser
4300-4309 - WebSphere MQ API Exerciser

AMQ4300 Please supply some text in order for the AMQ4306 Memory allocation failure. Stop some
MQPUT(1) operation to succeed. other applications and try again.
Explanation: No text has been supplied for the user so Explanation: There are not sufficient system resources
that the MQPUT or MQPUT1 operation can proceed. available in the system to satisfy the running of API
Exerciser.
Response: Supply some text in the editable area so
that the MQPUT or MQPUT1 operation can proceed. Response: Shut some other applications down and try
running the API Exerciser again.
AMQ4301 Please supply some text in order for the
MQPUT operation to succeed. AMQ4307 API Exerciser encountered a COM
failure and cannot continue. Please
Explanation: No text has been supplied for the user so
ensure that WebSphere MQ has been
that the MQPUT operation may proceed.
correctly installed and configured and
Response: Supply some text in the editable area so that your user id. is a member of the
that the MQPUT may proceed. mqm group.
Explanation: When the API Exerciser started, it was
AMQ4302 Please supply some text in order for the unable to make a COM connection to WebSphere MQ
MQPUT1 operation to succeed. Services.
Explanation: No text has been supplied for the user so Response: Ensure that WebSphere MQ has been
that the MQPUT1 operation may proceed. correctly installed and configured, and that your user
ID is a member of the mqm group. If the problem
Response: Supply some text in the editable area so persists, refer to your systems administrator.
that the MQPUT1 may proceed.
AMQ4308 API Exerciser cannot continue. Please

AMQ4303 The command server for the queue ensure that the userid you are using is a
manager [%s] is not started. Start the member of the mqm group.
command server and try again.
Explanation: In order for the API Exerciser to AMQ4309 API Exerciser cannot continue. Please
function, a command server must be running. ensure that the userid you are using is a
Response: Either start the command server from the member of the Administrator group.
MQServices application or run strmqcsv <Queue
Manager> from the command line.
AMQ4304 API Exerciser cannot enumerate objects

for queue manager [%s].
Explanation: The API Exerciser encountered a
problem trying to enumerate queues.
Response: Ensure that the command server is running
(from the Service application) and that there are queues
configured for the queue manager.
AMQ4305 There are no queue managers present in

the system. Please create one and try
again.
Explanation: The API Exerciser could not find any
queue managers on the system.
Response: Use the Services application to create one
or run crtmqm <Queue Manager>.
4350-4764 - Installation messages

AMQ4350 Setup cannot continue; a later version of AMQ4363 Setup could not detect the Windows
this product is installed. NT® Service Pack level (Service Pack 3
or later is required). Is Service Pack 3 or
Explanation: Installation detected that a version of
later installed?
this product later than version 5.3 is already installed
on the computer.
AMQ4364 Setup could not detect the Windows NT
Response: Do not attempt to install version 5.3 when
Service Pack level (Service Pack 6a or
a later version is already installed.
later is required). Is Service Pack 6a or
later installed?
AMQ4351 Uninstallation cannot continue;
uninstallation is already running.
AMQ4365 Setup cannot continue because Service
Explanation: An attempt was made to run two copies Pack 3 is not installed.
of uninstallation at once.
Response: Run only one copy of uninstallation at a AMQ4366 Setup cannot continue because Service
time. Pack 6a or later is not installed.
AMQ4352 Setup cannot continue; a supported AMQ4367 Setup cannot continue because Internet
version of Windows® is required. Explorer Version 4.01 SP1 is not
installed.
AMQ4353 Setup cannot continue; ’%s’ is not an
Administrator. AMQ4368 Select at least one component to
proceed.
Explanation: The user running installation does not
have administrator authority.
AMQ4369 The ’Web Administration Server’
Response: Log off and log back on using a user ID component requires the ’Server’
with administrator authority. component.
AMQ4354 No repository computer name entered. AMQ4370 Uninstallation of the ’Server’ component
requires uninstallation of the ’Web
AMQ4355 Repository computer name is not valid. Administration Server’ component.
AMQ4356 Enter a remote computer name. AMQ4371 The ’Documentation in Other

Languages’ component requires the
’Documentation in English’ component.
AMQ4357 Registration failed for file ’%s’ (code
0x%8.8lx).
AMQ4372 Uninstallation of the ’Documentation in
English’ component requires
AMQ4358 Unregistration failed for file ’%s’ (code uninstallation of the ’Documentation in
0x%8.8lx). Other Languages’ component.
AMQ4359 Unable to register file ’%s’. AMQ4373 There is not enough space on drive %s
(program files) to install these
AMQ4360 Unable to unregister file ’%s’. components. Please free up some disk
space or modify your selections
AMQ4361 Uninstall cannot continue;

Administrator logon required. AMQ4374 There is not enough space on drive %s
(data files) to install these components.
Please free up some disk space or
AMQ4362 Failed to create the default modify your selections
configuration.
are readable by an administrator. Check that there is

AMQ4375 The program files top-level folder is not
enough space on the drive containing the data files
valid.
folder (where the configuration is being saved in file
Explanation: The program files top-level folder is not \config\config.reg). If the error persists, contact your
a valid path. systems administrator.
Response: Enter a valid path.
AMQ4385 Unknown language specified (’%s’)
AMQ4376 The data files top-level folder is not
valid. AMQ4386 Codepage (%d) for specified language
not available.
Explanation: The data files top-level folder is not a
valid path.
AMQ4387 Before Setup can display help, this
Response: Enter a valid path.
computer’s help system needs
upgrading to HTML Help 1.3. Would
AMQ4377 The log files folder is not valid. you like to upgrade now? (You might
need to restart the computer.)
Explanation: The log files folder name is not a valid
path.
AMQ4388 WebSphere MQ Setup or uninstallation
Response: Enter a valid path. is already running.
AMQ4378 A root folder is not allowed for the AMQ4389 Setup could not create a local ’mqm’
program files top-level folder. group (code %d).
Explanation: WebSphere MQ cannot be installed in a Explanation: An error occurred creating a local user
root folder, for example ’c:\’. group called ’mqm’.
Response: Enter a non-root folder. Response: Review the installation log file for details of
any problems. If the error persists, contact your
AMQ4379 A root folder is not allowed for the data systems administrator.
files top-level folder.
Explanation: WebSphere MQ cannot be installed in a AMQ4390 Setup could not create a global ’Domain
root folder, for example ’c:\’. mqm’ group (code %d).
Response: Enter a non-root folder. Explanation: An error occurred creating a local user
group called ’mqm’.
AMQ4380 A root folder is not allowed for the log Response: Review the installation log file for details of
files folder. any problems. If the error persists, contact your
Explanation: WebSphere MQ cannot be installed in a
root folder, for example ’c:\’.
AMQ4391 Setup could not find the global ’Domain
Response: Enter a non-root folder. mqm’ group.
Explanation: The global ’mqm ’ group was created,
AMQ4381 There is not enough space on drive %s but could not then be found.
(log files) to install these components.
Please free up some disk space or Response: Review the installation log file for details of
modify your selections any problems. If the error persists, contact your
AMQ4382 Unable to create or replace folder ’%s’

AMQ4392 Setup could not add the global ’Domain
mqm’ group to the local ’mqm’ group
AMQ4383 Uninstallation cannot continue; failed to (code %d).
save queue manager configuration.
Explanation: An error occurred adding the global
Explanation: An error occurred while saving the ’mqm’ group to the local ’mqm’ group.
current queue manager configuration to a file.
Response: Review the installation log file for details of
Response: Check that the registry keys under any problems. If the error persists, contact your
’HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ’ systems administrator.
AMQ4393 No ports were specified; no listeners AMQ4709 Error creating TCP/IP listener for queue
will be created. manager ’%s’.
AMQ4394 No queue managers are selected for AMQ4710 Error updating ’%s’ environment
remote administration. variable.
AMQ4395 One or more ’Server’ component AMQ4711 One or more problems occurred during
prerequisites were not selected; the uninstallation. Review ’%s’ for details
component cannot be installed.
Explanation: Uninstallation was only partially
successful.
AMQ4396 One or more prerequisite upgrades were
Response: If the installation log file is available,
not selected; WebSphere MQ will not
review it for details of any problems. If the error
operate correctly.
persists, contact your systems administrator.
AMQ4397 Cannot install on a network drive (drive

AMQ4712 The WebSphere MQ Service failed to
%s),
stop.
Explanation: An error occurred trying to stop the
AMQ4703 One or more problems occurred during
WebSphere MQ service
Setup. Review ’%s’ for details
Explanation: Setup was only partially successful.
Response: Review the installation log file for details of systems administrator.
any problems.
AMQ4713 The WebSphere MQ Service failed to
AMQ4704 If specified, TCP/IP domain must be start.
’%s’
Explanation: An error occurred trying to start the
AMQ4705 Current maintenance level is ’%s’.
Re-apply maintenance after Setup
completes.
Explanation: Some service has been applied to the
current installation. Installation or reinstallation of
AMQ4714 Failed to delete the WebSphere MQ
WebSphere MQ components might regress some files.
Service (code %d).
Response: Review the instructions that came with the
Explanation: An error occurred trying to delete the
service that was applied. If necessary re-apply the
service.
Response: Review the installation log for details of
AMQ4706 Dialog ’%s’ failed.
AMQ4707 Error migrating ’%s’.

AMQ4715 Failed to add the WebSphere MQ
Explanation: An error occurred migrating a .ini file to Service.
the registry.
Explanation: An error occurred trying to create the
Response: Review the installation log file for details of WebSphere MQ service
Response: Review the installation log for details of
AMQ4708 Error creating remote administration
channel for queue manager ’%s’.
AMQ4716 Can’t load ’%s’.
AMQ4717 Can’t start dialog ’%s’. AMQ4726 The ’Internet Gateway’ component
requires the ’Windows NT Client’
component.
AMQ4718 Can’t load performance counters (code
0x%8.8lx).
AMQ4727 Uninstallation of the ’Windows NT
Explanation: An error occurred trying to register the
Client’ component requires
WebSphere MQ performance counter library.
uninstallation of the ’Internet Gateway’
Response: Review the installation log for details of component.
AMQ4728 Setup could not create a default
configuration because some files were
AMQ4719 Error migrating queue manager locked. Run WebSphere MQ First Steps
command files. after restarting the computer.
Explanation: An error occurred migrating queue
manager command files. AMQ4729 You cannot install the Windows Client
from the client CD because WebSphere
Response: Review the installation log for details of MQ server components are already
any problems. If the error persists, contact your installed on this computer. To install the
systems administrator. Windows Client on this computer, use
the server CD.
AMQ4720 Error initializing security environment. Explanation: An attempt has been made to install a
feature using the Windows client CD when one or
AMQ4721 WebSphere MQ messages language more features have already been installed using the
changed to %s. server CD. This is not allowed. Either uninstall the
server features first, or use only the server CD.
AMQ4722 Setup cannot continue without VGA or Response: Review the installation log file for details of
better screen resolution. any problems. If the error persists, contact your
Explanation: Setup was run using a monitor
resolution less than VGA resolution.
AMQ4730 Java™ support is now separately
Response: Use a monitor with resolution equal to or available; see the installation notes.
better than 640 x 480 pixels. Setup will delete existing MQSeries®
V5.1 Java files.
AMQ4723 Error during uninstaller initialization.
You might not be able to uninstall AMQ4731 Setup cannot continue without SVGA or
WebSphere MQ. better screen resolution (800 x 600).
AMQ4724 Error restoring queue manager AMQ4732 No installation language specified. Use
configuration. the TRANSFORMS property.
Explanation: An error occurred restoring queue Explanation: An attempt was made to invoke an
manager configuration from the config.reg file in the installation without specifying a user-interface
data directory. language. Use the TRANSFORMS property to specify a
Response: Review the installation log file for details of language.
any problems. If the error persists, contact your Response: Review the installation log file for details of
systems administrator. any problems. If the error persists, contact your
AMQ4725 The Server feature cannot be installed
without 800 x 600 or better screen AMQ4733 Unable to launch program ’%s’.
resolution.
Explanation: An error occurred trying to execute the
indicated program.
AMQ4734 Can’t open file ’%s’. AMQ4744 Have you purchased sufficient license
units to install IBM® WebSphere MQ on
Explanation: Setup was unable to open the indicated
this computer? (For further information
file for reading.
on license units refer to the Quick
Response: Review the installation log file for details of Beginnings book.)
Explanation: You must purchase the appropriate
number of license units for the number of processors in
this computer.
AMQ4735 Error %1 reading response file ’%2’.
Response: If you have purchased the appropriate
Explanation: An error occurred. number of license units, reply ″Yes″, otherwise reply
″No″.
systems administrator. AMQ4745 After the upgrade you might need to
reboot. Is it OK to proceed?
AMQ4736 Error %1 creating response file ’%2’.
AMQ4745 This installation requires %d license
Explanation: An error occurred restoring queue units to have been purchased with IBM
manager configuration from the config.reg file in the WebSphere MQ (for further information
data directory. on license units refer to the Quick
Response: Review the installation log file for details of Beginnings book). If you do not know
any problems. If the error persists, contact your how many license units have been
systems administrator. purchased, ask your system
administrator or vendor. Have sufficient
license units been purchased for this
AMQ4737 Unknown value ’%1’ for property ’%2’ installation?
in ’%3’.
AMQ4746 Setup needs to install or upgrade this

AMQ4738 Repair option is not supported. computer to version 2.0 of Microsoft®
Windows Installer. (MSI). OK to
AMQ4739 One or more problems occurred. Review proceed (you might need to reboot)?
the trace and/or log file for details. Explanation: A version of Microsoft Windows Installer
(MSI) earlier than 2.0 is installed. WebSphere MQ Setup
AMQ4740 Unknown feature(s) ’%1’ in requires at least version 2.0.
command-line property ’%2’. Response: Reply ″Yes″ to install MSI version 2.0,
Explanation: A property, for example ADDLOCAL, otherwise ″No″. To install WebSphere MQ, version 2.0
containing a feature-list was specified, but one or more is required.
of the feature names was invalid.
Response: Remove the invalid feature name. If the AMQ4747 You must reboot before continuing with
error persists, contact your systems administrator. installation. Do you want to reboot
now?
AMQ4742 Unknown feature(s) ’%1’ in property

’%2’ in ’%3’. AMQ4748 Can’t install on top of an Early-Release
installation. Uninstall the Early Release
Explanation: A property, for example ADDLOCAL, first.
containing a feature-list was specified, but one or more
of the feature names was invalid. Explanation: An attempt was made to install
WebSphere MQ on top of an Early Version (″beta″).
Response: Remove the invalid feature name. If the
error persists, contact your systems administrator. Response: Uninstall the Early Version before
proceeding. If the error persists, contact your systems
administrator.
AMQ4743 Unknown property ’%1’ in ’%2’.
Response: For more information, see the WebSphere

AMQ4749 Can’t install an Early Release on top of
MQ Installation Guide.
Version %s. Uninstall first.
Explanation: An attempt was made to install an Early
AMQ4754 SupportPac MS0J (Web Administration
Version (″beta″) on top of another version of
Server) is installed on this computer.
WebSphere MQ.
You must uninstall the SupportPac
Response: Uninstall the existing version of WebSphere before uninstalling WebSphere MQ
MQ before proceeding with the Early Version. If the server.
error persists, contact your systems administrator.
AMQ4756 IBM WebSphere MQ Version %s is not
AMQ4750 Can’t convert. Need production version installed.
of WebSphere MQ.
Explanation: The property TRIALTOPROD has been AMQ4757 IBM WebSphere MQ files are in use.
specified but the WebSphere MQ version on the CD is Stop activity and retry.
not a production version.
Explanation: One or more WebSphere MQ files are
Response: Do not specify TRIALTOPROD if the being used by processes running on the system.
version of WebSphere MQ you are using is not a
Response: Ensure that all queue managers, listeners,
production version. If the error persists, contact your
channels and WebSphere MQ services are stopped. Use
the Windows task manager to ensure that there are no
processes running with an ″amq″, ″runmq″, or ″strmq″
AMQ4751 Can’t convert. Installed product is not prefix. Stop any tools used to monitor WebSphere MQ
an Evaluation Copy. and stop any Performance Monitor tasks. If the process
locking WebSphere MQ files cannot be identified,
Explanation: The property TRIALTOPROD has been
installation can usually procede following a reboot,
specified but the WebSphere MQ version installed is
with the WebSphere MQ service disabled.
not an Evaluation Copy.
Response: Do not specify TRIALTOPROD if the
AMQ4758 Maintenance levels out of sequence.
installed version of WebSphere MQ is not an
Latest maintenance applied is %s.
Evaluation Copy. If the error persists, contact your
AMQ4759 SupportPac MA0C (Publish And
Subscribe) is installed on this system.
AMQ4752 You have insufficient license units for
You must uninstall the SupportPac
this installation, and you must purchase
before installing WebSphere MQ server;
additional units from your vendor. You
see the Installation Guide.
can continue to install WebSphere MQ,
but this status will be recorded in the
error log. For information on how to AMQ4760 Error installing %s. Examine log file
inform WebSphere MQ when you have ’%s’.
purchased sufficient license units, refer
to the System Administration Guide. Do
AMQ4761 Error uninstalling %s. Examine log file
you want to proceed with WebSphere
’%s’.
MQ installation?
Explanation: You replied ″No″ to message number
AMQ4762 No maintenance is installed.
AMQ4744.
Response: Reply ″Yes″ to continue the installation, or
AMQ4763 Cannot overwrite WebSphere MQ
″No″ to cancel. Make sure that you purchase the
Version %1 with Version %2.
appropriate number of license units.
Explanation: The service level you are trying to install
™ is less than that already installed. The installation will
AMQ4753 SupportPac MC74 (Microsoft Cluster
not proceed.
Server support) is installed on this
system. You must uninstall the Response: Check that you are attempting to install the
SupportPac before installing WebSphere latest CSD.
MQ server; see the Installation Guide.
Explanation: WebSphere MQ installation requires that
SupportPac MC74 be uninstalled.
AMQ4764 WebSphere MQ ’Client’ feature at

version %1 maintenance level %2 is not
installed.
Chapter 3. 5000-5999 - Installable services
messages.
operating system has terminated the process so that a

AMQ5005 Unexpected error
new process can be created.
Explanation: An unexpected error occurred in an AMQ5010 The system is restarting the WorkLoad
internal function of the product. Management Server process.
Response: Save the generated output files and contact Severity: 10 : Warning
your IBM support center.
Explanation: The system has detected that the
WorkLoad Management server process (amqzlwa0,
AMQ5006 Unexpected error: rc = <insert_1> pid:<insert_1>) has stopped and is restarting it.
Severity: 20 : Error Response: Save the generated output files which may
indicate the reason why the WorkLoad Management
Explanation: An unexpected error occurred in an
process stopped. If the reason the WorkLoad
internal function of the product.
Management Server process stopped is a problem in a
Response: Save the generated output files and contact WorkLoad Management user exit, correct the problem,
your IBM support center. otherwise contact your IBM support center.
AMQ5008 An essential WebSphere MQ process AMQ5011 The Queue Manager ended for reason
<insert_1> (<insert_3>) cannot be found <insert_1> <insert_3>
and is assumed to be terminated.
Explanation: The Queue Manager ended because of a
Explanation: 1) A user has inadvertently terminated previous error <insert_1> or <insert_3>
the process. 2) The system is low on resources. Some
Response: This message should be preceded by a
operating systems terminate processes to free resources.
message or FFST information from the internal routine
If your system is low on resources, it is possible it has
that detected the error. Take the action associated with
terminated the process so that a new process can be
the earlier error information.
created.
Response: WebSphere MQ will stop all MQ processes.
AMQ5019 Unable to access program <insert_3>.
Inform your systems administrator. When the problem
is rectified WebSphere MQ can be restarted. Severity: 40 : Stop Error
Explanation: A request was made to execute the
AMQ5009 WebSphere MQ agent process <insert_1> program <insert_3>, however the operation was
has terminated unexpectedly. unsuccessful because the program could not be found
in the specified location.
Response: Check the definition of the service specifies
Explanation: WebSphere MQ has detected that an
the correct and full path to the program to run. If the
agent process has terminated unexpectedly. The queue
path is correct then verify that the program exists in
manager connection(s) that this process is responsible
the specified location and that WebSphere MQ userid
for will be broken.
has permission to access it.
Response: Use any previous FFSTs to determine the
reason for the failure. Try to eliminate the following
AMQ5020 Permission denied attempting to execute
reasons before contacting your IBM support center.
program <insert_3>.
1) A user has inadvertently terminated the process.
2) The system is low on resources. Some operating Severity: 40 : Stop Error
systems terminate processes to free resources. If your
system is low on resources, it is possible that the
program <insert_3>, however the operation was
unsuccessful because the WebSphere MQ operating

environment has insufficient permissions to access the
AMQ5026 The Listener <insert_3> has started.
program file.
ProcessId(<insert_1>).
Response: Check the access permissions of the of the
program to be executed and if necessary alter them to
include execute permission for the WebSphere MQ Explanation: The Listener process has started.
userId. Also check that the WebSphere MQ userId has
Response: None.
search access on all directories which compose the path
to the program file.
AMQ5027 The Listener <insert_3> has ended.
AMQ5021 Unable to start program <insert_3>.
Explanation: The Listener process has ended.
program <insert_3> however the operation was Response: None.
unsuccessful. Reasons for the failure may include
a shortage of available system resources
a problem with the program to be started AMQ5028 The Server <insert_3> has started.
Response: If the problem persists then the WebSphere
MQ error logs should be consulted for further Severity: 0 : Information
information related to this error. The Operating System Explanation: The Server process has started.
error recording facilities should also be consutled for
information relating to shortage of system resources. Response: None.
AMQ5022 The Channel Initiator has started. AMQ5029 The Server <insert_3> has ended.
ProcessId(<insert_1>). ProcessId(<insert_1>).
Explanation: The Channel Initiator process has Explanation: The Server process has ended.
started. Response: None.
Response: None.
AMQ5030 The Command <insert_3> has started.
AMQ5023 The Channel Initiator has ended. ProcessId(<insert_1>).
ProcessId(<insert_1>). Severity: 0 : Information
Severity: 0 : Information Explanation: The Command has started.
Explanation: The Channel Initiator process has ended. Response: None.
Response: None.
AMQ5032 Error (<insert_4>) accessing file
AMQ5024 The Command Server has started. <insert_3>.
ProcessId(<insert_1>). Severity: 40 : Stop Error
Severity: 0 : Information Explanation: While attempting to access the file
Explanation: The Command Server process has <insert_3> the error <insert_4> occurred.
started. Response: Use the information contained in the error
Response: None. to locate and correct the cause of the failure.
AMQ5025 The Command Server has ended. AMQ5036 Error detected processing line <insert_1>,
ProcessId(<insert_1>). position <insert_2> in service
environment file.
Explanation: The Command Server process has ended.
Explanation: While processing the environment file
Response: None. <insert_3> an error was detected on line <insert_1> at
position <insert_2>. Possible causes are
Variable name too long
Variable value too long Response: Consult the Queue Manager error logs for
Incorrectly formed line. Lines must be in the format further details on the cause of the failure.
<name>=<value>. There should be no blank characters
in name field. All characters following the ’=’ are part
AMQ5044 <insert_3> task operation restricted due
of the value field.
to Reason Code <insert_1>.
Response: This error will not stop the command from
executing but any data on the invalid line is not
processed. Explanation: The <insert_3> task encountered a
non-fatal error which may effect the operation of the
task.
AMQ5037 The Queue Manager task <insert_3> has
started. Response: Using the Reason Code <insert_1> and any
previous messages recorded in the Error Logs correct
the error. It may be necessary to restart the Queue
Explanation: The Utility Task Manager, Manager in order remove the restriction caused by the
processId(<insert_1>) type(<insert_2>), has started the failure.
<insert_3> task.
Response: None. AMQ5045 System reconfiguration event received
AMQ5038 The Queue Manager task <insert_3>
Explanation: The Queue Manager received a system
failed to start with error-code <insert_1>.
re-configuration event. This is likely to have been
Severity: 40 : Stop Error caused by an administrative change in the
configuration of the machine (for example dynamically
Explanation: The Utility Task Manager, attempted to
adding or removing resources such as memory or
start the task <insert_3> but the start request failed with
processors).
error code <insert_1>.
Response: No action is required unless this
Response: The failure to start the identified task may
notification was unexpected.
not be critical to queue-manager operation however all
of the queue manager functionality may not be
available. Further details of the failure are available in AMQ5203 An error occurred calling the XA
WebSphere MQ error logs. interface.
AMQ5041 The Queue Manager task <insert_3> has
Explanation: The error number is <insert_2> where a
ended.
value of
Severity: 0 : Information 1 indicates the supplied flags value of <insert_1> was
invalid,
Explanation: The Queue Manager task <insert_3> has
2 indicates that there was an attempt to use threaded
ended.
and non-threaded libraries in the same process,
Response: None. 3 indicates that there was an error with the supplied
queue manager name <insert_3>,
4 indicates that the resource manager id of <insert_1>
AMQ5042 Request to start <insert_3> failed. was invalid,
Severity: 40 : Stop Error 5 indicates that an attempt was made to use a second
queue manager called <insert_3> when another queue
Explanation: The request to start the process manager was already connected,
<insert_3> failed. 6 indicates that the Transaction Manager has been
Response: Consult the Queue Manager error logs for called when the application isn’t connected to a queue
further details on the cause of the failure. manager,
7 indicates that the XA call was made while another
call was in progress,
AMQ5043 Statistics recording is unavailable due to 8 indicates that the xa_info string <insert_3> in the
error code <insert_1>. xa_open call contained an invalid parameter value for
Severity: 40 : Stop Error parameter name <insert_4>,
9 indicates that the xa_info string <insert_3> in the
Explanation: The statistics collection task was unable xa_open call is missing a required parameter, parameter
to start due the error code <insert_1>. Statistics name <insert_4>, and
collection will be unavailable until the problem is 10 indicates that MQ was called in dynamic registration
rectified and the Queue Manager is restarted. mode but cannot find the ax_reg and ax_unreg
Chapter 3. 5000-5999 - Installable services 39

functions ! Either call MQ in non-dynamic registration managers, such as DB2, can participate in global units
mode or supply the correct library name via the AXLIB of work.
parameter in the xa_open string.
Response: Look for a previous message outlining the
Response: Correct the error and try the operation reason for the load failure. Message AMQ6175 should
again. have been issued if the load failed because of a system
error. If this is the case then follow the guidance given
in message AMQ6175 to resolve the problem. In the
AMQ5204 A non-threaded application tried to run
absence of prior messages or FFST information related
as a Trusted application.
to this problem check that the AX support module and
Severity: 10 : Warning the mqmax library have been correctly installed on
your system.
Explanation: Only applications linked with the
threaded MQ libraries can run as Trusted applications.
AMQ5501 There was not enough storage to satisfy
Response: Make sure that the application is relinked the request
with the threaded MQ libraries, or set the the
environment variable MQ_CONNECT_TYPE to Severity: 20 : Error
STANDARD.
Explanation: An internal function of the product
attempted to obtain storage, but there was none
AMQ5205 File or directory <insert_3> not owned available.
by user <insert_4>.
Response: Stop the product and restart it. If this does
Severity: 40 : Stop Error not resolve the problem, save the generated output files
and contact your IBM support center.
Explanation: WebSphere MQ has detected that the file
or directory <insert_3> is not owned by the user
<insert_4>. This is not necessarily an error but you AMQ5502 The CDS directory name <insert_3> is
should investigate further if this is unexpected. not in the correct format.
Response: Severity: 20 : Error
If this is unexpected then you should alter the
Explanation: An internal function of the DCE Naming
ownership of the file or directory back to the user
service found a CDS directory name in the wrong
<insert_4>.
format. The name was expected to start with either
If this is expected, then WebSphere MQ will continue
’/...’ for a fully qualified name (from global root), or
however WebSphere MQ will be unable to verify the
’/.:’ for a partially qualified name (from local cell root).
security of this file or directory. If the access
permissions are too strict then you may encounter Response: Save the generated output files and contact
problems if WebSphere MQ cannot access the contents your IBM support center.
of the file or directory. If the access permissions are too
relaxed then there may be an increased risk to the
AMQ5503 The name of the local DCE cell cannot
security of the WebSphere MQ system.
be determined, status = <insert_1>
AMQ5206 Duplicate parameters detected.
Explanation: The DCE Naming Service attempted to
determine the name of the local DCE cell by calling
Explanation: WebSphere MQ has detected that the ’dce_cf_get_cell_name()’, which returned a nonzero
activity about to be displayed contains two or more return code.
parameters in the same group with the same parameter
Response: Save the generated output files and contact
identifier. The activity may be displayed incorrectly.
Response: Inform the author of the activity that there
may be an error in it.
AMQ5504 DCE error. No value for the XDS
attribute found.
AMQ5358 WebSphere MQ could not load AX
support module <insert_3>.
Explanation: The DCE Naming service called om_get()
to get the entry from the object returned by ds_read().
Explanation: An error has occurred loading the AX Although the status was correct, no objects were
support module <insert_3>. This module needs to be returned.
loaded so that dynamically-registering resource
AMQ5505 DCE error. No value for the XDS AMQ5510 DCE error. <insert_3> returned with
attribute number <insert_1> found. problem <insert_1>.
Explanation: The DCE Naming service called om_get() Explanation: The DCE Naming service found an
to get the entry from the object returned by ds_read(). unexpected XDS error.
Although the status was correct, no objects were
returned.
AMQ5511 Installable service component <insert_3>
returned <insert_4>.
AMQ5506 DCE error. <insert_3> returned <insert_1>
for attribute number <insert_2>.
Explanation: The internal function, that adds a
component to a service, called the component
Explanation: The DCE Naming service queried an initialization process. This process returned an error.
object by calling <insert_3> which returned a nonzero
Response: Check the component was installed
return code.
correctly. If it was, and the component was supplied by
Response: Save the generated output files and contact IBM, then save the generated output files and contact
your IBM support center. your IBM support center. If the component was not
supplied by IBM, save the generated output files and
follow the support procedure for that component.
AMQ5507 DCE error. <insert_3> failed for an
unknown reason.
AMQ5511 (iSeries) An installable service component
returned an error.
Explanation: An unexpected error occurred in an
internal function of the DCE Naming service.
Explanation: Installable service component <insert_3>
returned <insert_4>. The internal function, that adds a
component to a service, called the component
initialization process. This process returned an error.
AMQ5508 DCE error. The requested attribute is
not present.
Severity: 20 : Error IBM, then save the generated output files and contact
your IBM support center. If the component was not
Explanation: The DCE Naming service was supplied by IBM, save the generated output files and
attempting to extract the value from an attribute, but follow the support procedure for that component.
the attribute cannot be found in the XDS object.
Response: Save the generated output files and contact AMQ5512 Installable service component <insert_3>
your IBM support center. returned <insert_4> for queue manager
name = <insert_5>.
AMQ5509 DCE error. The XDS workspace cannot Severity: 20 : Error
be initialized.
Explanation: An installable service component
Severity: 20 : Error returned an unexpected return code.
Explanation: The DCE Naming service called Response: Check the component was installed
’ds_initialize()’ to initialize the XDS workspace, but correctly. If it was, and the component was supplied by
’ds_initialize()’ returned a nonzero return code. IBM, then save the generated output files and contact
Response: Save the generated output files and contact your IBM support center. If the component was not
your IBM support center. supplied by IBM, save the generated output files and
follow the support procedure for that component.

included a stanza for the installable service <insert_3>
AMQ5512 (iSeries) An installable service component
component <insert_4> with the module <insert_5>. The
returned an unexpected return code.
system returned <insert_1> when it tried to load this
Severity: 20 : Error module. The Queue Manager is continuing without this
component.
Explanation: Installable service component <insert_3>
returned <insert_4> for queue manager name = Response: Make sure that the module can be loaded.
<insert_5>. Put the module into a directory where the system can
load it, and specify its full path and name in the
configuration data . Then stop and restart the queue
manager.
IBM, then save the generated output files and contact
your IBM support center. If the component was not
supplied by IBM, save the generated output files and AMQ5520 (iSeries) The system could not load a
follow the support procedure for that component. module. The Queue Manager is
continuing without this component.
AMQ5513 <insert_3> returned <insert_1>. Severity: 10 : Warning
Severity: 20 : Error Explanation: The queue manager configuration data
included a stanza for the installable service <insert_3>
Explanation: An unexpected error occurred.
component <insert_4> with the module <insert_5>. The
Response: Save the generated output files and contact system returned <insert_1> when it tried to load this
your IBM support center. module. The Queue Manager is continuing without this
component.
AMQ5519 Bad DCE identity. Status = <insert_1>, Response: Make sure that the module can be loaded.
auth = <insert_2>, keytab file = Put the module into a directory where the system can
<insert_3>, principal = <insert_4>. load it, and specify its full path and name in the
configuration data . Then stop and restart the queue
Severity: 20 : Error manager.
Explanation: The keytab file was not installed
correctly, or the WebSphere MQ user ID has a different AMQ5521 The system could not open ″<insert_3>″.
password from that used to create the keytab file.
Response: Make sure that the MQ user ID defined
when the product was installed has the same password Explanation: The system failed to open the default
as that defined by the keytab file, and that the keytab object ″<insert_3>″ at connect time for reason
file has been installed correctly. <insert_4>. This may be because ″<insert_3>″ has been
deleted or changed.
AMQ5519 (iSeries) Bad DCE identity. Response: Recreate the default objects by running
″strmqm -c <qmgr>″ (where <qmgr> is the name of the
Severity: 20 : Error queue manager) and retry the application.
Explanation: Status = <insert_1>, auth = <insert_2>,
keytab file = <insert_3>, principal = <insert_4>. The AMQ5522 A WebSphere MQ installable service
keytab file was not installed correctly, or the WebSphere component could not be initialized.
MQ user ID has a different password from that used to
create the keytab file. Severity: 20 : Error
Response: Make sure that the MQ user ID defined Explanation: An installable service component
when the product was installed has the same password returned an unexpected return code.
as that defined by the keytab file, and that the keytab
Response: Check the queue manager error logs for
file has been installed correctly.
messages explaining which installable service could not
be initialized and why that service could not be
AMQ5520 The system could not load the module initialized. Check the component was installed
<insert_5> for the installable service correctly. If it was, and the component was supplied by
<insert_3> component <insert_4>. The IBM, then save the generated output files and contact
system return code was <insert_1>. The your IBM support center. If the component was not
Queue Manager is continuing without supplied by IBM, save the generated output files and
this component. follow the support procedure for that component.
Explanation: The queue manager configuration data
1) Queue
AMQ5524 The WebSphere MQ Object Authority
2) Namelist
Manager has failed to migrate authority
3) Process
data.
5) Queue Manager
Response: To extend access to this object use the
Explanation: The Object Authority Manager has setmqaut command, see the WebSphere MQ System
attempted to migrate existing queue manager authority Administration documentation for details.
data from a previous version of an Object Authority
Manager and failed.
AMQ5529 The Remote OAM Service is not
Response: Check this log for any previous related available.
messages, follow their recommendations then restart
the queue manager.
Explanation: The Remote OAM service is not
available. The <insert_1> call returned <insert_1>, errno
<insert_2> : <insert_3>. The context string is <insert_4>
Manager has failed.
Response: To extend access to this object use the
setmqaut command, see the WebSphere MQ System
Explanation: The Object Authority Manager has failed Administration documentation for details.
to complete an MQ request.
Response: Check the queue manager error logs for AMQ5600 Usage: crtmqm [-z] [-q] [-c Text] [-d
messages explaining the failure and try to correct the DefXmitQ] [-h MaxHandles]
problem accordingly. [-g ApplicationGroup]
Explanation: This shows the correct usage.
Manager has failed with reason
<insert_1> Response: None.
AMQ5601 [-t TrigInt] [-u DeadQ] [-x MaxUMsgs]
Explanation: The Object Authority Manager has failed
[-lp LogPri] [-ls LogSec]
an operation on the Object Authority Manager’s data
queue <insert_3> with reason <insert_1>. Severity: 0 : Information
Response: Investigate why the error has occured and Response: None.
correct the problem.
AMQ5602 [-lc | -ll] [-lf LogFileSize] [-ld LogPath]
AMQ5527 The WebSphere MQ Object Authority QMgrName
Manager has failed to locate an essential
authority file Severity: 0 : Information
Severity: 20 : Error Explanation: This shows the correct usage.
Explanation: The Object Authority Manager has failed Response: None.

to locate the authority file <insert_3>. The migration of
authority data cannot continue until the file has been AMQ5602 (iSeries) [-ll] [-lf LogFileSize] [-ld
restored. The queue manager will shutdown. LogPath] [-lz ASPNum] QMgrName
Response: Restore the authority file mentioned above Severity: 0 : Information
and restart the queue manager.
AMQ5528 The WebSphere MQ Object Authority Response: None.

Manager has failed to locate an object’s
authority file AMQ5603 Usage: dltmqm [-z] QMgrName
Severity: 20 : Error Severity: 0 : Information
Explanation: The Object Authority Manager has failed Explanation: This shows the correct usage.
to locate the authority file for the object <insert_3> of
type (<insert_1>). The authority access to this object Response: None.
will initially be limited to members of the mqm group.
Where type is one of the following:

AMQ5604 Usage: dspmqaut [-m QMgrName] [-n AMQ5610 (Unix) Usage: strmqtrc [-m QMgrName]
ObjName] -t ObjType (-p Principal | -g [-e] [-t TraceType] [-x TraceType]
Group) [-s ServiceComponent] [-l MaxFileSize] [-d UserDataSize]
Response: None. Explanation: This applies to UNIX systems.
MaxFileSize is the maximum size of a trace file in
millions of bytes. UserDataSize is the size of user data
AMQ5605 Usage: endmqm [-z] [-c | -w | -i | -p]
to be traced in bytes.
QMgrName
Response: None.
AMQ5610 (Windows) Usage: strmqtrc [-t TraceType]
Response: None. [-x TraceType] [-l MaxFileSize] [-d
UserDataSize]
AMQ5606 Usage: setmqaut [-m QMgrName] [-n Severity: 0 : Information
ObjName] -t ObjType (-p Principal | -g
Explanation: This applies to Windows NT and
Group) [-s ServiceComponent]
Windows 2000 systems only. MaxFileSize is the
Authorizations
maximum size of a trace file in millions of bytes.
Severity: 0 : Information UserDataSize is the size of user data to be traced in
bytes.
Response: None.
Response: None.
AMQ5607 Usage: strmqm [-a|-c|-r][-d
none|minimal|all][-z][-ns] [QMgrName] AMQ5611 (Unix) Usage: endmqtrc [-m QMgrName]
[-e] [-a]
Explanation: This applies to UNIX systems.
Response: None.
Response: None.
AMQ5608 Usage: dspmqtrn [-m QMgrName] [-e]
[-i] AMQ5611 (Windows) Usage: endmqtrc
Explanation: This shows the correct usage. Explanation: This applies to Windows NT and
Windows 2000 systems only.
Response: None.
Response: None.
AMQ5609 Usage: rsvmqtrn -m QMgrName (-a |
((-b | -c | -r RMId) AMQ5612 Usage: dspmqtrc [-t TemplateFile] [-hs]
Transaction,Number)) [-o OutputFileName] [-C
InputFileCCSID] InputFileName(s)
Explanation: Options: -t Template file for formatting
Response: None. trace data -h Skip the trace file header -s Summary
(format only the trace header) -o Save trace output to
AMQ5610 (iSeries) Usage: strmqtrc [-m QMgrName] file -C Specifies the CCSID value for the input file
[-e] [-t TraceType] [-o mqm|pex|all] [-x Response: None.
TraceType] [-l MaxFileSize] [-d
UserDataSize]
AMQ5613 Usage: dspmq [-m QMgrName] [-o
Severity: 0 : Information status | -s] [-o default]
Explanation: None. Severity: 0 : Information
Response: None.
AMQ5614 Usage: setmqtry AMQ5621 process_name
AMQ5622 q_name
Response: None.
AMQ5615 Default objects cannot be created:
CompCode = <insert_1> Reason = AMQ5623 connection_name
<insert_2>.
Explanation: During the creation of a queue manager, AMQ5624 generic_channel_name
using the crtmqm command, the default objects could
not be created. Possible reasons for this include another
command, issued elsewhere, quiescing or stopping the
queue manager, or insufficient storage being available. AMQ5625 generic_process_name
Response: Use the Completion and Reason codes Severity: 0 : Information
shown in the message to determine the cause of the
failure, then re-try the command.
AMQ5626 generic_q_name
AMQ5616 Usage: setmqprd LicenseFile Severity: 0 : Information
AMQ5627 qalias_name
Response: None.
AMQ5628 qmodel_name
AMQ5617 Default objects cannot be created.
Explanation: During the creation of a queue manager AMQ5629 qlocal_name
using the crtmqm command, the default objects could
not be created. The most likely reason for this error is Severity: 0 : Information
that the queue manager was started before the crtmqm
command had completed. AMQ5630 qremote_name
Response: Ensure that the queue manager being Severity: 0 : Information
created is not started before the create request
completes. Stop the queue manager if it is already
running. Restart the queue manager using the strmqm AMQ5631 namelist_name
command with the ’-c’ option to request that the Severity: 0 : Information
default objects are created.
AMQ5632 generic_namelist_name
AMQ5618 integer
AMQ5633 generic_Q_Mgr_name
AMQ5619 string
AMQ5634 generic_cluster_name
AMQ5620 channel_name

AMQ5635 The argument supplied with the -l flag AMQ5652 The Deferred Message process failed to
is not valid. connect to the WebSphere MQ queue
manager for reason <insert_1>.
Explanation: The argument supplied with the -l flag
must be in the range 1 - 4293. Explanation: The WebSphere MQ queue manager
<insert_3> might have generated earlier messages or
Response: Submit the command again with a valid
FFST information explaining why the deferred message
argument.
process (amqzdmaa) could not connect.
Response: Correct any configuration errors.
AMQ5636 cluster_name
Configuration errors that can cause this problem
Severity: 0 : Information include badly configured CLWL Exit modules. If the
problem persists contact your IBM service
representative.
AMQ5637 (AIX) The environment variable EXTSHM
is set to ″ON″. This is incompatable
with the way WebSphere MQ uses AMQ5653 The mqm user is not defined.
shared memory. Reset the environment
variable EXTSHM and retry the
command. Explanation: The system call getpwnam(″mqm″) failed
with errno <insert_1>. The program was running as
<insert_3>.
Explanation: On AIX the environment variable
Response: Create the mqm user as a member of the
EXTSHM causes shared memory segments to be fixed
mqm group and retry the operation.
size. WebSphere MQ expects to be able to extend
shared memory segments.
AMQ5654 Usage: dspmqrte [-c] [-n] [-l Persistence]
Response: Reset the environment variable EXTSHM
[-m QMgrName] [-o] [-p Priority]
and retry the command.
AMQ5646 Usage: setmqcap Processors Explanation: This shows the correct usage of the
DSPMQRTE command.
Response: None.
AMQ5647 Usage: dspmqcap
AMQ5655 [-rq ReplyQName [-rqm
ReplyQMgrName]] [-ro ReportOptions]
AMQ5648 Usage: dmpmqaut [-m QMgrName] [-n
Profile | -l] [-t ObjType] [-p Principal | Explanation: This shows the correct usage of the
-g Group] [-s ServiceComponent] [-e | DSPMQRTE command.
-x]
Response: None.
Response: None. AMQ5656 [-xs Expiry] [-xp Pass] [-qm
TargetQMgrName] [-ac [-ar]]
AMQ5649 generic_authinfo_name Severity: 0 : Information
Severity: 0 : Information Explanation: This shows the correct usage of the
DSPMQRTE command.
AMQ5650 authinfo_name Response: None.
AMQ5657 [-d Delivery] [-f Forwarding] [-s
Activities] [-t Detail]
AMQ5651 qmname
Explanation: This shows the correct usage of the
DSPMQRTE command.
Response: None.
AMQ5807 WebSphere MQ Publish/Subscribe
broker for queue manager <insert_3>
AMQ5658 [-i CorrelId] [-b] [-v Verbosity] [-w ended.
WaitTime] -q TargetQName
Explanation: The WebSphere MQ Publish/Subscribe
Explanation: This shows the correct usage of the broker on queue manager <insert_3> has ended.
DSPMQRTE command.
Response: None.
Response: None.
AMQ5700 listener_name broker for queue manager <insert_3> is
already quiescing.
AMQ5701 service_name Explanation: The endmqbrk command was
unsuccessful because an orderly shutdown of the
Severity: 0 : Information WebSphere MQ Publish/Subscribe broker running on
queue manager <insert_3> is already in progress.
AMQ5749 display_cmd Response: None.
AMQ5808 (iSeries) WebSphere MQ
AMQ5750 filter_keyword Publish/Subscribe broker is already
quiescing.
AMQ5751 operator Explanation: The endmqbrk command was

unsuccessful because an orderly shutdown of the
Severity: 0 : Information broker, running on queue manager <insert_3>, is
already in progress.
AMQ5752 filter_value Response: None.
AMQ5805 WebSphere MQ Publish/Subscribe broker for queue manager <insert_3>
broker currently running for queue starting.
manager. Severity: 0 : Information
Severity: 10 : Warning Explanation: The dspmqbrk command has been
Explanation: The command was unsuccessful because issued to query the state of the WebSphere MQ
queue manager <insert_3> currently has an WebSphere Publish/Subscribe broker. The WebSphere MQ
MQ Publish/Subscribe broker running. Publish/Subscribe broker is currently initializing.
Response: None. Response: None.
AMQ5806 WebSphere MQ Publish/Subscribe AMQ5810 WebSphere MQ Publish/Subscribe

broker started for queue manager broker for queue manager <insert_3>
<insert_3>. running.
Explanation: WebSphere MQ Publish/Subscribe Explanation: The dspmqbrk command has been

broker started for queue manager <insert_3>. issued to query the state of the WebSphere MQ
Publish/Subscribe broker. The WebSphere MQ
Response: None. Publish/Subscribe broker is currently running.
Response: None.

strmqbrk command. The broker stanza in the queue
manager initialization file is not valid. The broker will
terminate immediately. The invalid attribute is
quiescing.
<insert_5>.
Response: Correct the broker stanza in the queue
Explanation: The dspmqbrk command has been manager initialization file.
issued to query the state of the WebSphere MQ
AMQ5815 (iSeries) Invalid WebSphere MQ
Publish/Subscribe broker is currently performing a
Publish/Subscribe broker initialization
controlled shutdown.
file stanza.
Response: None.
Explanation: The broker was started using the
strmqbrk command. The Broker stanza in the queue
manager(<insert_3>) initialization file is not valid. The
stopping.
broker will terminate immediately. The invalid attribute
Severity: 0 : Information is <insert_5>.
Explanation: Either the dspmqbrk command or the Response: Correct the Broker stanza in the queue
endmqbrk command has been issued. The WebSphere manager initialization file.
MQ Publish/Subscribe broker is currently performing
an immediate shutdown. If the endmqbrk command
AMQ5815 (Windows) The WebSphere MQ
has been issued to request that the broker terminate,
Publish/Subscribe broker configuration
the command is unsuccessful because the broker is
for queue manager (<insert_3>) is not
already performing an immediate shutdown.
valid.
Response: None.
strmqbrk command. The broker configuration
broker for queue manager <insert_3> not
information is not valid. The broker will terminate
active.
immediately. The invalid attribute is <insert_5>.
Response: Correct the broker attribute using the
Explanation: An WebSphere MQ Publish/Subscribe cfgmqbrk configuration tool.
broker administration command has been issued to
query or change the state of the broker. The WebSphere
AMQ5816 Unable to open WebSphere MQ
MQ Publish/Subscribe broker is not currently running.
Publish/Subscribe broker control queue
Response: None. for reason <insert_1>,<insert_2>.
Explanation: The broker has failed to open the broker
control queue (<insert_3>). The attempt to open the
ended abnormally.
queue failed with completion code <insert_1> and
Severity: 0 : Information reason <insert_2>. The most likely reasons for this error
are that an application program has opened the broker
Explanation: The dspmqbrk command has been
control queue for exclusive access, or that the broker
issued to query the state of the WebSphere MQ
control queue has been defined incorrectly. The broker
will terminate immediately.
Publish/Subscribe broker has ended abnormally.
Response: Correct the problem and restart the broker.
Response: Refer to the queue manager error logs to
determine why the broker ended abnormally.
AMQ5817 An invalid stream queue has been
detected by the broker.
AMQ5815 Invalid WebSphere MQ
Publish/Subscribe broker initialization Severity: 10 : Warning
file stanza for queue manager
Explanation: WebSphere MQ has detected an attempt
(<insert_3>).
to use a queue (<insert_3>) as a stream queue, but the
Severity: 20 : Error attributes of the queue make it unsuitable for use as a
stream queue. The most likely reason for this error is
that the queue is: (1) Not a local queue; (2) A shareable message to the parent broker (<insert_3>) for reason
queue; (3) A temporary dynamic queue. If the queue <insert_1>. The broker will terminate immediately.
was created using implicit stream creation, the model
Response: Investigate why the problem occurred and
stream might have been defined incorrectly. The
take appropriate action to correct the problem. The
message that caused the stream to be created will be
problem is likely to be caused by the parent broker
rejected or put to the dead-letter queue, depending
name not resolving to the name of a transmission
upon the message report options and broker
queue on the local broker.
configuration.
Response: Correct the problem and resubmit the
request.
broker failed to register with parent
broker.
AMQ5818 Unable to open WebSphere MQ
Publish/Subscribe broker stream queue.
Explanation: The broker has been started specifying a
parent broker (<insert_3>). The broker attempted to
Explanation: The broker has failed to open a stream register as a child of the parent broker, but received an
queue (<insert_3>). The attempt to open the queue exception response (<insert_1>) indicating that this was
failed with completion code <insert_1> and reason not possible. The broker will attempt to reregister as a
<insert_2>. The most likely reason for this error is that child of the parent periodically. The child might not be
an application has the queue open for exclusive access. able to process global publications or subscriptions
The stream will be temporarily shut down and an correctly until this registration process has completed
attempt will be made to restart the stream after a short normally.
interval.
Response: Correct the problem. take appropriate action to correct the problem. The
problem is likely to be caused by the parent broker not
yet existing, or a problem with the
AMQ5819 An WebSphere MQ Publish/Subscribe
SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS
broker stream has ended abnormally.
queue at the parent broker.
Explanation: The broker stream (<insert_3>) has ended AMQ5823 Exit path attribute invalid in WebSphere
abnormally for reason <insert_1>. The broker will MQ Publish/Subscribe broker stanza.
attempt to restart the stream. If the stream should
repeatedly fail then the broker will progressively
increase the time between attempts to restart the Explanation: The broker exit path attribute <insert_3>
stream. is not valid. The attribute should be specified as:
<path><module name>(<function name>). The broker
will terminate immediately.
take appropriate action to correct the problem. If the
problem persists, contact your IBM service Response: Correct the problem with the attribute and
representative. restart the broker.
AMQ5820 WebSphere MQ Publish/Subscribe AMQ5824 WebSphere MQ Publish/Subscribe

broker stream (<insert_3>) restarted. broker exit module could not be loaded.
Explanation: The broker has restarted a stream that Explanation: The broker exit module <insert_3> could
ended abnormally. This message will frequently be not be loaded for reason <insert_1>:<insert_4>. The
preceded by message AMQ5867 or AMQ5819 indicating broker will terminate immediately.
why the stream ended.
Response: Correct the problem with the broker exit
Response: Correct the problem. module <insert_3> and restart the broker.
AMQ5821 WebSphere MQ Publish/Subscribe AMQ5825 The address of the WebSphere MQ

broker unable to contact parent broker. Publish/Subscribe broker exit function
could not be found.
Explanation: The broker has been started specifying a
parent broker. The broker has been unable to send a Explanation: The address of the broker exit function

<insert_4> could not be found in module <insert_3> for
reason <insert_1>:<insert_5>. The broker will terminate
broker exit returned an ExitResponse
immediately.
that is not valid.
Response: Correct the problem with the broker exit
function <insert_4> in module <insert_3>, and restart
the broker. Explanation: The broker exit returned an ExitResponse
<insert_1> that is not valid. The message has been
allowed to continue and an FFST has been generated
AMQ5826 The WebSphere MQ Publish/Subscribe
that contains the entire exit parameter structure.
broker has failed to propagate a
subscription to another broker. Response: Correct the problem with the broker exit.
AMQ5829 Usage: <insert_3> [-m QMgrName] [-p
Explanation: The broker failed to propagate
ParentQMgrName]
subscription to stream (<insert_4>) at broker
(<insert_3>). Reason codes <insert_1> and <insert_2>. Severity: 0 : Information
An application has either registered or deregistered a
global subscription to stream (<insert_4>). The broker
has attempted to propagate the subscription change to Response: None.
broker (<insert_3>) but the request has not been
successful. The message broker will immediately
attempt to refresh the state of the global subscriptions AMQ5830 Usage: endmqbrk [-c | -i] [-m
for stream (<insert_4>) at broker (<insert_3>). Until the QMgrName]
subscription state has been successfully refreshed, Severity: 0 : Information
messages published on stream (<insert_4>) through
broker (<insert_3>) might not reach this broker. Explanation: This shows the correct usage.
Response: Use the reason codes to investigate why the Response: None.
problem occurred and take appropriate action to correct
the problem. AMQ5831 Usage: dspmqbrk [-m QMgrName]
AMQ5827 An WebSphere MQ Publish/Subscribe
broker internal subscription has failed. Explanation: This shows the correct usage.
Severity: 10 : Warning Response: None.
Explanation: The broker failed to subscribe to stream

(<insert_4>) at broker (<insert_3>) with reason codes AMQ5832 WebSphere MQ Publish/Subscribe
<insert_1> and <insert_2>. Related brokers learn about broker failed to publish configuration
each others configuration by subscribing to information information on
published by each other. A broker has discovered that SYSTEM.BROKER.ADMIN.STREAM.
one of these internal subscriptions has failed. The Severity: 10 : Warning
broker will reissue the subscription immediately. The
broker cannot function correctly without knowing some Explanation: Related brokers learn about each others
information about neighboring brokers. The configuration by subscribing to information published
information that this broker has about broker by each other. A broker has discovered that one of
(<insert_3>) is not complete and this could lead to these internal publications has failed. The broker will
subscriptions and publications not being propagated republish the information immediately. Brokers cannot
around the network correctly. function correctly without knowing some information
about neighboring brokers. The information that
Response: Investigate why the problem occurred and neighboring brokers have of this broker might not be
take appropriate action to correct the problem. The complete and this could lead to some subscriptions and
most likely cause of this failure is a problem with the publications not being propagated around the network.
SYSTEM.BROKER.CONTROL.QUEUE at broker
(<insert_3>), or a problem with the definition of the Response: Investigate why the problem occurred and
route between this broker and broker (<insert_3>). take appropriate action to correct the problem.
this message can be ignored. It is strongly
AMQ5833 A loop has been detected in the
recommended that every queue manager in a broker
WebSphere MQ Publish/Subscribe
hierarchy has a unique name. It is not recommended
broker hierarchy.
that multiple queue managers use the same name.
Explanation: The broker, on queue manager AMQ5837 WebSphere MQ Publish/Subscribe
(<insert_3>), introduced a loop in the broker hierarchy. broker failed to quiesce queue
This broker will terminate immediately. (<insert_3>) for reason <insert_1>.
Response: Remove broker (<insert_3>) from the Severity: 10 : Warning
hierarchy, either by deleting the broker, or by removing
Explanation: When a broker is deleted, the broker’s
knowledge of the broker’s parent, using the clrmqbrk
input queues are quiesced by making the queue get
command.
inhibited, and writing the contents of the queue to the
dead-letter queue (depending upon the report options
AMQ5834 Conflicting queue manager names in the of the message). The broker was unable to quiesce the
WebSphere MQ Publish/Subscribe named queue for the reason shown. The attempt to
broker hierarchy. delete the broker will fail.
Severity: 10 : Warning Response: Investigate why the problem occurred, take
appropriate action to correct the problem, and reissue
Explanation: The names of the queue managers
the dltmqbrk command. Likely reasons include the
(<insert_3>) and (<insert_4>) in the broker hierarchy
queue being open for input by another process, there
both start with the same 12 characters. The first 12
being no dead-letter queue defined at this queue
characters of a broker’s queue manager name should be
manager, or the operator setting the queue to get
unique to ensure that no confusion arises within the
inhibited while the dltmqbrk command is running. If
broker hierarchy, and to guarantee unique message ID
there is no dead-letter queue defined, the reason will be
allocation.
reported as MQRC_UNKNOWN_OBJECT_NAME. If
Response: Use a queue manager naming convention the problem occurs because there is no dead-letter
that guarantees uniqueness of the first 12 characters of queue defined at this broker, the operator can either
the queue manager name. define a dead-letter queue, or manually empty the
queue causing the problem.
broker failed to inform its parent of a AMQ5837 (iSeries) WebSphere MQ
relation for reason <insert_1>. Publish/Subscribe broker failed to
quiesce queue.
Explanation: The failed to notify its parent on queue
manager (<insert_3>) of the relation (<insert_4>) in the Explanation: When a broker is deleted, the broker’s
broker hierarchy. The notification message will be put input queues are quiesced by making the queue get
to the parent’s dead-letter queue. A failure to notify a inhibited, and writing the contents of the queue to the
broker of a new relation will mean that no loop dead-letter queue (depending upon the report options
detection can be performed for the new relation. of the message). The broker was unable to quiesce the
queue (<insert_3>) for reason <insert_1>. The attempt to
Response: Diagnose and correct the problem on the delete the broker will fail.
parent queue manager. One possible reason for this is
that the parent broker does not yet exist. Response: Investigate why the problem occurred, take
appropriate action to correct the problem, and reissue
the dltmqbrk command. Likely reasons include the
AMQ5836 Duplicate queue manager name located queue being open for input by another process, there
in the WebSphere MQ being no dead-letter queue defined at this queue
Publish/Subscribe hierarchy. manager, or the operator setting the queue to get
Severity: 0 : Information inhibited while the dltmqbrk command is running. If
there is no dead-letter queue defined, the reason will be
Explanation: Multiple instances of the queue manager reported as MQRC_UNKNOWN_OBJECT_NAME. If
name (<insert_3>) have been located. This could either the problem occurs because there is no dead-letter
be the result of a previously resolved loop in the broker queue defined at this broker, the operator can either
hierarchy, or multiple queue managers in the broker define a dead-letter queue, or manually empty the
hierarchy having the same name. queue causing the problem.
Response: If this broker introduced a loop in the
hierarchy (typically identified by message AMQ5833),

delete for a dltmqbrk command to complete.
broker cannot be deleted.
broker (<insert_3>) deleted.
Explanation: The broker cannot be deleted as child
(<insert_3>) is still registered. A broker cannot be
deleted until all other brokers that have registered as Explanation: The broker (<insert_3>) has been deleted
children of that broker, have deregistered as its using the dltmqbrk command.
children.
Response: None.
Response: Use the clrmqbrk and dltmqbrk commands
to change the broker topology so that broker
(<insert_3>) is not registered as a child of the broker AMQ5842 WebSphere MQ Publish/Subscribe
being deleted. broker (<insert_3>) cannot be deleted for
reason <insert_1>:<insert_5>.
AMQ5839 WebSphere MQ Publish/Subscribe Severity: 20 : Error

broker received an unexpected Explanation: An attempt has been made to delete the
inter-broker communication. broker (<insert_3>) but the request has failed for reason
Severity: 10 : Warning <insert_1>:<insert_5>.
Explanation: A broker has received an inter-broker Response: Determine why the dltmqbrk command
communication that it did not expect. The message was cannot complete successfully. The message logs for the
sent by broker (<insert_3>). The message will be queue manager might contain more detailed
processed according to the report options in that information on why the broker cannot be deleted.
message. The most likely reason for this message is that Resolve the problem that is preventing the command
the broker topology has been changed while from completing and reissue the dltmqbrk command.
inter-broker communication messages were in transit
(for example, on a transmission queue) and that a AMQ5842 (iSeries) WebSphere MQ
message relating to the previous broker topology has Publish/Subscribe broker cannot be
arrived at a broker in the new topology. This message deleted.
may be accompanied by an informational FFST
including details of the unexpected communication. Severity: 20 : Error
Response: If the broker topology has changed and the Explanation: An attempt has been made to delete the
broker named in the message is no longer related to the WebSphere MQ Publish/Subscribe broker (<insert_3>)
broker issuing this message, this message can be but the request has failed for reason
ignored. If the clrmqbrk command was issued to <insert_1>:<insert_5>.
unilaterally remove knowledge of broker (<insert_3>) Response: Determine why the dltmqbrk command
from this broker, the clrmqbrk command should also be cannot complete successfully. The message logs for the
used to remove knowledge of this broker from broker queue manager might contain more detailed
(<insert_3>). If the clrmqbrk command was issued to information on why the broker cannot be deleted.
unilaterally remove knowledge of this broker from Resolve the problem that is preventing the command
broker (<insert_3>), the clrmqbrk command should also from completing and reissue the dltmqbrk command.
be used to remove knowledge of broker (<insert_3>) at
this broker.
broker (<insert_3>) cannot be started as
AMQ5840 WebSphere MQ Publish/Subscribe it is partially deleted.
broker unable to delete queue.
Explanation: An attempt has been made to start a
Explanation: The broker has failed to delete the queue broker that is in a partially deleted state. An earlier
(<insert_3>) for reason <insert_2>. The broker typically attempt to delete the broker has failed. The broker
attempts to delete queues during dltmqbrk processing, deletion must be completed before the broker will be
in which case the dltmqbrk command will fail. allowed to restart. When broker deletion is successful,
Response: The most likely reason for this error is that message AMQ5841 is issued, indicating that the broker
some other process has the queue open. Determine has been deleted. If this message is not received on
why the queue cannot be deleted, remove the inhibitor, completion of a dltmqbrk command, the broker
and retry the failed operation. In a multi-broker deletion has not been completed and the command will
environment, it is likely that a message channel agent have to be reissued.
might have queues open, which the broker needs to
Response: Investigate why the earlier attempt to to remove knowledge of broker (<insert_4>) from
delete the broker failed. Resolve the problem and broker (<insert_3>).
reissue the dltmqbrk command.
Response: None.

Publish/Subscribe broker cannot be
Publish/Subscribe broker relation
started as it is partially deleted.
removed.
Explanation: An attempt has been made to start the
Explanation: The clrmqbrk command has been used
broker <insert_3> that is in a partially deleted state. An
to remove knowledge of broker (<insert_4>) from
earlier attempt to delete the broker has failed. The
broker (<insert_3>).
broker deletion must be completed before the broker
will be allowed to restart. When broker deletion is Response: None.
successful, message AMQ5841 is issued, indicating that
the broker has been deleted. If this message is not
received on completion of a dltmqbrk command, the AMQ5848 WebSphere MQ Publish/Subscribe
broker deletion has not been completed and the broker (<insert_3>) has failed to remove
command will have to be reissued. references to relation (<insert_4>) for
reason <insert_1>:<insert_5>.
Response: Investigate why the earlier attempt to
delete the broker failed. Resolve the problem and Severity: 20 : Error
reissue the dltmqbrk command. Explanation: An attempt has been made to remove
references to broker (<insert_4>) from broker
AMQ5844 The relation between two WebSphere (<insert_3>) using the clrmqbrk command, but the
MQ Publish/Subscribe brokers is request has been unsuccessful.
unknown. Response: Determine why the clrmqbrk command
Severity: 10 : Warning cannot complete successfully. The message logs for the
queue manager might contain more detailed
Explanation: The clrmqbrk command has been issued information on why the broker cannot be deleted.
in an attempt to remove a brokers knowledge of a Resolve the problem that is preventing the command
relation of that broker. The relative (<insert_4>) is from completing and then reissue the clrmqbrk
unknown at broker (<insert_3>). If the ″-p″ flag was command.
specified, the broker does not currently have a parent.
If the ″-c″ flag was specified, the broker does not
recognize the named child. AMQ5848 (iSeries) WebSphere MQ
Publish/Subscribe broker has failed to
Response: Investigate why the broker is unknown. remove references to a related broker.
AMQ5845 Usage: dltmqbrk -m QMgrName
Explanation: An attempt has been made to remove
Severity: 0 : Information references to broker (<insert_4>) from broker
(<insert_3>) using the clrmqbrk command, but the
request has been unsuccessful for reason
Response: None. <insert_1>:<insert_5>.
Response: Determine why the clrmqbrk command
AMQ5846 Usage: clrmqbrk -p | -c cannot complete successfully. The message logs for the
ChildQMgrName -m QMgrName queue manager might contain more detailed
information on why the broker cannot be deleted.
Resolve the problem that is preventing the command
Explanation: This shows the correct usage. from completing and then reissue the clrmqbrk
command.
Response: None.

AMQ5847 WebSphere MQ Publish/Subscribe broker may not change parent.
broker (<insert_3>) has removed
knowledge of relation (<insert_4>). Severity: 10 : Warning
Severity: 0 : Information Explanation: An attempt has been made to start
broker (<insert_3>), nominating broker (<insert_4>) as
Explanation: The clrmqbrk command has been used

its parent. The broker (<insert_3>) has previously been from the queue. Ensure that no applications have the
started, nominating broker (<insert_5>) as its parent. queue open.
The strmqbrk command cannot be used to change an
existing relationship.
Response: Do not attempt to change the broker broker failed to propagate delete
topology by using the strmqbrk command. The publication command.
dltmqbrk and clrmqbrk commands are the only
supported means of changing the broker topology.
Refer to the documentation of those commands for Explanation: The broker failed to propagate delete
guidance on changing the broker topology. publication command for stream (<insert_3>) to related
broker (<insert_4>) for reason <insert_1>. When an
application issues a delete publication command to
delete a global publication, the command has to be
broker interrupted while creating queue.
propagated to all brokers in the sub-hierarchy
Severity: 10 : Warning supporting the stream. The broker reporting the error
has failed to forward a delete publication command to
Explanation: The broker was interrupted while
a related broker (<insert_4>) who supports stream
creating queue (<insert_3>) for user ID (<insert_4>).
(<insert_3>). Delete publication commands are
When the broker creates a queue, it first creates the
propagated without MQRO_DISCARD_MSG and the
queue with default security attributes and it then sets
command message might have been written to a
the appropriate security attributes for the queue. If the
dead-letter queue. The topic for which the delete
broker should be interrupted during this operation (for
publication has failed is (<insert_5>).
example the queue manager is shut down), the broker
cannot reliably detect that the security attributes have Response: If the delete publication has failed because
not been set correctly. The broker was creating a queue, the stream has been deleted at the related broker, this
but was interrupted before it could complete creation of message can be ignored. Investigate why the delete
the queue and setting the initial authority. If the publication has failed and take the appropriate action
interrupt occurred before the initial authority of the to recover the failed command.
queue could be set, it might be necessary for the
operator to set the appropriate authorities using the
setmqaut command.
failed to propagate a delete publication
Response: Confirm that the named queue has the command.
appropriate security attributes and modify them as
necessary.
Explanation: The broker failed to propagate a delete
publication command for stream (<insert_3>) to a
previously related broker. When an application issues a
broker interrupted while creating
delete publication command to delete a global
internal queue.
publication, the command is propagated to all brokers
Severity: 10 : Warning in the sub-hierarchy supporting the stream. The broker
topology was changed after deleting the publication,
Explanation: The broker was interrupted while
but before a broker removed by the topology change
creating internal queue (<insert_3>) for user ID
processed the propagated delete publication message.
(<insert_4>). When the broker creates an internal queue,
The topic for which the delete publication has failed is
it first creates the queue with default security attributes
(<insert_5>).
and it then sets the appropriate security attributes for
the queue. If the broker should be interrupted during Response: It is the user’s responsibility to quiesce
this operation (for example the queue manager is shut broker activity before changing the broker topology
down), the broker attempts to delete and redefine the using the clrmqbrk command. Investigate why this
queue. If the internal queue is available to users (for delete publication activity was not quiesced. The delete
example, the default stream or the administration publication command will have been written to the
stream), it is possible that a user will put a message on dead-letter queue at the broker that was removed from
the queue while it is in this invalid state, or that a user the topology. In this case, further action might be
application has the queue open. In this situation the necessary to propagate the delete publication command
broker does not automatically redefine the queue and that was not quiesced before the clrmqbrk command
cannot be restarted until the queue has been emptied or was issued. If this message occurs as a result of the
closed. dltmqbrk command, the publication will have been
deleted as a result of the dltmqbrk command, and the
Response: Examine any messages on the named
delete publication message will have been written to
queue and take appropriate action to remove them
the dead-letter queue at the queue manager where the
broker was deleted. In this case the delete publication
message on the dead-letter queue can be discarded. publication to the dead-letter queue.
AMQ5854 WebSphere MQ Publish/Subscribe AMQ5857 Broker control command message

broker failed to propagate a delete cannot be processed. Reason code
publication command. <insert_1>.
Explanation: When an application issues a delete Explanation: The WebSphere MQ Publish/Subscribe
publication command to delete a global publication, the broker failed to process a command message on the
command has to be propagated to all brokers in the SYSTEM.BROKER.CONTROL.QUEUE. The broker was
sub-hierarchy supporting the stream. At the time the unable to write the command message to the
delete publication was propagated, broker (<insert_4>) dead-letter queue and was not permitted to discard the
was a known relation of this message broker command message. The broker will temporarily stop
supporting stream (<insert_3>). Before the delete the stream and will restart the stream and consequently
publication command arrived at the related broker, the retry the command message after a short interval.
broker topology was changed so that broker Other broker control commands cannot be processed
(<insert_4>) no longer supported stream (<insert_3>). until this command message has been processed
The topic for which the delete publication has failed is successfully or removed from the control queue.
(<insert_5>).
Response: Investigate why the error has occurred and
Response: It is the user’s responsibility to quiesce why the command message cannot be written to the
broker activity before changing the stream topology of dead-letter queue. Either, manually remove the
the broker. Investigate why this delete publication command message from the stream queue, or correct
activity was not quiesced. The delete publication the problem that is preventing the broker from writing
command will have been written to the dead-letter the command message to the dead-letter queue.
queue at broker (<insert_4>).
AMQ5858 Broker could not send publication to
AMQ5855 WebSphere MQ Publish/Subscribe subscriber queue.
broker ended.
Explanation: A failure has occurred sending a
Explanation: An attempt has been made to run the publication to subscriber queue (<insert_4>) at queue
broker (<insert_3>) but the broker has ended for reason manager (<insert_3>) for reason <insert_1>. The broker
<insert_1>:<insert_5>. configuration options prevent it from recovering from
this failure by discarding the publication or by sending
Response: Determine why the broker ended. The
it to the dead-letter queue. Instead the broker will back
message logs for the queue manager might contain
out the unit of work under which the publication is
more detailed information on why the broker cannot be
being sent and retry the failing command message a
started. Resolve the problem that is preventing the
fixed number of times. If the problem still persists, the
command from completing and reissue the strmqbrk
broker will then attempt to recover by failing the
command.
command message with a negative reply message. If
the issuer of the command did not request negative
AMQ5856 Broker publish command message replies, the broker will either discard or send to the
cannot be processed. Reason code dead-letter queue the failing command message. If the
<insert_1>. broker configuration options prevent this, the broker
will restart the affected stream, which will reprocess the
Severity: 10 : Warning failing command message again. This behavior will be
Explanation: The WebSphere MQ Publish/Subscribe repeated until such time as the failure is resolved.
broker failed to process a publish message for stream During this time the stream will be unable to process
(<insert_3>). The broker was unable to write the further publications or subscriptions.
publication to the dead-letter queue and was not Response: Usually the failure will be due to a
permitted to discard the publication. The broker will transient resource problem, for example, the subscriber
temporarily stop the stream and will restart the stream queue, or an intermediate transmission queue,
and consequently retry the publication after a short becoming full. Use reason code <insert_1> to determine
interval. what remedial action is required. If the problem
Response: Investigate why the error has occurred and persists for a long time, you will notice the stream
why the publication cannot be written to the being continually restarted by the broker. Evidence of
dead-letter queue. Either manually remove the this occurring will be a large number of AMQ5820
publication from the stream queue, or correct the messages, indicating stream restart, being written to the
problem that is preventing the broker from writing the error logs. In such circumstances, manual intervention

will be required to allow the broker to dispose of the determine the nature of the problem. A value of 1
failing publication. To do this, you will need to end the means that queue
broker using the endmqbrk command and restart it SYSTEM.BROKER.INTERBROKER.QUEUE does not
with appropriate disposition options. This will allow exist. This is probably because no WebSphere MQ
the publication to be sent to the rest of the subscribers, Integrator broker has been defined yet on this queue
while allowing the broker to discard or send to the manager. A value of 2 means that the WebSphere MQ
dead-letter queue the publication that could not be Integrator broker does not have the queue open
sent. probably because it hasn’t been started or the first
message flow has yet to be deployed for it. If both of
these steps have been taken then the WebSphere MQ
Integrator broker may have been created incorrectly. In
broker stream is terminating due to an
particular, it should have been created in migration
internal resource problem.
mode. If the broker was not created with the migration
Severity: 10 : Warning flag set then it will need to be deleted and recreated
before migration can commence. Any other value in the
Explanation: The broker stream (<insert_3>) has run reason code will need to be reported to your IBM
out of internal resources and will terminate with reason Support Center for problem resolution. Note that until
code <insert_1>. If the command in progress was being the problem has been resolved the WebSphere MQ
processed under syncpoint control, it will be backed Publish/Subscribe broker can still be restarted with the
out and retried when the stream is restarted by the the strmqbrk command.
broker. If the command was being processed out of
syncpoint control, it will not be able to be retried when
the stream is restarted. AMQ5864 Broker reply message could not be sent.
The command will be retried.
Response: This message should only be issued in very
unusual circumstances. If this message is issued Severity: 10 : Warning
repeatedly for the same stream, and the stream is not
Explanation: While processing a publish/subscribe
especially large in terms of subscriptions, topics, and
command, the WebSphere MQ Publish/Subscribe
retained publications, save all generated diagnostic
broker could not send a reply message to queue
information and contact your IBM Support Center for
(<insert_4>) at queue manager (<insert_3>) for reason
problem resolution.
<insert_1>. The broker was also unable to write the
message to the dead-letter queue. Since the command
AMQ5862 WebSphere MQ Publish/Subscribe is being processed under syncpoint control, the broker
broker for queue manager <insert_3> will attempt to retry the command in the hope that the
migrating. problem is only of a transient nature. If, after a set
number of retries, the reply message still could not be
Severity: 0 : Information sent, the command message will be discarded if the
Explanation: The dspmqbrk command has been report options allow it. If the command message is not
issued to query the state of the broker. The broker is discardable, the stream will be restarted, and
currently being migrated. processing of the command message recommenced.
Response: None. Response: Use reason code <insert_1> to determine

what remedial action is required. If the failure is due to
a resource problem (for example, a queue being full),
AMQ5863 WebSphere MQ Integrator broker not you might find that the problem has already cleared
ready for migration. See message logs itself. If not, this message will be issued repeatedly
for guidance. each time the command is retried. In this case you are
Severity: 10 : Warning strongly advised to define a dead-letter queue to
receive the reply message so that the broker can
Explanation: The migmqbrk command was process other commands while the problem is being
unsuccessful because the WebSphere MQ Integrator investigated. Check the application from which the
broker was not ready to accept messages. The state of command originated and ensure that it is specifying its
the WebSphere MQ Publish/Subscribe message broker reply-to queue correctly.
is exported to the WebSphere MQ Integrator broker in
a series of messages sent to queue
SYSTEM.BROKER.INTERBROKER.QUEUE. Before AMQ5865 Broker reply message could not be sent.
migration commences the WebSphere MQ Severity: 10 : Warning
Publish/Subscribe broker checks whether the
WebSphere MQ Integrator broker is ready to accept Explanation: While processing a publish/subscribe
messages on this queue. This check has failed for command, the WebSphere MQ Publish/Subscribe
reason <insert_1> so migration has been abandoned. broker could not send a reply message to queue
(<insert_4>) at queue manager (<insert_3>) for reason
Response: Reason code <insert_1> should be used to
<insert_1>. The broker was also unable to write the While user ID (<insert_3>) remains unauthorized, the
message to the dead-letter queue. As the command is broker will continue to deregister subscriptions
not being processed under syncpoint control, the broker associated with that user ID.
is not able to retry the command.
Response: If the authority of user ID (<insert_3>) was
Response: Use reason code <insert_1> to determine intentionally removed, consider removing all of that
what remedial action is required. If the failure is due to user IDs subscriptions immediately by issuing an
a resource problem (for example, a queue being full), MQCMD_DEREGISTER_SUBSCRIBER command,
you might find that the problem has already cleared specifying the MQREGO_DEREGISTER_ALL option on
itself. If not, check the application from which the the subscriber’s behalf. If the authority was revoked
command originated and ensure that it is specifying its accidentally, reinstate it, but be aware that some, if not
reply-to queue correctly. You might find that defining a all, of the subscriber’s subscriptions will have been
dead-letter queue to capture the reply message on a deregistered by the broker.
subsequent failure will help you with this task.
AMQ5866 Broker command message has been broker is checkpointing registrations.
discarded. Reason code <insert_1>.
Explanation: A large number of changes have been
Explanation: The WebSphere MQ Publish/Subscribe made to the publisher and subscriber registrations of
broker failed to process a publish/subscribe command stream (<insert_3>). These changes are being
message, which has now been discarded. The broker checkpointed, in order to minimize both stream restart
will begin to process new command messages again. time and the amount of internal queue space being
used.
Response: Look for previous error messages to
indicate the problem with the command message. Response: None.
Correct the problem to prevent the failure from
happening again.
AMQ5870 (Unexpected Error)
broker stream has ended abnormally. Explanation: N/A
Severity: 10 : Warning Response: N/A
Explanation: The broker stream (<insert_3>) has ended
abnormally for reason <insert_1>. The broker will AMQ5871 (Resource Problem)
attempt to restart the stream. If the stream should
repeatedly fail, the broker will progressively increase Severity: 0 : Information
the time between attempts to restart the stream. Explanation: N/A
Response: Use the reason code <insert_1> to Response: N/A
investigate why the problem occurred. A reason code of
1 indicates that the stream ended because a command
message could not be processed successfully. Look in AMQ5872 (WebSphere MQ Publish/Subscribe
the error logs for earlier messages to determine the broker has a known child)
reason why the command message failed. A reason Severity: 0 : Information
code of 2 indicates that the stream ended because the
broker exit could not be loaded. Until the problem with Explanation: N/A
the broker exit has been resolved, the stream will Response: N/A
continue to fail.
AMQ5873 (WebSphere MQ Publish/Subscribe

AMQ5868 User is no longer authorized to broker active)
subscribe to stream.
Explanation: N/A
Explanation: The broker has attempted to publish a
publication to a subscriber, but the subscriber no longer Response: N/A
has browse authority to stream queue (<insert_4>). The
publication is not sent to the subscriber and his
subscription is deregistered. An event publication
containing details of the subscription that was removed
is published on SYSTEM.BROKER.ADMIN.STREAM.

AMQ5874 (One or more queues could not be AMQ5877 WebSphere MQ Publish/Subscribe
quiesced) broker stream has ended abnormally.
Explanation: N/A Explanation: A broker stream (<insert_3>) has ended
abnormally for reason <insert_1>. The broker recovery
Response: N/A
routines failed to reset the stream state and the stream
cannot be restarted automatically.
Response: Investigate why the stream failed and why
broker cannot write a message to the
the broker’s recovery routine could not recover
dead-letter queue.
following the failure. Take appropriate action to correct
Severity: 10 : Warning the problem. Depending upon the broker configuration
and the nature of the problem it will be necessary to
Explanation: The broker attempted to put a message restart either the broker,or both the queue manager and
to the dead-letter queue (<insert_3>) but the message the broker, to make the stream available. If the problem
could not be written to the dead-letter queue for reason persists contact your IBM service representative.
<insert_1>:<insert_4>. The message was being written to
the dead-letter queue with a reason of
<insert_2>:<insert_5>. AMQ5878 WebSphere MQ Publish/Subscribe
broker recovery failure detected.
Response: Determine why the message cannot be
written to the dead-letter queue. Also, if the message Severity: 10 : Warning
was not deliberately written to the dead-letter queue,
Explanation: An earlier problem has occurred with the
for example by a message broker exit, determine why
broker, and either a stream has been restarted or the
the message was written to the dead-letter queue and
broker has been restarted. The restarted stream or
resolve the problem that is preventing the message
broker has detected that the previous instance of the
from being sent to its destination.
stream or broker did not clean up successfully and the
restart will fail.
AMQ5876 A parent conflict has been detected in
Response: Investigate the cause of the failure that
the WebSphere MQ Publish/Subscribe
caused a stream or broker restart to be necessary, and
broker hierarchy.
why the broker or stream was unable to clean up its
Severity: 20 : Error resources following the failure. When the broker
processes with a non trusted routing exit
Explanation: The broker (<insert_3>) has been started, (RoutingExitConnectType=STANDARD), the broker
naming this broker as its parent. This broker was runs in a mode where it is more tolerant of unexpected
started naming broker (<insert_3>) as its parent. The failures and it is likely that the restart will succeed after
broker will send an exception message to broker a short delay. In the case of a stream restart, the broker
(<insert_3>) indicating that a conflict has been detected. will normally periodically retry the failing restart. In
The most likely reason for this message is that the the case of a broker restart, it will be necessary to
broker topology has been changed while inter-broker manually retry the broker restart after a short delay.
communication messages were in transit (for example, When the broker processes without a routing exit, or
on a transmission queue) and that a message relating to with a trusted routine exit
the previous broker topology has arrived at a broker in (RoutingExitConnectType=FASTPATH), the broker runs
the new topology. This message may be accompanied in a mode where it is less tolerant of unexpected
by an informational FFST including details of the failures and a queue manager restart will be necessary
unexpected communication. to resolve this problem. When the broker is running in
Response: If the broker topology has changed and the this mode, it is important that the broker processes are
broker named in the message no longer identifies this not subjected to unnecessary asynchronous interrupts,
broker as its parent, this message can be ignored - for for example, kill. If the problem persists, contact your
example, if the command ″clrmqbrk -m <insert_3> -p″ IBM service representative.
was issued. If broker (<insert_3>) has been defined as
this broker’s parent, and this broker has been defined AMQ5879 WebSphere MQ Publish/Subscribe
as broker (<insert_3>)’s parent, the clrmqbrk or the broker has been migrated.
dltmqbrk commands should be used to resolve the
conflict. Severity: 10 : Warning
Explanation: The command was unsuccessful because
the MQ Pub/Sub broker at queue manager <insert_3>
has been migrated. After migration the only command
which can be issued against the migrated broker is the
AMQ5881 (Windows) The WebSphere MQ
dltmqbrk command.
Response: Issue the dltmqbrk command to delete the parameter combination <insert_1> is not
migrated broker. valid.
AMQ5880 User is no longer authorized to
Explanation: A combination of Broker parameters in
subscribe to stream.
the broker configuration information is not valid. The
Severity: 0 : Information broker will not operate until this has been corrected.
An combination of (1) indicates that
Explanation: The broker has attempted to publish a SyncPointIfPersistent has been set to TRUE and
publication to a subscriber but the subscriber no longer DiscardNonPersistentInputMsg has been set to FALSE.
has altusr authority to stream queue (<insert_4>). The DiscardNonPersistentInputMsg must be set to TRUE
publication is not sent to the subscriber and that user when SyncPointIfPersistent is set to TRUE.
IDs subscription is deregistered. An event publication An combination of (2) indicates that
containing details of the subscription that was removed SyncPointIfPersistent has been set to TRUE and
is published on SYSTEM.BROKER.ADMIN.STREAM. DiscardNonPersistentResponse has been set to FALSE.
While user ID (<insert_3>) remains unauthorized, the DiscardNonPersistentResponse must be set to TRUE
broker will continue to deregister subscriptions when SyncPointIfPersistent is set to TRUE.
associated with that user ID. An combination of (3) indicates that
Response: If the authority of user ID (<insert_3>) was SyncPointIfPersistent has been set to TRUE and
intentionally removed, consider removing subscriptions DiscardNonPersistentPublication has been set to
immediately by issuing an FALSE. DiscardNonPersistentPublication must be set to
MQCMD_DEREGISTER_SUBSCRIBER command for TRUE when SyncPointIfPersistent is set to TRUE.
the appropriate topics on the subscriber’s behalf. If the Response: Alter the message broker configuration
authority was revoked accidentally, reinstate it, but be information using the cfgmqbrk tool to comply with
aware that some, if not all, of the subscriber’s the above rules and retry the command.
subscriptions will have been deregistered by the broker.

AMQ5881 The WebSphere MQ Publish/Subscribe broker has written a message to the
broker configuration parameter dead-letter queue.
combination <insert_1> is not valid.
Explanation: The broker has written a message to the
Explanation: A combination of Broker stanzas in the dead-letter queue (<insert_3>) for reason
queue manager initialization file is not valid. The <insert_1>:<insert_5>. Note. To save log space, after the
broker will not operate until this has been corrected. first occurrence of this message for stream (<insert_4>),
An combination of (1) indicates that it will only be written periodically.
SyncPointIfPersistent has been set to TRUE and
DiscardNonPersistentInputMsg has been set to FALSE. Response: If the message was not deliberately written
DiscardNonPersistentInputMsg must be set to TRUE to the dead-letter queue, for example by a message
when SyncPointIfPersistent is set to TRUE. broker exit, determine why the message was written to
An combination of (2) indicates that the dead-letter queue, and resolve the problem that is
SyncPointIfPersistent has been set to TRUE and preventing the message from being sent to its
DiscardNonPersistentResponse has been set to FALSE. destination.
DiscardNonPersistentResponse must be set to TRUE
when SyncPointIfPersistent is set to TRUE.
An combination of (3) indicates that
broker state not recorded.
SyncPointIfPersistent has been set to TRUE and
DiscardNonPersistentPublication has been set to Severity: 10 : Warning
FALSE. DiscardNonPersistentPublication must be set to
Explanation: The broker state on stream (<insert_3>)
TRUE when SyncPointIfPersistent is set to TRUE.
not recorded while processing a publication outside of
Response: Alter the message broker stanzas to comply syncpoint. A nonpersistent publication has requested a
with the above rules and retry the command. change to either a retained message or a publisher
registration. This publication is being processed outside
of syncpoint because the broker has been configured
with the SyncPointIfPersistent option set. A failure has
occurred hardening either the publisher registration or
the retained publication to the broker’s internal queue.

All state changes attempted as a result of this
AMQ5887 Migration started for stream <insert_3>
publication will be backed-out. Processing of the
publication will continue and the broker will attempt to Severity: 0 : Information
deliver it to all subscribers.
Explanation: Migration of stream <insert_3> has
Response: Investigate why the failure occurred. It is started.
probably due to a resource problem occurring on the
Response: None.
broker. The most likely cause is ’queue full’ on a broker
queue. If your publications also carry state changes,
you are advised to send them either as persistent AMQ5888 Migration complete for stream
publications or turn off the SyncPointIfPersistent <insert_3>
option. In this way, they will be carried out under
syncpoint and the broker can retry them in the event of Severity: 0 : Information
a failure such as this. Explanation: All of the state of stream <insert_3> has
been exported to the WebSphere MQ Integrator broker.
AMQ5884 WebSphere MQ Publish/Subscribe Response: None.
broker control queue is not a local
queue.
Severity: 10 : Warning broker has been successfully migrated.
Explanation: WebSphere MQ Publish/Subscribe has It will now be deleted.
detected that the queue Severity: 0 : Information
’SYSTEM.BROKER.CONTROL.QUEUE’ exists and is
not a local queue. This makes the queue unsuitable for Explanation: Migration of the broker has completed
use as the control queue of the broker. The broker will successfully. The broker will now be deleted.
terminate immediately. Response: The broker is no longer startable. If
Response: Delete the definition of the existing queue deletion fails then the dltmqbrk command will need to
and, if required, re-create the queue to be of type be re-issued to complete its deletion.
MQQT_LOCAL. If you do not re-create the queue the
broker will automatically create one of the correct type AMQ5890 The migration of the WebSphere MQ
when started. Publish/Subscribe broker has failed.
AMQ5885 Usage: migmqbrk -m QMgrName
Severity: 0 : Information broker is being migrated. During this migration all
Explanation: This shows the correct usage. persistent state, for example subscriptions, are exported
to the WebSphere MQ Integrator broker as a series of
Response: None. messages sent to queue <insert_3>. A migration
message could not be written to this queue for reason
AMQ5886 WebSphere MQ Publish/Subscribe <insert_1>.
broker is being migrated. Response: Use the MQPUT failure code <insert_1> to
Severity: 10 : Warning determine why the message cannot be written to the
queue. The reason code could indicate that the queue
Explanation: The command cannot be issued at this manager is terminating in which case the migmqbrk
time because the MQ Pub/Sub broker at queue command will need to be re-issued after the queue
manager <insert_3> is being migrated. manager has restarted. Alternatively there may be a
problem with the queue which may need to be rectified
Response: Once migration has commenced then the
before migration can be attempted again.
only command which can be issued against the MQ
Pub/Sub broker is the endmqbrk command to cancel
the migration. Once the broker has ended if migration AMQ5891 WebSphere MQ Publish/Subscribe
did not complete then it can be reattempted using the broker has failed to receive a reply
migmqbrk command again. Alternatively it can be while exporting its state to WebSphere
cancelled by restarting the broker using the strmqbrk MQ Integrator.
command.
broker is being migrated. During this migration all
persistent state, for example subscriptions, are exported
to the WebSphere MQ Integrator broker as a series of
messages. A reply message for one of the migration
messages could not be retrieved from queue <insert_3>
Publish/Subscribe broker cannot be
for reason <insert_1>. The migration of the WebSphere
migrated.
MQ Publish/Subscribe broker has failed.
Response: Use the MQGET failure code <insert_3> to
determine why the reply message could not be received Explanation: An attempt has been made to migrate
from the reply queue. The reason code could indicate the broker (<insert_3>) but the request has failed for
that the queue manager is terminating in which the reason <insert_1>:<insert_5>.
migmqbrk command will need to be re-issued after the
Response: Determine why the migmqbrk command
queue manager has restarted. A reason code of 2033
cannot complete successfully. The message logs for the
indicates that no reply message was received within a
queue manager might contain more detailed
30 second wait interval. In this case the problem is
information outlining why the broker cannot be
more likely to have occurred at the WebSphere MQ
migrated. Resolve the problem that is preventing the
Integrator broker. Check for error messages issued at
command from completing and reissue the migmqbrk
the WebSphere MQ Integrator broker.
command.
AMQ5892 Migration of stream <insert_3> has

failed for reason <insert_1>:<insert_4>.
broker cannot be migrated.
Explanation: Migration of stream <insert_3> has
failed.
broker cannot be migrated yet because the state of
Response: Use reason code <insert_1> to investigate stream <insert_3> is not consistent with respect to
the reason for the failure. Once the problem has been related broker <insert_4>. While an WebSphere MQ
resolved, re-issue the migmqbrk command to retry Publish/Subscribe broker is being migrated a check is
migration. made to ensure that the state of each stream is
consistent with respect to all of the broker’s relations.
This check has failed because an inconsistency has been
AMQ5892 (iSeries) Migration of stream <insert_3>
detected in the state of stream <insert_3> with respect
has failed.
to broker <insert_4>. The problem will most likely be of
Severity: 0 : Information a transient nature, caused because the WebSphere MQ
Publish/Subscribe broker has yet to complete
Explanation: Migration of stream <insert_3> has failed processing a recent change to the topology of the
for reason <insert_1>:<insert_4>. broker network. For example, the stream in question
Response: Use reason code <insert_1> to investigate may have recently been created or deleted at related
the reason for the failure. Once the problem has been broker <insert_4> and this broker has yet to complete
resolved, re-issue the migmqbrk command to retry its processing for this change. Another cause maybe
migration. that either this broker, or broker <insert_4>, have just
been added into the broker network and subscriptions
have yet to be exchanged the two brokers. If this is the
AMQ5893 WebSphere MQ Publish/Subscribe case then the brokers will be inconsistent with respect
broker (<insert_3>) cannot be migrated to all streams. If no recent topology changes have been
for reason <insert_1>:<insert_5>. made then there maybe a current failure with the
Severity: 20 : Error propagation of subscriptions to broker <insert_4>.
Explanation: An attempt has been made to migrate Response: In all cases migration of the WebSphere
the WebSphere MQ Publish/Subscribe broker MQ Publish/Subscribe broker will need to be
(<insert_3>) but the request has failed for reason suspended until the inconsistency has been resolved.
<insert_1>:<insert_5>. You will need to restart the broker using the strmqbrk
command so that it can resolve the problem. After a
Response: Determine why the migmqbrk command short while, the broker can be ended and migration
cannot complete successfully. The message logs for the reattempted. If repeated attempts to migrate the broker
queue manager might contain more detailed all fail with this message then try to resolve the
information outlining why the broker cannot be underlying problem. Look for earlier occurrences of
migrated. Resolve the problem that is preventing the message AMQ5826 and follow the guidance given
command from completing and reissue the migmqbrk there. In all cases ensure that the channels between the
command. two brokers are running.

broker cannot be migrated.
Explanation: A topic has been detected which cannot
be exported to the WebSphere MQ Integrator broker.
The topic <insert_3> cannot be migrated because it
contains wildcard characters recognised by the
WebSphere MQ Integrator broker. The wildcard
characters used by WebSphere MQ Integrator are the
’+’ and the ’#’ characters. The state associated with the
topic isn’t migrated and migration of the WebSphere
MQ Publish/Subscribe broker fails.
Response: The WebSphere MQ Publish/Subscribe
broker cannot be migrated while topic <insert_3> is in
use. All applications using topics which contain either
the ’+’ or ’#’ characters will need to be redesigned to
use different topic strings. Note that the amqspsd
sample can be used to dump the state of the
WebSphere MQ Publish/Subscribe broker. Within the
dump produced by this program locate topic <insert_3>
to determine information about the publishing or
subscribing applications concerned. Until the problem
has been resolved the WebSphere MQ
Publish/Subscribe broker can be restarted as normal
using the strmqbrk command.
AMQ5896 Unknown attribute for WebSphere MQ

parameter GroupId.
Explanation: The broker has attempted to create
stream <insert_4> belonging to group <insert_3>, this
group is unknown.
Response: Modify the attribute for broker
configuration parameter GroupId, to a group that
exists, or create the group <insert_3>.
Chapter 4. 6000-6999 - Common services
messages.
Explanation: WebSphere MQ is unable to start

AMQ6004 An error occurred during WebSphere
program <insert_3> because it was not found.
MQ initialization or ending.
Response: Check the program name is correctly
specified and rerun the program.
Explanation: An error was detected during
initialization or ending of MQ. The MQ error recording
AMQ6026 A resource shortage prevented the
routine has been called.
creation of a WebSphere MQ process.
Response: Use the standard facilities supplied with
your system to record the problem identifier, and to
save the generated output files. Contact your IBM Explanation: An attempt to create an MQ process was
support center. Do not discard these files until the rejected by the operating system due to a process limit
problem has been resolved. (either the number of processes for each user or the
total number of processes running system wide), or
because the system does not have the resources
AMQ6005 (iSeries) An error occurred during
necessary to create another process.
WebSphere MQ startup.
Response: Investigate whether a process limit is
preventing the creation of the process and if so why the
Explanation: An attempt to start the storage monitor system is constrained in this way. Consider raising this
process (job QMQM in subsystem QSYSWRK) was limit or reducing the workload on the system.
unsuccessful.
Response: Check the joblog for this job and for the AMQ6035 WebSphere MQ failed, no storage
QMQM job for possible reasons for failure, correct the available.
error and try the command again. If the problem is not
resolved, a problem may have been logged. Use
WRKPRB to record the problem identifier, and to save Explanation: An internal function of the product
the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. attempted to obtain storage, but there was none
Contact your IBM support center. Do not discard these available.
files until the problem has been resolved.
Response: Stop the product and restart it. If this does
not resolve the problem, save the generated output files
AMQ6015 The operating system is either too busy and contact your IBM support center.
or has insufficient resources to complete
a system request.
AMQ6037 WebSphere MQ was unable to obtain
Severity: 30 : Severe error enough storage.
Explanation: A system request <insert_3> was rejected Severity: 20 : Error
by the operating system with return code <insert_1>.
WebSphere MQ retried the request, but it continued to Explanation: The product is unable to obtain enough
fail. This failure may indicate that the operating system storage. The product’s error recording routine may
is either too busy or has insufficient resources to have been called.
complete the request. Response: Stop the product and restart it. If this does
Response: Investigate whether the system is not resolve the problem see if a problem has been
constrained by the workload on this system or by the recorded. If a problem has been recorded, use the
workload on a server that it is using, and reduce the standard facilities supplied with your system to record
workload. the problem identifier, and to save the generated
output files. Contact your IBM support center. Do not
discard these files until the problem has been resolved.
AMQ6025 Program not found.
Severity: 30 : Severe error AMQ6047 Conversion not supported.

AMQ6052 Conversion length error.
Explanation: WebSphere MQ is unable to convert
string data tagged in CCSID <insert_1> to data in
CCSID <insert_2>. Explanation: WebSphere MQ is unable to convert
string data in CCSID <insert_1> to data in CCSID
Response: Check the WebSphere MQ Application
<insert_2>.
Programming Reference Appendix and the appropriate
National Language Support publications to see if the
CCSIDs are supported by your system. AMQ6053 CCSID error
AMQ6048 DBCS error
Severity: 30 : Severe error string data in CCSID <insert_1> to data in CCSID
<insert_2>.
string data due to a DBCS error. Conversion is from Response: One of the CCSIDs is not supported by the
CCSID <insert_1> to CCSID <insert_2>. system. Check the WebSphere MQ Application
CCSIDs are supported by your system.
CCSIDs are supported by your system.
AMQ6064 An internal WebSphere MQ error has
occurred.
AMQ6049 DBCS-only string not valid.
Explanation: An error has been detected, and the MQ
error recording routine has been called.
<insert_2>. Message descriptor data must be in Response: Use the standard facilities supplied with
single-byte form. CCSID <insert_2> is a DBCS-only your system to record the problem identifier, and to
CCSID. save the generated output files. Contact your IBM
support center. Do not discard these files until the
Response: Check the CCSID of your job or system
problem has been resolved.
and change it to one supporting SBCS or mixed
character sets. Refer to the WebSphere MQ Application
Programming Reference Appendix and the appropriate AMQ6088 (iSeries) An internal WebSphere MQ error
National Language Support publications for character has occurred.
sets and CCSIDs supported.
Explanation: An internal error occurred when API call
AMQ6050 CCSID error.
<insert_3> was made.
Response: Use WRKPRB to record the problem
Explanation: WebSphere MQ is unable to convert identifier, and to save the QPSRVDMP, QPJOBLOG,
string data in CCSID <insert_1> to data in CCSID and QPDSPJOB files. Contact your IBM support center.
<insert_2>. Do not discard these files until the problem has been
resolved.
National Language Support publications to see if the AMQ6089 (iSeries) WebSphere MQ was unable to
CCSIDs are supported by your system. display an error message.
AMQ6051 Conversion length error.
Explanation: An attempt to display an error message
Severity: 30 : Severe error was unsuccessful. This may be because the AMQMSG
message file could not be found. The message identifier
is <insert_3>.
<insert_2>, due to an input length error. Response: Check that the library list is set up
correctly to access the AMQMSG message file. If a
change is necessary, rerun the failing application and
record the error message. If you are unable to resolve
the problem, contact your IBM support center.
AMQ6090 WebSphere MQ was unable to display AMQ6103 (iSeries) WebSphere MQ job submission
an error message <insert_6>. error.
Severity: 0 : Information Severity: 30 : Severe error
Explanation: MQ has attempted to display the Explanation: WebSphere MQ is unable to submit job
message associated with return code hexadecimal <insert_3>.
<insert_6>. The return code indicates that there is no
message text associated with the message. Associated
AMQ6107 CCSID not supported.
with the request are inserts <insert_1> : <insert_2> :
<insert_3> : <insert_4> : <insert_5>. Severity: 30 : Severe error
Response: Use the standard facilities supplied with Explanation: WebSphere MQ is unable to convert
your system to record the problem identifier, and to string data in CCSID <insert_1> to data in CCSID
save the generated output files. Contact your IBM <insert_2>, because one of the CCSIDs is not
support center. Do not discard these files until the recognized.
AMQ6091 An internal WebSphere MQ error has National Language Support publications to see if the
occurred. CCSIDs are supported by your system.
Explanation: Private memory has detected an error,
occurred.
and is abending due to <insert_3>. The error data is
<insert_1>. Severity: 30 : Severe error
Response: Use the standard facilities supplied with Explanation: An error has been detected, and the MQ
your system to record the problem identifier, and to error recording routine has been called.
save the generated output files. Contact your IBM
support center. Do not discard these files until the Response: Use the standard facilities supplied with
problem has been resolved. your system to record the problem identifier, and to
AMQ6092 (Windows) Manual conversion required problem has been resolved.
for CCSID: <insert_1>
Severity: 0 : Information AMQ6110 An internal WebSphere MQ error has
occurred.
Explanation: CCSID <insert_1> exists in new format
but could not be reconciled against your old format. Severity: 30 : Severe error
Response: Manually edit CCSID entry <insert_1> in Explanation: An error has been detected, and the MQ
conv\table\ccsid.tbl if you wish to retain your old error recording routine has been called.
conversion. For assistance call your Service
Representative. Response: Use the standard facilities supplied with
AMQ6100 An internal WebSphere MQ error has support center. Do not discard these files until the
occurred. problem has been resolved.
AMQ6112 (iSeries) WebSphere MQ CCSID
Explanation: MQ has detected an error, and is
<insert_1> is using a default value.
abending due to <insert_3>. The error data is
<insert_1>. Severity: 10 : Warning
Response: Use the standard facilities supplied with Explanation: When initializing WebSphere MQ, no
your system to record the problem identifier, and to valid job CCSID was found, so the CCSID used is the
save the generated output files. Contact your IBM default 37. This warning message will be issued until a
support center. Do not discard these files until the valid CCSID has been set correctly.
Response: Set the job CCSID.
Chapter 4. 6000-6999 - Common services 65

AMQ6114 (iSeries) An internal WebSphere MQ error
has occurred.
Severity: 30 : Severe error support center. Do not discard these files until the
Response: Use WRKPRB to record the problem
occurred.
identifier, and to save the QPSRVDMP, QPJOBLOG,
and QPDSPJOB files. Contact your IBM support center. Severity: 40 : Stop Error
Do not discard these files until the problem has been
resolved.
Response: MQ has detected a parameter count of
<insert_1> that is not valid. Use the standard facilities
occurred.
supplied with your system to record the problem
Severity: 10 : Warning identifier, and to save the generated output files.
Contact your IBM support center. Do not discard these
occurred.
support center. Do not discard these files until the Severity: 40 : Stop Error
Response: MQ has detected parameter <insert_1> that
occurred (<insert_1>)
is not valid, having value <insert_2><insert_3>. Use the
Severity: 40 : Stop Error standard facilities supplied with your system to record
the problem identifier, and to save the generated
occurred.
problem has been resolved. Severity: 40 : Stop Error
Explanation: An internal error has occurred with
AMQ6119 An internal WebSphere MQ error has identifier <insert_1>. This message is issued in
occurred (<insert_3>) association with other messages.
Severity: 40 : Stop Error Response: Use the standard facilities supplied with
Explanation: MQ detected an unexpected error when
calling the operating system. The MQ error recording
AMQ6134 (iSeries) Trace continues in buffer
support center. Do not discard these files until the Severity: 0 : Information
AMQ6135 (iSeries) Stopping early trace
occurred.
abending due to <insert_3>. The error data is
AMQ6136 (iSeries) Stopping early trace <insert_3>
<insert_1>.
system time
AMQ6137 (iSeries) Resuming MQI trace support center. Do not discard these files until the
AMQ6150 (iSeries) WebSphere MQ resource

AMQ6138 (iSeries) Resuming MQI trace <insert_3>
<insert_3> busy.
system time
Explanation: MQ was unable to access an MQ object
within the normal timeout period of <insert_1>
AMQ6139 (iSeries) Stopping MQI trace
minutes.
Response: MQ will continue to wait for access. Ensure
that all jobs using MQ are released. If the situation
AMQ6140 (iSeries) Stopping MQI trace <insert_3> persists, quiesce the queue manager.
system time
Severity: 0 : Information AMQ6150 (Windows) WebSphere MQ semaphore is
busy.
AMQ6141 (iSeries) Starting MQI trace Severity: 10 : Warning
Severity: 0 : Information Explanation: WebSphere MQ was unable to acquire a
semaphore within the normal timeout period of
<insert_1> minutes.
AMQ6142 (iSeries) Starting MQI trace <insert_3>
system time Response: MQ will continue to wait for access. If the
situation does not resolve itself and you suspect that
Severity: 0 : Information your system is locked then investigate the process
which owns the semaphore. The PID of this process
AMQ6143 (iSeries) WebSphere MQ function stack will be documented in the accompanying FFST.
AMQ6151 (iSeries) WebSphere MQ resource
<insert_3> released.
AMQ6144 (iSeries) No stack available
Explanation: An MQ resource, for which another
process has been waiting, for a period of over
AMQ6145 (iSeries) Terminating MQI trace <insert_1> minutes has been released.
Severity: 0 : Information Response: No recovery is needed.
AMQ6146 (iSeries) Entering end job processing AMQ6152 (iSeries) WebSphere MQ failed to end
Severity: 0 : Information commitment control while attempting to
quiesce a queue manager.
AMQ6147 (iSeries) Terminating MQI trace <insert_3> Severity: 30 : Severe error

system time Explanation: WebSphere MQ failed to end
Severity: 0 : Information commitment control whilst quiescing queue manager
<insert_3>.
AMQ6148 An internal WebSphere MQ error has Response: There are one or more active resources
occurred. under commitment control. Use the Work with Job
(WRKJOB) command with the OPTION(*CMTCTL)
Severity: 0 : Information parameter to display the active resources under
Explanation: MQ has detected an error, and is commitment control. Check the job log for previously
issued messages.

AMQ6153 (iSeries) The attempt to quiesce queue AMQ6162 An error has occurred reading an INI
manager <insert_3> failed file.
Severity: 30 : Severe error Severity: 20 : Error
Explanation: The attempt to quiesce queue manager Explanation: An error has occurred when reading the
<insert_3> was unsuccessful MQS.INI file or a queue manager QM.INI file.
Response: Check the job log for previously issued Response: If you have been changing the INI file
messages. If the quiesce was issued with the *CNTRLD content check and correct the change. If you have not
option, re-issue the command with the *IMMED option. changed the INI file, use the standard facilities
If a low TIMEOUT retry delay was used, re-issue the supplied with your system to record the problem
request with a higher value. identifier, and to save the generated output files.
AMQ6154 (iSeries) Queue manager <insert_3> has
been quiesced.
AMQ6162 (Windows) An error occurred when
reading the configuration data.
Explanation: The queue manager has been
successfully quiesced.
Explanation: An error has occurred when reading the
Response: None.
configuration data.
Response: If you have changed the configuration data,
AMQ6158 (iSeries) SBCS CCSID not found.
check and correct the change. If you have not changed
Severity: 30 : Severe error the configuration data, use the standard facilities
Explanation: WebSphere MQ is unable to find an identifier, and to save the generated output files.
SBCS CCSID which corresponds to mixed DBCS-SBCS Contact your IBM support center. Do not discard these
CCSID <insert_1>. files until the problem has been resolved.
Response: Check the CCSID of your job or system
and check it has a SBCS equivalent. Refer to the AMQ6163 An error has occurred locking an INI
National Language Support Planning Guide for file.
character sets and CCSIDs supported. If the CCSID
used does have an SBCS equivalent, save the job log Severity: 10 : Warning
containing this message and contact your IBM support
Explanation: An error has occurred locking the
center.
MQS.INI file or a queue manager QM.INI file.
Response: If you have been changing the INI file
AMQ6159 (iSeries) WebSphere MQ job submission
permissions check and correct the change. If you have
error.
not changed the INI file, use the standard facilities
Severity: 30 : Severe error supplied with your system to record the problem
identifier, and to save the generated output files.
Explanation: WebSphere MQ for iSeries is unable to Contact your IBM support center. Do not discard these
release job <insert_3>. files until the problem has been resolved.
Response: Contact you System Administrator to
remove job <insert_3>. Ensure you have *JOBCTL AMQ6163 (Windows) An error has occurred locking
authority and try again. the configuration data.
AMQ6160 EXPLANATION:
Severity: 0 : Information configuration data.
Response: If you have changed the the registry
AMQ6161 ACTION: permissions, check and correct the change. If you have
Severity: 0 : Information not changed the registry, use the standard facilities
AMQ6164 An expected stanza in an INI file is AMQ6172 No codeset found for current locale.
missing or contains errors.
Explanation: No codeset could be determined for the
Explanation: An expected stanza is missing from the current locale. Check that the locale in use is
MQS.INI file or a queue manager QM.INI file or the supported.
stanza contains errors.
Response: None.
content check and correct the change.
AMQ6173 No CCSID found for codeset <insert_3>.
AMQ6164 (Windows) An expected stanza in the
configuration data is missing or contains Explanation: Codeset <insert_3>. has no supported
errors. CCSID. Check that the locale in use is supported.
CCSIDs can be added by updating the file
/var/mqm/conv/table/ccsid.tbl.
Explanation: An expected stanza is missing from the
Response: None.
configuration data or the stanza contains errors.
AMQ6174 The library <insert_3> was not found.
check and correct the change.
The queue manager will continue
without this module.
AMQ6165 Unable to access an INI file.
Explanation: The dynamically loadable library
Explanation: Access to the MQS.INI file or a queue <insert_3> was not found.
manager QM.INI file is denied.
Response: Check that the file exists and is either fully
Response: If you have been changing the INI file qualified or is in the appropriate directory.
permissions check and correct the change.
AMQ6174 (iSeries) The library was not found.
AMQ6165 (Windows) Unable to access the
configuration data.
Explanation: The dynamically loadable file <insert_3>
was not found. The queue manager will continue
Explanation: Access to the configuration data is without this module.
denied.
Response: Check that the file exists and is either fully
Response: If you have changed the configuration data qualified or is in the appropriate directory.
permissions, check and correct the changes.
AMQ6174 (Unix) The dynamically loadable shared
AMQ6166 An INI file is missing. library <insert_3> was not found. The
system returned error number <insert_2>
and error message <insert_4>. The queue
Explanation: The MQS.INI file or a queue manager manager will continue without this
QM.INI file is missing. module.
Response: If you have been changing the INI file Severity: 0 : Information
recover the previous file and retry the operation.
Explanation: This message applies to UNIX systems.
The shared library <insert_3> was not found.
AMQ6166 (Windows) An entry in the configuration
Response: Check that the file exists, and is either fully
data is missing.
qualified or is in the appropriate director, also check
Severity: 20 : Error the file access permissions.
Explanation: A required entry in the configuration
data is missing.
recover the previous configuration data and retry the
operation.

generated output files. Contact your IBM support
AMQ6175 (AIX) The system could not dynamically
center. Do not discard these files until the problem has
load the shared library <insert_3>. The
been resolved.
system returned error number <insert_2>
and error message <insert_4>. The queue
manager will continue without this AMQ6179 The system could not find symbol
module. <insert_5> in the dynamically loaded
library <insert_3>. The system returned
error number <insert_2> and error
Explanation: This message applies to AIX systems. message <insert_4>.
The shared library <insert_3> failed to load correctly
due to a problem with the library.
Explanation: The library <insert_3> does not contain
Response: Check the file access permissions and that
symbol <insert_5> or it has not been exported.
the file has not been corrupted.
Response: Check that symbol name <insert_5> is
correct and has been exported from the library.
AMQ6175 (Unix) The system could not dynamically
system returned error message AMQ6179 (Unix) The system could not find the
<insert_4>. The queue manager will symbol <insert_5> in the dynamically
continue without this module. loaded shared library <insert_3>. The
system returned error message
<insert_4>.
due to a problem with the library. Explanation: This message applies to UNIX systems.
The shared library <insert_3> does not contain symbol
Response: Check the file access permissions and that
<insert_5> or it has not been exported.
the file has not been corrupted.
Response: Check that symbol name <insert_5> is
correct and has been exported from the library.
AMQ6175 (Windows) The system could not
dynamically load the library <insert_3>.
The system return code was <insert_1>. AMQ6180 (Windows) Default conversion not
The queue manager will continue supported.
without this module.
Explanation: This message applies to Windows NT string data tagged in CCSID <insert_1> to data in
and Windows 2000 systems only. The dynamically CCSID <insert_2>.
loadable file <insert_3> failed to load correctly due to
an internal error. The MQ error recording routine has Response: Check the default CCSIDs specified in the
been called. ccsid.tbl file and make sure that conversion is
supported between these CCSIDs.
Response: Check that the file has not been corrupted
then use the standard facilities supplied with your
system to record the problem identifier, and to save the AMQ6182 Error found in line <insert_1> of
generated output files. Contact your IBM support ccsid.tbl
center. Do not discard these files until the problem has Severity: 30 : Severe error
been resolved.
Explanation: Line <insert_1> contains and error. The
content of the line is <insert_3>. Processing continues
AMQ6177 (Windows) An internal WebSphere MQ but the line in error is ignored.
error has occurred.
Response: Correct the line and rerun the program or
Severity: 40 : Stop Error command giving this message.
error recording routine has been called. AMQ6183 An internal WebSphere MQ error has
Response: Details of the error have been stored at occurred.
<insert_3>. A synopsis is given in the data section Severity: 10 : Warning
below. Use the standard facilities supplied with your
system to record the problem identifier, and to save the Explanation: An error has been detected, and the
WebSphere MQ error recording routine has been called.
The failing process is process <insert_1>.
Response: Use the standard facilities supplied with load the shared library <insert_3> as the
your system to record the problem identifier, and to entry point to the library, symbol
save the generated output files. Contact your IBM ’MQStart’, could not be located within
support center. Do not discard these files until the the library. The system returned error
problem has been resolved. message <insert_4>. The queue manager
will continue without this library.
AMQ6184 An internal WebSphere MQ error has Severity: 30 : Severe error
occurred on queue manager <insert_3>.
Severity: 10 : Warning The shared library <insert_3> failed to load correctly
Explanation: An error has been detected, and the
WebSphere MQ error recording routine has been called. Response: Check that the entry point to the library,
The failing process is process <insert_1>. symbol ’MQStart’, exists and has been exported from
the library.
save the generated output files. Contact your IBM AMQ6188 (Windows) The system could not
support center. Do not discard these files until the dynamically load the library <insert_3>
problem has been resolved. due to a problem with the dll. The errno
was <insert_1>. The queue manager will
continue without this module.
AMQ6184 (iSeries) An internal WebSphere MQ error
has occurred. Severity: 30 : Severe error
Severity: 10 : Warning Explanation: This message applies to Windows NT
and Windows 2000 systems only. The dynamically
Explanation: An internal MQ error has occurred on loadable file <insert_3> failed to load correctly due to a
queue manager <insert_3> and the MQ error recording problem with the dll.
routine has been called. The failing process is process
<insert_1>. Response: Check that the dll is in the correct place
with the correct file permissions etc. and has not been
Response: Use the standard facilities supplied with corrupted.
support center. Do not discard these files until the AMQ6190 (Windows) Program <insert_3> not found.
Explanation: The program <insert_3> cannot be found.
AMQ6187 User is not authorized for
RestrictedMode queue manager. Response: Check that the program specified is
available on your system. If the program name is not
fully qualified, ensure that the PATH environment
Explanation: All users must be in the RestrictedMode variable includes the directory where the program is
application_group. located.
AMQ6188 (AIX) The system could not dynamically AMQ6191 (Windows) Program <insert_3> failed to
load the shared library <insert_3> as the start, return code <insert_1>.
entry point to the library, symbol
’MQStart’, could not be located within
the library. The queue manager will Explanation: The program <insert_3> was invoked,
continue without this library. but failed to start. The failure reason code is <insert_1>.
Severity: 30 : Severe error Response: Check that the program specified is
available on your system, and that sufficient system
Explanation: This message applies to AIX systems.
resources are available. Where applicable, verify that
the user is authorized to run the program.
Response: Check that the entry point to the library,
symbol ’MQStart’, exists and has been exported from
the library.

AMQ6192 (Windows) IBM WebSphere MQ Utilities AMQ6209 An unexpected asynchronous signal
(<insert_1> : <insert_3>) has been
received and ignored.
AMQ6193 (Windows) The registry entry <insert_3>
was not found. Explanation: Process <insert_2> received an
unexpected asynchronous signal and ignored it. This
has not caused an error but the source of the signal
Explanation: WebSphere MQ for Windows NT and should be determined as it is likely that the signal has
Windows 2000 sets the registry entry <insert_3> when been generated externally to WebSphere MQ.
the product is installed, but the entry is now missing.
Response: Determine the source of the signal and
Response: If the registry has been edited, restore the prevent it from re-occurring.
previous version. If the product is newly installed,
check whether the installation was successful, and
AMQ6212 Failed to load Library <insert_3> as C++
reinstall the product if necessary.
environment is not initialised.
AMQ6196 An error has occurred whilst processing
a temporary INI file <insert_3> Explanation: An attempt was made to load the
identified C++ shared library. However, the attempt
failed because the C++ environment has not been
Explanation: An error has occurred when creating a initialized for the current process.
backup of an INI file. The backup file <insert_4>
Response: Ensure the application is linked with the
already exists
appropriate C++ runtime environment.
Response: You may have created a backup of the INI
file with the name <insert_4>, or an earlier operation
AMQ6218 (AIX) EXTSHM variable detected with
may have failed. Move or delete the file <insert_4> and
unrecognised value <insert_3> and has
reattempt the operation. If you have not changed the
been reset to <insert_4>.
INI file, use the standard facilities supplied with your
system to record the problem identifier, and to save the Severity: 20 : Error
Explanation: Processes that access the internal queue
manager control blocks must use the AIX Extended
been resolved.
Shared Memory model, and while one such process
was starting, WebSphere MQ detected that the
AMQ6207 (AIX) Failed to attach shared memory EXTSHM variable was set but did not contain an
segment as Segment table is Full. appropriate value. This value has been reset and the
process will continue with the new setting.
Response: No further action is required. To prevent
Explanation: When running in native mode an
this message being issued in future, correct the value of
application may attach only 10 shared memory
the EXTSHM variable in your environment.
segments. The application which issued this message
attempted to exceed this number. By setting the
environment variable EXTSHM=ON this limit can be AMQ6230 Message <insert_3> suppressed
removed. Further explanation on using this variable <insert_1> times in the last <insert_4>
and other options available, may be found in the seconds.
documentation.
Response: Either reduce the number of segments to
Explanation: Message <insert_3> was issued
which your application needs to attach or set the
<insert_2> times in the last <insert_4> seconds but only
EXTSHM=ON variable in your environment before
the first instance of the message was written to the log.
starting the application.
The suppressed messages may have included differing
message arguments.
AMQ6208 <insert_3>
Response: If you wish to see all occurrences of this
Severity: 10 : Warning message you should alter the definition of the
SuppressMessage attribute in the Queue Manager
Explanation: <insert_4>
configuration.
Response: <insert_5>
Response: None
AMQ6231 (Unix) Usage: mqchkdir <insert_-a | -m
QMgrName> [-f]
AMQ6237 (Unix) File <insert_3> missing.
Explanation: An incorrect option was specified on the
command line for the command. Explanation: The identified file is missing.
Response: Reissue the command specifying the correct Response: Reissue the command selecting the option
parameters. to create missing files.
AMQ6232 (Unix) Operating System userid <insert_3> AMQ6238 (Unix) Missing file <insert_3> has been
not found. created.
Explanation: A request was made to the operating Explanation: The identified file was missing but has
system to lookup the details of the identified userid but been created.
the request failed.
Response: None
Response: Using the operating system supplied tools
check for the existence of the identified userid, and if
missing then recreate it. AMQ6239 (Unix) Permission denied attempting to
access filesystem location <insert_3>.
AMQ6233 (Unix) Operating System authorisation Severity: 20 : Error

group <insert_3> not found. Explanation: An attempt to query the filesystem object
Severity: 20 : Error identified failed because the command issued did not
have authority to access the object.
Explanation: A request was made to the operating
system to lookup the details of the identified group but Response: Check the authority on the object and of
the request failed. the user executing the command and reissue the
command.
Response: Using the operating system supplied tools
check for the existence of the identified group, and if
missing then recreate it. AMQ6240 (Unix) You must be an operating system
superuser to run this command.
AMQ6234 (Unix) Unknown Queue Manager name Severity: 20 : Error

specified. Explanation: In irder to run this command you must
Severity: 20 : Error be logged on as a user with superuser privelages.
Explanation: An invalid Queue Manager name Response: Log in as an appropriate user and reissue
<insert_3> was specified in the parameters to the the command.
command.
Response: Reissue the command specifying a valid AMQ6241 (Unix) The filesystem object <insert_3> is
Queue Manager name. a symbolic link.
AMQ6235 (Unix) Directory <insert_3> missing. Explanation: While checking the filesystem, an object
Severity: 20 : Error was found which is a symbolic link.
Explanation: The identified directory is missing. Response: This is not an error however you should
verify that the symbolic link is expected and that the
Response: Reissue the command selecting the option destination of the symbolic link is correct.
to create missing directories.
AMQ6242 (Unix) Incorrect ownership for <insert_3>.
AMQ6236 (Unix) Missing directory <insert_3> has Current(<insert_1>) Expected(<insert_2>)
been created.
Explanation: The filesystem object <insert_3> is owned
Explanation: The identified directory was missing but by the user with uid <insert_1> when it was expected
has been created. to be owned by the user with uid <insert_2>.

Response: Correct the ownership using operating
system commands or reissue the command selecting
the option to fix the incorrect owership.
queue manager will continue without
this module.
AMQ6243 (Unix) Incorrect group ownership for
<insert_3>. Current(<insert_1>)
Expected(<insert_2>) Explanation: This message applies to UNIX systems.
The shared library <insert_3> failed to load as it is
probably a <insert_1>-bit library, a <insert_2>-bit library
Explanation: The filesystem object <insert_3> is owned is required. Note that MQ found and loaded a
by the group with gid <insert_1> when it was expected <insert_2>-bit library named <insert_4> however this
to be owned by the group with gid <insert_2>. also failed to load with the system returning error
message <insert_5>. The following message gives
Response: Correct the ownership using operating details of the original failure.
system commands or reissue the command selecting
the option to fix the incorrect owership. Response: Supply the name of a <insert_2>-bit library.
AMQ6244 (Unix) Incorrect permissions on object AMQ6253 (Unix) The system could not dynamically
<insert_3>. Current(<insert_4>) load the shared library <insert_3>. The
Expected(<insert_5>) queue manager will continue without
this module.
Explanation: The filesystem object <insert_3> has the
wrong file permissions. Explanation: This message applies to UNIX systems.
Response: Correct the ownership using operating probably a <insert_1>-bit library, a <insert_2>-bit library
system commands or reissue the command selecting is required. Note that MQ attempted to locate and load
the option to fix the incorrect owership. a <insert_2>-bit library named either of these:
<insert_4>. The first library failed to load as it also is
AMQ6245 (Unix) Error executing system call probably a <insert_1>-bit library, the second library is a
<insert_3> on file <insert_4> error <insert_2>-bit library, however this also failed to load
<insert_2>. with the system returning error message <insert_5>.
The following message gives details of the original
Severity: 20 : Error failure.
Explanation: The execution of the system call Response: Supply the name of a <insert_2>-bit library.
<insert_3> on file <insert_4> failed and the error code
<insert_2> was returned.
Response: Investigate the cause of the failure using load the shared library <insert_3>,
the operating system error code <insert_1> and reissue library <insert_4> has been used instead.
the command.
AMQ6251 (Unix) The system could not dynamically Explanation: This message applies to UNIX systems.
load the shared library <insert_3>. The The shared library <insert_3> failed to load as it is
queue manager will continue without probably a <insert_1>-bit library, a <insert_2>-bit library
this module. is required. Note that MQ has sucessfully located and
loaded a <insert_2>-bit library named <insert_4>.
Response: Supply the name of a <insert_2>-bit library
Explanation: This message applies to UNIX systems. or put the library (alternatively a symbolic link can be
The shared library <insert_3> failed to load as it is used) in the appropriate place: 32-bit libraries in
probably a <insert_1>-bit library, a <insert_2>-bit library /var/mqm/exits; 64-bit libraries in /var/mqm/exits64.
is required. Note that MQ tried to find a <insert_2>-bit
library named either <insert_4> or <insert_5>, but
failed. The following message gives details of the AMQ6255 (Unix) The system could not dynamically
original failure. load the shared library <insert_3>. The
queue manager will continue without
Response: Supply the name of a <insert_2>-bit library. this module.
AMQ6260 Help Topic not found
is required. The following message gives details of the Severity: 10 : Warning
original failure.
Explanation: The requested help topic could not be
Response: Supply the name of a <insert_2>-bit library. located.
For further assistance, please refer to the WebSphere
MQ manuals.
load the shared library <insert_3>. The Response: Ensure that the WebSphere MQ InfoCenter
queue manager will continue without is installed.
this module.
Severity: 30 : Severe error AMQ6261 (Unix) An exception occurred trying to
dynamically load shared library
<insert_3>. The queue manager will
continue without this module.
is required. Note that MQ tried to find a <insert_2>-bit Severity: 30 : Severe error
library named <insert_4>, but failed. The following
message gives details of the original failure.
Exception number <insert_1> name <insert_4>, occurred
Response: Supply the name of a <insert_2>-bit library. trying to dynamically load shared library <insert_3>.
Response: Check the shared library has not been
AMQ6257 Message suppression enabled for corrupted. If the shared library contains any initializer
message numbers (<insert_3>). functions, ensure these are not causing the problem and
that they conform to the expected function prototype.
Explanation: The message contain’s a list of message
AMQ6261 (Windows) An exception occurred trying
id’s for which entries repeated within the <insert_1>
to load DLL <insert_3>. The queue
suppression interval will be suppressed.
manager will continue without this
Response: If you wish to see all occurrences of these module.
messages you should alter the definition of the
SuppressMessage attribute in the Queue Manager
configuration. Explanation: This message applies to Windows
systems only. Exception number <insert_1> error
<insert_4>, occurred trying to load DLL <insert_3>.
AMQ6258 Message exclusion enabled for message
numbers (<insert_3>). Response: Check the DLL has not been corrupted. If
the DLL contains any initializer functions, ensure these
are not causing the problem and that they conform to
Explanation: The message contain’s a list of message the expected function prototype.
id’s which have been excluded. Requests to write these
messages to the error log will be discarded.
AMQ6666 (iSeries) Required WebSphere MQ system
Response: If you wish to see instances of these profile(s) can not be accessed.
messages you should alter the definition of the
ExcludeMessage attribute in the Queue Manager
configuration. Explanation: The required MQ system profile(s)
QMQM and/or QMQMADM are not found or have
been disabled. MQ can not continue processing the
AMQ6259 Message <insert_3> cannot be <insert_4>.
command without the profiles existing and enabled on
Severity: 10 : Warning the system. The major error code is <insert_3>, the
minor error code is <insert_4>. The major error codes
Explanation: Message <insert_3> cannot be excluded and their meanings are as follows: *DISABLED - The
or suppressed but was specified in the ExcludeMessage user profile has been disabled. *PWDEXP - The
or SuppressMessage configuration for the Queue password for the user profile has expired . *EXIST -
Manager. The Queue Manager will continue however The user profile does not exist. If none of these error
the request to suppress or exclude this message will be codes are shown the major error code contains the
ignored. exception identifier. The minor error code identifies the
Response: Update the Queue Manager configuration user profile which cannot be accessed.
to remove the specified message identifier. Response: Check that both QMQM and QMQMADM

profiles exist and are both enabled using the manager’s configuration file matches the intended log
DSPUSRPRF command, or contact the WebSphere MQ path.
system administrator.
AMQ6767 Log file <insert_3> could not be opened
AMQ6708 A disk full condition was encountered for use.
when formatting a new log file in
location <insert_3>.
Explanation: Log file <insert_3> could not be opened
for use. Possible reasons include the file being missing,
Explanation: The queue manager attempted to format the queue manager being denied permission to open
a new log file in directory <insert_3>. The drive or file the file or the contents of the file being incorrect.
system containing this directory did not have sufficient
Response: If the log file was required to start the
free space to contain the new log file.
queue manager, ensure that the log file exists and that
Response: Increase the amount of space available for the queue manager is able to read from and write to it.
log files and retry the request. If the log file was required to recreate an object from its
media image and you do not have a copy of the
required log file, delete the object instead of recreating
AMQ6708 (iSeries) A disk full condition was
it.
encountered when formatting a new log
file.
AMQ6774 Log file <insert_3> did not contain the
requested log record.
Explanation: The queue manager attempted to format
a new log file in directory <insert_3>. The drive or file
system containing this directory did not have sufficient Explanation: Log file <insert_3> does not contain the
free space to contain the new log file. log record whose LSN is <insert_4>. This is because the
log file numbers have wrapped and the log file name
Response: Increase the amount of space available for
<insert_3> has been reused by a newer file. Once a log
log files and retry the request.
file name has been reused, it is not possible to access
the data in the previous versions of the file to use this
AMQ6709 The log for the Queue manager is full. name. The operation which requested this log record
cannot be completed.
Explanation: This message is issued when an attempt AMQ6782 The log file numbers have wrapped.
to write a log record is rejected because the log is full.
The queue manager will attempt to resolve the Severity: 0 : Information
problem.
Explanation: Each log file formatted is assigned a
Response: This situation may be encountered during a number which makes up part of its file name. The
period of unusually high message traffic. However, if numbers are allocated sequentially and consist of seven
you persistently fill the log, you may have to consider digits giving a maximum of 10 million different log file
enlarging the size of the log. You can either increase the names. Once all available numbers have been allocated,
number of log files by changing the values in the the queue manager again starts allocating numbers
queue manager configuration file. You will then have to starting from zero. Once a file number has been
stop and restart the queue manager. Alternatively, if re-allocated, you can no longer access data in the
you need to make the log files themselves bigger, you previous log files allocated the same number. The file
will have to delete and recreate the queue manager. numbers wrapped at log sequence number <insert_3>.
Response: You should periodically take media images
AMQ6710 Queue manager unable to access of all WebSphere MQ objects. You must ensure that
directory <insert_3>. media images of all objects which you may need to
recreate do not span more than 10 million log files.
Explanation: The queue manager was unable to access AMQ6901 (iSeries) WebSphere MQ for iSeries
directory <insert_3> for the log. This could be because
the directory does not exist, or because the queue
manager does not have sufficient authority. AMQ6902 (iSeries) WebSphere MQ for iSeries -
Samples
Response: Ensure that the directory exists and that the
queue manager has authority to read and write to it.
Ensure that the LogPath attribute in the queue
AMQ6903 (iSeries) Installation failed, WebSphere AMQ6907 (iSeries) All WebSphere MQ pre-requisite
MQ resources are still active. PTFs on OS/400 programs are installed.
Severity: 30 : Severe error Severity: 0 : Information
Explanation: An attempt to install WebSphere MQ Explanation: None.
was unsuccessful because MQ resources from a
Response: None.
previous installation of MQ are still active. This failure
may indicate that a queue manager from a previous
installation of MQ is still running or has active jobs. AMQ6908 (iSeries) WebSphere MQ pre-requisite
PTF <insert_4> for program <insert_3> is
Response: Ensure that all queue managers from
not installed.
previous installations of WebSphere MQ have been
quiesced, and that the QMQM subsystem is not active Severity: 40 : Stop Error
using the WRKSBS and ENDSBS commands. Refer to
the installation section in the WebSphere MQ for iSeries Explanation: PTF <insert_3>-<insert_4> is not installed
Quick Beginnings publication for further details. on system in state ’Permanently applied’ ’Temporarily
applied’ or ’Superseded’. WebSphere MQ installation
will proceed, but you must install the PTF before
AMQ6904 (iSeries) Installation of WebSphere MQ starting WebSphere MQ.
for iSeries failed due to previous release
installed. Response: Use the command GO CMDPTF to display
commands to order and apply the required PTF
Explanation: Some releases of WebSphere MQ for <insert_3>-<insert_4>..
iSeries require migration before a later release can be
installed.
AMQ6909 (iSeries) User space recovery failed,
Response: WebSphere MQ is running.
If you wish to retain your current MQ information you
must step through the migration process - see the Severity: 30 : Severe error
Quick Beginnings Manual. Explanation: An attempt to recover user space was
If you do not wish to retain your current MQ unsuccessful because MQ was running.
information remove the current version of MQ before
retrying the install. Response: Quiesce WebSphere MQ for iSeries and try
again. See the section on ″Quiescing WebSphere MQ″ in
the WebSphere MQ for iSeries Quick Beginnings.
AMQ6905 (iSeries) Found <insert_3> new MQ jobs to
end, and <insert_4> MQ jobs currently
ending. AMQ6910 (iSeries) The attempt to quiesce the queue
manager failed.
Explanation: Jobs with locks on library QMQM are
ended so that WebSphere MQ may be deleted or Explanation: The attempt to quiesce the queue
updated. manager was unsuccessful because the current job has
locks on library QMQM.
Response: None.
Response: Sign off the current job, sign on and
attempt to quiesce the queue manager again. See the
AMQ6906 (iSeries) <insert_3> jobs still ending. section on ″Quiescing WebSphere MQ″ in the
Severity: 40 : Stop Error WebSphere MQ for iSeries Quick Beginnings.
Explanation: Jobs report state of ’already being

deleted’ after timeout. AMQ6911 (iSeries) WebSphere MQ quiesce is
performing a RCDMQMIMG, please
Response: If system is heavily loaded wait and reissue wait.
the command CALL QMQM/AMQIQES4 to try to
delete jobs using WebSphere MQ resources. If this Severity: 0 : Information
message is issued again, issue the command Explanation: WebSphere MQ quiesce is performing a
WRKOBJLCK for library QMQM to see which jobs Record Object Image (RCDMQMIMG) for all objects.
have not been deleted, and end them manually. Please wait, there may be some delay until this is
completed.
Response: None.

AMQ6912 (iSeries) WebSphere MQ for iSeries - Java AMQ6998 (iSeries) An internal WebSphere MQ error
has occurred.
AMQ6913 (iSeries) WebSphere MQ for iSeries - Java Severity: 40 : Stop Error
samples
Explanation: WebSphere MQ for iSeries is diagnosing
an unexpected error.
AMQ6988 yes
Response: Save the job log, and contact your IBM
Severity: 0 : Information support center.
AMQ6988 (iSeries) Yes AMQ6999 (iSeries) An internal WebSphere MQ error

has occurred.
AMQ6989 no Severity: 0 : Information
Severity: 0 : Information Explanation: WebSphere MQ has experienced an
internal failure, from which it could not recover.
AMQ6989 (iSeries) No Response: Use WRKPRB to check if a problem has
been created. If one has, record the problem identifier,
and save the QPSRVDMP, QPJOBLOG, and QPDSPJOB
AMQ6992 (iSeries) Program <insert_3> parameter
files. If a problem has not been created, save the job
error.
log. Contact your IBM support center. Do not discard
Severity: 40 : Stop Error these files until the problem has been resolved.
Explanation: WebSphere MQ for iSeries program
<insert_3> has an incorrect number of parameters, or an
error in the parameter value.
Response: Display the job log, using the DSPJOBLOG
command, for more information on the problem.
AMQ6993 (iSeries) Program <insert_3> ended

abnormally.
Explanation: A WebSphere MQ for iSeries program,
<insert_3>, is ending abnormally.
Response: Display the job log, using the DSPJOBLOG
command, for information why the job or subsystem
ended abnormally. Correct the error and retry the
request.
AMQ6994 (Windows) 5724-H72 (C) Copyright IBM

Corp. 1994, 2004. ALL RIGHTS
RESERVED.
Explanation: None.
Response: None.
AMQ6995 (iSeries) xcsFFST has been called; take a

look at the job log.
Chapter 5. 7000-7999 - MQSeries product
messages.
file. In the case where the object that cannot be deleted

AMQ7001 The location specified for creation of the
is a directory then a non MQ process may be accessing
queue manager is not valid.
a file within the directory or one of its subdirectories.
Severity: 40 : Stop Error It is also possible that the error was caused by a disk
having insufficient space, or by problems with
Explanation: The directory under which queue
authorization to the underlying filesystem.
managers are to be created is not valid. It may not
exist, or there may be a problem with authorization. Response: Identify the file that caused the error, using
problem determination techniques. For example check
Response: The location is specified in the
if there are any FFST files, which may identify the
machine-wide ini file. Correct the file and submit the
queue manager file causing the error. This error may
request again.
also be caused if users have created, renamed or
deleted that file. Correct the error in the filesystem and
AMQ7001 (Windows) The location specified for the submit the request again.
creation of the queue manager is not
valid.
AMQ7005 The queue manager is running.
Explanation: The directory under which the queue
Explanation: You tried to perform an action that
managers are to be created is not valid. It may not
requires the queue manager stopped, however, it is
exist, or there may be a problem with authorization.
currently running. You probably tried to delete or start
Response: The location is specified in the a queue manager that is currently running.
configuration data. Correct the configuration data and
Response: If the queue manager should be stopped,
submit the request again.
stop the queue manager and submit the failed
command again.
AMQ7002 An error occurred manipulating a file.
Severity: 40 : Stop Error AMQ7006 Missing attribute <insert_5> on stanza
starting on line <insert_1> of ini file
Explanation: An internal error occurred while trying <insert_3>.
to create or delete a queue manager file. It is likely that
the error was caused by a disk having insufficient Severity: 20 : Error
space, or by problems with authorization to the
Explanation: The <insert_4> stanza starting on line
underlying filesystem.
<insert_1> of configuration file <insert_3> is missing the
Response: Identify the file that caused the error, using required <insert_5> attribute.
problem determination techniques. For example check
Response: Check the contents of the file and retry the
if there are any FFST files, which may identify the
operation.
queue manager file causing the error. This error may
also be caused if users have created, renamed or
deleted that file. Correct the error in the filesystem and AMQ7006 (Windows) Missing attribute <insert_5>
submit the request again. from configuration data.
AMQ7002 (Windows) An error occurred
Explanation: The <insert_4> stanza in the
manipulating a file.
configuration data is missing the required <insert_5>
Severity: 40 : Stop Error attribute.
Explanation: An internal error occurred while trying Response: Check the contents of the configuration
to create or delete a queue manager file. data and retry the operation.
In the case of a failure to delete a file a common reason
for this error is that a non MQ process, such as the
AMQ7008 The queue manager already exists.
windows explorer or a virus checker, is accessing the

AMQ7015 There is an error in the maximum
Explanation: You tried to create a queue manager that number of open object handles
already exists. specified.
Response: If you specified the wrong queue manager Severity: 40 : Stop Error
name, correct the name and submit the request again.
Explanation: You specified a value for the maximum
number of open object handles to be allowed that is not
AMQ7010 The queue manager does not exist. valid. The value must be not less than zero and not
greater than 999 999 999.
Response: Correct the value and submit the command
Explanation: You tried to perform an action against a again.
queue manager that does not exist. You may have
specified the wrong queue manager name.
AMQ7016 There is an error in the maximum
Response: If you specified the wrong name, correct it number of uncommitted messages
and submit the command again. If the queue manager specified.
should exist, create it, and then submit the command
again. Severity: 40 : Stop Error
Explanation: You specified a value for the maximum
AMQ7011 The queue manager files have not been number of uncommitted messages to be allowed that is
completely deleted. not valid. The value must be not less than 1 and not
greater than 999 999 999.
Response: Correct the value and submit the command
Explanation: While deleting the queue manager, an again.
error occurred deleting a file or directory. The queue
manager may not have been completely deleted.
AMQ7017 Log not available.
Response: Follow problem determination procedures
to identify the file or directory and to complete deletion Severity: 40 : Stop Error
Explanation: The queue manager was unable to use
the log. This could be due to a log file being missing or
AMQ7012 The specified trigger interval is not damaged, or the log path to the queue manager being
valid. inaccessible.
Severity: 40 : Stop Error Response: Ensure that the LogPath attribute in the
queue manager configuration file is correct. If a log file
Explanation: You specified a value for the trigger is missing or otherwise unusable, restore a backup copy
interval that is not valid. The value must be not less of the file, or the entire queue manager.
than zero and not greater than 999 999 999.
Response: Correct the value and resubmit the request. AMQ7018 The queue manager operation cannot be
completed.
AMQ7013 There is an error in the name of the Severity: 20 : Error
specified dead-letter queue.
Explanation: An attempt has been made to perform
Severity: 40 : Stop Error an operation on a queue manager. Resources required
Explanation: You specified a name for the dead-letter to perform the operation are not available.
queue that is not valid.
Response: Correct the name and resubmit the request. AMQ7019 An error occurred while creating the
directory structure for the new queue
manager.
AMQ7014 There is an error in the name of the
specified default transmission queue. Severity: 40 : Stop Error
Severity: 40 : Stop Error Explanation: During creation of the queue manager an

error occurred while trying to create a file or directory.
Explanation: You specified a name for the default
transmission queue that is not valid. Response: Identify why the queue manager files
cannot be created. It is probable that there is
Response: Correct the name and submit the command insufficient space on the specified disk, or that there is
again. a problem with access control. Correct the problem and
submit the command again.
AMQ7020 The operation was carried out, but one AMQ7023 The resource manager was in an invalid
or more transactions remain in-doubt. state.
Severity: 10 : Warning Severity: 20 : Error
Explanation: The queue manager tried to resolve all Explanation: The resource manager, the identification
internally coordinated transactions which are in-doubt. number of which you supplied, was in an invalid state.
In-doubt transactions still remain after the queue
Response: Ensure that you entered the correct
manager has attempted to deliver the outcome of these
resource manager identification number. Use the
transactions to the resource managers concerned.
DSPMQTRN command to display a list of resource
Transactions remain in-doubt when the queue manager
managers and their identification numbers. A resource
cannot deliver the outcome of the transaction to each of
manager is in an invalid state, if it is still available to
the participating resource managers. For example, a
resolve the transaction, use the -a optional flag to
resource manager may not be available at this time.
resolve this and all other internally coordinated
Response: Use the DSPMQTRN command to display in-doubt transactions.
the remaining in-doubt transactions.
AMQ7024 Arguments supplied to a command are
AMQ7020 (iSeries) The operation was carried out, not valid.
but one or more transactions remain
in-doubt.
Explanation: You supplied arguments to a command
that it could not interpret. It is probable that you
Explanation: The queue manager tried to resolve all specified a flag not accepted by the command, or that
internally coordinated transactions which are in-doubt. you included extra flags.
In-doubt transactions still remain after the queue
Response: Correct the command and submit it again.
manager has attempted to deliver the outcome of these
Additional information on the arguments causing the
transactions to the resource managers concerned.
error may be found in the error logs for the queue, or
Transactions remain in-doubt when the queue manager
queue manager, referenced in the command.
cannot deliver the outcome of the transaction to each of
the participating resource managers. For example, a
resource manager may not be available at this time. AMQ7025 Error in the descriptive text argument (-c
parameter) of the crtmqm command.
Response: Use the Work with Transactions
(WRKMQMTRN) command to display the remaining Severity: 40 : Stop Error
in-doubt transactions.
Explanation: The descriptive text you supplied to the
crtmqm command was in error.
AMQ7021 An error occurred while deleting the
directory structure for the queue Response: Correct the descriptive text argument and
manager. submit the command again.

AMQ7026 A principal or group name was invalid.
Explanation: While deleting the queue manager, an
error occurred deleting a file or directory. The queue Severity: 40 : Stop Error
manager may not have been completely deleted. Explanation: You specified the name of a principal or
Response: Follow problem determination procedures group which does not exist.
to identify the file or directory and to complete deletion Response: Correct the name and resubmit the request.
AMQ7027 Argument <insert_3> supplied to

AMQ7022 The resource manager identification command <insert_4> is invalid.
number is not recognized.
Explanation: The argument <insert_3> was supplied to
Explanation: The identification number of the resource the command <insert_4> which could not be
manager you supplied was not recognized. interpreted. This argument is either not accepted by the
Response: Ensure that you entered a valid resource command, or an extra flag has been included.
manager identification number. Use the DSPMQTRN Response: Correct the command and submit it again.
command to display a list of resource managers and
their identification numbers.
Chapter 5. 7000-7999 - MQSeries product 81

AMQ7028 The queue manager is not available for AMQ7042 (iSeries) Media image not available for
use. object <insert_3>.
Severity: 40 : Stop Error Severity: 20 : Error
Explanation: You have requested an action that Explanation: The media image for object <insert_3>,
requires the queue manager running, however, the type <insert_4>, is not available for media recovery. A
queue manager is not currently running. log file containing part of the media image cannot be
accessed.
Response: Start the required queue manager and
submit the command again. Response: A previous message indicates which log file
could not be accessed. Restore a copy of the log file
and all subsequent log files from backup. If this is not
AMQ7030 Quiesce request accepted. The queue
possible, you must delete the object instead.
manager will stop when all outstanding
work is complete.
AMQ7044 Media recovery not allowed.
Explanation: You have requested that the queue
manager end when there is no more work for it. In the Explanation: Media recovery is not possible on a
meantime, it will refuse new applications that attempt queue manager using a circular log. Damaged objects
to start, although it allows those already running to must be deleted on such a queue manager.
complete their work.
Response: None.
Response: None.
AMQ7047 An unexpected error was encountered
AMQ7031 The queue manager is stopping. by a command.
Severity: 40 : Stop Error Severity: 40 : Stop Error
Explanation: You issued a command that requires the Explanation: An internal error occurred during the
queue manager running, however, it is currently in the processing of a command.
process of stopping. The command cannot be run.
Response: Follow problem determination procedures
Response: None to identify the cause of the error.
AMQ7041 Object already exists. AMQ7048 The queue manager name is either not
valid or not known
Explanation: A Define Object operation was
performed, but the name selected for the object is Explanation: Either the specified queue manager name
already in use by an object that is unknown to does not conform to the rules required by WebSphere
WebSphere MQ. The object name selected by MQ was MQ or the queue manager does not exist. The rules for
<insert_3>, in directory <insert_4>, of object type naming MQ objects are detailed in the WebSphere MQ
<insert_5>. Command Reference.
Response: Remove the conflicting object from the MQ Response: Correct the name and submit the command
system, then try the operation again. again.
AMQ7042 Media image not available for object AMQ7053 The transaction has been committed.
<insert_3> of type <insert_4>.
Explanation: The prepared transaction has been
Explanation: The media image for object <insert_3>, committed.
type <insert_4>, is not available for media recovery. A
Response: None.
log file containing part of the media image cannot be
accessed.
AMQ7054 The transaction has been backed out.
Response: A previous message indicates which log file
could not be accessed. Restore a copy of the log file Severity: 0 : Information
and all subsequent log files from backup. If this is not
possible, you must delete the object instead. Explanation: The prepared transaction has been
backed out.
Response: None.
AMQ7060 An error has occurred locking an INI
file.
AMQ7055 The transaction number is not
recognized.
MQS.INI file or a queue manager QM.INI file.
Explanation: The number of the transaction you
supplied was not recognized as belonging to an
permissions check and correct the change. If you have
in-doubt transaction.
not changed the INI file, use the standard facilities
Response: Ensure that you entered a valid transaction supplied with your system to record the problem
number. It is possible that the transaction number you identifier, and to save the generated output files.
entered corresponds to a transaction which was Contact your IBM support center. Do not discard these
committed or backed out before you issued the files until the problem has been resolved.
command to resolve it.
AMQ7060 (Windows) An error has occurred locking
AMQ7056 Transaction number the configuration data.
<insert_1>,<insert_2>.
Explanation: This message is used to report the configuration data.
number of an in-doubt transaction.
Response: If you have changed the configuration data
Response: None. permissions, check and correct the change. If you have
not changed the configuration data, use the standard
facilities supplied with your system to record the
AMQ7059 An error has occurred reading an INI problem identifier, and to save the generated output
file. files. Contact your IBM support center. Do not discard
Severity: 20 : Error these files until the problem has been resolved.
Explanation: An error has occurred when reading the

MQS.INI file or a queue manager QM.INI file. AMQ7061 An expected stanza in an INI file is
missing or contains errors.
content check and correct the change. If you have not Severity: 20 : Error
changed the INI file, use the standard facilities Explanation: An expected stanza is missing from the
supplied with your system to record the problem MQS.INI file or a queue manager QM.INI file or the
identifier, and to save the generated output files. stanza contains errors.
files until the problem has been resolved. Response: If you have been changing the INI file
content check and correct the change.
AMQ7059 (Windows) An error occurred when
reading the configuration data. AMQ7061 (Windows) An expected stanza in the
configuration data is missing or contains
Severity: 20 : Error errors.
Explanation: An error has occurred when reading the Severity: 20 : Error
configuration data.
Explanation: An expected stanza is missing from the
Response: If you have changed the configuration data, configuration data or the stanza contains errors.
check and correct the change. If you have not changed
the configuration data, use the standard facilities Response: If you have changed the configuration data,
supplied with your system to record the problem check and correct the change.
AMQ7062 Unable to access an INI file.
Explanation: Access to the MQS.INI file or a queue
manager QM.INI file is denied.
permissions check and correct the change.

AMQ7062 (Windows) Unable to access the AMQ7065 Insufficient space on disk.
configuration data.
Explanation: The operation cannot be completed due
Explanation: Access to the configuration data is to shortage of disk space.
denied.
Response: Either make more disk space available, or
Response: If you have changed the configuration data reduce the disk requirements of the command you
permissions, check and correct the change. issued.
AMQ7063 An INI file is missing. AMQ7066 There are no prepared transactions.

Severity: 20 : Error Severity: 10 : Warning
Explanation: The MQS.INI file or a queue manager Explanation: There are no prepared transactions to be
QM.INI file is missing. resolved.
Response: If you have been changing the INI file Response: None.
recover the previous file and retry the operation.
AMQ7068 Authority file contains an authority
AMQ7063 (Windows) Configuration data is missing. stanza that is not valid.
Severity: 20 : Error Severity: 40 : Stop Error
Explanation: The configuration data for WebSphere Explanation: A syntax error has been found in one of
MQ is missing. the files containing authorization information for the
queue manager.
recover the previous configuration data and retry the Response: Correct the contents of the incorrect
operation. authorization file by editing it.
AMQ7064 Log path not valid or inaccessible. AMQ7069 The queue manager was created
successfully, but cannot be made the
default.
Explanation: The supplied log path could not be used
by the queue manager. Possible reasons for this include
the path not existing, the queue manager not being able Explanation: The queue manager was defined to be
to write to the path, or the path residing on a remote the default queue manager for the machine when it
device. was created. However, although the queue manager
has been created, an error occurred trying to make it
Response: Ensure that the log path exists and that the
the default. There may not be a default queue manager
queue manager has authority to read and write to it. If
defined for the machine at present.
the queue manager already exists, ensure that the
LogPath attribute in the queue manager’s configuration Response: There is probably a problem with the
file matches the intended log path. machine-wide ini file. Verify the existence of the file, its
access permissions, and its contents. If its backup file
exists, reconcile the contents of the two files and then
AMQ7064 (iSeries) Auxiliary storage pool identifier
delete the backup. Finally, either update the
not found.
machine-wide ini file by hand to specify the desired
Explanation: The auxiliary storage pool identifier default queue manager, or delete and recreate the
supplied does not exist on the system and could not be queue manager.
used by the queue manager to create a journal receiver.
Response: Specify *SYSTEM, or the identifier of an AMQ7069 (Windows) The queue manager was
existing auxiliary storage pool and try the request created successfully, but cannot be made
again. You can use WRKDSKSTS to check the the default.
assignment of disk units to auxiliary storage pools.
Explanation: The queue manager was defined to be
the default queue manager for the machine when it
was created. However, although the queue manager
has been created, an error occurred trying to make it
the default. There may not be a default queue manager
defined for the machine at present.
AMQ7074 (Windows) Unknown stanza key
Response: There is probably a problem with the <insert_4> at <insert_3> in the
configuration data. Update the configuration data to configuration data.
specify the desired default queue manager, or delete
and recreate the queue manager.
Explanation: Key <insert_3> contained a stanza called
<insert_4>. This stanza is not recognized.
AMQ7072 Invalid QM.INI file stanza. Refer to the
error log for more information. Response: Check the contents of the configuration
data and retry the operation.
Explanation: An invalid QM.INI file stanza was
AMQ7075 Unknown attribute in ini file.
found. Refer to the error log for more information.
Response: Correct the error and then retry the
operation. Explanation: Line <insert_1> of the configuration file
<insert_3> contained an attribute called <insert_4> that
is not valid. This attribute is not recognized in this
AMQ7072 (Windows) Stanza not valid. Refer to the
context.
error log for more information.
operation.
Explanation: A stanza that is not valid was found.
Refer to the error log for more information.
AMQ7075 (Windows) Unknown attribute <insert_4>
Response: Correct the error and retry the operation. at <insert_3> in the configuration data.
AMQ7073 Log size not valid.
Explanation: Key <insert_3> in the configuration data
Severity: 40 : Stop Error contained an attribute called <insert_4> that is not
valid. This attribute is not recognized in this context.
Explanation: Either the number of log files or the size
of the log files was outside the accepted values. Response: Check the contents of the configuration
Response: Make sure that the log parameters you
enter lie within the valid range.
AMQ7076 Invalid value for attribute in ini file.
AMQ7074 Unknown stanza key <insert_4> on line Severity: 10 : Warning
<insert_1> of ini file <insert_3>.
Explanation: Line <insert_1> of the configuration file
Severity: 10 : Warning <insert_3> contained value <insert_5> that is not valid
for the attribute <insert_4>.
<insert_3> contained a stanza called <insert_3>. This Response: Check the contents of the file and retry the
stanza is not recognized. operation.
operation. AMQ7076 (Windows) Value <insert_5> not valid for
attribute <insert_4> at <insert_3> in the
configuration data.
AMQ7074 (iSeries) Unknown stanza key.
Explanation: Key <insert_3> in the configuration data
Explanation: Line <insert_1> of the configuration file contained value <insert_5> that is not valid for the
<insert_3> contained a stanza key <insert_4>. This attribute <insert_4>.
stanza is not recognized.
Response: Check the contents of the configuration
Response: Check the contents of the file and retry the data and retry the operation.
operation.

the problem. Rectify the problem and retry the
AMQ7077 You are not authorized to perform the
operation.
requested operation.
AMQ7084 Object <insert_3>, type <insert_4>
Explanation: You tried to issue a command for the damaged.
queue manager. You are not authorized to perform the
command.
Explanation: The object <insert_3>, type <insert_4>
Response: Contact your system administrator to
was damaged. The object must be deleted or, if the
perform the command for you. Alternatively, request
queue manager supports media recovery, recreated
authority to perform the command from your system
from its media image.
administrator.
Response: Delete the object or recreate it from its
media image.
AMQ7078 You entered an object type that is
invalid with a generic profile name.
AMQ7085 Object <insert_3>, type <insert_4> not
found.
Explanation: You entered an object type of *ALL or
*MQM and an object name that contains generic
characters, this is an invalid combination. Explanation: Object <insert_3>, type <insert_4> cannot
be found.
Response: None.
AMQ7080 No objects processed.
AMQ7086 Media image for object <insert_3>, type
<insert_4> recorded.
Explanation: No objects were processed, either
because no objects matched the criteria given, or
because the objects found did not require processing. Explanation: The media image for object <insert_3>,
type <insert_4>, defined in Queue Manager <insert_5>,
Response: None.
has been recorded.
Response: None.
AMQ7081 Object <insert_3>, type <insert_4>
recreated.
AMQ7087 Object <insert_3>, type <insert_4> is a
temporary object
Explanation: The object <insert_3>, type <insert_4>
was recreated from its media image.
Explanation: Object <insert_3>, type <insert_4> is a
Response: None.
temporary object. Media recovery operations are not
permitted on temporary objects.
AMQ7082 Object <insert_3>, type <insert_4> is not
Response: None.
damaged.
AMQ7088 Object <insert_3>, type <insert_4> in use.
Explanation: Object <insert_3>, type <insert_4> cannot
be recreated since it is not damaged.
Explanation: Object <insert_3>, type <insert_4> is in
Response: None
use. Either an application has it open or, if it is a local
queue, there are uncommitted messages on it.
AMQ7083 A resource problem was encountered by
Response: Ensure that the object is not opened by any
a command.
applications, and that there are no uncommitted
Severity: 20 : Error messages on the object, if it is a local queue. Then, retry
the operation.
Explanation: The command failed due to a resource
problem. Possible causes include the log being full or
the command running out of memory.
Response: Look at the previous messages to diagnose
AMQ7089 Media recovery already in progress. AMQ7093 An object type is required but you did
not specify one.
Explanation: Another media recovery operation is
already in progress. Only one media recovery operation Explanation: The command needs the type of the
is permitted at a time. object, but you did not specify one.
Response: Wait for the existing media recovery Response: Correct the command and submit it again.
operation to complete and retry the operation.
AMQ7094 You specified an object type that is not
AMQ7090 (iSeries) The queue manager CCSID is not valid, or more than one object type.
valid.
Explanation: Either the type of object you specified
Explanation: The CCSID to be used by the QMGR is was not valid, or you specified multiple object types on
not valid for the iSeries platform. The CCSID encoding a command which supports only one.
must be a valid EBCDIC value.
Response: Check that the CCSID that you have
entered is a valid EBCDIC value.
AMQ7095 An entity name is required but you did
not specify one.
AMQ7090 (Windows) The queue manager CCSID is
not valid.
Explanation: The command needs one or more entity
names, but you did not specify any. Entities can be
Explanation: The CCSID to be used by the QMGR is principals or groups.
not valid, because:
1) It is a DBCS CCSID.
2) The CCSID encoding is not ASCII or ASCII related.
EBCDIC or UCS2 encodings are not valid on this AMQ7096 An authorization specification is
machine. required but you did not provide one.
3) The CCSID encoding is unknown.
Response: Check the CCSID is valid for the machine
on which you are working. Explanation: The command sets the authorizations on
WebSphere MQ objects. However you did not specify
which authorizations are to be set.
AMQ7091 You are performing authorization for the
queue manager, but you specified an Response: Correct the command and submit it again.
object name.
Severity: 40 : Stop Error AMQ7097 You gave an authorization specification
that is not valid.
Explanation: Modification of authorizations for a
queue manager can be performed only from that queue Severity: 40 : Stop Error
manager. You must not specify an object name. Explanation: The authorization specification you
Response: Correct the command and submit it again. provided to the command contained one or more items
that could not be interpreted.
AMQ7092 An object name is required but you did Response: Correct the command and submit it again.
not specify one.
Severity: 40 : Stop Error AMQ7098 The command accepts only one entity
name. You specified more than one.
Explanation: The command needs the name of an
object, but you did not specify one. Severity: 40 : Stop Error
Response: Correct the command and submit it again. Explanation: The command can accept only one
principal or group name. You specified more than one.

AMQ7099 Entity <insert_3> has the following AMQ7108 (iSeries) Any in-doubt transactions have
authorizations for object <insert_4>: been resolved.
Explanation: Informational message. The list of Explanation: All, if there were any, of the internally
authorizations follows. coordinated transactions which were in-doubt, have
now been resolved.
Response: None.
Response: None.
AMQ7104 Resource manager <insert_1> has
prepared. AMQ7109 A decision on behalf of the unavailable
resource manager has been delivered.
Explanation: This message reports the state of a
resource manager with respect to an in-doubt Explanation: A decision for an internally coordinated
transaction. transaction which was in-doubt, has now been
delivered on behalf of the unavailable resource
Response: None.
manager. This message reports successful completion of
the RSVMQTRN command when the -r option is used.
AMQ7105 Resource manager <insert_1> has
Response: None.
committed.
AMQ7110 Media image for the syncfile recorded.
resource manager with respect to an in-doubt
transaction. Explanation: The media image for the syncfile has
been recorded.
Response: None.
Response: None.
AMQ7106 Resource manager <insert_1> has rolled
back. AMQ7111 Resource manager <insert_1> has
participated.
resource manager with respect to an in-doubt Explanation: This message reports the state of a
transaction. resource manager with respect to an in-doubt
transaction.
Response: None.
Response: None.
AMQ7107 Resource manager <insert_1> is
<insert_3>. AMQ7112 Transaction number <insert_1>,<insert_2>
has encountered an error.
Explanation: This message reports the identification
number and name of a resource manager. Explanation: This message is used to report the
number of an in-doubt transaction which has
Response: None.
encountered an error with one or more resource
managers.
AMQ7108 Any in-doubt transactions have been
Response: Refer to the queue manager error log for
resolved.
more information about which resource managers are
Severity: 0 : Information in error. Ensure that the resource managers that were in
error, are working correctly, restart the queue manager.
Explanation: All, if there were any, of the internally If the problem persists, use the standard facilities
coordinated transactions which were in-doubt, have supplied with your system to record the problem
now been resolved. This message reports successful identifier, and to save the generated output files.
completion of the RSVMQTRN command when the -a Contact your IBM support center. Do not discard these
option is used. files until the problem has been resolved.
Response: None.
Response: Install a Production license for this copy of
AMQ7113 The Database Name argument, -rn, is
WebSphere MQ.
missing from the command crtmqm
AMQ7121 The trial period for this copy of
Explanation: The required flag, -rn, was omitted from WebSphere MQ has now expired.
the command crtmqm
Response: Add the flag and associated database name
Explanation: This copy of WebSphere MQ was
and submit it again.
licensed for a limited period only. This period has now
expired.
AMQ7114 The Database Password argument, -rp,
is missing from the command crtmqm
WebSphere MQ.
Explanation: The required flag, -rp, was omitted from AMQ7122 The Trial Period License Agreement was
the command crtmqm not accepted.
Response: Add the flag and associated database Severity: 10 : Warning
password and submit it again.
Explanation: When the Trial Period License
Agreement is displayed, the user must accept it before
AMQ7115 The Database Type argument, -rt, is this copy of WebSphere MQ can be used.
missing from the command crtmqm
Response: Submit the command again and accept the
Severity: 20 : Error agreement.
Explanation: The required flag, -rt, was omitted from
the command crtmqm AMQ7123 There is one day left in the trial period
for this copy of WebSphere MQ.
Response: Add the flag and associated database type
and submit it again Severity: 0 : Information
Explanation: This copy of WebSphere MQ is licensed
AMQ7116 The Database Type argument, -rt, is for a limited period only.
greater than 8 characters long
Response: None.
Explanation: The argument supplied with the flag -rt, AMQ7124 This is the final day of the trial period
is greater than 8 characters long for this copy of WebSphere MQ.
Response: Reduce the length of the database type Severity: 10 : Warning
argument and submit it again
for a limited period only.
AMQ7117 The MSD shared library failed to load.
Severity: 20 : Error WebSphere MQ.
Explanation: The MSD shared library was either not
located or failed to load correctly. AMQ7125 There are <insert_1> days left in the trial
period for this copy of WebSphere MQ.
Response: Ensure that the database type is specified
correctly when creating a queue manager since this is Severity: 0 : Information
used to form the name of the shared library to be
loaded. Further information on the failure may be
found in the FFST logs. Also, ensure that ensure that
the MSD shared library is installed correctly. Response: None.
AMQ7120 The Trial Period license for this copy of AMQ7126 This copy of WebSphere MQ is now
WebSphere MQ has expired. running in Production mode.
Explanation: This copy of WebSphere MQ was Explanation: A Production license has been installed
licensed to be used in trial mode for a limited period for this copy of WebSphere MQ.
only. This period has expired.

Response: None. PROGRAM TO IBM.
AMQ7127 Press Enter when you have read the
Explanation: This is part of the Trial Period License
messages
Agreement which must be accepted before a trial
Severity: 0 : Information period can be started. A trial period allows a copy of
WebSphere MQ to be used for a limited period only.
Explanation: One or more messages have been
displayed. They will disappear when the user presses Response: None.
the Enter key.
Response: Press the Enter key when the messages are AMQ7132 The Program is owned by International
no longer required. Business Machines Corporation or one
of its subsidiaries (IBM) or an IBM
supplier, and is copyrighted and
AMQ7128 No license installed for this copy of
licensed, not sold.
WebSphere MQ.
The term ″Program″ means the original
Severity: 20 : Error program and all whole or partial copies
of it. A Program consists of
Explanation: The installation of WebSphere MQ is machine-readable instructions, its
invalid since no Production, Beta, or Trial Period components, data, audio-visual content
license has been installed. (such as images, text, recordings, or
Response: Check that the installation steps described pictures), and related licensed materials.
in the Quick Beginnings book have been followed, and Severity: 0 : Information
if the problem persists contact your IBM service
representative. Explanation: This is part of the Trial Period License
period can be started. A trial period allows a copy of
AMQ7129 The trial period for this copy of WebSphere MQ to be used for a limited period only.
WebSphere MQ has already been
started. Response: None.
AMQ7133 This Agreement includes Part 1 -
Explanation: This copy of WebSphere MQ is licensed General Terms and Part 2 - Country
for a limited period only and the trial period has been Unique Terms and is the complete
started previously. agreement regarding the use of this
Response: None. Program, and replaces any prior oral or
written communications between you
and IBM. The terms of Part 2 may
AMQ7130 This copy of WebSphere MQ is running replace or modify those of Part 1.
in Production mode.
Explanation: A Production license has been installed Agreement which must be accepted before a trial
for this copy of WebSphere MQ. A beta or trial period period can be started. A trial period allows a copy of
cannot be started. WebSphere MQ to be used for a limited period only.
AMQ7131 International License Agreement for AMQ7134 1. License

Evaluation of Programs Use of the Program
Part 1 - General Terms IBM grants you a nonexclusive,
PLEASE READ THIS AGREEMENT nontransferable license to use the
CAREFULLY BEFORE USING THE Program.
PROGRAM. IBM WILL LICENSE THE You may 1) use the Program only for
PROGRAM TO YOU ONLY IF YOU internal evaluation, testing or
FIRST ACCEPT THE TERMS OF THIS demonstration purposes, on a trial or
AGREEMENT. BY USING THE ″try-and-buy″ basis and 2) make and
PROGRAM YOU AGREE TO THESE install a reasonable number of copies of
TERMS. IF YOU DO NOT AGREE TO the Program in support of such use,
THE TERMS OF THIS AGREEMENT, unless IBM identifies a specific number
PROMPTLY RETURN THE UNUSED of copies in the documentation
accompanying the Program. The terms
AMQ7137 This license begins with your first use
of this license apply to each copy you
of the Program and ends 1) as of the
make. You will reproduce the copyright
duration or date specified in the
notice and any other legends of
documentation accompanying the
ownership on each copy, or partial copy,
Program or 2) when the Program
of the Program.
automatically disables itself. Unless
Severity: 0 : Information IBM specifies in the documentation
accompanying the Program that you
Explanation: This is part of the Trial Period License may retain the Program (in which case,
Agreement which must be accepted before a trial an additional charge may apply), you
period can be started. A trial period allows a copy of will destroy the Program and all copies
WebSphere MQ to be used for a limited period only. made of it within ten days of when this
Response: None. license ends.
AMQ7135 THE PROGRAM MAY CONTAIN A Explanation: This is part of the Trial Period License
DISABLING DEVICE THAT WILL Agreement which must be accepted before a trial
PREVENT IT FROM BEING USED period can be started. A trial period allows a copy of
UPON EXPIRATION OF THIS WebSphere MQ to be used for a limited period only.
LICENSE. YOU WILL NOT TAMPER
WITH THIS DISABLING DEVICE OR Response: None.
THE PROGRAM. YOU SHOULD TAKE
PRECAUTIONS TO AVOID ANY LOSS
AMQ7138 2. No Warranty
OF DATA THAT MIGHT RESULT
SUBJECT TO ANY STATUTORY
WHEN THE PROGRAM CAN NO
WARRANTIES WHICH CANNOT BE
LONGER BE USED.
EXCLUDED, IBM MAKES NO
Severity: 0 : Information WARRANTIES OR CONDITIONS
EITHER EXPRESS OR IMPLIED,
Explanation: This is part of the Trial Period License INCLUDING WITHOUT LIMITATION,
Agreement which must be accepted before a trial THE WARRANTY OF
period can be started. A trial period allows a copy of NON-INFRINGEMENT AND THE
WebSphere MQ to be used for a limited period only. IMPLIED WARRANTIES OF
Response: None. MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE,
REGARDING THE PROGRAM OR
AMQ7136 You will 1) maintain a record of all TECHNICAL SUPPORT, IF ANY. IBM
copies of the Program and 2) ensure that MAKES NO WARRANTY
anyone who uses the Program does so REGARDING THE CAPABILITY OF
only for your authorized use and in THE PROGRAM TO CORRECTLY
compliance with the terms of this PROCESS, PROVIDE AND/OR
Agreement. RECEIVE DATE DATA WITHIN AND
You may not 1) use, copy, modify or BETWEEN THE 20TH AND 21ST
distribute the Program except as CENTURIES.
provided in this Agreement; 2) reverse This exclusion also applies to any of
assemble, reverse compile, or otherwise IBM’s subcontractors, suppliers or
translate the Program except as program developers (collectively called
specifically permitted by law without ″Suppliers″).
the possibility of contractual waiver; or Manufacturers, suppliers, or publishers
3) sublicense, rent or lease the Program. of non-IBM Programs may provide their
Severity: 0 : Information own warranties.
Explanation: This is part of the Trial Period License Severity: 0 : Information

Agreement which must be accepted before a trial Explanation: This is part of the Trial Period License
period can be started. A trial period allows a copy of Agreement which must be accepted before a trial
WebSphere MQ to be used for a limited period only. period can be started. A trial period allows a copy of
Response: None. WebSphere MQ to be used for a limited period only.
Response: None.

AMQ7139 3. Limitation of Liability
NEITHER IBM NOR ITS SUPPLIERS Explanation: This is part of the Trial Period License
ARE LIABLE FOR ANY DIRECT OR Agreement which must be accepted before a trial
INDIRECT DAMAGES, INCLUDING period can be started. A trial period allows a copy of
WITHOUT LIMITATION, LOST WebSphere MQ to be used for a limited period only.
PROFITS, LOST SAVINGS, OR ANY
INCIDENTAL, SPECIAL, OR OTHER Response: None.
ECONOMIC CONSEQUENTIAL
DAMAGES, EVEN IF IBM IS AMQ7142 Reply ’yes’ to accept the Agreement.
INFORMED OF THEIR POSSIBILITY. Reply ’no’ if you do not agree to the
SOME JURISDICTIONS DO NOT terms of the Agreement. Reply ’no’ and
ALLOW THE EXCLUSION OR submit the command again, if you want
LIMITATION OF INCIDENTAL OR to read the Agreement again.
CONSEQUENTIAL DAMAGES, SO
THE ABOVE EXCLUSION OR Severity: 0 : Information
LIMITATION MAY NOT APPLY TO Explanation: The Trial Period License Agreement has
YOU. been displayed to the user and the user should now
Severity: 0 : Information accept or reject the Agreement.
Explanation: This is part of the Trial Period License Response: Reply ’yes’ or ’no’ and press ’Enter’.
period can be started. A trial period allows a copy of AMQ7143 Press Enter to continue
WebSphere MQ to be used for a limited period only.
Response: None.
Explanation: Part of the Trial Period License
Agreement has been displayed to the user. The user
AMQ7140 4. General should press the Enter key to indicate that they are
Nothing in this Agreement affects any ready for the next part of the Agreement to be
statutory rights of consumers that displayed.
cannot be waived or limited by contract.
Response: Press the Enter key when ready for the
Severity: 0 : Information next part of the Agreement to be displayed.
Agreement which must be accepted before a trial AMQ7144 The laws of the country in which you
period can be started. A trial period allows a copy of acquire the Program govern this
WebSphere MQ to be used for a limited period only. Agreement, except 1) in Australia, the
Response: None. laws of the State or Territory in which
the transaction is performed govern this
Agreement; 2) in Albania, Armenia,
AMQ7141 IBM may terminate your license if you Belarus, Bosnia/Herzegovina, Bulgaria,
fail to comply with the terms of this Croatia, Czech Republic, Georgia,
Agreement. If IBM does so, you must Hungary, Kazakhstan, Kirghizia, Former
immediately destroy the Program and Yogoslav Republic of Macedonia
all copies you made of it. (FYROM), Moldova, Poland, Romania,
You may not export the Program. Russia, Slovak Republic, Slovenia,
Neither you nor IBM will bring a legal Ukraine, and Federal Republic of
action under this Agreement more than Yugoslavia, the laws of Austria govern
two years after the cause of action arose this Agreement; 3) in the United
unless otherwise provided by local law Kingdom, all disputes relating to this
without the possibility of contractual Agreement will be governed by English
waiver or limitation. law and will be submitted to the
Neither you nor IBM is responsible for exclusive jurisdiction of the English
failure to fulfill any obligations due to courts; 4) in Canada, the laws of the
causes beyond its control. Province of Ontario govern this
There is no additional charge for use of Agreement; and 5) in the United States
the Program for the duration of this and Puerto Rico, and People’s Republic
license. of China, the laws of the State of New
IBM does not provide program services York govern this Agreement.
or technical support, unless IBM
specifies otherwise. Severity: 0 : Information
Explanation: This is part of the Trial Period License apply in respect of any goods or services
Agreement which must be accepted before a trial which IBM provides, if you require the
period can be started. A trial period allows a copy of goods and services for the purposes of a
WebSphere MQ to be used for a limited period only. business as defined in the Act.
Response: None. Severity: 0 : Information
AMQ7145 Part 2 - Country Unique Terms Agreement which must be accepted before a trial
AUSTRALIA: period can be started. A trial period allows a copy of
No Warranty (Section 2): WebSphere MQ to be used for a limited period only.
The following paragraph is added to
Response: None.
this Section:
Although IBM specifies that there are
no warranties, you may have certain AMQ7148 Limitation of Liability (Section 3):
rights under the Trade Practices Act 1974 The following paragraph is added to
or other legislation and are only limited this Section:
to the extent permitted by the applicable Where products or services are not
legislation. acquired for the purposes of a business
Limitation of Liability (Section 3): as defined in the Consumer Guarantees
The following paragraph is added to Act 1993, the limitations in this Section
this Section: are subject to the limitations in that Act.
Explanation: This is part of the Trial Period License Explanation: This is part of the Trial Period License
Agreement which must be accepted before a trial Agreement which must be accepted before a trial
period can be started. A trial period allows a copy of period can be started. A trial period allows a copy of
WebSphere MQ to be used for a limited period only. WebSphere MQ to be used for a limited period only.
AMQ7146 Where IBM is in breach of a condition AMQ7149 GERMANY: No Warranty (Section 2):
or warranty implied by the Trade The following paragraphs are added to
Practices Act 1974, IBM’s liability is this Section:
limited to the repair or replacement of The minimum warranty period for
the goods, or the supply of equivalent Programs is six months.
goods. Where that condition or warranty In case a Program is delivered without
relates to right to sell, quiet possession specifications, we will only warrant that
or clear title, or the goods are of a kind the Program information correctly
ordinarily acquired for personal, describes the Program and that the
domestic or household use or Program can be used according to the
consumption, then none of the Program information. You have to check
limitations in this paragraph apply. the usability according to the Program
information within the ″money-back
guaranty″ period.
Explanation: This is part of the Trial Period License Limitation of Liability (Section 3):
Agreement which must be accepted before a trial The following paragraph is added to
period can be started. A trial period allows a copy of this Section:
WebSphere MQ to be used for a limited period only. The limitations and exclusions specified
in the Agreement will not apply to
Response: None.
damages caused by IBM with fraud or
gross negligence, and for express
AMQ7147 NEW ZEALAND: warranty.
No Warranty (Section 2):
this Section: Explanation: This is part of the Trial Period License
Although IBM specifies that there are Agreement which must be accepted before a trial
no warranties, you may have certain period can be started. A trial period allows a copy of
rights under the Consumer Guarantees WebSphere MQ to be used for a limited period only.
Act 1993 or other legislation which
Response: None.
cannot be excluded or limited. The
Consumer Guarantees Act 1993 will not

Supply of Goods and Services Act 1982.
AMQ7150 INDIA:
General (Section 4): Severity: 0 : Information
The following replaces the fourth
paragraph of this Section: Explanation: This is part of the Trial Period License
If no suit or other legal action is Agreement which must be accepted before a trial
brought, within two years after the period can be started. A trial period allows a copy of
cause of action arose, in respect of any WebSphere MQ to be used for a limited period only.
claim that either party may have against Response: None.
the other, the rights of the concerned
party in respect of such claim will be
forfeited and the other party will stand AMQ7153 A license could not be installed for this
released from its obligations in respect copy of WebSphere MQ.
of such claim. Severity: 20 : Error
Severity: 0 : Information Explanation: A Production, Beta or Trial Period license
Explanation: This is part of the Trial Period License could not be installed for this copy of WebSphere MQ.
Agreement which must be accepted before a trial This is because the ’nodelock’ file in the
period can be started. A trial period allows a copy of ’qmgrs/@SYSTEM’ directory could not be created or
WebSphere MQ to be used for a limited period only. updated.
Response: None. Response: Check the ownership and permissions of

the ’qmgrs/@SYSTEM’ directory.
AMQ7151 IRELAND:
No Warranty (Section 2): AMQ7154 The Production license for this copy of
The following paragraph is added to WebSphere MQ has expired.
this Section: Severity: 20 : Error
Except as expressly provided in these
terms and conditions, all statutory Explanation: The production license for this copy of
conditions, including all warranties WebSphere MQ has an expiry date. This date has been
implied, but without prejudice to the passed.
generality of the foregoing all Response: Contact your IBM support center.
warranties implied by the Sale of Goods
Act 1893 or the Sale of Goods and
Supply of Services Act 1980 are hereby AMQ7155 License file <insert_3> not found or not
excluded. valid.
ITALY:
Limitation of Liability (Section 3):
This section is replaced by the Explanation: The program requires that the file
following: <insert_3> is present, available and is a valid license
Unless otherwise provided by file.
mandatory law, IBM is not liable for
Response: Check that the installation steps described
any damages which might arise.
in the Quick Beginnings book have been followed, and
Severity: 0 : Information if the problem persists contact your IBM service
representative.
period can be started. A trial period allows a copy of AMQ7156 This copy of WebSphere MQ is already
WebSphere MQ to be used for a limited period only. running in Production mode.
Explanation: A Production license has previously been
AMQ7152 UNITED KINGDOM: installed for this copy of WebSphere MQ.
Limitation of Liability (Section 3):
Response: None.
this Section at the end of the first
paragraph: AMQ7157 The Production license is not valid for
The limitation of liability will not apply this copy of WebSphere MQ.
to any breach of IBM’s obligations
implied by Section 12 of the Sales of Severity: 20 : Error
Goods Act 1979 or Section 2 of the Explanation: The license <insert_3> has been installed
but it is not a valid production license for this copy of <insert_1> seconds to start job <insert_3> for Queue
WebSphere MQ. Manager: <insert_5>
Response: Submit the SETMQPRD command again Response: Check that the job queue that is associated
specifying the name of a valid production license. with job description <insert_4> is not held, and that the
subsystem that is associated with the job queue is
active.
AMQ7158 The Trial Period license is not valid for
this copy of WebSphere MQ.
AMQ7165 The Beta license for this copy of
WebSphere MQ has expired.
Explanation: The license <insert_3> has been installed
but it is not a valid trial period license for this copy of
WebSphere MQ. Explanation: This copy of WebSphere MQ was
licensed to be used for Beta testing for a limited period
Response: Check that the correct version of the file is
only. This period has expired.
available.
WebSphere MQ.
AMQ7159 A FASTPATH application has ended
unexpectedly.
AMQ7166 The Beta period for this copy of
WebSphere MQ has now expired.
Explanation: A FASTPATH application has ended in a
way which did not allow the queue manager to clean
up the resources owned by that application. Any Explanation: This copy of WebSphere MQ was
resources held by the application can only be released licensed for a limited period only. This period has now
by stopping and restarting the queue manager. expired.
Response: Investigate why the application ended Response: Install a Production license for this copy of
unexpectedly. Avoid ending FASTPATH applications in WebSphere MQ.
a way which prevents WebSphere MQ from releasing
resources held by the application.
AMQ7167 The ’Early Release of Programs License
Agreement’ was not accepted.
AMQ7160 Queue Manager Object
Explanation: When the IBM International License
Agreement for Early Release of Programs is displayed,
AMQ7161 Object Catalogue the user must accept it before this copy of WebSphere
MQ can be used.
Response: Submit the command again and accept the
agreement.
AMQ7162 The setmqaut command completed
successfully.
AMQ7168 There is one day left in the Beta test
AMQ7163 (iSeries) WebSphere MQ job <insert_2>
started for <insert_3>. Explanation: This copy of WebSphere MQ is licensed
Response: None.
Explanation: The job’s PID is <insert_2> the CCSID is
<insert_1>. The job name is <insert_4>.
AMQ7169 This is the final day of the Beta test
Response: None
AMQ7164 (iSeries) WebSphere MQ is waiting for a
job to start. Explanation: This copy of WebSphere MQ is licensed
Explanation: WebSphere MQ has been waiting
WebSphere MQ.

AMQ7170 (iSeries) Option is not valid for this AMQ7173 The term ″Early Release″ means that the
transaction. Program is not formally released or
generally available. The term does not
imply that the Program will be formally
Explanation: The Resolve option is not valid for released or made generally available.
external transactions. The Commit and Backout options IBM does not guarantee that a Program
are not valid for internal transactions. formally released or made generally
available will be similar to, or
Response: Select a different option for this transaction. compatible with, Early Release versions.
THIS AGREEMENT INCLUDES PART
AMQ7171 IBM International License Agreement 1 - GENERAL TERMS AND PART 2 -
for Early Release of Programs COUNTRY-UNIQUE TERMS AND IS
Part 1 - General Terms THE COMPLETE AGREEMENT
PLEASE READ THIS AGREEMENT REGARDING THE USE OF THIS
CAREFULLY BEFORE USING THE PROGRAM, AND REPLACES ANY
PROGRAM. IBM WILL LICENSE THE PRIOR ORAL OR WRITTEN
PROGRAM TO YOU ONLY IF YOU COMMUNICATIONS BETWEEN YOU
FIRST ACCEPT THE TERMS OF THIS AND IBM. THE TERMS OF PART 2
AGREEMENT. BY USING THE MAY REPLACE OR MODIFY THOSE
PROGRAM YOU AGREE TO THESE OF PART 1.
TERMS. IF YOU DO NOT AGREE TO Severity: 0 : Information
THE TERMS OF THIS AGREEMENT,
PROMPTLY RETURN THE UNUSED Explanation: This is part of the Early Release of
PROGRAM TO IBM. Programs License Agreement which must be accepted
before a Beta test period can be started. A Beta test
Severity: 0 : Information version allows a copy of WebSphere MQ to be used for
Explanation: This is part of the Early Release of a limited period only.
Programs License Agreement which must be accepted Response: None.
version allows a copy of WebSphere MQ to be used for
a limited period only. AMQ7174 1.License
Use of the Program
Response: None. IBM grants you a nonexclusive,
nontransferable license to use the
AMQ7172 The Program is owned by International Program.
Business Machines Corporation or one You may
of its subsidiaries (IBM) or an IBM 1) use the Program only for internal
supplier, and is copyrighted and evaluation or testing purposes and
licensed, not sold. 2) make and install a reasonable number
The term ″Program″ means the original of copies of the Program in support of
program and all whole or partial copies such use, unless IBM identifies a
of it. A Program consists of specific number of copies in the
machine-readable instructions, its documentation accompanying the
components, data, audio-visual content Program. The terms of this license apply
(such as images, text, recordings, or to each copy you make. You will
pictures), and related licensed materials. reproduce the copyright notice and any
other legends of ownership on each
Severity: 0 : Information copy, or partial copy, of the Program.
Explanation: This is part of the Early Release of Severity: 0 : Information
Programs License Agreement which must be accepted
before a Beta test period can be started. A Beta test Explanation: This is part of the Early Release of
version allows a copy of WebSphere MQ to be used for Programs License Agreement which must be accepted
a limited period only. before a Beta test period can be started. A Beta test
Response: None. a limited period only.
Response: None.
will destroy the Program and all copies
AMQ7175 THE PROGRAM MAY CONTAIN A
made of it within ten days of when this
DISABLING DEVICE THAT WILL
license ends.
PREVENT IT FROM BEING USED
UPON EXPIRATION OF THIS Severity: 0 : Information
LICENSE. YOU WILL NOT TAMPER
WITH THIS DISABLING DEVICE OR Explanation: This is part of the Early Release of
THE PROGRAM. YOU SHOULD TAKE Programs License Agreement which must be accepted
PRECAUTIONS TO AVOID ANY LOSS before a Beta test period can be started. A Beta test
OF DATA THAT MIGHT RESULT version allows a copy of WebSphere MQ to be used for
WHEN THE PROGRAM CAN NO a limited period only.
LONGER BE USED. Response: None.
You will
1) maintain a record of all copies of the
Program and AMQ7178 2.No Warranty
2) ensure that anyone who uses the SUBJECT TO ANY STATUTORY
Program does so only for your WARRANTIES WHICH CANNOT BE
authorized use and in compliance with EXCLUDED, IBM MAKES NO
the terms of this Agreement. WARRANTIES OR CONDITIONS
EITHER EXPRESS OR IMPLIED,
Severity: 0 : Information INCLUDING WITHOUT LIMITATION,
Explanation: This is part of the Early Release of THE WARRANTY OF
Programs License Agreement which must be accepted NON-INFRINGEMENT AND THE
before a Beta test period can be started. A Beta test IMPLIED WARRANTIES OF
version allows a copy of WebSphere MQ to be used for MERCHANTABILITY AND FITNESS
a limited period only. FOR A PARTICULAR PURPOSE,
REGARDING THE PROGRAM OR
Response: None. TECHNICAL SUPPORT, IF ANY.. IBM
MAKES NO WARRANTY
REGARDING THE CAPABILITY OF
AMQ7176 You may not
THE PROGRAM TO CORRECTLY
1) use, copy, modify, or distribute the
PROCESS, PROVIDE AND/OR
Program except as provided in this
RECEIVE DATE DATA WITHIN AND
Agreement;
BETWEEN THE 20TH AND 21ST
2) reverse assemble, reverse compile, or
CENTURIES.
otherwise translate the Program except
This exclusion also applies to any of
as specifically permitted by law without
IBM’s subcontractors, suppliers or
the possibility of contractual waiver; or
program developers (collectively called
3) sublicense, rent, or lease the Program.
″Suppliers″).
Severity: 0 : Information Manufacturers, suppliers, or publishers
of non-IBM Programs may provide their
Explanation: This is part of the Early Release of
own warranties.
before a Beta test period can be started. A Beta test Severity: 0 : Information
a limited period only.
Response: None. before a Beta test period can be started. A Beta test
AMQ7177 This license begins with your first use
of the Program and ends Response: None.
1) as of the duration or date specified in
the documentation accompanying the
AMQ7179 3.Limitation of Liability
Program,
NEITHER IBM NOR ITS SUPPLIERS
2) when the Program automatically
ARE LIABLE FOR ANY DIRECT OR
disables itself, or
INDIRECT DAMAGES, INCLUDING
3) when IBM makes the Program
WITHOUT LIMITATION, LOST
generally available. Unless IBM
PROFITS, LOST SAVINGS, OR ANY
specifies in the documentation
INCIDENTAL, SPECIAL, OR OTHER
accompanying the the Program that you
ECONOMIC CONSEQUENTIAL
may retain the Program (in which case,
DAMAGES, EVEN IF IBM IS
an additional charge may apply), you
INFORMED OF THEIR POSSIBILITY.

SOME JURISDICTIONS DO NOT or technical support, unless IBM
ALLOW THE EXCLUSION OR specifies otherwise.
LIMITATION OF INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO
THE ABOVE EXCLUSION OR Explanation: This is part of the Early Release of
LIMITATION MAY NOT APPLY TO Programs License Agreement which must be accepted
YOU. before a Beta test period can be started. A Beta test
4.Rights In Data version allows a copy of WebSphere MQ to be used for
You hereby assign to IBM all right, title, a limited period only.
and interest (including ownership of
copyright) in any data, suggestions, and Response: None.
written materials related to your use of
the Program you provide to IBM. If IBM AMQ7182 The laws of the country in which you
requires it, you will sign an appropriate acquire the Program govern this
document to assign such rights. Agreement, except
Severity: 0 : Information 1) in Australia, the laws of the State or
Territory in which the transaction is
Explanation: This is part of the Early Release of performed govern this Agreement;
Programs License Agreement which must be accepted 2) in Albania, Armenia, Belarus,
before a Beta test period can be started. A Beta test Bosnia/Herzegovina, Bulgaria, Croatia,
version allows a copy of WebSphere MQ to be used for Czech Republic, Georgia, Hungary,
a limited period only. Kazakhstan, Kirghizia, Former Yugoslav
Republic of Macedonia (FYROM),
Response: None.
Moldova, Poland, Romania, Russia,
Slovak Republic, Slovenia, Ukraine, and
AMQ7180 5.General Federal Republic of Yugoslavia, the laws
Nothing in this Agreement affects any of Austria govern this Agreement;
statutory rights of consumers that 3) in the United Kingdom, all disputes
cannot be waived or limited by contract. relating to this Agreement will be
IBM may terminate your license if you governed by English Law and will be
fail to comply with the terms of this submitted to the exclusive jurisdiction
Agreement. If IBM does so, you must of the English courts;
immediately destroy the Program and 4) in Canada, the laws of the Province
all copies you made of it. of Ontario govern this Agreement; and
You may not export the Program. 5) in the United States and Puerto Rico,
and People’s Republic of China, the
laws of the State of New York govern
Explanation: This is part of the Early Release of this Agreement.
version allows a copy of WebSphere MQ to be used for Explanation: This is part of the Early Release of
a limited period only. Programs License Agreement which must be accepted
Response: None.
AMQ7181 Neither you nor IBM will bring a legal
Response: None.
action under this Agreement more than
two years after the cause of action arose
unless otherwise provided by local law AMQ7183 Part 2 - Country-unique Terms
without the possibility of contractual AUSTRALIA: No Warranty (Section 2):
waiver or limitation. The following paragraph is added to
Neither you nor IBM is responsible for this Section: Although IBM specifies
failure to fulfill any obligations due to that there are no warranties, you may
causes beyond its control. have certain rights under the Trade
There is no additional charge for use of Practices Act 1974 or other legislation
the Program for the duration of this and are only limited to the extent
license. permitted by the applicable legislation.
Neither of us will charge the other for Limitation of Liability (Section 3): The
rights in data or any work performed as following paragraph is added to this
a result of this Agreement. Section: Where IBM is in breach of a
IBM does not provide program services condition or warranty implied by the
Trade Practices Act 1974, IBM’s liability Severity: 0 : Information
is limited to the repair or replacement of
the goods, or the supply of equivalent
goods. Where that condition or warranty
relates to right to sell, quiet possession
or clear title, or the goods are of a kind
ordinarily acquired for personal,
domestic or household use or Response: None.
consumption, then none of the
limitations in this paragraph apply.
AMQ7186 IRELAND: No Warranty (Section 2): The
Severity: 0 : Information following paragraph is added to this
Section: Except as expressly provided in
these terms and conditions, all statutory
conditions, including all warranties
implied, but without prejudice to the
generality of the foregoing, all
warranties implied by the Sale of Goods
Response: None. Act 1893 or the Sale of Goods and
Supply of Services Act 1980 are hereby
excluded.
AMQ7184 GERMANY: No Warranty (Section 2):
The following paragraphs are added to Severity: 0 : Information
this Section: The minimum warranty
period for Programs is six months. In
case a Program is delivered without
Specifications, IBM will only warrant
that the Program information correctly
describes the Program and that the
Program can be used according to the Response: None.
Program information. You have to check
the usability according to the Program
information within the ″money-back AMQ7187 ITALY: Limitation of Liability (Section
guaranty″ period. 3): This Section is replaced by the
Limitation of Liability (Section 3): The following: Unless otherwise provided
following paragraph is added to this by mandatory law, IBM is not liable for
Section: The limitations and exclusions any damages which might arise.
specified in the Agreement will not Severity: 0 : Information
apply to damages caused by IBM with
fraud or gross negligence, and for Explanation: This is part of the Early Release of
express warranty. Programs License Agreement which must be accepted
Severity: 0 : Information version allows a copy of WebSphere MQ to be used for
Explanation: This is part of the Early Release of a limited period only.
Programs License Agreement which must be accepted Response: None.
a limited period only. AMQ7188 JAPAN: Rights In Data (Section 4): The
following paragraph is added to this
Response: None. Section: You also agree to assign to IBM
the rights regarding derivative works, as
AMQ7185 INDIA: General (Section 5): The defined in Articles 27 and 28 of the
following replaces the fourth paragraph Japanese Copyright Law. You also agree
of this Section: If no suit or other legal not to exercise your moral rights.
action is brought, within two years after Severity: 0 : Information
the cause of action arose, in respect of
any claim that either party may have Explanation: This is part of the Early Release of
against the other, the rights of the Programs License Agreement which must be accepted
concerned party in respect of such claim before a Beta test period can be started. A Beta test
will be forfeited and the other party version allows a copy of WebSphere MQ to be used for
will stand released from its obligations a limited period only.
in respect of such claim.

Response: None.
AMQ7192 The Beta test period for this copy of
WebSphere MQ has already been
AMQ7189 NEW ZEALAND: No Warranty (Section started.
2): The following paragraph is added to
this Section: Although IBM specifies
that there are no warranties, you may Explanation: This copy of WebSphere MQ is licensed
have certain rights under the Consumer for a limited period only and the Beta test period has
Guarantees Act 1993 or other legislation been started previously.
which cannot be excluded or limited.
Response: None.
The Consumer Guarantees Act 1993 will
not apply in respect of any goods or
services which IBM provides, if you AMQ7193 Reply ’yes’ to accept the Agreement.
require the goods and services for the Reply ’no’ if you do not agree to the
purposes of a business as defined in terms of the Agreement. Reply ’no’ and
that Act. submit the command again, if you want
Limitation of Liability (Section 3): The to read the Agreement again.
following paragraph is added to this
Section: Where Programs are not Severity: 0 : Information
acquired for the purposes of a business Explanation: The IBM International License
as defined in the Consumer Guarantees Agreement for Early Release of Programs has been
Act 1993, the limitations in this Section displayed to the user and the user should now accept
are subject to the limitations in that Act. or reject the Agreement.
Severity: 0 : Information Response: Reply ’yes’ or ’no’ and press ’Enter’.
Programs License Agreement which must be accepted AMQ7194 Press Enter to continue
version allows a copy of WebSphere MQ to be used for Severity: 0 : Information
a limited period only. Explanation: Part of the IBM International License
Response: None. Agreement for Early Release of Programs has been
displayed to the user. The user should press the Enter
key to indicate that they are ready for the next part of
AMQ7190 UNITED KINGDOM: Limitation of the Agreement to be displayed.
Liability (Section 3): The following
paragraph is added to this Section at the Response: Press the Enter key when ready for the
end of the first paragraph: The next part of the Agreement to be displayed.
limitation of liability will not apply to
any breach of IBM’s obligations implied AMQ7195 The Beta test license is not valid for this
by Section 12 of the Sale of Goods Act copy of WebSphere MQ.
1979 or Section 2 of the Supply of
Goods and Services Act 1982. Severity: 20 : Error
Severity: 0 : Information Explanation: The license <insert_3> has been installed

but it is not a valid trial period license for this copy of
Explanation: This is part of the Early Release of WebSphere MQ.
Programs License Agreement (VZ125-5544-01 10/97
(MK002))which must be accepted before a Beta test Response: Check that the correct version of the file is
period can be started. A Beta test version allows a copy available.
of WebSphere MQ to be used for a limited period only.
Response: None. AMQ7196 By installing this product, you accept
the terms of the International Program
License Agreement and the License
AMQ7191 There are <insert_1> days left in the beta Information supplied with the product.
test period for this copy of WebSphere
MQ. Severity: 0 : Information
Severity: 0 : Information Response: None.

Response: None.

AMQ7197 A production or trial license could not AMQ7200 The purchased processor allowance is
be installed for this copy of WebSphere <insert_1>
MQ.
Explanation: The purchased processor allowance is
Explanation: This copy of WebSphere MQ is a beta currently set to <insert_1>
version and cannot be used with a production or trial
Response: Ensure sufficient license units have been
license.
purchased and, if necessary, use the MQ setmqcap
Response: Uninstall the beta version of WebSphere command to change the purchased processor allowance
MQ and install the production or trial version. for this installation. Refer to the Quick Beginnings book
for more information.
AMQ7198 Insufficient license units.
AMQ7200 (iSeries) The purchased processor
allowance is <insert_1>
Explanation: The purchased processor allowance
(<insert_1>) is less than the number of processors
(<insert_2>) in this machine. Explanation: The purchased processor allowance is
currently set to <insert_1>
purchased and use the MQ setmqcap command to set Response: Ensure sufficient license units have been
the purchased processor allowance for this installation. purchased and, if necessary, use the MQ
Refer to the Quick Beginnings book for more CHGMQMCAP command to change the purchased
information. processor allowance for this installation. Refer to the
Quick Beginnings book for more information.
AMQ7198 (iSeries) Insufficient license units.
AMQ7201 The number of processors in this
machine is <insert_1>
Explanation: The purchased processor allowance for
this installation is zero.
Explanation: The operating system reports that the
number of processors in this machine is <insert_1>
purchased and use the MQ CHGMQMCAP command
to set the purchased processor allowance for this Response: None.
installation. Refer to the Quick Beginnings book for
more information.
AMQ7202 The number of license units is sufficient
for all future possible upgrades to this
AMQ7199 The purchased processor allowance is machine.
set to <insert_1>.
Explanation: The purchased processor allowance for this installation has been set to -1, which allows any
this installation has been set to <insert_1> using the permitted processor configuration.
MQ setmqcap command.
Response: None.
Response: None.
AMQ7203 Purchased processor allowance not set
AMQ7199 (iSeries) The purchased processor (use setmqcap).
allowance is set to <insert_1>.
Explanation: The purchased processor allowance for this installation has not been set.
this installation has been set to <insert_1> using the
MQ CHGMQMCAP command.
purchased and use the MQ setmqcap command to set
Response: None. the purchased processor allowance for this installation.
Refer to the Quick Beginnings book for more
information.

AMQ7203 (iSeries) Purchased processor allowance AMQ7208 The queue manager failed to pass a PCF
not set (use CHGMQMCAP). message to another queue manager.
Explanation: The purchased processor allowance for Explanation: The queue manager attempted to put a
this installation has not been set. PCF message to <insert_3> to start the channel
<insert_4> to cluster queue manager <insert_5>. The put
failed with reason <insert_1>. When the queue manager
purchased and use the MQ CHGMQMCAP command
resolves a cluster queue to a remote cluster queue
to set the purchased processor allowance for this
manager, the message is put to the
installation. Refer to the Quick Beginnings book for
SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to
more information.
the remote cluster queue manager is not running, the
queue manager attempts to start the channel by
AMQ7204 Intel Hyper-Threading support enabled sending a PCF message to <insert_3>.
with Logical Processor Mask <insert_1>.
Response: Resolve the problem with <insert_3> and if
Severity: 0 : Information necessary start the channel manually.
Explanation: Install has detected Intel
Hyper=Threading support enabled for Logical AMQ7209 The queue manager attempted to open
Processors. The current Processor Mask is set to SYSTEM.CHANNEL.INITQ which
<insert_1>. failed with reason <insert_3>
Response: None. Severity: 10 : Warning
Explanation: When the queue manager resolves a
AMQ7205 System call SetProcessAffinityMask cluster queue to a remote cluster queue manager, the
failed for Logical Processor Mask message is put to the
<insert_1>. Process Affinity Mask is SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to
<insert_2>, process is continuing. the remote cluster queue manager is not running, the
queue manager attempts to start the channel by
Severity: 0 : Information sending a PCF message to the
Explanation: Microsoft Windows system call SYSTEM.CHANNEL.INITQ
SetProcessAffinityMask failed. If this problem persists Response: Resolve the problem with the
contact your IBM service representative. SYSTEM.CHANNEL.INITQ and if necessary start the
Response: None. channels manually.
AMQ7206 (Windows) Group name has been AMQ7210 The Cluster Workload exit module could
truncated. not be loaded.
Severity: 40 : Stop Error Severity: 10 : Warning
Explanation: WebSphere MQ only supports group Explanation: The Cluster Workload exit module
names up to 12 characters long. The operating system <insert_3> could not be loaded for reason <insert_4>.
is attempting to return a group longer than this. Response: Correct the problem with the Cluster
Response: Reduce the group name to 12 characters or Workload exit module <insert_3>
less.
AMQ7211 The Queue Manager is still waiting for
AMQ7207 (Windows) User ID longer than 12 a reply from the Cluster Workload Exit
characters. server process.
Severity: 40 : Stop Error Severity: 10 : Warning
Explanation: WebSphere MQ only supports user Explanation: The Queue Manager is configured to run
names up to 12 characters long. This operation is being the Cluster Workload Exit in SAFE mode. This means
attempted from a user name longer than this. that the Cluster Workload Exit is run by a server
process (amqzlw0). The Queue Manager has been
Response: Reduce the user name to 12 characters or waiting <insert_1> seconds for this server process to
less. reply to a request to run the Cluster Workload Exit. It
is possible that the exit is hung or is looping.
Response: End the Queue Manager, resolve the

problem with the Cluster Workload Exit and restart the
AMQ7217 The response set by the exit is not valid.
Queue Manager
AMQ7212 The address of the Cluster exit function Explanation: The API Exit <insert_3> module
could not be found. <insert_4> function <insert_5> returned a response code
<insert_1> that is not valid in the ExitResponse field of
the API Exit parameters (MQAXP).
Explanation: The address of the Cluster exit function
Response: Investigate why the API Exit <insert_3> set
<insert_4> could not be found in module <insert_3> for
a response code that is not valid.
reason <insert_1> <insert_5>.
Response: Correct the problem with the Cluster exit
AMQ7219 profile: <insert_3>
function <insert_4> in the module <insert_3>
AMQ7214 The module for API Exit <insert_3>
could not be loaded. AMQ7220 object type: <insert_3>
Severity: 40 : Stop Error Severity: 0 : Information
Explanation: The module <insert_4> for API Exit
<insert_3> could not be loaded for reason <insert_5>. AMQ7221 entity: <insert_3>
Response: Correct the problem with the API Exit Severity: 0 : Information
module <insert_3>.
AMQ7222 entity type: <insert_3>
AMQ7215 The API Exit <insert_3> function
<insert_4> could not be found in the
module <insert_5>.
AMQ7223 authority: <insert_3>
Explanation: The API Exit <insert_3> function
<insert_4> could not be found in the module <insert_5>.
The internal return code was <insert_1>. AMQ7224 profile: <insert_3>, object type:
<insert_4>
Response: Correct the problem with the API Exit
<insert_3>. Severity: 0 : Information
AMQ7215 (iSeries) Could not find a function in API AMQ7225 No matching authority records.
Exit <insert_3>.
Explanation: No authority records match the specified
Explanation: The API Exit <insert_3> function parameters.
<insert_4> could not be found in the module <insert_5>.
The internal return code was <insert_1>.
AMQ7226 The profile name is invalid.
<insert_3>. Severity: 20 : Error
Explanation: The profile name contains invalid
AMQ7216 An API Exit initialization function characters, contains an invalid wildcard specification,
returned an error. or is of invalid length.
Severity: 10 : Warning Response: Correct the profile name and submit it

again.
Explanation: The API Exit <insert_3> function
<insert_4> in the module <insert_5> returned
CompCode <insert_1> and ReasonCode <insert_2>. AMQ7227 WebSphere MQ encountered the
following network error: <insert_3>
<insert_3> Severity: 10 : Warning
Explanation: MQ failed to successfully complete a
network operation due to the specified error.

Response: Ensure that your network is functioning Response: None.
correctly.
AMQ7234 <insert_1> messages from queue
AMQ7228 (iSeries) Display MQ Authority Records <insert_4> loaded on queue manager
for <insert_3> <insert_3>.
Explanation: <insert_1> messages from queue
AMQ7229 <insert_1> log records accessed on queue <insert_4> have been loaded on queue manager
manager <insert_3> during the log <insert_3>.
replay phase.
Response: None.
Explanation: <insert_1> log records have been AMQ7235 (iSeries) Queue manager library <insert_3>
accessed so far on queue manager <insert_3> during already exists.
the log replay phase in order to bring the queue
manager back to a previously known state.
Explanation: The library <insert_3> already exists.
Response: None.
Response: Specify a library which does not already
exist.
AMQ7230 Log replay for queue manager <insert_3>
complete.
AMQ7236 WebSphere MQ queue manager
<insert_3> activated.
Explanation: The log replay phase of the queue
manager restart process has been completed for queue
manager <insert_3>. Explanation: WebSphere MQ queue manager
<insert_3> has been activated.
Response: None.
Response: None.
AMQ7231 <insert_1> log records accessed on queue
manager <insert_3> during the recovery AMQ7237 WebSphere MQ queue manager
phase. <insert_3> is not a backup queue
manager.
Explanation: <insert_1> log records have been
accessed so far on queue manager <insert_3> during Explanation: WebSphere MQ queue manager
the recovery phase of the transactions manager state. <insert_3> is not a backup queue manager and so
cannot be activated. A possible reason might be that the
Response: None.
queue manager is configured for circular logging.
Response: Re-try the command without the ’-a’
AMQ7232 Transaction manager state recovered for
option.
queue manager <insert_3>.
Explanation: The state of transactions at the time the <insert_3> replay completed.
queue manager ended has been recovered for queue
manager <insert_3>.
Explanation: WebSphere MQ queue manager
Response: None.
<insert_3> replay has completed.
Response: None.
AMQ7233 <insert_1> out of <insert_2> in-flight
transactions resolved for queue manager
<insert_3>. AMQ7249 WebSphere MQ queue manager
<insert_3> cannot be started for replay.
Explanation: <insert_1> transactions out of <insert_2>
in-flight at the time queue manager <insert_3> ended Explanation: WebSphere MQ queue manager
have been resolved. <insert_3> cannot be started for replay. A possible

reason might be that the queue manager is configured Response: Ensure that the dead-letter queue is
for circular logging. available and operational.
Response: Re-try the command without the ’-r’
option. AMQ7308 Trigger condition <insert_1> was not
satisfied.
AMQ7250 WebSphere MQ queue manager Severity: 0 : Information
<insert_3> has not been activated.
Explanation: At least one of the conditions required
Severity: 20 : Error for generating a trigger message was not satisfied, so a
trigger message was not generated. If you were
expecting a trigger message, consult the WebSphere
<insert_3> cannot be started because it has previously
MQ Application Programming Guide for a list of the
been started for replay but has not been activated.
conditions required. (Note that arranging for condition
Response: Activate the queue manager and try <insert_1> to be satisfied might not be sufficient
starting the queue manager again. because the conditions are checked in an arbitrary
order, and checking stops when the first unsatisfied
condition is discovered.)
AMQ7253 The command <insert_3> requires one of
the following arguments: <insert_4>. Response: If a trigger message is required, ensure that
all the conditions for generating one are satisfied.
Explanation: The command <insert_3> required at AMQ7310 Report message could not be put on a
least one of the following arguments, none of which reply-to queue.
you supplied: <insert_4>.
Response: Check the WebSphere MQ System
Administration documentation for details on the usage Explanation: The attempt to put a report message on
of the command, correct the command and then retry. queue <insert_4> on queue manager <insert_5> failed
with reason code <insert_1>. The message will be put
on the dead-letter queue.
AMQ7305 Trigger message could not be put on an
initiation queue. Response: Ensure that the reply-to queue is available
and operational.
Explanation: The attempt to put a trigger message on AMQ7315 Failed to put message to accounting
queue <insert_4> on queue manager <insert_5> failed queue. Reason(<insert_1>)
with reason code <insert_1>. The message will be put
on the dead-letter queue. Severity: 20 : Error
Response: Ensure that the initiation queue is Explanation: The attempt to put a messsage
available, and operational. containing accounting data to the queue <insert_3>
failed with reason code <insert_1>. The message data
has been discarded.
AMQ7306 The dead-letter queue must be a local This error message will be written only once for
queue. attempts to put a message to the queue as part of the
Severity: 10 : Warning same operation which fail for the same reason.
Explanation: An undelivered message has not been Response: Ensure that the queue <insert_3> is
put on the dead-letter queue <insert_4> on queue available and operational.
manager <insert_5>, because the queue is not a local
queue. The message will be discarded. AMQ7316 Failed to put message to statistics
Response: Inform your system administrator. queue. Reason(<insert_1>)
AMQ7307 A message could not be put on the Explanation: The attempt to put a messsage
dead-letter queue. containing statistics data to the queue <insert_3> failed
Severity: 10 : Warning with reason code <insert_1>. The message data has
been discarded.
Explanation: The attempt to put a message on the This error message will be written only once for
dead-letter queue <insert_4> on queue manager attempts to put a message to the queue as part of the
<insert_5> failed with reason code <insert_1>. The same operation which fail for the same reason.
message will be discarded.

Response: Ensure that the queue <insert_3> is
AMQ7459 (iSeries) WebSphere MQ journal receiver
available and operational.
<insert_3> is the oldest in the chain
AMQ7432 (iSeries) WebSphere MQ journal entry not
available for replay. Explanation: The oldest journal receiver in the
receiver chain is <insert_3> in library <insert_4>.
Response: None
Explanation: A journal replay operation was
attempted, but the operation required journal entries
from journal receivers that are not currently present on AMQ7460 (iSeries) WebSphere MQ startup journal
the system. information.
Response: Restore the required journal receivers from Severity: 0 : Information
backup. Then try the operation again.
Explanation: This message is issued periodically by
WebSphere MQ to help you identify which journal
AMQ7433 (iSeries) An Error occured while receivers can be removed from the system because they
performing a journal replay. are no longer required for startup recovery.
Severity: 40 : Stop Error Response: None
Explanation: WebSphere MQ encountered a problem
reading one or more journal entries while performing a AMQ7461 (iSeries) WebSphere MQ object re-created
journal replay operation. - reapply authorities.
Response: If you have previously created a journal Severity: 0 : Information
receiver for a queue manager or are performing a cold
Explanation: A previously damaged object has been
restart of a queue manager, delete the QMQMCHKPT
re-created, either automatically, or by explicit use of the
file from the queue manager subdirectory in
Recreate Object (RCRMQMOBJ) command. The
/QIBM/UserData/mqm/qmgrs/ and attempt to restart
authorities that applied to this object have not been
the queue manager. If the problem persists, use the
re-created.
standard facilities supplied with your system to record
the problem identifier, and to save the generated Response: Use the Grant Authority (GRTMQMAUT)
output files. Contact your IBM support center. Do not command, as appropriate, to re-create the required
discard these files until the problem has been resolved. authorities to this MQ object.
AMQ7434 (iSeries) The MQ commitment control exit AMQ7462 (iSeries) WebSphere MQ media recovery
program was called incorrectly. Code journal information.
<insert_1>.
Explanation: This message is issued periodically by
Explanation: The WebSphere MQ commitment control WebSphere MQ to help you identify which journal
exit program was called with incorrect parameters. receivers can be removed from the system because they
are no longer required for media recovery.
Response: If the program was called by OS/400 as
part of a commit or rollback, save the job log, and Response: None
contact your IBM support center.
AMQ7463 The log for queue manager <insert_3> is

AMQ7435 (iSeries) The MQ commitment control exit full.
program failed. Code <insert_1>.
Explanation: This message is issued when an attempt
Explanation: The WebSphere MQ commitment control to write a log record is rejected because the log is full.
exit program failed due to an unexpected error. The queue manager will attempt to resolve the
problem.
Response: Save the job log, and contact your IBM
support center. Response: This situation may be encountered during a
period of unusually high message traffic. However, if
you persistently fill the log, you may have to consider
enlarging the size of the log. You can either increase the
number of log files by changing the values in the
queue manager configuration file. You will then have to

stop and restart the queue manager. Alternatively, if
AMQ7468 The oldest log file required to perform
you need to make the log files themselves bigger, you
media recovery of queue manager
will have to delete and recreate the queue manager.
<insert_3> is <insert_4>.
AMQ7464 The log for queue manager <insert_3> is
no longer full. Explanation: The log file <insert_4> contains the
oldest log record required to recreate any of the objects
from their media images. Any log files prior to this will
Explanation: This message is issued when a log was not be accessed by media recovery operations.
previously full, but an attempt to write a log record has
Response: You can move log files older than
now been accepted. The log full situation has been
<insert_4> to an archive medium to release space in the
resolved.
log directory.
Response: None
AMQ7469 Transactions rolled back to release log
AMQ7465 The log for queue manager <insert_3> is space.
full.
Explanation: The log space for the queue manager is
Explanation: An attempt to resolve a log full situation becoming full. One or more long-running transactions
has failed. This is due to the presence of a long-running have been rolled back to release log space so that the
transaction. queue manager can continue to process requests.
Response: Try to ensure that the duration of your Response: Try to ensure that the duration of your
transactions is not excessive. Commit or roll back any transactions is not excessive. Consider increasing the
old transactions to release log space for further log size of the log to allow transactions to last longer
records. before the log starts to become full.
AMQ7466 There is a problem with the size of the AMQ7472 Object <insert_3>, type <insert_4>
logfile. damaged.
Explanation: The log for queue manager <insert_3> is Explanation: Object <insert_3>, type <insert_4> has
too small to support the current data rate. This message been marked as damaged. This indicates that the queue
is issued when the monitoring tasks maintaining the manager was either unable to access the object in the
log cannot keep up with the current rate of data being file system, or that some kind of inconsistency with the
written. data in the object was detected.
Response: The number of primary log files configured Response: If a damaged object is detected, the action
should be increased to prevent possible log full performed depends on whether the queue manager
situations. supports media recovery and when the damage was
detected. If the queue manager does not support media
recovery, you must delete the object as no recovery is
AMQ7467 The oldest log file required to start possible. If the queue manager does support media
queue manager <insert_3> is <insert_4>. recovery and the damage is detected during the
Severity: 0 : Information processing performed when the queue manager is
being started, the queue manager will automatically
Explanation: The log file <insert_4> contains the initiate media recovery of the object. If the queue
oldest log record required to restart the queue manager. manager supports media recovery and the damage is
Log records older than this may be required for media detected once the queue manager has started, it may be
recovery. recovered from a media image using the rcrmqmobj
Response: You can move log files older than command or it may be deleted.
<insert_4> to an archive medium to release space in the
log directory. If you move any of the log files required AMQ7472 (iSeries) Object <insert_3>, type <insert_4>
to recreate objects from their media images, you will damaged.
have to restore them to recreate the objects.
Explanation: Object <insert_3>, type <insert_4> has
been marked as damaged. This indicates that the queue
manager was either unable to access the object in the

file system, or that some kind of inconsistency with the
AMQ7601 (Windows) Duplicate XA resource
data in the object was detected.
manager <insert_5> not valid for
Response: If a damaged object is detected, the action attribute <insert_4> at <insert_3> in the
performed depends on whether the queue manager configuration data.
supports media recovery and when the damage was
detected. If the queue manager does not support media
recovery, you must delete the object as no recovery is Explanation: Key <insert_3> in the configuration data
possible. If the queue manager does support media contained a duplicate XA resource manager <insert_5>.
recovery and the damage is detected during the This is not valid for attribute <insert_4>. Each XA
processing performed when the queue manager is resource manager must be given a unique name.
being started, the queue manager will automatically
Response: Check the contents of the configuration
initiate media recovery of the object. If the queue
manager supports media recovery and the damage is
detected once the queue manager has started, it may be
recovered from a media image using the RCRMQMOBJ AMQ7602 (iSeries) The MQ commitment control exit
command or it may be deleted. program was called incorrectly.
AMQ7477 (iSeries) WebSphere MQ session no
longer active. Explanation: The WebSphere MQ commitment control
exit program was called with incorrect parameters.
Response: If the program was called by OS/400 as
Explanation: The commitment control exit program part of a commit or rollback, save the job log, and
was called during a commit or rollback operation. The contact your IBM support center.
queue manager was stopped while the program was
registered. This might have resulted in the rolling back
of some uncommitted message operations. AMQ7603 WebSphere MQ has been configured
with invalid resource manager
Response: Inform your system administrator that <insert_3>.
uncommitted message operations might have been
rolled back when the queue manager was stopped. Severity: 20 : Error
Explanation: The XA switch file <insert_4> for
AMQ7484 Failed to put message to logger event resource manager <insert_3> indicates that an attempt
queue. Reason(<insert_2>) has been made to configure another queue manager as
an external resource manager. This is not allowed so
Severity: 20 : Error the queue manager will terminate.
Explanation: The attempt to put a logger event Response: Remove the offending XAResourceManager
messsage to the queue <insert_3> failed with reason stanza from the qm.ini configuration file and restart the
code <insert_2>. The message data has been discarded. queue manager.
Response: Ensure that the queue <insert_3> is
available and operational. Current logger status AMQ7603 (Windows) WebSphere MQ has been
information can be displayed with the DISPLAY configured with resource manager
QMSTATUS runmqsc command. <insert_3> that is not valid.
AMQ7601 Duplicate XA resource manager is not
valid. Explanation: The XA switch file <insert_4> for
resource manager <insert_3> indicates that an attempt
Severity: 40 : Stop Error has been made to configure another queue manager as
an external resource manager. This is not allowed, so
the queue manager will terminate.
<insert_3> contained a duplicate XA resource manager
<insert_5>. This is not valid for attribute <insert_4>. Response: Remove the offending XAResourceManager
Each XA resource manager must be given a unique stanza from the configuration data and restart the
name. queue manager.
operation.

manager so that any change will be picked up.
AMQ7604 The XA resource manager <insert_3> was
Alternatively, the queue manager may be reaching a
not available when called for <insert_4>.
resource constraint with this resource manager. For
The queue manager is continuing
example, the resource manager may not be able to
without this resource manager.
accommodate all of the queue manager processes being
Severity: 10 : Warning connected at one time, you may need to alter one of its
tuning parameters.
Explanation: The XA resource manager <insert_3> has
indicated that it is not available, by returning
XAER_RMERR on an xa_open request or AMQ7605 The XA resource manager <insert_3> has
XAER_RMFAIL when called for something else. returned an unexpected return code
Normally this indicates that the resource manager has <insert_1>, when called for <insert_4>.
been shut down. In this case the resource manager
cannot participate in any new transactions. Any
in-flight transactions in which it was involved will be Explanation: WebSphere MQ received an unexpected
backed out, and any transactions in which it is in-doubt return code when calling XA resource manager
will only be resolved when contact with the resource <insert_3> at its <insert_4> entry point. This indicates
manager is re-established. A further message will be an internal error, either within MQ or the resource
issued when the queue manager has been able to do manager.
this. If the problem occurred on an xa_open request,
and the resource manager should be available, then Response: Try to determine the source of the error. A
there may be a configuration problem. trace of the failure could be used to look at the XA
flows between MQ and the resource manager. MQ has
Response: Try to establish the reason why the allocated an RMId of <insert_2> to this resource
resource manager is unavailable. It may be that an manager. This will be useful when isolating the flows
invalid XAOpenString has been defined for the associated with the resource manager concerned. If the
resource manager in the ’qm.ini’ configuration file. If error occurs on an xa_commit or xa_rollback request,
this is the case, stop and then restart the queue the queue manager will not attempt to redeliver the
manager so that any change will be picked up. commit or rollback instruction for this transaction, until
Alternatively, the queue manager may be reaching a after the queue manager has been restarted. The
resource constraint with this resource manager. For transaction indoubt is identified by the following XID
example, the resource manager may not be able to of X<insert_5>. If you think that the error lies within
accommodate all of the queue manager processes being the queue manager, contact your IBM support center.
connected at one time, you may need to alter one of its Do not discard any information describing the problem
tuning parameters. until after the problem has been resolved.
AMQ7604 (iSeries) The XA resource manager was AMQ7605 (iSeries) The XA resource manager has
not available when called. returned an unexpected return code.
Severity: 10 : Warning Severity: 20 : Error
Explanation: The XA resource manager <insert_3> has Explanation: WebSphere MQ received unexpected
indicated that it is not available, by returning return code <insert_1> when calling XA resource
XAER_RMERR on an xa_open request or manager <insert_3> at its <insert_4> entry point. This
XAER_RMFAIL when called for <insert_4>. The queue indicates an internal error, either within MQ or the
manager is continuing without this resource manager. resource manager.
Normally this indicates that the resource manager has
been shut down. In this case the resource manager Response: Try to determine the source of the error. A
cannot participate in any new transactions. Any trace of the failure could be used to look at the XA
in-flight transactions in which it was involved will be flows between MQ and the resource manager. MQ has
backed out, and any transactions in which it is in-doubt allocated an RMId of <insert_2> to this resource
will only be resolved when contact with the resource manager. This will be useful when isolating the flows
manager is re-established. A further message will be associated with the resource manager concerned. If the
issued when the queue manager has been able to do error occurs on an xa_commit or xa_rollback request,
this. If the problem occurred on an xa_open request, the queue manager will not attempt to redeliver the
and the resource manager should be available, then commit or rollback instruction for this transaction, until
there may be a configuration problem. after the queue manager has been restarted. The
transaction indoubt is identified by the following XID
Response: Try to establish the reason why the of X<insert_5>. If you think that the error lies within
resource manager is unavailable. It may be that an the queue manager, contact your IBM support center.
invalid XAOpenString has been defined for the Do not discard any information describing the problem
resource manager in the ’qm.ini’ configuration file. If until after the problem has been resolved.
this is the case, stop and then restart the queue

earlier AMQ7606 message reporting a mixed
AMQ7606 A transaction has been committed but
transaction outcome. It identifies one of the resource
one or more resource managers have
managers (<insert_4>) that failed to commit its updates.
backed out.
The transaction associated with this failure is identified
Severity: 20 : Error by the following XID of X<insert_3>.
Explanation: WebSphere MQ was processing the Response: Use the return code <insert_1> returned by
commit operation for a transaction involving external the resource manager to determine the effects of the
resource managers. One or more of these resource failure. The return code indicates that the resource
managers failed to obey the commit request and manager made a heuristic decision about the outcome
instead rolled back their updates. The outcome of the of the transaction which disagrees with the commit
transaction is now mixed and the resources owned by decision of the queue manager. In order to preserve
these resource managers may now be out of data integrity you will need to perform recovery steps
synchronization. MQ will issue further messages to local to this resource manager.
indicate which resource managers failed to commit
their updates.
AMQ7609 XA resource manager returned a
Response: The transaction with the mixed outcome is heuristic return code.
identified by the following XID of X<insert_3>. The
messages which identify the failing resource managers
will also contain this same XID. If the transaction has Explanation: This message is associated with an
completed it won’t be displayed by the dspmqtrn earlier AMQ7607 message reporting a mixed
command and all other transaction participants will transaction outcome. It identifies one of the resource
have committed their updates. If the transaction is managers (<insert_4>) that failed to rollback its
displayed by the dspmqtrn command then there are updates. The transaction associated with this failure is
some participants still in prepared state. In order to identified by the following XID of X<insert_3>.
preserve data integrity you will need to perform
recovery steps local to the failing resource managers. Response: Use the return code <insert_1> returned by
the resource manager to determine the effects of the
failure. The return code indicates that the resource
AMQ7607 A transaction has been rolled back but manager made a heuristic decision about the outcome
one or more resource managers have of the transaction which disagrees with the rollback
committed. decision of the queue manager. In order to preserve
data integrity you will need to perform recovery steps
local to this resource manager.
Explanation: WebSphere MQ was rolling back a
transaction involving external resource managers. One
AMQ7612 Switch call exception
or more of these resource managers failed to obey the
rollback request and instead committed their updates. Severity: 20 : Error
The outcome of the transaction is now mixed and the
resources owned by these resource managers may now Explanation: Exception number <insert_1> occurred
be out of synchronization. MQ will issue further when calling resource manager switch <insert_3>.
messages to indicate which resource managers failed to Response: Check the resource manager switch has not
roll back their updates. been corrupted.
Response: The transaction with the mixed outcome is
identified by the following XID of X<insert_3>. The AMQ7622 WebSphere MQ could not load the XA
messages which identify the failing resource managers switch load file for resource manager
will also contain this same XID. If the transaction has <insert_3>.
completed it won’t be displayed by the dspmqtrn
command and all other transaction participants will Severity: 20 : Error
have rolled back their updates. If the transaction is Explanation: An error has occurred loading XA switch
displayed by the dspmqtrn command then there are file <insert_4>. If the error occurred during startup then
some participants still in prepared state. In order to the queue manager will terminate. At all other times
preserve data integrity you will need to perform the queue manager will continue without this resource
recovery steps local to the failing resource managers. manager meaning that it will no longer be able to
participate in global transactions. The queue manager
AMQ7608 XA resource manager returned a will also retry the load of the switch file at regular
heuristic return code. intervals so that the resource manager will be able to
participate again should the load problem be resolved.
Response: Look for a previous message outlining the
Explanation: This message is associated with an reason for the load failure. Message AMQ6175 is issued

if the load failed because of a system error. If this is the logged as being involved in <insert_1> transactions that
case then follow the guidance given in message are still in-doubt. The queue manager cannot resolve
AMQ6175 to resolve the problem. In the absence of these transactions.
prior messages or FFST information related to this
Response: Check that the configuration data entry of
problem check that the name of the switch load file is
the queue manager concerned has not been altered by
correct and that it is present in a directory from which
mistake, resulting in an ’XAResourceManager’ stanza
it can be dynamically loaded by the queue manager.
being removed, or the ’Name’ of any the resource
The easiest method of doing this is to define the switch
managers being changed.
load file as a fully-qualified name. Note that if the
If the configuration data entry was changed by mistake,
queue manager is still running it will need to be
you need to reinstate resource manager <insert_3> in
restarted in order that any changes made to its
the configuration data before stopping, and then
configuration data can be picked up.
restarting the queue manager to access the change.
If you have intentionally removed a resource manager
AMQ7623 WebSphere MQ has not been from the configuration data, consider the integrity
configured with XA resource manager. implications of your action because the resource
manager concerned may be in an in-doubt state.
If you are sure that this is not the case, you can use the
Explanation: The queue manager has noticed that XA ’rsvmqtrn’ command to instruct the resource manager
resource manager <insert_3> was removed from the to inform the queue manager that it can forget about
qm.ini file of the queue manager. However, it was the transactions concerned.
logged as being involved in <insert_1> transactions that If using the ’rsvmqtrn’ command could result in an
are still in-doubt. The queue manager cannot resolve integrity problem, you should consider reinstating the
these transactions.The queue manager is continuing resource manager in the configuration data, so that the
without this resource manager. queue manager can contact the resource manager and
automatically resolve the transactions concerned next
Response: First check that the qm.ini configuration file time the queue manager is restarted.
of the queue manager concerned hasn’t been
mistakenly altered resulting in an
’XAResourceManager’ stanza being removed, or the AMQ7624 An exception occurred during an
’Name’ of any the resource managers being changed. If <insert_4> call to XA resource manager
the qm.ini file was changed by mistake then you will <insert_3>.
need to reinstate resource manager <insert_3> in the
qm.ini file before stopping and then restarting the
queue manager in order that the change will be picked Explanation: An exception has been detected during a
up. If you have intentionally removed a resource call to an XA resource manager. The queue manager
manager from the qm.ini file, consider the integrity will continue after assuming a return code of
implications of your action since the resource manager XAER_RMERR from the call.
concerned may be in an in-doubt state. If you are sure
Response: An FFST should have been produced
that is not the case then you can use the ’rsvmqtrn’
which documents the exception. Use this and any
command to deliver an outcome on behalf of the
further FFSTs to try and determine the reason for the
resource manager in order that the queue manager can
failure. A trace of the problem will be useful to identify
forget about the transactions concerned. If you cannot
the XA flows between the queue manager and the
be sure that such an action will not cause an integrity
resource manager concerned. MQ has allocated an
problem then you should consider re-instating the
RMId of <insert_1> to this resource manager. Use this
resource manager in the qm.ini file so that the queue
to isolate the flows concerned. First contact the supplier
manager can contact the resource manager and
of the resource manager for problem resolution. If
automatically resolve the transactions concerned next
however you think that the problem lies within the
time the queue manager is restarted.
queue manager then contact your IBM support center.
Do not discard any information describing the problem
AMQ7623 (Windows) WebSphere MQ has not been until after it has been resolved.
configured with XA resource manager
<insert_3> which may be involved in
AMQ7625 The XA resource manager <insert_3> has
in-doubt transactions. The queue
become available again.
manager is continuing without this
resource manager. Severity: 0 : Information
Severity: 10 : Warning Explanation: WebSphere MQ has managed to regain
contact with a resource manager that had become
Explanation: The queue manager has recognized that
unavailable. Any in-doubt transactions involving this
XA resource manager <insert_3> was removed from the
resource manager will be resolved. The resource
registry entry of the queue manager. However, it was

manager will now be able to participate in new
AMQ7704 DMPMQLOG command has used an
transactions.
invalid option <insert_3>.
Response: None.
Explanation: You started the DMPMQLOG command
AMQ7626 XA resource manager initialization
specifying an invalid option of <insert_3>.
failure. Refer to the error log for more
information. Response: Refer to the command syntax and then try
the command again.
Explanation: The queue manager has failed to
AMQ7705 Usage: dmpmqlog [-b | -s StartLSN | -n
initialize one or more of the XA resource managers
ExtentNumber] [-e EndLSN] [-f
defined in the qm.ini configuration file.
LogFilePath] [-m QMgrName]
Response: Correct the error and restart the queue
manager.
Response: None.
AMQ7626 (Windows) XA resource manager
initialization failure. Refer to the error AMQ7706 DMPMQLOG command has used an
log for more information. incorrect queue manager name
<insert_3> or path <insert_4>.
Explanation: The queue manager has failed to
initialize one or more of the XA resource managers Explanation: The DMPMQLOG command has used
defined in the configuration data. <insert_3> as the queue manager name and, if shown,
<insert_4> as the directory path for <insert_3>. Either
Response: Correct the error and restart the queue
<insert_3> and/or <insert_4> is incorrect; if <insert_4>
manager.
is not shown then it is <insert_3> which is incorrect.
Possible reasons for the error include:
AMQ7701 DMPMQLOG command is starting. that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ system
Severity: 0 : Information initialization (INI) file are incorrect;
Explanation: You have started the DMPMQLOG <insert_4> is not a correct path for <insert_3>.
command and it is processing your request. If you started the command specifying option -m
(queue manager name option) with a value then this
Response: None. value will have been used as the queue manager name,
otherwise the default queue manager name will have
AMQ7702 DMPMQLOG command has finished been used.
successfully. Response: Check that <insert_3> is an existing queue
Severity: 0 : Information manager name. Check your MQ system’s initialization
(INI) file to ensure that <insert_3> and its associated
Explanation: The DMPMQLOG command has entries are correct. If <insert_4> is shown, check that it
finished processing your request and no errors were is a correct MQ system directory path for <insert_3>.
detected.
Response: None. AMQ7706 (iSeries) DMPMQLOG command has used
an incorrect queue manager name or
AMQ7703 DMPMQLOG command has used path.
option <insert_3> with an invalid value Severity: 20 : Error
<insert_4>.
Explanation: The DMPMQLOG command has used
Severity: 20 : Error <insert_3> as the queue manager name and, if shown,
Explanation: You started the DMPMQLOG command <insert_4> as the directory path for <insert_3>. Either
specifying an invalid option value. The <insert_4> value <insert_3> and/or <insert_4> is incorrect; if <insert_4>
for option <insert_3> is either missing or of an incorrect is not shown then it is <insert_3> which is incorrect.
format. Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
Response: Refer to the command syntax, and then try the entries for <insert_3> in the MQ system
the command again. initialization (INI) file are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m

AMQ7708 DMPMQLOG command has used an
value will have been used as the queue manager name,
invalid default queue manager name.
otherwise the default queue manager name will have
been used. Severity: 20 : Error
Response: Check that <insert_3> is an existing queue Explanation: You started the DMPMQLOG command
manager name. Check your MQ system’s initialization without specifying option -m (queue manager name
(INI) file to ensure that <insert_3> and its associated option) and so your MQ default queue manager name
entries are correct. If <insert_4> is shown, check that it has been used. However, this default name either could
is a correct MQ system directory path for <insert_3>. not be found or is invalid.
Response: Check that the default queue manager
AMQ7706 (Windows) DMPMQLOG command has name exists and is valid, and then try the command
used an incorrect queue manager name again.
<insert_3> or path <insert_4>.
Severity: 20 : Error AMQ7709 DMPMQLOG command has used an
invalid combination of options.
Explanation: The DMPMQLOG command has used
<insert_3> as the queue manager name and, if shown, Severity: 20 : Error
<insert_4> as the directory path for <insert_3>. Either
Explanation: You started the DMPMQLOG command
<insert_3> and/or <insert_4> is incorrect; if <insert_4>
specifying an invalid combination of the options -b
is not shown then it is <insert_3> which is incorrect.
(base LSN option), -s (start LSN option) and -n (extent
Possible reasons for the error include:
number option). Only 1 or none of these options may
that <insert_3> is not an existing queue manager name;
be specified.
the entries for <insert_3> in the MQ configuration data
are incorrect; Response: Refer to the command syntax and then try
<insert_4> is not a correct path for <insert_3>. the command again.
If you started the command specifying option -m
value will have been used as the queue manager name, AMQ7710 DMPMQLOG command has used
otherwise the default queue manager name will have option -n which is invalid for circular
been used. logging.
Response: Check that <insert_3> is an existing queue Severity: 20 : Error

manager name. Check your MQ configuration data to Explanation: You started the DMPMQLOG command
ensure that <insert_3> and its associated entries are specifying option -n (extent number option) but this is
correct. If <insert_4> is shown, check that it is a correct not valid when your MQ log is defined as circular.
MQ system directory path for <insert_3>.
Response: Use a different option and then try the
command again.
AMQ7707 DMPMQLOG command has failed:
CompCode = 0x<insert_1>.
AMQ7711 DMPMQLOG command has used
Severity: 20 : Error option -m with a value that is too long.
Explanation: The DMPMQLOG command has Severity: 20 : Error
detected an error and the MQ recording routine has
been called. Possible reasons for this include a Explanation: You started the DMPMQLOG command
damaged log file, a problem during initialization for specifying option -m (queue manager name option)
the queue manager or an internal MQ failure. with a value that is more than <insert_1> characters.
Response: Check that the queue manager being used Response: Specify a shorter queue manager name and
by DMPMQLOG, as specified by you using the -m then try the command again.
command option or defaulted, exists and is not
currently running. If it does not exist, try the command AMQ7712 DMPMQLOG command has used
again specifying an existing queue manager. If it is option -f with a value which is too long.
running, stop the queue manager and then try the
command again. Otherwise, use the standard facilities Severity: 20 : Error
supplied with your system to record the problem Explanation: You started the DMPMQLOG command
identifier, and to save the generated output files. Do specifying option -f (log file path option) with a value
not discard these files until the problem has been which is more than <insert_1> characters.
resolved. Note the completion code (CompCode) and
then contact your IBM support center. Response: Specify a shorter log file path name and
then try the command again.

AMQ7713 DMPMQLOG command was unable to
allocate sufficient storage.
AMQ7718 DMPMQLOG command is using a
Explanation: The DMPMQLOG command has been default of <insert_3> for the queue
unable to allocate some storage. manager name.
Response: Free some storage and then try the Severity: 0 : Information
command again.
Explanation: You have started the DMPMQLOG
command without specifying option -m (queue
AMQ7714 DMPMQLOG command has reached the manager name option) and so a default value of
end of the log. <insert_3> is being used. This value is obtained from
your default queue manager name.
Response: None.
Explanation: The DMPMQLOG command has
processed any log data and has now reached the end of
the log. AMQ7718 (iSeries) DMPMQLOG command is using
a the default queue manager name.
Response: None.
AMQ7715 DMPMQLOG command cannot open Explanation: You have started the DMPMQLOG
file <insert_3>. command without specifying option -m (queue
manager name option) and so a default value of
<insert_3> is being used. This value is obtained from
Explanation: The DMPMQLOG command was unable your MQ default queue manager name.
to open file <insert_3> for reading.
Response: None.
Response: Check that the file exists, can be opened for
reading, and that you have authority to access it, and
AMQ7719 DMPMQLOG command is using a
default of <insert_3> for the starting
dump location.
AMQ7716 DMPMQLOG command has finished
unsuccessfully.
Explanation: You have started the DMPMQLOG
command without specifying option -b (base LSN
Explanation: The DMPMQLOG command has option), option -s (start LSN option) or option -n
finished with your request but an error has been (extent number option), and so a default value of
detected. The previous message issued by the <insert_3> is being used. This value is the Log
command can be used to identify the error. Sequence Number (LSN) of the first record in the active
part of the log, and will be used as the location from
Response: Refer to the previous message issued by which to start dumping.
the command.
Response: None.
AMQ7717 DMPMQLOG command has failed to
initialize: CompCode = 0x<insert_1>. AMQ7719 (iSeries) DMPMQLOG command is using
the default starting dump location.
Explanation: The DMPMQLOG command has failed
during its initialization and the MQ recording routine Explanation: You have started the DMPMQLOG
has been called. Possible reasons for this include that command without specifying option -b (base LSN
your queue manager is already running. The option), option -s (start LSN option) or option -n
completion code can be used to identify the error. (extent number option), and so a default value of
<insert_3> is being used. This value is the Log
Response: Check that the queue manager being used Sequence Number (LSN) of the first record in the active
by DMPMQLOG, as specified by you using the -m part of the log, and will be used as the location from
command option or defaulted, exists and is not which to start dumping.
currently running. If it is running, stop the queue
manager and then try the command again. Otherwise, Response: None.
use the standard facilities supplied with your system to
record the problem identifier, and to save the generated

AMQ7720 DMPMQLOG command is using extent AMQ7723 DMPMQLOG command cannot find the
<insert_1> but the current extent is requested Log Sequence Number (LSN).
<insert_2>.
Explanation: The DMPMQLOG command has been
Explanation: You have started the DMPMQLOG started with an LSN but it cannot be found in the log.
command specifying option -n (extent number option)
Response: Check for an existing LSN and then try the
with a value of <insert_1> but this value is greater than
command again.
<insert_2>, which represents the extent currently being
used.
AMQ7724 DMPMQLOG command cannot use the
Response: When using option -n, specify its value as
requested extent number.
being less than or equal to the extent number currently
being used. Severity: 20 : Error
AMQ7721 DMPMQLOG command has not found started with an extent number but it is beyond the end
any log records in extent number of the log.
<insert_1>.
Response: Check for an existing extent number and
Severity: 0 : Information then try the command again.
Explanation: During its normal processing, the
DMPMQLOG command did not find any log records in AMQ7725 DMPMQLOG command cannot find an
this extent. old Log Sequence Number (LSN).
Response: None. Severity: 20 : Error
AMQ7722 DMPMQLOG command cannot find the started specifying an LSN which is older than the log’s
object catalogue for queue manager base LSN. However, the specified LSN could not be
<insert_3>. found.
Severity: 20 : Error Response: Check for an existing LSN and then try the
command again.
Explanation: The DMPMQLOG command is using the
queue manager named <insert_3> but cannot find the
manager’s object catalogue file. This file should have AMQ7726 DMPMQLOG command has used
been created at the time the queue manager was option -s with an incorrect value for
created. circular logging.
Response: Refer to the ″System Management Guide″ Severity: 20 : Error
for a description of the location and name of the object
catalogue file. Check that the file exists and is available Explanation: You started the DMPMQLOG command
for use by this command. If it does not exist then you specifying option -s (start LSN option) with a value
will need to re-create the queue manager. which is less than the base LSN of a log which is
defined as circular. LSN values less than the base LSN
can only be specified when using a linear log.
AMQ7722 (iSeries) DMPMQLOG command cannot
find the object catalogue for the queue Response: When using option -s with a circular log,
manager. specify an option value which is equal or greater to the
log’s base LSN, and then try the command again.
Explanation: The DMPMQLOG command is using the AMQ7751 (iSeries) MIGRATEMQM program is
queue manager named <insert_3> but cannot find the starting.
manager’s object catalogue file. This file should have
been created at the time the queue manager was Severity: 0 : Information
created. Explanation: You have started the MIGRATEMQM
Response: Refer to the ″System Management Guide″ program.
for a description of the location and name of the object Response: None.
catalogue file. Check that the file exists and is available
for use by this command. If it does not exist then you
will need to re-create the queue manager.

AMQ7752 (iSeries) MIGRATEMQM has completed AMQ7757 (iSeries) Queue manager <insert_3>
successfully. already exists.
Severity: 0 : Information Severity: 20 : Error
Explanation: The MIGRATEMQM program has Explanation: The MIGRATEMQM program is unable
completed migration of your queue manager and no to create a queue manager with the same name as used
errors were detected. in the previous release because a queue manager of this
name has already been created.
Response: None.
Response: Delete the queue manager. Then restart the
MIGRATEMQM program.
AMQ7753 (iSeries) MIGRATEMQM has failed due
to errors.
AMQ7758 (iSeries) Queue manager starting.
Explanation: See the previously listed messages in the
job log. Correct the errors and then restart the Explanation: The queue manager ″<insert_3>″ is
MIGRATEMQM program. starting.
AMQ7754 (iSeries) MIGRATEMQM has detected an AMQ7759 (iSeries) Recreating WebSphere MQ

error and is unable to continue. objects.
Explanation: See the previously listed messages in this Explanation: WebSphere MQ objects are being
job log, or in associated job logs. Correct the errors and recreated from their media images contained in the log.
then restart the MIGRATEMQM program.
Response: None.
Response: None.
AMQ7760 (iSeries) Recreating WebSphere MQ
AMQ7755 (iSeries) Unable to locate a required channels.
journal receiver.
Explanation: WebSphere MQ channels are being
Explanation: The MIGRATEMQM program attempted recreated from the previous channel definition file.
to locate the journal receivers to use for migration, but
Response: None.
the operation required access to a journal or journal
receiver that is not currently present on the system.
AMQ7761 (iSeries) Unexpected return code from
Response: Restore the required journal or journal
command <insert_3>.
receiver from backup. Then restart the MIGRATEMQM
program. Severity: 20 : Error
Explanation: An unexpected return code, <insert_1>,
AMQ7756 (iSeries) Unable to locate a required was returned by command <insert_3>.
journal entry.
Response: See the previously listed messages in this
Severity: 20 : Error job log, or in associated job logs.
Explanation: The MIGRATEMQM program was
unable to retrieve a journal entry required for AMQ7762 (iSeries) Unexpected error from channel
migration. The operation may have failed because a migration.
required journal receiver is not currently present on the
system. Severity: 20 : Error
Response: Restore the required journal receiver from Explanation: The migration of channel definitions or
backup. Then restart the MIGRATEMQM program. channel synchronization data encountered an
unexpected error.
Response: See the previously listed messages in this
job log, or in associated job logs.

AMQ7770 Sent file <insert_3> AMQ7778 Syntax error. The correct syntax is:
Explanation: The file was successfully sent. Explanation: Invalid arguments supplied.
Response: None. Response: One or more options were incorrectly
specified when issuing the send or receive command.
Check the options used and reissue the command.
AMQ7771 Received file.
AMQ7779 Cannot connect to default queue
Explanation: The file was successfully received. manager.
Response: None. Severity: 40 : Stop Error
Explanation: Queue manager not available.
AMQ7772 Complete file list
Response: Check that the queue manager exists and
Severity: 40 : Stop Error that the listener is running.
Explanation: Displays a list of complete files.
Response: None. <insert_3>
AMQ7773 Incomplete file list
Explanation: Queue manager not available.
Response: Check that the queue manager exists and
Explanation: Displays a list of incomplete files. that the listener is running.
Response: None.
AMQ7781 Application memory unavailable.
AMQ7774 Other message list Severity: 40 : Stop Error
Severity: 40 : Stop Error Explanation: There is insufficient memory to perform
Explanation: Displays a list of other messages. the requested action.
Response: None. Response:

1) Check the message size is not excessive
2) Close other applications and try the command again
AMQ7775 Nothing to list.
Severity: 40 : Stop Error AMQ7783 Queue name required.
Explanation: Nothing to list. Severity: 40 : Stop Error
Response: None. Explanation: A queue name was not specified when
issuing a send or receive command.
AMQ7776 Deleted. Response: Reissue the command with the
Severity: 40 : Stop Error QueueName option.
Explanation: File deleted.

AMQ7784 Cannot open queue <insert_3>
Response: None.
AMQ7777 Nothing to delete. Explanation: Cannot open queue <insert_3>
Severity: 40 : Stop Error Response: Check that the queue exists.
Explanation: Nothing to delete.

AMQ7785 Cannot open file <insert_3>
Response: None.
Explanation: Cannot open file <insert_3>
Response: Check that the file exists, that it is in the

correct location and has the appropriate file
AMQ7791 Cannot write to file.
permissions.
AMQ7786 Cannot put to queue <insert_3> Explanation: The get or extract request has failed.
Severity: 40 : Stop Error Response:
1) Check that the file is not write-protected. In
Explanation: Cannot put to queue <insert_3>
Windows Explorer, right-click the file name and select
Response: Properties. Check the user has sufficient authority to
1) Check the Queue Manager has sufficient log space write to the destination file system.
for sending large messages 2) Check the destination file system exists
2) Check the queue does not have put inhibited 3) Check the destination file system is not full
3) Check the queue is not full
4) Check the message size of the queue is greater than
AMQ7792 CorrelId is invalid.
the message size
5) Check the user has sufficient authority to put Severity: 40 : Stop Error
messages on the queue
Explanation: CorrelId is invalid.
Response:
AMQ7787 No file name specified.
1) Check that a valid correlation ID has been specified
Severity: 40 : Stop Error when receiving a file with the -c option.
2) It must be 48 characters in length.
Explanation: No file name specified.
3) Use the -v option of the receive command to display
Response: A file name was not specified when issuing the correlation ID.
a send command. Reissue the command with the
FileName option.
AMQ7793 MsgId is invalid.
AMQ7788 Message length is too small to send
data. Explanation: MsgId is invalid.
Severity: 40 : Stop Error Response:
1) Check that a valid message ID has been specified
Explanation: Message length is too small to send data.
when receiving an ’other’ message with the -u option.
Response: Increase the message size and resend with 2) It must be 48 characters in length.
a send command, using the -l MessageSize option to
specify a larger message size.
AMQ7794 No messages to receive.
AMQ7789 Sending file has changed.
Explanation: There are no FTA files on the specified
queue.
Explanation: The file being sent has been changed
Response: Check with the sender that the file was
before the complete file has been sent.
actually sent.
Response: Check the file for integrity and reissue the
send command.
AMQ7795 Cannot delete the file because it’s not
unique.
AMQ7790 Cannot get from queue <insert_3>
Explanation: Cannot delete the file because it’s not
Explanation: The list, get, delete or extract request has unique.
failed.
Response: None.
Response:
1) Check the queue does have get inhibited
AMQ7796 Cannot replace an existing file.
2) Check the user has sufficient WMQ authority to get
messages from the queue Severity: 40 : Stop Error
Explanation: Cannot replace an existing file.
Response: Reissue the command with the -y option.

AMQ7797 Unable to load the WebSphere MQ AMQ7805 MsgId <insert_3>
library.
Explanation: None.
Explanation: Unable to load the WebSphere MQ
Response: None.
library.
Response: None.
AMQ7806 Could not start WebSphere MQ web
administration server: <insert_1>.
AMQ7798 Unable to locate <insert_3>.
Explanation: An unsuccessful attempt was made to
Explanation: This application requires <insert_3>. start the web administration server on port <insert_1>.
Response: Check that <insert_3> is available and Response: Check the product is installed correctly; the
installed correctly. required registry keys and values are correct and the
web server port is not already in use. If the problem
persists contact your service representative.
AMQ7799 Unable to start <insert_3>.
AMQ7807 WebSphere MQ web administration
Explanation: This application cannot start <insert_3>. server running.
Response: Check that <insert_3> is available and Severity: 0 : Information
installed correctly.
Explanation: WebSphere MQ web administration
server running. Listening on port <insert_4>, root
AMQ7800 CorrelId <insert_3> directory is <insert_5>.
Severity: 0 : Information Response: No action is required.
Explanation: None.
AMQ7808 Internal run-time error in WebSphere
Response: None. MQ web administration: <insert_4>.
AMQ7801 Dir <insert_3>
Explanation: WebSphere MQ web administration had
Severity: 0 : Information the following internal run-time error: <insert_4>.
Explanation: None. Response: Check that: the product is installed
Response: None. correctly and that the required registry keys and values
are correct. If the problem persists contact your service
representative.
AMQ7802 UserData <insert_3>
Severity: 0 : Information AMQ7809 WebSphere MQ Publish/Subscribe web
Explanation: None. administration user limit reached.

Explanation: The maximum number of concurrent
AMQ7803 FileName <insert_3> web administration users has been reached (<insert_4>).
Severity: 0 : Information Response: Use the ’Web Administration Server’

properties page in the Microsoft Management Console
Explanation: None. to increase the value of the web administration
Response: None. ’MaxClients’ parameter.
AMQ7804 Length <insert_3> AMQ7810 (Windows) Failed to create class, reason

code: <insert_1>.
Explanation: None.
Explanation: While trying to create class <insert_3> on
Response: None. <insert_4> error code <insert_1> was encountered. The

associated error message generated by the operating attempts have failed. There will be no more attempts to
system is: <insert_5> recover this service.
Response: Check the system documentation to Response: Use WebSphere MQ Explorer to investigate
determine the course of action required to rectify the why the service failed and could not be restarted.
problem.
AMQ7885 (Windows) Unable to delete queue
AMQ7880 (Windows) Error code <insert_1> starting manager <insert_4>, error <insert_1>.
<insert_4>/<insert_3> WebSphere MQ
service.
Explanation: An attempt to delete queue manager
<insert_4> failed. WebSphere MQ returned error code
Explanation: The service was unable to start <insert_1>: <insert_5>
<insert_4>/<insert_3>. The error message reported was
Response: Ensure that the queue manager name has
as follows: <insert_5>
been specified correctly, and try again.
Response: Use WebSphere MQ Explorer to investigate
why the service could not begin. If recovery for this
AMQ7886 (Windows) Unable to create queue
service is active, MQ will attempt to recover.
manager <insert_4>.
AMQ7881 (Windows) Unable to stop
<insert_4>/<insert_3> WebSphere MQ Explanation: Queue manager <insert_4> could not be
service, return code <insert_1>. created. WebSphere MQ returned error <insert_1>:
<insert_5>
Response: Check the error and application event logs
Explanation: The WebSphere MQ service was unable
to investigate the reason for the the returned error and
to stop <insert_4>/<insert_3>. The error message
suggested responses to take to rectify the fault. If the
reported was as follows: <insert_5>
problem cannot be resolved then use the standard
Response: Use WebSphere MQ Explorer to investigate facilities supplied with your system to record the
why the service could not be stopped. problem identifier and save the generated output files,
and then contact your IBM support center. Do not
AMQ7882 (Windows) Attempting to recover
<insert_4>/<insert_3> WebSphere MQ
service. AMQ7890 (Windows) Unable to open mapped file
containing WebSphere MQ performance
data.
Explanation: The WebSphere MQ service has detected
that <insert_4>/<insert_3> has failed, and is attempting
to restart it. Explanation: The WebSphere MQ extensible counter
dll was unable to open a mapped file used to collect
Response: No Action Required.
queue performance data. Your system may be running
short on virtual memory.
AMQ7883 (Windows) <insert_4>/<insert_3>
Response: No action required. Performance statistics
WebSphere MQ service started from
for MQ queues will not be displayed.
recovery.
AMQ7891 (Windows) Unable to create a mutex to
Explanation: The WebSphere MQ service has access WebSphere MQ performance
successfully recovered <insert_4>/<insert_3>. data.
Response: No Action Required. Severity: 20 : Error

Explanation: The WebSphere MQ extensible counter
AMQ7884 (Windows) Unable to recover dll was unable to create a mutex required to
<insert_4>/<insert_3> WebSphere MQ synchronise collection of queue performance data
service.
Severity: 10 : Warning for MQ queues will not be displayed.
Explanation: The WebSphere MQ service has
attempted to recover <insert_4>/<insert_3>, but all

AMQ7892 (Windows) Unable to map to shared AMQ7901 The data-conversion exit <insert_3> has
memory file containing WebSphere MQ not loaded.
performance data.
Explanation: The data-conversion exit program,
Explanation: The WebSphere MQ extensible counter <insert_3>, failed to load. The internal function gave
dll was unable to map the shared memory file required exception <insert_4>.
for collection of queue performance data.
Response: No action required. Performance statistics your system to record the problem identifier, and to
for MQ queues will not be displayed. save the generated output files. Contact your IBM
AMQ7893 (Windows) Unable to open ″Performance″
key for WebSphere MQ services. Status
code: <insert_1>. AMQ7903 The data-conversion exit <insert_3>
cannot be found.
dll was unable to obtain performance counter values Explanation: Message data conversion has been
from the ″Performance″ key for WebSphere MQ requested for a WebSphere MQ message with a
services. Status code is the return value from the user-defined format, but the necessary data-conversion
Windows registry call RegOpenKeyEx. exit program, <insert_3>, cannot be found. The internal
function gave exception <insert_4>.
for MQ queues will not be displayed. Response: Check that the necessary data-conversion
exit <insert_3> exists.
AMQ7894 (Windows) Unable to read the
″Performance\First Counter″ value for AMQ7904 The data-conversion exit <insert_3>
WebSphere MQ services. Status code: cannot be found, or loaded.
<insert_1>.
Explanation: Message data conversion was requested
Explanation: The WebSphere MQ extensible counter for a WebSphere MQ message with a user-defined
dll was unable to obtain performance counter values format, but the necessary data conversion exit program,
from the ″Performance\First Counter″ key for <insert_3>, was not found, or loaded. The <insert_4>
WebSphere MQ services. Status code is the return value function call gave a return code of <insert_1>.
from the Windows registry call RegOpenKeyEx.
Response: Check that the necessary data conversion
Response: No action required. Performance statistics exit routine exists in one of the standard directories for
for MQ queues will not be displayed. dynamically loaded modules. If necessary, inspect the
generated output to examine the message descriptor
(MQMD structure) of the MQ message for the
AMQ7895 (Windows) Unable to read the
conversion which was requested. This may help you to
″Performance\First Help″ value for
determine where the message originated.
WebSphere MQ services. Status code:
<insert_1>.
AMQ7905 Unexpected exception <insert_4> in
data-conversion exit.
dll was unable to obtain performance counter values
from the ″Performance\First Help″ key for WebSphere Explanation: The data-conversion exit program,
MQ services. Status code is the return value from the <insert_3>, ended with an unexpected exception
Windows registry call RegOpenKeyEx. <insert_4>. The message has not been converted.
Response: No action required. Performance statistics Response: Use the standard facilities supplied with
for MQ queues will not be displayed. your system to record the problem identifier, and to

AMQ7907 Unexpected exception in data-conversion AMQ7913 (Windows) The WebSphere MQ Active
exit. Directory container could not be created.
Severity: 30 : Severe error Severity: 20 : Error
Explanation: The data-conversion exit routine, Explanation: WebSphere MQ has failed to create an
<insert_3>, ended with an unexpected exception. The IBM-MQClientConnections container as a child of your
message has not been converted. domain’s system container in the Active Directory.
Response: Correct the error in the data-conversion exit Response: Ensure that you have permission to create
routine. sub-containers of the system container, and modify the
otherWellKnownObjects property of the system
container.
AMQ7908 (Windows) Display active directory CRL
server details.
AMQ7914 (Windows) Migration of the client
connection table for Queue Manager
Explanation: Display active directory CRL server <insert_3> failed with reason code
details. <insert_1><insert_4>.
Explanation: The client connection table for this
AMQ7909 (Windows) There are no active directory Queue Manager could not be migrated at this time.
CRL server details to display.
Response: Ensure that the client connection table
Severity: 0 : Information exists and is not corrupted, and that you have
authority to create new objects in the Active Directory
Explanation: No active directory CRL server on your domain.
definitions could be found.
Response: None. AMQ7915 (Windows) Created service connection
point for connection <insert_3>.
AMQ7910 (Windows) Usage: setmqscp [-m Severity: 0 : Information
QmgrName | * ] [-a] [-d] [-r]
Explanation: The service connection point was
Severity: 0 : Information successfully created for this client connection.
Response: None.
AMQ7911 (Windows) The default Active Directory
could not be located on your domain.
AMQ7916 (Windows) The Active Directory channel
Severity: 20 : Error definition table could not be opened.
Explanation: No domain controllers with Active Severity: 20 : Error
Directories could be found on the domain that your
computer is a member of. Explanation: The IBM-MQClientConnections Active
Directory container could not be located in the Global
Response: Active Directory support for MQ client Catalog.
connections cannot be used without a default Active
Directory available on your domain. Response: Ensure that setmqscp has been used to
create the container object and that you have
permission to read the container and its child objects.
AMQ7912 (Windows) The Active Directory support
library failed to initialize.
AMQ7917 (Windows) Display active directory
Severity: 20 : Error channel details.
Explanation: WebSphere MQ support libraries for Severity: 0 : Information
Active Directory client connections could not be
initialized. Explanation: Display active directory channel details.
Response: Check that the Active Directory client Response: None.
pre-requisite software has been installed on your
machine before attempting to use this feature.

AMQ7918 (Windows) The WebSphere MQ Active AMQ7923 A message had an unrecognized integer
Directory container could not be encoding - <insert_1>.
deleted.
Explanation: Message data conversion cannot convert
Explanation: There was a problem when attempting to a message because the integer encoding value of the
delete the MQ Active Directory container. The container message, <insert_1>, was not recognized.
must be empty before it can be deleted from the
directory.
Response: None. save the generated output files. Do not discard these
files until the problem has been resolved. Use the file
containing the Message Descriptor of the message to
AMQ7919 (Windows) There are no active directory
determine the source of the message and to see how
client channel details to display.
data that is not valid became included in the message.
Explanation: No active directory client channel AMQ7924 Bad length in the PCF header (length =
definitions could be found. <insert_1>).
Response: None. Severity: 30 : Severe error
AMQ7920 (Windows) Usage: setmqcrl [-m a message in Programmable Command Format (PCF)
QmgrName] [-a] [-d] [-r] because the PCF header structure contains an incorrect
length field. Either the message has been truncated, or
Severity: 0 : Information it contains data that is not valid.
AMQ7921 An incorrect eye-catcher field in an your system to record the problem identifier, and to
MQDXP structure has been detected. save the generated output files. Do not discard these
Severity: 30 : Severe error files until the problem has been resolved. Use the file
Explanation: The MQDXP structure passed to the determine the source of the message and to see how
Internal Formats Conversion routine contains an data that is not valid became included in the message.
incorrect eye-catcher field.
Response: Use the standard facilities supplied with AMQ7925 Message version <insert_1> is not
your system to record the problem identifier, and to supported.
support center. Do not discard these files until the Severity: 30 : Severe error
problem has been resolved. Explanation: Message data conversion cannot convert
a message because the Version field of the message
AMQ7922 A PCF message is incomplete. contains an incorrect value.
Severity: 30 : Severe error Response: Use the standard facilities supplied with
Explanation: Message data conversion cannot convert save the generated output files. Do not discard these
a message in Programmable Command Format (PCF) files until the problem has been resolved. Use the file
because the message is only <insert_1> bytes long and containing the Message Descriptor of the message to
does not contain a PCF header. The message has either determine the source of the message and to see how
been truncated, or it contains data that is not valid. data that is not valid became included in the message.
your system to record the problem identifier, and to AMQ7926 A PCF message has an incorrect
save the generated output files. Do not discard these parameter count value <insert_1>.
containing the Message Descriptor of the message to Severity: 30 : Severe error
determine the source of the message and to see how Explanation: Message data conversion cannot convert
data that is not valid became included in the message. a message in Programmable Command Format (PCF)
because the parameter count field of the PCF header is
incorrect.

AMQ7930 Bad CCSID in PCF structure number
save the generated output files. Do not discard these
<insert_1> (CCSID = <insert_2>).
Explanation: A Programmable Command Format
(PCF) structure passed to the Internal Formats
Converter contains an incorrect CCSID.
AMQ7927 Bad type in PCF structure number
<insert_1> (type = <insert_2>).
Severity: 30 : Severe error save the generated output files. Do not discard these
Converter contained an incorrect type field.
AMQ7931 Bad length in PCF structure number
<insert_1> (length = <insert_2>).
a message in Programmable Command Format (PCF)
because one of the structures of the message contains
AMQ7928 Bad length in PCF structure number an incorrect length field.
<insert_1> (length = <insert_2>).
Severity: 30 : Severe error your system to record the problem identifier, and to
Converter contained an incorrect length field.
Response: Use the standard facilities supplied with data that is not valid became included in the message.
AMQ7932 Bad count in PCF structure number
<insert_1> (count = <insert_2>).
determine the source of the message and to see how Severity: 30 : Severe error
AMQ7929 A PCF structure is incomplete. because a StringList structure of the message contains
an incorrect count field.
because structure number <insert_1>, of Type value
<insert_2>, within the message is incomplete. The
containing the Message Descriptor, the headers of the
message has either been truncated, or it contains data
message, and the incorrect structure to determine the
that is not valid.
source of the message, and to see how data that is not
Response: Use the standard facilities supplied with valid became included in the message.
AMQ7933 Bad string length in PCF structure.
because structure number <insert_1> of the message
contains an incorrect string length value <insert_2>.

AMQ7937 Structure length <insert_1> in
MQFMT_IMS_VAR_STRING format
message is not valid.
message, and the incorrect structure to determine the Severity: 30 : Severe error
source of the message and to see how data that is not
Explanation: This error is detected when attempting
valid became included in the message.
data conversion. The valid range for the length is 4
(with no string data) to 32767. The message is returned
AMQ7934 Wrong combination of unconverted with a reason code of
MQCCSI_DEFAULT with MQRC_CONVERTED_STRING_TOO_BIG.
MQCCSI_EMBEDDED or
Response: Check the content of the message before
MQEPH_CCSID_EMBEDDED.
data conversion and correct the message format. When
Severity: 30 : Severe error converting data using two or more bytes per character,
remember that the number of bytes in each character
Explanation: Message data conversion could not
can change during data conversion. This causes the
convert a message in Programmable Command Format
message lengths to change.
(PCF) because structure <insert_1> of the message
contained a CodedCharSetId field of
MQCCSI_DEFAULT while the message itself had a AMQ7943 Usage: crtmqcvx SourceFile TargetFile
CodedCharSetId of MQCCSI_EMBEDDED, or the Flags
field of the MQEPH structure containing the PCF
specified flag MQEPH_CCSID_EMBEDDED. These are Explanation: None.
incorrect combinations.
Response: None.
save the generated output files. Do not discard these AMQ7953 One structure has been parsed.
files until the problem has been resolved. Use the file Severity: 0 : Information
message and the incorrect structure to determine the Explanation: The crtmqcvx command has parsed one
source of the message and to see how data that is not structure.
valid became included in the message. Response: None.
AMQ7935 Bad CCSID in message header (CCSID AMQ7954 <insert_1> structures have been parsed.
= <insert_1>).
Explanation: The crtmqcvx command has parsed
Explanation: Message data conversion could not <insert_1> structures.
convert a message because the Message Descriptor of
the message contained an incorrect CodedCharSetId Response: None.
field.
Response: Use the standard facilities supplied with AMQ7955 Unexpected field: <insert_1>.
your system to record the problem identifier, and to Severity: 0 : Information
files until the problem has been resolved. Use the file Explanation: The field within the structure is of a type
containing the Message Descriptor of the message to that is not recognized.
Response: Correct the field and retry the command.
AMQ7956 Bad array dimension.

AMQ7936 The file <insert_3> already exists.
Explanation: An array field of the structure has an
Explanation: The output file already exists, but
incorrect dimension value.
REPLACE has not been specified.
Response: Correct the field and retry the command.
Response: Specify REPLACE to over-write the existing
file, or select a different output file name.

AMQ7957 Warning at line <insert_1>. AMQ7962 No input file specified.
Severity: 20 : Error Severity: 30 : Severe error
Explanation: The structure contains another field after Explanation: This command requires that an input file
a variable length field. A variable length field must be is specified.
the last field of the structure.
Response: Specify the name of the input file and retry
Response: Correct the structure and retry the the command.
command.
AMQ7963 No output file specified.
AMQ7958 Error at line <insert_1> in field
<insert_3>.
Explanation: This command requires that an output
file name is specified.
Explanation: Field name <insert_3> is a field of type
Response: Specify the name of the output file and
’float’. Fields of type float are not supported by this
retry the command.
command.
Response: Either correct the structure to eliminate
AMQ7964 Unexpected option <insert_3>.
fields of type float, or write your own routine to
support conversion of these fields. Severity: 30 : Severe error
Explanation: The option specified is not valid for this
AMQ7959 Error at line <insert_1> in field command.
<insert_3>.
Response: Retry the command with a valid option.
Explanation: Field name <insert_3> is a field of type AMQ7965 Incorrect number of arguments.
’double’. Fields of type double are not supported by
this command. Severity: 30 : Severe error
Response: Either correct the structure to eliminate Explanation: The command was passed an incorrect
fields of type double, or write your own routine to number of arguments.
support conversion of these fields. Response: Retry the command, passing it the correct
number of arguments.
AMQ7960 Error at line <insert_1> in field
<insert_3>. AMQ7968 Cannot open file <insert_3>.
Explanation: Field name <insert_3> is a ’pointer’ field. Explanation: You cannot open the file <insert_3>.
Fields of type pointer are not supported by this
command. Response: Check that you have the correct
authorization to the file and retry the command.
Response: Either correct the structure to eliminate
fields of type pointer, or write your own routine to
support conversion of these fields. AMQ7969 Syntax error.
AMQ7961 Error at line <insert_1> in field Explanation: This line of the input file contains a
<insert_3>. language syntax error.
Severity: 30 : Severe error Response: Correct the syntax error and retry the
Explanation: Field name <insert_3> is a ’bit’ field. Bit command.
fields are not supported by this command.
Response: Either correct the structure to eliminate bit AMQ7970 Syntax error on line <insert_1>.
fields, or write your own routine to support conversion Severity: 30 : Severe error
of these fields.
Explanation: This message identifies where, in the
input file, a previously reported error was detected.
Response: Correct the error and retry the command.

AMQ7A01 (iSeries) Convert MQ Data Type AMQ7A11 (iSeries) Change MQ Service
AMQ7A02 (iSeries) Display MQ Version AMQ7A12 (iSeries) Copy MQ Service
AMQ7A03 (iSeries) Create MQ Listener AMQ7A13 (iSeries) Service name
AMQ7A04 (iSeries) Listener name AMQ7A14 (iSeries) Start program
AMQ7A05 (iSeries) Listener control AMQ7A15 (iSeries) Start program arguments
AMQ7A06 (iSeries) Listener backlog AMQ7A16 (iSeries) End program
AMQ7A07 (iSeries) Change MQ Listener AMQ7A17 (iSeries) End program arguments
AMQ7A08 (iSeries) Copy MQ Listener AMQ7A18 (iSeries) Standard output
AMQ7A09 (iSeries) From Listener AMQ7A19 (iSeries) Standard error
AMQ7A0A (iSeries) To Listener AMQ7A1A (iSeries) Service type
AMQ7A0B (iSeries) Display MQ Listener AMQ7A1B (iSeries) Service control
AMQ7A0C (iSeries) Delete MQ Listener AMQ7A1C (iSeries) From Service
AMQ7A0D (iSeries) LSRNAME not allowed with AMQ7A1D (iSeries) To Service

PORT
Severity: 40 : Stop Error AMQ7A1E (iSeries) Display MQ Service
Explanation: A listener object can not be specified
with a port. AMQ7A20 (iSeries) Delete MQ Service
Response: Specify either a listener object or a port
number. AMQ7A21 (iSeries) Work with MQ Service object
AMQ7A0E (iSeries) LSRNAME not allowed with AMQ7A23 (iSeries) Start MQ Service
IPADDR
Severity: 40 : Stop Error AMQ7A24 (iSeries) End MQ Service
with an IP address. AMQ7A25 (iSeries) Channel initiator control
Response: Specify either a listener object or an IP
address. AMQ7A26 (iSeries) Command server control
AMQ7A0F (iSeries) Work with MQ Listener object AMQ7A27 (iSeries) Display Queue Manager Status
AMQ7A10 (iSeries) Create MQ Service AMQ7A28 (iSeries) Display Listener Status

AMQ7A29 (iSeries) Display Service Status AMQ7A39 (iSeries) Cluster workload queue use
AMQ7A2A (iSeries) LSRNAME not allowed with AMQ7A3A (iSeries) Queue Monitoring
OPTION
Severity: 40 : Stop Error AMQ7A3B (iSeries) Queue Manager Statistics
with an end option. AMQ7A3C (iSeries) Cluster Sender Monitoring
Response: Specify either a listener object or an end
option. AMQ7A3D (iSeries) Queue Statistics
AMQ7A2B (iSeries) Service startup AMQ7A3E (iSeries) Cluster Sender Statistics
AMQ7A2C (iSeries) Work with Connection Handles AMQ7A3F (iSeries) Statistics Interval
AMQ7A2D (iSeries) Connection Identifier AMQ7A40 (iSeries) Display MQ Route Information
AMQ7A2E (iSeries) End Queue Manager Connection AMQ7A41 (iSeries) Correlation Identifier
AMQ7A2F (iSeries) Work with MQ Connections AMQ7A42 (iSeries) Message Persistence
AMQ7A30 (iSeries) Header Compression AMQ7A43 (iSeries) Message Priority
AMQ7A31 (iSeries) Message Compression AMQ7A44 (iSeries) Report Option
AMQ7A32 (iSeries) Message compression *ANY not AMQ7A45 (iSeries) Reply Queue
valid for channel type.
Severity: 30 : Severe error AMQ7A46 (iSeries) Reply Queue Manager
Explanation: The message compression value *ANY is
only valid for *RCVR, *RQSTR and *SVRCN channel AMQ7A47 (iSeries) Message Expiry
types.
Response: Specify a valid message compression list. AMQ7A48 (iSeries) Expiry Report
AMQ7A33 (iSeries) Channel Monitoring AMQ7A49 (iSeries) Route Information
AMQ7A34 (iSeries) Channel Statistics AMQ7A4A (iSeries) Reply Message
AMQ7A35 (iSeries) Cluster Workload Rank AMQ7A4B (iSeries) Deliver Message
AMQ7A36 (iSeries) Cluster Workload Priority AMQ7A4C (iSeries) Forward Message
AMQ7A37 (iSeries) Cluster Channel Weight AMQ7A4D (iSeries) Maximum Activities
AMQ7A38 (iSeries) Cluster workload channels AMQ7A4E (iSeries) Route Detail

AMQ7A4F (iSeries) Browse Only AMQ7A58 (iSeries) RPLYQ required for
DSPMSG(*NO) and RPLYMSG(*YES).
AMQ7A50 (iSeries) Display Message Severity: 30 : Severe error
Explanation: DSPMSG(*NO) and RPLYMSG(*YES) can
AMQ7A51 (iSeries) Target Queue Manager not be specified without RPLYQ.
Response: If DSPMSG(*NO) and RPLYMSG(*YES) are
AMQ7A52 (iSeries) Display Information specified than RPLYQ must also be specified.
AMQ7A53 (iSeries) Wait Time AMQ7A59 (iSeries) RPLYQ required for

DSPMSG(*NO) and OPTION not
*NONE.
AMQ7A54 (iSeries) RTEINF(*YES) required for
RPLYMSG(*YES). Severity: 30 : Severe error
Severity: 30 : Severe error Explanation: DSPMSG(*NO) and OPTION not *NONE
can not be specified without RPLYQ.
Explanation: RPLYMSG(*YES) can not be specified
without RTEINF(*YES). Response: If DSPMSG(*NO) and OPTION not *NONE
are specified than RPLYQ must also be specified.
Response: If RPLYMSG(*YES) is specified then
RTEINF(*YES) must also be specified.
AMQ7A5A (iSeries) Run WebSphere MQ
Commands
AMQ7A55 (iSeries) RPLYQ required for
RPLYMQM.
AMQ7A5B (iSeries) Non Persistent Message Class
Explanation: RPLYMQM can not be specified without
AMQ7A5C (iSeries) NPMCLASS not allowed with
RPLYQ.
queue type *ALS or *RMT.
Response: If RPLYMQM is specified then RPLYQ
must also be specified.
Explanation: The NPMCLASS parameter may not be
specified for a queue of type *ALS or *RMT.
AMQ7A56 (iSeries) CRRLID specified with invalid
parameters. Response: Remove the NPMCLASS parameter from
the command or, if the command is CRTMQMQ,
specify a different value for QTYPE. Then try the
Explanation: The CRRLID parameter was specified command again.
with one or more of MSGPST, MSGPRTY, OPTION,
RPLYQ, RPLYMQM, EXPIRY, EXPRPT, RTEINF
AMQ7A5D (iSeries) MONQ not allowed with queue
RPLYMSG, DLVRMSG, FWDMSG, MAXACTS and
type *ALS or *RMT.
DETAIL which are invalid with CRRLID.
Response: Specify only those parameters which are
valid with CRRLID. Explanation: The MONQ parameter may not be
AMQ7A57 (iSeries) DSPMSG(*NO) specified with Response: Remove the MONQ parameter from the
invalid parameters. command or, if the command is CRTMQMQ, specify a
different value for QTYPE. Then try the command
again.
Explanation: DSPMSG(*NO) was specified with one
or more of BROWSE, DSPINF and WAIT which are
AMQ7A5E (iSeries) STATQ not allowed with queue
invalid with DSPMSG(*NO).
type *ALS or *RMT.
Response: Specify only those parameters which are
valid with DSPMSG(*NO).
Explanation: The STATQ parameter may not be
Response: Remove the STATQ parameter from the
command or, if the command is CRTMQMQ, specify a

AMQ7B04 (iSeries) Accounting Interval
again.
AMQ7B05 (iSeries) Accounting Override

AMQ7A5F (iSeries) ACCTQ not allowed with queue
type *ALS or *RMT.
AMQ7B06 (iSeries) Trace data size
Explanation: The ACCTQ parameter may not be
AMQ7B07 (iSeries) Perform replay only
Response: Remove the ACCTQ parameter from the
AMQ7B08 (iSeries) Activate backup
again. AMQ7B09 (iSeries) No connection handles to display
AMQ7A60 (iSeries) All queue managers have been AMQ7B0A (iSeries) Trace Route Recording
quiesced.
Severity: 0 : Information AMQ7B0B (iSeries) Activity Recording
Explanation: All queue managers have been
successfully quiesced. AMQ7B0C (iSeries) No queue manager connections
to display
Response: None.
AMQ7B0D (iSeries) No listener objects to display

AMQ7A61 (iSeries) MQMNAME not valid for
TRCEARLY(*YES).
AMQ7B0E (iSeries) No service objects to display
Explanation: The MQMNAME parameter may only be
AMQ7B0F (iSeries) CLWLRANK not allowed with
specified for TRCEARLY(*NO). TRCEARLY(*YES)
queue type *MDL.
applies to all queue managers.
Response: If TRCEARLY(*YES) is required remove
MQMNAME from the command. Explanation: The CLWLRANK parameter may not be
specified for a queue of type *MDL.
AMQ7A62 (iSeries) MQMNAME not valid for Response: Remove the CLWLRANK parameter from
SET(*END). the command or, if the command is CRTMQMQ,
command again.
Explanation: The MQMNAME parameter may only be
specified for SET(*ON) or SET(*OFF). SET(*END)
AMQ7B10 (iSeries) CLWLPRTY not allowed with
applies to all queue managers.
queue type *MDL.
Response: If SET(*END) is required remove
MQMNAME from the command.
Explanation: The CLWLPRTY parameter may not be
specified for a queue of type *MDL.
AMQ7B00 (iSeries) MQI Accounting
Response: Remove the CLWLPRTY parameter from
AMQ7B01 (iSeries) Input file
command again.
AMQ7B02 (iSeries) Queue Accounting
AMQ7B11 (iSeries) LSRNAME not allowed with
AMQ7B03 (iSeries) Member containing input BACKLOG
with a listener backlog.

Response: Specify either a listener object or a listener
AMQ7B16 (iSeries) CLWLWGHT only valid for
backlog.
channel types *CLUSSDR and
*CLUSRCVR.
AMQ7B12 (iSeries) MONCHL not valid for channel
type *CLTCN.
Explanation: The CLWLWGHT parameter may only
be specified with channel types *CLUSSDR or
Explanation: The MONCHL parameter may not be *CLUSRCVR.
specified with channel type *CLTCN.
Response: Remove the CLWLWGHT parameter from
Response: Remove the MONCHL parameter from the the command or, if the command is CRTMQMCHL,
command or, if the command is CRTMQMCHL, specify specify a different value for CHLTYPE. Then try the
a different value for CHLTYPE. Then try the command command again.
again.
AMQ7B17 (iSeries) CLWLUSEQ only allowed with
AMQ7B13 (iSeries) STATCHL not valid for channel queue type *LCL.
type *CLTCN.
Explanation: The CLWLUSEQ parameter may only be
Explanation: The STATCHL parameter may not be specified for a queue of type *LCL.
Response: Remove the CLWLUSEQ parameter from
Response: Remove the STATCHL parameter from the the command or, if the command is CRTMQMQ,
command or, if the command is CRTMQMCHL, specify specify a value of *LCL for QTYPE. Then try the
a different value for CHLTYPE. Then try the command command again.
again.
AMQ7B18 (iSeries) MCAUSRID not valid for
AMQ7B14 (iSeries) CLWLRANK only valid for channel type *CLTCN.
*CLUSRCVR.
Explanation: The MCAUSRID parameter may not be
Explanation: The CLWLRANK parameter may only be
Response: Remove the MCAUSRID parameter from
specified with channel types *CLUSSDR or
the command or, if the command is CRTMQMCHL,
*CLUSRCVR.
specify a different value for CHLTYPE. Then try the
Response: Remove the CLWLRANK parameter from command again.
command again.
AMQ7B15 (iSeries) CLWLPRTY only valid for

*CLUSRCVR.
Explanation: The CLWLPRTY parameter may only be
specified with channel types *CLUSSDR or
*CLUSRCVR.
Response: Remove the CLWLPRTY parameter from
command again.

Chapter 6. 8000-8999 - Administration
messages.
AMQ8001 WebSphere MQ queue manager created. AMQ8007 WebSphere MQ queue deleted.

Explanation: WebSphere MQ queue manager Explanation: WebSphere MQ queue <insert_5>
<insert_5> created. deleted.
AMQ8002 WebSphere MQ queue manager AMQ8008 WebSphere MQ queue changed.

<insert_5> deleted.
Explanation: WebSphere MQ queue <insert_5>
Explanation: WebSphere MQ queue manager changed.
<insert_5> deleted.
Response: None.
Response: None.
AMQ8009 (iSeries) WebSphere MQ queue created by
AMQ8003 WebSphere MQ queue manager copying.
<insert_5> started.
Explanation: Queue <insert_5> created in library
Explanation: WebSphere MQ queue manager <insert_3> by copying.
<insert_5> started.
Response: None.
Response: None.
AMQ8010 WebSphere MQ process created.
<insert_5> ended.
Explanation: WebSphere MQ process <insert_5>
created.
Response: None.
<insert_5> ended.
Response: None.
AMQ8011 WebSphere MQ process deleted.
changed. Explanation: WebSphere MQ process <insert_5>
deleted.
Response: None.
<insert_5> changed.
AMQ8012 WebSphere MQ process changed.
Response: None.
AMQ8006 WebSphere MQ queue created. Explanation: WebSphere MQ process <insert_5>
changed.
Response: None.
Explanation: WebSphere MQ queue <insert_5>
created.
AMQ8013 (iSeries) WebSphere MQ process copied.
Response: None.

AMQ8020 Ping WebSphere MQ channel complete.
Explanation: Process <insert_5> created in library
<insert_3> by copying.
Explanation: Ping channel <insert_5> complete.
Response: None.
Response: None.
AMQ8014 WebSphere MQ channel created.
AMQ8021 Request to start WebSphere MQ
Listener accepted.
Explanation: WebSphere MQ channel <insert_5>
created.
Explanation: The Request to start the Listener has
Response: None.
been accepted and is being processed.
Response: Should the request to start the listener be
AMQ8015 WebSphere MQ channel deleted.
unsuccessful then information related to the error will
Severity: 0 : Information be available in the queue manager error log. Once
started the status of the listener may be monitored
Explanation: WebSphere MQ channel <insert_5> using the MQSC command ’DISPLAY LSSTATUS’. On
deleted. iSeries the status of the listener may also be monitored
Response: None. using the ’WRKMQMLSR OPTION(*STATUS)’
command.
AMQ8016 WebSphere MQ channel changed.

AMQ8022 WebSphere MQ queue cleared.
Explanation: WebSphere MQ channel <insert_5>
changed. Explanation: All messages on queue <insert_5> have
been deleted.
Response: None.
Response: None.
AMQ8017 (iSeries) WebSphere MQ channel copied.

AMQ8023 WebSphere MQ channel reset.
Explanation: Channel <insert_5> created by copying.
Explanation: Channel <insert_5> has been reset.
Response: None.
Response: None.
AMQ8018 Start WebSphere MQ channel accepted.

AMQ8024 WebSphere MQ channel initiator
Severity: 0 : Information started.
Explanation: The channel <insert_5> is being started. Severity: 0 : Information
The start channel function has been initiated. This
involves a series of operations across the network Explanation: The channel initiator for queue
before the channel is actually started. The channel <insert_5> has been started.
status displays ″BINDING″ for a short period while Response: None.
communication protocols are negotiated with the
channel with whom communication is being initiated.
AMQ8025 WebSphere MQ channel resolved.
Response: None.
AMQ8019 Stop WebSphere MQ channel accepted. Explanation: In doubt messages for WebSphere MQ
channel <insert_5> have been resolved.
Response: None.
Explanation: The channel <insert_5> has been
requested to stop.
Response: None.

AMQ8026 End WebSphere MQ queue manager AMQ8033 WebSphere MQ object recreated.
accepted.
Explanation: MQ object <insert_5> has been recreated
Explanation: A controlled stop request has been from image.
initiated for queue manager <insert_5>.
Response: None.
Response: None.
AMQ8034 WebSphere MQ object image recorded.
AMQ8027 WebSphere MQ command server
started.
Explanation: Image of MQ object <insert_5> has been
recorded.
Explanation: The command server has been started.
Response: None.
Response: None.
AMQ8035 WebSphere MQ Command Server Status
AMQ8028 WebSphere MQ command server ended. . . : Running
Explanation: The command server has been stopped. Explanation: None.
AMQ8029 WebSphere MQ authority granted. AMQ8036 WebSphere MQ command server status .

. : Stopping
Explanation: Authority for object <insert_5> granted.
Explanation: None.
Response: None.
Response: None.
AMQ8030 WebSphere MQ authority revoked.
AMQ8037 WebSphere MQ command server status .
. : Starting
Explanation: Authority for object <insert_5> revoked.
Response: None.
Explanation: None.
Response: None.
AMQ8031 (iSeries) Message Queue Manager
connected.
AMQ8038 WebSphere MQ command server status .
. : Running with queue disabled
Explanation: The message queue manager has been
connected.
Explanation: None.
Response: None.
Response: None.
AMQ8032 (iSeries) Message Queue Manager
disconnected. AMQ8039 WebSphere MQ command server status .
. : Stopped
Explanation: The message queue manager has been
disconnected. Explanation: None.
Chapter 6. 8000-8999 - Administration 135

manager from the Windows Active Directory failed.
This may be because the appropriate entry could not be
ending.
opened or modified, or the Service Control Point has
Severity: 0 : Information already been removed.
Explanation: None. Response: Check that your account has the authority
to delete objects from the Active Directory, and that the
Response: None.
entry has not already been deleted.
AMQ8041 The queue manager cannot be restarted

AMQ8045 (Windows) An error occurred while
or deleted because processes, that were
removing the queue manager from the
previously connected, are still running.
Service Control Manager.
Explanation: Processes, that were connected to the
Explanation: The attempt to remove the queue
queue manager the last time it was running, are still
manager from the Windows registry failed. This may
active. The queue manager cannot be restarted.
be because the appropriate entry could not be opened
Response: Stop the processes and try to start the or modified.
queue manager.
Response: Check that the registry has sufficient space
on your disk to grow and that your account has the
AMQ8041 (iSeries) The queue manager cannot be authority to modify it.
restarted or deleted.
Severity: 40 : Stop Error AMQ8046 Migrating objects for <insert_3>.
Explanation: Jobs that were connected to the queue Severity: 0 : Information
manager the last time it was running, are still active.
Response: None.
The queue manager cannot be restarted or deleted.
Response: Use option 22 from WRKMQM to identify
AMQ8047 Channel migration statistics : <insert_1>
which jobs are connected to the queue manager. End
migrated. <insert_2> failed.
the connected jobs and then retry the command.
AMQ8042 Process <insert_1> is still running. Explanation: Information on the number of channel
objects migrated from previous versions of WebSphere
MQ channel definitions as well as any failures that
occurred.
AMQ8043 Non runtime application attempted to
Response: None.
connect to runtime only queue manager.
AMQ8048 Default objects statistics : <insert_1>
Explanation: A non runtime application attempted to created. <insert_2> replaced. <insert_3>
connect to a queue manager on a node where support failed.
for non runtime applications has not been installed.
The connect attempt will be rejected with a reason of
MQRC_ENVIRONMENT_ERROR. Explanation: Information on the number of objects
created or replaced successfully as well as any failures
Response: If the node is intended to support only
that occurred while creating the default objects.
runtime applications, investigate why a non runtime
application has attempted to connect to the queue Response: None.
manager. If the node is intended to support non
runtime only applications, investigate if the base option
AMQ8049 Object <insert_4>. Unable to create or
has been installed. The base option must be installed if
replace.
non runtime applications are to run on this node.
AMQ8044 (Windows) An error occurred while Explanation: While creating or replacing the default
removing the queue manager from the object <insert_4> for WebSphere MQ queue manager
Active Directory. <insert_5> an error occurred. The error was due to
improper authorization. The reason code is <insert_1>.
Response: Check this log for more details of what the
Explanation: The attempt to remove the queue

problem may be. Make sure there are sufficient
resources such as disk space and storage. For damaged
replace.
or corrupted objects, replace these from backup objects.
If all else fails, delete the queue manager <insert_5> Severity: 20 : Error
using dltmqm and create it again using crtmqm.
Explanation: While creating or replacing the default
object <insert_4> for WebSphere MQ queue manager
AMQ8050 Creating or replacing default objects for <insert_5> an error occurred. The error was due to a
<insert_3>. damaged object. The reason code is <insert_1>.
Severity: 0 : Information Response: Check this log for more details of what the
problem may be. Make sure there is sufficient resources
Response: None.
such as disk space and storage. For damaged or
corrupted objects, replace these from backup objects. If
AMQ8051 For details of the failures that occurred, all else fails, delete the queue manager <insert_5> using
please check AMQERR01.LOG. dltmqm and create it again using crtmqm.
Response: None. replace.
AMQ8052 Completing setup.
Explanation: While creating or replacing the default
Severity: 0 : Information object <insert_4> for WebSphere MQ queue manager
Response: None. <insert_5> an error occurred. The error was due to a
channel definition error. The error code is <insert_1>
(X<insert_2>).
replace. Response: Check this log for more details of what the
Severity: 20 : Error such as disk space and storage. For damaged or
Explanation: While creating or replacing the default corrupted objects, replace these from backup objects. If
object <insert_4> for WebSphere MQ queue manager all else fails, delete the queue manager <insert_5> using
<insert_5> an error occurred. The error was due to a dltmqm and create it again using crtmqm.
broken connection. The reason code is <insert_1>.
Response: Check this log for more details of what the AMQ8057 Object <insert_4>. Unable to create or
problem may be. Make sure there is sufficient resources replace.
such as disk space and storage. For damaged or Severity: 20 : Error
corrupted objects, replace these from backup objects. If
all else fails, delete the queue manager <insert_5> using Explanation: While creating or replacing the default
dltmqm and create it again using crtmqm. object <insert_4> for WebSphere MQ queue manager
<insert_5> an error occurred. The error was due to
invalid records in the channel definition file. The error
AMQ8054 Object <insert_4>. Unable to create or code is <insert_1> (X<insert_2>).
replace.
Severity: 20 : Error problem may be. Make sure there is sufficient resources
Explanation: While creating or replacing the default such as disk space and storage. For damaged or
object <insert_4> for WebSphere MQ queue manager corrupted objects, replace these from backup objects. If
<insert_5> an error occurred. The error was due to all else fails, delete the queue manager <insert_5> using
unavailable storage. The reason code is <insert_1>. dltmqm and create it again using crtmqm.

problem may be. Make sure there is sufficient resources AMQ8058 Object <insert_4>. Unable to create or
such as disk space and storage. For damaged or replace.
corrupted objects, replace these from backup objects. If Severity: 20 : Error
all else fails, delete the queue manager <insert_5> using
dltmqm and create it again using crtmqm. Explanation: While creating or replacing the default
object <insert_4> for WebSphere MQ queue manager
<insert_5> an error occurred. The error was due to not
finding the channel definition file. The error code is
<insert_1> (X<insert_2>).

AMQ8064 (Windows) Not authorized to start trusted
application.
corrupted objects, replace these from backup objects. If Severity: 20 : Error
all else fails, delete the queue manager <insert_5> using
Explanation: The user <insert_5> is not authorized to
dltmqm and create it again using crtmqm.
start the trusted application <insert_3>. The application
has not started.
Response: Add the user to the local ’mqm’ security
replace.
group and restart the application.
Explanation: While creating or replacing the default AMQ8065 (Windows) Local group <insert_3> not
object <insert_4> for WebSphere MQ queue manager found.
<insert_5> an error occurred. The error was due to an
unexpected error, error code <insert_1> (X<insert_2>).
Explanation: The local group <insert_3> is unavailable.
It is not possible to verify that the user is authorized.
The function cannot continue.
corrupted objects, replace these from backup objects. If Response: Create the required local group and retry
all else fails, delete the queue manager <insert_5> using the operation.
dltmqm and create it again using crtmqm.
AMQ8066 (Windows) Local mqm group not found.

AMQ8061 (Windows) Command <insert_4> is not
valid. Severity: 20 : Error
Severity: 10 : Warning Explanation: The local mqm group is unavailable. It is

not possible to verify that the user is authorized. The
Explanation: The command <insert_4> at line function cannot continue.
<insert_1> in the WebSphere MQ service command file
<insert_3> for queue manager <insert_5> is not valid Response: Create the local mqm group and retry the
for use in the service command file. The line is ignored. operation.

operation. AMQ8067 WebSphere MQ channel auto-defined.
AMQ8062 (Windows) Unexpected return code, Explanation: Channel <insert_5> auto-defined.
<insert_1>, from command <insert_3>.
Response: None.
Explanation: An unexpected return code, <insert_1>, AMQ8068 Setup completed.
was returned by command <insert_3>. This command
was issued by the WebSphere MQ service for queue Severity: 0 : Information
manager <insert_4>. Response: None.
Response: Verify that the command and parameters
are correct. AMQ8069 ApplicationGroup for the crtmqm
command does not contain the mqm
AMQ8063 (Windows) Not authorized to issue userid.
command <insert_3>. Severity: 40 : Stop Error
Severity: 20 : Error Explanation: WebSphere MQ queue manager
Explanation: The current user <insert_5> is not <insert_5> not created. The ApplicationGroup specified
authorized to issue the command <insert_3>. The for the crtmqm command must contain the mqm userid
command is ignored. when the RestrictedMode option (-g) is specified.
Response: Add the user to the local ’mqm’ security Response: None.
group and retry the operation.

AMQ8070 ApplicationGroup for crtmqm command AMQ8075 (Windows) Authorization failed because
is not defined. the SID for entity <insert_3> cannot be
obtained.
<insert_5> not created. RestrictedMode option (-g) Explanation: The Object Authority Manager was
specified, but the ApplicationGroup does not exist. unable to obtain a SID for the specified entity.
Response: None. Response: Ensure that the entity is valid, and that all
necessary domain controllers are available.
AMQ8071 RestrictedMode option not supported on
this platform. AMQ8076 (Windows) Authorization failed because
no SID was supplied for entity
<insert_3>.
<insert_5> not created. The RestrictedMode option was
specified but is not supported on this platform. Explanation: The Object Authority Manager was not
supplied with SID information for the specified entity,
Response: None.
and the security policy is set to ’NTSIDsRequired’.
Response: Ensure that the application is supplying a
AMQ8072 (Windows) Not authorized to administer
valid SID, and that the security policy is set as you
channels.
require.
Explanation: The command server for queue manager AMQ8077 (Windows) Entity <insert_3> has
<insert_3> received an administration command for insufficient authority to access object
channels. The user <insert_5> is not authorized to <insert_4>.
administer WebSphere MQ channels. The command
server has not processed the command.
Explanation: The specified entity is not authorized to
access the required object. The following requested
group, and ensure that the security policy is set as
permissions are unauthorized: <insert_5>
required.
Response: Ensure that the correct level of authority
has been set for this entity against the required object,
AMQ8073 (Windows) Authorization failed because
or ensure that the entity is a member of a privileged
SID: (<insert_3>) could not be resolved.
group.
Explanation: The Object Authority Manager was AMQ8078 Waiting for queue manager <insert_3> to
unable to resolve the specified SID into entity and end.
domain information.
Response: Ensure that the application provides a SID
Response: None.
that is recognized on this system, that all necessary
domain controllers are available, and that the security
policy is set as you required. AMQ8079 (iSeries) WebSphere MQ trigger monitor
job started.
AMQ8074 (Windows) Authorization failed as the Severity: 0 : Information
SID <insert_3> does not match the entity
Explanation: The message queue manager trigger
<insert_4>.
monitor job has been started for queue manager
Severity: 10 : Warning <insert_5> to process messages on the selected initiation
queue. See previously issued messages for job details.’
Explanation: The Object Authority Manager received
inconsistent data - the supplied SID does not match Response: None.
that of the supplied entity information.
Response: Ensure that the application is supplying
valid entity and SID information.

AMQ8079 (Windows) Access was denied when AMQ8083 WebSphere MQ queue manager
attempting to retrieve group <insert_3> starting.
membership information for user
<insert_3>.
<insert_3> starting.
Explanation: WebSphere MQ, running with the
Response: None.
authority of user <insert_4>, was unable to retrieve
group membership information for the specified user.
AMQ8084 WebSphere MQ connection not found.
Response: Ensure Active Directory access permissions
allow user <insert_4> to read group memberships for Severity: 40 : Stop Error
user <insert_3>. To retrieve group membership
information for a domain user, MQ must run with the Explanation: The connection specified does not exist.
authority of a domain user. Response: Correct the connection name and then try
the command again.
AMQ8080 (iSeries) WebSphere MQ trigger monitor
job start failed. AMQ8085 WebSphere MQ queue manager
Severity: 40 : Stop Error <insert_3> is being started for replay.
Explanation: Message queue manager trigger job Severity: 0 : Information

failed to start for manager <insert_5>. Failure reason Explanation: WebSphere MQ queue manager
code is <insert_2>. See previously issued messages for <insert_3> is being started for replay. The strmqm
more information.’ command has been issued with the ’-r’ option. see the
Response: None. WebSphere MQ System Administration documentation
for details.
AMQ8081 (Windows) Not authorized to administer Response: None.

queue managers.
Severity: 10 : Warning AMQ8086 WebSphere MQ queue manager
<insert_3> is being activated.
Explanation: The command server for queue manager
<insert_3> received an administration command for a Severity: 0 : Information
queue manager. The user <insert_5> is not authorized Explanation: WebSphere MQ queue manager
to administer WebSphere MQ queue managers. The <insert_3> is being activated. The strmqm command
command server has not processed the command. has been issued with the ’-a’ option. see the WebSphere
Response: Add the user to the local ’mqm’ security MQ System Administration documentation for details.
group, and ensure that the security policy is set as Response: None.
required.
AMQ8086 (iSeries) WebSphere MQ queue manager

AMQ8082 (Windows) Not authorized to administer <insert_3> is being activated.
clusters.
Explanation: The command server for queue manager <insert_3> is being activated. The STRMQM command
<insert_3> received an administration command for has been issued with the ACTIVATE(*YES) option. see
clusters. The user <insert_5> is not authorized to the WebSphere MQ System Administration
administer WebSphere MQ clusters. The command documentation for further details.
server has not processed the command.
Response: None.
group, and ensure that the security policy is set as
required. AMQ8087 Attempt to migrate listener <insert_3> to
a QM object failed with <insert_1>.
Explanation: Whilst processing legacy services,
listener <insert_3> could not be migrated to an MQ
object named <insert_4>, the object creation failed with
<insert_1>.

AMQ8092 Service migration statistics : <insert_1>
migrated. <insert_2> failed.
AMQ8088 Attempt to migrate trigger monitor
<insert_3> to a QM object failed with Explanation: Information on the number of service
<insert_1>. objects migrated from previous versions of WebSphere
MQ for Windows services as well as any failures that
occurred.
Explanation: Whilst processing legacy services, trigger
Response: None.
monitor <insert_3> could not be migrated to an MQ
object named <insert_4>, the object creation failed with
<insert_1>. AMQ8101 WebSphere MQ error (<insert_1>) has
occurred.
your IBM support center. Severity: 40 : Stop Error
Explanation: An unexpected reason code with
AMQ8089 Attempt to migrate channel service hexadecimal value <insert_1> was received from the
<insert_3> to a QM object failed with WebSphere MQ queue manager during command
<insert_1>. processing. (Note that hexadecimal values in the range
X’07D1’-X’0BB7’ correspond to MQI reason codes
2001-2999.) More information might be available in the
Explanation: Whilst processing legacy services, log. If the reason code value indicates that the error
channel service <insert_3> could not be migrated to an was associated with a particular parameter, the
MQ object named <insert_4>, the object creation failed parameter concerned is <insert_4>.
with <insert_1>.
Response: Correct the error and then try the
Response: Save the generated output files and contact command again.
AMQ8102 WebSphere MQ object name specified
AMQ8090 Attempt to migrate channel initiator in <insert_4> not valid.
<insert_3> to a QM object failed with
<insert_1>.
Explanation: The object name <insert_5> specified in
<insert_4> is not valid. The length of the name must
Explanation: Whilst processing legacy services, not exceed 48 characters, or 20 characters if it is a
channel initiator <insert_3> could not be migrated to an channel name. The name should contain the following
MQ object named <insert_4>, the object creation failed characters only: lowercase a-z, uppercase A-Z, numeric
with <insert_1>. 0-9, period (.), forward slash (/), underscore (_) and
percent sign (%).
your IBM support center. Response: Change the length of the parameter value
or change the parameter value to contain a valid
combination of characters, then try the command again.
AMQ8091 Attempt to migrate custom service
<insert_3> to a QM object failed with
<insert_1>. AMQ8103 Insufficient storage available.
Severity: 20 : Error Severity: 40 : Stop Error
Explanation: Whilst processing legacy services, Explanation: There was insufficient storage available
custom service <insert_3> could not be migrated to an to perform the requested operation.
MQ object named <insert_4>, the object creation failed
Response: Free some storage and then try the
with <insert_1>.
command again.
AMQ8104 WebSphere MQ directory <insert_3> not
found.
Explanation: Directory <insert_3> was not found. This
directory is created when WebSphere MQ is installed
successfully. Refer to the log for more information.

Response: Verify that installation of WebSphere MQ
AMQ8111 (iSeries) Message Queue Manager exists
was successful. Correct the error and then try the
under a different name.
command again.
AMQ8105 Object error. Explanation: A message queue manager exists with a
name different from the value <insert_5> specified in
<insert_2>.
Explanation: An object error occurred. Refer to the log
Response: Change the parameter value to the name of
for more information.
the existing message queue manager and then try the
Response: Correct the error and then try the command again.
command again.
AMQ8112 (iSeries) PRCNAME not allowed with
AMQ8106 WebSphere MQ queue manager being queue type *ALS or *RMT.
created.
Explanation: The PRCNAME parameter may not be
Explanation: The queue manager is being created. specified for a queue of type *ALS or *RMT.
Response: Wait for the creation process to complete Response: Remove the PRCNAME parameter from
and then try the command again. the command or, if the command is CRTMQMQ,
command again.
running.
AMQ8113 (iSeries) TRGENBL not allowed with
Severity: 10 : Warning queue type *ALS or *RMT.
Explanation: The queue manager is running. Severity: 40 : Stop Error
Response: None. Explanation: The TRGENBL parameter may not be
AMQ8108 WebSphere MQ queue manager Response: Remove the TRGENBL parameter from the
<insert_3> ending. command or, if the command is CRTMQMQ, specify a
Severity: 10 : Warning different value for QTYPE. Then try the command
again.
Explanation: The queue manager <insert_3> is ending.
Response: Wait for the queue manager to end and AMQ8114 (iSeries) GETENBL not allowed with
then try the command again. queue type *RMT.
AMQ8109 WebSphere MQ queue manager being
deleted. Explanation: The GETENBL parameter may not be
specified for a queue of type *RMT.
Response: Remove the GETENBL parameter from the
Explanation: The queue manager is being deleted. command or, if the command is CRTMQMQ, specify a
Response: Wait for the deletion process to complete. different value for QTYPE. Then try the command
again.
AMQ8110 WebSphere MQ queue manager already

exists. AMQ8115 (iSeries) SHARE not allowed with queue
type *ALS or *RMT.
Explanation: The queue manager <insert_5> already
exists. Explanation: The SHARE parameter may not be
Response: None.
Response: Remove the SHARE parameter from the
again.

AMQ8116 (iSeries) MSGDLYSEQ not allowed with AMQ8121 (iSeries) TRGMSGPTY not allowed with
queue type *ALS or *RMT. queue type *ALS or *RMT.
Explanation: The MSGDLYSEQ parameter may not be Explanation: The TRGMSGPTY parameter may not be
specified for a queue of type *ALS or *RMT. specified for a queue of type *ALS or *RMT.
Response: Remove the MSGDLYSEQ parameter from Response: Remove the TRGMSGPTY parameter from
the command or, if the command is CRTMQMQ, the command or, if the command is CRTMQMQ,
specify a different value for QTYPE. Then try the specify a different value for QTYPE. Then try the
command again. command again.
AMQ8117 WebSphere MQ queue manager deletion AMQ8122 (iSeries) TRGDATA not allowed with
incomplete. queue type *ALS or *RMT.
Explanation: Deletion of queue manager <insert_5> Explanation: The TRGDATA parameter may not be
was only partially successful. An object was not found, specified for a queue of type *ALS or *RMT.
or could not be deleted. Refer to the log for more
Response: Remove the TRGDATA parameter from the
information.
Response: Delete any remaining queue manager different value for QTYPE. Then try the command
objects. again.
AMQ8118 WebSphere MQ queue manager does AMQ8123 (iSeries) RTNITV not allowed with queue
not exist. type *ALS or *RMT.
Explanation: The queue manager <insert_5> does not Explanation: The RTNITV parameter may not be
exist. specified for a queue of type *ALS or *RMT.
Response: Either create the queue manager (crtmqm Response: Remove the RTNITV parameter from the
command) or correct the queue manager name used in command or, if the command is CRTMQMQ, specify a
the command and then try the command again. different value for QTYPE. Then try the command
again.
AMQ8119 (iSeries) TRGTYPE not allowed with
queue type *ALS or *RMT. AMQ8124 (iSeries) MAXMSGLEN not allowed with
Explanation: The TRGTYPE parameter may not be
specified for a queue of type *ALS or *RMT. Explanation: The MAXMSGLEN parameter may not
be specified for a queue of type *ALS or *RMT.
Response: Remove the TRGTYPE parameter from the
command or, if the command is CRTMQMQ, specify a Response: Remove the MAXMSGLEN parameter from
different value for QTYPE. Then try the command the command or, if the command is CRTMQMQ,
again. specify a different value for QTYPE. Then try the
command again.
AMQ8120 (iSeries) TRGDEPTH not allowed with
queue type *ALS or *RMT. AMQ8125 (iSeries) BKTTHLD not allowed with
Explanation: The TRGDEPTH parameter may not be
specified for a queue of type *ALS or *RMT. Explanation: The BKTTHLD parameter may not be
Response: Remove the TRGDEPTH parameter from
the command or, if the command is CRTMQMQ, Response: Remove the BKTTHLD parameter from the
specify a different value for QTYPE. Then try the command or, if the command is CRTMQMQ, specify a
command again. different value for QTYPE. Then try the command
again.

AMQ8126 (iSeries) BKTQNAME not allowed with AMQ8131 (iSeries) RMTQNAME only allowed with
queue type *ALS or *RMT. queue type *RMT.
Explanation: The BKTQNAME parameter may not be Explanation: The RMTQNAME parameter may only
specified for a queue of type *ALS or *RMT. be specified for a queue of type *RMT.
Response: Remove the BKTQNAME parameter from Response: Remove the RMTQNAME parameter from
the command or, if the command is CRTMQMQ, the command or, if the command is CRTMQMQ,
AMQ8127 (iSeries) INITQNAME not allowed with AMQ8132 (iSeries) RMTMQMNAME only allowed
queue type *ALS or *RMT. with queue type *RMT.
Explanation: The INITQNAME parameter may not be Explanation: The RMTMQMNAME parameter may
specified for a queue of type *ALS or *RMT. only be specified for a queue of type *RMT.
Response: Remove the INITQNAME parameter from Response: Remove the RMTMQMNAME parameter
the command or, if the command is CRTMQMQ, from the command or, if the command is CRTMQMQ,
AMQ8128 (iSeries) USAGE not allowed with queue AMQ8133 (iSeries) TMQNAME only allowed with
type *ALS or *RMT. queue type *RMT.
Explanation: The USAGE parameter may not be Explanation: The TMQNAME parameter may only be
specified for a queue of type *ALS or *RMT. specified for a queue of type *RMT.
Response: Remove the USAGE parameter from the Response: Remove the TMQNAME parameter from
command or, if the command is CRTMQMQ, specify a the command or, if the command is CRTMQMQ,
different value for QTYPE. Then try the command specify a different value for QTYPE. Then try the
again. command again.
AMQ8129 (iSeries) DFNTYPE only allowed with AMQ8134 (iSeries) HDNBKTCNT not allowed with
queue type *MDL. queue type *ALS or *RMT.
Explanation: The DFNTYPE parameter may only be Explanation: The HDNBKTCNT parameter may not
specified for a queue of type *MDL. be specified for a queue of type *ALS or *RMT.
Response: Remove the DFNTYPE parameter from the Response: Remove the HDNBKTCNT parameter from
command or, if the command is CRTMQMQ, specify a the command or, if the command is CRTMQMQ,
different value for QTYPE. Then try the command specify a different value for QTYPE. Then try the
again. command again.
AMQ8130 (iSeries) TGTQNAME only allowed with AMQ8135 Not authorized.

queue type *ALS.
Explanation: You are not authorized to perform the
Explanation: The TGTQNAME parameter may only requested operation for the WebSphere MQ object
be specified for a queue of type *ALS. <insert_5> specified in <insert_3>. Either you are not
authorized to perform the requested operation, or you
Response: Remove the TGTQNAME parameter from
are not authorized to the specified MQ object. For a
copy command, you may not be authorized to the
specified source MQ object, or, for a create command,
command again.
you may not be authorized to the system default MQ
object of the specified type.

Response: Obtain the necessary authority from your Response: Wait for the queue manager startup process
security officer or WebSphere MQ administrator. Then to complete and then try the command again.
try the command again.
AMQ8136 (iSeries) Error detected by prompt control stopped.
program.
Explanation: The queue manager <insert_5> is
Explanation: A prompt control program detected stopped.
errors.
Response: Use the strmqm command to start the
Response: See the previously listed messages in the queue manager, and then try the command again.
job log. Correct the errors and then prompt for the
command again.
AMQ8143 WebSphere MQ queue not empty.
AMQ8137 WebSphere MQ queue manager already
starting. Explanation: The queue <insert_5> specified in
<insert_2> is not empty or contains uncommitted
updates.
Explanation: The strmqm command was unsuccessful
Response: Commit or roll back any uncommitted
because the queue manager <insert_5> is already
updates. If the command is DELETE QLOCAL, use the
starting.
CLEAR QLOCAL command to clear the messages from
Response: Wait for the strmqm command to complete. the queue. Then try the command again.
AMQ8138 The WebSphere MQ queue has an AMQ8144 Log not available.

incorrect type.
Explanation: The WebSphere MQ logging resource is
Explanation: The operation is not valid with queue not available.
<insert_5> because it is not a local queue.
Response: Use the dltmqm command to delete the
Response: Change the QNAME parameter to specify a queue manager and then the crtmqm command to
queue of the correct type. create the queue manager. Then try the command
again.
AMQ8139 Already connected.
AMQ8145 Connection broken.
Explanation: A connection to the WebSphere MQ
queue manager already exists. Explanation: The connection to the WebSphere MQ
queue manager failed during command processing.
Response: None.
This may be caused by an endmqm command being
issued by another user, or by a queue manager error.
AMQ8140 Resource timeout error.
Severity: 40 : Stop Error message queue manager, wait until the message queue
manager has started, and try the command again.
Explanation: A timeout occurred in the
communication between internal WebSphere MQ queue
manager components. This is most likely to occur when AMQ8146 WebSphere MQ queue manager not
the system is heavily loaded. available.
Response: Wait until the system is less heavily loaded, Severity: 40 : Stop Error
Explanation: The queue manager is not available
because it has been stopped or has not been created.
AMQ8141 WebSphere MQ queue manager starting.
Response: Use the crtmqm command to create the
Severity: 40 : Stop Error message queue manager, or the strmqm command to
start the message queue manager as necessary. Then try
Explanation: The queue manager <insert_5> is the command again.
starting.

AMQ8146 (iSeries) WebSphere MQ queue manager AMQ8148 WebSphere MQ object in use.
not available.
Explanation: The object <insert_5> specified in
Explanation: The queue manager is not available <insert_3> is in use by an MQ application program.
because it has been stopped or has not been created.
Response: Wait until the object is no longer in use and
Response: Use the CRTMQM command to create the then try the command again. If the command is ALTER
message queue manager or the STRMQM command to or CHANGE, specify FORCE to force the processing of
start the message queue manager as necessary, then the object regardless of any application program
retry the command. If a queue manager was not affected by the change. If the object is the dead-letter
specified, ensure that a default queue manager has queue and the open input count is nonzero, it may be
been created and is started using the WRKMQM in use by an MQ channel. If the object is another queue
command. object with a nonzero open output count, it may be in
use by a MQ channel (of type RCVR or RQSTR). In
either case, use the STOP CHANNEL and START
AMQ8147 WebSphere MQ object <insert_3> not
CHANNEL commands to stop and restart the channel
found.
in order to solve the problem. To alter the queue
Severity: 40 : Stop Error USAGE the FORCE option must be used if the queue is
not empty.
Explanation: If the command entered was Change or
Display, the object <insert_3> specified does not exist. If
the command entered was Copy, the source object does AMQ8149 WebSphere MQ object damaged.
not exist. If the command entered was Create, the
system default MQ object of the specified type does not
exist. Explanation: The object <insert_5> specified in
<insert_4> is damaged.
Response: Correct the object name and then try the
command again or, if you are creating a new queue or Response: The object contents are not valid. Issue the
process object, either specify all parameters explicitly or DISPLAY CHANNEL, DISPLAY QUEUE, or DISPLAY
ensure that the system default object of the required PROCESS command, as required, to determine the
type exists. The system default queue names are name of the damaged object. Issue the DEFINE
SYSTEM.DEFAULT.LOCAL.QUEUE, command, for the appropriate object type, to replace
SYSTEM.DEFAULT.ALIAS.QUEUE and the damaged object, then try the command again.
SYSTEM.DEFAULT.REMOTE.QUEUE. The system
default process name is SYSTEM.DEFAULT.PROCESS.
AMQ8150 WebSphere MQ object already exists.
AMQ8147 (iSeries) WebSphere MQ object <insert_5>
not found. Explanation: The object <insert_5> specified for
<insert_3> could not be created because it already
exists.
Explanation: If the command entered was Change or
Response: Check that the name is correct and try the
Display, the MQ object <insert_5> specified does not
command again specifying REPLACE, or delete the
exist. If the command entered was Copy, the source
object. Then try the command again.
MQ object does not exist. If the command entered was
Create, the system default MQ object of the specified
type does not exist. AMQ8151 WebSphere MQ object has different
type.
Response: Correct the MQ object name and then try
the command again or, if you are creating a new MQ Severity: 40 : Stop Error
queue or process object, either specify all parameters
explicitly or ensure that the system default object of the Explanation: The type specified for object <insert_5> is
required type exists. The system default queue names different from the type of the object being altered or
are SYSTEM.DEFAULT.LOCAL.QUEUE, defined.
SYSTEM.DEFAULT.ALIAS.QUEUE and Response: Use the correct MQ command for the object
SYSTEM.DEFAULT.REMOTE.QUEUE. The system type, and then try the command again.
default process name is SYSTEM.DEFAULT.PROCESS.

until the problem has been corrected, and then try the
AMQ8152 Source WebSphere MQ object has
command again.
different type.
AMQ8158 (iSeries) API exit not found.
Explanation: The type of the source object is different
from that specified.
Explanation: The API crossing exit program was not
Response: Correct the name of the command, or
found.
source object name, and then try the command again,
or try the command using the REPLACE option. Response: Ensure that the API crossing exit program
for the MQI exists, and that its name and library are
correctly specified. Correct any errors and then try the
AMQ8153 Insufficient disk space for the specified
command again.
queue.
AMQ8159 (iSeries) MAXDEPTH not allowed with
Explanation: The command failed because there was queue type *ALS or *RMT.
insufficient disk space available for the specified queue.
Response: Release some disk space and then try the
Explanation: The MAXDEPTH parameter may not be
command again.
Response: Remove the MAXDEPTH parameter from
AMQ8154 API exit load error.
Severity: 40 : Stop Error specify a different value for QTYPE. Then try the
command again.
Explanation: The WebSphere MQ queue manager was
unable to load the API crossing exit.
AMQ8160 (iSeries) DFTSHARE not allowed with
Response: Ensure that the API crossing exit program
is valid, and that its name and directory are correctly
specified. Correct any error and then try the command Severity: 40 : Stop Error
again.
Explanation: The DFTSHARE parameter may not be
AMQ8155 Connection limit exceeded.
Response: Remove the DFTSHARE parameter from
Severity: 40 : Stop Error the command or, if the command is CRTMQMQ,
Explanation: The queue manager connection limit has
command again.
been exceeded.
Response: The maximum limit on the number of
AMQ8161 (iSeries) AUT(*MQMPASSID) only
WebSphere MQ application programs that may be
allowed with OBJTYPE(*ADM).
connected to the queue manager has been exceeded.
Try the command later. Severity: 40 : Stop Error
Explanation: AUT(*MQMPASSID) may only be
AMQ8156 WebSphere MQ queue manager specified with OBJTYPE(*ADM).
quiescing.
Response: Change the AUT parameter to specify
Severity: 40 : Stop Error another value and then try the command again.
Explanation: The queue manager is quiescing.
AMQ8162 (iSeries) AUT(*MQMPASSALL) only
Response: The queue manager was stopping with -c
specified for endmqm. Wait until the queue manager
has been restarted and then try the command again. Severity: 40 : Stop Error
Explanation: AUT(*MQMPASSALL) may only be
AMQ8157 Security error. specified with OBJTYPE(*ADM).
Severity: 40 : Stop Error Response: Change the AUT parameter to specify
another value and then try the command again.
Explanation: An error was reported by the security
manager program.
Response: Inform your systems administrator, wait

AMQ8163 (iSeries) AUT(*MQMSETID) only allowed AMQ8168 (iSeries) User profile name for parameter
with OBJTYPE(*ADM). USER not found.
Severity: 40 : Stop Error Severity: 30 : Severe error
Explanation: AUT(*MQMSETID) may only be Explanation: The user profile name specified for
specified with OBJTYPE(*ADM). parameter USER could not be found on the system, and
is not the special value *PUBLIC.
another value and then try the command again. Response: Correct the user profile name, or use the
Create User Profile (CRTUSRPRF) command to create
the user profile then try the request again.
AMQ8164 (iSeries) AUT(*MQMSETALL) only
AMQ8169 (iSeries) Authorization list for parameter
AUTL does not exist.
Explanation: AUT(*MQMSETALL) may only be
specified with OBJTYPE(*ADM).
Explanation: The authorization list specified for
parameter AUTL does not exist. It may have been
destroyed.
Response: Either specify an authorization list that
AMQ8165 (iSeries) AUT(*MQMALTUSR) only
exists, or create the authorization list using the Create
Authorization List (CRTAUTL) command. Try the
Severity: 40 : Stop Error request again.
Explanation: AUT(*MQMALTUSR) may only be
specified with OBJTYPE(*ADM). AMQ8170 (iSeries) REFOBJTYPE(*OBJTYPE) and
OBJTYPE(*ALL) cannot be used
Response: Change the AUT parameter to specify together.
AMQ8166 (iSeries) WebSphere MQ reference object Explanation: REFOBJTYPE(*OBJTYPE) can be
not found. specified only with a specific object type.
Severity: 40 : Stop Error Response: Change the REFOBJTYPE or OBJTYPE
input value to a specific object type. Then try the Grant
Explanation: The object specified by the REFOBJ and Authority (GRTMQMAUT) command again.
REFOBJTYPE parameters does not exist.
Response: Correct the reference object name and type, AMQ8171 (iSeries) Authority of *AUTL is only
and then try the command again. allowed with USER(*PUBLIC).
AMQ8167 (iSeries) Referenced object name not
valid. Explanation: AUT(*AUTL) was specified on either the
Grant Authority (GRTMQMAUT) command or the
Severity: 30 : Severe error Revoke Authority (RVKMQMAUT) command with the
Explanation: The referenced object name specified in USER parameter not set to *PUBLIC. Only the
REFOBJ is not valid. The length of the name must not authority for *PUBLIC can be deferred to the
exceed 48 characters and the name should contain the authorization list.
following characters only: lowercase a-z, uppercase Response: Change the AUT parameter to the
A-Z, numeric 0-9, period (.), forward slash (/), authorities that are correct for the users or change the
underscore (_) and percent sign (%). USER parameter to *PUBLIC. Then try the command
Response: Change the length of the parameter value again.
or change the parameter value to contain a valid
combination of characters. Then try the command AMQ8172 Already disconnected.
again.
Explanation: The MQI reason code of 2018 was
returned from the WebSphere MQ queue manager in
response to an MQDISC request issued during
command processing.

Response: None.
AMQ8180 (iSeries) WebSphere MQ trace end request
failed.
AMQ8173 No processes to display.
Explanation: Your request to end the trace was not
Explanation: There are no matching processes defined successful.
on this system.
Response: None.
Response: Using the DEFINE PROCESS command to
create a process.
AMQ8181 (iSeries) No jobs to display.
AMQ8174 No queues to display.
Explanation: There are no matching jobs running on
this system.
Explanation: There are no matching queues defined
Response: Specify another job name from the
on this system.
STRMQMSRV command.
Response: Use the appropriate command to define a
queue of the type that you require, that is, DEFINE
AMQ8182 (iSeries) WebSphere MQ trace already off.
QALIAS, DEFINE QLOCAL, DEFINE QMODEL, or
DEFINE QREMOTE. Severity: 10 : Warning
Explanation: An attempt was made to set trace off,
AMQ8175 (iSeries) WebSphere MQ trace has started. but the trace is not active.
Explanation: The trace has started successfully.
AMQ8183 (iSeries) WebSphere MQ trace already
Response: None.
running.
AMQ8176 (iSeries) WebSphere MQ trace has been
written. Explanation: An attempt was made to start trace, but
trace is already running.
Response: Either leave trace running as it is, or, if you
Explanation: The trace has been written successfully.
want to change the trace settings, turn trace off and
Response: None. then turn it on again with appropriate settings.
AMQ8177 (iSeries) WebSphere MQ trace has AMQ8184 (iSeries) Requested job cannot be found
stopped.
Explanation: The job specified cannot be found in the
Explanation: The trace has stopped. table that controls WebSphere MQ for iSeries trace. As
a result no trace action can be performed.
Response: None.
Response: Specify an appropriate job name.
AMQ8178 (iSeries) WebSphere MQ trace did not
start. AMQ8185 Operating system object already exists.
Explanation: The trace did not start successfully. Explanation: The WebSphere MQ object cannot be
created because an object that is not known to MQ
Response: None. already exists in the MQ directory with the name that
should be used for the new object. Refer to the log for
AMQ8179 (iSeries) WebSphere MQ trace output previous messages.
error. Response: Remove the non-MQ object from the MQ
Severity: 40 : Stop Error library, and try the command again.
Explanation: The trace was not output successfully.

Response: None.

Response: Examine the log for details of the errors
AMQ8186 Image not available for WebSphere MQ
encountered, and take appropriate action.
object <insert_5>.
AMQ8191 WebSphere MQ command server is
Explanation: The object <insert_5> type <insert_3> starting.
cannot be recreated because the image is not fully
available in the logs that are currently online. Refer to
earlier messages in the error log for information about Explanation: The command server is starting.
the logs that need to be brought online for this object to
be recreated. Response: Wait for the strmqcsv command to
complete and then try the operation again.
Response: Bring the relevant logs online, and try the
command again.
AMQ8191 (iSeries) WebSphere MQ command server
is starting.
AMQ8187 WebSphere MQ object <insert_5> is
currently open. Severity: 40 : Stop Error
Severity: 40 : Stop Error Explanation: The command server is starting.
Explanation: The object <insert_5>, type <insert_3>, is Response: Wait for the STRMQMCSVR command to
currently in use, so the <insert_1> command cannot be complete and then try the operation again.
issued against it. If a generic list was presented to the
command, the command is still issued against the other AMQ8192 WebSphere MQ command server
objects in the list. already starting.
Response: Wait until the object is no longer in use, Severity: 40 : Stop Error
and try the command again.
Explanation: The request to start the command server
was unsuccessful because the command server is
AMQ8188 Insufficient authorization to WebSphere already starting.
MQ object <insert_5>.
Response: Wait for the strmqcsv command to
Severity: 40 : Stop Error complete.
Explanation: You are not authorized to issue the
<insert_1> command against the object <insert_5> type AMQ8192 (iSeries) WebSphere MQ command server
<insert_3>. If a generic list was presented to the already starting.
command, the command is still issued against the other
objects in the list. Severity: 40 : Stop Error
Response: Obtain sufficient authorization for the Explanation: The request to start the command server
object, and retry the command. was unsuccessful because the command server is
already starting.
AMQ8189 WebSphere MQ object <insert_5> is Response: Wait for the STRMQMCSVR command to
damaged. complete.

AMQ8193 WebSphere MQ command server is
Explanation: The object <insert_5> type <insert_4> is ending.
damaged and the <insert_3> command cannot be
issued against it. If a generic list was presented to the Severity: 40 : Stop Error
command then the command is still issued against the Explanation: The command server is ending.
other objects in the list.
Response: Wait for the endmqcsv command to
Response: Issue the appropriate DEFINE command complete and then try the command again.
for the object, specifying REPLACE, and then try the
command again.
is ending.
AMQ8190 <insert_3> succeeded on <insert_1>
objects and failed on <insert_2> objects. Severity: 40 : Stop Error
Severity: 40 : Stop Error Explanation: The command server is ending.
Explanation: An operation performed on a generic list Response: Wait for the ENDMQMCSVR command to
of objects was not completely successful. complete and then try the command again.

Response: None.
already ending.
AMQ8198 (iSeries) Program <insert_3> called with
incorrect number of parameters.
Explanation: The end command server request was
unsuccessful because the command server is already
ending. Explanation: The number of parameters passed in the
call to program <insert_3> is not correct.
Response: Wait for the endmqcsv command to
complete. Response: Correct the calling program and then retry
the operation.
already ending. AMQ8199 (iSeries) Error in call identifier parameter
passed to program QMQM.
Explanation: The end command server request was
unsuccessful because the command server is already Explanation: The call identifier, the first parameter
ending. passed to program QMQM, is not in the required
packed decimal format, or its value is not supported.
Response: Wait for the ENDMQMCSVR command to
Permitted values of the call identifier are contained in
complete.
the RPG copy file CMQR.
Response: Correct the calling program, and retry the
call.
already running.
AMQ8200 (iSeries) MODENAME only allowed with
Explanation: The strmqcsv command was TRPTYPE(*LU62).
unsuccessful because the command server is already
running.
Explanation: The MODENAME parameter may only
Response: None.
be specified with TRPTYPE(*LU62).
Response: Remove the MODENAME parameter from
the command or change the TRPTYPE parameter value
already running.
to specify *LU62 and then try the command again.
Explanation: The STRMQMCSVR command was AMQ8201 (iSeries) TPGMNAME only allowed with
unsuccessful because the command server is already TRPTYPE(*LU62).
running.
Response: None.
Explanation: The TPGMNAME parameter may only
Response: Remove the TPGMNAME parameter from
already stopped.
Severity: 40 : Stop Error to specify *LU62. Then try the command again.
Explanation: The request to end the command server
was unsuccessful because the command server is AMQ8202 TMQNAME only allowed with channel
already stopped. type *SDR or *SVR.
Response: None. Severity: 40 : Stop Error
Explanation: The TMQNAME parameter may only be
AMQ8197 Deleted WebSphere MQ queue specified with channel type *SDR or *SVR.
damaged.
Response: Remove the TMQNAME parameter from
Severity: 20 : Error the command or, if the command is CRTMQMCHL,
change the CHLTYPE parameter value to specify *SDR
Explanation: The deleted MQ queue <insert_5> was
or *SVR. Then try the command again.
damaged, and any messages it contained have been
lost.

AMQ8203 (iSeries) CONNAME only allowed with AMQ8207 SHORTTMR only allowed with channel
channel type *SDR, *SVR, *RQSTR, type *CLUSSDR, CLUSRCVR, *SDR or
*CLUSSDR, *CLTCN and *CLUSRCVR *SVR.
Explanation: The CONNAME parameter may only be Explanation: The SHORTTMR parameter may only be
specified with channel type *SDR, *SVR, *RQSTR, specified with channel type *CLUSSDR, *CLUSRCVR,
*CLUSSDR, *CLTCN or *CLUSRCVR. *SDR or *SVR.
Response: Remove the CONNAME parameter from Response: Remove the SHORTTMR parameter from
the command or, if the command is CRTMQMCHL, the command or, if the command is CRTMQMCHL,
change the CHLTYPE parameter value to specify *SDR, change the CHLTYPE parameter value to specify
*SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR. *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the
Then try the command again. command again.
AMQ8204 MCANAME only allowed with channel AMQ8208 LONGRTY only allowed with channel
type *SDR, *SVR, or *RQSTR. type *CLUSSDR, *CLUSRCVR, *SDR or
*SVR.
Explanation: The MCANAME parameter may only be
specified with channel type *SDR, *SVR, or *RQSTR. Explanation: The LONGRTY parameter may only be
specified with channel type *CLUSSDR, *CLUSRCVR,
Response: Remove the MCANAME parameter from
*SDR or *SVR.
change the CHLTYPE parameter value to specify *SDR, Response: Remove the LONGRTY parameter from the
*SVR, or *RQSTR. Then try the command again. command or, if the command is CRTMQMCHL, change
the CHLTYPE parameter value to specify *CLUSSDR,
CLUSRCVR, *SDR or *SVR. Then try the command
AMQ8205 DSCITV only allowed with channel
again.
type *CLUSSDR, *CLUSRCVR,
*SVRCN, *SDR or *SVR.
AMQ8209 LONGTMR only allowed with channel
type *CLUSSDR, *CLUSRCVR, *SDR or
Explanation: The DSCITV parameter may only be *SVR.
*SVRCN, *SDR or *SVR.
Explanation: The LONGTMR parameter may only be
Response: Remove the DSCITV parameter from the
command or, if the command is CRTMQMCHL, change
*SDR or *SVR.
the CHLTYPE parameter value to specify *CLUSSDR,
*CLUSRCVR, *SVRCN, *SDR or *SVR. Then try the Response: Remove the LONGTMR parameter from
command again. the command or, if the command is CRTMQMCHL,
change the CHLTYPE parameter value to specify
*CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the
AMQ8206 SHORTRTY only allowed with channel
command again.
type *CLUSSDR, CLUSRCVR, *SDR or
*SVR.
AMQ8210 PUTAUT only allowed with channel
type *RCVR or RQSTR.
Explanation: The SHORTRTY parameter may only be
*SDR or *SVR. Explanation: The PUTAUT parameter may only be
specified with channel type *RCVR or RQSTR.
Response: Remove the SHORTRTY parameter from
the command or, if the command is CRTMQMCHL, Response: Remove the PUTAUT parameter from the
change the CHLTYPE parameter value to specify command or, if the command is CRTMQMCHL, change
*CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the the CHLTYPE parameter value to specify *RCVR or
command again. RQSTR. Then try the command again.

the CHLTYPE parameter value to specify *SDR, *SVR,
AMQ8211 BATCHINT only allowed with channel
*CLUSSDR or CLUSRCVR. Then try the command
type *SDR or *SVR.
again.
Explanation: The BATCHINT parameter may only be AMQ8216 (iSeries) MODENAME only allowed with
specified with channel type *SDR or *SVR. TRPTYPE(*LU62).
Response: Remove the BATCHINT parameter from Severity: 40 : Stop Error
Explanation: The MODENAME parameter may only
change the CHLTYPE parameter value to specify *SDR
or *SVR. Then try the command again.
Response: Remove the MODENAME parameter from
AMQ8212 (iSeries) TPGMNAME parameter required
to specify *LU62. Then try the command again.
with TRPTYPE(*LU62).
AMQ8217 (iSeries) CONNAME only allowed with
Explanation: A required parameter was not specified. channel type *SDR, *SVR, *RQSTR,
*CLUSSDR or CLUSRCVR.
Response: Enter a value for parameter TPGMNAME.
AMQ8213 (iSeries) TMQNAME parameter required Explanation: The CONNAME parameter may only be
with channel type *SDR or *SVR. specified with channel type *SDR, *SVR, *RQSTR,
CLUSSDR or CLUSRCVR.
Response: Remove the CONNAME parameter from
Explanation: The TMQNAME parameter must be
specified with channel type *SDR or *SVR.
change the CHLTYPE parameter value to specify *SDR,
Response: Enter a value for parameter TMQNAME. *SVR, *RQSTR, CLUSSDR or CLUSRCVR. Then try the
command again.
AMQ8214 CONNAME parameter missing.
AMQ8218 The system cannot accept the
Severity: 40 : Stop Error combination of parameters entered.
Explanation: The CONNAME parameter must be Severity: 30 : Severe error
specified with channel types SDR, RQSTR,
CLNTCONN, and CLUSSDR. It is also required with
channel type CLUSRCVR if the TRPTYPE is not TCP. AMQ8219 Command server queue is open, retry
later.
Response: Enter a value for parameter CONNAME.
AMQ8214 (iSeries) CONNAME parameter missing. Response: Wait and try again later.
AMQ8220 (iSeries) The PNGMQMCHL command
Explanation: The CONNAME parameter must be has completed.
specified with channel types *SDR, *RQSTR, and
*CLUSSDR. It is also required with channel type Severity: 0 : Information
*CLUSRCVR if the TRPTYPE is not *TCP.
Explanation: The PNGMQMCHL command sent
Response: Enter a value for parameter CONNAME. <insert_1> bytes of data to <insert_3> and received the
data back in <insert_4>.<insert_5> seconds. The number
of bytes will be less than the amount requested on the
AMQ8215 (iSeries) CVTMSG only allowed with command, when the length requested is greater than
channel type *SDR, *SVR, *CLUSSDR the allowed maximum, in one communications
or *CLUSRCVR. transmission, for the operating system and
Severity: 40 : Stop Error communications protocol.
Explanation: The CVTMSG parameter may only be Response: None.

specified with channel type *SDR, *SVR, *CLUSSDR or
*CLUSRCVR.
Response: Remove the CVTMSG parameter from the

channel and then try the command again.
AMQ8221 (iSeries) Ping data length truncated,
specified length <insert_1>, actual length
<insert_2>. AMQ8227 Channel <insert_3> not found.
Severity: 10 : Warning Severity: 30 : Severe error
Explanation: The length of the ping data sent was Explanation: The channel could not be found.
reduced because of constraints in the current
configuration. Response: Correct the Channel Name if wrong and
then try the command again. For DEFINE CHANNEL
Response: None. check that the Channel Name in error exists.
AMQ8222 (iSeries) The data sent and received by the AMQ8228 (iSeries) Unexpected return code
PNGMQMCHL command was not <insert_1>.
identical.
Explanation: The unexpected return code <insert_1>
Explanation: Ping data compare failed at offset was returned to a channel command.
<insert_1>, data sent <insert_3>, data received
<insert_4>. Response: This message is associated with an internal
error. Use WRKPRB to record the problem identifier,
Response: This is probably due to a communications and to save the QPSRVDMP, QPJOBLOG, and
failure. Other messages may have been issued. QPDSPJOB files. Contact your IBM support center. Do
not discard these files until the problem has been
resolved.
AMQ8223 (iSeries) No channels to display.
AMQ8229 (iSeries) No message queue managers to
Explanation: There are no channels defined on this display.
system.
Response: Create a channel using the CRTMQMCHL
Explanation: There are no message queue managers to
command.
administer.
Response: Add a queue manager using PF6 or the
AMQ8224 (iSeries) From channel <insert_3> not
ADMQMNAM command.
found.
AMQ8230 (iSeries) No queue manager objects to
Explanation: The source WebSphere MQ channel does display.
not exist.
Response: Correct the MQ channel name and then try
Explanation: Either the queue manager has no objects
the command again.
to display (this is unlikely), or the selection criteria
resulted in zero objects to display.
AMQ8225 (iSeries) From channel and to channel
Response: Change or remove the selection criteria.
names are equal.
AMQ8231 (iSeries) No responses to display.
Explanation: The same name has been specified for
the from channel name and the to channel name.
Explanation: There are no commands or command
Response: Choose two different names, of which the
responses to display.
from channel must exist.
Response: None.
AMQ8226 WebSphere MQ channel already exists.
AMQ8232 (iSeries) No messages to display.
Explanation: The channel <insert_3> cannot be created
because it already exists. Explanation: The queue is empty, or the queue does
not exist.
Response: Check that the name is correct and try the
command again specifying REPLACE, or delete the Response: None.

then issue the MQCONN call to connect to the new
AMQ8233 (iSeries) No message data to display.
queue manager. Disconnecting from the existing queue
Severity: 0 : Information manager will close any queues which are currently
open, it is recommended that any uncommitted units of
Explanation: The message contains no data.
work should be committed or backed out before the
Response: None. MQDISC call is used.
AMQ8234 (iSeries) No response data to display. AMQ8239 (iSeries) LOCLADDR not valid for
channel type *RCVR or *SVRCN.
Explanation: There is no response data to display for
this command. This is probably because the command Explanation: The LOCLADDR parameter may only be
has not yet completed. specified with channel type *SDR, *SVR, *RQSTR,
*CLUSSDR, *CLUSRCVR or *CLTCN.
Response: None.
AMQ8235 (iSeries) No command parameters to change the CHLTYPE parameter value to specify *SDR,
display. *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN.
Severity: 0 : Information Then try the command again.
Explanation: Some commands have no required

parameters. AMQ8240 (iSeries) Unexpected error <insert_1> in
<insert_3>.
Response: None.
AMQ8236 (iSeries) Channel <insert_3> not found. Explanation: The unexpected return code <insert_1>
was returned during <insert_3> processing.
Response: This message is associated with an internal
Explanation: CHGMQMCHL was issued for a error. Use WRKPRB to record the problem identifier,
non-existent channel. and to save the QPSRVDMP, QPJOBLOG, and
Response: Correct the WebSphere MQ channel name QPDSPJOB files. Contact your IBM support center. Do
and then try the command again. not discard these files until the problem has been
resolved.
AMQ8237 (iSeries) NPMSPEED only allowed with

channel type *SDR, *SVR, *RCVR AMQ8241 (iSeries) Unexpected message format
*RQSTR, CLUSSDR or CLUSRCVR. <insert_3> received.
Explanation: The NPMSPEED parameter may only be Explanation: The unexpected message format
specified with channel type *SDR, *SVR, *RCVR <insert_3> was received in message on the internal
*RQSTR, CLUSSDR or CLUSRCVR. reply queue.
Response: Remove the NPMSPEED parameter from Response: This message is probably a message sent
the command or, if the command is CRTMQMCHL, erroneously to this queue. The message in error is
change the CHLTYPE parameter value to specify *SDR, written to the SYSTEM.ADMIN.EXCEPTION.QUEUE,
*SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then where it may be viewed using the WRKMQMMSG
try the command again. command.
AMQ8238 (iSeries) Queue manager connection AMQ8242 SSLCIPH definition wrong.

already open. Severity: 40 : Stop Error
Severity: 30 : Severe error Explanation: The definition of the SSLCIPH parameter
Explanation: An MQCONN call was issued, but the was wrong.
thread or process is already connected to a different Response: Correct the SSLCIPH definition and try the
queue manager. The thread or process can connect to command again.
only one queue manager at a time.
Response: Use the MQDISC call to disconnect from
the queue manager which is already connected, and

Response: Check the name of the queue and retry the
AMQ8243 SSLPEER definition wrong.
operation. If you are attempting to display a queue of
Severity: 40 : Stop Error type *ALS, check the queue definition references an
existing queue definition.
Explanation: The definition of the SSLPEER parameter
was wrong. Possible causes may be that the syntax was
invalid or that it contained an invalid attribute type. AMQ8282 (iSeries) Queue manager <insert_3> is not
defined on the connected queue
Response: Correct the SSLPEER definition and try the
manager.
command again.
AMQ8266 (iSeries) No objects to display. Explanation: Either the necessary queue manager
name has been entered incorrectly on the add queue
manager panel, or the queue manager has not been
Explanation: There are no objects with the specified defined on the connected queue manager.
name and type.
Response: Correct the name, or define <insert_3> on
Response: None. the connected queue manager by creating a local queue
with name <insert_3> and usage *TMQ (transmission
queue), and then creating sender and receiver channels
AMQ8276 Display Connection details. on both the connected queue manager and queue
Severity: 0 : Information manager <insert_3>.
Explanation: The DISPLAY CONN command

completed successfully. Details follow this message. AMQ8283 (iSeries) The administration application
data store program failed to start.
AMQ8277 (iSeries) Object changed. Severity: 40 : Stop Error
Severity: 40 : Stop Error Explanation: The program AMQMCPRA (data store

program) was not started because of reason code
Explanation: The definition of WebSphere MQ object <insert_1>.
<insert_5> changed after it had been opened, thereby
invalidating the open operation. Response: Check the joblog for AMQMCPRA by
issuing a WRKSPLF QMQM. Correct the problem and
Response: Try the command again. try to start the Administration application by invoking
the STRMQMADM command. If the problem persists
AMQ8278 (iSeries) Maximum handle limit reached. contact your systems programmer.

AMQ8284 (iSeries) This user is not authorized to
Explanation: An attempt was made to exceed the queue <insert_3>.
maximum handle limit specified for the message queue
manager. Severity: 40 : Stop Error
Response: Increase the maximum handle limit Explanation: Queue <insert_3> (queue manager
specified for the message queue manager using the <insert_4>) has not been authorized for your use.
CHGMQM command. Then try the command again. Response: Have queue <insert_3> authorized for your
use. If queue manager <insert_4> is not the local queue
AMQ8279 (iSeries) Option not valid for type. manager, you might not be authorized to the
transmission queue for this queue manager.
Explanation: The options specified when opening AMQ8287 No channels with status to display.
WebSphere MQ object <insert_5> were not valid for the
object type. Severity: 0 : Information
Response: Correct the definition of the failing object. Explanation: There are no channels having status
Then try the command again. information to display. This indicates either, that the
channel has not been started previously, or, that the
channel has been started but has not yet completed a
AMQ8280 (iSeries) Queue does not exist. transmission sequence.
Severity: 30 : Severe error Response: None.
Explanation: The queue being displayed does not
exist on this queue manager.

AMQ8288 (iSeries) Not authorized to command AMQ8296 <insert_1> MQSC commands completed
<insert_1> successfully.
Explanation: You are not authorized to perform the Explanation: The <insert_3> command has completed
requested operation for WebSphere MQ command successfully. The <insert_1> MQ commands from
<insert_1>. <insert_5> have been processed without error and a
report written to the printer spool file.
Response: Obtain the necessary authority from your
WebSphere MQ administrator. Then try the command Response: None.
again.
AMQ8297 <insert_1> MQSC commands verified
AMQ8289 (iSeries) You are not authorized to the successfully.
WebSphere MQ command.
Explanation: The <insert_3> command completed
Explanation: You are not authorized to the WebSphere successfully. The <insert_1> MQ commands from
MQ command because your user profile is not a <insert_5> have been verified and a report written to
member of the QMQMADM group. the printer spool file.
Response: Ask your MQ administrator to give your Response: None.
user profile *ALLOBJ authority, or add your user
profile to the QMQMADM group (either as a primary
AMQ8298 Error report generated for MQSC
or supplemental group)
command process.
AMQ8291 (iSeries) WebSphere MQ remote trace
already running. Explanation: The <insert_3> command attempted to
process a sequence of MQ commands and encountered
some errors, however, the operation may have partially
Explanation: An attempt was made to start remote completed.
trace, but it is already running.
Response: If the STRMQMMQSC command was
Response: Either leave remote trace running as it is, executed a report has been written to a printer spool
or, if you want to change the settings, turn remote trace file. Examine the spooled printer file for details of the
off and then turn it on again with appropriate settings. errors encountered and correct the MQSC source
<insert_5> and retry the operation.
AMQ8294 (iSeries) WebSphere MQ remote trace
already off. AMQ8299 Cannot open <insert_5> for MQSC
process.
Explanation: An attempt was made to end remote
trace, but it is already off. Explanation: The <insert_1> command failed to open
<insert_5> for MQ command processing.
Response: Leave remote trace off.
Response: Check that the intended file exists, and has
been specified correctly. Correct the specification or
AMQ8295 (iSeries) WebSphere MQ object not
create the object, and try the operation again.
secured by authorization list.
AMQ8300 (iSeries) Too many exit programs/user data
Explanation: The specified object is not secured by the fields defined.
authorization list to be revoked from it.
Response: Use the display authority (DSPMQMAUT)
Explanation: An attempt was made to create or
command to determine what authorization list is
change a channel which had more than the allowed
securing the object, if any. Issue the RVKMQMAUT
maximum of a total of six exit programs and/or user
command again with the authorization list that is
data fields defined.
securing the the object to revoke the authorization list’s
authority. Response: Re-define the channel so that a total of six
exit programs and/or user data fields are defined.

*SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then
AMQ8301 (iSeries) WebSphere MQ storage monitor
job could not be started.
Severity: 50 : System Error
AMQ8307 (iSeries) SEQNUMWRAP only allowed
Explanation: An attempt to start the storage monitor with channel type *SDR, *SVR, *RCVR
process (job QMQM in subsystem QSYSWRK) was , *RQSTR, CLUSSDR or CLUSRCVR.
unsuccessful.
Response: Check the job log for the reason for the
Explanation: The SEQNUMWRAP parameter may
failure, and try the command again.
only be specified with channel type *SDR, *SVR,
*RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
AMQ8302 Internal failure initializing WebSphere
Response: Remove the SEQNUMWRAP parameter
MQ services.
from the command or, if the command is
Severity: 50 : System Error CRTMQMCHL, change the CHLTYPE parameter value
to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or
Explanation: An error occurred while attempting to
CLUSRCVR. Then try the command again.
initialize WebSphere MQ services.
Response: A call to xcsInitialize ended with the FAIL,
AMQ8308 (iSeries) MSGRTYEXIT only allowed with
STOP, or STOP_ALL return code. Refer to the log for
channel type *CLUSRCVR, *RCVR or
messages diagnosing this problem.
*RQSTR.
AMQ8303 Insufficient storage available to process
request. Explanation: The MSGRTYEXIT parameter may only
be specified with channel type *CLUSRCVR, *RCVR or
Severity: 50 : System Error
*RQSTR.
Response: Remove the MSGRTYEXIT parameter from
AMQ8304 Tracing cannot be started. Too many
traces are already running.
Severity: 40 : Stop Error *CLUSRCVR, *RCVR or *RQSTR. Then try the
command again.
Explanation: A maximum of 9 traces may be running
concurrently. This number is already running.
AMQ8309 (iSeries) MSGRTYDATA only allowed
Response: Stop one or more of the other traces and with channel type *CLUSRCVR, *RCVR
try the command again. or *RQSTR.
AMQ8305 Tracing cannot be started. Too many
traces are already running. Explanation: The MSGRTYDATA parameter may only
be specified with channel type *CLUSRCVR, *RCVR or
Severity: 40 : Stop Error *RQSTR.
Explanation: A maximum of 9 traces can be running Response: Remove the MSGRTYDATA parameter
concurrently, and this number of traces is already from the command or, if the command is
running. CRTMQMCHL, change the CHLTYPE parameter value
Response: Stop one or more of the other traces and to specify *CLUSRCVR, *RCVR or *RQSTR. Then try
try the command again. the command again.
AMQ8306 (iSeries) BATCHSIZE only allowed with AMQ8310 (iSeries) MSGRTYNBR only allowed with
channel type *SDR, *SVR, *RCVR, channel type *CLUSRCVR, *RCVR or
*RQSTR, CLUSSDR or CLUSRCVR. *RQSTR.
Explanation: The BATCHSIZE parameter may only be Explanation: The MSGRTYNBR parameter may only
specified with channel type *SDR, *SVR, *RCVR, be specified with channel type *CLUSRCVR, *RCVR or
*RQSTR, CLUSSDR or CLUSRCVR. *RQSTR.
Response: Remove the BATCHSIZE parameter from Response: Remove the MSGRTYNBR parameter from
the command or, if the command is CRTMQMCHL, the command or, if the command is CRTMQMCHL,
change the CHLTYPE parameter value to specify *SDR, change the CHLTYPE parameter value to specify

*CLUSRCVR, *RCVR or *RQSTR. Then try the Response: Use the Create Namelist (CRTMQMNL)
command again. command to create a namelist.
AMQ8311 (iSeries) MSGRTYITV only allowed with AMQ8316 No cluster queue managers to display.
channel type *CLUSRCVR, *RCVR or
*RQSTR.
Explanation: There are no matching cluster queue
managers defined on this system.
Explanation: The MSGRTYITV parameter may only be
Response: None.
specified with channel type *CLUSRCVR, *RCVR or
*RQSTR.
AMQ8317 (iSeries) CLUSTER only allowed with
Response: Remove the MSGRTYITV parameter from
channel type *CLUSSDR and
*CLUSRCVR.
*CLUSRCVR, *RCVR or *RQSTR. Then try the Severity: 40 : Stop Error
command again.
Explanation: The CLUSTER parameter may only be
specified with channel type *CLUSSDR and
AMQ8312 (iSeries) CLUSTER only allowed with *CLUSRCVR.
queue type *ALS, *LCL and *RMT.
Response: Remove the CLUSTER parameter from the
Severity: 40 : Stop Error command or, if the command is CRTMQMCHL, change
the CHLTYPE parameter value to specify *CLUSSDR or
Explanation: The CLUSTER parameter may only be
*CLUSRCVR. Then try the command again.
specified with queue type *ALS, *LCL and *RMT.
Response: Remove the CLUSTER parameter from the
AMQ8318 (iSeries) CLUSNL only allowed with
command or, if the command is CRTMQMQ, change
channel type *CLUSSDR and
the QTYPE parameter value to specify *ALS, *LCL or
*CLUSRCVR.
*RMT. Then try the command again.
AMQ8313 (iSeries) CLUSNL only allowed with Explanation: The CLUSNL parameter may only be
queue type *ALS, *LCL and *RMT. specified with channel type *CLUSSDR and
*CLUSRCVR.
Response: Remove the CLUSNL parameter from the
Explanation: The CLUSNL parameter may only be
the CHLQTYPE parameter value to specify *CLUSSDR
Response: Remove the CLUSNL parameter from the or *CLUSRCVR. Then try the command again.
command or, if the command is CRTMQMQ, change
the QTYPE parameter value to specify *ALS, *LCL or
AMQ8319 MSGEXIT only allowed with channel
*RMT. Then try the command again.
type *SDR, *SVR, *RCVR *RQSTR,
*CLUSSDR or *CLUSRCVR.
AMQ8314 (iSeries) DEFBIND only allowed with
queue type *ALS, *LCL and *RMT.
Explanation: The MSGEXIT parameter may only be
specified with channel type *SDR, *SVR, *RCVR,
Explanation: The DEFBIND parameter may only be *RQSTR, *CLUSSDR, or *CLUSRCVR.
Response: Remove the MSGEXIT parameter from the
Response: Remove the DEFBIND parameter from the command or, if the command is CRTMQMCHL, change
command or, if the command is CRTMQMQ, change the CHLTYPE parameter value to specify *SDR or *SVR
the QTYPE parameter value to specify *ALS, *LCL or or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR.
*RMT. Then try the command again. Then try the command again.
AMQ8315 No namelists to display. AMQ8320 (iSeries) MSGUSRDATA only allowed

with channel type *SDR, *SVR, *RCVR
*RQSTR, or *CLUSSDR or
Explanation: There are no matching namelists defined *CLUSRCVR.
on this system.

Explanation: The MSGUSRDATA parameter may only
AMQ8325 (iSeries) MQMNAME(*ALL) is not
be specified with channel type *SDR, *SVR, *RCVR
allowed with ENDCCTJOB(*NO).
*RQSTR, *CLUSSDR or *CLUSRCVR.
Response: Remove the MSGUSRDATA parameter
from the command or, if the command is Explanation: The MQMNAME(*ALL) parameter is
CRTMQMCHL, change the CHLTYPE parameter value only allowed when performing a full shutdown of the
to specify *SDR or *SVR or *RCVR or *RQSTR or queue managers.
*CLUSSDR or *CLUSRCVR. Then try the command
Response: Specify individual queue manager names
again.
to shut the queue managers down one-by-one or
change the ENDCCTJOB parameter to *YES. Then try
AMQ8321 (iSeries) Process <insert_3> is still the command again.
running.
Severity: 0 : Information AMQ8330 Running
AMQ8322 (iSeries) TIMEOUT only allowed with
ENDCCTJOB(*YES).
AMQ8331 Ended normally
Explanation: The TIMEOUT parameter may only be
specified when connected jobs are being ended with the
AMQ8332 Ended immediately
ENDCCTJOB option set to *YES.
Response: Remove the TIMEOUT parameter from the
command or, if you want to fully quiesce the queue
manager, change the ENDCCTJOB parameter to *YES. AMQ8333 Ended preemptively
Then try the command again.
AMQ8323 (iSeries) OPTION(*PREEMPT) must not

be used with ENDCCTJOB(*YES). AMQ8334 Ended unexpectedly
Explanation: When performing a pre-emptive

shutdown of the queue manager the AMQ8335 Starting
ENDCCTJOB(*YES) parameter is not allowed. Severity: 0 : Information
Response: Change the ENDCCTJOB(*YES) parameter
to ENDCCTJOB(*NO) or, if you want to fully quiesce AMQ8336 Quiescing
the queue manager without doing a pre-emptive
shutdown, change the OPTION(*PREEMPT) parameter Severity: 0 : Information
to another value. Then try the command again.
AMQ8337 Ending immediately
AMQ8324 (iSeries) OPTION(*WAIT) not allowed Severity: 0 : Information
with MQMNAME(*ALL).
Severity: 40 : Stop Error AMQ8338 Ending preemptively
Explanation: The OPTION(*WAIT) parameter is not Severity: 0 : Information
allowed when performing a shutdown of all queue
managers.
AMQ8339 Being deleted
Response: Remove the OPTION(*WAIT) parameter
from the command or, specify individual queue Severity: 0 : Information
manager names to shut down the queue managers
one-by-one with the OPTION(*WAIT) parameter. Then AMQ8340 Not available

value for the Queue Manager Identifier for Removal
AMQ8341 SUBPOOL(<insert_3>)<insert_4>PID(<insert_1>)
(QMID) parameter.
Response: A value for QMID is not allowed unless
QMNAME is *QMID. Change the value specified on
AMQ8342 No authorities to display. the QMNAME parameter or the value of the QMID
parameter and then try the request again.
Explanation: There are no authority records defined
AMQ8347 (iSeries) USERID not valid for channel
on this system, satisfying the input parameters.
type *RCVR, *SVRCN or *CLUSRCVR.
Response: Use the appropriate input to list all the
authorities defined on the system, or enter the
command again with different input.. Explanation: The USERID parameter may only be
specified with channel type *SDR, *SVR, *RQSTR,
*CLUSSDR, or *CLTCN.
AMQ8343 (iSeries) The requested operation is not
valid for user QMQMADM. Response: Remove the USERID parameter from the
Explanation: You are not allowed to completely delete *RQSTR, *CLUSSDR, or *CLTCN. Then try the
the authorities assigned to user QMQMADM, for a command again.
valid WebSphere MQ object, with the authority
*REMOVE or *NONE.
AMQ8348 (iSeries) PASSWORD not valid for
Response: Remove QMQMADM from the list of users channel type *RCVR, *SVRCN or
to this command. *CLUSRCVR.
AMQ8344 (iSeries) The delete option is only valid
Explanation: The PASSWORD parameter may only be
for a generic profile name.
specified with channel type *SDR, *SVR, *RQSTR,
Severity: 0 : Information *CLUSSDR, or *CLTCN.
Explanation: The delete option, which will delete this Response: Remove the PASSWORD parameter from
authority profile by removing all the users from this the command or, if the command is CRTMQMCHL,
authority profile, is not valid for an object name or the change the CHLTYPE parameter value to specify *SDR,
special value &class. *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the
command again.
Response: To delete users from an object, work from
the WRKMQMAUTD command.
AMQ8349 (iSeries) Authority changes to <insert_5>
failed.
AMQ8345 (iSeries) BATCHHB not valid for channel
type *RCVR, *RQSTR, *SVRCN or Severity: 40 : Stop Error
*CLTCN.
Explanation: Authority changes to an object were
Severity: 40 : Stop Error requested but could not be made.
Explanation: The BATCHHB parameter may only be Response: Check the authorities that you are granting
specified with channel type *SDR, *SVR, *CLUSSDR, or are relevant to the object type of <insert_5>.
*CLUSRCVR.
Response: Remove the BATCHHB parameter from the AMQ8350 Usage: dspmqver [-p Components] [-f
command or, if the command is CRTMQMCHL, change Fields] [-b] [-v]
*CLUSSDR or *CLUSRCVR. Then try the command
again. Explanation: This shows the correct usage.
Response: None.
AMQ8346 (iSeries) Parameter mismatch between
QMNAME and QMID.
AMQ8359 QMNAME(<insert_3>)<insert_4>STATUS(Being
Severity: 40 : Stop Error deleted)
Explanation: The Queue Manager Name for Removal Severity: 0 : Information
(QMNAME) parameter is not *QMID and there is a

AMQ8370 Usage: runmqdnm -q Queue -a AMQ8375 WebSphere MQ queue manager
Assembly <insert_3> not available.
[-m QueueManager] [-c ClassName] [-u
Text] [-s Syncpoint]
[-n MaxThreads] [-t Timeout] [-b Explanation: The WebSphere MQ queue manager
BackoutThreshold] <insert_3> is not available because it has been stopped
[-r BackoutQueue] [-p Context] [-d] or is otherwise not contactable.
Severity: 0 : Information Response: Use the strmqm command to start the
message queue manager as necessary or correct any
intermittent problems (eg. network connectivity) then
Response: None. try the command again.
AMQ8371 <insert_3> is not a valid command line AMQ8376 WebSphere MQ queue <insert_3> not
option. found.
Explanation: The option <insert_3> was specified on Explanation: The queue <insert_3> could not be
the command line to the application however this is found, it may not have been created.
not one of the valid set of command line options.
Response: Ensure that the name of the queue
Response: Check the usage information for the specified is correct, queue names are case sensitive. If
application and then retry. the queue is not created, use the runmqsc command to
create it. Then try the command again.
AMQ8372 The required command line option
<insert_3> is missing. AMQ8377 Unexpected error <insert_1> was
received by the application.
Explanation: The application expects several
mandatory command line options. One of these, Explanation: The error <insert_1> was returned
<insert_3>, was not specified. unexpectedly to the application.
Response: Check the usage information for the Response: Save the generated output files and contact
application and ensure that all required parameters are your IBM support center.
specified then retry.
AMQ8378 Unexpected exception received from
AMQ8373 Invalid value specified for command .NET Framework
line option <insert_3> (<insert_4>). <insert_3>
Explanation: The value specified for command line Explanation: The application received an exception
option <insert_3> (<insert_4>) is invalid. from the underlying .NET framework, information
about the exception follows:
Response: Check the usage information for the
<insert_4>
application and ensure that all options specify values in
the valid range then retry. Response: Examine the information contained within
the exception to determine if it is possible to resolve
locally.
If it is not possible to resolve the problem locally, save
<insert_3> does not exist.
the generated output files and contact your IBM
Severity: 40 : Stop Error support center.
Explanation: The WebSphere MQ queue manager
<insert_3> does not exist. AMQ8379 Assembly <insert_3> could not be
loaded
Response: Either create the queue manager (crtmqm
command) or correct the queue manager name used in Severity: 40 : Stop Error
the command and then try the command again.
Explanation: The WebSphere MQ .NET Monitor
attempted to load assembly <insert_3> but received an
exception from the underlying .NET framework
indicating that it could not be found. <insert_4>

Response: Check that the assembly does exist and is
AMQ8383 A Message breaking the backout
accessible to the user running the application then retry.
threshold (<insert_1>) could not be
If the assembly should be available, contact your IBM
moved.
support center.
AMQ8380 No classes implementing Explanation: While processing queue <insert_3> a
IMQObjectTrigger found in <insert_3>. message whose backout count exceeded the specified
backout threshold (<insert_1>) was encountered
however, it was not possible to move it to either a
Explanation: The WebSphere MQ .NET monitor was backout queue or the dead-letter queue.
unable to identify any classes in referenced assembly
Response: Because it was not possible to move the
<insert_3> which implement the IMQObjectTrigger
backed out message to another queue, it has been left
interface.
on the input queue. As a result, the .NET monitor has
Response: It is a requirement of the WebSphere MQ ended.
.NET monitor that either a single class implementing It is possible that the backout queue or dead-letter
the IMQObjectTrigger interface exists in the referenced queue are full or disabled for put - in this case, resolve
assembly or that a class is identified in that assembly to this problem first.
execute. Either modify the assembly to include a single If backout processing should have resulted in the
class implementing IMQObjectTrigger or specify a class message being placed on another queue, check the
name on the command line and retry. command line options, input queue definition and
queue manager dead-letter queue attribute to ensure
that they are correct, then retry.
AMQ8381 Too many classes implementing
IMQObjectTrigger (<insert_1>) found in
<insert_3>. AMQ8390 Usage: endmqdnm -q Queue [-m
QueueManager]
Explanation: The WebSphere MQ .NET monitor found
<insert_1> classes in referenced assembly <insert_3> all Explanation: This shows the correct usage.
of which implement the IMQObjectTrigger interface.
Response: None.
Response: It is a requirement of the WebSphere MQ
.NET monitor that either a single class implementing
AMQ8391 <insert_3> is not a valid command line
the IMQObjectTrigger interface exists in the referenced
option.
assembly or that a class is identified in that assembly to
execute. Either modify the assembly to include a single Severity: 40 : Stop Error
class implementing IMQObjectTrigger or specify a class
Explanation: The option <insert_3> was specified on
name on the command line and retry.
the command line to the application however this is
not one of the valid set of command line options.
AMQ8382 A Message breaking the backout
threshold (<insert_1>) was moved to
application and then retry.
<insert_4>
AMQ8392 The required command line option
Explanation: Whilst processing queue <insert_3> a <insert_3> is missing.
message whose backout count exceeded the specified
backout threshold (<insert_1>) was successfully moved
to <insert_4> Explanation: The application expects mandatory
command line options. One of these, <insert_3>, was
Response: The message moved to the backout queue
not specified.
has a backout count greater than the backout threshold
specified (or picked up from the input queue Response: Check the usage information for the
BOTHRESH attribute). You should investigate the application and ensure that all required parameters are
reason why this message was rolled back onto the specified then retry.
input queue and resolve that issue. If backout
processing is not required, modify the command line
options and or queue definitions to achieve the
required behaviour from the .NET monitor.

AMQ8393 Invalid value specified for command AMQ8398 Unexpected exception received from
line option <insert_3> (<insert_4>). .NET Framework
<insert_3>
Explanation: The value specified for command line
option <insert_3> (<insert_4>) is invalid. Explanation: The application received an exception
from the underlying .NET framework, information
about the exception follows:
application and ensure that all options specify values in
<insert_4>
the valid range then retry.
Response: Examine the information contained within
the exception to determine if it is possible to resolve
locally.
If it is not possible to resolve the problem locally, save
Severity: 40 : Stop Error the generated output files and contact your IBM
support center.
Explanation: The WebSphere MQ queue manager
AMQ8401 <insert_1> MQSC commands read.
Response: Either create the queue manager (crtmqm
command) or correct the queue manager name used in Severity: 0 : Information
the command and then try the command again.
Explanation: The MQSC script contains <insert_1>
commands.
Response: None.
<insert_3> not available.
AMQ8402 <insert_1> commands have a syntax
Explanation: The WebSphere MQ queue manager error.
<insert_3> is not available because it has been stopped
or is otherwise not contactable.
commands having a syntax error.
message queue manager as necessary or correct any
intermittent problems (eg. network connectivity) then Response: None.
AMQ8403 <insert_1> valid MQSC commands could
AMQ8396 WebSphere MQ queue <insert_3> not not be processed.
found.
Explanation: The queue <insert_3> could not be commands that failed to process.
found, it may not have been created.
Response: None.
Response: Ensure that the name of the queue
specified is correct, queue names are case sensitive. If
AMQ8404 Command failed.
the queue is not created, use the runmqsc command to
create it. Then try the command again. Severity: 0 : Information
Explanation: An MQSC command has been
AMQ8397 Unexpected error <insert_1> was recognized, but cannot be processed.
received by the application.
Response: None.
Explanation: The error <insert_1> was returned AMQ8405 Syntax error detected at or near end of
unexpectedly to the application. command segment below:-
Response: Save the generated output files and contact Severity: 0 : Information
commands having a syntax error.
Response: None.

AMQ8406 Unexpected ’end of input’ in MQSC. AMQ8413 String Length Error.
Explanation: An MQSC command contains a Explanation: A string assigned to an MQSC keyword
continuation character, but the ’end of input’ has been is either NULL, or longer than the maximum permitted
reached without completing the command. for that keyword.
AMQ8407 Display Process details. AMQ8414 Display Channel details.

Explanation: The MQSC DISPLAY PROCESS Explanation: The MQSC DISPLAY CHL command
command completed successfully, and details follow completed successfully, and details follow this message.
this message.
Response: None.
Response: None.
AMQ8415 Ping WebSphere MQ Queue Manager
AMQ8408 Display Queue Manager details. command complete.
Explanation: The MQSC DISPLAY QMGR command Explanation: The MQSC PING QMGR command
completed successfully, and details follow this message. completed successfully.
AMQ8409 Display Queue details. AMQ8416 MQSC timed out waiting for a response
from the command server.
Explanation: The MQSC DISPLAY QUEUE command
completed successfully, and details follow this message. Explanation: MQSC did not receive a response
message from the remote command server in the time
Response: None.
specified.
Response: None.
AMQ8410 Parser Error.
AMQ8417 Display Channel Status details.
Explanation: The MQSC Parser has an internal error.
Response: None.
Explanation: The MQSC DISPLAY CHANNEL
STATUS command completed successfully, and details
AMQ8411 Duplicate Keyword Error. follow this message.
Explanation: A command in the MQSC script contains
duplicate keywords. AMQ8418 <insert_1> command responses received.
Explanation: Running in queued mode, <insert_1>
AMQ8412 Numeric Range Error. command responses were received from the remote
command server.
Response: None.
Explanation: The value assigned to an MQSC
command keyword is out of the permitted range.
AMQ8419 The Queue is already in the DCE cell.
Response: None.
Explanation: The Queue is already in the cell, that is,
its SCOPE attribute is already CELL.

Response: None.
AMQ8426 Valid MQSC commands are:
AMQ8420 Channel Status not found.
Explanation: The text shows valid MQSC commands.
Response: None.
Explanation: No status was found for the specified
channel(s).
AMQ8427 Valid syntax for the MQSC command:
Response: None.
AMQ8421 A required keyword was not specified. Explanation: The text shown is the valid syntax for
the MQSC command.
Response: None.
Explanation: A keyword required in this command
was not specified.
AMQ8428 TYPE Keyword has already been
Response: None.
specified.
AMQ8422 MQSC found the following response to
a previous command on the reply q :- Explanation: The TYPE has already been specified
after the DISPLAY verb, for example DISPLAY
QUEUE(*) type(QLOCAL) type(QALIAS).
Explanation: MQSC found additional command
Response: Delete the second TYPE keyword and run
responses on the reply q. They will fill follow this
the command again.
message.
Response: None.
AMQ8429 (iSeries) Error detected in a exit parameter.
AMQ8423 Cell Directory not available.
Explanation: A syntax error occurred an the exit
parameter. This may be because it contained characters
Explanation: The DCE cell directory is not available, which are not accepted as exit names. Check the
so the requested operation has failed. parameters in the MSGEXIT, RCVEXIT, SCYEXIT and
SENDEXIT definitions.
Response: None.
Response: None.
AMQ8424 Error detected in a name keyword.
AMQ8430 Remote queue manager name is
Severity: 0 : Information unknown.
Explanation: A keyword in an MQSC command Severity: 0 : Information
contained a name string which was not valid. This may
be because it contained characters which are not Explanation: The Remote queue manager name is not
accepted in MQ names. Typical keywords which can known to this queue manager. Check that a
produce this error are QLOCAL (and the other q types), transmission queue of the same name as the remote
CHANNEL, XMITQ, INITQ, MCANAME etc. queue manager name exists.
Response: None. Response: Create a transmission queue of the same
name as the remote queue manager if one does not
exist.
AMQ8425 Attribute value error.
Severity: 0 : Information AMQ8431 Transmission queue does not exist
Explanation: A keyword in an MQSC command Severity: 0 : Information
contained a value that was not valid.
Explanation: The transmission queue does not exist on
Response: None. this queue manager.
Response: None.

AMQ8432 You are not allowed to set both the AMQ8438 One MQSC command read.
REPOS and REPOSNL fields.
Explanation: The MQSC script contains one
Explanation: An attempt to set both the REPOS and command.
REPOSNL fields has been made. Only one of these
Response: None.
fields can have a value other than blank. Both of the
fields may be blank.
AMQ8439 No commands have a syntax error.
Response: None.
AMQ8433 You are not allowed to set both the Explanation: The MQSC script contains no commands
CLUSTER and CLUSNL fields. having a syntax error.
Explanation: An attempt to set both the CLUSTER
and CLUSNL fields has been made. Only one of these AMQ8440 One command has a syntax error.
fields can have a value other than blank. Both of the
fields may be blank. Severity: 0 : Information
Response: None. Explanation: The MQSC script contains one command

which has a syntax error.
AMQ8434 The repository is unavailable. Response: None.
AMQ8441 Display Cluster Queue Manager details.
Explanation: The repository is unavailable and the
data cannot be accessed. Stop and restart the queue Severity: 0 : Information
manager. Explanation: The MQSC DISPLAY CLUSQMG
Response: None. command completed successfully, and details follow
this message.
AMQ8435 All valid MQSC commands were Response: None.

processed.
Severity: 0 : Information AMQ8442 USAGE can not be set to XMITQ with
either the CLUSTER or CLUSNL fields
Explanation: The MQSC script contains no commands set.
that failed to process.
Response: None.
Explanation: An attempt has been made to set USAGE
to XMITQ when the CLUSTER or CLUSNL field has a
AMQ8436 One valid MQSC command could not value. Change the value of USAGE, or set the
be processed. CLUSTER and CLUSNL fields to blank, and try the
command again.
Response: None.
Explanation: The MQSC script contains one command
that failed to process.
AMQ8442 (iSeries) USAGE can not be set to *TMQ
Response: None.
with either the CLUSTER or CLUSNL
fields set.
AMQ8437 No MQSC commands read.
Explanation: An attempt has been made to set USAGE
Explanation: The MQSC script contains no commands. to *TMQ when the CLUSTER or CLUSNL field has a
value. Change the value of USAGE, or set the
Response: None.
CLUSTER and CLUSNL fields to blank, and try the
command again.
Response: None.

AMQ8443 Only the CLUSTER or CLUSNL field AMQ8448 Channel <insert_5> is not running.
may have a value.
Explanation: A request to end channel <insert_5> has
Explanation: An attempt has been made to set both failed because the channel is not running.
CLUSTER and CLUSNL fields. One and only one of the
Response: Check that the correct operation was
fields may have a value, the other field must be blank.
requested. If it was, check that the correct channel
Change the value of one of the fields to blank and try
name was specified.
the command again.
Response: None.
AMQ8449 Queue <insert_5> inhibited for MQGET.
AMQ8444 The CLUSTER or CLUSNL fields must
have a value. Explanation: An MQGET failed because the queue
<insert_5> had been previously inhibited for MQGET.
Response: None.
Explanation: Both the CLUSTER and CLUSNL fields
are blank. One and only one of the fields may be blank,
the other field must be a value. Change one of the AMQ8450 Display queue status details.
fields from blank to a value and try the command
again. Severity: 0 : Information
Response: None. Explanation: The MQSC DISPLAY QSTATUS

command completed successfully. Details follow this
message.
AMQ8445 Program cannot open queue manager
object.
AMQ8451 (iSeries) STATUS(*STOPPED) not allowed
Severity: 30 : Severe error with CONNAME specified.
Explanation: An attempt to open a queue manager Severity: 0 : Information
object has failed.
Explanation: The STATUS(*STOPPED) parameter is
Response: See the previously listed messages in the not allowed when specifying CONNAME on the
job log. ENDMQMCHL command.
AMQ8446 Channel is currently active. the command or, specify STATUS(*INACTIVE) to end
the channel instance for the specified connection name.
Explanation: The requested operation failed because
AMQ8452 (iSeries) STATUS(*STOPPED) not allowed
the channel is currently active.
with RQMNAME specified.
Response: See the previously listed messages in the
job log.
Explanation: The STATUS(*STOPPED) parameter is
not allowed when specifying RQMNAME on the
AMQ8447 Requested operation on channel
ENDMQMCHL command.
<insert_5> not valid for this channel
type. Response: Remove the RQMNAME parameter from
the command or, specify STATUS(*INACTIVE) to end
the channel instance for the specified remote queue
Explanation: The operation requested cannot be manager.
performed because channel <insert_5> is not of a
suitable type. For example, only sender, server and
AMQ8453 The path <insert_3> is invalid
cluster-sender channels can be resolved.
Response: Check that the correct operation was
requested. If it was, check that the correct channel Explanation: You typed a path which was not
name was specified. syntactically correct for the operating system you are
running WebSphere MQ on.
Response: Determine the correct syntax of a path
name for the operating system you are running

WebSphere MQ on and use this information to type in
AMQ8460 Syntax error in connection identifier.
a valid path.
AMQ8454 Syntax error found in parameter Explanation: You specified an invalid connection
<insert_3>. identifier. A valid connection identifier contains 16 hex
characters, where all of the characters in the connection
identifier should lie within the range 0-9, a-z or A-Z.
Explanation: The data you entered for <insert_3> does
Response: Correct the connection identifier so that it
not conform to the syntax rules laid down by
conforms to the above specification.
WebSphere MQ for this parameter.
Response: Carefully check the data entered for this
AMQ8461 Connection identifier not found.
parameter in conjunction with the WebSphere MQ
Command Reference to determine the cause of error. Severity: 0 : Information
Explanation: You specified a connection identifier
AMQ8455 Password length error which is not associated with this queue manager.
Severity: 20 : Error Response: Correct the connection identifier so that it
describes a connection identifier which is associated
Explanation: The password string length is rounded
with this queue manager. Use the command DISPLAY
up by WebSphere MQ to the nearest eight bytes. This
CONN to identify potential connection identifiers to
rounding causes the total length of the SSLCRYP string
use with this command.
to exceed its maximum.
Response: Decrease the size of the password, or of
AMQ8498 Starting MQSC for queue manager
earlier fields in the SSLCRYP string.
<insert_3>.
AMQ8456 Conflicting parameters in command.
commands.
Explanation: The command contains parameters that
Response: None.
cannot be used together.
Response: Refer to the WebSphere MQ Script (MQSC)
AMQ8499 Usage: runmqsc [-e] [-v] [-w WaitTime
Command Reference to determine an allowable
[-x]] QMgrName
combination of parameters for this command.
AMQ8457 WebSphere MQ connection stopped. Explanation: None.
Explanation: The STOP CONN command successfully
stopped the connection that was specified. AMQ8500 WebSphere MQ Display MQ Files
AMQ8458 WebSphere MQ connection not stopped. AMQ8501 Common services initialization failed
with return code <insert_1>.
Explanation: The STOP CONN command could not
stop the connection that was specified. Explanation: A request by the command server to
initialize common services failed with return code
Response: None.
<insert_1>.
Response: None.
AMQ8459 Not Found.
AMQ8502 Connect shared memory failed with
Explanation: You specified an identifier that was not return code <insert_1>.
found. Please try the command again and supply a
valid identifier.
Explanation: A request by the command server to
Response: None.

connect shared memory failed with return code delete a queue manager object list failed with return
<insert_1>. code <insert_1>.
AMQ8503 Post event semaphore failed with return AMQ8509 Command server MQCLOSE reply-to
code <insert_1>. queue failed with reason code
<insert_1>.
Explanation: A request by the command server to post
an event semaphore failed with return code <insert_1>. Explanation: An MQCLOSE request by the command
server for the reply-to queue failed with reason code
Response: None.
<insert_1>.
Response: None.
AMQ8504 Command server MQINQ failed with
reason code <insert_1>.
AMQ8510 Command server queue is open, try
again later.
Explanation: An MQINQ request by the command
server, for the WebSphere MQ queue <insert_3>, failed
with reason code <insert_1>.
AMQ8511 Usage: strmqcsv [QMgrName]
Response: None.
AMQ8505 Reallocate memory failed with return
code <insert_1>. AMQ8512 Usage: endmqcsv [-c | -i] QMgrName
Explanation: A request by the command server to
reallocate memory failed with return code <insert_1>. AMQ8513 Usage: dspmqcsv [QMgrName]
AMQ8506 Command server MQGET failed with AMQ8514 No response received after <insert_1>
reason code <insert_1>. seconds.
Explanation: An MQGET request by the command Explanation: The command server has not reported
server, for the WebSphere MQ queue <insert_3>, failed the status of running, to the start request, before the
with reason code <insert_1>. timeout of <insert_1> seconds was reached.
AMQ8507 Command server MQPUT1 request for AMQ8549 Total string length exceeds the
an undelivered message failed with maximum value of 999 characters.
Explanation: The total length of a channel exit string
Explanation: An attempt by the command server to is 999 characters. The string list assigned to an MQSC
put a message to the dead-letter queue, using keyword is longer than the maximum value of 999
MQPUT1, failed with reason code <insert_1>. The characters permitted for that keyword.
MQDLH reason code was <insert_2>.
Response: None.
Response: None.
AMQ8550 Display namelist details.
AMQ8508 Queue Manager Delete Object List
failed with return code <insert_1>.
Explanation: The MQSC DISPLAY NAMELIST
command completed successfully, and details follow
Explanation: A request by the command server to this message.

Response: None.
AMQ8557 SUSPEND QUEUE MANAGER
accepted.
AMQ8551 WebSphere MQ namelist changed.
Explanation: The SUSPEND QUEUE MANAGER
Explanation: WebSphere MQ namelist <insert_5> command has been accepted for processing. The
changed. command will be sent to the repository which will
process the command and notify all other repositories
Response: None. that this queue manager is leaving the cluster.
Response: None.
AMQ8552 WebSphere MQ namelist created.
Severity: 0 : Information AMQ8558 REFRESH CLUSTER accepted.
Explanation: WebSphere MQ namelist <insert_5> Severity: 0 : Information
created.
Explanation: The REFRESH CLUSTER command has
Response: None. been accepted for processing. The command will be
sent to the Repository which will process the command
AMQ8553 WebSphere MQ namelist deleted. and notify all other repositories that the Cluster needs
refreshing.
Response: None.
Explanation: WebSphere MQ namelist <insert_5>
deleted.
AMQ8559 RESET CLUSTER accepted.
Response: None.
AMQ8554 String List String Count Error. Explanation: The RESET CLUSTER command has
been accepted for processing. The command will be
Severity: 0 : Information sent to the Repository which will process the command
Explanation: The number of strings within the and notify all other repositories that the Cluster needs
stringlist is greater than the maximum number allowed resetting.
for the keyword. Reduce the number of strings within Response: None.
the list and try the command again.
Response: None. AMQ8560 WebSphere MQ security cache
refreshed.
AMQ8555 String List String Length Error. Severity: 0 : Information
Severity: 0 : Information Explanation: The Object Authority Manager security
Explanation: A string in a string list assigned to a cache has been refreshed.
keyword is longer than the maximum permitted for Response: None.
that keyword.
Response: None. AMQ8561 (Windows) Domain controller
unavailable.
AMQ8556 RESUME QUEUE MANAGER accepted. Severity: 10 : Warning
Severity: 0 : Information Explanation: WebSphere MQ was unable to contact
Explanation: The RESUME QUEUE MANAGER the domain controller to obtain information for user
command has been accepted for processing. The <insert_3>.
command will be sent to the repository which will Response: Ensure that a domain controller for the
process the command and notify all other repositories domain on which user <insert_3> is defined is
that this queue manager is now back in the cluster. available. Alternatively, if you are using a computer
Response: None. which is not currently connected to the network and
have logged on using a domain user ID, you may wish
to log on using a local user ID instead.

valid for the type of parameter, that the parameter can
AMQ8563 WebSphere MQ authentication
be filtered on, and that the value that you specified for
information object created.
the filter is valid for the type of attribute you are
Severity: 0 : Information filtering on.
Explanation: WebSphere MQ authentication Response: None.
information object <insert_5> created.
Response: None. AMQ8570 Attribute value error in <insert_3>.
Explanation: The keyword <insert_3> contained a
information object deleted.
value that was not valid for this configuration. Please
Severity: 0 : Information check the MQSC Command Reference to determine
valid values for <insert_3>.
Explanation: WebSphere MQ authentication
information object <insert_5> deleted. Response: None.
Response: None.
AMQ8601 WebSphere MQ trigger monitor started.
AMQ8565 Queue Status not found. Severity: 0 : Information
Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor has
been started.
Explanation: Queue Status for the specified queue
could not be found. Response: None.
Response: None.
AMQ8601 (iSeries) WebSphere MQ trigger monitor
started.
AMQ8566 Display authentication information
details. Severity: 0 : Information
Severity: 0 : Information Explanation: The trigger monitor has been started
with initiation queue <insert_3>.
Explanation: The MQSC DISPLAY AUTHINFO
command completed successfully. Details follow this Response: None.
message.
Response: None. AMQ8602 WebSphere MQ trigger monitor ended.
Explanation: The WebSphere MQ trigger monitor has
information changed.
ended.
Response: None.
Explanation: WebSphere MQ authentication
information <insert_5> changed.
AMQ8603 Usage: runmqtrm [-m QMgrName] [-q
Response: None. InitQ]
AMQ8568 (iSeries) No authinfo objects to display.
Explanation: None.
Response: None.
Explanation: There are no matching authinfo objects
defined on this system.
AMQ8604 Use of WebSphere MQ trigger monitor
Response: Using the DEFINE AUTHINFO command not authorized.
to create an authinfo object.
Explanation: The trigger monitor cannot be run due to
AMQ8569 Error in filter specification
lack of authority to the requested queue manager or
Severity: 0 : Information initiation queue.
Explanation: You specified an invalid filter. Check the Response: Obtain the necessary authority from your
WHERE statement and make sure that the operator is

security officer or WebSphere MQ administrator. Then
AMQ8610 Initiation queue in use
AMQ8605 Queue manager not available to the Explanation: The WebSphere MQ trigger monitor
WebSphere MQ trigger monitor could not open the initiation queue because the queue
is open for exclusive use by another application.
Response: Wait until the queue is no longer in use,
Explanation: The queue manager specified for the
and try the command again.
trigger monitor does not exist, or is not active.
Response: Check that you named the correct queue
AMQ8611 Initiation queue could not be opened.
manager. Ask your systems administrator to start it, if
it is not active. Then try the command again. Severity: 0 : Information
Explanation: The WebSphere MQ trigger monitor
AMQ8606 Insufficient storage available for the could not open the initiation queue; reason code
WebSphere MQ trigger monitor. <insert_1> was returned from MQOPEN.
Severity: 0 : Information Response: Consult your systems administrator.
Explanation: There was insufficient storage available
for the WebSphere MQ trigger monitor to run. AMQ8612 Waiting for a trigger message
Response: Free some storage and then try the Severity: 0 : Information
command again.
Explanation: The WebSphere MQ trigger monitor is
waiting for a message to arrive on the initiation queue.
AMQ8607 WebSphere MQ trigger monitor
Response: None.
connection failed.
AMQ8613 Initiation queue changed or deleted
Explanation: The trigger monitor’s connection to the
requested queue manager failed because of MQI reason
code <insert_1> from MQCONN. Explanation: The WebSphere MQ trigger monitor is
unable to continue because the initiation queue has
Response: Consult your systems administrator about
been deleted or changed since it was opened.
the state of the queue manager.
Response: Retry the command.
AMQ8608 WebSphere MQ trigger monitor
connection broken. AMQ8614 Initiation queue not enabled for input.
Explanation: The connection to the queue manager Explanation: The WebSphere MQ trigger monitor
failed while the trigger monitor was running. This may cannot read from the initiation queue because input is
be caused by an endmqm command being issued by not enabled.
another user, or by a queue manager error.
Response: Ask your systems administrator to enable
Response: Consult your systems administrator about the queue for input.
the state of the queue manager.
AMQ8615 WebSphere MQ trigger monitor failed
AMQ8609 Initiation queue missing or wrong type to get message.
Explanation: The named initiation queue could not be Explanation: The WebSphere MQ trigger monitor
found; or the queue type is not correct for an initiation failed because of MQI reason code <insert_1> from
queue. MQGET.
Response: Check that the named queue exists, and is Response: Consult your systems administrator.
a local queue, or that the named queue is an alias for a
local queue which exists.

AMQ8616 End of application trigger. AMQ8622 Usage: CICS-Transaction-Name
[MQTMC2 structure]
Explanation: The action to trigger an application has
been completed. Explanation: None.
AMQ8617 Not a valid trigger message. AMQ8623 WebSphere MQ listener changed.

Explanation: The WebSphere MQ trigger monitor Explanation: WebSphere MQ listener <insert_5>
received a message that is not recognized as a valid changed.
trigger message. It has been written to the undelivered
Response: None.
message queue.
Response: Consult your systems administrator.
AMQ8624 WebSphere MQ service changed.
AMQ8618 Error starting triggered application.
Explanation: WebSphere MQ service <insert_5>
changed.
Explanation: An error was detected when trying to
Response: None.
start the application identified in a trigger message.
Response: Check that the application the trigger
AMQ8625 WebSphere MQ service created.
monitor was trying to start is available.
AMQ8619 Application type <insert_1> not Explanation: WebSphere MQ service <insert_5>
supported. created.
Explanation: A trigger message was received which
specifies application type <insert_1>; the trigger AMQ8626 WebSphere MQ listener created.
monitor does not support this type.
Response: Use an alternative trigger monitor for this
initiation queue. Explanation: WebSphere MQ listener <insert_5>
created.
AMQ8620 Trigger message with warning <insert_1> Response: None.
AMQ8627 WebSphere MQ service object deleted.
Explanation: The trigger monitor received a message
with a warning. For example, it may have been Severity: 0 : Information
truncated or it could not be converted to the trigger Explanation: WebSphere MQ service object <insert_5>
monitor’s data representation. The reason code for the deleted.
warning is <insert_1>.
Response: None.
Response: None.
AMQ8628 WebSphere MQ listener object deleted.

AMQ8621 Usage: runmqtmc [-m QMgrName] [-q
InitQ] Severity: 0 : Information
Severity: 0 : Information Explanation: WebSphere MQ listener object <insert_5>

deleted.
Explanation: None.
Response: None.
Response: None.

information should have been available. Running the
AMQ8629 Display service information details.
command with the ’outline’ verbosity option (used
Severity: 0 : Information with the -v flag) may be useful in determining where
the message was when the activity information was
Explanation: The MQSC DISPLAY SERVICE command
generated.
completed successfully. Details follow this message.
Response: None.
AMQ8650 (iSeries) Activity information unavailable.
AMQ8630 Display listener information details.
Explanation: The DSPMQMRTE command was
expecting activity information but it was unavailable.
Explanation: The MQSC DISPLAY LISTENER This does not always constitute an error. Reasons why
command completed successfully. Details follow this the activity information is unavailable include the
message. following:
1) One of the queue managers on the route did not
Response: None. support trace-route messaging.
2) One of the queue managers on the route did not
AMQ8631 Display listener status details. allow route information to be returned to the reply
queue. See the documentation on the ActivityRecording
Severity: 0 : Information and TraceRouteRecording queue manager attributes for
Explanation: The MQSC DISPLAY LSSTATUS more details.
command completed successfully. Details follow this 3) The report could not a find route back to the reply
message. queue.
Response: Try and determine whether the activity
AMQ8632 Display service status details. information should have been available. Running the
command with DSPINF(*ALL) may be useful in
Severity: 0 : Information determining where the message was when the activity
Explanation: The MQSC DISPLAY SVSTATUS information was generated.
message. AMQ8651 DSPMQRTE command has finished
with errors.
AMQ8649 Reset WebSphere MQ Queue Manager Severity: 0 : Information
accepted.
Explanation: The DSPMQRTE command has finished
Severity: 0 : Information processing your request but an execution error was
Explanation: The MQSC RESET QMGR command detected. Previous messages issued by the command
completed successfully. Details follow this message. can be used to identify the error.
Response: None. Response: Refer to previous messages issued by the

command.
AMQ8650 Activity information unavailable.

AMQ8651 (iSeries) DSPMQMRTE command has
Severity: 0 : Information finished with errors.
Explanation: The DSPMQRTE command was Severity: 0 : Information
expecting activity information but it was unavailable.
This does not always constitute an error. Reasons why Explanation: The DSPMQMRTE command has
the activity information is unavailable include the finished processing your request but an execution error
following: was detected. Previous messages issued by the
1) One of the queue managers on the route did not command can be used to identify the error.
support trace-route messaging. Response: Refer to previous messages issued by the
2) One of the queue managers on the route did not command.
allow route information to be returned to the reply
queue. See the documentation on the ActivityRecording
and TraceRouteRecording queue manager attributes for AMQ8652 DSPMQRTE command has finished.
more details. Severity: 0 : Information
3) The report could not a find route back to the reply
queue. Explanation: The DSPMQRTE command has finished
processing your request and no execution errors were
Response: Try and determine whether the activity detected.

Response: None.
AMQ8655 Trace-route message expired.
finished. Explanation: The DSPMQRTE command has received
confirmation that the trace-route message has expired.
Response: The expiry interval of trace-route messages
Explanation: The DSPMQMRTE command has
generated by the DSPMQRTE command can be altered
finished processing your request and no execution
using the -xs option if this is required.
errors were detected.
Response: None.
AMQ8655 (iSeries) Trace-route message expired.
AMQ8653 DSPMQRTE command started with
options <insert_3>. Explanation: The DSPMQMRTE command has
received confirmation that the trace-route message has
expired.
Explanation: You have started the DSPMQRTE
Response: The expiry interval of trace-route messages
command with command line options <insert_3> and
generated by the DSPMQMRTE command can be
the command is now processing your request.
altered using the EXPIRY parameter if this is required.
Response: Wait for the command to finish processing
your request. Any further messages that are issued can
AMQ8656 DSPMQRTE command received an
be used to determine the outcome of the request.
exception report from queue manager
<insert_4> with feedback <insert_1>
AMQ8653 (iSeries) DSPMQMRTE command started. <insert_3>.
Explanation: You have started the DSPMQMRTE Explanation: The DSPMQRTE command trace-route
command and the command is now processing your message caused an exception on queue manager
request. <insert_4>. The Feedback field in the report was
<insert_1> or <insert_3>.
Response: Wait for the command to finish processing
your request. Any further messages that are issued can Response: Use the feedback given to determine why
be used to determine the outcome of the request. the trace-route message caused the exception.
AMQ8654 Trace-route message arrived on queue AMQ8656 (iSeries) DSPMQMRTE command

manager <insert_3>. received an exception report from queue
manager <insert_4> with feedback
Severity: 0 : Information <insert_1> <insert_3>.
Explanation: The DSPMQRTE command has received Severity: 0 : Information
confirmation of the successful arrival of the trace-route
message at its destination queue on queue manager Explanation: The DSPMQMRTE command trace-route
<insert_3>. message caused an exception on queue manager
<insert_4>. The Feedback field in the report was
Response: None. <insert_1> or <insert_3>.
Response: Use the feedback given to determine why
AMQ8654 (iSeries) Trace-route message arrived on the trace-route message caused the exception.
Severity: 0 : Information AMQ8657 DSPMQRTE command used <insert_3>
Explanation: The DSPMQMRTE command has 0x<insert_4>.
received confirmation of the successful arrival of the Severity: 0 : Information
trace-route message at its destination queue on queue
manager <insert_3>. Explanation: You started the DSPMQRTE command
specifying that it should generate a trace-route
Response: None. message. This took place and the trace-route message
had <insert_3> X<insert_4>.
Response: The <insert_3> can be used to retrieve
responses to this trace-route request. Run the

DSPMQRTE command again specifying this identifier
AMQ8659 (iSeries) DSPMQMRTE command
with the -i flag and with the target queue specified as
successfully put a message on queue
the queue where the responses are expected to return
<insert_3>, queue manager <insert_4>.
or where the trace-route message is expected to have
arrived. This may be on another queue manager. Severity: 0 : Information
Explanation: The request for the DSPMQMRTE
AMQ8657 (iSeries) DSPMQMRTE command used command to put a message on the target queue was
<insert_3> 0x<insert_4>. successful. The target queue resolved to <insert_3> on
Response: None.
Explanation: You started the DSPMQMRTE command
specifying that it should generate a trace-route
message. This took place and the trace-route message AMQ8660 DSPMQRTE command could not
had <insert_3> X<insert_4>. correctly order the following activities:
Response: The <insert_3> can be used to retrieve Severity: 0 : Information
responses to this trace-route request. Run the
Explanation: The DSPMQRTE command received the
DSPMQMRTE command again specifying this identifier
following activities, but they could not be printed in
for CRLLID and with the target queue specified as the
the correct order. This is commonly because an activity
queue where the responses are expected to return or
report has been received that does not contain a
where the trace-route message is expected to have
TraceRoute PCF group or is missing the
arrived. This may be on another queue manager.
RecordedActivities parameter which would allow it to
be ordered correctly.
AMQ8658 DSPMQRTE command failed to put a
Response: Find and correct the application that is
message on the target queue.
generating activity reports without the necessary
Severity: 0 : Information information for them to be ordered correctly.
Explanation: The request for the DSPMQRTE
command to put a trace-route message on the target AMQ8660 (iSeries) DSPMQMRTE command could
queue was unsuccessful. Previous messages issued by not correctly order the following
the command can be used to identify why the message activities:
could not be put on the target queue.
Response: Refer to previous messages issued by the
Explanation: The DSPMQMRTE command received
command.
the following activities, but they could not be printed
in the correct order. This is commonly because an
AMQ8658 (iSeries) DSPMQMRTE command failed activity report has been received that does not contain
to put a message on the target queue. a TraceRoute PCF group or is missing the
RecordedActivities parameter which would allow it to
be ordered correctly.
Explanation: The request for the DSPMQMRTE
Response: Find and correct the application that is
command to put a trace-route message on the target
generating activity reports without the necessary
queue was unsuccessful. Previous messages issued by
information for them to be ordered correctly.
the command can be used to identify why the message
could not be put on the target queue.
AMQ8661 DSPMQRTE command will not put to
queue <insert_3>, queue manager
command.
<insert_4>.
AMQ8659 DSPMQRTE command successfully put
a message on queue <insert_3>, queue Explanation: You started the DSPMQRTE command
manager <insert_4>. specifying that the trace-route message should not be
delivered to a local queue (-d yes was not specified).
However, it has been determined that the target queue
Explanation: The request for the DSPMQRTE does not resolve to a transmission queue. Therefore the
command to put a message on the target queue was DSPMQRTE command has chosen not to put the
successful. The target queue resolved to <insert_3> on trace-route message to the target queue <insert_3> on
queue manager <insert_4>. queue manager <insert_4>.
Response: None. Response: Determine whether it was expected that the

target queue would resolve to a local queue. queue manager. Previous messages issued by the
command can be used to identify the error.
AMQ8661 (iSeries) DSPMQMRTE command will not Response: Refer to previous messages issued by the
put to queue <insert_3>, queue manager command.
<insert_4>.
Severity: 20 : Error AMQ8664 (iSeries) DSPMQMRTE command could
not connect to queue manager
<insert_3>.
specifying that the trace-route message should not be
delivered to a local queue (DLVRMSG(*NO) was Severity: 20 : Error
specified). However, it has been determined that the
target queue does not resolve to a transmission queue.
specifying that it should connect to queue manager
Therefore the DSPMQMRTE command has chosen not
<insert_3>. The command could not connect to that
to put the trace-route message to the target queue
queue manager. Previous messages issued by the
<insert_3> on queue manager <insert_4>.
Response: Determine whether it was expected that the
target queue would resolve to a local queue.
command.
AMQ8662 Trace-route message delivered on queue

AMQ8665 DSPMQRTE command was supplied an
manager <insert_3>.
invalid CorrelId <insert_3>.
Explanation: The DSPMQRTE command has received
Explanation: You started the DSPMQRTE command
confirmation of the successful delivery of the
specifying option -i with a CorrelId <insert_3> that was
trace-route message on queue manager <insert_3> to a
invalid. The CorrelId was either too long or not in the
requesting application.
correct format.
Response: None.
Response: Refer to the command syntax, and then try
the command again.
AMQ8662 (iSeries) Trace-route message delivered on
AMQ8665 (iSeries) DSPMQMRTE command was
Severity: 0 : Information supplied an invalid CorrelId <insert_3>.
Explanation: The DSPMQMRTE command has Severity: 20 : Error
received confirmation of the successful delivery of the
trace-route message on queue manager <insert_3> to a
specifying CRLLID with a CorrelId <insert_3> that was
requesting application.
invalid.
Response: None.
the command again.
AMQ8663 Client connection not supported in this
environment.
AMQ8666 Queue <insert_3> on queue manager
Severity: 20 : Error <insert_4>.
Explanation: An attempt was made to connect to a Severity: 0 : Information
queue manager using a client connection. However,
Explanation: The DSPMQRTE command trace-route
client connections are not supported in your
message has been confirmed as having taken a route
environment.
involving queue <insert_3> on queue manager
Response: Connect to the queue manager using a <insert_4> in an attempt to reach the destination queue.
server connection.
Response: Wait for subsequent messages which may
indicate another queue which the message has been
AMQ8664 DSPMQRTE command could not routed through.
connect to queue manager <insert_3>.
specifying that it should connect to queue manager
<insert_3>. The command could not connect to that

manager <insert_4>. Previous messages issued by the
AMQ8666 (iSeries) Queue <insert_3> on queue
manager <insert_4>.
command. Specify a queue, using the -q option, that
Explanation: The DSPMQMRTE command trace-route can be opened and then retry the command.
message has been confirmed as having taken a route
involving queue <insert_3> on queue manager
AMQ8668 (iSeries) DSPMQMRTE command could
<insert_4> in an attempt to reach the destination queue.
not open queue <insert_3>, queue
Response: Wait for subsequent messages which may manager <insert_4>.
indicate another queue which the message has been
routed through.
specifying queue <insert_3> for the QNAME parameter.
AMQ8667 DSPMQRTE command could not open
However the DSPMQMRTE command could not
reply queue <insert_3>, queue manager
successfully open a queue of that name on queue
<insert_4>.
manager <insert_4>. Previous messages issued by the
Severity: 20 : Error command can be used to identify the error.
Explanation: You started the DSPMQRTE command Response: Refer to previous messages issued by the
specifying reply queue <insert_3>. However the command. Specify a queue, using the QNAME
DSPMQRTE command could not successfully open a parameter, that can be opened and then retry the
queue of that name on queue manager <insert_4>. command.
Previous messages issued by the command can be used
to identify the error. If the -rq option was not specified
AMQ8669 DSPMQRTE command failed to resolve
then the reply queue will be a temporary dynamic
queue manager <insert_3> on queue
queue modelled on
manager <insert_4>.
SYSTEM.DEFAULT.MODEL.QUEUE.
command. Specify a reply queue that can be opened Explanation: The DSPMQRTE command attempted to
and then retry the command. resolve queue manager <insert_3> (supplied by the -qm
option) on queue manager <insert_4> but the attempt
failed. The queue specified by the -q option could not
AMQ8667 (iSeries) DSPMQMRTE command could
be opened.
not open reply queue <insert_3>, queue
manager <insert_4>. Response: Ensure that queue manager <insert_3> can
be resolved on queue manager <insert_4> or specify a
different queue manager with the -qm option. Retry the
Explanation: You started the DSPMQMRTE command command.
specifying reply queue <insert_3>. However the
DSPMQMRTE command could not successfully open a
AMQ8669 (iSeries) DSPMQMRTE command failed
queue of that name on queue manager <insert_4>.
to resolve queue manager <insert_3> on
Previous messages issued by the command can be used
to identify the error. If the RPLYQ parameter was not
specified then the reply queue will be a temporary Severity: 20 : Error
dynamic queue modelled on
SYSTEM.DEFAULT.MODEL.QUEUE. Explanation: The DSPMQMRTE command attempted
to resolve queue manager <insert_3> (supplied by the
Response: Refer to previous messages issued by the TGTMQM parameter) on queue manager <insert_4> but
command. Specify a reply queue that can be opened the attempt failed. The queue specified by the QNAME
and then retry the command. parameter could not be opened.
Response: Ensure that queue manager <insert_3> can
AMQ8668 DSPMQRTE command could not open be resolved on queue manager <insert_4> or specify a
queue <insert_3>, queue manager different queue manager with the TGTMQM parameter.
<insert_4>. Retry the command.
specifying queue <insert_3>, using the -q option.
However the DSPMQRTE command could not
successfully open a queue of that name on queue

specifying option <insert_3> with an object name
AMQ8670 Loading of server module <insert_3>
<insert_4> that is invalid. In general, the names of
failed.
WebSphere MQ objects can have up to 48 characters.
Severity: 20 : Error An object name can contain the following characters:
1) Uppercase alphabetic characters (A through Z).
Explanation: An attempt to dynamically load the
2) Lowercase alphabetic characters (a through z).
server module <insert_3> failed. Typically this is
3) Numeric digits (0 through 9).
because only the client modules are installed.
4) Period (.), forward slash (/), underscore (_), percent
Response: Check which modules are installed and (%).
retry the command with the -c option specified if See the WebSphere MQ System Administration
applicable. documentation for further details and restrictions.
Response: Specify a valid object name and then try
AMQ8671 DSPMQRTE command was not supplied the command again.
a reply queue when one was required.
Severity: 20 : Error AMQ8673 (iSeries) DSPMQMRTE command was
supplied with an invalid object name
Explanation: The DSPMQRTE command was <insert_4>.
expecting a reply queue specified by the -rq option but
no reply queue was specified. Specifying a reply queue Severity: 20 : Error
is mandatory if both the -n (no display) option and a
response generating option (-ar or -ro
specifying an object name <insert_4> that is invalid. In
[activity|coa|cod|exception|expiration]) is specified.
general, the names of WebSphere MQ objects can have
Response: Specify a reply queue and retry the up to 48 characters. An object name can contain the
command. following characters:
1) Uppercase alphabetic characters (A through Z).
2) Lowercase alphabetic characters (a through z).
AMQ8672 DSPMQRTE command failed to get a 3) Numeric digits (0 through 9).
message from queue <insert_3>, queue 4) Period (.), forward slash (/), underscore (_), percent
manager <insert_4>. (%).
Severity: 20 : Error See the WebSphere MQ System Administration
documentation for further details and restrictions.
Explanation: The DSPMQRTE command attempted to
get a message from queue <insert_3>, queue manager Response: Specify a valid object name and then try
<insert_4>, but the attempt failed. Previous messages the command again.
issued by the command can be used to identify the
error. AMQ8674 DSPMQRTE command is now waiting
Response: Refer to previous messages issued by the for information to display.
command. Severity: 0 : Information
Explanation: The DSPMQRTE command has
AMQ8672 (iSeries) DSPMQMRTE command failed successfully generated and put the trace-route message
to get a message from queue <insert_3>, and is now waiting for responses to be returned to the
queue manager <insert_4>. reply queue to indicate the route that the trace-route
Severity: 20 : Error message took to its destination.
Explanation: The DSPMQMRTE command attempted Response: Wait for responses to be returned to the
to get a message from queue <insert_3>, queue reply queue and for the information about the route to
manager <insert_4>, but the attempt failed. Previous be displayed.
messages issued by the command can be used to
identify the error. AMQ8674 (iSeries) DSPMQMRTE command is now
Response: Refer to previous messages issued by the waiting for information to display.
command. Severity: 0 : Information
AMQ8673 DSPMQRTE command was supplied successfully generated and put the trace-route message
option <insert_3> with an invalid object and is now waiting for responses to be returned to the
name <insert_4>. reply queue to indicate the route that the trace-route
Severity: 20 : Error message took to its destination.
Explanation: You started the DSPMQRTE command Response: Wait for responses to be returned to the

reply queue and for the information about the route to
AMQ8678 DSPMQRTE command was supplied
be displayed.
option <insert_3> with an invalid value
<insert_4>.
AMQ8675 DSPMQRTE command was supplied an
invalid option <insert_3>.
specifying an invalid option value. The <insert_4> value
Explanation: You started the DSPMQRTE command for option <insert_3> is either not recognized or of an
specifying an option of <insert_3> that was not incorrect format.
recognized. The command will end.
Response: Refer to the command syntax and retry the the command again.
command.
AMQ8676 DSPMQRTE command was supplied an supplied an invalid value <insert_4>.
invalid combination of options.
Explanation: You started the DSPMQRTE command specifying an invalid parameter value. Value <insert_4>
specifying a combination of the options that is not is either not recognized or of an incorrect format.
valid. The -i option cannot be specified with one or
more of the following options: -ac, -ar, -d, -f, -l, -n, -o,
the command again.
-p, -qm, -ro, -rq, -rqm, -s, -t, -xs, -xp. The -n option
cannot be specified with one or more of the following
options: -b, -i, -v, -w. The -ar option can only be AMQ8679 Persistent messages not allowed on
specified if the -ac option has also been specified. The reply queue <insert_3>, queue manager
-rqm option can only be specified if the -rq option has <insert_4>.
also been specified.
Response: Refer to the command documentation and
Explanation: It was specified that the DSPMQRTE
command should put a persistent trace-route message
on the target queue (see the documentation for the -l
AMQ8677 DSPMQRTE command was supplied an option). However, persistent messages are not allowed
option <insert_3> with conflicting on the reply queue because it is a temporary dynamic
values. queue and persistent responses were expected to return
to it. The trace-route message was not put on the target
queue.
Response: Ensure that the reply queue is not a
specifying values for option <insert_3> that conflict. At
temporary dynamic queue. Use the -rq option to
least two values were specified for the same option but
specify the reply queue.
they conflict with each other. The DSPMQRTE
command will end.
AMQ8679 (iSeries) Persistent messages not allowed
Response: Refer to the command syntax and then try
on reply queue <insert_3>, queue
the command again.
manager <insert_4>.
supplied a parameter with conflicting Explanation: It was specified that the DSPMQMRTE
values. command should put a persistent trace-route message
on the target queue (see the documentation for the
MSGPST parameter). However, persistent messages are
Explanation: You started the DSPMQMRTE command not allowed on the reply queue because it is a
specifying values that conflict. At least two values were temporary dynamic queue and persistent responses
specified for the same parameter but they conflict with were expected to return to it. The trace-route message
each other. The DSPMQMRTE command will end. was not put on the target queue.
Response: Refer to the command syntax and then try Response: Ensure that the reply queue is not a
the command again. temporary dynamic queue. Use the RPLYQ parameter
to specify the reply queue.

was then delivered by queue manager <insert_4> to
AMQ8680 DSPMQRTE command failed to open
application <insert_3> which processed the message.
Response: Determine if it was expected that this
application would process the trace-route message.
Explanation: The DSPMQRTE command tried to open
queue manager <insert_3> for inquire but the open
AMQ8682 (iSeries) Trace-route message processed by
failed. Previous messages issued by the command can
application <insert_3> on queue manager
be used to identify the error.
<insert_4>.
command.
Explanation: The DSPMQMRTE command
successfully put a trace-route message on the target
AMQ8680 (iSeries) DSPMQMRTE command failed
queue and it was then delivered by queue manager
to open queue manager <insert_3>.
<insert_4> to application <insert_3> which processed
Severity: 20 : Error the message.
Explanation: The DSPMQMRTE command tried to Response: Determine if it was expected that this
open queue manager <insert_3> for inquire but the application would process the trace-route message.
open failed. Previous messages issued by the command
can be used to identify the error.
AMQ8683 Trace-route message reached the
Response: Refer to previous messages issued by the maximum activities limit of <insert_1>.
command.
AMQ8681 DSPMQRTE command has detected an
message was rejected after the number of activities of
error, reason <insert_1> <insert_3>.
which it was a participant reached the maximum
Severity: 20 : Error activities limit. The limit was set to <insert_1>. The
maximum activities limit is set using the -s option.
Explanation: The DSPMQRTE command has detected
an error from an MQI call during the execution of your Response: Using the output from the command
request. The reason for failure is <insert_1> or determine whether it is expected that the trace-route
<insert_3>. message should have reached the maximum activities
limit.
Response: See the WebSphere MQ Messages
documentation for an explanation of the reason for
failure. Follow any correction action and retry the AMQ8683 (iSeries) Trace-route message reached the
command. maximum activities limit of <insert_1>.
Explanation: The DSPMQMRTE command trace-route
detected an error, reason <insert_1>
message was rejected after the number of activities of
<insert_3>.
which it was a participant reached the maximum
Severity: 20 : Error activities limit. The limit was set to <insert_1>. The
maximum activities limit is set using the MAXACTS
parameter.
detected an error from an MQI call during the
execution of your request. The reason for failure is Response: Using the output from the command
<insert_1> or <insert_3>. determine whether it is expected that the trace-route
message should have reached the maximum activities
Response: See the WebSphere MQ Messages
limit.
documentation for an explanation of the reason for
failure. Follow any correction action and retry the
command. AMQ8684 Trace-route message reached trace-route
incapable queue manager <insert_3>.
AMQ8682 Trace-route message processed by Severity: 0 : Information
application <insert_3> on queue manager
<insert_4>.
message was rejected because it was about to be sent to
Severity: 0 : Information a queue manager which does not support trace-route
messaging. This behaviour was requested because the
Explanation: The DSPMQRTE command successfully
forwarding options specified on the command only
put a trace-route message on the target queue and it

allowed the trace-route message to be forwarded to Response: Change the application that inserted the
queue managers which support trace-route messaging. forwarding options that were not recognized to insert
Sending a trace-route message to a queue manager valid and supported forwarding options.
which cannot process it in accordance with its specified
options could cause undesirable results, including
AMQ8686 Trace-route message rejected due to
having the trace-route message be put to a local queue
invalid delivery options X<insert_1>.
on the remote queue manager. If this is acceptable then
the ’-f all’ option can be specified. Severity: 20 : Error
Response: Retry the command with different Explanation: The DSPMQRTE command trace-route
forwarding options, if appropriate. message was rejected because one or more of the
delivery options was not recognized and it was in the
MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask.
AMQ8684 (iSeries) Trace-route message reached
The delivery options, when they were last observed, in
trace-route incapable queue manager
hexadecimal were X<insert_1>.
<insert_3>.
Response: Change the application that inserted the
delivery options that were not recognized to insert
Explanation: The DSPMQMRTE command trace-route valid and supported delivery options.
message was rejected because it was about to be sent to
a queue manager which does not support trace-route
AMQ8686 (iSeries) Trace-route message rejected due
messaging. This behaviour was requested because the
to invalid delivery options X<insert_1>.
forwarding options specified on the command only
allowed the trace-route message to be forwarded to Severity: 20 : Error
queue managers which support trace-route messaging.
Sending a trace-route message to a queue manager Explanation: The DSPMQMRTE command trace-route
which cannot process it in accordance with its specified message was rejected because one or more of the
options could cause undesirable results, including delivery options was not recognized and it was in the
having the trace-route message be put to a local queue MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask.
on the remote queue manager. If this is acceptable then The delivery options, when they were last observed, in
FWDMSG(*ALL) can be specified. hexadecimal were X<insert_1>.
Response: Retry the command with different Response: Change the application that inserted the
forwarding options, if appropriate. delivery options that were not recognized to insert
valid and supported delivery options.
AMQ8685 Trace-route message rejected due to

invalid forwarding options X<insert_1>. AMQ8687 Program ending.
Explanation: The DSPMQRTE command trace-route Explanation: The program operation was interrupted
message was rejected because one or more of the by a SIGINT signal on UNIX systems or a
forwarding options was not recognized and it was in CTRL+c/CTRL+BREAK signal on Windows systems.
the MQROUTE_FORWARD_REJ_UNSUP_MASK The program is now ending.
bitmask. The forwarding options, when they were last Response: Wait for the program to end.
observed, in hexadecimal were X<insert_1>.
Response: Change the application that inserted the AMQ8688 DSPMQRTE command has detected an
forwarding options that were not recognized to insert unexpected error, reason <insert_1>
valid and supported forwarding options. <insert_3>.
AMQ8685 (iSeries) Trace-route message rejected due
to invalid forwarding options Explanation: The DSPMQRTE command has detected
X<insert_1>. an unexpected error during execution of your request.
The reason for failure is <insert_1> or <insert_3>. The
Severity: 20 : Error WebSphere MQ error recording routine has been called.
Explanation: The DSPMQMRTE command trace-route Response: Use the standard facilities supplied with
message was rejected because one or more of the your system to record the problem identifier, and to
forwarding options was not recognized and it was in save the generated output files. Contact your IBM
the MQROUTE_FORWARD_REJ_UNSUP_MASK support center. Do not discard these files until the
bitmask. The forwarding options, when they were last problem has been resolved.
observed, in hexadecimal were X<insert_1>.

Response: None.
detected an unexpected error, reason
<insert_1> <insert_3>. AMQ8706 Request to stop WebSphere MQ
Listener accepted.
detected an unexpected error during execution of your Explanation: The channel listener program has been
request. The reason for failure is <insert_1> or requested to stop. This command executes
<insert_3>. The WebSphere MQ error recording routine asynchronously so may complete after this message has
has been called. been displayed.
Response: Use the standard facilities supplied with Response: Further information on the progress of the
your system to record the problem identifier, and to request is available in the queue manager error log.
problem has been resolved. AMQ8707 (iSeries) Start WebSphere MQ DLQ
Handler
AMQ8689 Loading of client module <insert_3> Severity: 0 : Information

failed.
Severity: 20 : Error AMQ8708 Dead-letter queue handler started to
process INPUTQ(<insert_3>).
client module <insert_3> failed. Typically this is because Severity: 0 : Information
the client modules are not installed. Explanation: The dead-letter queue handler
Response: Check which modules are installed and (runmqdlq) has been started and has parsed the input
retry the command without the -c option specified, if file without detecting any errors and is about to start
applicable. processing the queue identified in the message.
Response: None.
AMQ8701 Usage: rcdmqimg [-z] [-l] [-m
QMgrName] -t ObjType AMQ8708 (iSeries) Dead-letter queue handler started
[GenericObjName] to process INPUTQ(<insert_3>).
Explanation: None. Explanation: The dead-letter queue handler
Response: None. (STRMQMDLQ) has been started and has parsed the
input file without detecting any errors and is about to
start processing the queue identified in the message.
AMQ8702 Usage: rcrmqobj [-z] [-m QMgrName] -t
ObjType [GenericObjName] Response: None.
AMQ8709 Dead-letter queue handler ending.
Explanation: None.
Response: None.
Explanation: The dead-letter queue handler
(runmqdlq) is ending because the WAIT interval has
AMQ8703 Usage: dspmqfls [-m QMgrName] [-t expired and there are no messages on the dead-letter
ObjType] GenericObjName queue, or because the queue manager is shutting down,
or because the dead-letter queue handler has detected
an error. If the dead-letter queue handler has detected
Explanation: None. an error, an earlier message will have identified the
error.
Response: None.
Response: None.
AMQ8705 Display Queue Manager Status Details.
Explanation: The MQSC DISPLAY QMSTATUS
message.

AMQ8709 (iSeries) Dead-letter queue handler AMQ8721 (iSeries) Dead-letter queue message not
ending. prefixed by a valid MQDLH.
Explanation: The dead-letter queue handler Explanation: The dead-letter queue handler
(STRMQMDLQ) is ending because the WAIT interval (STRMQMDLQ) retrieved a message from the
has expired and there are no messages on the nominated dead-letter queue, but the message was not
dead-letter queue, or because the queue manager is prefixed by a recognizable MQDLH. This typically
shutting down, or because the dead-letter queue occurs because an application is writing directly to the
handler has detected an error. If the dead-letter queue dead-letter queue but is not prefixing messages with a
handler has detected an error, an earlier message will valid MQDLH. The message is left on the dead-letter
have identified the error. queue and the dead-letter queue handler continues to
process the dead-letter queue. Each time the dead-letter
Response: None.
queue handler repositions itself to a position before this
message to process messages that could not be
AMQ8710 Usage: runmqdlq [QName[QMgrName]]. processed on a previous scan it will reprocess the
failing message and will consequently re-issue this
Severity: 0 : Information message.
Explanation: Syntax for the usage of runmqdlq. Response: Remove the invalid message from the
Response: None. dead-letter queue. Do not write messages to the
dead-letter queue unless they have been prefixed by a
valid MQDLH. If you require a dead-letter queue
AMQ8711 (iSeries) Job <insert_5> has terminated handler that can process messages not prefixed by a
unexpectedly. valid MQDLH, you must change the sample program
Severity: 10 : Warning called amqsdlq to cater for your needs.
Explanation: Execution of the command <insert_3>

caused job <insert_5> to be started, but the job AMQ8722 Dead-letter queue handler unable to put
terminated unexpectedly. message: Rule <insert_1> Reason
<insert_2>.
Response: Consult the log for job <insert_5> to
determine why it was terminated. Severity: 10 : Warning
Explanation: This message is produced by the
AMQ8721 Dead-letter queue message not prefixed dead-letter queue handler when it is requested to
by a valid MQDLH. redirect a message to another queue but is unable to do
so. If the reason that the redirect fails is the same as the
Severity: 10 : Warning reason the message was put to the dead-letter queue
Explanation: The dead-letter queue handler then it is assumed that no new error has occurred and
(runmqdlq) retrieved a message from the nominated no message is produced. The retry count for the
dead-letter queue, but the message was not prefixed by message will be incremented and the dead-letter queue
a recognizable MQDLH. This typically occurs because handler will continue.
an application is writing directly to the dead-letter Response: Investigate why the dead-letter queue
queue but is not prefixing messages with a valid handler was unable to put the message to the
MQDLH. The message is left on the dead-letter queue dead-letter queue. The line number of the rule used to
and the dead-letter queue handler continues to process determine the action for the message should be used to
the dead-letter queue. Each time the dead-letter queue help identify to which queue the dead-letter queue
handler repositions itself to a position before this handler attempted to PUT the message.
message to process messages that could not be
processed on a previous scan it will reprocess the
failing message and will consequently re-issue this AMQ8729 The listener could not be stopped at this
message. time.
Response: Remove the invalid message from the Severity: 10 : Warning

dead-letter queue. Do not write messages to the Explanation: A request was made to stop a listener,
dead-letter queue unless they have been prefixed by a however the listener could not be stopped at this time.
valid MQDLH. If you require a dead-letter queue Reasons why a listener could not be stopped are:
handler that can process messages not prefixed by a The listener has active channels and the
valid MQDLH, you must change the sample program communications protocol being used is LU 6.2, SPX or
called amqsdlq to cater for your needs. NETBIOS.
The listener has active channels and the

communications protocol being used is TCP/IP and
AMQ8735 Command failed - Access denied.
channel threads are restricted to run within the listener
process. Severity: 20 : Error
Response: End the channels using the STOP Explanation: The command requested was
CHANNEL command and reissue the request. unsuccessful because access was denied attempting to
execuete the program defined to run.
AMQ8730 Listener already active. Response: Examine the definition of the object and
ensure that the path to program file is correct. If the
defined path is correct ensure that the program exists at
Explanation: A request was made to start a listener, the location specified and that the WebSphere MQ user
however the listener is already running and cannot be has access to execute the program.
started.
Response: If the listener should not be running then AMQ8736 Command failed - Program start failed.
use the STOP LISTENER command to stop the listener
before reissuing the command.
Explanation: The command requested was
unsuccessful because the attempt to execute the
AMQ8731 Listener not active.
program defined to run was unsuccessful.
Response: Examine the definition of the object and
Explanation: A request was made to stop a listener, ensure that the path to program file is correct. If the
however the listener is not running. defined path is correct ensure that the program exists at
the location specified and that the WebSphere MQ user
Response: If the listener should be running then use has access to execute the program. Further information
the START LISTENER command to start the listener. on the failure may be available in the WebSphere MQ
error logs.
AMQ8732 Request to stop Service accepted.
Severity: 0 : Information AMQ8737 Service already active.
Explanation: The Request to stop the Service has been Severity: 10 : Warning
accepted and is being processed. Explanation: A request was made to start a service,
Response: None. however the service is already running and cannot be
started.
AMQ8733 Request to start Service accepted. Response: If the service should not be running then
use the STOP SERVICE command to stop the service
Severity: 0 : Information before reissuing the command. If the intention is to
Explanation: The Request to start the Service has been allow more than one instance of s service to run, then
accepted and is being processed. the service definition may be altered to be of
SERVTYPE(COMMAND) which allows more than one
Response: None. instance of the service to be executed concurrently,
however status of services of type COMMAND is not
AMQ8734 Command failed - Program could not be available from the SVSTAUS command.
started.
Severity: 20 : Error AMQ8738 Service not active.
Explanation: The command requested was Severity: 10 : Warning

unsuccessful because the program which was defined Explanation: A request was made to stop a service,
to be run to complete the action could not be started. however the service is not running.
Reasons why the program could not be started are
The program does not exist at the specified location. Response: If the service should be running then use
The WebSphere MQ user does not have sufficient the START SERVICE command to start the service.
access to execute the program.
If STDOUT or STDERR are defined for the program, AMQ8739 Stop cannot be executed for service with
the WebSphere MQ user does not have sufficient access blank STOPCMD.
to the locations specified.
Response: Check the Queue Manager error logs for
further details on the cause of the failure and correct Explanation: A request was made to STOP a service,
before reissuing the command.

however the service has no Stop Command defined so (runmqdlq) could not open the queue manager object.
no action could be taken. This message is typically issued because of a resource
shortage or because the process does not have sufficient
Response: Examine the definition of the service and if
authority. The completion code and the reason can be
necessary update the definition of the service to include
used to identify the error. The dead-letter queue
the command to run when STOP is issued. For services
handler ends.
of type ’SERVER’ the command to run when STOP is
executed is stored when the service is started so any Response: Take appropriate action based upon the
alteration to the service definition will have no effect completion code and reason.
until the service is restarted following the update.
AMQ8742 (iSeries) Unable to open queue manager:
AMQ8740 Start cannot be executed for service with CompCode = <insert_1> Reason =
blank STARTCMD. <insert_2>.
Explanation: A request was made to START a service, Explanation: The dead-letter queue handler
however the service has no Start Command defined so (STRMQMDLQ) could not open the queue manager
no action could be taken. object. This message is typically issued because of a
resource shortage or because the process does not have
Response: Examine the definition of the service and if
sufficient authority. The completion code and the
necessary update the definition of the service to include
reason can be used to identify the error. The dead-letter
the command to run when START is issued.
queue handler ends.
Response: Take appropriate action based upon the
AMQ8741 Unable to connect to queue manager.
completion code and reason.
Explanation: The dead-letter queue handler AMQ8743 Unable to inquire on queue manager:
(runmqdlq) could not connect to queue manager CompCode = <insert_1> Reason =
<insert_3>. This message is typically issued when the <insert_2>.
requested queue manager has not been started or is
quiescing, or if the process does not have sufficient
authority. The completion code (<insert_1>) and the Explanation: The dead-letter queue handler
reason (<insert_2>) can be used to identify the error. (runmqdlq) could not inquire on the queue manager.
The dead-letter queue handler ends. This message is typically issued because of a resource
shortage or because the queue manager is ending. The
completion code and the reason can be used to identify
the error. The dead-letter queue handler ends.
AMQ8741 (iSeries) Unable to connect to queue
manager.
AMQ8743 (iSeries) Unable to inquire on queue
Explanation: The dead-letter queue handler manager: CompCode = <insert_1>
(STRMQMDLQ) could not connect to queue manager Reason = <insert_2>.
<insert_3>. This message is typically issued when the
requested queue manager has not been started or is
quiescing, or if the process does not have sufficient Explanation: The dead-letter queue handler
authority. The completion code (<insert_1>) and the (STRMQMDLQ) could not inquire on the queue
reason (<insert_2>) can be used to identify the error. manager. This message is typically issued because of a
The dead-letter queue handler ends. resource shortage or because the queue manager is
ending. The completion code and the reason can be
used to identify the error. The dead-letter queue
handler ends.
AMQ8742 Unable to open queue manager:
CompCode = <insert_1> Reason =
<insert_2>.

and the reason(<insert_2>) can be used to identify the
AMQ8744 Unable to close queue manager:
error. The dead-letter queue handler ends.
<insert_2>. Response: Take appropriate action based upon the
AMQ8746 Unable to close dead-letter queue:
(runmqdlq) could not close the queue manager. This
message is typically issued because of a resource
<insert_2>.
completion code and the reason can be used to identify Severity: 20 : Error
Response: Take appropriate action based upon the (runmqdlq) could not close the dead-letter queue. This
completion code and reason. message is typically issued because of a resource
AMQ8744 (iSeries) Unable to close queue manager:
<insert_2>. Response: Take appropriate action based upon the
AMQ8746 (iSeries) Unable to close dead-letter
(STRMQMDLQ) could not close the queue manager.
queue: CompCode = <insert_1> Reason
This message is typically issued because of a resource
= <insert_2>.
completion code and the reason can be used to identify Severity: 20 : Error
Response: Take appropriate action based upon the (STRMQMDLQ) could not close the dead-letter queue.
completion code and reason. This message is typically issued because of a resource
AMQ8745 Unable to open dead-letter queue for
browse.
(runmqdlq) could not open the dead-letter queue
AMQ8747 Integer parameter outside permissible
<insert_3> for browsing. This message is typically
range.
issued because another process has opened the
dead-letter queue for exclusive access, or because an Severity: 20 : Error
invalid dead-letter queue name was specified. Other
possible reasons include resource shortages or Explanation: The integer parameter (<insert_2>)
insufficient authority. The completion code(<insert_1>) supplied to the dead-letter handler was outside of the
and the reason(<insert_2>) can be used to identify the valid range for <insert_3> on line <insert_1>.
error. The dead-letter queue handler ends. Response: Correct the input data and restart the
Response: Take appropriate action based upon the dead-letter queue handler.
AMQ8748 Unable to get message from dead-letter
AMQ8745 (iSeries) Unable to open dead-letter queue queue: CompCode = <insert_1> Reason
for browse. = <insert_2>.
Explanation: The dead-letter queue handler Explanation: The dead-letter queue handler
(STRMQMDLQ) could not open the dead-letter queue (runmqdlq) could not get the next message from the
<insert_3> for browsing. This message is typically dead-letter queue. This message is typically issued
issued because another process has opened the because of the queue manager ending, a resource
dead-letter queue for exclusive access, or because an problem, or another process having deleted the
invalid dead-letter queue name was specified. Other dead-letter queue. The completion code and the reason
possible reasons include resource shortages or can be used to identify the error. The dead-letter queue
insufficient authority. The completion code(<insert_1>) handler ends.

AMQ8750 No valid input provided to runmqdlq.
AMQ8748 (iSeries) Unable to get message from Explanation: Either no input was provided to
dead-letter queue: CompCode = runmqdlq, or the input to runmqdlq contained no valid
<insert_1> Reason = <insert_2>. message templates. If input was provided to runmqdlq
but was found to be invalid, earlier messages will have
been produced explaining the cause of the error. The
Explanation: The dead-letter queue handler dead-letter queue handler will ends.
(STRMQMDLQ) could not get the next message from
Response: Correct the input data and restart the
the dead-letter queue. This message is typically issued
dead-letter queue handler.
because of the queue manager ending, a resource
problem, or another process having deleted the
dead-letter queue. The completion code and the reason AMQ8750 (iSeries) No valid input provided to
can be used to identify the error. The dead-letter queue STRMQMDLQ.
handler ends.
Explanation: Either no input was provided to
STRMQMDLQ, or the input to STRMQMDLQ
contained no valid message templates. If input was
AMQ8749 Unable to commit/backout action on provided to STRMQMDLQ but was found to be
dead-letter queue: CompCode = invalid, earlier messages will have been produced
<insert_1> Reason = <insert_2>. explaining the cause of the error. The dead-letter queue
handler will ends.
(runmqdlq) was unable to commit or backout an
update to the dead-letter queue. This message is
typically issued because of the queue manager ending, AMQ8751 Unable to obtain private storage.
or because of a resource shortage. If the queue manager
has ended, the update to the dead-letter queue (and
any associated updates) will be backed out when the Explanation: The dead-letter queue handler
queue manager restarts. If the problem was due to a (runmqdlq) was unable to obtain private storage. This
resource problem then the updates will be backed out problem would typically arise as a result of some more
when the dead-letter queue handler terminates. The global problem. For example if there is a persistent
completion code and the reason can be used to identify problem that is causing messages to be written to the
the error. The dead-letter queue handler ends. DLQ and the same problem (for example queue full) is
preventing the dead-letter queue handler from taking
the requested action with the message, it is necessary
for the dead-letter queue handler to maintain a large
amount of state data to remember the retry counts
AMQ8749 (iSeries) Unable to commit/backout action associated with each message, or if the dead-letter
on dead-letter queue: CompCode = queue contains a large number of messages and the
<insert_1> Reason = <insert_2>. rules table has directed the dead-letter queue handler
to ignore the messages.
Response: Investigate if some more global problem
exists, and if the dead-letter queue contains a large
(STRMQMDLQ) was unable to commit or backout an
number of messages. If the problem persists contact
update to the dead-letter queue. This message is
your support center.
typically issued because of the queue manager ending,
or because of a resource shortage. If the queue manager
has ended, the update to the dead-letter queue (and AMQ8751 (iSeries) Unable to obtain private storage.
any associated updates) will be backed out when the
queue manager restarts. If the problem was due to a
resource problem then the updates will be backed out Explanation: The dead-letter queue handler
when the dead-letter queue handler terminates. The (STRMQMDLQ) was unable to obtain private storage.
completion code and the reason can be used to identify This problem would typically arise as a result of some
the error. The dead-letter queue handler ends. more global problem. For example if there is a
persistent problem that is causing messages to be
written to the DLQ and the same problem (for example

queue full) is preventing the dead-letter queue handler the earlier error information.
from taking the requested action with the message, it is
necessary for the dead-letter queue handler to maintain
AMQ8757 Integer parameter(<insert_3>) outside
a large amount of state data to remember the retry
permissible range on line <insert_1>.
counts associated with each message, or if the
dead-letter queue contains a large number of messages Severity: 20 : Error
and the rules table has directed the dead-letter queue
handler to ignore the messages. Explanation: An integer supplied as input to the
dead-letter handler was outside of the valid range of
Response: Investigate if some more global problem integers supported by the dead-letter queue handler.
exists, and if the dead-letter queue contains a large
number of messages. If the problem persists contact Response: Correct the input data and restart the
your support center. dead-letter queue handler.
AMQ8752 Parameter(<insert_3>) exceeds maximum AMQ8758 <insert_1> errors detected in input to

length on line <insert_1>. runmqdlq.
Explanation: A parameter supplied as input to the Explanation: One or more errors have been detected
dead-letter handler exceeded the maximum length for in the input to the dead-letter queue
parameters of that type. handler(runmqdlq). Error messages will have been
generated for each of these errors. The dead-letter
Response: Correct the input data and restart the queue handler ends.
AMQ8753 Duplicate parameter(<insert_3>) found
on line <insert_1>.
AMQ8758 (iSeries) <insert_1> errors detected in
Severity: 20 : Error input to STRMQMDLQ.
Explanation: Two or more parameters of the same Severity: 20 : Error
type were supplied on a single input line to the
dead-letter queue handler. Explanation: One or more errors have been detected
in the input to the dead-letter queue
Response: Correct the input and restart the dead-letter handler(STRMQMDLQ). Error messages will have been
queue handler. generated for each of these errors. The dead-letter
queue handler ends.
AMQ8756 Error detected releasing private storage. Response: Correct the input data and restart the
AMQ8759 Invalid combination of parameters to
(runmqdlq) was informed of an error while attempting
dead-letter queue handler on line
to release an area of private storage. The dead-letter
<insert_1>.
queue handler ends.
Response: This message should be preceded by a
message or FFST information from the internal routine Explanation: An invalid combination of input
that detected the error. Take the action associated with parameters has been supplied to the dead-letter queue
the earlier error information. handler. Possible causes are: no ACTION specified,
ACTION(FWD) but no FWDQ specified,
HEADER(YES|NO) specified without ACTION(FWD).
AMQ8756 (iSeries) Error detected releasing private
storage. Response: Correct the input data and restart the
AMQ8760 Unexpected failure while initializing
(STRMQMDLQ) was informed of an error while
process: Reason = <insert_1>.
attempting to release an area of private storage. The
dead-letter queue handler ends. Severity: 30 : Severe error
Response: This message should be preceded by a Explanation: The dead-letter queue handler
message or FFST information from the internal routine (runmqdlq) could not perform basic initialization
that detected the error. Take the action associated with required to use MQ services because of an unforeseen

error. The dead-letter queue handler ends.
AMQ8762 Unexpected error while attempting to
Response: Use the standard facilities supplied with open queue manager: CompCode =
your system to record the problem identifier and to <insert_1> Reason = <insert_2>.
save the generated output files. Contact your support
been resolved. Explanation: The dead-letter queue handler
(runmqdlq) could not open the queue manager because
of an unforeseen error. The completion code and the
AMQ8760 (iSeries) Unexpected failure while
initializing process: Reason = <insert_1>.
queue handler ends.
Explanation: The dead-letter queue handler your system to record the problem identifier and to
(STRMQMDLQ) could not perform basic initialization save the generated output files. Contact your support
required to use MQ services because of an unforeseen center. Do not discard these files until the problem has
error. The dead-letter queue handler ends. been resolved.
your system to record the problem identifier and to AMQ8762 (iSeries) Unexpected error while
save the generated output files. Contact your support attempting to open queue manager:
center. Do not discard these files until the problem has CompCode = <insert_1> Reason =
been resolved. <insert_2>.
AMQ8761 Unexpected failure while connecting to
queue manager: CompCode = <insert_1>
(STRMQMDLQ) could not open the queue manager
Reason = <insert_2>.
because of an unforeseen error. The completion code
Severity: 30 : Severe error and the reason can be used to identify the error. The
dead-letter queue handler ends.
(runmqdlq) could not connect to the requested queue Response: Use the standard facilities supplied with
manager because of an unforeseen error. The your system to record the problem identifier and to
dead-letter queue handler ends. save the generated output files. Contact your support
Response: Use the standard facilities supplied with been resolved.
your system to record the problem identifier and to
center. Do not discard these files until the problem has AMQ8763 Unexpected error while inquiring on
been resolved. queue manager: CompCode = <insert_1>
Reason = <insert_2>.
AMQ8761 (iSeries) Unexpected failure while Severity: 30 : Severe error
connecting to queue manager:
Explanation: The dead letter queue handler
(runmqdlq) could not inquire on the queue manager
<insert_2>.
Severity: 30 : Severe error and the reason can be used to identify the error. The
dead letter queue handler ends.
(STRMQMDLQ) could not connect to the requested Response: Use the standard facilities supplied with
queue manager because of an unforeseen error. The your system to record the problem identifier and to
dead-letter queue handler ends. save the generated output files. Contact your support
Response: Use the standard facilities supplied with been resolved.
center. Do not discard these files until the problem has AMQ8763 (iSeries) Unexpected error while inquiring
been resolved. on queue manager: CompCode =
<insert_1> Reason = <insert_2>.
Explanation: The dead letter queue handler
(STRMQMDLQ) could not inquire on the queue
manager because of an unforeseen error. The

AMQ8765 (iSeries) Unexpected failure while
the error. The dead letter queue handler ends.
opening dead-letter queue for browse:
Response: Use the standard facilities supplied with CompCode = <insert_1> Reason =
your system to record the problem identifier and to <insert_2>.
(STRMQMDLQ) could not open the dead-letter queue
for browsing because of an unforeseen error. The
AMQ8764 Unexpected error while attempting to
close queue manager: CompCode =
Explanation: The dead-letter queue handler save the generated output files. Contact your support
(runmqdlq) could not close the queue manager because center. Do not discard these files until the problem has
of an unforeseen error. The completion code and the been resolved.
queue handler ends.
AMQ8766 Unexpected error while closing
Response: Use the standard facilities supplied with dead-letter queue: CompCode =
your system to record the problem identifier and to <insert_1> Reason = <insert_2>.
(runmqdlq) could not close the dead-letter queue
AMQ8764 (iSeries) Unexpected error while
and the reason can be used to identify the error. The
attempting to close queue manager:
<insert_2>. Response: Use the standard facilities supplied with
Explanation: The dead-letter queue handler center. Do not discard these files until the problem has
(STRMQMDLQ) could not close the queue manager been resolved.
AMQ8766 (iSeries) Unexpected error while closing
dead-letter queue: CompCode =
Response: Use the standard facilities supplied with <insert_1> Reason = <insert_2>.
center. Do not discard these files until the problem has Explanation: The dead-letter queue handler
been resolved. (STRMQMDLQ) could not close the dead-letter queue
AMQ8765 Unexpected failure while opening
dead-letter queue for browse:
CompCode = <insert_1> Reason = Response: Use the standard facilities supplied with
<insert_2>. your system to record the problem identifier and to
Explanation: The dead-letter queue handler been resolved.
(runmqdlq) could not open the dead-letter queue for
browsing because of an unforeseen error. The
AMQ8767 Unexpected error while getting message
from dead-letter queue: CompCode =
save the generated output files. Contact your support Explanation: The dead-letter queue handler
center. Do not discard these files until the problem has (runmqdlq) could not get the next message from the
been resolved. dead-letter queue because of an unforeseen error. The

completion code and the reason can be used to identify save the generated output files. Contact your support
the error. The dead-letter queue handler ends. center. Do not discard these files until the problem has
been resolved.
save the generated output files. Contact your support AMQ8769 Unable to disconnect from queue
center. Do not discard these files until the problem has manager: CompCode = <insert_1>
been resolved. Reason = <insert_2>.
AMQ8767 (iSeries) Unexpected error while getting
message from dead-letter queue:
(runmqdlq) was unable to disconnect from the queue
manager because of an unexpected error. The
<insert_2>.
Severity: 30 : Severe error the error. The dead-letter queue handler ends.
Explanation: The dead-letter queue handler Response: Use the standard facilities supplied with
(STRMQMDLQ) could not get the next message from your system to record the problem identifier and to
the dead-letter queue because of an unforeseen error. save the generated output files. Contact your support
The completion code and the reason can be used to center. Do not discard these files until the problem has
identify the error. The dead-letter queue handler ends. been resolved.
your system to record the problem identifier and to AMQ8769 (iSeries) Unable to disconnect from queue
save the generated output files. Contact your support manager: CompCode = <insert_1>
center. Do not discard these files until the problem has Reason = <insert_2>.
been resolved.
AMQ8768 Unexpected error committing/backing
(STRMQMDLQ) was unable to disconnect from the
out action on dead-letter queue:
queue manager because of an unexpected error. The
<insert_2>.
Explanation: The dead-letter queue handler your system to record the problem identifier and to
(runmqdlq) was unable to either commit or backout an save the generated output files. Contact your support
update to the dead-letter queue because of an center. Do not discard these files until the problem has
unforeseen error. The completion code and the reason been resolved.
can be used to identify the error. The dead-letter queue
handler ends.
AMQ8770 (iSeries) Cannot open <insert_5> for
Response: Use the standard facilities supplied with command <insert_3>.
center. Do not discard these files until the problem has Explanation: The <insert_3> command failed to open
been resolved. <insert_5> for WebSphere MQ processing.
Response: Check that the intended file or member
AMQ8768 (iSeries) Unexpected error exists, and was specified correctly. Correct the
committing/backing out action on specification or create the object and try the operation
dead-letter queue: CompCode = again.
Severity: 30 : Severe error AMQ8822 Invalid response, please re-enter (y or
n):
(STRMQMDLQ) was unable to either commit or Severity: 0 : Information
backout an update to the dead-letter queue because of
an unforeseen error. The completion code and the Response: None.
queue handler ends.

AMQ8919 There are no matching WebSphere MQ AMQ8A0F (iSeries) Work with MQ Queues
queue manager names.
Severity: 30 : Severe error AMQ8A10 (iSeries) Change MQ Process
AMQ8934 (iSeries) Message . . . . : AMQ8A11 (iSeries) Copy MQ Process

AMQ8A12 (iSeries) Create MQ Process
AMQ8935 (iSeries) Cause . . . . . :
AMQ8A13 (iSeries) Delete MQ Process
AMQ8A14 (iSeries) Display MQ Process

AMQ8936 (iSeries) Recovery . . . :
AMQ8A15 (iSeries) Work with MQ Processes
AMQ8937 (iSeries) Technical Description . . . . . . . . :

AMQ8A16 (iSeries) Start MQ Command Server
AMQ8A17 (iSeries) End MQ Command Server
AMQ8A01 (iSeries) Create Message Queue Manager
AMQ8A18 (iSeries) Display MQ Command Server
AMQ8A02 (iSeries) Delete Message Queue Manager
AMQ8A19 (iSeries) Set MQ
AMQ8A04 (iSeries) Work with MQ Messages
AMQ8A20 (iSeries) Quiesce Message Queue
AMQ8A05 (iSeries) Change Message Queue Managers
Manager
AMQ8A21 (iSeries) Quiesce Retry Delay
AMQ8A06 (iSeries) Display Message Queue
Manager
AMQ8A23 (iSeries) Work with Queue Status
AMQ8A07 (iSeries) End Message Queue Manager

AMQ8A30 (iSeries) Create MQ Channel
AMQ8A08 (iSeries) Start Message Queue Manager

AMQ8A31 (iSeries) Display MQ Channel
AMQ8A09 (iSeries) Change MQ Queue

AMQ8A32 (iSeries) Start MQ Listener
AMQ8A0A (iSeries) Clear MQ Queue

AMQ8A33 (iSeries) Ping MQ Channel
AMQ8A0B (iSeries) Copy MQ Queue

AMQ8A34 (iSeries) Delete MQ Channel
AMQ8A0C (iSeries) Create MQ Queue

AMQ8A36 (iSeries) Work with MQ Channels
AMQ8A0D (iSeries) Delete MQ Queue

AMQ8A37 (iSeries) Change MQ Channel
AMQ8A0E (iSeries) Display MQ Queue

AMQ8A38 (iSeries) Copy MQ Channel

AMQ8A39 (iSeries) Reset MQ Channel AMQ8A5B (iSeries) Remove Queues
AMQ8A40 (iSeries) End MQ Channel AMQ8A5C (iSeries) Refresh Repository
AMQ8A41 (iSeries) Start MQ Channel AMQ8A5D (iSeries) IP Address
AMQ8A42 (iSeries) Start MQ Channel Initiator AMQ8A60 (iSeries) Cluster Name
AMQ8A43 (iSeries) Grant MQ Object Authority AMQ8A61 (iSeries) Cluster Name List
AMQ8A44 (iSeries) Revoke MQ Object Authority AMQ8A62 (iSeries) Mode Name
AMQ8A45 (iSeries) Display MQ Object Authority AMQ8A63 (iSeries) Password
AMQ8A46 (iSeries) Display MQ Object Names AMQ8A64 (iSeries) Transaction Program Name
AMQ8A47 (iSeries) Refresh WebSphere MQ AMQ8A65 (iSeries) User Profile

Authority
AMQ8A66 (iSeries) Network Connection Priority
AMQ8A48 (iSeries) Work with MQ Authority
AMQ8A67 (iSeries) Batch Interval
AMQ8A49 (iSeries) Start MQ Service
AMQ8A68 (iSeries) Batch Interval
AMQ8A50 (iSeries) End MQ Service
AMQ8A69 (iSeries) Cluster Workload Exit Data
AMQ8A51 (iSeries) Connect MQ
AMQ8A6A (iSeries) Cluster Workload Exit
AMQ8A52 (iSeries) Disconnect MQ
AMQ8A6B (iSeries) Repository Cluster
AMQ8A53 (iSeries) Work with MQ Authority Data
AMQ8A6C (iSeries) Repository Cluster Namelist
AMQ8A54 (iSeries) Resolve MQ Channel
AMQ8A6D (iSeries) Cluster Workload Exit Data
AMQ8A55 (iSeries) Work with MQ Channel Status Length
AMQ8A56 (iSeries) SSL Client Authentication AMQ8A6E (iSeries) Maximum Message Length
AMQ8A57 (iSeries) SSL CipherSpec AMQ8A6F (iSeries) Default Queue Manager
AMQ8A58 (iSeries) SSL Peer name AMQ8A70 (iSeries) Default Binding
AMQ8A59 (iSeries) Local communication address AMQ8A71 (iSeries) Channel Table
AMQ8A5A (iSeries) Batch Heartbeat Interval AMQ8A72 (iSeries) Change MQ Namelist

AMQ8A73 (iSeries) List of Names AMQ8A8A (iSeries) Display Journal Receiver Data
AMQ8A74 (iSeries) Namelist AMQ8A8B (iSeries) Start MQ Pub/Sub Broker
AMQ8A75 (iSeries) Create MQ Namelist AMQ8A8C (iSeries) End MQ Pub/Sub Broker
AMQ8A76 (iSeries) Recreate MQ Object AMQ8A8D (iSeries) Display MQ Pub/Sub Broker
AMQ8A77 (iSeries) Record MQ Object Image AMQ8A8E (iSeries) Clear MQ Pub/Sub Broker
AMQ8A78 (iSeries) Start WebSphere MQ Commands AMQ8A8F (iSeries) Delete MQ Pub/Sub Broker
AMQ8A7A (iSeries) Copy MQ Namelist AMQ8B01 (iSeries) Message Queue Manager name
AMQ8A7B (iSeries) From Namelist AMQ8B02 (iSeries) Text ’description’
AMQ8A7C (iSeries) To Namelist AMQ8B03 (iSeries) Trigger interval
AMQ8A7D (iSeries) Delete MQ Namelist AMQ8B04 (iSeries) Undelivered message queue
AMQ8A7E (iSeries) Display MQ Namelist AMQ8B05 (iSeries) Default transmission queue
AMQ8A7F (iSeries) Work with MQ Namelist AMQ8B06 (iSeries) Maximum handle limit
AMQ8A80 (iSeries) Group Profile AMQ8B07 (iSeries) Maximum uncommitted

messages
AMQ8A81 (iSeries) User Profile
AMQ8B08 (iSeries) Queue name
AMQ8A82 (iSeries) Service Component
AMQ8B09 (iSeries) Output
AMQ8A83 (iSeries) Work with MQ Queue Manager
AMQ8B0A (iSeries) Library
AMQ8A84 (iSeries) Work with MQ Clusters
AMQ8B0B (iSeries) File to receive output
AMQ8A85 (iSeries) Start MQ Trigger Monitor
AMQ8B0C (iSeries) OPTION(*MVS) not valid
without specifying a value for WAIT.
AMQ8A86 (iSeries) End MQ Listeners
AMQ8A87 (iSeries) Work with MQ Transactions Explanation: The OPTION(*MVS) parameter may not
be specified without specifying a value for the WAIT
parameter.
AMQ8A88 (iSeries) Resolve MQ Transaction
Response: Remove the OPTION(*MVS) parameter
from the command or, specify a value for the WAIT
AMQ8A89 (iSeries) Work with MQ Cluster Queues
parameter. Then try the command again.

AMQ8B0D (iSeries) Member to receive output AMQ8B23 (iSeries) Backout requeue name
AMQ8B0E (iSeries) Replace or add records AMQ8B24 (iSeries) Initiation queue
AMQ8B0F (iSeries) Option AMQ8B25 (iSeries) Usage
AMQ8B10 (iSeries) Mode AMQ8B26 (iSeries) Definition type
AMQ8B11 (iSeries) Put enabled AMQ8B27 (iSeries) Target queue
AMQ8B12 (iSeries) Default message priority AMQ8B28 (iSeries) Remote queue
AMQ8B13 (iSeries) Default message persistence AMQ8B29 (iSeries) Remote Message Queue Manager
AMQ8B14 (iSeries) Process name AMQ8B2A (iSeries) Transmission queue
AMQ8B15 (iSeries) Triggering enabled AMQ8B2B (iSeries) From queue name
AMQ8B16 (iSeries) Get enabled AMQ8B2C (iSeries) To queue name
AMQ8B17 (iSeries) Sharing enabled AMQ8B2D (iSeries) Replace
AMQ8B18 (iSeries) Default share option AMQ8B2E (iSeries) Queue type
AMQ8B19 (iSeries) Message delivery sequence AMQ8B2F (iSeries) Application type
AMQ8B1A (iSeries) Harden backout count AMQ8B30 (iSeries) Application identifier
AMQ8B1B (iSeries) Trigger type AMQ8B31 (iSeries) User data
AMQ8B1C (iSeries) Trigger depth AMQ8B32 (iSeries) Environment data
AMQ8B1D (iSeries) Trigger message priority AMQ8B33 (iSeries) From process
AMQ8B1E (iSeries) Trigger data AMQ8B34 (iSeries) To process
AMQ8B1F (iSeries) Retention interval AMQ8B36 (iSeries) Job name
AMQ8B20 (iSeries) Maximum queue depth AMQ8B37 (iSeries) Number
AMQ8B21 (iSeries) Maximum message length AMQ8B3A (iSeries) Convert message
AMQ8B22 (iSeries) Backout threshold AMQ8B3B (iSeries) Replace to member

AMQ8B3C (iSeries) Heartbeat interval AMQ8B59 (iSeries) Automatic Channel Definition
AMQ8B3D (iSeries) Non Persistent Message Speed AMQ8B5A (iSeries) Auto Chan. Def. events enabled
AMQ8B3E (iSeries) Force AMQ8B5B (iSeries) Auto Chan. Def. exit program
AMQ8B3F (iSeries) No Jobs to display AMQ8B5C (iSeries) Redefine system objects
AMQ8B41 (iSeries) Queue definition scope AMQ8B5D (iSeries) Wait time
AMQ8B42 (iSeries) Queue depth high threshold AMQ8B5E (iSeries) Startup Status Detail
AMQ8B43 (iSeries) Queue depth low threshold AMQ8B60 (iSeries) Transaction type
AMQ8B44 (iSeries) Queue full events enabled AMQ8B61 (iSeries) Log recovery events enabled
AMQ8B45 (iSeries) Queue high events enabled AMQ8B62 (iSeries) IP protocol
AMQ8B46 (iSeries) Queue low events enabled AMQ8B63 (iSeries) Configuration events enabled
AMQ8B47 (iSeries) Service interval AMQ8B64 (iSeries) Refresh Message Queue Manager
AMQ8B48 (iSeries) Service interval events AMQ8B65 (iSeries) Refresh Type
AMQ8B49 (iSeries) Distribution list support AMQ8B66 (iSeries) Include Interval
AMQ8B4A (iSeries) Parent Message Queue Manager AMQ8B67 (iSeries) WebSphere MQ queue manager
refreshed.
AMQ8B4B (iSeries) Break Parent link
AMQ8B68 (iSeries) Channel events enabled
AMQ8B4C (iSeries) Child Message Queue Manager
AMQ8B69 (iSeries) SSL events enabled
AMQ8B53 (iSeries) Authorization events enabled
AMQ8B6A (iSeries) Filter command
AMQ8B54 (iSeries) Inhibit events enabled
AMQ8B6B (iSeries) Filter keyword
AMQ8B55 (iSeries) Local error events enabled
AMQ8B6C (iSeries) Filter operator
AMQ8B56 (iSeries) Remote error events enabled
AMQ8B6D (iSeries) Filter value
AMQ8B57 (iSeries) Performance events enabled
AMQ8B6E (iSeries) Filter value <insert_5> not valid
with keyword <insert_4>.
AMQ8B58 (iSeries) Start and stop events enabled
Explanation: The filter value <insert_5> is not valid
with the keyword <insert_4>.
Response: Specify a valid filter value for the keyword
<insert_4>.

AMQ8B70 (iSeries) Change MQ AuthInfo object AMQ8C09 (iSeries) Message channel agent
AMQ8B71 (iSeries) Copy MQ AuthInfo object AMQ8C10 (iSeries) Message channel agent user ID
AMQ8B72 (iSeries) Create MQ AuthInfo object AMQ8C12 (iSeries) Batch size
AMQ8B73 (iSeries) Delete MQ AuthInfo object AMQ8C13 (iSeries) Disconnect interval
AMQ8B74 (iSeries) Display MQ AuthInfo object AMQ8C14 (iSeries) Short retry count
AMQ8B75 (iSeries) From AuthInfo name AMQ8C15 (iSeries) Short retry interval
AMQ8B76 (iSeries) AuthInfo name AMQ8C16 (iSeries) Long retry count
AMQ8B77 (iSeries) AuthInfo type AMQ8C17 (iSeries) Long retry interval
AMQ8B78 (iSeries) User name AMQ8C18 (iSeries) Security exit
AMQ8B79 (iSeries) User password AMQ8C19 (iSeries) Message exit
AMQ8B7A (iSeries) Work with AuthInfo objects AMQ8C20 (iSeries) Send exit
AMQ8B7B (iSeries) To AuthInfo name AMQ8C21 (iSeries) Receive exit
AMQ8B80 (iSeries) Change MQ Processor Allowance AMQ8C22 (iSeries) SSL CRL Namelist
AMQ8B81 (iSeries) Display MQ Processor AMQ8C23 (iSeries) SSL Key Repository

Allowance
AMQ8C24 (iSeries) Put authority
AMQ8B82 (iSeries) Sufficient Licence Units
AMQ8C25 (iSeries) Sequence number wrap
AMQ8C01 (iSeries) From channel
AMQ8C27 (iSeries) Transport type
AMQ8C02 (iSeries) Channel name
AMQ8C28 (iSeries) Data count
AMQ8C03 (iSeries) Channel type
AMQ8C29 (iSeries) Count
AMQ8C04 (iSeries) SSL key reset count
AMQ8C30 (iSeries) To channel
AMQ8C05 (iSeries) Remote queue manager
AMQ8C31 (iSeries) Message sequence number
AMQ8C07 (iSeries) Transmission queue
AMQ8C32 (iSeries) SSL Cryptographic Hardware
AMQ8C08 (iSeries) Connection name

AMQ8C33 (iSeries) Security exit user data AMQ8C55 (iSeries) Suspend Cluster Queue Manager
AMQ8C34 (iSeries) Send exit user data AMQ8C56 (iSeries) Reset Cluster
AMQ8C35 (iSeries) Receive exit user data AMQ8C57 (iSeries) Refresh MQ Cluster
AMQ8C36 (iSeries) Message exit user data AMQ8C58 (iSeries) Resume Cluster Queue Manager
AMQ8C37 (iSeries) Resolve option AMQ8C59 (iSeries) Action
AMQ8C38 (iSeries) Connection name AMQ8C5A (iSeries) Queue Manager Name for
removal
AMQ8C39 (iSeries) Transmission queue name
AMQ8C5B (iSeries) Work with MQ Listeners
AMQ8C40 (iSeries) SSL Repository Password
AMQ8C5C (iSeries) Queue Manager Id for removal
AMQ8C41 (iSeries) First Message
AMQ8C60 (iSeries) Display Cluster Message Queue
Manager
AMQ8C42 (iSeries) Maximum number of messages
AMQ8C61 (iSeries) Cluster Queue Manager name

AMQ8C43 (iSeries) Maximum message size
AMQ8C62 (iSeries) End MQ Listeners

AMQ8C44 (iSeries) Message retry exit
AMQ8C63 (iSeries) Port number

AMQ8C45 (iSeries) Message retry exit data
AMQ8C64 (iSeries) Message channel agent Type

AMQ8C46 (iSeries) Number of message retries
AMQ8C65 (iSeries) Task user identifier

AMQ8C47 (iSeries) Message retry interval
AMQ8D01 (iSeries) Trace MQ

AMQ8C48 (iSeries) Coded Character Set
AMQ8D02 (iSeries) Trace option setting

AMQ8C49 (iSeries) Max message length
AMQ8D03 (iSeries) Trace level

AMQ8C50 (iSeries) Repository name
AMQ8D04 (iSeries) Trace types

AMQ8C51 (iSeries) Repository name list
AMQ8D05 (iSeries) Maximum storage to use

AMQ8C52 (iSeries) Cluster workload exit length
AMQ8D06 (iSeries) Trace early

AMQ8C53 (iSeries) Cluster workload exit
AMQ8D07 (iSeries) Exclude types

AMQ8C54 (iSeries) Cluster workload exit data
AMQ8D0A (iSeries) Output member options

AMQ8D10 (iSeries) Object name AMQ8D30 (iSeries) Keep Alive Interval
AMQ8D11 (iSeries) Object type
AMQ8D12 (iSeries) User names
AMQ8D13 (iSeries) Authority
AMQ8D14 (iSeries) Authorization list
AMQ8D15 (iSeries) Reference object name
AMQ8D16 (iSeries) Reference object type
AMQ8D17 (iSeries) Object name
AMQ8D18 (iSeries) Process name
AMQ8D19 (iSeries) Queue name
AMQ8D1A (iSeries) Queue Manager Library
AMQ8D1B (iSeries) ASP Number
AMQ8D1C (iSeries) Journal receiver threshold
AMQ8D20 (iSeries) Channel name
AMQ8D22 (iSeries) Cluster name
AMQ8D23 (iSeries) Cluster namelist name
AMQ8D24 (iSeries) User name
AMQ8D25 (iSeries) Channel status
AMQ8D26 (iSeries) End connected jobs
AMQ8D27 (iSeries) Timeout interval (seconds)
AMQ8D28 (iSeries) Object/Profile name
AMQ8D29 (iSeries) Service Component name

Chapter 7. 9000-9999 - Remote
messages.
secondary response code <insert_1> in the

AMQ9001 Channel <insert_3> ended normally.
ExitResponse2 field of the channel exit parameters
Severity: 0 : Information (MQCXP) that is not valid. Message AMQ9190 is issued
giving more details, and the channel stops.
Explanation: Channel <insert_3> ended normally.
Response: Investigate why the user exit program set a
Response: None.
secondary response code that is not valid.
AMQ9002 Channel <insert_3> is starting.

AMQ9184 The exit buffer address set by the exit is
Severity: 0 : Information not valid.
Explanation: Channel <insert_3> is starting. Severity: 30 : Severe error
Response: None. Explanation: The user exit <insert_3> returned an
address <insert_1> for the exit buffer that is not valid,
when the secondary response code in the
AMQ9003 (iSeries) Channel <insert_3> last message ExitResponse2 field of the channel exit parameters
sequence number is <insert_1>. (MQCXP) is set to MQXR2_USE_EXIT_BUFFER.
Severity: 0 : Information Message AMQ9190 is issued giving more details, and
the channel stops.
Explanation: Channel <insert_3> last message
sequence number is <insert_1>. Response: Investigate why the user exit program set
an exit buffer address that is not valid. The most likely
Response: None. cause is the failure to set a value, so that the value is 0.
AMQ9004 (iSeries) Channel <insert_3> status AMQ9185 The exit space set by the exit is not
information. valid.
Severity: 0 : Information Severity: 30 : Severe error
Explanation: Channel <insert_3> status information: Explanation: The user exit <insert_3> returned an exit
Number of Messages in Doubt - <insert_1> In Doubt space value <insert_1> that is not valid in the ExitSpace
Sequence Number - <insert_2> In Doubt Logic Unit of field of the channel exit parameters (MQCXP). Message
Work ID - <insert_4> AMQ9190 is issued giving more details, and the
Response: None. channel stops.
Response: Investigate why the user exit program set
AMQ9181 The response set by the exit is not valid. an exit space value that is not valid. Correct the error.

AMQ9186 Too much exit space reserved by send
Explanation: The user exit <insert_3> returned a exits.
response code <insert_1> that is not valid in the
ExitResponse field of the channel exit parameters Severity: 30 : Severe error
(MQCXP). Message AMQ9190 is issued giving more Explanation: At exit initialization the send exits in the
details, and the channel stops. send exit chain for channel <insert_3> returned values
Response: Investigate why the user exit program set a in the ExitSpace field of the channel exit parameters
response code that is not valid. (MQCXP). The total of these ExitSpace values is
<insert_1>. The maximum number of bytes that can be
sent in a single transmission is <insert_2>. Room must
AMQ9182 The secondary response set by the exit be left for at least 1024 bytes of message data in each
is not valid. transmission. So too much exit space has been reserved
Severity: 30 : Severe error by the send exits. The channel stops.
Explanation: The user exit <insert_3> returned a Response: Investigate why the send exit programs set

exit space values that are too large. Correct the error.
AMQ9195 Data length larger than maximum
segment length.
AMQ9187 The header compression value set by
the exit is not valid.
Explanation: The data length <insert_1> set by send
exit <insert_3> is larger than the maximum segment
Explanation: The user exit <insert_3> returned a length (<insert_2>). The maximum segment length is
header compression value <insert_1> in the the maximum number of bytes that can be sent in a
CurHdrCompression field of the channel exit single transmission minus the user exit space required
parameters (MQCXP) that was not one of the by all the send exits subsequent to the current one in
negotiated supported values specified in the the send exit chain. Message AMQ9190 is issued giving
HdrCompList field of the channel description (MQCD). more details, and the channel stops.
Message AMQ9190 is issued giving more details, and
the channel stops.
data length that is not valid. Correct the error.
Response: Investigate why the user exit program
specified a header compression value that was not one
AMQ9196 Data length is larger than the agent
of the negotiated supported values.
buffer length.
AMQ9188 The message compression value set by
the exit is not valid. Explanation: The data length <insert_1> set by exit
<insert_3> is larger than the agent buffer length. The
user exit returned data in the supplied agent buffer, but
Explanation: The user exit <insert_3> returned a the length specified is greater than the length of the
message compression value <insert_1> in the buffer. Message AMQ9190 is issued giving more details,
CurMsgCompression field of the channel exit and the channel stops.
parameters (MQCXP) that was not one of the
negotiated supported values specified in the
data length that is not valid. Correct the error.
MsgCompList field of the channel description (MQCD).
the channel stops. AMQ9197 Data length is larger than the exit buffer
length.
Response: Investigate why the user exit program
specified a message compression value that was not Severity: 30 : Severe error
one of the negotiated supported values.
Explanation: The data length <insert_1> set by exit
<insert_3> is larger than the exit buffer length. The user
AMQ9189 The data length set by the exit is not exit returned data in the supplied exit buffer, but the
valid. length specified is greater than the length of the buffer.
the channel stops.
Explanation: The user exit <insert_3> returned a data
length value <insert_1> that was not greater than zero.
data length that is not valid.
the channel stops.
AMQ9201 Allocate failed to host <insert_3>.
data length that is not valid. Severity: 30 : Severe error
Explanation: The attempt to allocate a conversation
AMQ9190 Channel stopping because of an error in using <insert_4> to host <insert_3> was not successful.
the exit.
Response: The error may be due to an incorrect entry
Severity: 30 : Severe error in the <insert_4> parameters contained in the channel
definition to host <insert_3>. Correct the error and try
Explanation: The user exit <insert_3>, invoked for
again. If the error persists, record the error values and
channel <insert_4> with id <insert_1> and reason
contact your systems administrator. The return code
<insert_2>, returned values that are not valid, as
from the <insert_4><insert_5> call was <insert_1>
reported in the preceding messages. The channel stops.
(X<insert_2>). It may be possible that the listening
Response: Investigate why the user exit program set program at host <insert_3> is not running. If this is the
values that are not valid. case, perform the relevant operations to start the
listening program for protocol <insert_4> and try again.

<insert_3>.
AMQ9202 Remote host <insert_3> not available,
If the conversation uses LU 6.2, it is possible that either
retry later.
the User ID or Password supplied to the remote host is
Severity: 30 : Severe error incorrect.
If the conversation uses TCP/IP, it is possible that the
Explanation: The attempt to allocate a conversation
remote host does not recognize the local host as a valid
using <insert_4> to host <insert_3> was not successful.
host.
However the error may be a transitory one and it may
The return code from the <insert_4><insert_5> call was
be possible to successfully allocate a <insert_4>
<insert_1> X(<insert_2>).
conversation later.
Record the error values and tell the systems
Response: Try the connection again later. If the failure administrator.
persists, record the error values and contact your
systems administrator. The return code from <insert_4>
AMQ9205 The host name supplied is not valid.
is <insert_1> (X<insert_2>). The reason for the failure
may be that this host cannot reach the destination host. Severity: 30 : Severe error
It may also be possible that the listening program at
Explanation: The supplied <insert_4> host name
host <insert_3> was not running. If this is the case,
<insert_3> could not be resolved into a network
perform the relevant operations to start the <insert_4>
address. Either the name server does not contain the
listening program, and try again.
host, or the name server was not available.
Response: Check the <insert_4> configuration on your
AMQ9203 A configuration error for <insert_4>
host.
occurred.
AMQ9206 Error sending data to host <insert_3>.
Explanation: Error in configuration for
communications to host <insert_3>. Allocation of a
<insert_4> conversation to host <insert_3> was not Explanation: An error occurred sending data over
possible. <insert_4> to <insert_3>. This may be due to a
Response: The configuration error may be one of the
following: Response: The return code from the
1.If the communications protocol is LU 6.2, it may be <insert_4><insert_5> call was <insert_1> X(<insert_2>).
that one of the transmission parameters (Mode, or TP Record these values and tell your systems
Name) is incorrect. Correct the error and try again. The administrator.
mode name should be the same as the mode defined
on host <insert_3>. The TP name on <insert_3> should
be defined. AMQ9207 The data received from host <insert_3>
2.If the communications protocol is LU 6.2, it may be is not valid.
that an LU 6.2 session has not been established. Contact Severity: 30 : Severe error
your systems administrator.
3.If the communications protocol is TCP/IP, it may be Explanation: Incorrect data format received from host
that the host name specified is incorrect. Correct the <insert_3> over <insert_4>. It may be that an unknown
error and try again. host is attempting to send data. An FFST file has been
4.If the communications protocol is TCP/IP, it may be generated containing the invalid data received.
that the host name specified cannot be resolved to a Response: Tell the systems administrator.
network address. The host name may not be in the
nameserver.
The return code from the <insert_4><insert_5> call was AMQ9208 Error on receive from host <insert_3>.
<insert_1> (X<insert_2>). Severity: 30 : Severe error
Record the error values and tell the system
administrator. Explanation: An error occurred receiving data from
<insert_3> over <insert_4>. This may be due to a
AMQ9204 Connection to host <insert_3> rejected.
Response: The return code from the
Severity: 30 : Severe error <insert_4><insert_5> call was <insert_1> (X<insert_2>).
Explanation: Connection to host <insert_3> over Record these values and tell the systems administrator.
<insert_4> was rejected.
Response: The remote system may not be configured
to allow connections from this host. Check the
<insert_4> listener program has been started on host
Chapter 7. 9000-9999 - Remote 205

Response: Check the channel definition file. It may be
AMQ9209 Connection to host <insert_3> closed.
that the communications protocol entered is not a
Severity: 30 : Severe error currently supported one.
Explanation: An error occurred receiving data from
<insert_3> over <insert_4>. The connection to the AMQ9215 Communications subsystem unavailable.
remote host has unexpectedly terminated.
Response: Tell the systems administrator.
Explanation: An attempt was made to use the
communications subsystem, but it has not been started.
AMQ9210 Remote attachment failed.
Response: Start the communications subsystem, and
Severity: 30 : Severe error rerun the program.
Explanation: There was an incoming attachment from
a remote host, but the local host could not complete the AMQ9216 Usage: <insert_3> [-m QMgrName] [-n
bind. TPName]
Response: The return code from the Severity: 20 : Error
<insert_4><insert_5> call was <insert_1> (X<insert_2>).
Explanation: Values passed to the responder channel
Record these values and tell the systems administrator
program are not valid. The parameters that are not
who should check the <insert_4> configuration.
valid are as follows :-
<insert_4>
AMQ9211 Error allocating storage. The responder channel program exits.
Severity: 30 : Severe error Response: Correct the parameters passed to the
channel program and retry the operation.
Explanation: The program was unable to obtain
enough storage.
AMQ9216 (AIX) Usage: <insert_3> [-m QMgrName]
Response: Stop some programs which are using
storage and retry the operation. If the problem persists Severity: 20 : Error
Explanation: Values passed to the responder channel
program are not valid. The parameters that are not
AMQ9212 A TCP/IP socket could not be allocated. valid are as follows :-
<insert_4>
The responder channel program exits.
Explanation: A TCP/IP socket could not be created,
Response: Correct the parameters passed to the
possibly because of a storage problem.
channel program and retry the operation.
Response: The return code from the
AMQ9216 (HP-UX) Usage: <insert_3> [-m
Try the program again. If the failure persists, record the
QMgrName]
error values and tell the systems administrator.
AMQ9213 A communications error for <insert_4> Explanation: Values passed to the responder channel
occurred. program are not valid. The parameters that are not
valid are as follows :-
<insert_4>
Explanation: An unexpected error occurred in The responder channel program exits.
communications.
Response: The return code from the channel program and retry the operation.
Record these values and tell the systems administrator.
AMQ9217 The TCP/IP listener program could not
be started.
AMQ9214 Attempt to use an unsupported
communications protocol.
Explanation: An attempt was made to start a new
instance of the listener program, but the program was
Explanation: An attempt was made to use an rejected.
unsupported communications protocol type <insert_2>.
Response: The failure could be because either the

subsystem has not been started (in this case you should communication parameters. Default values will be
start the subsystem), or there are too many programs used.
waiting (in this case you should try to start the listener
Response: None.
program later).
AMQ9223 Enter a protocol type.

AMQ9218 The <insert_4> listener program could
not bind to port number <insert_1>. Severity: 30 : Severe error
Severity: 30 : Severe error Explanation: The operation you are performing
requires that you enter the type of protocol.
Explanation: An attempt to bind the <insert_4> socket
to the listener port was unsuccessful. Response: Add the protocol parameter and retry the
operation.
Response: The failure could be due to another
program using the same port number. The return code
from the <insert_3> call for port <insert_5><insert_1> AMQ9224 Unexpected token detected.
was <insert_2>. Record these values and tell the
systems administrator. Severity: 30 : Severe error
Explanation: On line <insert_1> of the INI file,
AMQ9219 The TCP/IP listener program could not keyword <insert_3> was read when a keyword was
create a new connection for the expected.
incoming conversation. Response: Correct the file and retry the operation.
Explanation: An attempt was made to create a new AMQ9224 (Windows) Unexpected token detected.
socket because an attach request was received, but an Severity: 30 : Severe error
error occurred.
Explanation: Keyword <insert_3> was read when a
Response: The failure may be transitory, try again keyword was expected.
later. If the problem persists, record the return code
<insert_1> and tell the systems administrator. It may be Response: Correct the configuration data and retry the
necessary to free some jobs, or restart the operation.
communications system.
AMQ9225 File syntax error.
AMQ9220 The <insert_4> communications program Severity: 30 : Severe error
could not be loaded.
Explanation: A syntax error was detected on line
Severity: 30 : Severe error <insert_1> while processing the INI file.
Explanation: The attempt to load the <insert_4> Response: Correct the problem and retry the
library or procedure <insert_3> failed with error code operation.
<insert_1>.
Response: Either the library must be installed on the AMQ9225 (Windows) File syntax error.
system or the environment changed to allow the
program to locate it. Severity: 30 : Severe error
Explanation: A syntax error was detected while
AMQ9221 Unsupported protocol was specified. processing the configuration data.
Severity: 30 : Severe error Response: Correct the problem and retry the
operation.
Explanation: The specified value of <insert_3> was not
recognized as one of the protocols supported.
AMQ9226 Usage: <insert_3> [-m QMgrName] -t
Response: Correct the parameter and retry the (TCP | LU62 | NETBIOS | SPX)
operation. [ProtocolOptions]
AMQ9222 Cannot find the configuration file.
Explanation: Values passed to the listener program
Severity: 10 : Warning were invalid.
Explanation: The configuration file <insert_3> cannot The parameter string passed to this program is as
be found. This file contains default definitions for follows:
[-m QMgrName] ( -t TCP [-p Port] |
Chapter 7. 9000-9999 - Remote 207

-t LU62 [-n TPName] | responder program later). The <insert_5> reason code
-t NETBIOS [-l LocalName] [-e Names] [-s Sessions] was <insert_1>.
[-o Commands] [-a Adaptor] |
-t SPX [-x Socket])
AMQ9229 The application has been ended.
Default values will be used for parameters not
supplied. Severity: 30 : Severe error
Response: Correct the parameters passed to the Explanation: You have issued a request to end the
listener program and retry the operation. application.
Response: None.
AMQ9226 (AIX) Usage: <insert_3> [-m QMgrName] -t
TCP [ProtocolOptions]
AMQ9230 An unexpected <insert_4> event
Severity: 10 : Warning occurred.
Explanation: Values passed to the listener program Severity: 30 : Severe error
were invalid.
The parameter string passed to this program is as Explanation: During the processing of network events,
follows: an unexpected event <insert_1> occurred.
[-m QMgrName] -t TCP [-p Port] Response: None.
supplied.
AMQ9231 The supplied parameter is not valid.
listener program and retry the operation. Severity: 30 : Severe error
Explanation: The value of the <insert_4> <insert_5>
AMQ9226 (Unix) Usage: <insert_3> [-m QMgrName] parameter has the value <insert_3>. This value has
-t TCP [ProtocolOptions] either not been specified or has been specified
incorrectly.
Response: Check value of the <insert_5> parameter
Explanation: Values passed to the listener program and correct it if necessary. If the fault persists, record
were invalid. the return code (<insert_1>,<insert_2>) and <insert_4>
The parameter string passed to this program is as and tell the systems administrator.
follows:
[-m QMgrName] -t TCP [-p Port]
Default values will be used for parameters not AMQ9232 No <insert_3> specified
supplied. Severity: 30 : Severe error
Response: Correct the parameters passed to the Explanation: The operation requires the specification
listener program and retry the operation. of the <insert_3> field.
Response: Specify the <insert_3> and retry the
AMQ9227 <insert_3> local host name not provided. operation.
Explanation: A name is required for the <insert_3> AMQ9233 Error creating <insert_3> thread.
process to register with the network. Severity: 30 : Severe error
Response: Add a local name to the configuration file Explanation: The process attempted to create a new
and retry the operation. thread. The most likely cause of this problem is a
shortage of an operating system resource (for example:
AMQ9228 The <insert_4> responder program could memory). Use any previous FFSTs to determine the
not be started. reason for the failure. The WebSphere MQ internal
return code describing the reason for the failure is
Severity: 30 : Severe error <insert_1>.
Explanation: An attempt was made to start an Response: Contact the systems administrator. If the
instance of the responder program, but the program problem persists contact your IBM support center.
was rejected.
Response: The failure could be because either the
subsystem has not been started (in this case you should
start the subsystem), or there are too many programs
waiting (in this case you should try to start the

program is as follows, default values being used for
AMQ9235 The supplied local communications
parameters not supplied: [-m QMgrName] -n TpName
address cannot be resolved.
-g Gateway-name
Explanation: The local communications address listener program and retry the operation.
(LOCLADDR) value <insert_3> cannot be resolved into
an IP address.
AMQ9240 An SPX socket was already in use.
Response: Enter a local communications address value
which can be resolved into an IP address, and try
again. Explanation: The Listener received return code
<insert_1> when attempting to open socket <insert_2>.
AMQ9236 The supplied Partner LU was invalid. Response: The specified socket is already in use by
another process. To use another socket specify another
socket on the command line to RUNMQLSR or update
Explanation: The <insert_4> Partner LU name the default in the qm.ini file.
<insert_3> was invalid.
Response: Either the Partner LU name was entered AMQ9240 (iSeries) An SPX socket was already in
incorrectly or it was not in the <insert_4> use.
communications configuration. Correct the error and
try again.
Explanation: The Listener received return code
<insert_1> when attempting to open socket <insert_2>.
AMQ9237 A configuration error for <insert_4>
occurred. Response: The specified socket is already in use by
another process. To use another socket specify another
socket on the command line to STRMQMLSR or update
Explanation: Allocation of a <insert_4> conversation to the default in the qm.ini file.
host <insert_3> was not possible. The configuration
error may be one of the following:
AMQ9240 (Windows) An SPX socket was already in
1. It may be that one of the transmission parameters
use.
(Mode, or TP Name) was incorrect. Correct the error
and try again. The mode name should be the same as Severity: 30 : Severe error
the mode defined on host <insert_3>. The TP name on
<insert_3> should be defined. Explanation: The listener received return code
2. It may be that an LU 6.2 session has not been <insert_1> when attempting to open socket <insert_2>.
established. Contact your systems administrator. Response: The specified socket is already in use by
The return code from <insert_4> is <insert_1> with another process. To use another socket, specify a
associated <insert_5> <insert_2>. different socket on the command line to the runmqlsr
Response: Record the error values and tell the system command, or update the default in the configuration
administrator. data.
AMQ9238 A communications error for <insert_4> AMQ9241 SPX is not available.

occurred. Severity: 30 : Severe error
Severity: 30 : Severe error Explanation: WebSphere MQ received return code
Explanation: An unexpected error occurred in <insert_1> when attempting to start SPX
communications. communications.
Response: The return code from the Response: Ensure that IPX/SPX support is installed
<insert_4><insert_3> call was <insert_1> with associated on the machine and that it is started before trying to
<insert_5> <insert_2>. start a WebSphere MQ SPX channel.
AMQ9239 Usage: <insert_3> [-m QMgrName] -n AMQ9242 SPX resource problem.

TpName -g Gateway-name Severity: 30 : Severe error
Severity: 10 : Warning Explanation: WebSphere MQ received return code
Explanation: Values passed to the listener program <insert_1> when attempting to start SPX
were invalid. The parameter string passed to this communications, indicating a resource problem.
Chapter 7. 9000-9999 - Remote 209

Response: Ensure that sufficient IPX/SPX resources directed at the port on which this listener is listening.
are available before commencing communications over
Response: An extra listener process should be started
IPX/SPX.
to listen on a different port. Some of the channels to the
queue manager should be redirected from the port on
AMQ9243 The queue manager <insert_3> does not which the existing listener is listening to the new port.
exist.
Severity: 30 : Severe error AMQ9247 SSPI Security: bad return from SSPI
call.
Explanation: You tried to perform an action against a
queue manager that does not exist. You may have Severity: 30 : Severe error
specified the wrong queue manager name.
Explanation: Channel <insert_3> has been closed
Response: If you specified the wrong name, correct because the SSPI channel exit received a bad return
the name and submit the command again. If the queue code from SSPI.
manager does not exist, create the queue manager and
Response: Consult the appropriate SSPI manuals to
submit the command again.
find out the meaning of status <insert_4> on call
<insert_5>, and correct the error.
AMQ9244 The default queue manager does not
exist.
AMQ9248 The program could not bind to a
Severity: 30 : Severe error <insert_3> socket.
Explanation: You tried to perform an action against a Severity: 30 : Severe error
queue manager that does not exist.
Explanation: The attempt to bind to socket <insert_4>
Response: Create the default queue manager and failed with return code <insert_1>. The failing
submit the command again. <insert_3> call was <insert_5>. The most likely cause of
this problem is incorrect configuration of the <insert_3>
local address or incorrect start and end port
AMQ9245 (Windows) Unable to obtain account
parameters.
details for channel MCA user ID.
Response: Contact the system administrator. If the
problem persists contact your IBM support center.
Explanation: WebSphere MQ was unable to obtain the
account details for MCA user ID <insert_3>. This user
AMQ9255 Listener already running.
ID was the MCA user ID for channel <insert_4> on
queue manager <insert_5> and may have been defined Severity: 30 : Severe error
in the channel definition, or supplied either by a
Explanation: The request to start the WebSphere MQ
channel exit or by a client.
listener failed because there is already a listener
Response: Ensure that the user ID is correct and that running against the specified network resources.
it is defined on the Windows local system, the local
Response: None.
domain or on a trusted domain. For a domain user ID,
ensure that all necessary domain controllers are
available. AMQ9259 Connection timed out from host
<insert_3>.
AMQ9246 The TCP/IP listener on port <insert_1> Severity: 30 : Severe error
could not start a new channel.
Explanation: A connection from host <insert_3> over
Severity: 30 : Severe error <insert_4> timed out.
Explanation: An attempt has been made to connect to Response: Check to see why data was not received in
the queue manager by starting a new channel within the expected time. Correct the problem. Reconnect the
the TCP/IP listener which is listening on port channel, or wait for a retrying channel to reconnect
<insert_1>. The maximum socket number which can be itself.
used by a channel running on this listener is <insert_2>.
A socket number beyond this maximum was allocated
for the new channel. This connection attempt has been AMQ9401 Channel <insert_3> autodefined.
rejected, but the listener continues to listen for further Severity: 0 : Information
connection requests. The socket number allocated for a
new listener channel is related to the number of Explanation: Channel <insert_3> which did not
channels currently running within that listener process. previously exist has been autodefined.
The problem has arisen because too many channels are Response: None.

3) Change this queue manager definition so that it is
AMQ9402 Autodefinition exit for Channel
not a full repository.
<insert_3> failed to load.
AMQ9407 Cluster queue <insert_3> is defined
Explanation: Autodefinition of Channel <insert_3> inconsistently.
failed because <insert_4> would not load.
Response: Ensure that the user exit is specified
Explanation: The definition of cluster queue
correctly in the queue manager definition, and that the
<insert_3> on the queue manager with UUID <insert_4>
user exit program is correct and available.
has different DEFPRTY, DEFPSIST and DEFBIND
values from the definition of the same cluster queue on
AMQ9403 Autodefinition of Channel <insert_3> the queue manager with UUID <insert_5>. Both
suppressed by user exit. definitions now exist in the local repository. All
definitions of the same cluster queue should be
identical. In particular, problems arise if your
Explanation: Autodefinition exit <insert_4> for applications rely on a queue default value which is
Channel <insert_3> returned a failure code. defined inconsistently to determine messaging
behavior. This applies, for example, if the applications
Response: None. open a cluster queue with option
MQOO_BIND_AS_Q_DEF. If different instances of the
AMQ9404 REFRESH CLUSTER REPOS(YES) queue have different DEFBIND values the behavior of
command processed, cluster <insert_4>, the message transfer differs depending on which
<insert_1> objects changed. instance of the queue is selected when it is opened. In
general the instance selected varies across opens.
Response: For each inconsistency decide which of the
Explanation: The queue manager successfully values is the correct one. Alter the definitions of cluster
processed a REFRESH CLUSTER command with the queue <insert_3> so that all definitions have correct
REPOS(YES) option for the indicated cluster. DEFPRTY, DEFPSIST and DEFBIND values.
Response: None.
AMQ9408 BIND_ON_OPEN messages for channel
AMQ9405 FORCEREMOVE QUEUES(YES) <insert_3> to dead-letter queue.
command processed, cluster <insert_3> Severity: 0 : Information
target <insert_4>.
Explanation: The remote CLUSRCVR for channel
Severity: 0 : Information <insert_3> was deleted while undelivered
Explanation: The repository queue manager BIND_ON_OPEN messages associated with that
successfully processed a RESET channel existed on the local
ACTION(FORCEREMOVE) command with the SYSTEM.CLUSTER.TRANSMIT.QUEUE. These
QUEUES(YES) option for the indicated cluster and messages could not be allocated to another channel
target queue manager. because they were put BIND_ON_OPEN, but were
very unlikely to ever flow along the channel with
Response: None. which they were associated as this has now been
deleted. An attempt has therefore been made to move
AMQ9406 REFRESH CLUSTER REPOS(YES) them from the transmission queue to the local
command failed, this queue manager is dead-letter queue. The MQDLH reason is
a full repository for cluster <insert_4>. MQFB_BIND_OPEN_CLUSRCVR_DEL. Note that any
internal WebSphere MQ Clustering messages for the
Severity: 30 : Severe error deleted channel will also have been removed from the
SYSTEM.CLUSTER.TRANSMIT.QUEUE (these are
Explanation: The repository queue manager could not
discarded) so the current depth of the queue may have
process a REFRESH CLUSTER command with the
decreased by more than the number of user messages
REPOS(YES) option for the indicated cluster, because
moved to the dead-letter queue.
the local queue manager provides full repository
management services for the cluster. The command is Response: Examine the contents of the dead-letter
ignored. queue. Each message is contained in an MQDLH
structure that includes the reason why it was written
Response: Either
and where it was originally addressed. Also look at
1) Reissue the command without REPOS(YES), or
previous error messages to see if the attempt to put
2) Issue the command on a queue manager which is
messages to the dead-letter queue failed.
not a full repository, or
Chapter 7. 9000-9999 - Remote 211

AMQ9409 Repository manager ended abnormally. AMQ9415 (iSeries) An internal error has occurred.
Explanation: The repository manager ended Explanation: Repository command unexpected,
abnormally. command code <insert_1>, cluster object <insert_3>,
sender <insert_4>
Response: Look at previous error messages for the
repository manager in the error files to determine the Response: Collect the items listed in the ’Problem
cause of the failure. determination’ section of the System Administration
manual and contact your IBM support center.
AMQ9410 Repository manager started
AMQ9416 Repository command processing error,
RC=<insert_2>, command code
Explanation: The repository manager started <insert_1>, cluster object <insert_3>,
successfully. sender <insert_4>.
Response: None. Severity: 30 : Severe error
Explanation: An internal error has occurred.
AMQ9411 Repository manager ended normally.
Response: Collect the items listed in the ’Problem
Severity: 0 : Information determination’ section of the System Administration
Explanation: The repository manager ended normally.
Response: None. AMQ9416 (iSeries) An internal error has occurred.
AMQ9412 Repository command received for
<insert_3>. Explanation: Repository command processing error,
RC=<insert_2>, command code <insert_1>, cluster object
Severity: 30 : Severe error <insert_3>, sender <insert_4>.
Explanation: The repository manager received a Response: Collect the items listed in the ’Problem
command intended for some other queue manager, determination’ section of the System Administration
whose identifier is <insert_3>. The command was sent manual and contact your IBM support center.
by the queue manager with identifier <insert_4>.
Response: Check the channel and cluster definitions AMQ9417 Manually defined CLUSSDR channels
of the sending queue manager. have been forcibly removed.
AMQ9413 Repository command format error,
command code <insert_1> Explanation: The administrator has asked for the
queue manager <insert_3> to be deleted, or forcibly
Severity: 30 : Severe error removed, but has not yet deleted the manually defined
Explanation: An internal error has occurred. CLUSSDR channels to <insert_3>. The auto-defined
channels to <insert_3> have been deleted, but
Response: Collect the items listed in the ’Problem <insert_3> continues to receive updates until the
determination’ section of the System Administration manually defined CLUSSDR channels have been
manual and contact your IBM support center. deleted.
Response: Delete the manually defined CLUSSDR
AMQ9415 Repository command unexpected, channels to <insert_3>.
command code <insert_1>, cluster object
<insert_3>, sender <insert_4>
AMQ9418 Only one repository for cluster
Severity: 30 : Severe error <insert_3>.
Explanation: An internal error has occurred. Severity: 0 : Information
Response: Collect the items listed in the ’Problem Explanation: The queue manager has received
determination’ section of the System Administration information about a cluster for which it is the only
manual and contact your IBM support center. repository.
Response: Alter the REPOS or REPOSNL attribute of
the queue manager, that is to have the second full

repository for the cluster, to specify the cluster name.
AMQ9426 Repository command recipient
unknown.
AMQ9419 No cluster-receiver channels for cluster
<insert_3>
Explanation: The repository manager tried to send a
command to another queue manager using channel
Explanation: The repository manager has received <insert_4>. The recipient queue manager, whose
information about a cluster for which no identifier is <insert_3>, could not be found. Command
cluster-receiver channels are known. code <insert_1>.
Response: Define cluster-receiver channels for the Response: Check the channel and cluster definitions
cluster on the local queue manager. of the sending and receiving queue managers.
AMQ9420 No repositories for cluster <insert_3>. AMQ9427 CLUSSDR channel does not point to a
repository queue manager.
Explanation: The queue manager has received
information about a cluster for which no repositories Explanation: A CLUSSDR channel must point to a
are known. queue manager that hosts repositories for all clusters of
which the channel is a member. In addition, the
Response: Alter the REPOS or REPOSNL attribute of CLUSRCVR for the channel must be a member of all
the queue manager, that is to have a full repository for the same clusters as the CLUSSDR channel. The queue
the cluster, to specify the cluster name. manager pointed to by CLUSSDR channel <insert_3>
does not meet these criteria for cluster <insert_4>. The
AMQ9421 Invalid cluster record action code remote queue manager has a QMID of <insert_5>.
detected Response: Check the definitions on the local and
Severity: 30 : Severe error remote queue managers to ensure that the CLUSSDR
channel points to a queue manager that hosts a
Explanation: An invalid record was read from the repository for the cluster, and that the CLUSRCVR for
SYSTEM.CLUSTER.REPOSITORY.QUEUE. An FFST the channel is a member of the cluster.
record has been generated containing the invalid
record. was
AMQ9428 Unexpected publication of a cluster
Response: Collect the items listed in the Problem queue object received.
Determination section of the System Administration
manual and contact your IBM support center. Severity: 30 : Severe error
Explanation: The local queue manager has received a
AMQ9422 Repository manager error, RC=<insert_1> publication of a cluster queue object from a remote
queue manager on cluster <insert_3>. The local queue
Severity: 30 : Severe error manager discards the request because it does not host a
Explanation: An internal error has occurred. repository for cluster <insert_3> and has not subscribed
to the published object. The remote CLUSSDR channel
Response: Collect the items listed in the ’Problem used to access the local queue manager has a channel
determination’ section of the System Administration name of <insert_4> and the remote queue manager has
manual and contact your IBM support center. a QMID of <insert_5>.
Response: Check the definitions on the local and
AMQ9425 An internal error has occurred. remote queue managers to ensure that the CLUSSDR
Severity: 30 : Severe error channel points to a repository queue manager for the
cluster.
Explanation: Repository command merge error,
command code <insert_1>, cluster object <insert_3>,
sender <insert_4> AMQ9429 Unexpected publication of a cluster
queue deletion received.
determination’ section of the System Administration Severity: 30 : Severe error
manual and contact your IBM support center. Explanation: The local queue manager has received a
publication of a cluster queue deletion from a remote
queue manager on cluster <insert_3>. The local queue
manager discards the request because it does not host a
repository for cluster <insert_3> and has not subscribed
Chapter 7. 9000-9999 - Remote 213

to the published object. The remote CLUSSDR channel remote queue managers to ensure that the CLUSSDR
used to access the local queue manager has a channel channel points to a repository queue manager for the
name of <insert_4> and the remote queue manager has cluster.
a QMID of <insert_5>.
Response: Check the definitions on the local and AMQ9433 CLUSRCVR must be in the same cluster
remote queue managers to ensure that the CLUSSDR as its matching CLUSSDR.
channel points to a repository queue manager for the
cluster.
Explanation: CLUSRCVR channel <insert_3> is not
defined as a member of cluster <insert_4>. The local
AMQ9430 Unexpected cluster queue manager
queue manager has received a command that indicates
publication received.
that CLUSSDR channel <insert_3> on the remote queue
Severity: 30 : Severe error manager with QMID <insert_5> is defined as a member
of cluster <insert_4>.
cluster queue manager publication on cluster Response: Alter the CLUSRCVR or CLUSSDR
<insert_3>. The local queue manager should not have definitions for channel <insert_3>, so that they are both
received the publication because it does not host a members of the same cluster.
repository for cluster <insert_3>, it has not subscribed
to information concerning the published object, and the
AMQ9434 Unrecognized message on <insert_3>.
published object does not match any of its CLUSSDRs.
The queue manager that sent the publication to the Severity: 30 : Severe error
local queue manager has QMID <insert_4> (note that
this is not necessarily the queue manager which Explanation: The repository manager found a message
originated the publication). CLUSSDR channel on one of its queues having, either a format that could
<insert_5> was used to send the publication. not be recognized, or that did not come from a queue
manager or repository manager. The message was put
Response: Check the CLUSSDR definition on the on the dead-letter queue.
sending queue manager to ensure that it points to a
repository queue manager for the cluster. Response: Examine the message on the dead-letter
queue to determine the originator of the message.
AMQ9431 Remote queue manager no longer hosts

a repository for cluster AMQ9435 Unable to put repository manager
message.
message from remote queue manager QMID <insert_3> Explanation: The repository manager tried to send a
indicating that it no longer hosts a repository for message to the
cluster <insert_4>. CLUSSDR channel <insert_5> is SYSTEM.CLUSTER.COMMAND.QUEUE on another
altered so that it can no longer be used to access queue queue manager whose identifier is <insert_3>, but the
manager <insert_3> within cluster <insert_4>. If the MQPUT call was unsuccessful. MQCC=<insert_1>,
local queue manager does not host a repository for MQRC=<insert_2>. Processing continues, but the
cluster <insert_4> the relevant subscriptions and repository information may be out of date.
publications are remade if possible. Response: Refer to the Application Programming
Response: None. Reference manual for information about MQCC
<insert_1> and MQRC <insert_2>. Check the channel
and cluster definitions on the local and target queue
AMQ9432 Query received by a non-repository managers, and ensure that the channels between them
queue manager are running. When the problem is corrected, the
repository information will normally be updated
automatically. The REFRESH CLUSTER command can
Explanation: The local queue manager has received a be used to ensure that the repository information is up
query from a remote queue manager on cluster to date.
<insert_3>. The local queue manager discards the query
because it does not host a repository for cluster
AMQ9436 Unable to send repository manager
<insert_3>. The remote CLUSSDR channel used to
message.
access the local queue manager has a channel name of
<insert_4> and the remote queue manager has a QMID Severity: 30 : Severe error
of <insert_5>.
Explanation: The repository manager tried to send a
Response: Check the definitions on the local and message to the

SYSTEM.CLUSTER.COMMAND.QUEUE on a queue guide and contact your IBM support center.
manager that has the full repository for the specified
cluster(<insert_3>), but the MQPUT call was
AMQ9440 Reset command failed.
unsuccessful. MQCC=<insert_1>, MQRC=<insert_2>.
Processing continues, but repository information may Severity: 0 : Information
be out of date.
Explanation: Reset Cluster(<insert_3>)
Response: Refer to the Application Programming Qmname(<insert_4>) command failed. To issue this
Reference manual for information about MQCC command, queue manager <insert_5> must be a
<insert_1> and MQRC <insert_2>. Check the channel repository for cluster <insert_3>. Alter the queue
and cluster definitions on the local and target queue manager attributes Repos, or Reposnl, to include cluster
managers, and ensure that the channels between them <insert_3> and retry the command.
are running. When the problem is corrected, the
repository information will normally be updated Response: None.
automatically. The REFRESH CLUSTER command can
be used to ensure that the repository information is up AMQ9441 Reset command processed.
to date.
AMQ9437 Unable to commit repository changes. Explanation: The reset Cluster(<insert_3>)

Qmname(<insert_4>) command has processed on this
Severity: 30 : Severe error repository and <insert_1> other queue managers have
Explanation: The repository manager tried to commit been sent notification.
some updates to the repository but was unsuccessful. Response: None.
Processing continues, but repository information may
be out of date.
AMQ9442 Refresh Cluster command processed.
Response: If this occurs when the repository manager
is stopping, this message can be ignored, because the Severity: 0 : Information
repository information will normally be updated Explanation: The Refresh Cluster(<insert_4>)
automatically when the repository manager is restarted. command caused <insert_1> objects to be refreshed and
If there is an isolated occurrence at other times, use the <insert_2> objects to be republished.
REFRESH CLUSTER command to bring the repository
information up to date. If the problem persists, contact Response: None.
your IBM support center for assistance.
AMQ9443 Suspend Qmgr Cluster command
AMQ9438 CONNAME could not be discovered for processed.
CLUSRCVR <insert_3>. Severity: 0 : Information
Severity: 30 : Severe error Explanation: The Suspend Qmgr Cluster command
Explanation: TCP/IP CLUSRCVR <insert_3> was completed. <insert_1> objects suspended.I n the case of
validly specified with a blank or absent CONNAME a name list the cluster name is the first name in the list.
parameter. However when the repository process, Response: None.
amqrrmfa, attempted to obtain the CONNAME (IP
address) for itself it was unable to. If there is an
existing matching CLUSRCVR object in the cache its AMQ9444 Resume Qmgr Cluster command
CONNAME is used. The CONNAME used was processed.
<insert_4>.
Response: Check the error log for a message arising
Explanation: The Resume Qmgr Cluster(<insert_4>)
from an associated TCP/IP call (gethostname,
command completed. <insert_1> objects resumed. In the
gethostbyname or inet_ntoa). Pass all the error
case of a name list the cluster name is the first name in
information to your systems administrator.
the list.
Response: None.
AMQ9439 Repository corruption: bad CLQMGR
object for channel <insert_3>.
AMQ9445 Error creating channel <insert_3>.
Explanation: An internal error has occurred.
Explanation: Channel <insert_4> tried to replace itself
by creating channel <insert_3>. The attempt to create
determination’ chapter in the System Administration
the channel was unsuccessful for the following reason:
Chapter 7. 9000-9999 - Remote 215

″<insert_5>″. A previous message may give further follows:
information. [-m QMgrName] -f OutputFile [-v OutputFileVersion]
where OutputFileVersion can be either 2 or 5 (5 is the
Response: Rectify the problem which prevented
default)
successful creation of channel <insert_3>. Restart
channel <insert_4>.
supplied.
AMQ9446 Error deleting channel <insert_3>.
channel table writer program and retry the operation.
Explanation: Channel <insert_3> tried to delete itself AMQ9453 FORCEREMOVE command failed,
after creating channel <insert_4> to replace it. The cluster <insert_3> target <insert_4> is not
attempt to delete the channel was unsuccessful for the unique.
following reason: ″<insert_5>″.
Response: If channel <insert_3> still exists rectify the
problem which prevented its deletion and then
process a RESET ACTION(FORCEREMOVE) command
manually delete the channel.
for the indicated cluster and target queue manager,
because there is more than one queue manager with
AMQ9447 Unable to backout repository changes. the specified name in the cluster. The command is
ignored.
Response: Reissue the command specifying the
Explanation: Following an error, the repository identifier (QMID) of the queue manager to be removed,
manager tried to backout some updates to the rather than its name.
repository, but was unsuccessful. The repository
manager terminates.
AMQ9455 FORCEREMOVE command failed,
Response: If the repository manager subsequently cluster <insert_3>, target <insert_4>, not
restarts successfully, this message can be ignored. If the found.
repository manager does not restart, contact your IBM
support center for assistance. Severity: 0 : Information
AMQ9448 Repository manager stopping because of process a RESET ACTION(FORCEREMOVE) command
errors. Restart in <insert_1> seconds. for the indicated cluster and target queue manager,
because no information about that queue manager was
Severity: 30 : Severe error found in the local repository. The command is ignored.
Explanation: A severe error, as reported in the Response: Reissue the command, specifying the
preceding messages, occurred during repository correct queue manager name or identifier.
manager processing. The repository manager was
unable to continue and terminates. The repository
manager will try to restart after the specified interval. AMQ9456 Update not received for queue
<insert_3>, queue manager <insert_4>
Response: Correct the problem reported in the from full repository for cluster
preceding messages. <insert_5>.
AMQ9449 Repository manager restarted.
Explanation: The repository manager detected a queue
Severity: 0 : Information that has been used in the last 30 days for which
Explanation: The repository manager restarted updated information should have been sent from a full
successfully following an error. repository. However, this has not occurred.
The repository manager will keep the information
Response: None. about this queue for a further 60 days.
Response: If the queue is still required, check that:
AMQ9450 Usage: <insert_3> [-m QMgrName] -f 1) The cluster channels to and from the full repository
OutputFile [-v OutputFileVersion] and the queue manager that hosts the queue, are able
Severity: 10 : Warning to run.
2) The repository managers running on these queue
Explanation: Values passed to the channel table writer managers have not ended abnormally.
program were invalid.
The parameter string passed to this program is as

Response: Look at previous error messages in the
AMQ9456 (iSeries) Update not received from full
error files to determine the error encountered by the
repository.
responder program.
Explanation: Update not received for queue AMQ9494 A protocol error was detected for
<insert_3>, queue manager <insert_4> from full channel <insert_3>.
repository for cluster <insert_5>.
The repository manager detected a queue that has been
used in the last 30 days for which updated information Explanation: During communications with the remote
should have been sent from a full repository. However, queue manager, a TCP/IP read and receive call
this has not occurred. returned EINTR, indicating that it had been
The repository manager will keep the information interrupted. Immediately after this the channel program
about this queue for a further 60 days. detected a protocol error. The failure type was
<insert_1> with associated data of <insert_2>.
Response: If the queue is still required, check that:
1) The cluster channels to and from the full repository Response: If you are running an AIX client you will
and the queue manager that hosts the queue, are able avoid problems arising from EINTRs on TCP/IP reads,
to run. by writing your application so that system calls
2) The repository managers running on these queue interrupted by signals are restarted. You must establish
managers have not ended abnormally. the signal handler with sigaction(2) and set the
SA_RESTART flag in the sa_flags field of the new
action structure. If you are running on a platform other
AMQ9457 Repository available, cluster <insert_4>,
than AIX, an AIX server, or an AIX client with an
channel <insert_5>, sender <insert_3>.
application that adheres to the restart guidelines
Severity: 0 : Information provided above, contact the systems administrator who
should examine the error logs to determine the cause of
Explanation: The repository queue manager received a
the failure.
command from another queue manager, whose
identifier is <insert_3>, reporting that it is again a
repository for cluster <insert_4>. The cluster-sender AMQ9495 The CLWL exit <insert_3> is inconsistent
channel <insert_5> is changed so that it can be used to with a dynamic cache.
access the other queue manager in relation to the the
cluster.
Explanation: When the CLWL exit <insert_3> was
Response: None.
called for the ExitReason MQXR_INIT, the value
<insert_1> was returned in the ExitResponse2 field.
AMQ9491 Transmission Queue <insert_3> set to This indicates the CLWL exit is incompatible with the
NOSHARE. Queue Manager cache type which is dynamic. Either
change the Queue Manager cache type to static (using
the Tuning Parameter, ClusterCacheType=STATIC) or
Explanation: The channel <insert_4> on queue rewrite the CLWL exit to be compatible with a dynamic
manager <insert_5> cannot start because this queue cache″. The CLWL exit has been suppressed.
manager has a setting for PipeLineLength greater than
Response: None.
1, and so multiple threads will run in this channel’s
MCA. Only the first thread would be able to open the
Transmission Queue <insert_3> because it is set to be AMQ9496 Channel ended by a remote exit.
non-shareable.
Response: Check the definition of the Transmission
Explanation: Channel program <insert_3> was ended
Queue <insert_3> on queue manager <insert_5> and set
because the channel exit at the remote end requested it.
it to be SHARE instead of NOSHARE. Alternatively,
you can set all channels on this queue manager to use Response: Examine the error logs at the remote end of
only a single thread, by using the PipeLineLength the channel to see the reason why the remote exit
parameter. ended the channel.
AMQ9492 The <insert_3> responder program AMQ9498 The MQCD structure supplied was not
encountered an error. valid.
Explanation: The responder program was started but Explanation: The value of the <insert_3> field has the
detected an error.
Chapter 7. 9000-9999 - Remote 217

value <insert_4>. This value is invalid for the operation using problem determination techniques. For example,
requested. look for FFST files, and examine the error logs on the
local and remote systems where there may be messages
Response: Change the parameter and retry the
explaining the cause of failure. More information may
operation.
be obtained by repeating the operation with tracing
enabled.
AMQ9499 A WebSphere MQ listener will end
shortly.
AMQ9504 A protocol error was detected for
Severity: 0 : Information channel <insert_3>.
Explanation: One listener detected in the system is Severity: 30 : Severe error
scheduled for shutdown.
Explanation: During communications with the remote
Response: None. queue manager, the channel program detected a
protocol error. The failure type was <insert_1> with
associated data of <insert_2>.
AMQ9500 No Repository storage
Response: Contact the systems administrator who
Severity: 10 : Warning should examine the error logs to determine the cause of
Explanation: An operation failed because there was no the failure.
storage available in the repository. An attempt was
made to allocate <insert_1> bytes from <insert_3>. AMQ9505 Channel sequence number wrap values
Response: Reconfigure the Queue Manager to allocate are different.
a larger repository. Severity: 30 : Severe error
Explanation: The sequence number wrap value for
AMQ9501 Usage: <insert_3> [-m QMgrName] -c channel <insert_3> is <insert_1>, but the value specified
ChlName. at the remote location is <insert_2>. The two values
Severity: 10 : Warning must be the same before the channel can be started.
Explanation: Values passed to the channel program Response: Change either the local or remote channel
are not valid. The parameter string passed to this definitions so that the values specified for the message
program is as follows :- [-m QMgrName] -c ChlName sequence number wrap values are the same.
supplied. AMQ9506 Message receipt confirmation failed.
Response: Correct the parameters passed to the Severity: 30 : Severe error
Channel program and retry the operation.
Explanation: Channel <insert_3> has ended because
the remote queue manager did not accept the last batch
AMQ9502 Type of channel not suitable for action of messages.
requested.
Response: The error log for the channel at the remote
Severity: 30 : Severe error site will contain an explanation of the failure. Contact
Explanation: The operation requested cannot be the remote Systems Administrator to resolve the
performed on channel <insert_3>. Some operations are problem.
only valid for certain channel types. For example, you
can only ping a channel from the end sending the AMQ9507 Channel <insert_3> is currently in-doubt.
message.
Response: Check whether the channel name is
specified correctly. If it is check that the channel has Explanation: The requested operation cannot complete
been defined correctly. because the channel is in-doubt with host <insert_4>.
Response: Examine the status of the channel, and
AMQ9503 Channel negotiation failed. either restart a channel to resolve the in-doubt state, or
use the RESOLVE CHANNEL command to correct the
Severity: 30 : Severe error problem manually.
Explanation: Channel <insert_3> between this machine
and the remote machine could not be established due
to a negotiation failure.
Response: Tell the systems administrator, who should
attempt to identify the cause of the channel failure

AMQ9508 Program cannot connect to the queue AMQ9513 Maximum number of channels reached.
manager.
Explanation: The maximum number of channels that
Explanation: The connection attempt to queue can be in use simultaneously has been reached. The
manager <insert_4> failed with reason code <insert_1>. number of permitted channels is a configurable
parameter in the queue manager configuration file.
Response: Ensure that the queue manager is available
and operational. Response: Wait for some of the operating channels to
close. Retry the operation when some channels are
available.
object.
AMQ9514 Channel <insert_3> is in use.
Explanation: The attempt to open either the queue or
queue manager object <insert_4> on queue manager Explanation: The requested operation failed because
<insert_5> failed with reason code <insert_1>. channel <insert_3> is currently active.
Response: Ensure that the queue is available and retry Response: Either end the channel manually, or wait
the operation. for it to close, and retry the operation.
AMQ9510 Messages cannot be retrieved from a AMQ9515 Channel <insert_3> changed.

queue.
Explanation: The statistics shown are for the channel
Explanation: The attempt to get messages from queue requested, but it is a new instance of the channel. The
<insert_4> on queue manager <insert_5> failed with previous channel instance has ended.
Response: None.
Response: If the reason code indicates a conversion
problem, for example
AMQ9516 File error occurred.
MQRC_SOURCE_CCSID_ERROR, remove the
message(s) from the queue. Otherwise, ensure that the Severity: 30 : Severe error
required queue is available and operational.
Explanation: The filesystem returned error code
<insert_1> for file <insert_3>.
AMQ9511 Messages cannot be put to a queue.
Response: Record the name of the file <insert_3> and
Severity: 30 : Severe error tell the systems administrator, who should ensure that
file <insert_3> is correct and available.
Explanation: The attempt to put messages to queue
<insert_4> on queue manager <insert_5> failed with
reason code <insert_1>. AMQ9516 (iSeries) File error occurred.
Response: Ensure that the required queue is available Severity: 30 : Severe error
and operational.
Explanation: The filesystem returned error code
<insert_4> for file <insert_3>.
AMQ9512 Ping operation is not valid for channel
<insert_3>. Response: Record the name of the file <insert_3> and
tell the systems administrator, who should ensure that
Severity: 30 : Severe error file <insert_3> is correct and available.
Explanation: Ping may only be issued for SENDER,
SERVER or CLUSSDR channel types. Also, it may not AMQ9517 File damaged.
be issued for an SSL channel on the HP-UX or Linux
platforms. Severity: 30 : Severe error
Response: If the local channel is a receiver channel, Explanation: The program has detected damage to the
you must issue the ping from the remote queue contents of file <insert_3>.
manager. Response: Record the values and tell the systems
administrator who must restore a saved version of file
<insert_3>. The return code was <insert_1> and the
record length returned was <insert_2>.
Chapter 7. 9000-9999 - Remote 219

AMQ9518 File <insert_3> not found. AMQ9523 Remote host detected a protocol error.
Explanation: The program requires that the file Explanation: During communications through channel
<insert_3> is present and available. <insert_3>, the remote queue manager channel program
detected a protocol error. The failure type was
Response: This may be caused by invalid values for
<insert_1> with associated data of <insert_2>.
the optional environment variables MQCHLLIB,
MQCHLTAB or MQDATA. If these variables are valid Response: Tell the systems administrator, who should
or not set then record the name of the file and tell the examine the error files to determine the cause of the
systems administrator who must ensure that file failure.
<insert_3> is available to the program.
AMQ9524 Remote queue manager unavailable.
AMQ9519 Channel <insert_3> not found.
Explanation: Channel <insert_3> cannot start because
Explanation: The requested operation failed because the remote queue manager is not currently available.
the program could not find a definition of channel
Response: Either start the remote queue manager, or
<insert_3>.
retry the operation later.
Response: Check that the name is specified correctly
and the channel definition is available.
AMQ9525 Remote queue manager is ending.
AMQ9520 Channel not defined remotely.
Explanation: Channel <insert_3> is closing because the
remote queue manager is ending.
Explanation: There is no definition of channel
Response: None.
<insert_3> at the remote location.
Response: Add an appropriate definition to the
AMQ9526 Message sequence number error for
remote hosts list of defined channels and retry the
channel <insert_3>.
operation.
AMQ9521 Host is not supported by this channel. Explanation: The local and remote queue managers do
not agree on the next message sequence number. A
message with sequence number <insert_1> has been
Explanation: The connection across channel <insert_5> sent when sequence number <insert_2> was expected.
was refused because the remote host <insert_4> did not
Response: Determine the cause of the inconsistency. It
match the host <insert_3> specified in the channel
could be that the synchronization information has
definition.
become damaged, or has been backed out to a previous
Response: Update the channel definition, or remove version. If the situation cannot be resolved, the
the explicit mention of the remote machine connection sequence number can be manually reset at the sending
name. end of the channel using the RESET CHANNEL
command.
AMQ9522 Error accessing the status table.
AMQ9527 Cannot send message through channel
<insert_3>.
Explanation: The program could not access the
channel status table.
Explanation: The channel has closed because the
Response: A value of <insert_1> was returned from
remote queue manager cannot receive a message.
the subsystem when an attempt was made to access the
Channel status table. Contact the systems administrator, Response: Contact the systems administrator who
who should examine the log files to determine why the should examine the error files of the remote queue
program was unable to access the status table. manager, to determine why the message cannot be
received, and then restart the channel.

Response: None.
AMQ9528 User requested closure of channel
<insert_3>.
AMQ9534 Channel <insert_3> is currently not
enabled.
Explanation: The channel is closing because of a
request by the user.
Explanation: The channel program ended because the
Response: None.
channel is currently not enabled.
Response: Issue the START CHANNEL command to
AMQ9529 Target queue unknown on remote host.
re-enable the channel.
Explanation: Communication using channel <insert_3> AMQ9535 User exit not valid.
has ended because the target queue for a message is
unknown at the remote host.
Explanation: Channel program <insert_3> ended
Response: Ensure that the remote host contains a
because user exit <insert_4> is not valid.
correctly defined target queue, and restart the channel.
Response: Ensure that the user exit is specified
correctly in the channel definition, and that the user
AMQ9530 Program could not inquire queue
exit program is correct and available.
attributes.
AMQ9536 Channel ended by an exit.
Explanation: The attempt to inquire the attributes of
queue <insert_4> on queue manager <insert_5> failed
with reason code <insert_1>. Explanation: Channel program <insert_3> was ended
by exit <insert_4>.
Response: Ensure that the queue is available and retry
the operation. Response: None.
AMQ9531 Transmission queue specification error. AMQ9537 Usage: <insert_3> [-m QMgrName] [-q
InitQ]
Explanation: Queue <insert_4> identified as a
transmission queue in the channel definition <insert_3> Explanation: Values passed to the Channel Initiator
is not a transmission queue. program are not valid. The parameters should be
passed as follows: [-m QMgrName] [-q InitQ] Default
Response: Ensure that the queue name is specified
values are used for parameters that are not supplied.
correctly. If so, alter the queue usage parameter of the
queue to that of a transmission queue. Response: Correct the parameters passed to the
program and retry the operation.
AMQ9532 Program cannot set queue attributes.
AMQ9538 Commit control error.
Explanation: The attempt to set the attributes of queue
<insert_4> on queue manager <insert_5> failed with Explanation: An error occurred when attempting to
reason code <insert_1>. start commitment control. Either exception <insert_3>
was received when querying commitment status, or
Response: Ensure that the queue is available and retry
commitment control could not be started.
the operation.
Response: Refer to the error log for other messages
pertaining to this problem.
AMQ9533 Channel <insert_3> is not currently
active.
AMQ9539 No channels available.
Explanation: The channel was not stopped because it
was not currently active. If attempting to stop a specific Explanation: The channel initiator program received a
instance of a channel by connection name or by remote trigger message to start an MCA program to process
queue manager name this message indicates that the queue <insert_3>. The program could not find a
specified instance of the channel is not running. defined, available channel to start.
Chapter 7. 9000-9999 - Remote 221

Response: Ensure that there is a defined channel, previous error messages to see if the attempt to put
which is enabled, to process the transmission queue. messages to a dead-letter queue failed. The program
identifier (PID) of the processing program was
<insert_4>.
AMQ9540 Commit failed.
AMQ9545 Disconnect interval expired.
Explanation: The program ended because return code
<insert_1> was received when an attempt was made to
commit change to the resource managers. The commit Explanation: Channel <insert_3> closed because no
ID was <insert_3>. messages arrived on the transmission queue within the
disconnect interval period.
Response: Tell the systems administrator.
Response: None.
AMQ9541 CCSID supplied for data conversion not
supported. AMQ9546 Error return code received.
Explanation: The program ended because, either the Explanation: The program has ended because return
source CCSID <insert_1> or the target CCSID <insert_2> code <insert_1> was returned from function <insert_3>
is not valid, or is not currently supported.
Response: Correct the cause of the failure and retry
Response: Correct the CCSID that is not valid, or the operation.
ensure that the requested CCSID can be supported.
AMQ9547 Type of remote channel not suitable for
AMQ9542 Queue manager is ending. action requested.
Severity: 10 : Warning Severity: 30 : Severe error
Explanation: The program will end because the queue Explanation: The operation requested cannot be
manager is quiescing. performed because channel <insert_3> on the remote
machine is not of a suitable type. For example, if the
Response: None.
local channel is defined as a sender the remote machine
must define its channel as either a receiver or requester.
AMQ9543 Status table damaged.
Response: Check that the channel name is specified
Severity: 30 : Severe error correctly. If it is, check that the remote channel has
been defined correctly.
Explanation: The channel status table has been
damaged.
AMQ9548 Message put to the ’dead-letter queue’.
Response: End all running channels and issue a
DISPLAY CHSTATUS command to see the status of the Severity: 10 : Warning
channels. Use the standard facilities supplied with your
Explanation: During processing a message has been
system to record the problem identifier, and to save the
put to the dead-letter queue.
center. Do not discard these files until the problem has Response: Examine the contents of the dead-letter
been resolved. queue. Each message is contained in a structure that
describes why the message was put to the queue, and
to where it was originally addressed.
AMQ9544 Messages not put to destination queue.
AMQ9549 Transmission Queue <insert_3> inhibited
Explanation: During the processing of channel for MQGET.
<insert_3> one or more messages could not be put to
the destination queue and attempts were made to put
them to a dead-letter queue. The location of the queue Explanation: An MQGET failed because the
is <insert_1>, where 1 is the local dead-letter queue and transmission queue had been previously inhibited for
2 is the remote dead-letter queue. MQGET.
Response: Examine the contents of the dead-letter Response: None.
queue. Each message is contained in a structure that
describes why the message was put to the queue, and
to where it was originally addressed. Also look at

AMQ9550 Channel program <insert_3> cannot be AMQ9556 Channel synchronization file missing or
stopped at this time. damaged.
Explanation: The channel program can not be Explanation: The channel synchronization file
terminated immediately but should end shortly. <insert_3> is missing or does not correspond to the
stored channel information for queue manager
Response: If the channel does not end in a short time
<insert_4>.
issue the STOP CHANNEL command again.
Response: Rebuild the synchronization file using the
rcrmqmobj command rcrmqmobj -t syncfile (-m
AMQ9551 Protocol not supported by remote host
q-mgr-name)
Explanation: The operation you are performing over AMQ9556 (iSeries) Channel synchronization file
Channel <insert_3> to the host at <insert_4> is not missing or damaged.
supported by the target host.
Response: Check that the connection name parameter
Explanation: The channel synchronization file
is specified correctly and that the levels of the products
<insert_3> is missing or does not correspond to the
in use are compatible.
stored channel information for queue manager
<insert_4>.
AMQ9552 Security flow not received.
Response: Rebuild the synchronization file using the
Severity: 30 : Severe error RCRMQMOBJ command.
Explanation: During communications through channel
<insert_3> the local security exit requested security data AMQ9557 Queue Manager User ID initialization
from the remote machine. The security data has not failed.
been received so the channel has been closed.
Response: Tell the systems administrator who should
Explanation: The call to initialize the User ID failed
ensure that the security exit on the remote machine is
with CompCode <insert_1> and Reason <insert_2>.
defined correctly.
Response: Correct the error and try again.
AMQ9553 The function is not supported.
AMQ9558 Remote Channel is not currently
available.
Explanation: The <insert_3> function <insert_4>
attempted is not currently supported on this platform.
Explanation: The channel program ended because the
Response: None.
channel <insert_3> is not currently available on the
remote system. This could be because the channel is
AMQ9554 User not authorized. disabled or that the remote system does not have
sufficient resources to run a further channel.
Response: Check the remote system to ensure that the
Explanation: You are not authorized to perform the channel is available to run, and retry the operation.
Channel operation.
Response: Tell the systems administrator who should AMQ9560 Rebuild Synchronization File - program
ensure that the correct access permissions are available started
to you, and then retry the operation.
AMQ9555 File format error. Explanation: Rebuilding the Synchronization file for
Queue Manager <insert_3> .
Response: None.
Explanation: The file <insert_3> does not have the
expected format.
Response: Ensure that the file name is specified
correctly.
Chapter 7. 9000-9999 - Remote 223

AMQ9561 Rebuild Synchronization File - program AMQ9566 Invalid MQSERVER value
completed normally
Explanation: The value of the MQSERVER
Explanation: Rebuild Synchronization File program environment variable was <insert_3>. The variable
completed normally. should be in the format
’ChannelName/Protocol/ConnectionName’.
Response: None.
Response: Correct the MQSERVER value and retry the
operation.
AMQ9562 Synchronization file in use.
AMQ9572 Message header is not valid.
Explanation: The Synchronization file <insert_3> is in
use and cannot be recreated.
Explanation: Channel <insert_3> is stopping because a
Response: Stop any channel activity and retry the
message header is not valid. During the processing of
rcrmqmobj command.
the channel, a message was found that has a header
that is not valid. The dead-letter queue has been
AMQ9562 (iSeries) Synchronization file in use. defined as a transmission queue, so a loop would be
created if the message had been put there.
Response: Correct the problem that caused the
Explanation: The Synchronization file <insert_3> is in message to have a header that is not valid.
use and cannot be recreated.
Response: Stop any channel activity and retry the AMQ9573 Maximum number of active channels
RCRMQMOBJ command. reached.
AMQ9563 Synchronization file cannot be deleted
Explanation: There are too many channels active to
Severity: 30 : Severe error start another. The current defined maximum number of
Explanation: The filesystem returned error code active channels is <insert_1>.
<insert_1> for file <insert_3>. Response: Either wait for some of the operating
Response: Tell the systems administrator who should channels to close or use the stop channel command to
ensure that file <insert_3> is available and not in use. close some channels. Retry the operation when some
channels are available. The maximum number of active
channels is a configurable parameter in the queue
AMQ9564 Synchronization File cannot be created manager configuration file.
Explanation: The filesystem returned error code AMQ9574 Channel <insert_3> can now be started.
<insert_1> for file <insert_3>. Severity: 30 : Severe error
Response: Tell the systems administrator. Explanation: Channel <insert_3> has been waiting to
start, but there were no channels available because the
AMQ9565 No dead-letter queue defined. maximum number of active channels was running.
One, or more, of the active channels has now closed so
Severity: 30 : Severe error this channel can start.
Explanation: The queue manager <insert_4> does not
have a defined dead-letter queue. AMQ9575 DCE Security: failed to get the user’s
Response: Either correct the problem that caused the login name.
program to try and write a message to the dead-letter Severity: 30 : Severe error
queue or create a dead-letter queue for the queue
manager. Explanation: System call <insert_4> to get the login
name of the user running WebSphere MQ client
application process <insert_1> failed with error value
<insert_2>. This occurred in security exit function
create_cred. The exit will now attempt to open channel
<insert_3> using the DCE default login context.
Response: If you wish to run using the DCE default

login context take no action. If you wish to run using exit suppressed the channel.
the user’s login name as the DCE security exit principal
Response: Examine the channel definition of channel
examine the documentation for the operating system on
<insert_3> and alter it so that the relevant name on the
which you are running MQ clients and reconfigure the
partner system matches that specified in the SCYDATA
operating system as necessary to allow the <insert_4>
field.
call to succeed.
AMQ9580 DCE Security: invalid message received.

AMQ9576 DCE Security: an exit could not allocate
memory. Severity: 30 : Severe error
Severity: 30 : Severe error Explanation: An IBM-supplied DCE exit on channel
<insert_3> received a message that was not generated
Explanation: A DCE exit was unsuccessful in
by a matching exit, or was not the expected type of
obtaining the memory it needed. The failure occurred
message. The header.mechanism field had value
in exit function <insert_4>. Channel <insert_3> is
<insert_1>. The header.msgtype field had value
closed.
<insert_2>. The name of the exit function in which the
Response: Make more memory available to the error was discovered is <insert_4>.
WebSphere MQ system and restart the relevant
Response: Make sure that the exits at both ends of the
channel.
channel generate compatible flows.
AMQ9577 DCE security exit: no partner name.

AMQ9581 DCE Security: wrong exit called.
Explanation: Channel <insert_3> has not been opened
Explanation: Exit <insert_4> on channel <insert_3>
because the DCE security exit which initiates the
was called for use as a WebSphere MQ exit of the
security context was not passed a valid partner name.
wrong type. DCE_SEC_SCY_CHANNELEXIT functions
When the DCE security exit is called to initiate the
as a security exit; DCE_SEC_SRM_CHANNELEXIT
security context it is essential that the PartnerName
functions as a send, receive or message exit. The ExitId
field in the MQCXP structure contains a valid partner
parameter passed to the exit was <insert_1>.
name. On this call it did not. This can arise as a result
of a usage error, for instance only specifying the Response: Alter the exit definitions to ensure that exit
security exit on one end of the channel. The error was <insert_4> is called correctly.
reported from security exit function savePartnerName.
Response: Check your usage of the DCE security exit AMQ9582 DCE Security: invalid exit function
for errors, such as only specifying the exit in one of the requested.
matching channel definitions. Correct any errors found
and retry. Severity: 30 : Severe error
Explanation: Exit <insert_4> on channel <insert_3>
AMQ9578 DCE Security: bad return from DCE call. was called with an invalid ExitReason (value
<insert_1>).
Response: Check that the exit is being run with a
Explanation: Channel <insert_3> has been closed compatible release of WebSphere MQ base code. If not
because one of the DCE channel exits received a bad then correct it. If it is, contact your IBM support center
return code from DCE. for help.
Response: Consult the appropriate DCE manuals to
find out the meaning of major_status <insert_1> and AMQ9583 The DCE security exit was not run.
minor_status <insert_2> on call <insert_5>. Then rectify
the error. The exit function name is <insert_4>. Severity: 30 : Severe error
Explanation: The DCE_SEC_SRM_CHANNELEXIT
AMQ9579 DCE Security: partner name does not exit was called on channel <insert_3>; the value of
match target. pContext->mechanism (<insert_1>) passed was not
valid.
Response: This is probably because the
Explanation: The DCE Security exit was requested to DCE_SEC_SRM_CHANNELEXIT exit has been called
perform a trusted channel check: target partner name without first calling the
<insert_4> was specified in the SCYDATA field of DCE_SEC_SCY_CHANNELEXIT security exit. Alter the
channel <insert_3>. The actual partner name associated system so that either both or neither are run.
with channel <insert_3> was <insert_5>, so the security
Chapter 7. 9000-9999 - Remote 225

on queue manager <insert_5> failed with reason code
AMQ9584 DCE Security: message too short.
<insert_1>.
Explanation: The DCE_SEC_SRM_CHANNELEXIT your system to record the problem identifier. Contact
receive or message exit was called on channel your IBM support center.
<insert_3> to process an incoming message. The
pDataLength parameter supplied to the exit indicated
AMQ9589 Program cannot query queue manager
that the message received was too short to be a valid
object.
message for the relevant exit. The *pDataLength value
was <insert_1>. Severity: 30 : Severe error
Response: Configure the system so that compatible Explanation: The attempt to query object <insert_4>
send/receive/message exits are run at both ends of the on queue manager <insert_5> failed with reason code
channel. <insert_1>.
AMQ9585 Maximum number of channel initiators your system to record the problem identifier. Contact
reached. your IBM support center.
AMQ9590 Program cannot close queue manager
Explanation: The maximum number of channels
object.
initiators that can be in use simultaneously has been
reached. The number of permitted channel initiators is Severity: 30 : Severe error
a configurable parameter in the queue manager
configuration file. Explanation: The attempt to close object <insert_4> on
queue manager <insert_5> failed with reason code
Response: Wait for one or more channel initiators to <insert_1>.
close and retry the operation or modify the
configuration file to allow more initiators and restart Response: Use the standard facilities supplied with
the Queue Manager. your system to record the problem identifier. Contact
AMQ9586 Program cannot create queue manager

object. AMQ9591 Program cannot prepare queue manager
object.
Explanation: The attempt to create object <insert_4>
on queue manager <insert_5> failed with reason code Explanation: The attempt to prepare object <insert_4>
<insert_1>. on queue manager <insert_5> failed with reason code
<insert_1>.
your system to record the problem identifier. Contact Response: Use the standard facilities supplied with
your IBM support center. your system to record the problem identifier. Contact

object. AMQ9592 Program cannot resolve queue manager
object.
Explanation: The attempt to open object <insert_4> on
queue manager <insert_5> failed with reason code Explanation: The attempt to resolve object <insert_4>
<insert_1>. on queue manager <insert_5> failed with reason code
<insert_1>.
your system to record the problem identifier. Contact Response: Use the standard facilities supplied with
your IBM support center. your system to record the problem identifier. Contact
AMQ9588 Program cannot update queue manager

object. AMQ9593 Program cannot delete queue manager
object.
Explanation: The attempt to update object <insert_4>
Explanation: The attempt to delete object <insert_4>

on queue manager <insert_5> failed with reason code the operation. If the message is from a remote Queue
<insert_1>. Manager, check the Message Channel Agent User
Identifier has the correct authority.
your system to record the problem identifier. Contact
your IBM support center. AMQ9601 Program could not inquire on queues on
this queue manager.
AMQ9594 Usage: runmqfmt [filename]. Severity: 30 : Severe error
Severity: 0 : Information Explanation: The WebSphere MQ clustering repository
program was attempting to find out about the queues
Explanation: Syntax for the usage of runmqfmt.
on queue manager <insert_3>. One of the calls failed
Response: None. with reason code <insert_1>. The repository command
was backed out and the repository process went into a
timed wait.
AMQ9595 Usage: endmqlsr [-w] [-m QMgrName]
Response: Correct the error. When the repository
Severity: 10 : Warning process restarts it processes the backed out command
Explanation: The correct usage is shown. again and continues.

endmqlsr program and retry the operation. AMQ9602 Maximum number of channel processes
reached.
AMQ9596 Queue Manager <insert_3> still running Severity: 30 : Severe error
Severity: 30 : Severe error Explanation: The channel can not start because the
number of channel processes has already reached the
Explanation: The requested operation can not maximum allowable value. The maximum number of
complete because queue manager <insert_3> is still channels processes is configured as <insert_1>. This
running. value is a configurable parameter in the queue manager
Response: End the queue manager and retry the configuration file.
operation. Response: Wait for some of the operating channels to
close. Retry the operation when some channels are
AMQ9597 No WebSphere MQ listeners for Queue available.
Manager <insert_3>.
Severity: 0 : Information AMQ9603 Error accessing the process pool shared
segment.
Explanation: No listener processes were found in the
system for Queue Manager <insert_3>. Severity: 30 : Severe error
Response: None. Explanation: The program could not access the

process pool shared segment
AMQ9598 <insert_1> WebSphere MQ listeners will Response: A value of <insert_1> was returned from
end shortly. the subsystem when an attempt was made to access the
Channel process pool shared memory. Contact the
Severity: 0 : Information systems administrator, who should examine the log
Explanation: <insert_1> listeners detected in the files to determine why the program was unable to
system are scheduled for shutdown. access the process pool shared segment.
Response: None.
AMQ9604 Channel <insert_3> terminated
unexpectedly
AMQ9599 Program could not open queue manager
object. Severity: 30 : Severe error
Severity: 30 : Severe error Explanation: The process or thread executing channel

<insert_3> is no longer running. The check process
Explanation: The attempt to open either the queue or system call returned <insert_1> for process <insert_2>.
queue manager object <insert_4> on queue manager
<insert_5> by user <insert_3> failed with reason code Response: No immediate action is required because
<insert_1>. the channel entry has been removed from the list of
running channels. Inform the system administrator who
Response: Ensure that the queue is available and retry should examine the operating system procedures to
Chapter 7. 9000-9999 - Remote 227

determine why the channel process has terminated. The listener process contains channels which are still
active.
AMQ9605 <insert_1> WebSphere MQ listeners Response: Active channels may be stopped using the
have been ended. ’STOP CHANNEL’ command or by ending the Queue
Manager, and reissuing the end-listener request.
Explanation: <insert_1> listeners detected in the
AMQ9614 (iSeries) Certificate is not signed by a
system have been ended.
trusted Certificate Authority.
Response: None.
Explanation: The attempt to start channel <insert_3>
AMQ9606 A WebSphere MQ listener has ended.
failed because the certificate used in the SSL handshake
Severity: 0 : Information is not signed by a Certificate Authority (CA) listed in
the certificate trust list for this queue manager. This
Explanation: One listener detected in the system has error occurs when the SSL key repository for the queue
been ended. manager is specified as ’*SYSTEM’ and the application
Response: None. definition in Digital Certificate Manager has been
modified to specify a CA trust list.
AMQ9608 Remote resources in recovery Response: Use Digital Certificate Manager to add the
required Certificate Authority (CA) certificates to the
Severity: 30 : Severe error application definitions CA trust list.
Explanation: Channel <insert_3> could not establish a
successful connection with the remote Queue Manager AMQ9615 (iSeries) Queue Manager is not registered
because resources are being recovered. with DCM.
Response: Restart the channel at a later time. If the Severity: 0 : Information
problem persists then examine the error logs of the
remote Queue Manager to see the full explanation of Explanation: The attempt to start channel <insert_3>
the cause of the problem. failed because the queue manager is not registered as a
SSL server application with Digital Certificate Manager
(DCM). This error occurs when the SSL key repository
AMQ9610 AMQ<insert_1> messages suppressed for the queue manager is specified as ’*SYSTEM’ but
Severity: 0 : Information WebSphere MQ cannot register the queue manager as
an SSL server application with DCM, or alternatively
Explanation: <insert_2> messages of type when the application definition for the queue manager
AMQ<insert_1> were suppressed has been manually removed from DCM.
Response: Message suppression is controlled by Response: Attempt to re-register the queue manager
MQ_CHANNEL_SUPPRESS_MSGS and with Digital Certificate Manager by issuing CHGMQM
MQ_CHANNEL_SUPPRESS_INTERVAL environment SSLKEYR(*SYSTEM). If this is unsuccessful you may
variables. need to manually add the application definition
through Digital Certificate Manager, see the WebSphere
AMQ9611 Rebuild Client Channel Table - program MQ Security manual for more details.
completed normally
Severity: 0 : Information AMQ9616 The CipherSpec proposed is not enabled
on the SSL server.
Explanation: Rebuild Client Channel Table program
completed normally. Severity: 30 : Severe error
Response: None. Explanation: The SSL subsystem at the SSL server end
of a channel been configured in such a way that it has
rejected the CipherSpec proposed by an SSL client. This
AMQ9612 <insert_1> WebSphere MQ listeners rejection occured during the SSL handshake (i.e. it
could not be ended. happened before the proposed CipherSpec was
compared with the CipherSpec in the SSL server
channel definition). This error most commonly occurs
Explanation: The request to the end the WebSphere when the choice of acceptable CipherSpecs has been
MQ listeners for specified Queue Manager was limited by setting the SSLFipsRequired attribute on the
completed however <insert_1> listeners could not be SSL server queue manager while the SSL client is trying
stopped. Reasons why listener may not be stopped are: to connect with a CipherSpec which is not
FIPS-certified on the SSL server. The channel is

<insert_3>; in some cases its name cannot be determined and so is shown as ’????’. The channel did
determined and so is shown as ’????’. The channel did not start.
not start.
Response: Analyse why the proposed CipherSpec was determination’ section of the System Administration
not enabled on the SSL server. Alter the client manual and contact your IBM support center.
CipherSpec, or reconfigure the SSL server to accept the
original client CipherSpec. Restart the channel.
AMQ9620 (iSeries) Unexpected SSL error on call to
<insert_4>.
AMQ9617 Parameter requesting FIPS has an
invalid value.
Explanation: An unexpected SSL error was returned
from function <insert_4> for channel <insert_3>. The
Explanation: An SSL channel running on an MQ client error code returned was <insert_1>. GSKit error codes
has failed to start. This is because the value specified are documented in the MQ manuals and also in the
for the MQSSLFIPS environment variable, or in the GSKSSL member of the H file in library QSYSINC.
MQSCO FipsRequired field, is invalid. The value
specified was ″<insert_3>″; valid values are ″YES″ or
determination’ section of the System Administration
″NO″.
Response: Set the value specified for the MQSSLFIPS
environment variable, or in the MQSCO FipsRequired
AMQ9621 Error on call to SSL function ignored on
field, to ″YES″ or ″NO″. Restart the channel.
channel <insert_3>.
AMQ9618 SSLCRLNL attribute points to a
namelist with no names. Explanation: An error indicating a software problem
was returned from a function which is used to provide
SSL support. The error code returned was <insert_1>.
Explanation: An SSL channel has failed to start The function call was <insert_4>. The channel is
because the SSLCRLNL queue manager attribute points <insert_3>; in some cases its name cannot be
to a namelist with an empty list of names. determined and so is shown as ’????’. This error is not
regarded as sufficiently serious to interrupt channel
Response: If CRL checking is required, set up the
operation; channel operation was not affected.
namelist referenced by SSLCRLNL with a non-empty
list of authentication information object names. If no Response: None.
CRL checking is required, clear the SSLCRLNL queue
manager attribute. Restart the failing channel.
AMQ9622 AUTHINFO object <insert_3> does not
exist.
AMQ9619 SSL cannot be run from an unthreaded
HP-UX MQ client.
Explanation: A channel or channel process has failed
to start because the namelist of CRL AUTHINFO
Explanation: On HP-UX, SSL cannot be run from a objects includes the name <insert_3>, but no
WebSphere MQ client which was linked with the AUTHINFO object of that name exists.
unthreaded client libraries.
Response: Ensure all the names in the namelist
Response: Either relink your client application with specified on the SSLCRLNL queue manager attribute
the threaded client libraries, or do not attempt to use correspond to AUTHINFO objects which are to be used
SSL from this application. on the SSL channels. Restart the failing channel or
channel process.
AMQ9620 Internal error on call to SSL function on
channel <insert_3>. AMQ9623 Error inquiring on AUTHINFO object
<insert_3>.
Explanation: An error indicating a software problem
was returned from a function which is used to provide Explanation: A channel or channel process has failed
SSL support. The error code returned was <insert_1>. to start because reason code <insert_1> was returned
The function call was <insert_4>. The channel is when an inquire was performed on AUTHINFO object
<insert_3>; in some cases its name cannot be <insert_3>.
Response: Look at the MQRC_ values in the
Chapter 7. 9000-9999 - Remote 229

WebSphere MQ Application Programming Reference to
AMQ9628 An LDAP server containing CRLs was
determine the meaning of reason code <insert_1>,
specified with an invalid CONNAME.
correct the error, and restart the failing channel or
channel process. Severity: 30 : Severe error
Explanation: The WebSphere MQ client has failed to
AMQ9624 AUTHINFO object <insert_3> is not of connect because an invalid CONNAME was found for
type CRLLDAP. one of the LDAP servers containing CRLs. The invalid
value is <insert_3>.
Response: Correct the invalid parameter. If the LDAP
details were defined on a queue manager system,
to start because one of the AUTHINFO objects specified
regenerate the client definitions. Reconnect.
in the SSLCRLNL namelist is not of AUTHTYPE
CRLLDAP. Instead the type value is <insert_1>.
AMQ9629 Bad SSL cryptographic hardware
Response: Only include CRLLDAP AUTHINFO
parameters.
objects in the namelist specified on the SSLCRLNL
queue manager attribute. Restart the channel or Severity: 30 : Severe error
channel process.
Explanation: The following string was supplied to
specify or control use of SSL cryptographic hardware:
AMQ9625 AUTHINFO object <insert_3> was <insert_4>. This string does not conform to any of the
specified with an invalid CONNAME. MQ SSL cryptographic parameter formats. The channel
is <insert_3>. The channel did not start.
Response: Correct your SSL cryptographic hardware
parameters and restart the channel.
to start because one of the AUTHINFO objects specified
in the SSLCRLNL namelist has an invalid CONNAME
parameter. The invalid value is <insert_4>. AMQ9630 An expired SSL certificate was loaded.
Response: Correct the invalid parameter. Restart the Severity: 30 : Severe error
channel or channel process.
Explanation: An SSL certificate that was loaded was
not corrupt, but failed validation checks on its date
AMQ9626 Channel hanging while initializing SSL. fields. The certificate has either expired, or its date is
not valid yet (that is, the from date is later than today),
or the validity date range is incorrect (for example, the
Explanation: The current channel cannot start because to date is earlier than the from date).
another channel is hanging while initializing the SSL
Response: Ensure that the specified SSL certificate has
subsystem.
a valid expiry date.
Response: Investigate the reason for the hang on the
other channel. Once this is rectified, restart this
AMQ9631 The CipherSpecs on the two ends of
channel.
channel <insert_3> do not match.
AMQ9627 The path and stem name for the SSL
key repository have not been specified. Explanation: There is a mismatch between the
CipherSpecs on the local and remote ends of channel
<insert_3>. The channel will not run until this
Explanation: The directory path and file stem name mismatch is resolved.
for the SSL key repository have not been specified. On
Response: Change the channel definitions for
a MQ client system there is no default location for this
<insert_3> so the two ends have matching CipherSpecs
file. SSL connectivity is therefore impossible as this file
and restart the channel.
cannot be accessed.
Response: Use the MQSSLKEYR environment variable
AMQ9631 (iSeries) The CipherSpecs at the ends of
or MQCONNX API call to specify the directory path
channel <insert_3> do not match.
and file stem name for the SSL key repository.
Explanation: There is a mismatch between the
CipherSpecs on the local and remote ends of channel
<insert_3>. The channel will not run until this
mismatch is resolved. The local CipherSpec is

<insert_4> and the remote CipherSpec is <insert_5>.
AMQ9635 (iSeries) Channel <insert_3> did not
Response: Change the channel definition for specify a valid CipherSpec.
<insert_3> so that both ends have matching
CipherSpecs and restart the channel.
Explanation: Channel <insert_3> did not specify a
valid CipherSpec, or it specified a CipherSpec that is
AMQ9633 Bad SSL certificate for channel
not available from the IBM Cryptographic Access
<insert_3>.
Provider product installed on this machine.
Severity: 30 : Severe error CipherSpecs that use 128-bit encryption algorithms are
only available in 5722-AC3 (128-bit) IBM Cryptographic
Explanation: A certificate encountered during SSL Access Provider.
handshaking is regarded as bad for one of the
following reasons: Response: Change channel <insert_3> to specify a
(a) it was formatted incorrectly and could not be valid CipherSpec that is available from the IBM
validated, or Cryptographic Access Provider product installed on
(b) it was formatted correctly but failed validation this machine. Check that the CipherSpec you are using
against the Certification Authority (CA) root and other is available on this machine in either the 5722-AC2
certificates held on the local system, or (56-bit) IBM Cryptographic Access Provider or
(c) it was found in a Certification Revocation List (CRL) 5722-AC3 (128-bit) IBM Cryptographic Access Provider
on an LDAP server. licensed program.
(d) a CRL was specified but the CRL could not be
found on the LDAP server.
AMQ9636 SSL distinguished name does not match
The channel is <insert_3>; in some cases its name
peer name, channel <insert_3>.
cannot be determined and so is shown as ’????’. The
channel did not start. Severity: 30 : Severe error
Response: Check which of the three possible causes Explanation: The distinguished name, <insert_4>,
applies on your system. Correct the error, and restart contained in the SSL certificate for the remote end of
the channel. the channel does not match the local SSL peer name for
channel <insert_3>. The distinguished name at the
remote end must match the peer name specified (which
AMQ9634 SSL security context expired.
can be generic) before the channel can be started.
Response: If this remote system should be allowed to
Explanation: During an SSL operation to encrypt or connect, either change the SSL peer name specification
decrypt a secured message, the SSL security context, for the local channel so that it matches the
which is used to secure communications and was distinguished name in the SSL certificate for the remote
previously established with the remote party, has end of the channel, or obtain the correct certificate for
expired because the remote party has shut down. The the remote end of the channel. Restart the channel.
secured message has not been encrypted or decrypted.
This failure has closed WebSphere MQ channel name
AMQ9637 Channel is lacking a certificate.
<insert_3>. If the name is ’????’, the name is unknown.
The SSL operation was <insert_4> and its completion Severity: 30 : Severe error
code was <insert_5>.
Explanation: The channel is lacking a certificate to use
Response: Determine why the remote party has shut for the SSL handshake. The channel name is <insert_3>
down and if necessary re-start the channel. The shut (if ’????’ it is unknown at this stage in the SSL
down might be the result of controlled termination by a processing). The channel did not start.
system administrator, or the result of an unexpected
Response: Make sure the appropriate certificates are
termination due to an error. The SSL operation is
correctly configured in the key repositories for both
described in the Windows Schannel reference manual.
ends of the channel.
If you have migrated from WebSphere MQ V5.3 to V6,
AMQ9635 Channel <insert_3> did not specify a it is possible that the missing certificate is due to a
valid CipherSpec. failure during SSL key repository migration. Check the
relevant error logs. If these show that an orphan
certificate was encountered then you should obtain the
Explanation: Channel <insert_3> did not specify a relevant missing certification authority (signer)
valid CipherSpec. certificates and then import these and the orphan
certificate into the WebSphere MQ V6 key repository,
Response: Change channel <insert_3> to specify a and then re-start the channel.
valid CipherSpec.
Chapter 7. 9000-9999 - Remote 231

which is associated with the queue manager or client.
AMQ9638 SSL communications error for channel
Alternatively, if appropriate, change the remote channel
<insert_3>.
definition so that its SSLCAUTH attribute is set to
Severity: 30 : Severe error OPTIONAL and it has no SSLPEER value set.
If you have migrated from WebSphere MQ V5.3 to V6,
Explanation: An unexpected SSL communications
it is possible that the missing certificate is due to a
error occurred for a channel, as reported in the
failure during SSL key repository migration. Check the
preceding messages. The channel is <insert_3>; in some
relevant error logs. If these show that an orphan
cases its name cannot be determined and so is shown
certificate was encountered then you should obtain the
as ’????’. The channel did not start.
relevant missing certification authority (signer)
Response: Investigate the problem reported in the certificates and then import these and the orphan
preceding messages. Review the local and remote certificate into the WebSphere MQ V6 key repository,
console logs for reports of network errors. Correct the and then re-start the channel.
errors and restart the channel.
AMQ9642 (iSeries) No SSL certificate for channel
AMQ9639 Remote channel <insert_3> did not <insert_3>.
specify a CipherSpec.
Explanation: The channel <insert_3> did not supply a
Explanation: Remote channel <insert_3> did not certificate to use during SSL handshaking, but a
specify a CipherSpec when the local channel expected certificate is required by the remote queue manager.
one to be specified. The channel did not start. The channel did not start.
Response: Change the remote channel <insert_3> to Response: If the SSL key repository for the queue
specify a CipherSpec so that both ends of the channel manager has been specified as ’*SYSTEM’ ensure that a
have matching CipherSpecs. certificate has been associated with the application
description for the queue manager in Digital Certificate
Manager. Alternatively, if appropriate, change the
AMQ9640 SSL invalid peer name, channel remote channel definition so that its SSLCAUTH
<insert_3>, attribute <insert_5>. attribute is set to OPTIONAL and it has no SSLPEER
Severity: 30 : Severe error value set.
Explanation: The SSL peer name for channel

<insert_3> includes a distinguished name attribute key AMQ9643 Remote SSL peer name error for channel
<insert_5> which is invalid or unsupported. The <insert_3>.
channel did not start. Severity: 30 : Severe error
Response: Correct the SSL peer name for the channel. Explanation: The remote end of channel <insert_3>
Restart the channel. has had an SSL peer name error. The channel did not
start.
AMQ9641 Remote CipherSpec error for channel Response: Review the error logs on the remote system
<insert_3>. to discover the problem with the peer name.
Explanation: The remote end of channel <insert_3> AMQ9645 Correctly labelled SSL certificate
has had a CipherSpec error. The channel did not start. missing on channel <insert_3>.
Response: Review the error logs on the remote system Severity: 30 : Severe error
to discover the problem with the CipherSpec. Explanation: The key database file in use has not been
set up with a correctly labelled SSL certificate. The
AMQ9642 No SSL certificate for channel channel is <insert_3>; in some cases its name cannot be
<insert_3>. determined and so is shown as ’????’. The channel did
not start.
Response: Add a correctly labelled SSL certificate to
Explanation: The channel <insert_3> did not supply a the current key database file. Restart the channel.
certificate to use during SSL handshaking, but a
certificate is required by the remote queue manager.
The channel did not start.
Response: Ensure that the key repository of the local
queue manager or MQ client contains an SSL certificate

AMQ9646 Channel <insert_3> could not connect to AMQ9650 The SSL key repository contains entries
any LDAP CRL servers. with duplicate labels.
Explanation: LDAP Certification Revocation List Explanation: The SSL key repository contains two or
(CRL) servers were specified but a connection could more entries with the same label. The channel is
not be established to any of them. The channel is <insert_3>; in some cases its name cannot be
<insert_3>; in some cases its name cannot be determined and so is shown as ’????’. The channel did
determined and so is shown as ’????’. The channel did not start.
not start.
Response: Use your key management tool to remove
Response: Check that the LDAP CRL server the duplicate entries. Restart the channel.
specifications are correct. If they are, check that the
servers are running and that the networking to access
AMQ9651 The SSL key repository is corrupt or has
them is working correctly. Fix any errors found and
a bad password.
restart the channel.
AMQ9647 I/O error on SSL key repository. Explanation: The SSL key repository has become
corrupted or its password id is incorrect. The channel is
<insert_3>; in some cases its name cannot be
Explanation: An I/O error was encountered when determined and so is shown as ’????’. The channel did
attempting to read the SSL key repository. The channel not start.
is <insert_3>; in some cases its name cannot be
Response: Use your key management tool to recreate
determined and so is shown as ’????’. The channel did
the key repository with a new password. Restart the
not start.
channel.
Response: Analyse why there is a I/O problem when
reading the key repository. Fix the error if one is found,
AMQ9652 The remote SSL certificate has expired.
or it may be a temporary problem. Restart the channel.
AMQ9648 The SSL key repository has an invalid Explanation: The SSL certificate used by MQ on the
internal format. remote end of the channel has expired. The channel is
Explanation: The SSL key repository has an invalid not start.
internal format. The channel is <insert_3>; in some
Response: Use your key management tool to provide
cases its name cannot be determined and so is shown
MQ with a current SSL certificate on the remote end of
as ’????’. The channel did not start.
the channel. Restart the channel.
Response: Recreate the SSL key repository and restart
the channel.
AMQ9653 An SSL trace file could not be opened.
AMQ9649 The SSL key repository contains
duplicate keys. Explanation: An SSL trace file could not be opened.
The SSL trace files are created in directory
/var/mqm/trace and have names AMQ.SSL.TRC and
Explanation: The SSL key repository contains two or AMQ.SSL.TRC.1. The channel is <insert_3>; in some
more entries with the same key. The channel is cases its name cannot be determined and so is shown
<insert_3>; in some cases its name cannot be as ’????’. This error is not regarded as sufficiently
determined and so is shown as ’????’. The channel did serious to interrupt channel operation; channel
not start. operation was not affected.
Response: Use your key management tool to remove Response: Check that you have a directory called
the duplicate keys. Restart the channel. /var/mqm/trace and that the userid under which
WebSphere MQ runs has permissions and space to
create and open a file in that directory. Fix the problem
and you will get SSL trace output.
Chapter 7. 9000-9999 - Remote 233

AMQ9654 An invalid SSL certificate was received AMQ9658 An invalid SSL certificate has been
from the remote system. encountered.
Explanation: An SSL certificate received from the Explanation: An SSL certificate has been encountered
remote system was not corrupt but failed validation which was not corrupt but which failed validation
checks on something other than its ASN fields and checks on its date fields. The certificate has either
date. The channel is <insert_3>; in some cases its name expired, or its date is not valid yet (i.e. the from date is
cannot be determined and so is shown as ’????’. The later than today), or the validity date range is incorrect
channel did not start. (e.g. the to date is earlier than the from date). The
channel is <insert_3>; in some cases its name cannot be
Response: Ensure that the remote system has a valid
SSL certificate. Restart the channel.
not start.
Response: Ensure that both the local and remote
AMQ9655 Problem loading GSKit SSL support.
systems have valid, current SSL certificates. Restart the
Severity: 30 : Severe error channel.
Explanation: MQ SSL support is provided on this
platform using a component called GSKit which is AMQ9659 A failure occurred during SSL
installed as part of MQ. GSKit had an internal problem handshaking.
loading one if its dynamic link libraries. The channel is
determined and so is shown as ’????’. The channel did Explanation: During SSL handshaking, or associated
not start. activities, a failure occurred. The failure is <insert_4>
and has caused WebSphere MQ channel name
Response: Uninstall MQ and reinstall. Restart the
<insert_3> to be closed. If the name is ’????’ then the
channel.
name is unknown.
Response: Refer to prior message in the WebSphere
AMQ9656 An invalid SSL certificate was received
MQ error log for information related to this problem.
from the remote system.
AMQ9660 SSL key repository: password stash file
Explanation: An SSL certificate received from the absent or unusable.
remote system was not corrupt but failed validation
checks on its ASN fields. The channel is <insert_3>; in
some cases its name cannot be determined and so is Explanation: The SSL key repository cannot be used
shown as ’????’. The channel did not start. because MQ cannot obtain a password to access it.
Reasons giving rise to this error include:
Response: Ensure that the remote system has a valid
(a) the key database file and password stash file are not
SSL certificate. Restart the channel.
present in the location configured for the key
repository,
AMQ9657 The key repository could not be opened (b) the key database file exists in the correct place but
(channel <insert_3>). that no password stash file has been created for it,
(c) the files are present in the correct place but the
Severity: 30 : Severe error userid under which MQ is running does not have
Explanation: The key repository could not be opened. permission to read them,
The key repository either does not exist or has incorrect (d) one or both of the files are corrupt.
permissions associated with it. The channel is The channel is <insert_3>; in some cases its name
<insert_3>; in some cases its name cannot be cannot be determined and so is shown as ’????’. The
determined and so is shown as ’????’. The channel did channel did not start.
not start. Response: Ensure that the key repository variable is
Response: Ensure that the key repository you specify set to where the key database file is. Ensure that a
exists and that its permissions are such that the MQ password stash file has been associated with the key
process involved can read from it. Restart the channel. database file in the same directory, and that the userid
under which MQ is running has read access to both
files. If both are already present and readable in the
correct place, delete and recreate them. Restart the
channel.

working correctly. Check that the remote certificates
AMQ9661 Bad SSL data from peer on channel
you are using conform to the X509 General Name
<insert_3>.
formats listed. Fix the problem and restart the channel.
Explanation: An SSL channel has stopped because bad AMQ9663 An invalid SSL certificate was received
SSL data was received from the remote end of the from the remote system.
channel. More detail on the nature of the corruption
can be found from the GSKit return value of <insert_1>
(the GSKit return values are documented in the MQ Explanation: An SSL certificate received from the
manuals). The channel is <insert_3>; in some cases its remote system failed validation checks on its signature.
name cannot be determined and so is shown as ’????’. The channel is <insert_3>; in some cases its name
Response: Ensure you are connecting to a version of
channel did not start.
MQ which supports SSL at the remote end of the
channel. Check your network between the two ends of Response: Ensure that the remote system has a valid
the channel, and consider whether any possible causes SSL certificate. Restart the channel.
of message corruption could be present. Fix any
problems which may exist and restart the channel.
AMQ9664 Bad userid for CRL LDAP server; SSL
channel <insert_3>.
AMQ9661 (iSeries) Bad SSL data from peer on
channel <insert_3>. Severity: 30 : Severe error
Severity: 0 : Information Explanation: Certification Revocation List (CRL)

checking on an LDAP server or servers has been
Explanation: An SSL channel has stopped because bad configured on the local MQ system. The userid
SSL data was received from the remote end of the information configured for the LDAP server or servers
channel. More detail on the nature of the corruption is incorrect. The channel is <insert_3>; in some cases its
can be found from the GSKit return value of <insert_1> name cannot be determined and so is shown as ’????’.
(the GSKit return values are documented in the MQ The channel did not start.
manuals and also in the GSKSSL member of the H file
in library QSYSINC). The channel is <insert_3>; in some Response: Check the userid information for the CRL
cases its name cannot be determined and so is shown LDAP server or servers you have configured locally.
as ’????’. Correct any problems found and restart the channel.
Response: Ensure the remote queue manager and

channel listener are running and that you are AMQ9665 SSL connection closed by remote end of
connecting to a version of MQ which supports SSL at channel <insert_3>.
the remote end of the channel. Check your network Severity: 30 : Severe error
between the two ends of the channel, and consider
whether any possible causes of message corruption Explanation: The SSL connection was closed by the
could be present. Fix any problems which may exist remote end of the channel during the SSL handshake.
and restart the channel. The channel is <insert_3>; in some cases its name
AMQ9662 SSL has encountered something it does
not support. Response: Check the remote end of the channel for
SSL-related errors. Fix them and restart the channel.
Explanation: This error can arise for a number of AMQ9666 Error accessing CRL LDAP servers; SSL
reasons: 1) The platform does not support a given type channel <insert_3>.
of cryptographic hardware, e.g. Ncipher and Rainbow
are/were not supported on the Linux/390 platform. 2) Severity: 30 : Severe error
The cryptographic hardware cryptography has returned Explanation: CRL checking on LDAP servers has been
an error. 3) Unsupported X509 General Name format configured on the local MQ system. An error was
when checking the remote certificate. The GSKit SSL found when trying to access the CRL LDAP servers
provider incorporated in MQ only supports formats when validating a certificate from the remote system.
rfc822, DNSName, directoryname, uniformResourceID, Possible causes are:
and IPAddress. The channel is <insert_3>; in some cases (a) cannot connect to any of the LDAP servers, or
its name cannot be determined and so is shown as (b) invalid login user id or password for an LDAP
’????’. The channel did not start. server, or
Response: Check that your cryptographic hardware is (c) the certificate issuer’s Distinguished Name (DN) is
supported on your platform and test it to see that it is not defined in the DIT of an LDAP server.
Chapter 7. 9000-9999 - Remote 235

The channel is <insert_3>; in some cases its name cannot be determined and so is shown as ’????’. The
cannot be determined and so is shown as ’????’. The channel did not start.
Response: Ensure that the correct PKCS #11 card is
Response: Check access to the CRL LDAP server(s) present in the slot. Restart the channel.
you have configured locally. Put right any problems
found and restart the channel.
AMQ9671 The PKCS #11 token password specified
is invalid.
AMQ9667 Bad password for CRL LDAP server;
SSL channel <insert_3>.
Explanation: The password to access the PKCS #11
token is invalid. This is specified to MQ in the PKCS
Explanation: Certification Revocation List (CRL) #11 token password field of the GSK_PKCS11 SSL
checking on an LDAP server or servers has been CryptoHardware parameter. The channel is <insert_3>;
configured on the local MQ system. The password in some cases its name cannot be determined and so is
information configured for the LDAP server or servers shown as ’????’. The channel did not start.
is incorrect. The channel is <insert_3>; in some cases its
Response: Ensure that the PKCS #11 token password
name cannot be determined and so is shown as ’????’.
specified on GSK_PKCS11 allows access to the PKCS
#11 token specified on GSK_PKCS11. Restart the
Response: Check the password information for the channel.
CRL LDAP server or servers you have configured
locally. Correct any problems found and restart the
AMQ9672 An SSL security call failed.
channel.
AMQ9668 The specified PKCS #11 shared library Explanation: An SSPI call to the Secure Channel
could not be loaded. (Schannel) SSL provider failed. The failure has caused
WebSphere MQ channel name <insert_3> to be closed.
If the name is ’????’ then the name is unknown.
Explanation: A failed attempt was made to load the
Response: Consult the Windows Schannel reference
PKCS #11 shared library specified to MQ in the PKCS
manual to determine the meaning of status <insert_5>
#11 driver path field of the GSK_PKCS11 SSL
for SSPI call <insert_4>. Correct the failure and if
CryptoHardware parameter. The channel is <insert_3>;
necessary re-start the channel.
in some cases its name cannot be determined and so is
shown as ’????’. The channel did not start.
AMQ9673 SSL client handshaking failed.
Response: Ensure that the PKCS #11 shared library
exists and is valid at the location specified. Restart the Severity: 30 : Severe error
channel.
Explanation: During an SSL client’s handshaking, an
SSPI call to the Secure Channel (Schannel) SSL provider
AMQ9669 The PKCS #11 token could not be failed. The failure has caused WebSphere MQ channel
found. name <insert_3> to be closed. If the name is ’????’ then
the name is unknown.
Explanation: The PKCS #11 driver failed to find the
token specified to MQ in the PKCS #11 token label field
of the GSK_PKCS11 SSL CryptoHardware parameter.
The channel is <insert_3>; in some cases its name
channel did not start. AMQ9674 An unknown error occurred during an
SSL security call.
Response: Ensure that the PKCS #11 token exists with
the label specified. Restart the channel. Severity: 30 : Severe error
Explanation: An unknown error occurred during an
AMQ9670 PKCS #11 card not present. SSPI call to the Secure Channel (Schannel) SSL
provider. The error may be due to a Windows SSL
problem or to a general Windows problem or to invalid
Explanation: A PKCS #11 card is not present in the WebSphere MQ data being used in the call. The
slot. The channel is <insert_3>; in some cases its name WebSphere MQ error recording routine has been called.
The error has caused WebSphere MQ channel name

AMQ9677 The Windows security services library
name is unknown.
could not be loaded.
for SSPI call <insert_4>. If the problem can be resolved Explanation: WebSphere MQ requires <insert_3> to be
using the manual, correct the failure and if necessary available in order to run or configure SSL functionality.
re-start the channel. If the problem cannot be resolved The attempt to load this library returned the Windows
then use the standard facilities supplied with your error code <insert_1>. The WebSphere MQ error
system to record the problem identifier and save the recording routine has been called.
generated output files, and then contact your IBM
Response: Consult the Windows reference manual to
determine the meaning of error code <insert_1>. Check
that the <insert_3> file is available and not corrupt. If
the problem cannot be resolved then use the standard
AMQ9675 The requested certificate could not be facilities supplied with your system to record the
found. problem identifier and save the generated output files,
Explanation: A request for a certificate identified as
<insert_4> <insert_5> in the store <insert_3> has failed,
AMQ9678 The certificate <insert_4>/<insert_5>
because the certificate could not be found. The
already exists in the store <insert_3>.
Windows error code has been set to <insert_1>. The
WebSphere MQ error recording routine has been called. Severity: 10 : Warning
Response: Consult the Windows reference manual to Explanation: The certificate store <insert_3> already
determine the meaning of error <insert_1> if this value contains the specified certificate, identified by the issuer
is non-zero. Check to see whether the specified name of <insert_4>, serial number <insert_5>. The
certificate has been copied to the correct certificate store existing certificate has not been replaced.
and has not been deleted. Use the amqmcert command
line utility or the WebSphere MQ Explorer
AMQ9679 The certificate store <insert_3> could not
administration application to configure certificate store
be opened.
for use with WebSphere MQ. If the problem cannot be
resolved then use the standard facilities supplied with Severity: 30 : Severe error
your system to record the problem identifier and save
the generated output files, and then contact your IBM Explanation: The certificate store <insert_3> could not
support center. Do not discard these files until the be opened, and failed with the Windows error code
problem has been resolved. <insert_1>. The WebSphere MQ error recording routine
has been called.
AMQ9676 The Windows cryptographic services Response: Consult the Windows reference manual to
library could not be loaded. determine the meaning of error <insert_1> if this value
is non-zero. Check that either your MQSSLKEYR
Severity: 30 : Severe error environment variable (for client connections), or
SSLKEYR queue manager attribute (for WebSphere MQ
Explanation: WebSphere MQ requires crypt32.dll to be
queue managers) has been defined correctly, and that
available in order to carry out cryptographic
the file path specified is valid. If the problem cannot be
functionality. The attempt to load this library returned
resolved then use the standard facilities supplied with
the Windows error code <insert_1>. The WebSphere
MQ error recording routine has been called.
the generated output files, and then contact your IBM
Response: Consult the Windows reference manual to support center. Do not discard these files until the
determine the meaning of error code <insert_1>. Check problem has been resolved.
that the crypt32.dll file is available and not corrupt. If
the problem cannot be resolved then use the standard
AMQ9680 A problem was encountered with the
specified certificate file.
problem identifier and save the generated output files,
and then contact your IBM support center. Do not Severity: 30 : Severe error
Explanation: A problem occurred when attempting to
read the certificate from the file <insert_3>. The file
may be corrupt or incorrectly formatted. The Windows
error code reported is <insert_1>. The WebSphere MQ
Chapter 7. 9000-9999 - Remote 237

Response: Ensure that the certificate file is valid and problem cannot be resolved then use the standard
complete, and in one of the file formats supported by facilities supplied with your system to record the
WebSphere MQ. If the problem cannot be resolved then problem identifier and save the generated output files,
use the standard facilities supplied with your system to and then contact your IBM support center. Do not
record the problem identifier and save the generated discard these files until the problem has been resolved.
output files, and then contact your IBM support center.
AMQ9684 A problem occurred while attempting to
resolved.
access the certificate’s properties.
AMQ9681 The requested functionality is not
supported on this system. Explanation: The certificate issued by <insert_3> with
serial number <insert_4>, or it’s private key data,
appears to be unusable and may be corrupt. The
Explanation: An SSL function was attempted that is Windows return code <insert_1> was generated when
not supported on this system. a) importing pfx format attempting to use this certificate. The WebSphere MQ
certificate files with private key data is only supported error recording routine has been called.
on Windows 2000 or greater. b) a the security library
installed on your system is not of the correct level and
determine the meaning of error <insert_1>. Check that
does not contain the pre-requisite functions. On pre
the certificate is valid and has not been corrupted. If it
Windows 2000 systems, Internet Explorer 4.1 or greater
is possible that the certificate or private key data is
must be installed. The WebSphere MQ error recording
corrupt, try to remove the certificate from your system
and re-import it. If the problem cannot be resolved then
Response: If pre-requisite software is missing, please use the standard facilities supplied with your system to
install the necessary levels of software and retry the record the problem identifier and save the generated
operation. If the problem cannot be resolved then use output files, and then contact your IBM support center.
the standard facilities supplied with your system to Do not discard these files until the problem has been
record the problem identifier and save the generated resolved.
AMQ9685 A problem occured while accessing the
resolved.
registry.
AMQ9682 The WebSphere MQ SSL library has not
been initialized. Explanation: An error occured while attempting to
load or unload the personal registry hive
(HKEY_LOCAL_USER) for the user who launched this
Explanation: The WebSphere MQ SSL library process. The WebSphere MQ error recording routine
’amqcssln.dll’ has been called without it first being has been called.
initialized by the calling process.
Response: If the problem cannot be resolved then use
Response: Ensure that the initialization function has the standard facilities supplied with your system to
been called prior to issuing any amqcssln function calls. record the problem identifier and save the generated
AMQ9683 The private key data for this certificate
resolved.
is not exportable.
AMQ9686 An unexpected error occured while
Explanation: An attempt has been made to export the attempting to manage a certificate store.
private key data from a certificate, but the properties of
the certificate will not allow this. WebSphere MQ needs
to be able to export private key data when copying Explanation: The Windows cryptographic API
personal certificates between certificate stores. The returned error code <insert_1> when calling the
Windows cryptographic API returned the error code function <insert_3> for certificate store <insert_4>. The
<insert_1>. error may be due to a certificate store problem or to a
general Windows problem or to a problem with a
Response: When requesting the certificate from the
certificate in the store. The WebSphere MQ error
certificate authority, the private key data must be
recording routine has been called.
marked as exportable to enable WebSphere MQ to be
able to copy the certificate and private key data into a Response: Consult the Windows reference manual to
WebSphere MQ store. The certificate file may need to determine the meaning of error <insert_1>. Check that
be requested again to resolve this problem. If the the certificate store is valid and not corrupt. If the

problem cannot be resolved then use the standard
AMQ9690 The public key in the issuer’s certificate
has failed to validate the subject
problem identifier and save the generated output files,
certificate.
discard these files until the problem has been resolved. Severity: 30 : Severe error
Explanation: The public key in the issuer’s certificate
AMQ9687 The pfx password provided is invalid. (CA or signer certificate), is used to verify the signature
on the subject certificate assigned to channel <insert_3>.
This verification has failed, and the subject certificate
Explanation: The password supplied for importing or therefore cannot be used. The WebSphere MQ error
copying the certificate is incorrect, and the operation recording routine has been called.
could not be completed.
Response: Check that the issuer’s certificate is valid
Response: Make sure the password is correct and try and available, and that it is up to date. Verify with the
again. If the password has been forgotten or lost, the certificate’s issuer that the subject certificate and issuer
certificate will need to be regenerated or exported from certificate should still be valid. If the problem cannot be
the original source. resolved then use the standard facilities supplied with
AMQ9688 The private key data for this certificate support center. Do not discard these files until the
is unavailable. problem has been resolved.
Explanation: The private key data associated with this AMQ9691 The WebSphere MQ MQI library could
certificate is reported as being present on the system, not be loaded.
but has failed, returning the Windows error code Severity: 30 : Severe error
<insert_1>. The WebSphere MQ error recording routine
has been called. Explanation: The library file <insert_3> is expected to
be available on your system, but attempts to load it
Response: Consult the Windows reference manual to have failed with Windows return code <insert_1>. The
determine the meaning of error code <insert_1>. If the WebSphere MQ error recording routine has been called.
problem can be resolved using the manual, correct the
failure and if necessary re-try the operation. If the Response: Ensure that the WebSphere MQ <insert_3>
problem cannot be resolved then use the standard library file exists and is available on your system.
facilities supplied with your system to record the Consult the Windows reference manual to determine
problem identifier and save the generated output files, the meaning of error code <insert_1>. If the problem
and then contact your IBM support center. Do not cannot be resolved then use the standard facilities
discard these files until the problem has been resolved. supplied with your system to record the problem
identifier and save the generated output files, and then
contact your IBM support center. Do not discard these
AMQ9689 An unknown error occurred deleting the files until the problem has been resolved.
store <insert_3>.
Severity: 30 : Severe error AMQ9692 The SSL library has already been
Explanation: The WebSphere MQ certificate store for initialized.
queue manager <insert_3> could not be deleted. The Severity: 20 : Error
filename for the certificate store is <insert_4>. The
Windows error code has been set to <insert_1>. The Explanation: The SSL library has already been
WebSphere MQ error recording routine has been called. initialized once for this process, any changes to SSL
attributes will not take affect, and the original values
Response: Consult the Windows reference manual to will remain in force.
determine the meaning of error <insert_1>. If the
problem can be resolved using the manual, correct the Response: If the problem cannot be resolved then use
failure and if necessary re-try the operation. Check that the standard facilities supplied with your system to
the store file exists and that other processes (such as record the problem identifier and save the generated
queue managers) that may be accessing the store are output files, and then contact your IBM support center.
not running. If the problem cannot be resolved then use Do not discard these files until the problem has been
the standard facilities supplied with your system to resolved.
record the problem identifier and save the generated
resolved.
Chapter 7. 9000-9999 - Remote 239

AMQ9693 The password provided for the LDAP AMQ9696 Usage: amqmcert [SERVERNAME] [-a
server is incorrect. handle]
[-k SSLKeyR|CA|ROOT|MY] [-m
QueueMgr]
Explanation: One or more of the LDAP servers used [-s CertFile] [-p PersonalCertFile] [-z
for providing CRL information to WebSphere MQ has Password]
rejected a login attempt because the password provided [-x handle] [-l] [-d handle] [-r handle]
is incorrect. The WebSphere MQ error recording routine [-u]
has been called. The error has caused WebSphere MQ [-h]
channel name <insert_3> to be closed. If the name is
’????’ then the name is unknown.
Response: Ensure that the passwords specified in the
AuthInfo objects are correct for each server name Response: None.
provided. If the problem cannot be resolved then use
the standard facilities supplied with your system to
AMQ9697 WebSphere MQ Services could not be
contacted on the target server.
Do not discard these files until the problem has been Severity: 30 : Severe error
resolved.
Explanation: An attempt was made to contact the
WebSphere MQ Services on the target server <insert_3>.
AMQ9694 The DN syntax provided for an LDAP The call failed with return code <insert_1>. The
search is invalid. WebSphere MQ error recording routine has been called.
Severity: 30 : Severe error Response: Ensure that the target server name
specified is correct and that you have sufficient access
Explanation: The distinguished name provided in one
rights on that server to be able to administer
or more AuthInfo object definitions is invalid, and the
WebSphere MQ. If the problem cannot be resolved then
request to a CRL LDAP server has been rejected. The
use the standard facilities supplied with your system to
WebSphere MQ error recording routine has been called.
The error has caused WebSphere MQ channel name
name is unknown.
resolved.
Response: Verify that the details supplied in the
AuthInfo object definitions for this channel are correct.
AMQ9698 An SSL security call failed during SSL
If the problem cannot be resolved then use the
handshaking.
the problem identifier and save the generated output Severity: 30 : Severe error
files, and then contact your IBM support center. Do not
discard these files until the problem has been resolved. Explanation: An SSPI call to the Secure Channel
(Schannel) SSL provider failed during SSL handshaking.
The failure has caused WebSphere MQ channel name
AMQ9695 The username provided for the LDAP <insert_3> to be closed. If the name is ’????’ then the
server is incorrect. name is unknown.
Severity: 30 : Severe error Response: Consult the Windows Schannel reference
Explanation: One or more of the LDAP servers used
for providing CRL information to WebSphere MQ has
rejected a login attempt because the username provided
does not exist. The WebSphere MQ error recording
routine has been called. The error has caused AMQ9699 An unknown error occurred during an
WebSphere MQ channel name <insert_3> to be closed. SSL security call during SSL
If the name is ’????’ then the name is unknown. handshaking.
Response: Ensure that the usernamed specified in the Severity: 30 : Severe error
AuthInfo objects for this channel are correct for each
LDAP server name provided. If the problem cannot be Explanation: An unknown error occurred during an
resolved then use the standard facilities supplied with SSPI call to the Secure Channel (Schannel) SSL provider
your system to record the problem identifier and save during SSL handshaking. The error may be due to a
the generated output files, and then contact your IBM Windows SSL problem or to a general Windows
support center. Do not discard these files until the problem or to invalid WebSphere MQ data being used
problem has been resolved. in the call. The WebSphere MQ error recording routine

has been called. The error has caused WebSphere MQ cannot start while the SSL security refresh is in
channel name <insert_3> to be closed. If the name is progress. The channel is restarted automatically once
’????’ then the name is unknown. the SSL security refresh is complete.
Response: Consult the Windows Schannel reference Response: None.
for SSPI call <insert_4>. If the problem can be resolved
AMQ9714 SSL refresh on receiving queue
using the manual, correct the failure and if necessary
manager: channel did not start.
re-start the channel. If the problem cannot be resolved
then use the standard facilities supplied with your Severity: 30 : Severe error
system to record the problem identifier and save the
generated output files, and then contact your IBM Explanation: An SSL security refresh is in progress on
support center. Do not discard these files until the the queue manager at the receiving end of this SSL
problem has been resolved. channel. The channel is <insert_3>; in some cases its
name cannot be determined and so is shown as ’????’.
AMQ9710 SSL security refresh failed.
Response: Restart the channel once the SSL refresh is
Severity: 30 : Severe error complete. The channel will restart automatically if it is
configured to retry the connection.
Explanation: The request to refresh SSL security was
unsuccessful.
AMQ9715 Unexpected error detected in validating
Response: Look at previous error messages in the
SSL session ID.
error files to determine the cause of the failure.
AMQ9711 SSL security refresh succeeded but Explanation: This error can arise when the GSKit SSL
channel restarts failed. provider is missing one or more pre-requisite PTFs on
the OS/400 platform. The channel is <insert_3>; in
some cases its name cannot be determined and so is
Explanation: The SSL environments for this queue shown as ’????’.
manager have been refreshed so current values and
Response: Ensure the GSKit SSL provider is at the
certificates are in use for all SSL channels. However, not
latest level of maintenance and restart the channel.
all the outbound SSL channels which were running
when the security refresh was initiated could be
restarted after the refresh had completed. AMQ9719 Invalid CipherSpec for FIPS mode.
Response: Look at previous error messages in the Severity: 30 : Severe error
error files to determine which channels could not be
restarted. Restart these if necessary. Explanation: The user is attempting to start a channel
on a queue manager or MQ client which has been
configured to run in FIPS mode. The user has specified
AMQ9712 SSL security refresh timed out waiting a CipherSpec which is not FIPS-compliant. The channel
for channel <insert_3>. is <insert_3>; in some cases its name cannot be
determined and so is shown as ’????’.
Response: Redefine the channel to run with a
Explanation: The system was performing a security
FIPS-compliant CipherSpec. Alternatively, the channel
refresh for SSL. This function requests all outbound and
may be defined with the correct CipherSpec and the
inbound SSL channels to stop. It then waits for these
queue manager or MQ client should not be running in
channels to actually stop. SSL channel <insert_3> did
FIPS mode; if this is the case, ensure that FIPS mode is
not stop within the timeout period.
not configured. Once the error is corrected, restart the
Response: Investigate why channel <insert_3> is hung. channel.
Terminate the hung channel. Rerun the SSL security
refresh.
AMQ9720 QUEUE MANAGERS:
AMQ9713 Channel <insert_3> ended: SSL refresh
in progress. Explanation: None.
Explanation: The SSL support on this queue manager
is in the middle of a security refresh. An attempt was
made to start outbound SSL channel <insert_3>. It
Chapter 7. 9000-9999 - Remote 241

AMQ9721 Queue Manager Name: <insert_3> AMQ9727 A certificate failed to be migrated
because it has an incomplete
certification path.
Explanation: None. The certificate’s details are:
[Microsoft Certificate Store], [Subject],
Response: None. [Issuer], [Serial Number]:
<insert_3>.
AMQ9722 CLIENTS: Severity: 30 : Severe error
Severity: 0 : Information Explanation: During the migration of a certificate, the
Explanation: None. certificate’s certification authority (signer) certificate
could not be found. The certificate is therefore regarded
Response: None. as an orphan certificate.
A copy of the certificate has been written to the file
AMQ9723 Client Certificate Store: <insert_3> name <insert_4>.
If file name is suffixed ″.cer″ then the certificate is a
Severity: 0 : Information certification authority (signer) certificate. If file name is
Explanation: None. suffixed ″.pfx″ then the certificate is a personal
certificate and it has a password which is the same as
Response: None. that specified for the GSKit key database <insert_5>.
The certificate has not been migrated.
AMQ9724 Expiry Time: <insert_1> Response: If the certificate is required for migration
Migration Status: To be migrated then ensure that a complete certification path exists in
Password: ******** the GSKit key database <insert_5> before importing the
certificate.
Explanation: None.
AMQ9728 A certificate failed to be migrated
Response: None. because it could not be imported into
the GSKit key database <insert_5>.
The certificate’s details are:
AMQ9725 Expiry Time: <insert_1>
Migration Status: Failed
[Issuer], [Serial Number]:
Password: ********
<insert_3>.
Explanation: None.
Explanation: A certificate failed to be imported
Response: None. because there was a problem during the migration of
the certificate.
A copy of the certificate has been written to the file
AMQ9726 A certificate failed to be migrated name <insert_4>.
because it has an invalid date. If file name is suffixed ″.cer″ then the certificate is a
The certificate’s details are: certification authority (signer) certificate. If file name is
[Microsoft Certificate Store], [Subject], suffixed ″.pfx″ then the certificate is a personal
[Issuer], [Serial Number]: certificate and it has a password which is the same as
<insert_3>. that specified for the GSKit key database <insert_5>.
Severity: 30 : Severe error The certificate has not been migrated.
Explanation: During the migration of a certificate, the Response: Refer to the previous message in the error
certificate’s date fields have been found to be invalid. log to determine the cause of the failure. If appropriate,
The certificate has either expired or its ″from″ date is refer to the Windows or GSKit reference documentation
later than today’s date or its ″to″ date is earlier than the to determine the cause.
″from″ date.
The certificate has not been migrated. AMQ9729 Unable to create certificate file
Response: If the certificate is required for migration <insert_3>.
then obtain a valid replacement before importing it into Severity: 30 : Severe error
the GSKit key database <insert_5>.
Explanation: A certificate failed to be imported
because there was a problem during the migration of
the certificate. In addition to this first problem, a

second problem occurred when trying to create a copy entry in the registry for this store. If the request was for
of the certificate by writing it to the file <insert_3>. The a queue manager then <insert_3> is the queue manager
certificate is located in the Microsoft Certificate Store name, otherwise it is the name of the client’s Microsoft
<insert_4>. The certificate is intended for the GSKit key Certificate Store.
database <insert_5>. If file name is suffixed ″.cer″ then
Response: List, and then check, the contents of the
the certificate is a certification authority (signer)
registry by running the Transfer Certificates (amqtcert)
certificate. If file name is suffixed ″.pfx″ then the
command with the options ″-a -l″. If it is necessary to
certificate is a personal certificate. The certificate has
replace the entry then firstly remove it, by using
not been migrated.
amqtcert with the ″-r″ option, then use amqtcert to
Response: Determine the cause of the 2 problems. request automatic migration.
Refer to the previous message in the error log to
determine the cause of the first failure. If appropriate,
AMQ9733 The request to automatically migrate
refer to the Windows or GSKit reference documentation
certificates has completed successfully.
to determine the cause. The second failure occurred
during a call to the Windows ’CreateFile’ function with Severity: 0 : Information
a return code of <insert_1>. For this failure, check that
file does not already exist and that you have authority Explanation: A request was made to automatically
to create this file. migrate SSL certificates. This request may have been
made during the installation of WebSphere MQ or by
using the Transfer Certificates (amqtcert) command.
AMQ9730 Certificate migration has completed The request has now been performed and the migration
with no failures. The number of has completed successfully.
certificates migrated was <insert_1>.
Response: Use the GSKit iKeyman GUI to verify that
Severity: 0 : Information the GSKit key database contains all the certificates
required to support the intended SSL channel. If no
Explanation: The migration of certificates from the
certificates were migrated then this is because the
Microsoft Certificate Store <insert_3> to the GSKit key
Microsoft Certificate Store contained only a default set
database <insert_4> has completed and there were no
of certification authority (signer) certificates. The
migration failures. The number of certificates migrated
default set is not migrated because the newly created
was <insert_1>.
GSKit key database will have its own set which will be
Response: If any certificates were migrated, use the the same or more up to date.
GSKit iKeyman GUI to verify that the GSKit key
database contains all the certificates required to support
AMQ9734 There was a failure during the
the intended SSL channel. If no certificates were
automatic migration of certificates.
migrated then this is probably because <insert_3>
contained only a default set of certification authority Severity: 30 : Severe error
(signer) certificates. The default set is not migrated
because the newly created GSKit key database will Explanation: A request was made to automatically
have its own set which will be the same or more up to migrate SSL certificates. This request may have been
date. made during the installation of WebSphere MQ or by
Although there were no failures which caused using the Transfer Certificates (amqtcert) command.
certificates not to be migrated, there may have been The request has now been performed but there was a
other failures and these must be resolved otherwise the failure during the migration process.
SSL channel may subsequently fail to start. Refer to the Response: Refer to previous messages in the error log
error log and check for any failures. to determine the cause of the failure. It may be the case
that all certificates have successfully migrated and that
AMQ9731 The Transfer Certificates (amqtcert) the failure did not affect this part of the migration
command has completed. process. In this case, use the GSKit iKeyman GUI to
verify that the GSKit key database contains all the
Severity: 0 : Information certificates required to support the intended SSL
channel.
Response: None.
AMQ9735 Certificate migration has terminated

AMQ9732 A registry entry already exists for
unexpectedly. A failure occured during
<insert_3>.
GSKit initialization.
Explanation: The command has been used to request
Explanation: The certificate migration process has
automatic migration for a queue manager’s or a client’s
terminated unexpectedly. The migration requires the
Microsoft Certificate Store. However, there is already an
GSKit environment to be successfully initialized. This
Chapter 7. 9000-9999 - Remote 243

involves the GSKit operations of initialization, creation
of the key database and stashing of the key database
be accessed.
password. There was a failure during one of these
operations. No certificates have been migrated. If the Severity: 30 : Severe error
stashing of the password failed then the key database
Explanation: The certificate store <insert_3> could not
<insert_4> will have been created. The failure occurred
be accessed, and failed with Windows error code
during the GSKit operation <insert_3> and the GSKit
<insert_1>. If you are using the -c parameter check that
return code <insert_1> was generated.
the name given to amqtcert is correct. If you are using
Response: If the key database has been created then, the -m parameter check the SSLKEYR value on the
after the cause of the failure has been resolved, delete queue manager specified.
it, remove the relevant registry state information and
then re-try the certificate migration process. Use the
determine the meaning of error <insert_1> if this value
is non-zero. If the problem cannot be resolved then use
the problem identifier and save the generated output
files, and then contact your IBM support center. Do not
AMQ9736 The library <insert_3> was not found. resolved.
be opened.
library <insert_3> failed because the library was not
found. If this an WebSphere MQ library, it is only Severity: 30 : Severe error
available on WebSphere MQ server installations and is
Explanation: The certificate store <insert_3> could not
required when the Transfer Certificates (amqtcert)
be opened, and failed with Windows error code
command is used to perform a queue manager
<insert_1>.
operation. If this a GSKit library, it should have been
installed during the WebSphere MQ installation. Response: Consult the Windows reference manual to
determine the meaning of error <insert_1> if this value
Response: Do not use the command to perform a
is non-zero. If the problem cannot be resolved then use
queue manager operation on a WebSphere MQ
client-only installation. If the command has been made
on a WebSphere MQ server installation, or if it is a
GSKit library which is missing, then record the
problem identifier, save any generated output files and
resolved.
then contact your IBM support center. Do not discard
these files until the problem has been resolved.
AMQ9741 A problem occurred during a Windows
operation.
AMQ9737 Unable to allocate memory.
Explanation: During operation <insert_3>, the
Explanation: An attempt to allocate memory failed.
Windows return code <insert_1> was generated.
Response: Make more memory available to the
command.
determine the meaning of return code <insert_1> for
operation <insert_3>.
AMQ9738 Unable to obtain the MQSSLKEYR
environment variable value.
AMQ9742 A problem occured during a GSKit
Severity: 30 : Severe error operation.
Explanation: An attempt to obtain the MQSSLKEYR Severity: 30 : Severe error
environment variable value failed. When using the
Explanation: During operation <insert_3>, the GSKit
command to specify all clients then the MQSSLKEYR
environment variable must be defined with the name of
a Microsoft Certificate Store file containing certificates Response: Use the standard facilities supplied with
for all clients. your system to record the problem identifier and save
Response: Ensure that the MQSSLKEYR environment
variable is defined with an appropriate value.

AMQ9743 A certificate failed to be migrated and AMQ9747 Usage: amqtcert [-a] [-c [Filename | *]]
failed to be logged. [-e ExpirationTime] [-g FileName]
The certificate’s details are: [-i ListNumber] [-l] [-m [QMgrName |
[Microsoft Certificate Store], [Subject], *]] [-p Password]
[Issuer], [Serial Number]: [-r] [-u ClientLogonID] [-w FileName]
<insert_3>.
Response: None.
Explanation: There was a problem trying to migrate a
certificate to the GSKit key database <insert_5>.
AMQ9748 A problem occurred accessing the
Response: Refer to the previous message in the error Windows registry.
log to determine why the migration failed.
Explanation: An attempt to access a key or value or
AMQ9744 No matching automatic migration
data field in the Windows registry key failed. The
registry entry.
failure may be due to part of the registry being in an
Severity: 10 : Warning invalid state or may be due to insufficient authority to
access that part. The WebSphere MQ error recording
Explanation: There is no automatic certificate
migration entry in the registry which matches the input
provided. Response: If <insert_3> includes the name of a
Windows call, consult the Windows reference manual
Response: None, if the entry to be removed was
to determine the meaning of status <insert_1> for that
correctly specified. Otherwise, input the command
call. Use the standard facilities supplied with your
again with correct parameters.
system to record the problem identifier, and to save the
AMQ9745 amqtcert: insufficient memory to center. Do not discard these files until the problem has
migrate certificates. been resolved.
AMQ9749 Invalid combination of command
Explanation: An attempt to allocate memory failed arguments.
while amqtcert was migrating certificate file
<insert_3>.sto’. The migration did not complete Severity: 30 : Severe error
successfully.
Explanation: The command syntax is incorrect
Response: Do not delete <insert_3>.sto’, but delete all because of an invalid combination of arguments.
other files called <insert_4>.*’ (these were created as a
Response: Re-try the command using a valid
result of the failed migration). Also, if you want to
combination of arguments.
rerun this migration automatically, use the -r flag on
amqtcert to remove the automatic migration registry
entry for this .sto file. Then use the -a flag on amqtcert AMQ9750 File <insert_3> already exists.
to create a new automatic migration registry entry for
this .sto file.
Make more memory available. Rerun the migration. Explanation: The file <insert_3> cannot be created
because it already exists.
AMQ9746 File <insert_3> not found. Response: Ensure that the file does not exist in the
directory. If necessary, make a copy of the file before
renaming or moving or deleting it.
Explanation: The file specified as a command
argument has not been found. The characters ″.sto″
AMQ9751 You are not authorized to perform the
have been automatically appended to the file name.
requested operation.
Response: Check that file exists and that it is specified
as the absolute (rather than relative) directory path and
file name (excluding the .sto suffix) of the Microsoft Explanation: You tried to issue a command for which
Certificate Store. you are not authorized.
Response: Contact your system administrator to
perform the command for you or to request authority
to perform the command.
Chapter 7. 9000-9999 - Remote 245

Response: If any certificates were migrated, use the
GSKit iKeyman GUI to verify that the GSKit key
because a Windows operation failed.
database contains all the certificates required to support
The certificate’s details are:
the intended SSL channel. The failures must be
resolved otherwise the SSL channel may subsequently
[Issuer], [Serial Number]:
fail to start. Refer to previous messages in the error log
<insert_4>.
to determine the cause of such failures.
Explanation: A personal certificate could not be AMQ9756 The number of certificates in the
migrated because there was a failure during the Microsoft Certificate Store <insert_3> is
Windows operation <insert_3> with a return code of <insert_1>.
<insert_1>. A personal certificate is exported, with its
private key data, from the Microsoft Certificate Store
prior to being imported into the GSKit key database. Explanation: Provides a count of the number of
The failure occurred during the export and is probably certificates in the Microsoft Certificate Store <insert_3>.
due to a problem with accessing or using the private
key data assoicated with the personal certificate. Response: None.
Response: Check that the private key data is available

and that you have authority to access it. Consult the AMQ9757 Certificate <insert_1>
Windows reference manual to determine the meaning Severity: 0 : Information
of return code <insert_1> for operation <insert_3>.
Explanation: None.
AMQ9753 File <insert_3> is empty. Response: None.

AMQ9758 Subject: <insert_3>
Explanation: The file <insert_3> cannot be used
because it is empty. Severity: 0 : Information
Response: Ensure that the correct file has been used Explanation: None.
and if necessary investigate the reason for it being Response: None.
empty.
AMQ9759 Issuer: <insert_3>

because a GSKit operation failed. Severity: 0 : Information
The certificate’s details are: Explanation: None.
[Issuer], [Serial Number]: Response: None.
<insert_4>.
Severity: 30 : Severe error AMQ9760 Valid From: <insert_3> to <insert_4>
Explanation: During operation <insert_3>, the GSKit Severity: 0 : Information
Explanation: None.
Response: None.
support center. Do not discard these files until the AMQ9761 Certificate Usage: <All>
Explanation: None.
AMQ9755 Certificate migration has completed
with some failures. The number of Response: None.
certificates migrated was <insert_1>.
Severity: 0 : Information AMQ9762 Certificate Usage: <insert_3>
Explanation: The migration of certificates from the Severity: 0 : Information
Microsoft Certificate Store <insert_3> to the GSKit key
database <insert_4> has completed but there has been Explanation: None.
one or more failures. The number of certificates Response: None.
migrated was <insert_1>.

Response: Check that the directory exists and that it is
AMQ9763 Certificate Type: Personal
specified as an absolute (rather than relative) directory
Severity: 0 : Information path.
Explanation: None.
AMQ9769 Usage: runmqckm
Response: None.
-keydb -changepw Change the password
for a key database
AMQ9764 Certificate Type: Signer -convert Convert the format of a key
database
Severity: 0 : Information -create Create a key database
Explanation: None. -delete Delete a key database
-stashpw Stash the password of a key
Response: None. database into a file
-list Currently supported types of key
AMQ9765 Personal certificate not found for the database.
command option ″-i <insert_1>″. -cert -add Add a CA Certificate
-create Create a self-signed certificate
Severity: 30 : Severe error -delete Delete a certificate
Explanation: The Transfer Certificates (amqtcert) -details Show the details of a specific
command was executed using the ″-i ListNumber″ certificate
option with a value of <insert_1>. However, no -export Export a personal certificate and
personal certificate was found which corresponded to associated private key into a PKCS12
this value. Certificate migration has failed and no file or a key database
certificates were migrated. -extract Extract a certificate from a key
database
Response: Check that the option value corresponds to -getdefault Show the default personal
a correctly identified personal certificate. If it is not certificate
correct then run the command using the ″-l List″ option -import Import a certificate from a key
to determine the correct number. A GSKit key database, database or a PKCS12 file
and its associated key database files, was created when -list List certificates in a key database
the command was run using the ″-i ListNumber″ -modify Modify a certificate (NOTE: the
option. The database and associated files must be only field that my be modified is the
deleted before re-trying the command with the ″-i″ trust field)
option. -receive Receive a certificate
-setdefault Set the default personal
certificate
AMQ9766 A failure occurred creating the GSKit
-sign Sign a certificate
key database <insert_4>.
-certreq -create Create a certificate
Severity: 30 : Severe error request
-delete Delete a certificate request from
Explanation: GSKit was unable to create the key
a certificate request database
database and its associated files. During the GSKit
-details Show the details of a specific
operation <insert_3>, the return code <insert_1> was
certificate request
generated. This is probably due to insufficient authority
-extract Extract a certificate from a
or to insufficient disk space being available.
certificate request database
Response: Check that you have sufficient authority -list List all certificate requests in a
and that there is sufficient disk space available. certificate request database
-recreate Recreate a certificate request
-version Display ikeycmd version
AMQ9767 Usage: strmqikm information
[iKeymanWorkingDirectory] -help Display this help text
AMQ9768 Directory <insert_3> not found.

Explanation: The directory specified as a command
argument has not been found.
Chapter 7. 9000-9999 - Remote 247

AMQ9913 The specified local address <insert_3> AMQ9922 Maximum wait time exceeded on queue
cannot be resolved to an IP address. The <insert_3>.
return code is <insert_1>.
Explanation: The maximum time waiting for a
Explanation: An attempt to resolve the local address message to arrive on queue <insert_3> has been
hostname to an IP address has failed. exceeded.
Response: Check that the local address hostname is Response: Ensure that the queue is not put inhibited.
correct and has an entry in the DNS database. Ensure that messages are being written to the queue.
AMQ9914 The type of local address specified is AMQ9923 Insufficient parameters on command.
incompatible with the IP protocol
(<insert_3>) used.
Explanation: The SOAP command has been issued
with insufficient paramaters.
Explanation: An attempt to use a local address that is
Response: Supply the correct number of parameters
incompatible with the IP protocol used.
and reissue the command.
Response: Make sure that the local address specified
is of the same type (IPv4 or IPV6) as the IP Protocol.
AMQ9924 Usage: amqwSOAPNETListener -u
wmqUri
AMQ9915 The IP protocol <insert_3> is not present [-w WebServiceDirectory] [-n
on the system. MaxThreads]
[-d StayAlive] [-i IdContext]
[-x TransactionalControl] [-a Integrity]
Explanation: An attempt to use an IP protocol that is [-? ThisHelp]
not present on the system has been made.
Response: Install the required IP protocol or use an IP
protocol that is available on the system.
Response: None.
AMQ9920 A SOAP Exception has been thrown.
<insert_3>.
Explanation: A SOAP method encountered a problem
and has thrown an exception. Details of the exception
are: Explanation: A SOAP application or the SOAP listener
<insert_3> cannot connect to the queue manager <insert_3> using
<insert_4> bindings.
Response: Investigate why the SOAP method threw
the exception. Response: Ensure the bindings are set to the correct
value and that the queue manager exists. Check any
error messages from the Java MQQueueManager class.
AMQ9921 An error was encountered writing to the
Dead Letter Queue.
AMQ9926 Null SOAP action specified in a
received SOAP message.
Explanation: An error was encountered when an
attempt was made to write a message to Dead Letter
Queue <insert_3>. The message was <insert_4>. Explanation: A NULL soap action has been specified
in the SOAP message <insert_3>. The message will not
Response: Ensure that Dead Letter Queue <insert_3>
be processed.
exists and is put enabled. Ensure that the Queue
Manager attribute DEADQ is set up correctly. Resend Response: Include the appropriate SOAP action in the
the SOAP message. SOAP message.

AMQ9927 MQ queue backout threshold exceeded. AMQ9933 Options <insert_3> and <insert_4> are
mutually exclusive
Explanation: The WebSphere MQ backout threshold
value has been exceeded for queue <insert_3>, Explanation: The SOAP command was issued with
processing message <insert_4>. incompatible options <insert_3> and <insert_4>.
Response: Correct the backout threshold value for Response: Reissue the SOAP command supplying
queue <insert_3> and resend the SOAP message. compatible options.
AMQ9928 Target service or URI is missing from a AMQ9934 Could not parse URL <insert_3>.
SOAP message. MQCC_FAILED(2)
MQRC_SOAP_URL_ERROR(2212).
Explanation: The target service or the target URI is
missing from SOAP message <insert_3>. Explanation: .Could not parse URL
<insert_3>.MQCC_FAILED(2)
Response: Supply a target service or the target URI in
the SOAP message.
Response: Correct the URL and retry.
AMQ9929 Message backout for message
(<insert_3>) failed. AMQ9935 Illegal URL <insert_3>.
MQCC_FAILED(2)
Explanation: Backout for a message has failed.
Response: Investigate the reason for the backout
Explanation: .The URL <insert_3> failed validation..
failure.
MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
AMQ9930 Required Option <insert_3> missing
from command.
AMQ9936 Cannot get connection using <insert_3>
bindings. MQCC_FAILED(2)
Explanation: The SOAP command was issued with MQRC_CONNECTION_ERROR(2273).
manadatory option <insert_3> missing.
Response: Reissue the SOAP command supplying the
Explanation: .Cannot get connection using <insert_3>
missing option.
bindings. MQCC_FAILED(2)
MQRC_CONNECTION_ERROR(2273).
AMQ9931 Invalid value <insert_3> specified for
Response: Check that the queue manager is available
option <insert_4>.
and running.
Explanation: THE SOAP command was issued with AMQ9937 The asyncResult is null.
an invalid value for an option. MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR.(2210).
Response: Reissue the SOAP command supplying the
correct option value. Severity: 30 : Severe error
Explanation: .The asyncResult is null.
AMQ9932 Application host class not found MQCC_FAILED(2)
Response: Check why the SOAP responses are not
Explanation: Application host class <insert_3> has not being received.
been found.
Response: Specify the correct application host class in
the SOAP message.
Chapter 7. 9000-9999 - Remote 249

AMQ9938 SOAP/WMQ Timeout. AMQ9943 Unrecognised RFH2 version.
MQCC_FAILED(2)
MQRC_RFH_FORMAT_ERROR(2421).
Explanation: .The MQGET operation timed out.
MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR.(2210). Explanation: .Unrecognised RFH2 version.
MQCC_FAILED(2)
Response: Check why the SOAP responses are not
being received. MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR.(2210). Response: Correct the version in the RFH2 message
and retry.
AMQ9939 SOAP/WMQ Error. MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR.(2210). AMQ9944 Invalid RFH2 length. MQCC_FAILED(2)
Explanation: .A SOAP error was detected.
MQCC_FAILED(2) Explanation: .Invalid RFH2 length. MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR.(2210). MQRC_RFH_FORMAT_ERROR(2421).
Response: Check the WMQ logs for the reason of the Response: Correct the RFH2 length and retry.
failure.
AMQ9945 Illegal RFH2 <insert_3> folder length.
AMQ9940 Report message returned in MQCC_FAILED(2)
MQWebResponse. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Explanation: .Illegal RFH2 <insert_3> folder length.
Explanation: .Report message returned in MQCC_FAILED(2)
MQWebResponse. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the RFH2 message and retry.
Response: Check the report message for the reason of
the failure.
AMQ9946 Invalid actual message length.
MQCC_FAILED(2)
AMQ9941 No RFH2 header recognised. MQRC_RFH_FORMAT_ERROR(2421).
MQCC_FAILED(2)
MQRCCF_MD_FORMAT_ERROR(3023).
Explanation: .Invalid actual message length.
MQCC_FAILED(2)
Explanation: .No RFH2 header recognised. MQRC_RFH_FORMAT_ERROR(2421).
MQCC_FAILED(2)
MQRCCF_MD_FORMAT_ERROR(3023).
Response: Check why the message is being sent with
AMQ9947 Illegal RFH2 Folder <insert_3>
no RFH2 header.
<insert_4>. MQCC_FAILED(2)
AMQ9942 Message format is not MQFMT_NONE.
MQCC_FAILED(2)
MQRC_RFH_FORMAT_ERROR(2421). Explanation: .Illegal RFH2 Folder <insert_3>
<insert_4>. MQCC_FAILED(2)
Explanation: .Message format is not MQFMT_NONE.
Response: Correct the RFH2 folder syntax/format and
MQCC_FAILED(2)
retry.
Response: Correct the message format and retry.

AMQ9948 Backout Threshold exceeded. AMQ9953 Either the ContentType or the
MQCC_FAILED(2) TransportVersion in the RFH2 header
MQRC_BACKOUT_THRESHOLD_REACHED(2362). have the wrong value.
MQCC_FAILED(2)
MQRC_RFH_HEADER_FIELD_ERROR(2228)
Explanation: .Backout Threshold exceeded.
MQCC_FAILED(2)
MQRC_BACKOUT_THRESHOLD_REACHED(2362). Explanation: .Either the ContentType or the
TransportVersion in the RFH2 header have the wrong
Response: Correct the backout threshold limit and
value. MQCC_FAILED(2)
retry.
MQRC_RFH_HEADER_FIELD_ERROR(2228)
Response: Correct the message format and retry.
AMQ9949 <insert_3> missing from RFH2.
MQCC_FAILED(2)
MQRC_RFH_PARM_MISSING(2339). AMQ9954 ViaTran.Redirect called out of
transaction MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR(2410)
Explanation: .<insert_3> missing from RFH2.
MQCC_FAILED(2)
MQRC_RFH_PARM_MISSING(2339). Explanation: .ViaTran.Redirect called out of
transaction MQCC_FAILED(2)
MQRC_SOAP_DOTNET_ERROR(2410)
Response: Make sure ViaTran.Redirect is only called
AMQ9950 Target service missing from SOAP URL.
in a transaction.
MQCC_FAILED(2)
AMQ9955 Usage: amqswsdl [?] Uri inputFile
outputFile
Explanation: .Target service missing from SOAP URL.
MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Response: None.
AMQ9951 Asynchronous request queued
successfully. MQCC_OK(0). AMQ9990 (iSeries) Keyword <insert_3> not valid for
this command or the command is
incomplete.
Explanation: .Asynchronous request queued
successfully. MQCC_OK(0).
Explanation: The command is incomplete, or an
Response: Wait for response if any is expected.
invalid keyword was specified, or the parameter value
of the keyword was not specified.
AMQ9952 Unexpected message type received.
Response: Complete the command, or correct the
MQCC_FAILED(2)
keyword, or add the parameter value, and then try the
MQRC_UNEXPECTED_MSG_TYPE.(2215).
command again.
Explanation: .A message of the wrong type was AMQ9991 (iSeries) The value specified is not
received; for instance, a report message was received allowed by the command.
when one had not been requested.
Response: If you are running WMQ SOAP using the
Explanation: <insert_3> not valid for parameter
IBM supplied SOAP/WMQ sender, please contact IBM.
<insert_4>.
If you are running WMQ SOAP using a bespoke
sender, please check that the SOAP/WMQ request Response: Enter one of the values that is defined for
message has the correct options. the parameter, and try the command again. More
information on parameters and commands can be
found in the CL reference manual or the appropriate
licensed program manual.
Chapter 7. 9000-9999 - Remote 251

AMQ9992 (iSeries) A matching parenthesis not
found.
Explanation: A matching left or right parenthesis is
missing.
Response: Add the missing parenthesis or remove the
extra parenthesis.
AMQ9999 Channel program ended abnormally.

Explanation: Channel program <insert_3> ended
abnormally.
Response: Look at previous error messages for
channel program <insert_3> in the error files to
determine the cause of the failure.

Chapter 8. API completion and reason codes
For each call, a completion code and a reason code are returned by the queue
manager or by an exit routine, to indicate the success or failure of the call.
For more information about the WebSphere MQ API, see the WebSphere MQ
Application Programming Guide and the WebSphere MQ Application Programming
Reference manual.
Completion codes
The following is a list of the completion codes (MQCC) returned by WebSphere
MQ
0: Successful completion (MQCC_OK)
The call completed fully; all output parameters have been set.
The Reason parameter always has the value MQRC_NONE in this case.
1: Warning (partial completion) (MQCC_WARNING)
The call completed partially. Some output parameters might have been set
in addition to the CompCode and Reason output parameters.
The Reason parameter gives additional information.
2: Call failed (MQCC_FAILED)
The processing of the call did not complete, and the state of the queue
manager is normally unchanged; exceptions are specifically noted. Only
the CompCode and Reason output parameters have been set; all other
parameters are unchanged.
The reason might be a fault in the application program, or it might be a
result of some situation external to the program, for example the
application’s authority might have been revoked. The Reason parameter
gives additional information.
Reason codes
The reason code parameter (Reason) is a qualification to the completion code
parameter (CompCode).
If there is no special reason to report, MQRC_NONE is returned. A successful call

returns MQCC_OK and MQRC_NONE.
If the completion code is either MQCC_WARNING or MQCC_FAILED, the queue

manager always reports a qualifying reason; details are given under each call
description.
Where user exit routines set completion codes and reasons, they should adhere to
these rules. In addition, any special reason values defined by user exits should be
less than zero, to ensure that they do not conflict with values defined by the queue
manager. Exits can set reasons already defined by the queue manager, where these
are appropriate.

Completion and reason codes
Reason codes also occur in:

v The Reason field of the MQDLH structure
v The Feedback field of the MQMD structure
Reason code list

The following is a list of reason codes, in numeric order, providing detailed
information to help you understand them, including:
v An explanation of the circumstances that have caused the code to be raised
v The associated completion code
v Suggested programmer actions in response to the code
See “Reason code cross reference” on page 321 for a list of reason codes in
alphabetic order.
Programmer Response: Correct the queue definitions.

0 (X'0000') MQRC_NONE
Explanation: The call completed normally. The
2002 (X'07D2') MQRC_ALREADY_CONNECTED
completion code (CompCode) is MQCC_OK.
Explanation: An MQCONN or MQCONNX call was
Completion Code: MQCC_OK
issued, but the application is already connected to the
Programmer Response: None. queue manager.
v On z/OS, this reason code occurs for batch and IMS
900 (X'0384') MQRC_APPL_FIRST applications only; it does not occur for CICS
applications.
Explanation: This is the lowest value for an
v On AIX, HP-UX, i5/OS, Solaris, Windows, this
application-defined reason code returned by a
reason code occurs if the application attempts to
data-conversion exit. Data-conversion exits can return
create a nonshared handle when a nonshared handle
reason codes in the range MQRC_APPL_FIRST through
already exists for the thread. A thread can have no
MQRC_APPL_LAST to indicate particular conditions
more than one nonshared handle.
that the exit has detected.
v On Windows, MTS objects do not receive this reason
Completion Code: MQCC_WARNING or code, as additional connections to the queue manager
MQCC_FAILED are allowed.
Programmer Response: As defined by the writer of Completion Code: MQCC_WARNING
the data-conversion exit.
Programmer Response: None. The Hconn parameter
returned has the same value as was returned for the
999 (X'03E7') MQRC_APPL_LAST previous MQCONN or MQCONNX call.
Explanation: This is the highest value for an An MQCONN or MQCONNX call that returns this
application-defined reason code returned by a reason code does not mean that an additional MQDISC
data-conversion exit. Data-conversion exits can return call must be issued in order to disconnect from the
reason codes in the range MQRC_APPL_FIRST through queue manager. If this reason code is returned because
MQRC_APPL_LAST to indicate particular conditions the application has been called in a situation where the
that the exit has detected. connect has already been done, a corresponding
Completion Code: MQCC_WARNING or MQDISC should not be issued, because this will cause
MQCC_FAILED the application that issued the original MQCONN or
MQCONNX call to be disconnected as well.
Programmer Response: As defined by the writer of
the data-conversion exit.
2003 (X'07D3') MQRC_BACKED_OUT
2001 (X'07D1') Explanation: The current unit of work encountered a

MQRC_ALIAS_BASE_Q_TYPE_ERROR fatal error or was backed out. This occurs in the
following cases:
Explanation: An MQOPEN or MQPUT1 call was v On an MQCMIT or MQDISC call, when the commit
issued specifying an alias queue as the destination, but operation has failed and the unit of work has been
the BaseQName in the alias queue definition resolves to a backed out. All resources that participated in the unit
queue that is not a local queue, a local definition of a of work have been returned to their state at the start
remote queue, or a cluster queue. of the unit of work. The MQCMIT or MQDISC call
Completion Code: MQCC_FAILED completes with MQCC_WARNING in this case.

– On z/OS, this reason code occurs only for batch

2006 (X'07D6')
applications.
MQRC_CHAR_ATTR_LENGTH_ERROR
v On an MQGET, MQPUT, or MQPUT1 call that is
operating within a unit of work, when the unit of Explanation: CharAttrLength is negative (for MQINQ
work has already encountered an error that prevents or MQSET calls), or is not large enough to hold all
the unit of work being committed (for example, selected attributes (MQSET calls only). This reason also
when the log space is exhausted). The application occurs if the parameter pointer is not valid. (It is not
must issue the appropriate call to back out the unit always possible to detect parameter pointers that are
of work. (For a unit of work coordinated by the not valid; if not detected, unpredictable results occur.)
queue manager, this call is the MQBACK call, Completion Code: MQCC_FAILED
although the MQCMIT call has the same effect in
these circumstances.) The MQGET, MQPUT, or Programmer Response: Specify a value large enough
MQPUT1 call completes with MQCC_FAILED in this to hold the concatenated strings for all selected
case. attributes.
– On z/OS, this case does not occur.
2007 (X'07D7') MQRC_CHAR_ATTRS_ERROR
Completion Code: MQCC_WARNING or
MQCC_FAILED Explanation: CharAttrs is not valid. The parameter
pointer is not valid, or points to read-only storage for
Programmer Response: Check the returns from
MQINQ calls or to storage that is not as long as
previous calls to the queue manager. For example, a
implied by CharAttrLength. (It is not always possible to
previous MQPUT call may have failed.
detect parameter pointers that are not valid; if not
detected, unpredictable results occur.)
2004 (X'07D4') MQRC_BUFFER_ERROR
Completion Code: MQCC_FAILED
Explanation: The Buffer parameter is not valid for
Programmer Response: Correct the parameter.
one of the following reasons:
v The parameter pointer is not valid. (It is not always
possible to detect parameter pointers that are not 2008 (X'07D8') MQRC_CHAR_ATTRS_TOO_SHORT
valid; if not detected, unpredictable results occur.)
v The parameter pointer points to storage that cannot Explanation: For MQINQ calls, CharAttrLength is not
be accessed for the entire length specified by large enough to contain all of the character attributes
BufferLength. for which MQCA_* selectors are specified in the
v For calls where Buffer is an output parameter: the Selectors parameter.
parameter pointer points to read-only storage. The call still completes, with the CharAttrs parameter
Completion Code: MQCC_FAILED string filled in with as many character attributes as
there is room for. Only complete attribute strings are
Programmer Response: Correct the parameter. returned: if there is insufficient space remaining to
accommodate an attribute in its entirety, that attribute
and subsequent character attributes are omitted. Any
2005 (X'07D5') MQRC_BUFFER_LENGTH_ERROR
space at the end of the string not used to hold an
Explanation: The BufferLength parameter is not valid, attribute is unchanged.
or the parameter pointer is not valid. (It is not always
An attribute that represents a set of values (for
possible to detect parameter pointers that are not valid;
example, the namelist Names attribute) is treated as a
if not detected, unpredictable results occur.)
single entity—either all of its values are returned, or
This reason can also be returned to an MQ client none.
program on the MQCONN or MQCONNX call if the
Completion Code: MQCC_WARNING
negotiated maximum message size for the channel is
smaller than the fixed part of any call structure. Programmer Response: Specify a large enough value,
unless only a subset of the values is needed.
This reason should also be returned by the
MQZ_ENUMERATE_AUTHORITY_DATA installable
service component when the AuthorityBuffer 2009 (X'07D9') MQRC_CONNECTION_BROKEN
parameter is too small to accommodate the data to be
returned to the invoker of the service component. Explanation: Connection to the queue manager has
been lost. This can occur because the queue manager
Completion Code: MQCC_FAILED has ended. If the call is an MQGET call with the
MQGMO_WAIT option, the wait has been canceled. All
Programmer Response: Specify a value that is zero or
connection and object handles are now invalid.
greater. For the mqAddString and mqSetString calls,
the special value MQBL_NULL_TERMINATED is also For MQ client applications, it is possible that the call
valid. did complete successfully, even though this reason code
Chapter 8. API completion and reason codes 255

is returned with a CompCode of MQCC_FAILED. Completion Code: MQCC_FAILED

Completion Code: MQCC_FAILED Programmer Response: Specify a valid name.
Programmer Response: Applications can attempt to
reconnect to the queue manager by issuing the 2012 (X'07DC') MQRC_ENVIRONMENT_ERROR
MQCONN or MQCONNX call. It may be necessary to
Explanation: The call is not valid for the current
poll until a successful response is received.
environment.
v On z/OS for CICS applications, it is not necessary to
v On z/OS, one of the following applies:
issue the MQCONN or MQCONNX call, because
– An MQCONN or MQCONNX call was issued, but
CICS applications are connected automatically.
the application has been linked with an adapter
that is not supported in the environment in which
Any uncommitted changes in a unit of work should be
the application is running. For example, this can
backed out. A unit of work that is coordinated by the
arise when the application is linked with the MQ
queue manager is backed out automatically.
RRS adapter, but the application is running in a
DB2 Stored Procedure address space. RRS is not
2010 (X'07DA') MQRC_DATA_LENGTH_ERROR supported in this environment. Stored Procedures
wishing to use the MQ RRS adapter must run in a
Explanation: The DataLength parameter is not valid. DB2 WLM-managed Stored Procedure address
Either the parameter pointer is not valid, or it points to space.
read-only storage. (It is not always possible to detect – An MQCMIT or MQBACK call was issued, but
parameter pointers that are not valid; if not detected, the application has been linked with the RRS
unpredictable results occur.) batch adapter CSQBRSTB. This adapter does not
This reason can also be returned to an MQ client support the MQCMIT and MQBACK calls.
program on the MQGET, MQPUT, or MQPUT1 call, if – An MQCMIT or MQBACK call was issued in the
the BufferLength parameter exceeds the maximum CICS or IMS environment.
message size that was negotiated for the client channel. – The RRS subsystem is not up and running on the
z/OS system that ran the application.
v On HP OpenVMS, OS/2, i5/OS, HP NonStop Server,
Programmer Response: Correct the parameter. UNIX systems, and Windows, one of the following
applies:
If the error occurs for an MQ client program, also check
– The application is linked to the wrong libraries
that the maximum message size for the channel is big
(threaded or nonthreaded).
enough to accommodate the message being sent; if it is
– An MQBEGIN, MQCMIT, or MQBACK call was
not big enough, increase the maximum message size
issued, but an external unit-of-work manager is in
for the channel.
use. For example, this reason code occurs on
Windows when an MTS object is running as a
2011 (X'07DB') DTC transaction. This reason code also occurs if
MQRC_DYNAMIC_Q_NAME_ERROR the queue manager does not support units of
work.
Explanation: On the MQOPEN call, a model queue is – The MQBEGIN call was issued in an MQ client
specified in the ObjectName field of the ObjDesc environment.
parameter, but the DynamicQName field is not valid, for – An MQXCLWLN call was issued, but the call did
one of the following reasons: not originate from a cluster workload exit.
v DynamicQName is completely blank (or blank up to the
first null character in the field). Completion Code: MQCC_FAILED
v Characters are present that are not valid for a queue
Programmer Response: Do one of the following (as
name.
appropriate):
v An asterisk is present beyond the 33rd position (and
before any null character). v On z/OS:
v An asterisk is present followed by characters that are – Link the application with the correct adapter.
not null and not blank. – Modify the application to use the SRRCMIT and
SRRBACK calls in place of the MQCMIT and
This reason code can also sometimes occur when a MQBACK calls. Alternatively, link the application
server application opens the reply queue specified by with the RRS batch adapter CSQBRRSI. This
the ReplyToQ and ReplyToQMgr fields in the MQMD of a adapter supports MQCMIT and MQBACK in
message that the server has just received. In this case addition to SRRCMIT and SRRBACK.
the reason code indicates that the application that sent – For a CICS or IMS application, issue the
the original message placed incorrect values into the appropriate CICS or IMS call to commit or
ReplyToQ and ReplyToQMgr fields in the MQMD of the backout the unit of work.
original message. – Start the RRS subsystem on the z/OS system that
is running the application.

v In the other environments: distribution list containing a large number of queues

– Link the application with the correct libraries that are consuming all of the available handles. If it is,
(threaded or nonthreaded). increase the maximum number of handles that the task
– Remove from the application the call that is not can use, or reduce the size of the distribution list. The
supported. maximum number of open handles that a task can use
is given by the MaxHandles queue manager attribute.
2013 (X'07DD') MQRC_EXPIRY_ERROR
2018 (X'07E2') MQRC_HCONN_ERROR
Explanation: On an MQPUT or MQPUT1 call, the
value specified for the Expiry field in the message Explanation: The connection handle Hconn is not valid,
descriptor MQMD is not valid. for one of the following reasons:
Completion Code: MQCC_FAILED v The parameter pointer is not valid, or (for the
MQCONN or MQCONNX call) points to read-only
Programmer Response: Specify a value that is greater storage. (It is not always possible to detect parameter
than zero, or the special value MQEI_UNLIMITED. pointers that are not valid; if not detected,
unpredictable results occur.)
2014 (X'07DE') MQRC_FEEDBACK_ERROR v The value specified was not returned by a preceding
MQCONN or MQCONNX call.
value specified for the Feedback field in the message v The value specified has been made invalid by a
descriptor MQMD is not valid. The value is not preceding MQDISC call.
MQFB_NONE, and is outside both the range defined v The handle is a shared handle that has been made
for system feedback codes and the range defined for invalid by another thread issuing the MQDISC call.
application feedback codes. v The handle is a shared handle that is being used on
Completion Code: MQCC_FAILED the MQBEGIN call (only nonshared handles are valid
on MQBEGIN).
Programmer Response: Specify MQFB_NONE, or a v The handle is a nonshared handle that is being used
value in the range MQFB_SYSTEM_FIRST through a thread that did not create the handle.
MQFB_SYSTEM_LAST, or MQFB_APPL_FIRST through
MQFB_APPL_LAST. v The call was issued in the MTS environment in a
situation where the handle is not valid (for example,
passing the handle between processes or packages;
2016 (X'07E0') MQRC_GET_INHIBITED note that passing the handle between library
packages is supported).
Explanation: MQGET calls are currently inhibited for
the queue, or for the queue to which this queue Completion Code: MQCC_FAILED
resolves.
Programmer Response: Ensure that a successful
Completion Code: MQCC_FAILED MQCONN or MQCONNX call is performed for the
queue manager, and that an MQDISC call has not
Programmer Response: If the system design allows
already been performed for it. Ensure that the handle is
get requests to be inhibited for short periods, retry the
being used within its valid scope (see the description of
operation later.
MQCONN in the WebSphere MQ Application
Programming Guide).
2017 (X'07E1') MQRC_HANDLE_NOT_AVAILABLE v On z/OS, also check that the application has been
Explanation: An MQOPEN or MQPUT1 call was linked with the correct stub; this is CSQCSTUB for
issued, but the maximum number of open handles CICS applications, CSQBSTUB for batch applications,
allowed for the current task has already been reached. and CSQQSTUB for IMS applications. Also, the stub
Be aware that when a distribution list is specified on used must not belong to a release of the queue
the MQOPEN or MQPUT1 call, each queue in the manager that is more recent than the release on
distribution list uses one handle. which the application will run.
v On z/OS, “task” means a CICS task, a z/OS task, or
an IMS-dependent region. 2019 (X'07E3') MQRC_HOBJ_ERROR
Completion Code: MQCC_FAILED Explanation: The object handle Hobj is not valid, for
one of the following reasons:
Programmer Response: Check whether the application
is issuing MQOPEN calls without corresponding v The parameter pointer is not valid, or (for the
MQCLOSE calls. If it is, modify the application to issue MQOPEN call) points to read-only storage. (It is not
the MQCLOSE call for each open object as soon as that always possible to detect parameter pointers that are
object is no longer needed. not valid; if not detected, unpredictable results
occur.)
Also check whether the application is specifying a

v The value specified was not returned by a preceding

2023 (X'07E7') MQRC_INT_ATTRS_ARRAY_ERROR
MQOPEN call.
v The value specified has been made invalid by a Explanation: On an MQINQ or MQSET call, the
preceding MQCLOSE call. IntAttrs parameter is not valid. The parameter pointer
is not valid (MQINQ and MQSET), or points to
v The handle is a shared handle that has been made
read-only storage or to storage that is not as long as
invalid by another thread issuing the MQCLOSE call.
indicated by the IntAttrCount parameter (MQINQ
v The handle is a nonshared handle that is being used only). (It is not always possible to detect parameter
by a thread that did not create the handle. pointers that are not valid; if not detected,
v The call is MQGET or MQPUT, but the object unpredictable results occur.)
represented by the handle is not a queue.
Programmer Response: Ensure that a successful
MQOPEN call is performed for this object, and that an
2024 (X'07E8')
MQCLOSE call has not already been performed for it.
MQRC_SYNCPOINT_LIMIT_REACHED
Ensure that the handle is being used within its valid
scope (see the description of MQOPEN in the Explanation: An MQGET, MQPUT, or MQPUT1 call
WebSphere MQ Application Programming Guide). failed because it would have caused the number of
uncommitted messages in the current unit of work to
exceed the limit defined for the queue manager (see the
2020 (X'07E4') MQRC_INHIBIT_VALUE_ERROR
MaxUncommittedMsgs queue-manager attribute). The
Explanation: On an MQSET call, the value specified number of uncommitted messages is the sum of the
for either the MQIA_INHIBIT_GET attribute or the following since the start of the current unit of work:
MQIA_INHIBIT_PUT attribute is not valid. v Messages put by the application with the
MQPMO_SYNCPOINT option
Completion Code: MQCC_FAILED v Messages retrieved by the application with the
Programmer Response: Specify a valid value for the MQGMO_SYNCPOINT option
InhibitGet or InhibitPut queu attribute. v Trigger messages and COA report messages
generated by the queue manager for messages put
with the MQPMO_SYNCPOINT option
2021 (X'07E5') MQRC_INT_ATTR_COUNT_ERROR v COD report messages generated by the queue
Explanation: On an MQINQ or MQSET call, the manager for messages retrieved with the
IntAttrCount parameter is negative (MQINQ or MQGMO_SYNCPOINT option
MQSET), or smaller than the number of integer v On HP NonStop Server, this reason code occurs
attribute selectors (MQIA_*) specified in the Selectors when the maximum number of I/O operations in a
parameter (MQSET only). This reason also occurs if the single TM/MP transaction has been exceeded.
parameter pointer is not valid. (It is not always possible Completion Code: MQCC_FAILED
to detect parameter pointers that are not valid; if not
detected, unpredictable results occur.) Programmer Response: Check whether the application
is looping. If it is not, consider reducing the complexity
Completion Code: MQCC_FAILED of the application. Alternatively, increase the
Programmer Response: Specify a value large enough queue-manager limit for the maximum number of
for all selected integer attributes. uncommitted messages within a unit of work.
v On z/OS, the limit for the maximum number of
uncommitted messages can be changed by using the
2022 (X'07E6') ALTER QMGR command.
MQRC_INT_ATTR_COUNT_TOO_SMALL v On i5/OS, the limit for the maximum number of
Explanation: On an MQINQ call, the IntAttrCount uncommitted messages can be changed by using the
parameter is smaller than the number of integer CHGMQM command.
attribute selectors (MQIA_*) specified in the Selectors v On HP NonStop Server, the application should cancel
parameter. the transaction and retry with a smaller number of
operations in the unit of work. See the MQSeries for
The call completes with MQCC_WARNING, with the Tandem NonStop Kernel System Management Guide for
IntAttrs array filled in with as many integer attributes more details.
as there is room for.
Programmer Response: Specify a large enough value,
unless only a subset of the values is needed.

to which the reply message or report message is to be

2025 (X'07E9')
sent.
MQRC_MAX_CONNS_LIMIT_REACHED
1 Explanation: The MQCONN or MQCONNX call was
1 2029 (X'07ED') MQRC_MSG_TYPE_ERROR
1 rejected because the maximum number of concurrent
1 connections has been exceeded. 1 Explanation: Either:
1 v On z/OS, connection limits are applicable only to 1 v On an MQPUT or MQPUT1 call, the value specified
1 TSO and batch requests. The limits are determined 1 for the MsgType field in the message descriptor
1 by the customer using the following parameters of 1 (MQMD) is not valid.
1 the CSQ6SYSP macro: 1 v A message processing program received a message
1 – For TSO: IDFORE 1 that does not have the expected message type. For
1 – For batch: IDBACK 1 example, if the WebSphere MQ command server
1 receives a message which is not a request message
1 For more information, see the WebSphere MQ for z/OS 1 (MQMT_REQUEST) then it rejects the request with
1 System Setup Guide. 1 this reason code.
1 v On HP OpenVMS, OS/2, i5/OS, HP NonStop Server,
1 Completion Code: MQCC_FAILED
1 UNIX systems, and Windows, this reason code can
1 also occur on the MQOPEN call. 1 Programmer Response: Specify a valid value for the
1 v When using Java applications, a limit to the number 1 MsgType field. In the case where a request is rejected by
1 of concurrent connections may be defined by the 1 a message processing program, refer to the
1 connection manager. 1 documentation for that program for details of the
1 message types that it supports.
Programmer Response: Either increase the size of the 2030 (X'07EE') MQRC_MSG_TOO_BIG_FOR_Q
appropriate parameter value, or reduce the number of
concurrent connections. Explanation: An MQPUT or MQPUT1 call was issued
to put a message on a queue, but the message was too
long for the queue and
2026 (X'07EA') MQRC_MD_ERROR MQMF_SEGMENTATION_ALLOWED was not
Explanation: The MQMD structure is not valid, for specified in the MsgFlags field in MQMD. If
one of the following reasons: segmentation is not allowed, the length of the message
v The StrucId field is not MQMD_STRUC_ID. cannot exceed the lesser of the queue MaxMsgLength
v The Version field specifies a value that is not valid attribute and queue-manager MaxMsgLength attribute.
or not supported. v On z/OS, the queue manager does not support the
v The parameter pointer is not valid. (It is not always segmentation of messages; if
possible to detect parameter pointers that are not MQMF_SEGMENTATION_ALLOWED is specified, it
valid; if not detected, unpredictable results occur.) is accepted but ignored.
v The queue manager cannot copy the changed
structure to application storage, even though the call This reason code can also occur when
is successful. This can occur, for example, if the MQMF_SEGMENTATION_ALLOWED is specified, but
pointer points to read-only storage. the nature of the data present in the message prevents
the queue manager splitting it into segments that are
small enough to place on the queue:
Programmer Response: Ensure that input fields in the v For a user-defined format, the smallest segment that
MQMD structure are set correctly. the queue manager can create is 16 bytes.
v For a built-in format, the smallest segment that the
queue manager can create depends on the particular
2027 (X'07EB') MQRC_MISSING_REPLY_TO_Q
format, but is greater than 16 bytes in all cases other
Explanation: On an MQPUT or MQPUT1 call, the than MQFMT_STRING (for MQFMT_STRING the
ReplyToQ field in the message descriptor MQMD is minimum segment size is 16 bytes).
blank, but one or both of the following is true:
v A reply was requested (that is, MQMT_REQUEST MQRC_MSG_TOO_BIG_FOR_Q can also occur in the
was specified in the MsgType field of the message Feedback field in the message descriptor of a report
descriptor). message; in this case it indicates that the error was
v A report message was requested in the Report field encountered by a message channel agent when it
of the message descriptor. attempted to put the message on a remote queue.
Completion Code: MQCC_FAILED Completion Code: MQCC_FAILED
Programmer Response: Specify the name of the queue Programmer Response: Check whether the

BufferLength parameter is specified correctly; if it is, v Specify MQMF_SEGMENTATION_ALLOWED in the

do one of the following: MsgFlags field in MQMD; this will allow the queue
v Increase the value of the queue’s MaxMsgLength manager to break the message into segments.
attribute; the queue-manager’s MaxMsgLength v Check the channel definitions.
attribute may also need increasing.
v Break the message into several smaller messages.
2033 (X'07F1') MQRC_NO_MSG_AVAILABLE
v Specify MQMF_SEGMENTATION_ALLOWED in the
MsgFlags field in MQMD; this will allow the queue Explanation: An MQGET call was issued, but there is
manager to break the message into segments. no message on the queue satisfying the selection
criteria specified in MQMD (the MsgId and CorrelId
fields), and in MQGMO (the Options and MatchOptions
2031 (X'07EF')
fields). Either the MQGMO_WAIT option was not
MQRC_MSG_TOO_BIG_FOR_Q_MGR
specified, or the time interval specified by the
Explanation: An MQPUT or MQPUT1 call was issued WaitInterval field in MQGMO has expired. This
to put a message on a queue, but the message was too reason is also returned for an MQGET call for browse,
long for the queue manager and when the end of the queue has been reached.
MQMF_SEGMENTATION_ALLOWED was not
This reason code can also be returned by the mqGetBag
specified in the MsgFlags field in MQMD. If
and mqExecute calls. mqGetBag is similar to MQGET.
segmentation is not allowed, the length of the message
For the mqExecute call, the completion code can be
cannot exceed the lesser of the queue-manager
either MQCC_WARNING or MQCC_FAILED:
MaxMsgLength attribute and queue MaxMsgLength
v If the completion code is MQCC_WARNING, some
attribute.
response messages were received during the
This reason code can also occur when specified wait interval, but not all. The response bag
MQMF_SEGMENTATION_ALLOWED is specified, but contains system-generated nested bags for the
the nature of the data present in the message prevents messages that were received.
the queue manager splitting it into segments that are v If the completion code is MQCC_FAILED, no
small enough for the queue-manager limit: response messages were received during the
v For a user-defined format, the smallest segment that specified wait interval.
the queue manager can create is 16 bytes.
v For a built-in format, the smallest segment that the
MQCC_FAILED
queue manager can create depends on the particular
format, but is greater than 16 bytes in all cases other Programmer Response: If this is an expected
than MQFMT_STRING (for MQFMT_STRING the condition, no corrective action is required.
minimum segment size is 16 bytes).
If this is an unexpected condition, check that:
MQRC_MSG_TOO_BIG_FOR_Q_MGR can also occur in v The message was put on the queue successfully.
the Feedback field in the message descriptor of a report v The unit of work (if any) used for the MQPUT or
message; in this case it indicates that the error was MQPUT1 call was committed successfully.
encountered by a message channel agent when it v The options controlling the selection criteria are
attempted to put the message on a remote queue. specified correctly. All of the following can affect the
eligibility of a message for return on the MQGET
This reason also occurs if a channel, through which the call:
message is to pass, has restricted the maximum MQGMO_LOGICAL_ORDER
message length to a value that is actually less than that MQGMO_ALL_MSGS_AVAILABLE
supported by the queue manager, and the message MQGMO_ALL_SEGMENTS_AVAILABLE
length is greater than this value. MQGMO_COMPLETE_MSG
v On z/OS, this return code is issued only if you are MQMO_MATCH_MSG_ID
using CICS for distributed queuing. Otherwise, MQMO_MATCH_CORREL_ID
MQRC_MSG_TOO_BIG_FOR_CHANNEL is issued. MQMO_MATCH_GROUP_ID
MQMO_MATCH_MSG_SEQ_NUMBER
MQMO_MATCH_OFFSET
Programmer Response: Check whether the Value of MsgId field in MQMD
BufferLength parameter is specified correctly; if it is, Value of CorrelId field in MQMD
do one of the following:
Consider waiting longer for the message.
v Increase the value of the queue-manager’s
MaxMsgLength attribute; the queue’s MaxMsgLength
attribute may also need increasing.
v Break the message into several smaller messages.

manager or object was specified, and that appropriate

2034 (X'07F2') MQRC_NO_MSG_UNDER_CURSOR
authority exists.
Explanation: An MQGET call was issued with either
the MQGMO_MSG_UNDER_CURSOR or the
2036 (X'07F4') MQRC_NOT_OPEN_FOR_BROWSE
MQGMO_BROWSE_MSG_UNDER_CURSOR option.
However, the browse cursor is not positioned at a Explanation: An MQGET call was issued with one of
retrievable message. This is caused by one of the the following options:
following: MQGMO_BROWSE_FIRST
v The cursor is positioned logically before the first MQGMO_BROWSE_NEXT
message (as it is before the first MQGET call with a MQGMO_BROWSE_MSG_UNDER_CURSOR
browse option has been successfully performed). MQGMO_MSG_UNDER_CURSOR
v The message the browse cursor was positioned on
has been locked or removed from the queue but the queue had not been opened for browse.
(probably by some other application) since the Completion Code: MQCC_FAILED
browse operation was performed.
v The message the browse cursor was positioned on Programmer Response: Specify MQOO_BROWSE
has expired. when the queue is opened.

2037 (X'07F5') MQRC_NOT_OPEN_FOR_INPUT
Programmer Response: Check the application logic.
This may be an expected reason if the application Explanation: An MQGET call was issued to retrieve a
design allows multiple servers to compete for messages message from a queue, but the queue had not been
after browsing. Consider also using the opened for input.
MQGMO_LOCK option with the preceding browse Completion Code: MQCC_FAILED
MQGET call.
Programmer Response: Specify one of the following
when the queue is opened:
2035 (X'07F3') MQRC_NOT_AUTHORIZED MQOO_INPUT_SHARED
Explanation: The user is not authorized to perform MQOO_INPUT_EXCLUSIVE
the operation attempted: MQOO_INPUT_AS_Q_DEF
v On an MQCONN or MQCONNX call, the user is not
authorized to connect to the queue manager. 2038 (X'07F6') MQRC_NOT_OPEN_FOR_INQUIRE
– On z/OS, for CICS applications, Explanation: An MQINQ call was issued to inquire
MQRC_CONNECTION_NOT_AUTHORIZED is object attributes, but the object had not been opened for
issued instead. inquire.
v On an MQOPEN or MQPUT1 call, the user is not
authorized to open the object for the option(s)
specified. Programmer Response: Specify MQOO_INQUIRE
– On z/OS, if the object being opened is a model when the object is opened.
queue, this reason also arises if the user is not
authorized to create a dynamic queue with the 2039 (X'07F7') MQRC_NOT_OPEN_FOR_OUTPUT
required name.
v On an MQCLOSE call, the user is not authorized to Explanation: An MQPUT call was issued to put a
delete the object, which is a permanent dynamic message on a queue, but the queue had not been
queue, and the Hobj parameter specified on the opened for output.
MQCLOSE call is not the handle returned by the Completion Code: MQCC_FAILED
MQOPEN call that created the queue.
Programmer Response: Specify MQOO_OUTPUT
v On a command, the user is not authorized to issue
when the queue is opened.
the command, or to access the object it specifies.
This reason code can also occur in the Feedback field in 2040 (X'07F8') MQRC_NOT_OPEN_FOR_SET
the message descriptor of a report message; in this case
Explanation: An MQSET call was issued to set queue
it indicates that the error was encountered by a
attributes, but the queue had not been opened for set.
message channel agent when it attempted to put the
message on a remote queue. Completion Code: MQCC_FAILED
Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET when the
object is opened.
Programmer Response: Ensure that the correct queue

2041 (X'07F9') MQRC_OBJECT_CHANGED 2044 (X'07FC') MQRC_OD_ERROR

Explanation: Object definitions that affect this object Explanation: On the MQOPEN or MQPUT1 call, the
have been changed since the Hobj handle used on this object descriptor MQOD is not valid, for one of the
call was returned by the MQOPEN call. See the following reasons:
description of MQOPEN in the WebSphere MQ v The StrucId field is not MQOD_STRUC_ID.
Application Programming Guide for more information. v The Version field specifies a value that is not valid
or not supported.
This reason does not occur if the object handle is
specified in the Context field of the PutMsgOpts
possible to detect parameter pointers that are not
parameter on the MQPUT or MQPUT1 call.
Completion Code: MQCC_FAILED v The queue manager cannot copy the changed
structure to application storage, even though the call
Programmer Response: Issue an MQCLOSE call to is successful. This can occur, for example, if the
return the handle to the system. It is then usually pointer points to read-only storage.
sufficient to reopen the object and retry the operation.
However, if the object definitions are critical to the Completion Code: MQCC_FAILED
application logic, an MQINQ call can be used after
Programmer Response: Ensure that input fields in the
reopening the object, to obtain the new values of the
MQOD structure are set correctly.
object attributes.
2045 (X'07FD')
2042 (X'07FA') MQRC_OBJECT_IN_USE
MQRC_OPTION_NOT_VALID_FOR_TYPE
Explanation: An MQOPEN call was issued, but the
Explanation: On an MQOPEN or MQCLOSE call, an
object in question has already been opened by this or
option is specified that is not valid for the type of
another application with options that conflict with
object or queue being opened or closed.
those specified in the Options parameter. This arises if
the request is for shared input, but the object is already For the MQOPEN call, this includes the following
open for exclusive input; it also arises if the request is cases:
for exclusive input, but the object is already open for v An option that is inappropriate for the object type
input (of any sort). (for example, MQOO_OUTPUT for an
MCAs for receiver channels, or the intra-group queuing MQOT_PROCESS object).
agent (IGQ agent), may keep the destination queues v An option that is unsupported for the queue type
open even when messages are not being transmitted; (for example, MQOO_INQUIRE for a remote queue
this results in the queues appearing to be “in use”. Use that has no local definition).
the MQSC command DISPLAY QSTATUS to find out v One or more of the following options:
who is keeping the queue open. MQOO_INPUT_AS_Q_DEF
v On z/OS, this reason can also occur for an MQOPEN MQOO_INPUT_SHARED
or MQPUT1 call, if the object to be opened (which MQOO_INPUT_EXCLUSIVE
can be a queue, or for MQOPEN a namelist or MQOO_BROWSE
process object) is in the process of being deleted. MQOO_INQUIRE
MQOO_SET
when either:
Programmer Response: System design should specify
whether an application is to wait and retry, or take – the queue name is resolved through a cell
other action. directory, or
– ObjectQMgrName in the object descriptor specifies
the name of a local definition of a remote queue
2043 (X'07FB') MQRC_OBJECT_TYPE_ERROR
(in order to specify a queue-manager alias), and
Explanation: On the MQOPEN or MQPUT1 call, the the queue named in the RemoteQMgrName attribute
ObjectType field in the object descriptor MQOD of the definition is the name of the local queue
specifies a value that is not valid. For the MQPUT1 call, manager.
the object type must be MQOT_Q.
For the MQCLOSE call, this includes the following
case:
Programmer Response: Specify a valid object type. v The MQCO_DELETE or MQCO_DELETE_PURGE
option when the queue is not a dynamic queue.
This reason code can also occur on the MQOPEN call

when the object being opened is of type

MQOT_NAMELIST, MQOT_PROCESS, or placed on temporary dynamic queues.

MQOT_Q_MGR, but the ObjectQMgrName field in
This reason code can also occur in the Feedback field in
MQOD is neither blank nor the name of the local
queue manager.
Completion Code: MQCC_FAILED message channel agent when it attempted to put the
message on a remote queue.
Programmer Response: Specify the correct option. For
the MQOPEN call, ensure that the ObjectQMgrName field Completion Code: MQCC_FAILED
is set correctly. For the MQCLOSE call, either correct
Programmer Response: Specify
the option or change the definition type of the model
MQPER_NOT_PERSISTENT if the message is to be
queue that is used to create the new queue.
placed on a temporary dynamic queue. If persistence is
required, use a permanent dynamic queue or
2046 (X'07FE') MQRC_OPTIONS_ERROR predefined queue in place of a temporary dynamic
queue.
Explanation: The Options parameter or field contains
options that are not valid, or a combination of options Be aware that server applications are recommended to
that is not valid. send reply messages (message type MQMT_REPLY)
v For the MQOPEN, MQCLOSE, MQXCNVC, with the same persistence as the original request
mqBagToBuffer, mqBufferToBag, mqCreateBag, and message (message type MQMT_REQUEST). If the
mqExecute calls, Options is a separate parameter on request message is persistent, the reply queue specified
the call. in the ReplyToQ field in the message descriptor MQMD
cannot be a temporary dynamic queue. Use a
This reason also occurs if the parameter pointer is
permanent dynamic queue or predefined queue as the
not valid. (It is not always possible to detect
reply queue in this situation.
parameter pointers that are not valid; if not detected,
v For the MQBEGIN, MQCONNX, MQGET, MQPUT, 2049 (X'0801')
and MQPUT1 calls, Options is a field in the relevant MQRC_PRIORITY_EXCEEDS_MAXIMUM
options structure (MQBO, MQCNO, MQGMO, or Explanation: An MQPUT or MQPUT1 call was issued,
MQPMO). but the value of the Priority field in the message
Completion Code: MQCC_FAILED descriptor MQMD exceeds the maximum priority
supported by the local queue manager, as shown by the
Programmer Response: Specify valid options. Check MaxPriority queue-manager attribute. The message is
the description of the Options parameter or field to accepted by the queue manager, but is placed on the
determine which options and combinations of options queue at the queue manager’s maximum priority. The
are valid. If multiple options are being set by adding Priority field in the message descriptor retains the
the individual options together, ensure that the same value specified by the application that put the message.
option is not added twice.
2047 (X'07FF') MQRC_PERSISTENCE_ERROR Programmer Response: None required, unless this

reason code was not expected by the application that
Explanation: On an MQPUT or MQPUT1 call, the put the message.
value specified for the Persistence field in the message
descriptor MQMD is not valid.
2050 (X'0802') MQRC_PRIORITY_ERROR
Explanation: An MQPUT or MQPUT1 call was issued,
Programmer Response: Specify one of the following but the value of the Priority field in the message
values: descriptor MQMD is not valid. The maximum priority
MQPER_PERSISTENT supported by the queue manager is given by the
MQPER_NOT_PERSISTENT MaxPriority queue-manager attribute.
MQPER_PERSISTENCE_AS_Q_DEF
2048 (X'0800') Programmer Response: Specify a value in the range

MQRC_PERSISTENT_NOT_ALLOWED zero through MaxPriority, or the special value
MQPRI_PRIORITY_AS_Q_DEF.
value specified for the Persistence field in MQMD (or
obtained from the DefPersistence queue attribute)
specifies MQPER_PERSISTENT, but the queue on
which the message is being placed does not support
persistent messages. Persistent messages cannot be

2051 (X'0803') MQRC_PUT_INHIBITED 2055 (X'0807') MQRC_Q_NOT_EMPTY

Explanation: MQPUT and MQPUT1 calls are currently Explanation: An MQCLOSE call was issued for a
inhibited for the queue, or for the queue to which this permanent dynamic queue, but the call failed because
queue resolves. the queue is not empty or still in use. One of the
following applies:
v The MQCO_DELETE option was specified, but there
are messages on the queue.
v The MQCO_DELETE or MQCO_DELETE_PURGE
message channel agent when it attempted to put the
option was specified, but there are uncommitted get
or put calls outstanding against the queue.
See the usage notes pertaining to dynamic queues for
Programmer Response: If the system design allows the MQCLOSE call for more information.
put requests to be inhibited for short periods, retry the
operation later. This reason code is also returned from a command to
clear or delete or move a queue, if the queue contains
uncommitted messages (or committed messages in the
2052 (X'0804') MQRC_Q_DELETED
case of delete queue without the purge option).
Explanation: An Hobj queue handle specified on a call
refers to a dynamic queue that has been deleted since
the queue was opened. (See the description of Programmer Response: Check why there might be
MQCLOSE in the WebSphere MQ Application messages on the queue. Be aware that the
Programming Guide for information about the deletion CurrentQDepth queue attribute might be zero even
of dynamic queues.) though there are one or more messages on the queue;
v On z/OS, this can also occur with the MQOPEN and this can happen if the messages have been retrieved as
MQPUT1 calls if a dynamic queue is being opened, part of a unit of work that has not yet been committed.
but the queue is in a logically-deleted state. See If the messages can be discarded, try using the
MQCLOSE for more information about this. MQCLOSE call with the MQCO_DELETE_PURGE
option. Consider retrying the call later.
Programmer Response: Issue an MQCLOSE call to 2056 (X'0808') MQRC_Q_SPACE_NOT_AVAILABLE
return the handle and associated resources to the
system (the MQCLOSE call will succeed in this case). Explanation: An MQPUT or MQPUT1 call was issued,
Check the design of the application that caused the but there is no space available for the queue on disk or
error. other storage device.
2053 (X'0805') MQRC_Q_FULL the message descriptor of a report message; in this case
Explanation: An MQPUT or MQPUT1 call, or a message channel agent when it attempted to put the
command, failed because the queue is full, that is, it message on a remote queue.
already contains the maximum number of messages
v On z/OS, this reason code does not occur.
possible, as specified by the MaxQDepth queue attribute.
the message descriptor of a report message; in this case Programmer Response: Check whether an application
it indicates that the error was encountered by a is putting messages in an infinite loop. If not, make
message channel agent when it attempted to put the more disk space available for the queue.
Completion Code: MQCC_FAILED 2057 (X'0809') MQRC_Q_TYPE_ERROR
Programmer Response: Retry the operation later. Explanation: One of the following occurred:
Consider increasing the maximum depth for this queue, v On an MQOPEN call, the ObjectQMgrName field in the
or arranging for more instances of the application to object descriptor MQOD or object record MQOR
service the queue. specifies the name of a local definition of a remote
queue (in order to specify a queue-manager alias),
and in that local definition the RemoteQMgrName
attribute is the name of the local queue manager.
However, the ObjectName field in MQOD or MQOR
specifies the name of a model queue on the local

queue manager; this is not allowed. See the 1 v On i5/OS, this reason can also be returned by the
WebSphere MQ Application Programming Guide for 1 MQOPEN and MQPUT1 calls, when
more information. 1 MQHC_DEF_HCONN is specified for the Hconn
v On an MQPUT1 call, the object descriptor MQOD or 1 parameter by an application running in
object record MQOR specifies the name of a model 1 compatibility mode.
queue. 1 2. On an MQCONN or MQCONNX call from an MQ
v On a previous MQPUT or MQPUT1 call, the 1 client application:
ReplyToQ field in the message descriptor specified the
name of a model queue, but a model queue cannot
1 v Attempting to connect to a queue manager within
be specified as the destination for reply or report
1 an MQ-client queue-manager group when none
1 of the queue managers in the group is available
messages. Only the name of a predefined queue, or
1 for connection (see the QMgrName parameter of the
the name of the dynamic queue created from the
model queue, can be specified as the destination. In
1 MQCONN call).
this situation the reason code 1 v If there is an error with the client-connection or
MQRC_Q_TYPE_ERROR is returned in the Reason 1 the corresponding server-connection channel
field of the MQDLH structure when the reply 1 definitions.
message or report message is placed on the 1 v On z/OS, if the optional OS/390 client
dead-letter queue. 1 attachment feature has not been installed.
Completion Code: MQCC_FAILED 1 3. If a command uses the CommandScope parameter
1 specfying a queue manager that is not active in the
Programmer Response: Specify a valid queue. 1 queue-sharing group.
2058 (X'080A') MQRC_Q_MGR_NAME_ERROR
Programmer Response: Ensure that the queue
Explanation: On an MQCONN or MQCONNX call, manager has been started. If the connection is from a
the value specified for the QMgrName parameter is not client application, check the channel definitions.
valid or not known. This reason also occurs if the
parameter pointer is not valid. (It is not always possible
to detect parameter pointers that are not valid; if not 2061 (X'080D') MQRC_REPORT_OPTIONS_ERROR
detected, unpredictable results occur.) Explanation: An MQPUT or MQPUT1 call was issued,
v On z/OS for CICS applications, this reason can occur but the Report field in the message descriptor MQMD
on any call if the original connect specified an contains one or more options that are not recognized
incorrect or unrecognized name. by the local queue manager. The options that cause this
reason code to be returned depend on the destination
This reason code can also occur if an MQ client of the message; see the description of REPORT in the
application attempts to connect to a queue manager WebSphere MQ Application Programming Guide for more
within an MQ-client queue-manager group (see the details.
QMgrName parameter of MQCONN), and either:
v Queue-manager groups are not supported.
the MQMD of a report message, or in the Reason field
v There is no queue-manager group with the specified
in the MQDLH structure of a message on the
name.
dead-letter queue; in both cases it indicates that the
Completion Code: MQCC_FAILED destination queue manager does not support one or
more of the report options specified by the sender of
Programmer Response: Use an all-blank name if
the message.
possible, or verify that the name used is valid.
2059 (X'080B') MQRC_Q_MGR_NOT_AVAILABLE Programmer Response: Do the following:
v Ensure that the Report field in the message
1 Explanation: This occurs:
descriptor is initialized with a value when the
1 1. On an MQCONN or MQCONNX call, the queue message descriptor is declared, or is assigned a value
1 manager identified by the QMgrName parameter is not prior to the MQPUT or MQPUT1 call. Specify
1 available for connection. MQRO_NONE if no report options are required.
1 v On z/OS: v Ensure that the report options specified are valid; see
1 – For batch applications, this reason can be the Report field described in the description of
1 returned to applications running in LPARs that MQMD in the WebSphere MQ Application
1 do not have a queue manager installed. Programming Guide for valid report options.
1 – For CICS applications, this reason can occur on v If multiple report options are being set by adding the
1 any call if the original connect specified a individual report options together, ensure that the
1 queue manager whose name was recognized, same report option is not added twice.
1 but which is not available.

v Check that conflicting report options are not selectors specified on the call; the valid range is 0
specified. For example, do not add both through 256.
MQRO_EXCEPTION and
MQRO_EXCEPTION_WITH_DATA to the Report
2067 (X'0813') MQRC_SELECTOR_ERROR
field; only one of these can be specified.
Explanation: An MQINQ or MQSET call was issued,
but the Selectors array contains a selector that is not
2062 (X'080E')
valid for one of the following reasons:
MQRC_SECOND_MARK_NOT_ALLOWED
v The selector is not supported or out of range.
Explanation: An MQGET call was issued specifying v The selector is not applicable to the type of object
the MQGMO_MARK_SKIP_BACKOUT option in the whose attributes are being inquired or set.
Options field of MQGMO, but a message has already v The selector is for an attribute that cannot be set.
been marked within the current unit of work. Only one
This reason also occurs if the parameter pointer is not
marked message is allowed within each unit of work.
valid. (It is not always possible to detect parameter
This reason code occurs only on z/OS. pointers that are not valid; if not detected,
Programmer Response: Modify the application so that
no more than one message is marked within each unit Programmer Response: Ensure that the value
of work. specified for the selector is valid for the object type
represented by Hobj. For the MQSET call, also ensure
that the selector represents an integer attribute that can
2063 (X'080F') MQRC_SECURITY_ERROR
be set.
Explanation: An MQCONN, MQCONNX, MQOPEN,
MQPUT1, or MQCLOSE call was issued, but it failed
2068 (X'0814') MQRC_SELECTOR_NOT_FOR_TYPE
because a security error occurred.
v On z/OS, the security error was returned by the Explanation: On the MQINQ call, one or more
External Security Manager. selectors in the Selectors array is not applicable to the
type of the queue whose attributes are being inquired.
This reason also occurs when the queue is a cluster
Programmer Response: Note the error from the queue that resolved to a remote instance of the queue.
security manager, and contact your system programmer In this case only a subset of the attributes that are valid
or security administrator. for local queues can be inquired. See the usage notes in
v On i5/OS, the FFST log will contain the error the description of MQINQ in the WebSphere MQ
information. Application Programming Guide for further details.
The call completes with MQCC_WARNING, with the
2065 (X'0811') MQRC_SELECTOR_COUNT_ERROR attribute values for the inapplicable selectors set as
follows:
Explanation: On an MQINQ or MQSET call, the v For integer attributes, the corresponding elements of
SelectorCount parameter specifies a value that is not IntAttrs are set to MQIAV_NOT_APPLICABLE.
valid. This reason also occurs if the parameter pointer v For character attributes, the appropriate parts of the
is not valid. (It is not always possible to detect CharAttrs string are set to a character string
parameter pointers that are not valid; if not detected, consisting entirely of asterisks (*).
Programmer Response: Verify that the selector
Programmer Response: Specify a value in the range 0 specified is the one that was intended.
through 256.
If the queue is a cluster queue, specifying one of the
MQOO_BROWSE, MQOO_INPUT_*, or MQOO_SET
2066 (X'0812') options in addition to MQOO_INQUIRE forces the
MQRC_SELECTOR_LIMIT_EXCEEDED queue to resolve to the local instance of the queue.
Explanation: On an MQINQ or MQSET call, the However, if there is no local instance of the queue the
SelectorCount parameter specifies a value that is larger MQOPEN call fails.
than the maximum supported (256).
Programmer Response: Reduce the number of

2069 (X'0815') MQRC_SIGNAL_OUTSTANDING 2072 (X'0818')

MQRC_SYNCPOINT_NOT_AVAILABLE
Explanation: An MQGET call was issued with either
the MQGMO_SET_SIGNAL or MQGMO_WAIT option, Explanation: Either MQGMO_SYNCPOINT was
but there is already a signal outstanding for the queue specified on an MQGET call or MQPMO_SYNCPOINT
handle Hobj. was specified on an MQPUT or MQPUT1 call, but the
local queue manager was unable to honor the request.
This reason code occurs only in the following
If the queue manager does not support units of work,
environments: z/OS, Windows 95, Windows 98.
the SyncPoint queue-manager attribute will have the
Completion Code: MQCC_FAILED value MQSP_NOT_AVAILABLE.
Programmer Response: Check the application logic. If This reason code can also occur on the MQGET,
it is necessary to set a signal or wait when there is a MQPUT, and MQPUT1 calls when an external
signal outstanding for the same queue, a different unit-of-work coordinator is being used. If that
object handle must be used. coordinator requires an explicit call to start the unit of
work, but the application has not issued that call prior
to the MQGET, MQPUT, or MQPUT1 call, reason code
2070 (X'0816') MQRC_SYNCPOINT_NOT_AVAILABLE is returned.
MQRC_SIGNAL_REQUEST_ACCEPTED v On i5/OS, this reason codes means that i5/OS
Explanation: An MQGET call was issued specifying Commitment Control is not started, or is unavailable
MQGMO_SET_SIGNAL in the GetMsgOpts parameter, for use by the queue manager.
but no suitable message was available; the call returns v On z/OS, this reason code does not occur.
immediately. The application can now wait for the Completion Code: MQCC_FAILED
signal to be delivered.
v On z/OS, the application should wait on the Event Programmer Response: Remove the specification of
Control Block pointed to by the Signal1 field. MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as
v On Windows 95, Windows 98, the application should appropriate.
wait for the signal Windows message to be delivered. v On i5/OS, ensure that Commitment Control has been
started. If this reason code occurs after Commitment
This reason code occurs only in the following Control has been started, contact your system
environments: z/OS, Windows 95, Windows 98. programmer.
2075 (X'081B')
Programmer Response: Wait for the signal; when it is
MQRC_TRIGGER_CONTROL_ERROR
delivered, check the signal to ensure that a message is
now available. If it is, reissue the MQGET call. Explanation: On an MQSET call, the value specified
v On z/OS, wait on the ECB pointed to by the Signal1 for the MQIA_TRIGGER_CONTROL attribute selector
field and, when it is posted, check it to ensure that a is not valid.
message is now available.
v On Windows 95, Windows 98, the application Completion Code: MQCC_FAILED
(thread) should continue executing its message loop. Programmer Response: Specify a valid value.
2071 (X'0817') MQRC_STORAGE_NOT_AVAILABLE 2076 (X'081C') MQRC_TRIGGER_DEPTH_ERROR

Explanation: The call failed because there is Explanation: On an MQSET call, the value specified
insufficient main storage available. for the MQIA_TRIGGER_DEPTH attribute selector is
Completion Code: MQCC_FAILED not valid.
Programmer Response: Ensure that active applications Completion Code: MQCC_FAILED

are behaving correctly, for example, that they are not Programmer Response: Specify a value that is greater
looping unexpectedly. If no problems are found, make than zero.
more main storage available.
v On z/OS, if no application problems are found, ask
2077 (X'081D')
your system programmer to increase the size of the
MQRC_TRIGGER_MSG_PRIORITY_ERR
region in which the queue manager runs.
Explanation: On an MQSET call, the value specified
for the MQIA_TRIGGER_MSG_PRIORITY attribute
selector is not valid.
Programmer Response: Specify a value in the range

zero through the value of MaxPriority queue-manager This reason code can also occur when BaseQName is the
attribute. name of a cluster queue that cannot be resolved
successfully.
2078 (X'081E') MQRC_TRIGGER_TYPE_ERROR Completion Code: MQCC_FAILED
Explanation: On an MQSET call, the value specified Programmer Response: Correct the queue definitions.
for the MQIA_TRIGGER_TYPE attribute selector is not
valid.
2085 (X'0825') MQRC_UNKNOWN_OBJECT_NAME
Programmer Response: Specify a valid value. issued, but the object identified by the ObjectName and
ObjectQMgrName fields in the object descriptor MQOD
cannot be found. One of the following applies:
2079 (X'081F')
MQRC_TRUNCATED_MSG_ACCEPTED v The ObjectQMgrName field is one of the following:
– Blank
Explanation: On an MQGET call, the message length – The name of the local queue manager
was too large to fit into the supplied buffer. The – The name of a local definition of a remote queue
MQGMO_ACCEPT_TRUNCATED_MSG option was (a queue-manager alias) in which the
specified, so the call completes. The message is RemoteQMgrName attribute is the name of the local
removed from the queue (subject to unit-of-work queue manager
considerations), or, if this was a browse operation, the
browse cursor is advanced to this message. but no object with the specified ObjectName and
ObjectType exists on the local queue manager.
The DataLength parameter is set to the length of the
v The object being opened is a cluster queue that is
message before truncation, the Buffer parameter
hosted on a remote queue manager, but the local
contains as much of the message as fits, and the
queue manager does not have a defined route to the
MQMD structure is filled in.
remote queue manager.
Completion Code: MQCC_WARNING v The object being opened is a queue definition that
Programmer Response: None, because the application has QSGDISP(GROUP). Such definitions cannot be
expected this situation. used with the MQOPEN and MQPUT1 calls.
This can also occur in response to a command that

2080 (X'0820') MQRC_TRUNCATED_MSG_FAILED specifies the name of an object or other item that does
Explanation: On an MQGET call, the message length not exist.
was too large to fit into the supplied buffer. The Completion Code: MQCC_FAILED
MQGMO_ACCEPT_TRUNCATED_MSG option was not
specified, so the message has not been removed from Programmer Response: Specify a valid object name.
the queue. If this was a browse operation, the browse Ensure that the name is padded to the right with
cursor remains where it was before this call, but if blanks if necessary. If this is correct, check the object
MQGMO_BROWSE_FIRST was specified, the browse definitions.
cursor is positioned logically before the highest-priority
message on the queue. 2086 (X'0826')
The DataLength field is set to the length of the message MQRC_UNKNOWN_OBJECT_Q_MGR
before truncation, the Buffer parameter contains as Explanation: On an MQOPEN or MQPUT1 call, the
much of the message as fits, and the MQMD structure ObjectQMgrName field in the object descriptor MQOD
is filled in. does not satisfy the naming rules for objects. For more
Completion Code: MQCC_WARNING information, see the WebSphere MQ Application
Programming Guide.
Programmer Response: Supply a buffer that is at least
as large as DataLength, or specify This reason also occurs if the ObjectType field in the
MQGMO_ACCEPT_TRUNCATED_MSG if not all of object descriptor has the value MQOT_Q_MGR, and
the message data is required. the ObjectQMgrName field is not blank, but the name
specified is not the name of the local queue manager.
2082 (X'0822') MQRC_UNKNOWN_ALIAS_BASE_Q Completion Code: MQCC_FAILED
Explanation: An MQOPEN or MQPUT1 call was Programmer Response: Specify a valid queue
issued specifying an alias queue as the target, but the manager name. To refer to the local queue manager, a
BaseQName in the alias queue attributes is not name consisting entirely of blanks or beginning with a
recognized as a queue name. null character can be used. Ensure that the name is

padded to the right with blanks or terminated with a

2090 (X'082A') MQRC_WAIT_INTERVAL_ERROR
null character if necessary.
Explanation: On the MQGET call, the value specified
for the WaitInterval field in the GetMsgOpts parameter
2087 (X'0827')
is not valid.
MQRC_UNKNOWN_REMOTE_Q_MGR
Explanation: On an MQOPEN or MQPUT1 call, an
error occurred with the queue-name resolution, for one Programmer Response: Specify a value greater than
of the following reasons: or equal to zero, or the special value
v ObjectQMgrName is blank or the name of the local MQWI_UNLIMITED if an indefinite wait is required.
queue manager, ObjectName is the name of a local
definition of a remote queue (or an alias to one), and 2091 (X'082B') MQRC_XMIT_Q_TYPE_ERROR
one of the following is true:
– RemoteQMgrName is blank or the name of the local Explanation: On an MQOPEN or MQPUT1 call, a
queue manager. Note that this error occurs even if message is to be sent to a remote queue manager. The
XmitQName is not blank. ObjectName or ObjectQMgrName field in the object
– XmitQName is blank, but there is no transmission descriptor specifies the name of a local definition of a
queue defined with the name of RemoteQMgrName, remote queue but one of the following applies to the
and the DefXmitQName queue-manager attribute is XmitQName attribute of the definition:
blank. v XmitQName is not blank, but specifies a queue that is
– RemoteQMgrName and RemoteQName specify a cluster not a local queue
queue that cannot be resolved successfully, and v XmitQName is blank, but RemoteQMgrName specifies a
the DefXmitQName queue-manager attribute is queue that is not a local queue
blank.
v ObjectQMgrName is the name of a local definition of a This reason also occurs if the queue name is resolved
remote queue (containing a queue-manager alias through a cell directory, and the remote queue manager
definition), and one of the following is true: name obtained from the cell directory is the name of a
– RemoteQName is not blank. queue, but this is not a local queue.
– XmitQName is blank, but there is no transmission Completion Code: MQCC_FAILED
queue defined with the name of RemoteQMgrName,
and the DefXmitQName queue-manager attribute is Programmer Response: Check the values specified for
blank. ObjectName and ObjectQMgrName. If these are correct,
check the queue definitions. For more information on
v ObjectQMgrName is not:
transmission queues, see the WebSphere MQ Application
– Blank
Programming Guide.
– The name of the local queue manager
– The name of a transmission queue
– The name of a queue-manager alias definition 2092 (X'082C') MQRC_XMIT_Q_USAGE_ERROR
(that is, a local definition of a remote queue with a
blank RemoteQName)
1 Explanation: On an MQOPEN or MQPUT1 call, a
1 message is to be sent to a remote queue manager, but
but the DefXmitQName queue-manager attribute is 1 one of the following occurred:
blank and the queue manager is not part of a 1 v ObjectQMgrName specifies the name of a local queue,
queue-sharing group with intra-group queuing 1 but it does not have a Usage attribute of
enabled. 1 MQUS_TRANSMISSION.
v ObjectQMgrName is the name of a model queue. 1 v The ObjectName or ObjectQMgrName field in the object
v The queue name is resolved through a cell directory. 1 descriptor specifies the name of a local definition of
However, there is no queue defined with the same 1 a remote queue but one of the following applies to
name as the remote queue manager name obtained 1 the XmitQName attribute of the definition:
from the cell directory, and the DefXmitQName 1 – XmitQName is not blank, but specifies a queue that
queue-manager attribute is blank. 1 does not have a Usage attribute of
1 MQUS_TRANSMISSION
1 – XmitQName is blank, but RemoteQMgrName specifies a
Programmer Response: Check the values specified for 1 queue that does not have a Usage attribute of
ObjectQMgrName and ObjectName. If these are correct, 1 MQUS_TRANSMISSION
check the queue definitions. 1 – XmitQName specifies the queue
1 SYSTEM.QSG.TRANSMIT.QUEUE the IGQ queue
1 manager attribute indicates that IGQ is
1 DISABLED.
1 v The queue name is resolved through a cell directory,
1 and the remote queue manager name obtained from

1 the cell directory is the name of a local queue, but it that implies it) when the queue is opened.
1 does not have a Usage attribute of
1 MQUS_TRANSMISSION.
2097 (X'0831') MQRC_CONTEXT_HANDLE_ERROR
Explanation: On an MQPUT or MQPUT1 call,
Programmer Response: Check the values specified for MQPMO_PASS_IDENTITY_CONTEXT or
ObjectName and ObjectQMgrName. If these are correct, MQPMO_PASS_ALL_CONTEXT was specified, but the
check the queue definitions. For more information on handle specified in the Context field of the PutMsgOpts
transmission queues, see the WebSphere MQ Application parameter is either not a valid queue handle, or it is a
Programming Guide. valid queue handle but the queue was not opened with
MQOO_SAVE_ALL_CONTEXT.
2093 (X'082D') MQRC_NOT_OPEN_FOR_PASS_ALL Completion Code: MQCC_FAILED
Explanation: An MQPUT call was issued with the Programmer Response: Specify
MQPMO_PASS_ALL_CONTEXT option specified in the MQOO_SAVE_ALL_CONTEXT when the queue
PutMsgOpts parameter, but the queue had not been referred to is opened.
opened with the MQOO_PASS_ALL_CONTEXT option.
Completion Code: MQCC_FAILED 2098 (X'0832') MQRC_CONTEXT_NOT_AVAILABLE
Programmer Response: Specify Explanation: On an MQPUT or MQPUT1 call,
MQOO_PASS_ALL_CONTEXT (or another option that MQPMO_PASS_IDENTITY_CONTEXT or
implies it) when the queue is opened. MQPMO_PASS_ALL_CONTEXT was specified, but the
queue handle specified in the Context field of the
PutMsgOpts parameter has no context associated with it.
2094 (X'082E')
This arises if no message has yet been successfully
MQRC_NOT_OPEN_FOR_PASS_IDENT
retrieved with the queue handle referred to, or if the
Explanation: An MQPUT call was issued with the last successful MQGET call was a browse.
MQPMO_PASS_IDENTITY_CONTEXT option specified
This condition does not arise if the message that was
in the PutMsgOpts parameter, but the queue had not
last retrieved had no context associated with it.
been opened with the
MQOO_PASS_IDENTITY_CONTEXT option. v On z/OS, if a message is received by a message
channel agent that is putting messages with the
Completion Code: MQCC_FAILED authority of the user identifier in the message, this
Programmer Response: Specify code is returned in the Feedback field of an exception
MQOO_PASS_IDENTITY_CONTEXT (or another option report if the message has no context associated with
that implies it) when the queue is opened. it.
2095 (X'082F') MQRC_NOT_OPEN_FOR_SET_ALL Programmer Response: Ensure that a successful
Explanation: An MQPUT call was issued with the nonbrowse get call has been issued with the queue
MQPMO_SET_ALL_CONTEXT option specified in the handle referred to.
PutMsgOpts parameter, but the queue had not been
opened with the MQOO_SET_ALL_CONTEXT option. 2099 (X'0833') MQRC_SIGNAL1_ERROR
Completion Code: MQCC_FAILED Explanation: An MQGET call was issued, specifying
Programmer Response: Specify MQGMO_SET_SIGNAL in the GetMsgOpts parameter,
MQOO_SET_ALL_CONTEXT when the queue is but the Signal1 field is not valid.
opened. v On z/OS, the address contained in the Signal1 field
is not valid, or points to read-only storage. (It is not
always possible to detect parameter pointers that are
2096 (X'0830') MQRC_NOT_OPEN_FOR_SET_IDENT not valid; if not detected, unpredictable results
occur.)
Explanation: An MQPUT call was issued with the
v On Windows 95, Windows 98, the window handle in
MQPMO_SET_IDENTITY_CONTEXT option specified
the Signal1 field is not valid.
in the PutMsgOpts parameter, but the queue had not
been opened with the
MQOO_SET_IDENTITY_CONTEXT option. This reason code occurs only in the following
environments: z/OS, Windows 95, Windows 98.
MQOO_SET_IDENTITY_CONTEXT (or another option Programmer Response: Correct the setting of the
Signal1 field.

v On HP OpenVMS, OS/2, i5/OS, HP NonStop Server,

2100 (X'0834') MQRC_OBJECT_ALREADY_EXISTS
and UNIX systems, consult the FFST record to obtain
Explanation: An MQOPEN call was issued to create a more detail about the problem.
dynamic queue, but a queue with the same name as the
dynamic queue already exists.
2103 (X'0837')
v On z/OS, a rare “race condition” can also give rise MQRC_ANOTHER_Q_MGR_CONNECTED
to this reason code; see the description of reason
code MQRC_NAME_IN_USE for more details. Explanation: An MQCONN or MQCONNX call was
issued, but the thread or process is already connected
Completion Code: MQCC_FAILED to a different queue manager. The thread or process can
Programmer Response: If supplying a dynamic queue connect to only one queue manager at a time.
name in full, ensure that it obeys the naming v On z/OS, this reason code does not occur.
conventions for dynamic queues; if it does, either v On Windows, MTS objects do not receive this reason
supply a different name, or delete the existing queue if code, as connections to other queue managers are
it is no longer required. Alternatively, allow the queue allowed.
manager to generate the name.
If the queue manager is generating the name (either in
part or in full), reissue the MQOPEN call. Programmer Response: Use the MQDISC call to
disconnect from the queue manager that is already
connected, and then issue the MQCONN or
2101 (X'0835') MQRC_OBJECT_DAMAGED MQCONNX call to connect to the new queue manager.
Explanation: The object accessed by the call is Disconnecting from the existing queue manager will
damaged and cannot be used. For example, this may be close any queues that are currently open; it is
because the definition of the object in main storage is recommended that any uncommitted units of work
not consistent, or because it differs from the definition should be committed or backed out before the MQDISC
of the object on disk, or because the definition on disk call is issued.
cannot be read. The object can be deleted, although it
may not be possible to delete the associated user space.
2104 (X'0838')
v On z/OS, this reason occurs when the DB2 list
MQRC_UNKNOWN_REPORT_OPTION
header or structure number associated with a shared
queue is zero. This situation arises as a result of Explanation: An MQPUT or MQPUT1 call was issued,
using the MQSC command DELETE CFSTRUCT to but the Report field in the message descriptor MQMD
delete the DB2 structure definition. The command contains one or more options that are not recognized
resets the list header and structure number to zero by the local queue manager. The options are accepted.
for each of the shared queues that references the
deleted CF strcture. The options that cause this reason code to be returned
depend on the destination of the message; see the
Completion Code: MQCC_FAILED description of REPORT in the WebSphere MQ Application
Programming Guide for more details.
Programmer Response: It may be necessary to stop
and restart the queue manager, or to restore the Completion Code: MQCC_WARNING
queue-manager data from back-up storage.
Programmer Response: If this reason code is expected,
v On HP OpenVMS, OS/2, i5/OS, HP NonStop Server, no corrective action is required. If this reason code is
and UNIX systems, consult the FFST™ record to not expected, do the following:
obtain more detail about the problem. v Ensure that the Report field in the message
v On z/OS, delete the shared queue and redefine it descriptor is initialized with a value when the
using the MQSC command DEFINE QLOCAL. This message descriptor is declared, or is assigned a value
will automatically define a CF structure and allocate prior to the MQPUT or MQPUT1 call.
list headers for it. v Ensure that the report options specified are valid; see
the Report field described in the description of
MQMD in the WebSphere MQ Application
2102 (X'0836') MQRC_RESOURCE_PROBLEM
Programming Guide for valid report options.
Explanation: There are insufficient system resources to v If multiple report options are being set by adding the
complete the call successfully. individual report options together, ensure that the
same report option is not added twice.
v Check that conflicting report options are not
Programmer Response: Run the application when the specified. For example, do not add both
machine is less heavily loaded. MQRO_EXCEPTION and
v On z/OS, check the operator console for messages MQRO_EXCEPTION_WITH_DATA to the Report
that may provide additional information. field; only one of these can be specified.

2105 (X'0839') MQRC_STORAGE_CLASS_ERROR 2109 (X'083D') MQRC_SUPPRESSED_BY_EXIT

Explanation: The MQPUT or MQPUT1 call was Explanation: On any call other than MQCONN or
issued, but the storage-class object defined for the MQDISC, the API crossing exit suppressed the call.
queue does not exist.
This reason code occurs only on z/OS.
Programmer Response: Obey the rules for MQI calls
Programmer Response: Create the storage-class object that the exit enforces. To find out the rules, see the
required by the queue, or modify the queue definition writer of the exit.
to use an existing storage class. The name of the
storage-class object used by the queue is given by the
2110 (X'083E') MQRC_FORMAT_ERROR
StorageClass queue attribute.
Explanation: An MQGET call was issued with the
MQGMO_CONVERT option specified in the
2106 (X'083A')
GetMsgOpts parameter, but the message cannot be
MQRC_COD_NOT_VALID_FOR_XCF_Q
converted successfully due to an error associated with
Explanation: An MQPUT or MQPUT1 call was issued, the message format. Possible errors include:
but the Report field in the message descriptor MQMD v The format name in the message is MQFMT_NONE.
specifies one of the MQRO_COD_* options and the v A user-written exit with the name specified by the
target queue is an XCF queue. MQRO_COD_* options Format field in the message cannot be found.
cannot be specified for XCF queues. v The message contains data that is not consistent with
the format definition.
The message is returned unconverted to the application
issuing the MQGET call, the values of the
Programmer Response: Remove the relevant CodedCharSetId and Encoding fields in the MsgDesc
MQRO_COD_* option. parameter are set to those of the message returned, and
the call completes with MQCC_WARNING.
2107 (X'083B') MQRC_XWAIT_CANCELED
If the message consists of several parts, each of which
Explanation: An MQXWAIT call was issued, but the is described by its own CodedCharSetId and Encoding
call has been canceled because a STOP CHINIT fields (for example, a message with format name
command has been issued (or the queue manager has MQFMT_DEAD_LETTER_HEADER), some parts may
been stopped, which causes the same effect). Refer to be converted and other parts not converted. However,
the WebSphere MQ Intercommunication book for details the values returned in the various CodedCharSetId and
of the MQXWAIT call. Encoding fields always correctly describe the relevant
message data.
Programmer Response: Check the format name that
Programmer Response: Tidy up and terminate. was specified when the message was put. If this is not
one of the built-in formats, check that a suitable exit
2108 (X'083C') MQRC_XWAIT_ERROR with the same name as the format is available for the
queue manager to load. Verify that the data in the
Explanation: An MQXWAIT call was issued, but the message corresponds to the format expected by the
invocation was not valid for one of the following exit.
reasons:
v The wait descriptor MQXWD contains data that is
not valid. 2111 (X'083F') MQRC_SOURCE_CCSID_ERROR
v The linkage stack level is not valid. Explanation: The coded character-set identifier from
v The addressing mode is not valid. which character data is to be converted is not valid or
v There are too many wait events outstanding. not supported.
This reason code occurs only on z/OS. This can occur on the MQGET call when the
MQGMO_CONVERT option is included in the
Completion Code: MQCC_FAILED GetMsgOpts parameter; the coded character-set identifier
Programmer Response: Obey the rules for using the in error is the CodedCharSetId field in the message
MQXWAIT call. Refer to the WebSphere MQ being retrieved. In this case, the message data is
Intercommunication book for details of this call. returned unconverted, the values of the CodedCharSetId
and Encoding fields in the MsgDesc parameter are set to

those of the message returned, and the call completes Encoding fields always correctly describe the relevant
with MQCC_WARNING. message data.
This reason can also occur on the MQGET call when This reason code can also occur on the MQXCNVC call,
the message contains one or more MQ header when the Options parameter contains an unsupported
structures (MQCIH, MQDLH, MQIIH, MQRMH), and MQDCC_SOURCE_* value, or when
the CodedCharSetId field in the message specifies a MQDCC_SOURCE_ENC_UNDEFINED is specified for
character set that does not have SBCS characters for the a UCS-2 code page.
characters that are valid in queue names. MQ header
structures containing such characters are not valid, and
MQCC_FAILED
so the message is returned unconverted. The Unicode
character set UCS-2 is an example of such a character Programmer Response: Check the integer encoding
set. that was specified when the message was put. If this is
correct, check that it is one for which queue-manager
conversion is supported. If queue-manager conversion
is described by its own CodedCharSetId and Encoding
is not supported for the required integer encoding,
fields (for example, a message with format name
conversion must be carried out by the application.
MQFMT_DEAD_LETTER_HEADER), some parts may
be converted and other parts not converted. However,
the values returned in the various CodedCharSetId and 2113 (X'0841')
Encoding fields always correctly describe the relevant MQRC_SOURCE_DECIMAL_ENC_ERROR
message data.
Explanation: On an MQGET call with the
This reason can also occur on the MQXCNVC call; the MQGMO_CONVERT option included in the
coded character-set identifier in error is the GetMsgOpts parameter, the Encoding value in the
SourceCCSID parameter. Either the SourceCCSID message being retrieved specifies a decimal encoding
parameter specifies a value that is not valid or not that is not recognized. The message data is returned
supported, or the SourceCCSID parameter pointer is not unconverted, the values of the CodedCharSetId and
valid. (It is not always possible to detect parameter Encoding fields in the MsgDesc parameter are set to
pointers that are not valid; if not detected, those of the message returned, and the call completes
unpredictable results occur.) with MQCC_WARNING.
Completion Code: MQCC_WARNING or If the message consists of several parts, each of which
MQCC_FAILED is described by its own CodedCharSetId and Encoding
Programmer Response: Check the character-set
identifier that was specified when the message was put,
or that was specified for the SourceCCSID parameter on
the values returned in the various CodedCharSetId and
the MQXCNVC call. If this is correct, check that it is
Encoding fields always correctly describe the relevant
one for which queue-manager conversion is supported.
message data.
If queue-manager conversion is not supported for the
specified character set, conversion must be carried out Completion Code: MQCC_WARNING
by the application.
Programmer Response: Check the decimal encoding
that was specified when the message was put. If this is
2112 (X'0840') correct, check that it is one for which queue-manager
MQRC_SOURCE_INTEGER_ENC_ERROR conversion is supported. If queue-manager conversion
is not supported for the required decimal encoding,
Explanation: On an MQGET call, with the
conversion must be carried out by the application.
MQGMO_CONVERT option included in the
GetMsgOpts parameter, the Encoding value in the
message being retrieved specifies an integer encoding 2114 (X'0842')
that is not recognized. The message data is returned MQRC_SOURCE_FLOAT_ENC_ERROR
unconverted, the values of the CodedCharSetId and
Encoding fields in the MsgDesc parameter are set to Explanation: On an MQGET call, with the
those of the message returned, and the call completes MQGMO_CONVERT option included in the
with MQCC_WARNING. GetMsgOpts parameter, the Encoding value in the
message being retrieved specifies a floating-point
If the message consists of several parts, each of which encoding that is not recognized. The message data is
is described by its own CodedCharSetId and Encoding returned unconverted, the values of the CodedCharSetId
fields (for example, a message with format name and Encoding fields in the MsgDesc parameter are set to
MQFMT_DEAD_LETTER_HEADER), some parts may those of the message returned, and the call completes
be converted and other parts not converted. However, with MQCC_WARNING.

is described by its own CodedCharSetId and Encoding

2116 (X'0844')
MQRC_TARGET_INTEGER_ENC_ERROR
be converted and other parts not converted. However, Explanation: On an MQGET call with the
the values returned in the various CodedCharSetId and MQGMO_CONVERT option included in the
Encoding fields always correctly describe the relevant GetMsgOpts parameter, the Encoding value in the
message data. MsgDesc parameter specifies an integer encoding that is
not recognized. The message data is returned
Programmer Response: Check the floating-point Encoding fields in the MsgDesc parameter are set to
encoding that was specified when the message was those of the message being retrieved, and the call
put. If this is correct, check that it is one for which completes with MQCC_WARNING.
queue-manager conversion is supported. If
This reason code can also occur on the MQXCNVC call,
queue-manager conversion is not supported for the
when the Options parameter contains an unsupported
required floating-point encoding, conversion must be
MQDCC_TARGET_* value, or when
carried out by the application.
MQDCC_TARGET_ENC_UNDEFINED is specified for
a UCS-2 code page.
2115 (X'0843') MQRC_TARGET_CCSID_ERROR
Explanation: The coded character-set identifier to MQCC_FAILED
which character data is to be converted is not valid or
Programmer Response: Check the integer encoding
not supported.
that was specified. If this is correct, check that it is one
This can occur on the MQGET call when the for which queue-manager conversion is supported. If
MQGMO_CONVERT option is included in the queue-manager conversion is not supported for the
GetMsgOpts parameter; the coded character-set identifier required integer encoding, conversion must be carried
in error is the CodedCharSetId field in the MsgDesc out by the application.
parameter. In this case, the message data is returned
2117 (X'0845')
Encoding fields in the MsgDesc parameter are set to
MQRC_TARGET_DECIMAL_ENC_ERROR
those of the message returned, and the call completes
with MQCC_WARNING. Explanation: On an MQGET call with the
This reason can also occur on the MQGET call when
GetMsgOpts parameter, the Encoding value in the
the message contains one or more MQ header
MsgDesc parameter specifies a decimal encoding that is
structures (MQCIH, MQDLH, MQIIH, MQRMH), and
not recognized. The message data is returned
the CodedCharSetId field in the MsgDesc parameter
specifies a character set that does not have SBCS
Encoding fields in the MsgDesc parameter are set to
characters for the characters that are valid in queue
those of the message returned, and the call completes
names. The Unicode character set UCS-2 is an example
with MQCC_WARNING.
of such a character set.
This reason can also occur on the MQXCNVC call; the
coded character-set identifier in error is the Programmer Response: Check the decimal encoding
TargetCCSID parameter. Either the TargetCCSID that was specified. If this is correct, check that it is one
parameter specifies a value that is not valid or not for which queue-manager conversion is supported. If
supported, or the TargetCCSID parameter pointer is not queue-manager conversion is not supported for the
valid. (It is not always possible to detect parameter required decimal encoding, conversion must be carried
pointers that are not valid; if not detected, out by the application.
Completion Code: MQCC_WARNING or 2118 (X'0846')
MQCC_FAILED MQRC_TARGET_FLOAT_ENC_ERROR
Programmer Response: Check the character-set Explanation: On an MQGET call with the
identifier that was specified for the CodedCharSetId MQGMO_CONVERT option included in the
field in the MsgDesc parameter on the MQGET call, or GetMsgOpts parameter, the Encoding value in the
that was specified for the SourceCCSID parameter on MsgDesc parameter specifies a floating-point encoding
the MQXCNVC call. If this is correct, check that it is that is not recognized. The message data is returned
one for which queue-manager conversion is supported. unconverted, the values of the CodedCharSetId and
If queue-manager conversion is not supported for the Encoding fields in the MsgDesc parameter are set to
specified character set, conversion must be carried out those of the message returned, and the call completes
by the application. with MQCC_WARNING.

Completion Code: MQCC_WARNING be converted and other parts not converted. However,
the values returned in the various character-set and
Programmer Response: Check the floating-point
encoding fields always correctly describe the relevant
encoding that was specified. If this is correct, check that
message data.
it is one for which queue-manager conversion is
supported. If queue-manager conversion is not This reason can also occur on the MQXCNVC call,
supported for the required floating-point encoding, when the TargetBuffer parameter is too small too
conversion must be carried out by the application. accommodate the converted string, and the string has
been truncated to fit in the buffer. The length of valid
data returned is given by the DataLength parameter; in
2119 (X'0847') MQRC_NOT_CONVERTED
the case of a DBCS string or mixed SBCS/DBCS string,
Explanation: An MQGET call was issued with the this length may be less than the length of TargetBuffer.
MQGMO_CONVERT option specified in the
GetMsgOpts parameter, but an error occurred during
conversion of the data in the message. The message Programmer Response: For the MQGET call, check
data is returned unconverted, the values of the that the exit is converting the message data correctly
CodedCharSetId and Encoding fields in the MsgDesc and setting the output length DataLength to the
parameter are set to those of the message returned, and appropriate value. If it is, the application issuing the
the call completes with MQCC_WARNING. MQGET call must provide a larger buffer for the
Buffer parameter.
is described by its own CodedCharSetId and Encoding For the MQXCNVC call, if the string must be converted
fields (for example, a message with format name without truncation, provide a larger output buffer.
2121 (X'0849')
MQRC_NO_EXTERNAL_PARTICIPANTS
Encoding fields always correctly describe the relevant
message data. Explanation: An MQBEGIN call was issued to start a
unit of work coordinated by the queue manager, but no
This error may also indicate that a parameter to the
participating resource managers have been registered
data-conversion service is not supported.
with the queue manager. As a result, only changes to
Completion Code: MQCC_WARNING MQ resources can be coordinated by the queue
manager in the unit of work.
Programmer Response: Check that the message data
is correctly described by the Format, CodedCharSetId This reason code occurs in the following environments:
and Encoding parameters that were specified when the AIX, HP-UX, OS/2, i5/OS, Solaris, Windows.
message was put. Also check that these values, and the
CodedCharSetId and Encoding specified in the MsgDesc
parameter on the MQGET call, are supported for Programmer Response: If the application does not
queue-manager conversion. If the required conversion require non-MQ resources to participate in the unit of
is not supported, conversion must be carried out by the work, this reason code can be ignored or the
application. MQBEGIN call removed. Otherwise consult your
system programmer to determine why the required
resource managers have not been registered with the
2120 (X'0848')
queue manager; the queue manager’s configuration file
MQRC_CONVERTED_MSG_TOO_BIG
may be in error.
2122 (X'084A')
GetMsgOpts parameter, the message data expanded
MQRC_PARTICIPANT_NOT_AVAILABLE
during data conversion and exceeded the size of the
buffer provided by the application. However, the Explanation: An MQBEGIN call was issued to start a
message had already been removed from the queue unit of work coordinated by the queue manager, but
because prior to conversion the message data could be one or more of the participating resource managers that
accommodated in the application buffer without had been registered with the queue manager is not
truncation. available. As a result, changes to those resources cannot
be coordinated by the queue manager in the unit of
The message is returned unconverted, with the
work.
CompCode parameter of the MQGET call set to
MQCC_WARNING. If the message consists of several This reason code occurs in the following environments:
parts, each of which is described by its own AIX, HP-UX, OS/2, i5/OS, Solaris, Windows.
character-set and encoding fields (for example, a
message with format name Completion Code: MQCC_WARNING

Programmer Response: If the application does not

2125 (X'084D') MQRC_BRIDGE_STARTED
require non-MQ resources to participate in the unit of
work, this reason code can be ignored. Otherwise Explanation: The IMS bridge has been started.
consult your system programmer to determine why the
required resource managers are not available. The
resource manager may have been halted temporarily, or Programmer Response: None. This reason code is
there may be an error in the queue manager’s only used to identify the corresponding event message.
configuration file.
2126 (X'084E') MQRC_BRIDGE_STOPPED
2123 (X'084B') MQRC_OUTCOME_MIXED
Explanation: The IMS bridge has been stopped.
Explanation: The queue manager is acting as the
unit-of-work coordinator for a unit of work that Completion Code: MQCC_WARNING
involves other resource managers, but one of the Programmer Response: None. This reason code is
following occurred: only used to identify the corresponding event message.
v An MQCMIT or MQDISC call was issued to commit
the unit of work, but one or more of the
participating resource managers backed-out the unit 2127 (X'084F')
of work instead of committing it. As a result, the MQRC_ADAPTER_STORAGE_SHORTAGE
outcome of the unit of work is mixed. Explanation: On an MQCONN call, the adapter was
v An MQBACK call was issued to back out a unit of unable to acquire storage.
work, but one or more of the participating resource
managers had already committed the unit of work. This reason code occurs only on z/OS.
This reason code occurs in the following environments:
AIX, HP-UX, OS/2, Solaris, Windows. Programmer Response: Notify the system
programmer. The system programmer should
Completion Code: MQCC_FAILED determine why the system is short on storage, and take
Programmer Response: Examine the queue-manager appropriate action, for example, increase the region size
error logs for messages relating to the mixed outcome; on the step or job card.
these messages identify the resource managers that are
affected. Use procedures local to the affected resource 2128 (X'0850') MQRC_UOW_IN_PROGRESS
managers to resynchronize the resources.
Explanation: An MQBEGIN call was issued to start a
This reason code does not prevent the application unit of work coordinated by the queue manager, but a
initiating further units of work. unit of work is already in existence for the connection
handle specified. This may be a global unit of work
2124 (X'084C') MQRC_OUTCOME_PENDING started by a previous MQBEGIN call, or a unit of work
that is local to the queue manager or one of the
Explanation: The queue manager is acting as the cooperating resource managers. No more than one unit
unit-of-work coordinator for a unit of work that of work can exist concurrently for a connection handle.
involves other resource managers, and an MQCMIT or
MQDISC call was issued to commit the unit of work, This reason code occurs in the following environments:
but one or more of the participating resource managers AIX, HP-UX, OS/2, i5/OS, Solaris, Windows.
has not confirmed that the unit of work was committed Completion Code: MQCC_FAILED
successfully.
Programmer Response: Review the application logic
The completion of the commit operation will happen at to determine why there is a unit of work already in
some point in the future, but there remains the existence. Move the MQBEGIN call to the appropriate
possibility that the outcome will be mixed. place in the application.
AIX, HP-UX, OS/2, Solaris, Windows. 2129 (X'0851')
Completion Code: MQCC_WARNING MQRC_ADAPTER_CONN_LOAD_ERROR
Programmer Response: Use the normal Explanation: On an MQCONN call, the connection
error-reporting mechanisms to determine whether the handling module (CSQBCON for batch and
outcome was mixed. If it was, take appropriate action CSQQCONN for IMS) could not be loaded, so the
to resynchronize the resources. adapter could not link to it.
This reason code does not prevent the application This reason code occurs only on z/OS.
initiating further units of work. Completion Code: MQCC_FAILED

Programmer Response: Ensure that the correct library application program execution JCL, and in the
concatenation has been specified in the batch queue-manager startup JCL.
application program execution JCL, and in the
queue-manager startup JCL.
2134 (X'0856') MQRC_BO_ERROR
Explanation: On an MQBEGIN call, the begin-options
2130 (X'0852')
structure MQBO is not valid, for one of the following
MQRC_ADAPTER_SERV_LOAD_ERROR
reasons:
Explanation: On an MQI call, the batch adapter could v The StrucId field is not MQBO_STRUC_ID.
not load the API service module CSQBSRV, and so v The Version field is not MQBO_VERSION_1.
could not link to it. v The parameter pointer is not valid. (It is not always
Completion Code: MQCC_FAILED v The queue manager cannot copy the changed
Programmer Response: Ensure that the correct library is successful. This can occur, for example, if the
concatenation has been specified in the batch pointer points to read-only storage.
application program execution JCL, and in the
queue-manager startup JCL.
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
2131 (X'0853') MQRC_ADAPTER_DEFS_ERROR WebSphere MQ clients connected to these systems.
Explanation: On an MQCONN call, the subsystem Completion Code: MQCC_FAILED
definition module (CSQBDEFV for batch and
CSQQDEFV for IMS) does not contain the required
MQBO structure are set correctly.
control block identifier.
2135 (X'0857') MQRC_DH_ERROR
Programmer Response: Check your library but the message data contains an MQDH structure that
concatenation. If this is correct, check that the is not valid. Possible errors include the following:
CSQBDEFV or CSQQDEFV module contains the v The StrucId field is not MQDH_STRUC_ID.
required subsystem ID. v The Version field is not MQDH_VERSION_1.
v The StrucLength field specifies a value that is too
small to include the structure plus the arrays of
2132 (X'0854') MQOR and MQPMR records.
MQRC_ADAPTER_DEFS_LOAD_ERROR v The CodedCharSetId field is zero, or a negative value
Explanation: On an MQCONN call, the subsystem that is not valid.
definition module (CSQBDEFV for batch and v The BufferLength parameter of the call has a value
CSQQDEFV for IMS) could not be loaded. that is too small to accommodate the structure (the
structure extends beyond the end of the message).
Completion Code: MQCC_FAILED This reason code occurs in the following environments:
Programmer Response: Ensure that the correct library WebSphere MQ clients connected to these systems.
concatenation has been specified in the application
program execution JCL, and in the queue-manager Completion Code: MQCC_FAILED
startup JCL. Programmer Response: Check that the fields in the
structure are set correctly. Ensure that the application
2133 (X'0855') sets the CodedCharSetId field to a valid value (note:
MQRC_ADAPTER_CONV_LOAD_ERROR MQCCSI_DEFAULT, MQCCSI_EMBEDDED,
MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not
Explanation: On an MQGET call, the adapter (batch or valid in this field).
IMS) could not load the data conversion services
modules.
2136 (X'0858') MQRC_MULTIPLE_REASONS
Explanation: An MQOPEN, MQPUT or MQPUT1 call
Completion Code: MQCC_FAILED was issued to open a distribution list or put a message
Programmer Response: Ensure that the correct library to a distribution list, but the result of the call was not
concatenation has been specified in the batch

the same for all of the destinations in the list. One of records are provided by the application on the call to
the following applies: enable the error(s) to be determined.
v The call succeeded for some of the destinations but
not others. The completion code is
2138 (X'085A')
MQCC_WARNING in this case.
MQRC_ADAPTER_DISC_LOAD_ERROR
v The call failed for all of the destinations, but for
differing reasons. The completion code is Explanation: On an MQDISC call, the disconnect
MQCC_FAILED in this case. handling module (CSQBDSC for batch and CSQQDISC
for IMS) could not be loaded, so the adapter could not
This reason code occurs in the following environments: link to it.
WebSphere MQ clients connected to these systems.
MQCC_FAILED Programmer Response: Ensure that the correct library
concatenation has been specified in the application
Programmer Response: Examine the MQRR response
program execution JCL, and in the queue-manager
records to identify the destinations for which the call
startup JCL. Any uncommitted changes in a unit of
failed, and the reason for the failure. Ensure that
work should be backed out. A unit of work that is
sufficient response records are provided by the
coordinated by the queue manager is backed out
application on the call to enable the error(s) to be
automatically.
determined. For the MQPUT1 call, the response records
must be specified using the MQOD structure, and not
the MQPMO structure. 2139 (X'085B') MQRC_CNO_ERROR
Explanation: On an MQCONNX call, the
2137 (X'0859') MQRC_OPEN_FAILED connect-options structure MQCNO is not valid, for one
of the following reasons:
Explanation: A queue or other MQ object could not be
v The StrucId field is not MQCNO_STRUC_ID.
opened successfully, for one of the following reasons:
v The Version field specifies a value that is not valid
v An MQCONN or MQCONNX call was issued, but
or not supported.
the queue manager was unable to open an object that
is used internally by the queue manager. As a result,
processing cannot continue. The error log will
contain the name of the object that could not be
opened.
v An MQPUT call was issued to put a message to a
is successful. This can occur, for example, if the
distribution list, but the message could not be sent to
parameter pointer points to read-only storage.
the destination to which this reason code applies
because that destination was not opened successfully
by the MQOPEN call. This reason occurs only in the This reason code occurs in the following environments:
Reason field of the MQRR response record. AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
plus WebSphere MQ clients connected to these systems.
This reason code occurs in the following environments: Completion Code: MQCC_FAILED
WebSphere MQ clients connected to these systems. Programmer Response: Ensure that input fields in the
MQCNO structure are set correctly.
Programmer Response: Do one of the following: 2140 (X'085C') MQRC_CICS_WAIT_FAILED
v If the error occurred on the MQCONN or Explanation: On any MQI call, the CICS adapter
MQCONNX call, ensure that the required objects issued an EXEC CICS WAIT request, but the request
exist by running the following command and then was rejected by CICS.
retrying the application:
STRMQM -c qmgr This reason code occurs only on z/OS.
where qmgr should be replaced by the name of the
queue manager. Programmer Response: Examine the CICS trace data
for actual response codes. The most likely cause is that
v If the error occurred on the MQPUT call, examine the task has been canceled by the operator or by the
the MQRR response records specified on the system.
MQOPEN call to determine the reason that the
queue failed to open. Ensure that sufficient response

always possible to detect parameter pointers that are

2141 (X'085D') MQRC_DLH_ERROR
not valid; if not detected, unpredictable results occur.)
This reason code can also occur on the MQGET call
but the message data contains an MQDLH structure
when the MQGMO_CONVERT option is specified. In
that is not valid. Possible errors include the following:
this case it indicates that the
v The StrucId field is not MQDLH_STRUC_ID.
MQRC_SOURCE_LENGTH_ERROR reason was
v The Version field is not MQDLH_VERSION_1.
returned by an MQXCNVC call issued by the data
v The CodedCharSetId field is zero, or a negative value
conversion exit.
that is not valid.
v The BufferLength parameter of the call has a value Completion Code: MQCC_WARNING or
that is too small to accommodate the structure (the MQCC_FAILED
Programmer Response: Specify a length that is zero or
greater. If the reason code occurs on the MQGET call,
check that the logic in the data-conversion exit is
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
correct.
2144 (X'0860') MQRC_TARGET_LENGTH_ERROR
Programmer Response: Check that the fields in the
Explanation: On the MQXCNVC call, the
TargetLength parameter is not valid for one of the
sets the CodedCharSetId field to a valid value (note:
following reasons:
MQCCSI_DEFAULT, MQCCSI_EMBEDDED,
v TargetLength is less than zero.
v The TargetLength parameter pointer is not valid. (It
valid in this field).
is not always possible to detect parameter pointers
that are not valid; if not detected, unpredictable
2142 (X'085E') MQRC_HEADER_ERROR results occur.)
v The MQDCC_FILL_TARGET_BUFFER option is
specified, but the value of TargetLength is such that
but the message data contains an MQ header structure
the target buffer cannot be filled completely with
valid characters. This can occur when TargetCCSID is
v The StrucId field is not valid.
a pure DBCS character set (such as UCS-2), but
v The Version field is not valid.
TargetLength specifies a length that is an odd
v The StrucLength field specifies a value that is too
number of bytes.
small.
that is not valid.
v The BufferLength parameter of the call has a value
that is too small to accommodate the structure (the
MQRC_TARGET_LENGTH_ERROR reason was
returned by an MQXCNVC call issued by the data
conversion exit.
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, Completion Code: MQCC_WARNING or
plus WebSphere MQ clients connected to these systems. MQCC_FAILED
Completion Code: MQCC_FAILED Programmer Response: Specify a length that is zero or
greater. If the MQDCC_FILL_TARGET_BUFFER option
is specified, and TargetCCSID is a pure DBCS character
set, ensure that TargetLength specifies a length that is a
multiple of two.
MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not If the reason code occurs on the MQGET call, check
valid in this field). that the logic in the data-conversion exit is correct.
2143 (X'085F') MQRC_SOURCE_LENGTH_ERROR 2145 (X'0861') MQRC_SOURCE_BUFFER_ERROR

Explanation: On the MQXCNVC call, the Explanation: On the MQXCNVC call, the
SourceLength parameter specifies a length that is less SourceBuffer parameter pointer is not valid, or points
than zero or not consistent with the string’s character to storage that cannot be accessed for the entire length
set or content (for example, the character set is a specified by SourceLength. (It is not always possible to
double-byte character set, but the length is not a detect parameter pointers that are not valid; if not
multiple of two). This reason also occurs if the detected, unpredictable results occur.)
SourceLength parameter pointer is not valid. (It is not


2149 (X'0865') MQRC_PCF_ERROR
this case it indicates that the Explanation: An MQPUT or MQPUT1 call was issued
MQRC_SOURCE_BUFFER_ERROR reason was to put a message containing PCF data, but the length of
returned by an MQXCNVC call issued by the data the message does not equal the sum of the lengths of
conversion exit. the PCF structures present in the message. This can
occur for messages with the following format names:
MQFMT_ADMIN
MQCC_FAILED
MQFMT_EVENT
Programmer Response: Specify a valid buffer. If the MQFMT_PCF
reason code occurs on the MQGET call, check that the
logic in the data-conversion exit is correct. This reason code occurs in the following environments:
2146 (X'0862') MQRC_TARGET_BUFFER_ERROR
Explanation: On the MQXCNVC call, the
TargetBuffer parameter pointer is not valid, or points Programmer Response: Ensure that the length of the
to read-only storage, or to storage that cannot be message specified on the MQPUT or MQPUT1 call
accessed for the entire length specified by equals the sum of the lengths of the PCF structures
TargetLength. (It is not always possible to detect contained within the message data.
2150 (X'0866') MQRC_DBCS_ERROR
Explanation: An error was encountered attempting to
convert a double-byte character set (DBCS) string. This
can occur in the following cases:
MQRC_TARGET_BUFFER_ERROR reason was returned
by an MQXCNVC call issued by the data conversion v On the MQXCNVC call, when the SourceCCSID
exit. parameter specifies the coded character-set identifier
of a double-byte character set, but the SourceBuffer
Completion Code: MQCC_WARNING or parameter does not contain a valid DBCS string. This
MQCC_FAILED may be because the string contains characters that
Programmer Response: Specify a valid buffer. If the are not valid DBCS characters, or because the string
reason code occurs on the MQGET call, check that the is a mixed SBCS/DBCS string and the
logic in the data-conversion exit is correct. shift-out/shift-in characters are not correctly paired.
The completion code is MQCC_FAILED in this case.
v On the MQGET call, when the MQGMO_CONVERT
2148 (X'0864') MQRC_IIH_ERROR
option is specified. In this case it indicates that the
Explanation: An MQPUT or MQPUT1 call was issued, MQRC_DBCS_ERROR reason code was returned by
but the message data contains an MQIIH structure that an MQXCNVC call issued by the data conversion
is not valid. Possible errors include the following: exit. The completion code is MQCC_WARNING in
v The StrucId field is not MQIIH_STRUC_ID. this case.
v The Version field is not MQIIH_VERSION_1.
v The StrucLength field is not MQIIH_LENGTH_1.
MQCC_FAILED
that is too small to accommodate the structure (the Programmer Response: Specify a valid string.
If the reason code occurs on the MQGET call, check
that the data in the message is valid, and that the logic
in the data-conversion exit is correct.
2152 (X'0868') MQRC_OBJECT_NAME_ERROR
issued to open a distribution list (that is, the
structure are set correctly.
RecsPresent field in MQOD is greater than zero), but
the ObjectName field is neither blank nor the null string.

Completion Code: MQCC_FAILED This reason code occurs in the following environments:
Programmer Response: If it is intended to open a
distribution list, set the ObjectName field to blanks or
the null string. If it is not intended to open a Completion Code: MQCC_FAILED
distribution list, set the RecsPresent field to zero.
Programmer Response: Ensure that one of
ObjectRecOffset and ObjectRecPtr is zero and the
2153 (X'0869') other nonzero. Ensure that the field used points to
MQRC_OBJECT_Q_MGR_NAME_ERROR accessible storage.
issued to open a distribution list (that is, the 2156 (X'086C')
RecsPresent field in MQOD is greater than zero), but MQRC_RESPONSE_RECORDS_ERROR
the ObjectQMgrName field is neither blank nor the null
string.
This reason code occurs in the following environments: RecsPresent field in MQOD is greater than zero), but
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus the MQRR response records are not specified correctly.
WebSphere MQ clients connected to these systems. One of the following applies:
v ResponseRecOffset is not zero and ResponseRecPtr is
not zero and not the null pointer.
Programmer Response: If it is intended to open a v ResponseRecPtr is not a valid pointer.
distribution list, set the ObjectQMgrName field to blanks v ResponseRecPtr or ResponseRecOffset points to
or the null string. If it is not intended to open a storage that is not accessible.
distribution list, set the RecsPresent field to zero.
2154 (X'086A') MQRC_RECS_PRESENT_ERROR
issued, but the call failed for one of the following
reasons: Programmer Response: Ensure that at least one of
v RecsPresent in MQOD is less than zero. ResponseRecOffset and ResponseRecPtr is zero. Ensure
v ObjectType in MQOD is not MQOT_Q, and that the field used points to accessible storage.
RecsPresent is not zero. RecsPresent must be zero if
the object being opened is not a queue.
2157 (X'086D') MQRC_ASID_MISMATCH
This reason code occurs in the following environments: Explanation: On any MQI call, the caller’s primary
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus ASID was found to be different from the home ASID.
Programmer Response: If it is intended to open a
Programmer Response: Correct the application (MQI
distribution list, set the ObjectType field to MQOT_Q
calls cannot be issued in cross-memory mode). Any
and RecsPresent to the number of destinations in the
uncommitted changes in a unit of work should be
list. If it is not intended to open a distribution list, set
the RecsPresent field to zero.
queue manager is backed out automatically.
2155 (X'086B') MQRC_OBJECT_RECORDS_ERROR

2158 (X'086E')
Explanation: An MQOPEN or MQPUT1 call was MQRC_PMO_RECORD_FLAGS_ERROR
Explanation: An MQPUT or MQPUT1 call was issued
RecsPresent field in MQOD is greater than zero), but
to put a message, but the PutMsgRecFields field in the
the MQOR object records are not specified correctly.
MQPMO structure is not valid, for one of the following
One of the following applies:
reasons:
v ObjectRecOffset is zero and ObjectRecPtr is zero or
v The field contains flags that are not valid.
the null pointer.
v The message is being put to a distribution list, and
v ObjectRecOffset is not zero and ObjectRecPtr is not
put message records have been provided (that is,
zero and not the null pointer.
RecsPresent is greater than zero, and one of
v ObjectRecPtr is not a valid pointer.
PutMsgRecOffset or PutMsgRecPtr is nonzero), but
v ObjectRecPtr or ObjectRecOffset points to storage
PutMsgRecFields has the value MQPMRF_NONE.
that is not accessible.

v MQPMRF_ACCOUNTING_TOKEN is specified This reason code occurs only on z/OS.

without either MQPMO_SET_IDENTITY_CONTEXT
or MQPMO_SET_ALL_CONTEXT.
Programmer Response: Ensure that the naming
This reason code occurs in the following environments: conventions used in different systems that might
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus connect to the queue manager do not conflict.
Completion Code: MQCC_FAILED 2161 (X'0871') MQRC_Q_MGR_QUIESCING
Programmer Response: Ensure that PutMsgRecFields Explanation: An MQI call was issued, but the call
is set with the appropriate MQPMRF_* flags to indicate failed because the queue manager is quiescing
which fields are present in the put message records. If (preparing to shut down).
MQPMRF_ACCOUNTING_TOKEN is specified, ensure
When the queue manager is quiescing, the MQOPEN,
that either MQPMO_SET_IDENTITY_CONTEXT or
MQPUT, MQPUT1, and MQGET calls can still
MQPMO_SET_ALL_CONTEXT is also specified.
complete successfully, but the application can request
Alternatively, set both PutMsgRecOffset and
that they fail by specifying the appropriate option on
PutMsgRecPtr to zero.
the call:
v MQOO_FAIL_IF_QUIESCING on MQOPEN
2159 (X'086F') v MQPMO_FAIL_IF_QUIESCING on MQPUT or
MQRC_PUT_MSG_RECORDS_ERROR MQPUT1
v MQGMO_FAIL_IF_QUIESCING on MQGET
to put a message to a distribution list, but the MQPMR Specifying these options enables the application to
put message records are not specified correctly. One of become aware that the queue manager is preparing to
the following applies: shut down.
v PutMsgRecOffset is not zero and PutMsgRecPtr is not v On z/OS:
zero and not the null pointer. – For batch applications, this reason can be returned
v PutMsgRecPtr is not a valid pointer. to applications running in LPARs that do not have
v PutMsgRecPtr or PutMsgRecOffset points to storage a queue manager installed.
that is not accessible. – For CICS applications, this reason can be returned
when no connection was established.
v On i5/OS for applications running in compatibility
mode, this reason can be returned when no
connection was established.
Programmer Response: Ensure that at least one of
Programmer Response: The application should tidy
PutMsgRecOffset and PutMsgRecPtr is zero. Ensure that
up and end. If the application specified the
the field used points to accessible storage.
MQOO_FAIL_IF_QUIESCING,
MQPMO_FAIL_IF_QUIESCING, or
2160 (X'0870') MQRC_CONN_ID_IN_USE MQGMO_FAIL_IF_QUIESCING option on the failing
call, the relevant option can be removed and the call
Explanation: On an MQCONN call, the connection reissued. By omitting these options, the application can
identifier assigned by the queue manager to the continue working in order to complete and commit the
connection between a CICS or IMS allied address space current unit of work, but the application should not
and the queue manager conflicts with the connection start a new unit of work.
identifier of another connected CICS or IMS system.
The connection identifier assigned is as follows:
v For CICS, the applid 2162 (X'0872') MQRC_Q_MGR_STOPPING
v For IMS, the IMSID parameter on the IMSCTRL
Explanation: An MQI call was issued, but the call
(sysgen) macro, or the IMSID parameter on the
failed because the queue manager is shutting down. If
execution parameter (EXEC card in IMS control
the call was an MQGET call with the MQGMO_WAIT
region JCL)
option, the wait has been canceled. No more MQI calls
v For batch, the job name
can be issued.
v For TSO, the user ID
For MQ client applications, it is possible that the call
A conflict arises only if there are two CICS systems, did complete successfully, even though this reason code
two IMS systems, or one each of CICS and IMS, having is returned with a CompCode of MQCC_FAILED.
the same connection identifiers. Batch and TSO v On z/OS, the MQRC_CONNECTION_BROKEN
connections need not have unique identifiers. reason may be returned instead if, as a result of

system scheduling factors, the queue manager shuts concatenation has been specified, and that the API
down before the call completes. crossing exit module is executable and correctly named.
Any uncommitted changes in a unit of work should be
Programmer Response: The application should tidy queue manager is backed out automatically.
up and end. If the application is in the middle of a unit
of work coordinated by an external unit-of-work
2184 (X'0888') MQRC_REMOTE_Q_NAME_ERROR
coordinator, the application should issue the
appropriate call to back out the unit of work. Any unit Explanation: On an MQOPEN or MQPUT1 call, one
of work that is coordinated by the queue manager is of the following occurred:
backed out automatically. v A local definition of a remote queue (or an alias to
one) was specified, but the RemoteQName attribute in
the remote queue definition is entirely blank. Note
2163 (X'0873') MQRC_DUPLICATE_RECOV_COORD
that this error occurs even if the XmitQName in the
Explanation: On an MQCONN or MQCONNX call, a definition is not blank.
recovery coordinator already exists for the connection v The ObjectQMgrName field in the object descriptor is
name specified on the connection call issued by the not blank and not the name of the local queue
adapter. manager, but the ObjectName field is blank.
A conflict arises only if there are two CICS systems, Completion Code: MQCC_FAILED
two IMS systems, or one each of CICS and IMS, having
Programmer Response: Alter the local definition of
the same connection identifiers. Batch and TSO
the remote queue and supply a valid remote queue
connections need not have unique identifiers.
name, or supply a nonblank ObjectName in the object
This reason code occurs only on z/OS. descriptor, as appropriate.
2185 (X'0889')
Programmer Response: Ensure that the naming MQRC_INCONSISTENT_PERSISTENCE
conventions used in different systems that might
connect to the queue manager do not conflict. Explanation: An MQPUT call was issued to put a
message in a group or a segment of a logical message,
but the value specified or defaulted for the Persistence
2173 (X'087D') MQRC_PMO_ERROR field in MQMD is not consistent with the current group
Explanation: On an MQPUT or MQPUT1 call, the and segment information retained by the queue
MQPMO structure is not valid, for one of the following manager for the queue handle. All messages in a group
reasons: and all segments in a logical message must have the
v The StrucId field is not MQPMO_STRUC_ID. same value for persistence, that is, all must be
v The Version field specifies a value that is not valid persistent, or all must be nonpersistent.
or not supported. If the current call specifies
v The parameter pointer is not valid. (It is not always MQPMO_LOGICAL_ORDER, the call fails. If the
possible to detect parameter pointers that are not current call does not specify
valid; if not detected, unpredictable results occur.) MQPMO_LOGICAL_ORDER, but the previous MQPUT
v The queue manager cannot copy the changed call for the queue handle did, the call succeeds with
structure to application storage, even though the call completion code MQCC_WARNING.
is successful. This can occur, for example, if the
pointer points to read-only storage. This reason code occurs in the following environments:
Completion Code: MQCC_FAILED plus WebSphere MQ clients connected to these systems.
Programmer Response: Ensure that input fields in the Completion Code: MQCC_WARNING or
MQPMO structure are set correctly. MQCC_FAILED
Programmer Response: Modify the application to
2183 (X'0887') MQRC_API_EXIT_LOAD_ERROR ensure that the same value of persistence is used for all
Explanation: The API crossing exit module could not messages in the group, or all segments of the logical
be linked. If this reason is returned when the API message.
crossing exit is invoked after the call has been executed,
the call itself may have executed correctly. 2186 (X'088A') MQRC_GMO_ERROR
This reason code occurs only on z/OS. Explanation: On an MQGET call, the MQGMO
Completion Code: MQCC_FAILED structure is not valid, for one of the following reasons:
v The StrucId field is not MQGMO_STRUC_ID.
Programmer Response: Ensure that the correct library

v The Version field specifies a value that is not valid Completion Code: MQCC_FAILED
or not supported.
Programmer Response: Check that the repository
manager is operating and that the queue and channel
definitions are correct.
structure to application storage, even though the call 2190 (X'088E')
is successful. This can occur, for example, if the MQRC_CONVERTED_STRING_TOO_BIG
pointer points to read-only storage.
Completion Code: MQCC_FAILED MQGMO_CONVERT option included in the
GetMsgOpts parameter, a string in a fixed-length field in
the message expanded during data conversion and
MQGMO structure are set correctly.
exceeded the size of the field. When this happens, the
queue manager tries discarding trailing blank
2187 (X'088B') characters and characters following the first null
MQRC_CICS_BRIDGE_RESTRICTION character in order to make the string fit, but in this case
there were insufficient characters that could be
Explanation: It is not permitted to issue MQI calls
discarded.
from user transactions that are run in an
MQ/CICS-bridge environment where the bridge exit This reason code can also occur for messages with a
also issues MQI calls. The MQI call fails. If this occurs format name of MQFMT_IMS_VAR_STRING. When
in the bridge exit, it will result in a transaction abend. this happens, it indicates that the IMS variable string
If it occurs in the user transaction, this may result in a expanded such that its length exceeded the capacity of
transaction abend. the 2-byte binary length field contained within the
structure of the IMS variable string. (The queue
manager never discards trailing blanks in an IMS
Completion Code: MQCC_FAILED variable string.)
Programmer Response: The transaction cannot be run The message is returned unconverted, with the
using the MQ/CICS bridge. Refer to the appropriate CompCode parameter of the MQGET call set to
CICS manual for information about restrictions in the MQCC_WARNING. If the message consists of several
MQ/CICS bridge environment. parts, each of which is described by its own
character-set and encoding fields (for example, a
message with format name
2188 (X'088C') MQFMT_DEAD_LETTER_HEADER), some parts may
MQRC_STOPPED_BY_CLUSTER_EXIT be converted and other parts not converted. However,
Explanation: An MQOPEN, MQPUT, or MQPUT1 call the values returned in the various character-set and
was issued to open or put a message on a cluster encoding fields always correctly describe the relevant
queue, but the cluster workload exit rejected the call. message data.
This reason code occurs in the following environments: This reason code does not occur if the string could be
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, made to fit by discarding trailing blank characters.
plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING
Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the
Programmer Response: Check the cluster workload message contain the correct values, and that the
exit to ensure that it has been written correctly. character-set identifiers specified by the sender and
Determine why it rejected the call and correct the receiver of the message are correct. If they are, the
problem. layout of the data in the message must be modified to
increase the lengths of the field(s) so that there is
sufficient space to allow the string(s) to expand when
2189 (X'088D') converted.
MQRC_CLUSTER_RESOLUTION_ERROR
Explanation: An MQOPEN, MQPUT, or MQPUT1 call 2191 (X'088F') MQRC_TMC_ERROR
was issued to open or put a message on a cluster
queue, but the queue definition could not be resolved Explanation: An MQPUT or MQPUT1 call was issued,
correctly because a response was required from the but the message data contains an MQTMC2 structure
repository manager but none was available. that is not valid. Possible errors include the following:
v The StrucId field is not MQTMC_STRUC_ID.
This reason code occurs in the following environments: v The Version field is not MQTMC_VERSION_2.

v The BufferLength parameter of the call has a value This reason code occurs only on z/OS.
Programmer Response: Check that the storage class
This reason code occurs in the following environments: for the queue maps to a valid page set using the
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus DISPLAY Q(xx) STGCLASS, DISPLAY STGCLASS(xx),
WebSphere MQ clients connected to these systems. and DISPLAY USAGE PSID commands. If you are
unable to resolve the problem, notify the system
programmer who should:
Programmer Response: Check that the fields in the v Collect the following diagnostic information:
structure are set correctly. – A description of the actions that led to the error
– A listing of the application program being run at
2192 (X'0890') MQRC_PAGESET_FULL the time of the error
– Details of the page sets defined for use by the
Explanation: Former name for queue manager
MQRC_STORAGE_MEDIUM_FULL. v Attempt to re-create the problem, and take a system
dump immediately after the error occurs
2192 (X'0890') MQRC_STORAGE_MEDIUM_FULL v Contact your IBM Support Center
Explanation: An MQI call or command was issued to
operate on an object, but the call failed because the 2194 (X'0892')
external storage medium is full. One of the following MQRC_NAME_NOT_VALID_FOR_TYPE
applies:
v A page-set data set is full (nonshared queues only). Explanation: An MQOPEN call was issued to open
v A coupling-facility structure is full (shared queues the queue manager definition, but the ObjectName field
only). in the ObjDesc parameter is not blank.
Programmer Response: Ensure that the ObjectName
Completion Code: MQCC_FAILED field is set to blanks.
Programmer Response: Check which queues contain
messages and look for applications that might be filling 2195 (X'0893') MQRC_UNEXPECTED_ERROR
the queues unintentionally. Be aware that the queue
that has caused the page set or coupling-facility Explanation: The call was rejected because an
structure to become full is not necessarily the queue unexpected error occurred.
referenced by the MQI call that returned Completion Code: MQCC_FAILED
MQRC_STORAGE_MEDIUM_FULL.
Programmer Response: Check the application’s
Check that all of the usual server applications are parameter list to ensure, for example, that the correct
operating correctly and processing the messages on the number of parameters was passed, and that data
queues. pointers and storage keys are valid. If the problem
If the applications and servers are operating correctly, cannot be resolved, contact your system programmer.
increase the number of server applications to cope with v On z/OS, check whether any information has been
the message load, or request the system programmer to displayed on the console. If this error occurs on an
increase the size of the page-set data sets. MQCONN or MQCONNX call, check that the
subsystem named is an active MQ subsystem. In
particular, check that it is not a DB2™ subsystem. If
2193 (X'0891') MQRC_PAGESET_ERROR the problem cannot be resolved, rerun the
application with a CSQSNAP DD card (if you have
Explanation: An error was encountered with the page
not already got a dump) and send the resulting
set while attempting to access it for a locally defined
dump to IBM.
queue. This could be because the queue is on a page
v On OS/2 and i5/OS, consult the FFST record to
set that does not exist. A console message is issued that
obtain more detail about the problem.
tells you the number of the page set in error. For
v On HP OpenVMS, HP NonStop Server, and UNIX
example if the error occurred in the TEST job, and your
systems, consult the FDC file to obtain more detail
user identifier is ABCDEFG, the message is:
about the problem.
CSQI041I CSQIALLC JOB TEST USER ABCDEFG HAD ERROR ACCESSING PAGE SET 27
If this reason code occurs while attempting to delete a

dynamic queue with MQCLOSE, the dynamic queue
has not been deleted.

v Specify a local transmission queue as the value of the

2196 (X'0894') MQRC_UNKNOWN_XMIT_Q
DefXmitQName queue-manager attribute.
Explanation: On an MQOPEN or MQPUT1 call, a
message is to be sent to a remote queue manager. The See the WebSphere MQ Application Programming Guide
ObjectName or the ObjectQMgrName in the object for more information.
descriptor specifies the name of a local definition of a
remote queue (in the latter case queue-manager aliasing
is being used), but the XmitQName attribute of the 2199 (X'0897')
definition is not blank and not the name of a MQRC_DEF_XMIT_Q_USAGE_ERROR
locally-defined queue. Explanation: An MQOPEN or MQPUT1 call was
Completion Code: MQCC_FAILED issued specifying a remote queue as the destination.
Either a local definition of the remote queue was
Programmer Response: Check the values specified for specified, or a queue-manager alias was being resolved,
ObjectName and ObjectQMgrName. If these are correct, but in either case the XmitQName attribute in the local
check the queue definitions. For more information on definition is blank.
transmission queues, see the WebSphere MQ Application
Programming Guide. Because there is no transmission queue defined with
the same name as the destination queue manager, the
local queue manager has attempted to use the default
2197 (X'0895') MQRC_UNKNOWN_DEF_XMIT_Q transmission queue. However, the queue defined by the
DefXmitQName queue-manager attribute does not have a
Usage attribute of MQUS_TRANSMISSION.
issued specifying a remote queue as the destination. If
a local definition of the remote queue was specified, or Completion Code: MQCC_FAILED
if a queue-manager alias is being resolved, the
XmitQName attribute in the local definition is blank. Programmer Response: Do one of the following:
Because there is no queue defined with the same name XmitQName attribute in the local definition of the
as the destination queue manager, the queue manager remote queue.
has attempted to use the default transmission queue. v Define a local transmission queue with a name that
However, the name defined by the DefXmitQName is the same as that of the remote queue manager.
queue-manager attribute is not the name of a v Specify a different local transmission queue as the
locally-defined queue. value of the DefXmitQName queue-manager attribute.
v Change the Usage attribute of the DefXmitQName
queue to MQUS_TRANSMISSION.
Programmer Response: Correct the queue definitions,
or the queue-manager attribute. See the WebSphere MQ See the WebSphere MQ Application Programming Guide
Application Programming Guide for more information. for more information.
2198 (X'0896') MQRC_DEF_XMIT_Q_TYPE_ERROR 2201 (X'0899') MQRC_NAME_IN_USE

Explanation: An MQOPEN or MQPUT1 call was Explanation: An MQOPEN call was issued to create a
issued specifying a remote queue as the destination. dynamic queue, but a queue with the same name as the
Either a local definition of the remote queue was dynamic queue already exists. The existing queue is
specified, or a queue-manager alias was being resolved, one that is logically deleted, but for which there are
but in either case the XmitQName attribute in the local still one or more open handles. For more information,
definition is blank. see the description of MQCLOSE in the WebSphere MQ
Application Programming Guide.
Because there is no transmission queue defined with
the same name as the destination queue manager, the This reason code occurs only on z/OS.
local queue manager has attempted to use the default
transmission queue. However, although there is a Completion Code: MQCC_FAILED
queue defined by the DefXmitQName queue-manager Programmer Response: Either ensure that all handles
attribute, it is not a local queue. for the previous dynamic queue are closed, or ensure
Completion Code: MQCC_FAILED that the name of the new queue is unique; see the
description for reason code
Programmer Response: Do one of the following: MQRC_OBJECT_ALREADY_EXISTS.
XmitQName attribute in the local definition of the
remote queue.
v Define a local transmission queue with a name that
is the same as that of the remote queue manager.


2202 (X'089A') MQRC_CONNECTION_QUIESCING
Programmer Response: The application should tidy
1 Explanation: This reason code is issued when the
up and terminate. Any uncommitted changes in a unit
1 connection to the queue manager is in quiescing state,
of work should be backed out. A unit of work that is
1 and an application issues one of the following calls:
coordinated by the queue manager is backed out
1 v MQCONN or MQCONNX
automatically.
1 v MQOPEN, with no connection established, or with
1 MQOO_FAIL_IF_QUIESCING included in the
1 Options parameter 2206 (X'089E') MQRC_MSG_ID_ERROR
1 v MQGET, with MQGMO_FAIL_IF_QUIESCING
1 included in the Options field of the GetMsgOpts Explanation: An MQGET call was issued to retrieve a
1 parameter message using the message identifier as a selection
1 v MQPUT or MQPUT1, with criterion, but the call failed because selection by
1 MQPMO_FAIL_IF_QUIESCING included in the message identifier is not supported on this queue.
1 Options field of the PutMsgOpts parameter v On z/OS, the queue is a shared queue, but the
IndexType queue attribute does not have an
1 MQRC_CONNECTION_QUIESCING is also issued by appropriate value:
1 the message channel agent (MCA) when the queue – If selection is by message identifier alone,
1 manager is in quiescing state. IndexType must have the value MQIT_MSG_ID.
– If selection is by message identifier and correlation
Completion Code: MQCC_FAILED identifier combined, IndexType must have the
Programmer Response: The application should tidy value MQIT_MSG_ID or MQIT_CORREL_ID.
up and terminate. Any uncommitted changes in a unit v On HP NonStop Server, a key file is required but has
of work should be backed out. not been defined.
2203 (X'089B') MQRC_CONNECTION_STOPPING
Programmer Response: Do one of the following:
1 Explanation: This reason code is issued when the v Modify the application so that it does not use
1 connection to the queue manager is shutting down, and selection by message identifier: set the MsgId field to
1 the application issues an MQI call. No more MQMI_NONE and do not specify
1 message-queuing calls can be issued. For the MQGET MQMO_MATCH_MSG_ID in MQGMO.
1 call, if the MQGMO_WAIT option was specified, the v On z/OS, change the IndexType queue attribute to
1 wait is canceled. MQIT_MSG_ID.
v On HP NonStop Server, define a key file.
1 Note that the MQRC_CONNECTION_BROKEN reason
1 may be returned instead if, as a result of system
1 scheduling factors, the queue manager shuts down 2207 (X'089F') MQRC_CORREL_ID_ERROR
1 before the call completes.
Explanation: An MQGET call was issued to retrieve a
1 MQRC_CONNECTION_STOPPING is also issued by message using the correlation identifier as a selection
1 the message channel agent (MCA) when the queue criterion, but the call failed because selection by
1 manager is shutting down. correlation identifier is not supported on this queue.
1 For MQ client applications, it is possible that the call v On z/OS, the queue is a shared queue, but the
1 did complete successfully, even though this reason code IndexType queue attribute does not have an
1 is returned with a CompCode of MQCC_FAILED. appropriate value:
– If selection is by correlation identifier alone,
Completion Code: MQCC_FAILED IndexType must have the value
Programmer Response: The application should tidy MQIT_CORREL_ID.
up and terminate. Any uncommitted changes in a unit – If selection is by correlation identifier and message
of work should be backed out. A unit of work that is identifier combined, IndexType must have the
coordinated by the queue manager is backed out value MQIT_CORREL_ID or MQIT_MSG_ID.
automatically. v On HP NonStop Server, a key file is required but has
not been defined.
2204 (X'089C') MQRC_ADAPTER_NOT_AVAILABLE Completion Code: MQCC_FAILED
Explanation: This is issued only for CICS applications, Programmer Response: Do one of the following:
if any call is issued and the CICS adapter (a Task v On z/OS, change the IndexType queue attribute to
Related User Exit) has been disabled, or has not been MQIT_CORREL_ID.
enabled. v On HP NonStop Server, define a key file.
v Modify the application so that it does not use
This reason code occurs only on z/OS. selection by correlation identifier: set the CorrelId

field to MQCI_NONE and do not specify

2217 (X'08A9')
MQMO_MATCH_CORREL_ID in MQGMO.
MQRC_CONNECTION_NOT_AUTHORIZED
Explanation: This reason code arises only for CICS
2208 (X'08A0') MQRC_FILE_SYSTEM_ERROR
applications. For these, connection to the queue
Explanation: An unexpected return code was received manager is done by the adapter. If that connection fails
from the file system, in attempting to perform an because the CICS subsystem is not authorized to
operation on a queue. connect to the queue manager, this reason code is
issued whenever an application running under that
This reason code occurs only on VSE/ESA. subsystem subsequently issues an MQI call.
Completion Code: MQCC_FAILED This reason code occurs only on z/OS.
Programmer Response: Check the file system Completion Code: MQCC_FAILED
definition for the queue that was being accessed. For a
VSAM file, check that the control interval is large Programmer Response: Ensure that the subsystem is
enough for the maximum message length allowed for authorized to connect to the queue manager.
the queue.
2218 (X'08AA')
2209 (X'08A1') MQRC_NO_MSG_LOCKED MQRC_MSG_TOO_BIG_FOR_CHANNEL
Explanation: An MQGET call was issued with the Explanation: A message was put to a remote queue,
MQGMO_UNLOCK option, but no message was but the message is larger than the maximum message
currently locked. length allowed by the channel. This reason code is
returned in the Feedback field in the message descriptor
Completion Code: MQCC_WARNING of a report message.
Programmer Response: Check that a message was v On z/OS, this return code is issued only if you are
locked by an earlier MQGET call with the not using CICS for distributed queuing. Otherwise,
MQGMO_LOCK option for the same handle, and that MQRC_MSG_TOO_BIG_FOR_Q_MGR is issued.
no intervening call has caused the message to become
unlocked. Completion Code: MQCC_FAILED
Programmer Response: Check the channel definitions.
1 2210 (X'08A2') MQRC_SOAP_DOTNET_ERROR Increase the maximum message length that the channel
can accept, or break the message into several smaller
1 Explanation: An exception from the .NET messages.
1 environment (as opposed to WebSphere MQ .NET) has
1 been received and is included as an inner exception.
2219 (X'08AB') MQRC_CALL_IN_PROGRESS
Explanation: The application issued an MQI call
1 Programmer Response: Refer to the .NET whilst another MQI call was already being processed
1 documentation for details about the inner exception. for that connection. Only one call per application
1 Follow the corrective action recommended there. connection can be processed at a time.
Concurrent calls can arise when an application uses
1 2211 (X'08A3') MQRC_SOAP_AXIS_ERROR multiple threads, or when an exit is invoked as part of
the processing of an MQI call. For example, a
1 Explanation: An exception from the Axis environment
data-conversion exit invoked as part of the processing
1 has been received and is included as a chained
of the MQGET call may try to issue an MQI call.
1 exception.
v On z/OS, concurrent calls can arise only with batch
1 Completion Code: MQCC_FAILED or IMS applications; an example is when a subtask
ends while an MQI call is in progress (for example,
1 Programmer Response: Refer to the Axis an MQGET that is waiting), and there is an
1 documentation for details about the chained exception. end-of-task exit routine that issues another MQI call.
1 Follow the corrective action recommended there. v On OS/2 and Windows, concurrent calls can also
arise if an MQI call is issued in response to a user
1 2212 (X'08A4') MQRC_SOAP_URL_ERROR message while another MQI call is in progress.
v If the application is using multiple threads with
1 Explanation: The SOAP URL has been specified shared handles, MQRC_CALL_IN_PROGRESS occurs
1 incorrectly. when the handle specified on the call is already in
1 Completion Code: MQCC_FAILED use by another thread and
MQCNO_HANDLE_SHARE_NO_BLOCK was
1 Programmer Response: Correct the SOAP URL and specified on the MQCONNX call.
1 rerun.

2224 (X'08B0') MQRC_Q_DEPTH_HIGH
Programmer Response: Ensure that an MQI call
Explanation: An MQPUT or MQPUT1 call has caused
cannot be issued while another one is active. Do not
the queue depth to be incremented to or above the
issue MQI calls from within a data-conversion exit.
limit specified in the QDepthHighLimit attribute.
v On z/OS, if you want to provide a subtask to allow
an application that is waiting for a message to arrive Completion Code: MQCC_WARNING
to be canceled, wait for the message by using Programmer Response: None. This reason code is
MQGET with MQGMO_SET_SIGNAL, rather than only used to identify the corresponding event message.
MQGMO_WAIT.
2225 (X'08B1') MQRC_Q_DEPTH_LOW

2220 (X'08AC') MQRC_RMH_ERROR
Explanation: An MQGET call has caused the queue
Explanation: An MQPUT or MQPUT1 call was issued, depth to be decremented to or below the limit specified
but the message data contains an MQRMH structure in the QDepthLowLimit attribute.
v The StrucId field is not MQRMH_STRUC_ID. Completion Code: MQCC_WARNING
v The Version field is not MQRMH_VERSION_1. Programmer Response: None. This reason code is
v The StrucLength field specifies a value that is too only used to identify the corresponding event message.
small to include the structure plus the
variable-length data at the end of the structure.
v The CodedCharSetId field is zero, or a negative value 2226 (X'08B2')
that is not valid. MQRC_Q_SERVICE_INTERVAL_HIGH
Explanation: No successful gets or puts have been
detected within an interval that is greater than the limit
specified in the QServiceInterval attribute.
This reason code occurs in the following environments: Completion Code: MQCC_WARNING
Programmer Response: None. This reason code is
only used to identify the corresponding event message.
Programmer Response: Check that the fields in the 2227 (X'08B3') MQRC_Q_SERVICE_INTERVAL_OK
Explanation: A successful get has been detected
within an interval that is less than or equal to the limit
specified in the QServiceInterval attribute.
valid in this field). Completion Code: MQCC_WARNING
2222 (X'08AE') MQRC_Q_MGR_ACTIVE only used to identify the corresponding event message.
Explanation: This condition is detected when a queue
manager becomes active. 1 2228 (X'08B4')
v On z/OS, this event is not generated for the first 1 MQRC_RFH_HEADER_FIELD_ERROR
start of a queue manager, only on subsequent 1 Explanation: An expected RFH header field was not
restarts. 1 found or had an invalid value. If this error occurs in a
Completion Code: MQCC_WARNING 1 WebSphere MQ SOAP listener, the missing or
1 erroneous field is either the contentType field or the
Programmer Response: None. This reason code is 1 transportVersion field or both.
2223 (X'08AF') MQRC_Q_MGR_NOT_ACTIVE 1 Programmer Response: If this error occurs in a
1 WebSphere MQ SOAP listener, and you are using the
Explanation: This condition is detected when a queue 1 IBM-supplied sender, contact your IBM Support Center.
manager is requested to stop or quiesce. 1 If you are using a bespoke sender, check the associated
Completion Code: MQCC_WARNING 1 error message, and that the RFH2 section of the
1 SOAP/MQ request message contains all the mandatory
Programmer Response: None. This reason code is 1 fields, and that these fields have valid values.

Programmer Response: Examine the additional

1 2229 (X'08B5') MQRC_RAS_PROPERTY_ERROR
information returned in the event message to determine
1 Explanation: There is an error related to the RAS the reason for the failure.
1 property file. The file may be missing, it may be not
1 accessible, or the commands in the file may be
2235 (X'08BB') MQRC_CFH_ERROR
1 incorrect.
but the message data contains an MQCFH structure
1 Programmer Response: Look at the associated error that is not valid.
1 message, which will explain the error in detail. Correct
1 the error and retry.
2232 (X'08B8')
MQRC_UNIT_OF_WORK_NOT_STARTED
Explanation: An MQGET, MQPUT or MQPUT1 call
was issued to get or put a message within a unit of
work, but no TM/MP transaction had been started. If
MQGMO_NO_SYNCPOINT is not specified on 2236 (X'08BC') MQRC_CFIL_ERROR
MQGET, or MQPMO_NO_SYNCPOINT is not specified
on MQPUT or MQPUT1 (the default), the call requires Explanation: An MQPUT or MQPUT1 call was issued,
a unit of work. but the message data contains an MQCFIL or
MQRCFIL64 structure that is not valid.
Programmer Response: Ensure a TM/MP transaction AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
is available, or issue the MQGET call with the WebSphere MQ clients connected to these systems.
MQGMO_NO_SYNCPOINT option, or the MQPUT or
MQPUT1 call with the MQPMO_NO_SYNCPOINT Completion Code: MQCC_FAILED
option, which will cause a transaction to be started Programmer Response: Check that the fields in the
automatically. structure are set correctly.
2233 (X'08B9') MQRC_CHANNEL_AUTO_DEF_OK 2237 (X'08BD') MQRC_CFIN_ERROR

Explanation: This condition is detected when the Explanation: An MQPUT or MQPUT1 call was issued,
automatic definition of a channel is successful. The but the message data contains an MQCFIN or
channel is defined by the MCA. MQCFIN64 structure that is not valid.
This reason code occurs in the following environments: This reason code occurs in the following environments:
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
WebSphere MQ clients connected to these systems. plus WebSphere MQ clients connected to these systems.
Completion Code: MQCC_WARNING Completion Code: MQCC_FAILED
Programmer Response: None. This reason code is Programmer Response: Check that the fields in the
only used to identify the corresponding event message. structure are set correctly.
2234 (X'08BA') 2238 (X'08BE') MQRC_CFSL_ERROR

MQRC_CHANNEL_AUTO_DEF_ERROR
Explanation: This condition is detected when the but the message data contains an MQCFSL structure
automatic definition of a channel fails; this may be that is not valid.
because an error occurred during the definition process,
or because the channel automatic-definition exit This reason code occurs in the following environments:
inhibited the definition. Additional information is AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
returned in the event message indicating the reason for WebSphere MQ clients connected to these systems.
the failure. Completion Code: MQCC_FAILED
This reason code occurs in the following environments: Programmer Response: Check that the fields in the
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus structure are set correctly.

v On the MQPUT call, when the application specifies

2239 (X'08BF') MQRC_CFST_ERROR
MQPMO_LOGICAL_ORDER and attempts to put a
Explanation: An MQPUT or MQPUT1 call was issued, message that is not a segment, or that has a setting
but the message data contains an MQCFST structure for the MQMF_LAST_MSG_IN_GROUP flag that is
that is not valid. different from the previous message. The completion
code is MQCC_FAILED in this case.
v On the MQPUT call, when the application does not
specify MQPMO_LOGICAL_ORDER, but the
previous MQPUT call for the queue handle did
Completion Code: MQCC_FAILED specify MQPMO_LOGICAL_ORDER. The completion
code is MQCC_WARNING in this case.
Programmer Response: Check that the fields in the v On the MQGET call, when the application does not
structure are set correctly. specify MQGMO_LOGICAL_ORDER, but the
previous MQGET call for the queue handle did
2241 (X'08C1') MQRC_INCOMPLETE_GROUP specify MQGMO_LOGICAL_ORDER. The
completion code is MQCC_WARNING in this case.
Explanation: An operation was attempted on a queue v On the MQCLOSE call, when the application
using a queue handle that had an incomplete message attempts to close the queue that has the incomplete
group. This reason code can arise in the following logical message. The completion code is
situations: MQCC_WARNING in this case.
v On the MQPUT call, when the application specifies
MQPMO_LOGICAL_ORDER and attempts to put a This reason code occurs in the following environments:
message that is not in a group. The completion code AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
is MQCC_FAILED in this case. plus WebSphere MQ clients connected to these systems.
v On the MQPUT call, when the application does not
specify MQPMO_LOGICAL_ORDER, but the Completion Code: MQCC_WARNING or
previous MQPUT call for the queue handle did MQCC_FAILED
specify MQPMO_LOGICAL_ORDER. The completion
Programmer Response: If this reason code is expected,
code is MQCC_WARNING in this case.
no corrective action is required. Otherwise, ensure that
v On the MQGET call, when the application does not
the MQPUT call for the last segment specifies
specify MQGMO_LOGICAL_ORDER, but the
MQMF_LAST_SEGMENT.
previous MQGET call for the queue handle did
specify MQGMO_LOGICAL_ORDER. The
completion code is MQCC_WARNING in this case. 2243 (X'08C3') MQRC_INCONSISTENT_CCSIDS
v On the MQCLOSE call, when the application
Explanation: An MQGET call was issued specifying
attempts to close the queue that has the incomplete
the MQGMO_COMPLETE_MSG option, but the
message group. The completion code is
message to be retrieved consists of two or more
MQCC_WARNING in this case.
segments that have differing values for the
CodedCharSetId field in MQMD. This can arise when
If there is an incomplete logical message as well as an
the segments take different paths through the network,
incomplete message group, reason code
and some of those paths have MCA sender conversion
MQRC_INCOMPLETE_MSG is returned in preference
enabled. The call succeeds with a completion code of
to MQRC_INCOMPLETE_GROUP.
MQCC_WARNING, but only the first few segments
that have identical character-set identifiers are returned.
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, This reason code occurs in the following environments:
plus WebSphere MQ clients connected to these systems. AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
MQCC_FAILED Completion Code: MQCC_WARNING
Programmer Response: If this reason code is expected, Programmer Response: Remove the
no corrective action is required. Otherwise, ensure that MQGMO_COMPLETE_MSG option from the MQGET
the MQPUT call for the last message in the group call and retrieve the remaining message segments one
specifies MQMF_LAST_MSG_IN_GROUP. by one.
2242 (X'08C2') MQRC_INCOMPLETE_MSG 2244 (X'08C4')

MQRC_INCONSISTENT_ENCODINGS
Explanation: An operation was attempted on a queue
using a queue handle that had an incomplete logical Explanation: An MQGET call was issued specifying
message. This reason code can arise in the following the MQGMO_COMPLETE_MSG option, but the
situations: message to be retrieved consists of two or more

segments that have differing values for the Encoding

2246 (X'08C6')
field in MQMD. This can arise when the segments take
MQRC_INVALID_MSG_UNDER_CURSOR
different paths through the network, and some of those
paths have MCA sender conversion enabled. The call Explanation: An MQGET call was issued specifying
succeeds with a completion code of the MQGMO_COMPLETE_MSG option with either
MQCC_WARNING, but only the first few segments MQGMO_MSG_UNDER_CURSOR or
that have identical encodings are returned. MQGMO_BROWSE_MSG_UNDER_CURSOR, but the
message that is under the cursor has an MQMD with
an Offset field that is greater than zero. Because
MQGMO_COMPLETE_MSG was specified, the
message is not valid for retrieval.
Programmer Response: Remove the AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
MQGMO_COMPLETE_MSG option from the MQGET WebSphere MQ clients connected to these systems.
call and retrieve the remaining message segments one
by one.
Programmer Response: Reposition the browse cursor
so that it is located on a message whose Offset field in
2245 (X'08C5') MQRC_INCONSISTENT_UOW
MQMD is zero. Alternatively, remove the
Explanation: One of the following applies: MQGMO_COMPLETE_MSG option.
v An MQPUT call was issued to put a message in a
group or a segment of a logical message, but the 2247 (X'08C7') MQRC_MATCH_OPTIONS_ERROR
value specified or defaulted for the
MQPMO_SYNCPOINT option is not consistent with Explanation: An MQGET call was issued, but the
the current group and segment information retained value of the MatchOptions field in the GetMsgOpts
by the queue manager for the queue handle. parameter is not valid, for one of the following reasons:
If the current call specifies v An undefined option is specified.
MQPMO_LOGICAL_ORDER, the call fails. If the v All of the following are true:
current call does not specify – MQGMO_LOGICAL_ORDER is specified.
MQPMO_LOGICAL_ORDER, but the previous – There is a current message group or logical
MQPUT call for the queue handle did, the call message for the queue handle.
succeeds with completion code MQCC_WARNING. – Neither
v An MQGET call was issued to remove from the MQGMO_BROWSE_MSG_UNDER_CURSOR nor
queue a message in a group or a segment of a logical MQGMO_MSG_UNDER_CURSOR is specified.
message, but the value specified or defaulted for the – One or more of the MQMO_* options is specified.
MQGMO_SYNCPOINT option is not consistent with – The values of the fields in the MsgDesc parameter
the current group and segment information retained corresponding to the MQMO_* options specified,
by the queue manager for the queue handle. differ from the values of those fields in the
MQMD for the message to be returned next.
If the current call specifies
MQGMO_LOGICAL_ORDER, the call fails. If the v On z/OS, one or more of the options specified is not
current call does not specify valid for the index type of the queue.
MQGMO_LOGICAL_ORDER, but the previous
MQGET call for the queue handle did, the call This reason code occurs in the following environments:
succeeds with completion code MQCC_WARNING. AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
plus WebSphere MQ clients connected to these systems. Programmer Response: Ensure that only valid options
are specified for the field.
MQCC_FAILED
2248 (X'08C8') MQRC_MDE_ERROR
Programmer Response: Modify the application to
ensure that the same unit-of-work specification is used Explanation: An MQPUT or MQPUT1 call was issued,
for all messages in the group, or all segments of the but the message data contains an MQMDE structure
logical message. that is not valid. Possible errors include the following:
v The StrucId field is not MQMDE_STRUC_ID.
v The Version field is not MQMDE_VERSION_2.
v The StrucLength field is not MQMDE_LENGTH_2.


2250 (X'08CA')
that is not valid.
MQRC_MSG_SEQ_NUMBER_ERROR
that is too small to accommodate the structure (the Explanation: An MQGET, MQPUT, or MQPUT1 call
structure extends beyond the end of the message). was issued, but the value of the MsgSeqNumber field in
the MQMD or MQMDE structure is less than one or
This reason code occurs in the following environments: greater than 999 999 999.
This error can also occur on the MQPUT call if the
MsgSeqNumber field would have become greater than
Completion Code: MQCC_FAILED 999 999 999 as a result of the call.
Programmer Response: Check that the fields in the This reason code occurs in the following environments:
structure are set correctly. Ensure that the application AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
sets the CodedCharSetId field to a valid value (note: plus WebSphere MQ clients connected to these systems.
valid in this field). Programmer Response: Specify a value in the range 1
through 999 999 999. Do not attempt to create a
message group containing more than 999 999 999
2249 (X'08C9') MQRC_MSG_FLAGS_ERROR
messages.
but the MsgFlags field in the message descriptor
2251 (X'08CB') MQRC_OFFSET_ERROR
MQMD contains one or more message flags that are
not recognized by the local queue manager. The Explanation: An MQPUT or MQPUT1 call was issued,
message flags that cause this reason code to be but the value of the Offset field in the MQMD or
returned depend on the destination of the message; see MQMDE structure is less than zero or greater than
the description of REPORT in the WebSphere MQ 999 999 999.
Application Programming Guide for more details.
This error can also occur on the MQPUT call if the
This reason code can also occur in the Feedback field in Offset field would have become greater than
the MQMD of a report message, or in the Reason field 999 999 999 as a result of the call.
in the MQDLH structure of a message on the
dead-letter queue; in both cases it indicates that the
destination queue manager does not support one or
more of the message flags specified by the sender of
the message. Completion Code: MQCC_FAILED
This reason code occurs in the following environments: Programmer Response: Specify a value in the range 0
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, through 999 999 999. Do not attempt to create a
plus WebSphere MQ clients connected to these systems. message segment that would extend beyond an offset
of 999 999 999.
Programmer Response: Do the following:
2252 (X'08CC')
v Ensure that the MsgFlags field in the message
MQRC_ORIGINAL_LENGTH_ERROR
descriptor is initialized with a value when the
message descriptor is declared, or is assigned a value Explanation: An MQPUT or MQPUT1 call was issued
prior to the MQPUT or MQPUT1 call. Specify to put a report message that is a segment, but the
MQMF_NONE if no message flags are needed. OriginalLength field in the MQMD or MQMDE
v Ensure that the message flags specified are valid; see structure is either:
the MsgFlags field described in the description of v Less than the length of data in the message, or
MQMD in the WebSphere MQ Application v Less than one (for a segment that is not the last
Programming Guide for valid message flags. segment), or
v If multiple message flags are being set by adding the v Less than zero (for a segment that is the last
individual message flags together, ensure that the segment)
same message flag is not added twice.
v On z/OS, ensure that the message flags specified are This reason code occurs in the following environments:
valid for the index type of the queue; see the AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
description of the MsgFlags field in MQMD for plus WebSphere MQ clients connected to these systems.
further details.
Programmer Response: Specify a value that is greater

than zero. Zero is valid only for the last segment. plus WebSphere MQ clients connected to these systems.
2253 (X'08CD') MQRC_SEGMENT_LENGTH_ZERO
Programmer Response: Modify the application to pass
Explanation: An MQPUT or MQPUT1 call was issued a version-2 MQGMO. Check the application logic to
to put the first or an intermediate segment of a logical ensure that the Version field in MQGMO has been set
message, but the length of the application message data to MQGMO_VERSION_2. Alternatively, remove the
in the segment (excluding any MQ headers that may be option that requires the version-2 MQGMO.
present) is zero. The length must be at least one for the
first or intermediate segment.
2257 (X'08D1') MQRC_WRONG_MD_VERSION
Explanation: An MQGET, MQPUT, or MQPUT1 call
was issued specifying options that required an MQMD
with a version number not less than
Completion Code: MQCC_FAILED MQMD_VERSION_2, but the MQMD supplied did not
satisfy this condition.
Programmer Response: Check the application logic to
ensure that segments are put with a length of one or This reason code occurs in the following environments:
greater. Only the last segment of a logical message is AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
permitted to have a length of zero. plus WebSphere MQ clients connected to these systems.
2255 (X'08CF') MQRC_UOW_NOT_AVAILABLE
Programmer Response: Modify the application to pass
Explanation: An MQGET, MQPUT, or MQPUT1 call a version-2 MQMD. Check the application logic to
was issued to get or put a message outside a unit of ensure that the Version field in MQMD has been set to
work, but the options specified on the call required the MQMD_VERSION_2. Alternatively, remove the option
queue manager to process the call within a unit of that requires the version-2 MQMD.
work. Because there is already a user-defined unit of
work in existence, the queue manager was unable to
2258 (X'08D2') MQRC_GROUP_ID_ERROR
create a temporary unit of work for the duration of the
call. Explanation: An MQPUT or MQPUT1 call was issued
to put a distribution-list message that is also a message
This reason occurs in the following circumstances:
in a group, a message segment, or has segmentation
v On an MQGET call, when the
allowed, but an invalid combination of options and
MQGMO_COMPLETE_MSG option is specified in
values was specified. All of the following are true:
MQGMO and the logical message to be retrieved is
persistent and consists of two or more segments. v MQPMO_LOGICAL_ORDER is not specified in the
v On an MQPUT or MQPUT1 call, when the Options field in MQPMO.
MQMF_SEGMENTATION_ALLOWED flag is v Either there are too few MQPMR records provided
specified in MQMD and the message requires by MQPMO, or the GroupId field is not present in
segmentation. the MQPMR records.
v One or more of the following flags is specified in the
This reason code occurs in the following environments: MsgFlags field in MQMD or MQMDE:
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus MQMF_SEGMENTATION_ALLOWED
WebSphere MQ clients connected to these systems. MQMF_*_MSG_IN_GROUP
Completion Code: MQCC_FAILED MQMF_*_SEGMENT
v The GroupId field in MQMD or MQMDE is not
Programmer Response: Issue the MQGET, MQPUT,
MQGI_NONE.
or MQPUT1 call inside the user-defined unit of work.
Alternatively, for the MQPUT or MQPUT1 call, reduce This combination of options and values would result in
the size of the message so that it does not require the same group identifier being used for all of the
segmentation by the queue manager. destinations in the distribution list; this is not permitted
by the queue manager.
2256 (X'08D0') MQRC_WRONG_GMO_VERSION
Explanation: An MQGET call was issued specifying AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
options that required an MQGMO with a version WebSphere MQ clients connected to these systems.
number not less than MQGMO_VERSION_2, but the
MQGMO supplied did not satisfy this condition.
Programmer Response: Specify MQGI_NONE for the
GroupId field in MQMD or MQMDE. Alternatively, if

the call is MQPUT specify MQPMO_LOGICAL_ORDER The exit returns this reason in the Feedback field of the
in the Options field in MQPMO. MQCXP structure. If an exception report is requested, it
is copied to the Feedback field of the MQMD associated
with the report.
2259 (X'08D3') MQRC_INCONSISTENT_BROWSE
Explanation: An MQGET call was issued with the This reason code occurs in the following environments:
MQGMO_BROWSE_NEXT option specified, but the AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
specification of the MQGMO_LOGICAL_ORDER WebSphere MQ clients connected to these systems.
option for the call is different from the specification of
that option for the previous call for the queue handle.
Either both calls must specify Programmer Response: Specify the source
MQGMO_LOGICAL_ORDER, or neither call must environment data correctly.
specify MQGMO_LOGICAL_ORDER.
This reason code occurs in the following environments: 2262 (X'08D6') MQRC_SRC_NAME_ERROR
WebSphere MQ clients connected to these systems. Explanation: This reason occurs when a channel exit
that processes reference messages detects an error in
Completion Code: MQCC_FAILED the source name data of a reference message header
(MQRMH). One of the following is true:
Programmer Response: Add or remove the
v SrcNameLength is less than zero.
MQGMO_LOGICAL_ORDER option as appropriate.
v SrcNameLength is greater than zero, but there is no
Alternatively, to switch between logical order and
source name data.
physical order, specify the MQGMO_BROWSE_FIRST
v SrcNameLength is greater than zero, but
option to restart the scan from the beginning of the
SrcNameOffset is negative, zero, or less than the
queue, omitting or specifying
length of the fixed part of MQRMH.
MQGMO_LOGICAL_ORDER as required.
v SrcNameLength is greater than zero, but
SrcNameOffset plus SrcNameLength is greater than
2260 (X'08D4') MQRC_XQH_ERROR StrucLength.
The exit returns this reason in the Feedback field of the
but the message data contains an MQXQH structure
MQCXP structure. If an exception report is requested, it
v The StrucId field is not MQXQH_STRUC_ID.
with the report.
v The Version field is not MQXQH_VERSION_1.
that is too small to accommodate the structure (the This reason code occurs in the following environments:
structure extends beyond the end of the message). AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
plus WebSphere MQ clients connected to these systems. Programmer Response: Specify the source name data
correctly.
Programmer Response: Check that the fields in the 2263 (X'08D7') MQRC_DEST_ENV_ERROR
Explanation: This reason occurs when a channel exit
2261 (X'08D5') MQRC_SRC_ENV_ERROR the destination environment data of a reference
message header (MQRMH). One of the following is
Explanation: This reason occurs when a channel exit
true:
v DestEnvLength is less than zero.
the source environment data of a reference message
v DestEnvLength is greater than zero, but there is no
header (MQRMH). One of the following is true:
destination environment data.
v SrcEnvLength is less than zero.
v DestEnvLength is greater than zero, but
v SrcEnvLength is greater than zero, but there is no
DestEnvOffset is negative, zero, or less than the
source environment data.
length of the fixed part of MQRMH.
v SrcEnvLength is greater than zero, but SrcEnvOffset
v DestEnvLength is greater than zero, but
is negative, zero, or less than the length of the fixed
DestEnvOffset plus DestEnvLength is greater than
part of MQRMH.
StrucLength.
v SrcEnvLength is greater than zero, but SrcEnvOffset
plus SrcEnvLength is greater than StrucLength.


2266 (X'08DA') MQRC_CLUSTER_EXIT_ERROR
is copied to the Feedback field of the MQMD associated Explanation: An MQOPEN, MQPUT, or MQPUT1 call
with the report. was issued to open or put a message on a cluster
queue, but the cluster workload exit defined by the
This reason code occurs in the following environments: queue-manager’s ClusterWorkloadExit attribute failed
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus unexpectedly or did not respond in time. Subsequent
WebSphere MQ clients connected to these systems. MQOPEN, MQPUT, and MQPUT1 calls for this queue
handle are processed as though the
Completion Code: MQCC_FAILED ClusterWorkloadExit attribute were blank.
Programmer Response: Specify the destination v On z/OS, a message giving more information about
environment data correctly. the error is written to the system log, for example
message CSQV455E or CSQV456E.
2264 (X'08D8') MQRC_DEST_NAME_ERROR
Explanation: This reason occurs when a channel exit AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
that processes reference messages detects an error in plus WebSphere MQ clients connected to these systems.
the destination name data of a reference message
header (MQRMH). One of the following is true: Completion Code: MQCC_FAILED
v DestNameLength is less than zero. Programmer Response: Check the cluster workload
v DestNameLength is greater than zero, but there is no exit to ensure that it has been written correctly.
destination name data.
v DestNameLength is greater than zero, but
DestNameOffset is negative, zero, or less than the 2267 (X'08DB')
length of the fixed part of MQRMH. MQRC_CLUSTER_EXIT_LOAD_ERROR
v DestNameLength is greater than zero, but Explanation: An MQCONN or MQCONNX call was
DestNameOffset plus DestNameLength is greater than issued to connect to a queue manager, but the queue
StrucLength. manager was unable to load the cluster workload exit.
Execution continues without the cluster workload exit.
v On z/OS, if the cluster workload exit cannot be
loaded, a message is written to the system log, for
example message CSQV453I. Processing continues as
with the report.
though the ClusterWorkloadExit attribute had been
blank.
Completion Code: MQCC_FAILED WebSphere MQ clients connected to these systems.
Programmer Response: Specify the destination name Completion Code: MQCC_WARNING
data correctly.
Programmer Response: Ensure that the
queue-manager’s ClusterWorkloadExit attribute has the
2265 (X'08D9') MQRC_TM_ERROR correct value, and that the exit has been installed into
the correct location.
but the message data contains an MQTM structure that
is not valid. Possible errors include the following: 2268 (X'08DC') MQRC_CLUSTER_PUT_INHIBITED
v The StrucId field is not MQTM_STRUC_ID.
Explanation: An MQOPEN call with the
v The Version field is not MQTM_VERSION_1.
MQOO_OUTPUT and MQOO_BIND_ON_OPEN
options in effect was issued for a cluster queue, but the
call failed because all of the following are true:
v All instances of the cluster queue are currently
put-inhibited (that is, all of the queue instances have
This reason code occurs in the following environments: the InhibitPut attribute set to
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, MQQA_PUT_INHIBITED).
plus WebSphere MQ clients connected to these systems. v There is no local instance of the queue. (If there is a
Completion Code: MQCC_FAILED local instance, the MQOPEN call succeeds, even if
the local instance is put-inhibited.)
Programmer Response: Check that the fields in the v There is no cluster workload exit for the queue, or
structure are set correctly. there is a cluster workload exit but it did not choose

a queue instance. (If the cluster workload exit does and queue status to determine why all instances of the
choose a queue instance, the MQOPEN call succeeds, queue were removed from the cluster. Correct the
even if that instance is put-inhibited.) problem and rerun the application.
If the MQOO_BIND_NOT_FIXED option is specified on

2271 (X'08DF') MQRC_CONN_TAG_IN_USE
the MQOPEN call, the call can succeed even if all of
the queues in the cluster are put-inhibited. However, a Explanation: An MQCONNX call was issued
subsequent MQPUT call may fail if all of the queues specifying one of the MQCNO_*_CONN_TAG_*
are still put-inhibited at the time of the MQPUT call. options, but the call failed because the connection tag
specified by ConnTag in MQCNO is in use by an active
This reason code occurs in the following environments: process or thread, or there is an unresolved unit of
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, work that references this connection tag.
Programmer Response: If the system design allows
Programmer Response: The problem is likely to be
put requests to be inhibited for short periods, retry the
transitory. The application should wait a short while
operation later. If the problem persists, determine why
and then retry the operation.
all of the queues in the cluster are put-inhibited.
2272 (X'08E0') MQRC_PARTIALLY_CONVERTED

2269 (X'08DD')
MQRC_CLUSTER_RESOURCE_ERROR Explanation: On an MQGET call with the
Explanation: An MQOPEN, MQPUT, or MQPUT1 call
GetMsgOpts parameter, one or more MQ header
was issued for a cluster queue, but an error occurred
structures in the message data could not be converted
whilst trying to use a resource required for clustering.
to the specified target character set or encoding. In this
This reason code occurs in the following environments: situation, the MQ header structures are converted to
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, the queue-manager’s character set and encoding, and
plus WebSphere MQ clients connected to these systems. the application data in the message is converted to the
target character set and encoding. On return from the
Completion Code: MQCC_FAILED call, the values returned in the various CodedCharSetId
Programmer Response: Do the following: and Encoding fields in the MsgDesc parameter and MQ
v Check that the SYSTEM.CLUSTER.* queues are not header structures indicate the character set and
put inhibited or full. encoding that apply to each part of the message. The
v Check the event queues for any events relating to the call completes with MQCC_WARNING.
SYSTEM.CLUSTER.* queues, as these may give This reason code usually occurs when the specified
guidance as to the nature of the failure. target character set is one that causes the character
v Check that the repository queue manager is strings in the MQ header structures to expand beyond
available. the lengths of their fields. Unicode character set UCS-2
v On z/OS, check the console for signs of the failure, is an example of a character set that causes this to
such as full page sets. happen.
2270 (X'08DE')
MQRC_NO_DESTINATIONS_AVAILABLE Programmer Response: If this is an expected situation,
no corrective action is required.
to put a message on a cluster queue, but at the time of If this is an unexpected situation, check that the MQ
the call there were no longer any instances of the queue header structures contain valid data. If they do, specify
in the cluster. The message therefore could not be sent. as the target character set a character set that does not
cause the strings to expand.
This situation can occur when
MQOO_BIND_NOT_FIXED is specified on the
MQOPEN call that opens the queue, or MQPUT1 is 1 2273 (X'08E1') MQRC_CONNECTION_ERROR
used to put the message.
1 Explanation: An MQCONN or MQCONNX call failed
This reason code occurs in the following environments: 1 for one of the following reasons:
AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, 1 v The installation and customization options chosen for
plus WebSphere MQ clients connected to these systems. 1 WebSphere MQ do not allow connection by the type
1 of application being used.
Completion Code: MQCC_FAILED 1 v The system parameter module is not at the same
Programmer Response: Check the queue definition 1 release level as the queue manager.

1 v The channel initiator is not at the same release level v ClientConnOffset is not zero and ClientConnPtr is
1 as the queue manager. not zero and not the null pointer.
1 v An internal error was detected by the queue v ClientConnPtr is not a valid pointer.
1 manager. v ClientConnPtr or ClientConnOffset points to storage
that is not accessible.
1 This reason code occurs only on z/OS.
1 Completion Code: MQCC_FAILED AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
1 Programmer Response: None, if the installation and WebSphere MQ clients connected to these systems. It
1 customization options chosen for WebSphere MQ do also occurs in Java applications when a client channel
1 not allow all functions to be used. definition table is specified to determine the name of
the channel, but the table itself cannot be found.
1 Otherwise, if this occurs while starting the channel
1 initiator, ensure that the queue manager and the Completion Code: MQCC_FAILED
1 channel initiator are both at the same release level and
Programmer Response: Ensure that at least one of
1 that their started task JCL procedures both specify the
ClientConnOffset and ClientConnPtr is zero. Ensure
1 same level of WebSphere MQ program libraries; if this
that the field used points to accessible storage. Ensure
1 occurs while starting the queue manager, relinkedit the
that the URL of the client channel definition table is
1 system parameter module (CSQZPARM) to ensure that
correct.
1 it is at the correct level. If the problem persists, contact
1 your IBM support center.
2279 (X'08E7')
MQRC_CHANNEL_STOPPED_BY_USER
2274 (X'08E2')
MQRC_OPTION_ENVIRONMENT_ERROR Explanation: This condition is detected when the
channel has been stopped by an operator. The reason
Explanation: An MQGET call with the
qualifier identifies the reasons for stopping.
MQGMO_MARK_SKIP_BACKOUT option specified
was issued from a DB2 Stored Procedure. The call Completion Code: MQCC_WARNING
failed because the MQGMO_MARK_SKIP_BACKOUT
option cannot be used from a DB2 Stored Procedure.
Completion Code: MQCC_FAILED 2280 (X'08E8') MQRC_HCONFIG_ERROR
Programmer Response: Remove the Explanation: The configuration handle Hconfig
MQGMO_MARK_SKIP_BACKOUT option from the specified on the MQXEP call or MQZEP call is not
MQGET call. valid. The MQXEP call is issued by an API exit
function; the MQZEP call is issued by an installable
service.
2277 (X'08E5') MQRC_CD_ERROR
Explanation: An MQCONNX call was issued to
connect to a queue manager, but the MQCD channel Completion Code: MQCC_FAILED
definition structure addressed by the ClientConnOffset Programmer Response: Specify the configuration
or ClientConnPtr field in MQCNO contains data that is handle that was provided by the queue manager:
not valid. Consult the error log for more information
v On the MQXEP call, use the handle passed in the
about the nature of the error.
Hconfig field of the MQAXP structure.
This reason code occurs in the following environments: v On the MQZEP call, use the handle passed to the
AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus installable service’s configuration function on the
WebSphere MQ clients connected to these systems. component initialization call. See the WebSphere MQ
Completion Code: MQCC_FAILED System Administration Guide book for information
about installable services.
MQCD structure are set correctly.
2281 (X'08E9') MQRC_FUNCTION_ERROR
2278 (X'08E6') MQRC_CLIENT_CONN_ERROR Explanation: An MQXEP or MQZEP call was issued,

but the function identifier Function specified on the call
Explanation: An MQCONNX call was issued to is not valid, or not supported by the installable service
connect to a queue manager, but the MQCD channel being configured.
definition structure is not specified correctly. One of the
following applies:

Programmer Response: Do the following:

2286 (X'08EE') MQRC_INITIALIZATION_FAILED
v For the MQXEP call, specify one of the MQXF_*
values. Explanation: This reason should be returned by an
installable service component when the component is
v For the MQZEP call, specify an MQZID_* value that
unable to complete initialization successfully.
is valid for the installable service being configured.
Refer to the description of the MQZEP call in the v On z/OS, this reason code does not occur.
WebSphere MQ System Administration Guide book to Completion Code: MQCC_FAILED
determine which values are valid.
Programmer Response: Correct the error and retry the
operation.
2282 (X'08EA') MQRC_CHANNEL_STARTED
Explanation: One of the following has occurred: 2287 (X'08EF') MQRC_TERMINATION_FAILED
v An operator has issued a Start Channel command.
v An instance of a channel has been successfully Explanation: This reason should be returned by an
established. This condition is detected when Initial installable service component when the component is
Data negotiation is complete and resynchronization unable to complete termination successfully.
has been performed where necessary such that v On z/OS, this reason code does not occur.
message transfer can proceed.
Programmer Response: None. This reason code is operation.
2288 (X'08F0') MQRC_UNKNOWN_Q_NAME

2283 (X'08EB') MQRC_CHANNEL_STOPPED
Explanation: This reason should be returned by the
Explanation: This condition is detected when the MQZ_LOOKUP_NAME installable service component
channel has been stopped. The reason qualifier when the name specified for the QName parameter is not
identifies the reasons for stopping. recognized.
Completion Code: MQCC_WARNING v On z/OS, this reason code does not occur.
Programmer Response: None. This reason code is Completion Code: MQCC_FAILED

only used to identify the corresponding event message. Programmer Response: None. See the WebSphere MQ
System Administration Guide book for information about
2284 (X'08EC') MQRC_CHANNEL_CONV_ERROR installable services.
Explanation: This condition is detected when a

channel is unable to do data conversion and the 2289 (X'08F1') MQRC_SERVICE_ERROR
MQGET call to get a message from the transmission Explanation: This reason should be returned by an
queue resulted in a data conversion error. The installable service component when the component
conversion reason code identifies the reason for the encounters an unexpected error.
failure.
only used to identify the corresponding event message. Programmer Response: Correct the error and retry the
operation.
2285 (X'08ED') MQRC_SERVICE_NOT_AVAILABLE

2290 (X'08F2') MQRC_Q_ALREADY_EXISTS
Explanation: This reason should be returned by an
installable service component when the requested Explanation: This reason should be returned by the
action cannot be performed because the required MQZ_INSERT_NAME installable service component
underlying service is not available. when the queue specified by the QName parameter is
already defined to the name service.
Programmer Response: Make the underlying service
available. Programmer Response: None. See the WebSphere MQ
System Administration Guide book for information about
installable service.

attempt to establish connection with its partner.

2291 (X'08F3') MQRC_USER_ID_NOT_AVAILABLE
However, it is unable to do so because the limit on the
Explanation: This reason should be returned by the number of active channels has been reached.
MQZ_FIND_USERID installable service component v On z/OS, the maximum number of active channels is
when the user ID cannot be determined. given by the ACTCHL queue manager attribute.
v On z/OS, this reason code does not occur. v In other environments, the maximum number of
active channels is given by the MaxActiveChannels
Completion Code: MQCC_FAILED parameter in the qm.ini file.
Programmer Response: None. See the WebSphere MQ The channel waits until it is able to take over an active
System Administration Guide book for information about slot released when another channel ceases to be active.
installable services. At that time a Channel Activated event is generated.
2292 (X'08F4') MQRC_UNKNOWN_ENTITY
Explanation: This reason should be returned by the only used to identify the corresponding event message.
authority installable service component when the name
specified by the EntityName parameter is not
recognized. 2297 (X'08F9') MQRC_UOW_CANCELED
v On z/OS, this reason code does not occur. Explanation: An MQI call was issued, but the unit of
work (TM/MP transaction) being used for the MQ
operation had been canceled. This may have been done
Programmer Response: Ensure that the entity is by TM/MP itself (for example, due to the transaction
defined. running for too long, or exceeding audit trail sizes), or
by the application program issuing an
ABORT_TRANSACTION. All updates performed to
2294 (X'08F6') MQRC_UNKNOWN_REF_OBJECT resources owned by the queue manager are backed out.
Explanation: This reason should be returned by the Completion Code: MQCC_FAILED
MQZ_COPY_ALL_AUTHORITY installable service
component when the name specified by the Programmer Response: Refer to the operating
RefObjectName parameter is not recognized. system’s Transaction Management Operations Guide to
v On z/OS, this reason code does not occur. determine how the Transaction Manager can be tuned
to avoid the problem of system limits being exceeded.
Programmer Response: Ensure that the reference 2298 (X'08FA')
object is defined. See the WebSphere MQ System MQRC_FUNCTION_NOT_SUPPORTED
Administration Guide book for information about
installable services. Explanation: The function requested is not available in
the current environment.
2295 (X'08F7') MQRC_CHANNEL_ACTIVATED Completion Code: MQCC_FAILED
Explanation: This condition is detected when a Programmer Response: Remove the call from the
channel that has been waiting to become active, and for application.
which a Channel Not Activated event has been
generated, is now able to become active because an 2299 (X'08FB') MQRC_SELECTOR_TYPE_ERROR
active slot has been released by another channel.
Explanation: The Selector parameter has the wrong
This event is not generated for a channel that is able to data type; it must be of type Long.
become active without waiting for an active slot to be
released. Completion Code: MQCC_FAILED
Completion Code: MQCC_WARNING Programmer Response: Declare the Selector

parameter as Long.
2300 (X'08FC') MQRC_COMMAND_TYPE_ERROR
2296 (X'08F8') Explanation: The mqExecute call was issued, but the
MQRC_CHANNEL_NOT_ACTIVATED value of the MQIASY_TYPE data item in the
administration bag is not MQCFT_COMMAND.
channel is required to become active, either because it Completion Code: MQCC_FAILED
is starting or because it is about to make another Programmer Response: Ensure that the

MQIASY_TYPE data item in the administration bag has If the bag was not created with the
the value MQCFT_COMMAND. MQCBO_CHECK_SELECTORS option:
v The value must be zero or greater.
2301 (X'08FD') Completion Code: MQCC_FAILED
MQRC_MULTIPLE_INSTANCE_ERROR
Programmer Response: Specify a valid value.
Explanation: The Selector parameter specifies a
system selector (one of the MQIASY_* values), but the
value of the ItemIndex parameter is not 2305 (X'0901') MQRC_SELECTOR_NOT_UNIQUE
MQIND_NONE. Only one instance of each system Explanation: The ItemIndex parameter has the value
selector can exist in the bag. MQIND_NONE, but the bag contains more than one
Completion Code: MQCC_FAILED data item with the selector value specified by the
Selector parameter. MQIND_NONE requires that the
Programmer Response: Specify MQIND_NONE for bag contain only one occurrence of the specified
the ItemIndex parameter. selector.
This reason code also occurs on the mqExecute call
2302 (X'08FE') when the administration bag contains two or more
MQRC_SYSTEM_ITEM_NOT_ALTERABLE occurrences of a selector for a required parameter that
Explanation: A call was issued to modify the value of permits only one occurrence.
a system data item in a bag (a data item with one of Completion Code: MQCC_FAILED
the MQIASY_* selectors), but the call failed because the
data item is one that cannot be altered by the Programmer Response: Check the logic of the
application. application that created the bag. If correct, specify for
ItemIndex a value that is zero or greater, and add
Completion Code: MQCC_FAILED application logic to process all of the occurrences of the
Programmer Response: Specify the selector of a selector in the bag.
user-defined data item, or remove the call. Review the description of the administration command
being issued, and ensure that all required parameters
2303 (X'08FF') MQRC_BAG_CONVERSION_ERROR are defined correctly in the bag.
Explanation: The mqBufferToBag or mqGetBag call

was issued, but the data in the buffer or message could 2306 (X'0902') MQRC_INDEX_NOT_PRESENT
not be converted into a bag. This occurs when the data Explanation: The specified index is not present:
to be converted is not valid PCF. v For a bag, this means that the bag contains one or
Completion Code: MQCC_FAILED more data items that have the selector value
specified by the Selector parameter, but none of
Programmer Response: Check the logic of the them has the index value specified by the ItemIndex
application that created the buffer or message to ensure parameter. The data item identified by the Selector
that the buffer or message contains valid PCF. and ItemIndex parameters must exist in the bag.
If the message contains PCF that is not valid, the v For a namelist, this means that the index parameter
message cannot be retrieved using the mqGetBag call: value is too large, and outside the range of valid
v If one of the MQGMO_BROWSE_* options was values.
specified, the message remains on the queue and can Completion Code: MQCC_FAILED
be retrieved using the MQGET call.
v In other cases, the message has already been Programmer Response: Specify the index of a data
removed from the queue and discarded. If the item that does exist in the bag or namelist. Use the
message was retrieved within a unit of work, the mqCountItems call to determine the number of data
unit of work can be backed out and the message items with the specified selector that exist in the bag, or
retrieved using the MQGET call. the nameCount method to determine the number of
names in the namelist.
2304 (X'0900') MQRC_SELECTOR_OUT_OF_RANGE

2307 (X'0903') MQRC_STRING_ERROR
Explanation: The Selector parameter has a value that
is outside the valid range for the call. If the bag was Explanation: The String parameter is not valid. Either
created with the MQCBO_CHECK_SELECTORS option: the parameter pointer is not valid, or it points to
v For the mqAddInteger call, the value must be within read-only storage. (It is not always possible to detect
the range MQIA_FIRST through MQIA_LAST. parameter pointers that are not valid; if not detected,
v For the mqAddString call, the value must be within unpredictable results occur.)
the range MQCA_FIRST through MQCA_LAST. Completion Code: MQCC_FAILED

Programmer Response: Correct the parameter. Programmer Response: If the entire string is required,
provide a larger buffer. On the mqInquireString call,
the StringLength parameter is set by the call to indicate
2308 (X'0904')
the size of the buffer required to accommodate the
MQRC_ENCODING_NOT_SUPPORTED
string without truncation.
Explanation: The Encoding field in the message
descriptor MQMD contains a value that is not
2312 (X'0908') MQRC_SELECTOR_WRONG_TYPE
supported:
v For the mqPutBag call, the field in error resides in Explanation: A data item with the specified selector
the MsgDesc parameter of the call. exists in the bag, but has a data type that conflicts with
the data type implied by the call being used. For
v For the mqGetBag call, the field in error resides in:
example, the data item might have an integer data
– The MsgDesc parameter of the call if the
type, but the call being used might be mqSetString,
MQGMO_CONVERT option was specified.
which implies a character data type.
– The message descriptor of the message about to
be retrieved if MQGMO_CONVERT was not This reason code also occurs on the mqBagToBuffer,
specified. mqExecute, and mqPutBag calls when mqAddString or
mqSetString was used to add the MQIACF_INQUIRY
data item to the bag.
Programmer Response: The value must be
MQENC_NATIVE.
Programmer Response: For the mqSetInteger and
If the value of the Encoding field in the message is not
mqSetString calls, specify MQIND_ALL for the
valid, the message cannot be retrieved using the
ItemIndex parameter to delete from the bag all existing
mqGetBag call:
occurrences of the specified selector before creating the
v If one of the MQGMO_BROWSE_* options was
new occurrence with the required data type.
specified, the message remains on the queue and can
be retrieved using the MQGET call. For the mqInquireBag, mqInquireInteger, and
v In other cases, the message has already been mqInquireString calls, use the mqInquireItemInfo call to
removed from the queue and discarded. If the determine the data type of the item with the specified
message was retrieved within a unit of work, the selector, and then use the appropriate call to determine
unit of work can be backed out and the message the value of the data item.
retrieved using the MQGET call.
For the mqBagToBuffer, mqExecute, and mqPutBag
calls, ensure that the MQIACF_INQUIRY data item is
2309 (X'0905') MQRC_SELECTOR_NOT_PRESENT added to the bag using the mqAddInteger or
mqSetInteger calls.
Explanation: The Selector parameter specifies a
selector that does not exist in the bag.
2313 (X'0909') MQRC_INCONSISTENT_ITEM_TYPE
Explanation: The mqAddInteger or mqAddString call
Programmer Response: Specify a selector that does
was issued to add another occurrence of the specified
exist in the bag.
selector to the bag, but the data type of this occurrence
differed from the data type of the first occurrence.
2310 (X'0906') MQRC_OUT_SELECTOR_ERROR
This reason can also occur on the mqBufferToBag and
Explanation: The OutSelector parameter is not valid. mqGetBag calls, where it indicates that the PCF in the
Either the parameter pointer is not valid, or it points to buffer or message contains a selector that occurs more
read-only storage. (It is not always possible to detect than once but with inconsistent data types.
Programmer Response: For the mqAddInteger and
mqAddString calls, use the call appropriate to the data
Programmer Response: Correct the parameter. type of the first occurrence of that selector in the bag.
For the mqBufferToBag and mqGetBag calls, check the
2311 (X'0907') MQRC_STRING_TRUNCATED logic of the application that created the buffer or sent
the message to ensure that multiple-occurrence
Explanation: The string returned by the call is too selectors occur with only one data type. A message that
long to fit in the buffer provided. The string has been contains a mixture of data types for a selector cannot
truncated to fit in the buffer. be retrieved using the mqGetBag call:


2317 (X'090D') MQRC_FORMAT_NOT_SUPPORTED
be retrieved using the MQGET call. Explanation: The Format field in the message
v In other cases, the message has already been descriptor MQMD contains a value that is not
removed from the queue and discarded. If the supported:
message was retrieved within a unit of work, the v In an administration message, the format value must
unit of work can be backed out and the message be one of the following: MQFMT_ADMIN,
retrieved using the MQGET call. MQFMT_EVENT, MQFMT_PCF. For the mqPutBag
call, the field in error resides in the MsgDesc
2314 (X'090A') MQRC_INDEX_ERROR parameter of the call. For the mqGetBag call, the
field in error resides in the message descriptor of the
Explanation: An index parameter to a call or method message about to be retrieved.
has a value that is not valid. The value must be zero or
v On z/OS, the message was put to the command
greater. For bag calls, certain MQIND_* values can also
input queue with a format value of
be specified:
MQFMT_ADMIN, but the version of MQ being used
v For the mqDeleteItem, mqSetInteger and mqSetString
does not support that format for commands.
calls, MQIND_ALL and MQIND_NONE are valid.
v For the mqInquireBag, mqInquireInteger, Completion Code: MQCC_FAILED
mqInquireString, and mqInquireItemInfo calls,
Programmer Response: If the error occurred when
MQIND_NONE is valid.
putting a message, correct the format value.
If the error occurred when getting a message, the
Programmer Response: Specify a valid value. message cannot be retrieved using the mqGetBag call:
2315 (X'090B')
be retrieved using the MQGET call.
MQRC_SYSTEM_BAG_NOT_ALTERABLE
v In other cases, the message has already been
Explanation: A call was issued to add a data item to a removed from the queue and discarded. If the
bag, modify the value of an existing data item in a bag, message was retrieved within a unit of work, the
or retrieve a message into a bag, but the call failed unit of work can be backed out and the message
because the bag is one that had been created by the retrieved using the MQGET call.
system as a result of a previous mqExecute call. System
bags cannot be modified by the application.
2318 (X'090E')
Completion Code: MQCC_FAILED MQRC_SELECTOR_NOT_SUPPORTED
Programmer Response: Specify the handle of a bag Explanation: The Selector parameter specifies a value
created by the application, or remove the call. that is a system selector (a value that is negative), but
the system selector is not one that is supported by the
call.
2316 (X'090C') MQRC_ITEM_COUNT_ERROR
Explanation: The mqTruncateBag call was issued, but
the ItemCount parameter specifies a value that is not Programmer Response: Specify a selector value that is
valid. The value is either less than zero, or greater than supported.
the number of user-defined data items in the bag.
This reason also occurs on the mqCountItems call if the 2319 (X'090F') MQRC_ITEM_VALUE_ERROR
parameter pointer is not valid, or points to read-only
Explanation: The mqInquireBag or mqInquireInteger
storage. (It is not always possible to detect parameter
call was issued, but the ItemValue parameter is not
pointers that are not valid; if not detected,
valid. Either the parameter pointer is not valid, or it
points to read-only storage. (It is not always possible to
Completion Code: MQCC_FAILED detect parameter pointers that are not valid; if not
Programmer Response: Specify a valid value. Use the
mqCountItems call to determine the number of Completion Code: MQCC_FAILED
user-defined data items in the bag.

2320 (X'0910') MQRC_HBAG_ERROR 2325 (X'0915')

MQRC_NESTED_BAG_NOT_SUPPORTED
Explanation: A call was issued that has a parameter
that is a bag handle, but the handle is not valid. For Explanation: A bag that is input to the call contains
output parameters, this reason also occurs if the nested bags. Nested bags are supported only for bags
parameter pointer is not valid, or points to read-only that are output from the call.
pointers that are not valid; if not detected,
unpredictable results occur.) Programmer Response: Use a different bag as input to
the call.
2326 (X'0916') MQRC_BAG_WRONG_TYPE
Explanation: The Bag parameter specifies the handle
2321 (X'0911') MQRC_PARAMETER_MISSING
of a bag that has the wrong type for the call. The bag
Explanation: An administration message requires a must be an administration bag, that is, it must be
parameter that is not present in the administration bag. created with the MQCBO_ADMIN_BAG option
This reason code occurs only for bags created with the specified on the mqCreateBag call.
MQCBO_ADMIN_BAG or
MQCBO_REORDER_AS_REQUIRED options.
Programmer Response: Specify the
MQCBO_ADMIN_BAG option when the bag is created.
Programmer Response: Review the description of the
administration command being issued, and ensure that
2327 (X'0917') MQRC_ITEM_TYPE_ERROR
all required parameters are present in the bag.
Explanation: The mqInquireItemInfo call was issued,
but the ItemType parameter is not valid. Either the
2322 (X'0912')
parameter pointer is not valid, or it points to read-only
MQRC_CMD_SERVER_NOT_AVAILABLE
Explanation: The command server that processes pointers that are not valid; if not detected,
administration commands is not available. unpredictable results occur.)
Programmer Response: Start the command server. Programmer Response: Correct the parameter.
2323 (X'0913') MQRC_STRING_LENGTH_ERROR 2328 (X'0918')

MQRC_SYSTEM_BAG_NOT_DELETABLE
Explanation: The StringLength parameter is not valid.
Either the parameter pointer is not valid, or it points to Explanation: An mqDeleteBag call was issued to
read-only storage. (It is not always possible to detect delete a bag, but the call failed because the bag is one
parameter pointers that are not valid; if not detected, that had been created by the system as a result of a
unpredictable results occur.) previous mqExecute call. System bags cannot be
deleted by the application.
Programmer Response: Specify the handle of a bag
created by the application, or remove the call.
2324 (X'0914')
MQRC_INQUIRY_COMMAND_ERROR
2329 (X'0919')
Explanation: The mqAddInquiry call was used
MQRC_SYSTEM_ITEM_NOT_DELETABLE
previously to add attribute selectors to the bag, but the
command code to be used for the mqBagToBuffer, Explanation: A call was issued to delete a system data
mqExecute, or mqPutBag call is not recognized. As a item from a bag (a data item with one of the
result, the correct PCF message cannot be generated. MQIASY_* selectors), but the call failed because the
data item is one that cannot be deleted by the
application.
Programmer Response: Remove the mqAddInquiry
calls and use instead the mqAddInteger call with the
appropriate MQIACF_*_ATTRS or MQIACH_*_ATTRS Programmer Response: Specify the selector of a
selectors. user-defined data item, or remove the call.


2330 (X'091A')
MQRC_CODED_CHAR_SET_ID_ERROR
Explanation: The CodedCharSetId parameter is not v On z/OS, this error also occurs when the IndexType
valid. Either the parameter pointer is not valid, or it attribute of the queue is MQIT_MSG_TOKEN, but
points to read-only storage. (It is not always possible to the message data does not begin with an MQWIH
detect parameter pointers that are not valid; if not structure.
Programmer Response: Correct the parameter. structure are set correctly. Ensure that the application
1 2331 (X'091B') MQRC_MSG_TOKEN_ERROR MQCCSI_DEFAULT, MQCCSI_EMBEDDED,
1 Explanation: An MQGET call was issued to retrieve a valid in this field).
1 message using the message token as a selection
v On z/OS, if the queue has an IndexType of
1 criterion, but the options specified are not valid,
MQIT_MSG_TOKEN, ensure that the message data
1 because MQMO_MATCH_MSG_TOKEN was specified
begins with an MQWIH structure.
1 with either MQGMO_WAIT or MQGMO_SET_SIGNAL.
1 This reason code occurs only on z/OS. 2334 (X'091E') MQRC_RFH_ERROR
1 Completion Code: MQCC_FAILED Explanation: An MQPUT or MQPUT1 call was issued,
1 Programmer Response: Remove the but the message data contains an MQRFH or MQRFH2
1 MQMO_MATCH_MSG_TOKEN option from the structure that is not valid. Possible errors include the
1 MQGET call. following:
v The StrucId field is not MQRFH_STRUC_ID.
v The Version field is not MQRFH_VERSION_1
2332 (X'091C') MQRC_MISSING_WIH (MQRFH), or MQRFH_VERSION_2 (MQRFH2).
Explanation: An MQPUT or MQPUT1 call was issued v The StrucLength field specifies a value that is too
to put a message on a queue whose IndexType attribute small to include the structure plus the
had the value MQIT_MSG_TOKEN, but the Format variable-length data at the end of the structure.
field in the MQMD was not v The CodedCharSetId field is zero, or a negative value
MQFMT_WORK_INFO_HEADER. This error occurs that is not valid.
only when the message arrives at the destination queue v The BufferLength parameter of the call has a value
manager. that is too small to accommodate the structure (the
Programmer Response: Modify the application to structure are set correctly. Ensure that the application
ensure that it places an MQWIH structure at the start sets the CodedCharSetId field to a valid value (note:
of the message data, and sets the Format field in the MQCCSI_DEFAULT, MQCCSI_EMBEDDED,
MQMD to MQFMT_WORK_INFO_HEADER. MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not
Alternatively, change the ApplType attribute of the valid in this field).
process definition used by the destination queue to be
MQAT_WLM, and specify the required service name
and service step name in its EnvData attribute. 2335 (X'091F') MQRC_RFH_STRING_ERROR
Explanation: The contents of the NameValueString
2333 (X'091D') MQRC_WIH_ERROR field in the MQRFH structure are not valid.
NameValueString must adhere to the following rules:
Explanation: An MQPUT or MQPUT1 call was issued, v The string must consist of zero or more name/value
but the message data contains an MQWIH structure pairs separated from each other by one or more
that is not valid. Possible errors include the following: blanks; the blanks are not significant.
v The StrucId field is not MQWIH_STRUC_ID. v If a name or value contains blanks that are
v The Version field is not MQWIH_VERSION_1. significant, the name or value must be enclosed in
v The StrucLength field is not MQWIH_LENGTH_1. double-quote characters.
v The CodedCharSetId field is zero, or a negative value v If a name or value itself contains one or more
that is not valid. double-quote characters, the name or value must be
enclosed in double-quote characters, and each
embedded double-quote character must be doubled.

v A name or value can contain any characters other Programmer Response: Modify the application that
than the null, which acts as a delimiter. The null and generated the message to ensure that it places in the
characters following it, up to the defined length of NameValueString field all parameters that are required
NameValueString, are ignored. for the specified command.
The following is a valid NameValueString:
Famous_Words "The program displayed ""Hello World""" 2340 (X'0924')
MQRC_CHAR_CONVERSION_ERROR
Explanation: This reason code is returned by the Java
Programmer Response: Modify the application that MQQueueManager constructor when a required
generated the message to ensure that it places in the character-set conversion is not available. The
NameValueString field data that adheres to the rules conversion required is between two nonUnicode
listed above. Check that the StrucLength field is set to character sets.
the correct value.
This reason code occurs in the following environment:
MQ Classes for Java on z/OS.
2336 (X'0920') MQRC_RFH_COMMAND_ERROR
Explanation: The message contains an MQRFH
structure, but the command name contained in the Programmer Response: Ensure that the National
NameValueString field is not valid. Language Resources component of the OS/390
Language Environment is installed, and that conversion
Completion Code: MQCC_FAILED between the IBM-1047 and ISO8859-1 character sets is
Programmer Response: Modify the application that available.
generated the message to ensure that it places in the
NameValueString field a command name that is valid. 2341 (X'0925') MQRC_UCS2_CONVERSION_ERROR
Explanation: This reason code is returned by the Java
2337 (X'0921') MQRC_RFH_PARM_ERROR MQQueueManager constructor when a required
Explanation: The message contains an MQRFH character-set conversion is not available. The
structure, but a parameter name contained in the conversion required is between the UCS-2 Unicode
NameValueString field is not valid for the command character set and the queue-manager’s character set.
specified. IBM-500 is used for the queue-manager’s character set
if no specific value is available.
This reason code occurs in the following environment:
Programmer Response: Modify the application that MQ Classes for Java on z/OS.
generated the message to ensure that it places in the
NameValueString field only parameters that are valid Completion Code: MQCC_FAILED
for the specified command. Programmer Response: Ensure that the relevant
Unicode conversion tables are installed, and that they
2338 (X'0922') MQRC_RFH_DUPLICATE_PARM are available to the z/OS Language Environment. The
conversion tables should be installed as part of the
Explanation: The message contains an MQRFH z/OS C/C++ optional feature. Refer to the z/OS C/C++
structure, but a parameter occurs more than once in the Programming Guide for more information about enabling
NameValueString field when only one occurrence is UCS-2 conversions.
valid for the specified command.
Completion Code: MQCC_FAILED 2342 (X'0926') MQRC_DB2_NOT_AVAILABLE
Programmer Response: Modify the application that Explanation: An MQOPEN, MQPUT1, or MQSET call,
generated the message to ensure that it places in the or a command, was issued to access a shared queue,
NameValueString field only one occurrence of the but it failed because the queue manager is not
parameter. connected to a DB2 subsystem. As a result, the queue
manager is unable to access the object definition
relating to the shared queue.
2339 (X'0923') MQRC_RFH_PARM_MISSING
Explanation: The message contains an MQRFH
structure, but the command specified in the Completion Code: MQCC_FAILED
NameValueString field requires a parameter that is not
present. Programmer Response: Configure the DB2 subsystem
so that the queue manager can connect to it.

of coupling facilities that are available.

2343 (X'0927') MQRC_OBJECT_NOT_UNIQUE
Explanation: An MQOPEN or MQPUT1 call, or a
2346 (X'092A') MQRC_CF_STRUC_IN_USE
command, was issued to access a queue, but the call
failed because the queue specified cannot be resolved 1 Explanation: An MQI call or command was issued to
unambiguously. There exists a shared queue with the 1 operate on a shared queue, but the call failed because
specified name, and a nonshared queue with the same 1 the coupling-facility structure specified in the queue
name. 1 definition is temporarily unavailable. The
1 coupling-facility structure can be unavailable because a
1 structure dump is in progress, or new connectors to the
Completion Code: MQCC_FAILED 1 structure are currently inhibited, or an existing
1 connector to the structure failed or disconnected
Programmer Response: One of the queues must be
1 abnormally and clean-up is not yet complete.
deleted. If the queue to be deleted contains messages,
use the MQSC command MOVE QLOCAL to move the 1 This reason code occurs only on z/OS.
messages to a different queue, and then use the
command DELETE QLOCAL to delete the queue.
Programmer Response: The problem is temporary;
wait a short while and then retry the operation.
2344 (X'0928')
MQRC_CONN_TAG_NOT_RELEASED
2347 (X'092B')
Explanation: An MQDISC call was issued when there
MQRC_CF_STRUC_LIST_HDR_IN_USE
was a unit of work outstanding for the connection
handle. For CICS, IMS, and RRS connections, the Explanation: An MQGET, MQOPEN, MQPUT1, or
MQDISC call does not commit or back out the unit of MQSET call was issued to access a shared queue, but
work. As a result, the connection tag associated with the call failed because the list header associated with
the unit of work is not yet available for reuse. The tag the coupling-facility structure specified in the queue
becomes available for reuse only when processing of definition is temporarily unavailable. The list header is
the unit of work has been completed. unavailable because it is undergoing recovery
processing.
Programmer Response: Do not try to reuse the
connection tag immediately. If the MQCONNX call is Programmer Response: The problem is temporary;
issued with the same connection tag, and that tag is wait a short while and then retry the operation.
still in use, the call fails with reason code
MQRC_CONN_TAG_IN_USE.
2348 (X'092C') MQRC_CF_STRUC_AUTH_FAILED
2345 (X'0929') MQRC_CF_NOT_AVAILABLE Explanation: An MQOPEN or MQPUT1 call was

issued to access a shared queue, but the call failed
Explanation: An MQOPEN or MQPUT1 call was because the user is not authorized to access the
issued to access a shared queue, but the allocation of coupling-facility structure specified in the queue
the coupling-facility structure specified in the queue definition.
definition failed because there is no suitable coupling
facility to hold the structure, based on the preference This reason code occurs only on z/OS.
list in the active CFRM policy. Completion Code: MQCC_FAILED
This reason code can also occur when the API call Programmer Response: Modify the security profile for
requires a capability that is not supported by the CF the user identifier used by the application so that the
level defined in the coupling-facility structure object. application can access the coupling-facility structure
For example, this reason code is returned by an attempt specified in the queue definition.
to open a shared queue that has a index type of
MQIT_GROUP_ID, but the coupling-facility structure
for the queue has a CF level lower than three. 2349 (X'092D') MQRC_CF_STRUC_ERROR
This reason code occurs only on z/OS. Explanation: An MQOPEN or MQPUT1 call was
issued to access a shared queue, but the call failed
Completion Code: MQCC_FAILED because the coupling-facility structure name specified
Programmer Response: Make available a coupling in the queue definition is not defined in the CFRM data
facility with one of the names specified in the CFRM set, or is not the name of a list structure.
policy, or modify the CFRM policy to specify the names This reason code occurs only on z/OS.

Completion Code: MQCC_FAILED Transaction Support” attribute defined for the object’s
class is set correctly. If necessary, modify the
Programmer Response: Modify the queue definition
application so that the connection handle is not used by
to specify the name of a coupling-facility list structure
objects participating in different units of work.
that is defined in the CFRM data set.
2353 (X'0931') MQRC_HANDLE_IN_USE_FOR_UOW

2350 (X'092E') MQRC_CONN_TAG_NOT_USABLE
Explanation: An attempt was made to use outside a
Explanation: An MQCONNX call was issued
unit of work a connection handle that is participating
specifying one of the MQCNO_*_CONN_TAG_*
in a global unit of work.
options, but the call failed because the connection tag
specified by ConnTag in MQCNO is being used by the This error can occur when an application passes
queue manager for recovery processing, and this connection handles between objects where one object is
processing is delayed pending recovery of the coupling involved in a DTC transaction and the other is not.
facility. Because transaction completion is asynchronous, it is
possible for this error to occur after the application has
finalized the first object and committed its transaction.
This error can also occur when a single object that was
Programmer Response: The problem is likely to created and associated with the transaction loses that
persist. Consult the system programmer to ascertain the association whilst the object is running. The association
cause of the problem. is lost when DTC terminates the transaction
independently of MTS. This might be because the
transaction timed out, or because DTC shut down.
2351 (X'092F') MQRC_GLOBAL_UOW_CONFLICT
This error does not occur for nontransactional MQI
Explanation: An attempt was made to use inside a calls.
global unit of work a connection handle that is
participating in another global unit of work. This can This reason code occurs only on Windows.
occur when an application passes connection handles
between objects where the objects are involved in
different DTC transactions. Because transaction Programmer Response: Check that the “MTS
completion is asynchronous, it is possible for this error Transaction Support” attribute defined for the object’s
to occur after the application has finalized the first class is set correctly. If necessary, modify the
object and committed its transaction. application so that objects executing within different
units of work do not try to use the same connection
handle.
calls.
This reason code occurs only on Windows and z/OS.
2354 (X'0932') MQRC_UOW_ENLISTMENT_ERROR
Explanation: This reason code can occur for a variety
Programmer Response: Check that the “MTS of reasons. The most likely reason is that an object
Transaction Support” attribute defined for the object’s created by a DTC transaction does not issue a
class is set correctly. If necessary, modify the transactional MQI call until after the DTC transaction
application so that the connection handle is not used by has timed out. (If the DTC transaction times out after a
objects participating in different units of work. transactional MQI call has been issued, reason code
MQRC_HANDLE_IN_USE_FOR_UOW is returned by
the failing MQI call.)
2352 (X'0930') MQRC_LOCAL_UOW_CONFLICT
Another cause of MQRC_UOW_ENLISTMENT_ERROR
Explanation: An attempt was made to use inside a is incorrect installation; Windows NT Service pack must
global unit of work a connection handle that is be installed after the Windows NT Option pack.
participating in a queue-manager coordinated local unit
of work. This can occur when an application passes This reason code occurs only on Windows.
connection handles between objects where one object is
involved in a DTC transaction and the other is not.
Programmer Response: Check the DTC “Transaction
timeout” value. If necessary, verify the NT installation
calls.
order.
This reason code occurs only on Windows and z/OS.
Programmer Response: Check that the “MTS

2355 (X'0933') 2357 (X'0935') MQRC_CURRENT_RECORD_ERROR

MQRC_UOW_MIX_NOT_SUPPORTED
Explanation: An MQXCLWLN call was issued from a
Explanation: The mixture of calls used by the cluster workload exit to obtain the address of the next
application to perform operations within a unit of work record in the chain, but the address specified by the
is not supported. In particular, it is not possible to mix CurrentRecord parameter is not the address of a valid
within the same process a local unit of work record. CurrentRecord must be the address of a
coordinated by the queue manager with a global unit destination record (MQWDR), queue record (MQWQR),
of work coordinated by DTC (Distributed Transaction or cluster record (MQWCR) residing within the cluster
Coordinator). cache.
An application may cause this mixture to arise if some Completion Code: MQCC_FAILED
objects in a package are coordinated by DTC and others
Programmer Response: Ensure that the cluster
are not. It can also occur if transactional MQI calls from
workload exit passes the address of a valid record
an MTS client are mixed with transactional MQI calls
residing in the cluster cache.
from a library package transactional MTS object.
No problem arises if all transactional MQI calls
2358 (X'0936') MQRC_NEXT_OFFSET_ERROR
originate from transactional MTS objects, or all
transactional MQI calls originate from nontransactional Explanation: An MQXCLWLN call was issued from a
MTS objects. But when a mixture of styles is used, the cluster workload exit to obtain the address of the next
first style used fixes the style for the unit of work, and record in the chain, but the offset specified by the
subsequent attempts to use the other style within the NextOffset parameter is not valid. NextOffset must be
process fail with reason code the value of one of the following fields:
MQRC_UOW_MIX_NOT_SUPPORTED. v ChannelDefOffset field in MQWDR
v ClusterRecOffset field in MQWDR
When an application is run twice, scheduling factors in
v ClusterRecOffset field in MQWQR
the operating system mean that it is possible for the
v ClusterRecOffset field in MQWCR
queue-manager-coordinated transactional calls to fail in
one run, and for the DTC-coordinated transactional Completion Code: MQCC_FAILED
calls to fail in the other run.
Programmer Response: Ensure that the value
This reason code occurs only on Windows when specified for the NextOffset parameter is the value of
running a version of the queue manager prior to one of the fields listed above.
version 5.2.
Completion Code: MQCC_FAILED 2359 (X'0937') MQRC_NO_RECORD_AVAILABLE
Programmer Response: Check that the “MTS Explanation: An MQXCLWLN call was issued from a
Transaction Support” attribute defined for the object’s cluster workload exit to obtain the address of the next
class is set correctly. If necessary, modify the record in the chain, but the current record is the last
application so that objects executing within different record in the chain.
units of work do not try to use the same connection
handle. Completion Code: MQCC_FAILED
Programmer Response: None.
2356 (X'0934') MQRC_WXP_ERROR
Explanation: An MQXCLWLN call was issued from a 2360 (X'0938')
cluster workload exit to obtain the address of the next MQRC_OBJECT_LEVEL_INCOMPATIBLE
record in the chain, but the workload exit parameter Explanation: An MQOPEN or MQPUT1 call, or a
structure ExitParms is not valid, for one of the command, was issued, but the definition of the object
following reasons: to be accessed is not compatible with the queue
v The parameter pointer is not valid. (It is not always manager to which the application has connected. The
possible to detect parameter pointers that are not object definition was created or modified by a different
valid; if not detected, unpredictable results occur.) version of the queue manager.
v The StrucId field is not MQWXP_STRUC_ID.
v The Version field is not MQWXP_VERSION_2. If the object to be accessed is a queue, the incompatible
v The CacheContext field does not contain the value object definition could be the object specified, or one of
passed to the exit by the queue manager. the object definitions used to resolve the specified
object (for example, the base queue to which an alias
Completion Code: MQCC_FAILED queue resolves, or the transmission queue to which a
Programmer Response: Ensure that the parameter remote queue or queue-manager alias resolves).
specified for ExitParms is the MQWXP structure that This reason code occurs only on z/OS.
was passed to the exit when the exit was invoked.


2363 (X'093B') MQRC_MSG_NOT_MATCHED
Programmer Response: The application must be run
Explanation: This reason code occurs only in the
on a queue manager that is compatible with the object
Reason field in an MQDLH structure, or in the Feedback
definition. Refer to the WebSphere MQ for z/OS Concepts
field in the MQMD of a report message.
and Planning Guide and the WebSphere MQ for z/OS
System Setup Guide for information about compatibility While performing Point-to-Point messaging, JMS
and migration between different versions of the queue encountered a message matching none of the selectors
manager. of ConnectionConsumers monitoring the queue. To
maintain performance, the message was processed as
specified by the disposition options in the Report field
2361 (X'0939') MQRC_NEXT_RECORD_ERROR
in the MQMD of the message.
Explanation: An MQXCLWLN call was issued from a
If the Report field specifies one of the
cluster workload exit to obtain the address of the next
MQRO_EXCEPTION_* options, this reason code
record in the chain, but the address specified for the
appears in the Feedback field of the report message. If
NextRecord parameter is either null, not valid, or the
the Report field specifies MQRO_DEAD_LETTER_Q, or
address of read-only storage. (It is not always possible
the disposition report options are left as default, this
to detect parameter pointers that are not valid; if not
reason code appears in the Reason field of the MQDLH.
Completion Code: None
Programmer Response: To correct this, ensure that the
Programmer Response: Specify a valid address for the
ConnectionConsumers monitoring the queue provide a
NextRecord parameter.
complete set of selectors. Alternatively, set the
QueueConnectionFactory to retain messages.
2362 (X'093A')
MQRC_BACKOUT_THRESHOLD_REACHED
2364 (X'093C') MQRC_JMS_FORMAT_ERROR
Explanation: This reason code occurs only in the
Explanation: This reason code is generated when JMS
Reason field in an MQDLH structure, or in the Feedback
encounters a message that it is unable to parse. If such
field in the MQMD of a report message.
a message is encountered by a JMS
A JMS ConnectionConsumer found a message that ConnectionConsumer, the message is processed as
exceeds the queue’s backout threshold. The queue does specified by the disposition options in the Report field
not have a backout requeue queue defined, so the in the MQMD of the message.
message was processed as specified by the disposition
options in the Report field in the MQMD of the
message.
appears in the Feedback field of the report message. If
On queue managers that do not support the the Report field specifies MQRO_DEAD_LETTER_Q, or
BackoutThreshold and BackoutRequeueQName queue the disposition report options are left as default, this
attributes, JMS ConnectionConsumer uses a value of 20 reason code appears in the Reason field of the MQDLH.
for the backout threshold. When the BackoutCount of a
Completion Code: None
message reaches this threshold, the message is
processed as specified by the disposition options. Programmer Response: Investigate the origin of the
message.
appears in the Feedback field of the report message. If 2365 (X'093D')
the Report field specifies MQRO_DEAD_LETTER_Q, or MQRC_SEGMENTS_NOT_SUPPORTED
the disposition report options are left as default, this
Explanation: An MQPUT call was issued to put a
reason code appears in the Reason field of the MQDLH.
segment of a logical message, but the queue on which
Completion Code: None the message is to be placed has an IndexType of
MQIT_GROUP_ID. Message segments cannot be placed
Programmer Response: Investigate the cause of the
on queues with this index type.
backout count being greater than the threshold. To
correct this, define the backout queue for the queue This reason code occurs only on z/OS.
concerned.
Programmer Response: Modify the application to put
messages that are not segments; ensure that the
MQMF_SEGMENT and MQMF_LAST_SEGMENT flags
in the MsgFlags field in MQMD are not set, and that

the Offset is zero. Alternatively, change the index type Programmer Response: None. This reason code is
of the queue. only used to identify the corresponding event message.
2366 (X'093E') MQRC_WRONG_CF_LEVEL 2373 (X'0945') MQRC_CF_STRUC_FAILED

Explanation: An MQOPEN or MQPUT1 call was 1 Explanation: An MQI call or command was issued to
issued specifying a shared queue, but the queue 1 access a shared queue, but the call failed because the
requires a coupling-facility structure with a different 1 coupling-facility structure used for the shared queue
level of capability. 1 had failed.
This reason code occurs only on z/OS. 1 This reason code occurs only on z/OS.
Programmer Response: Ensure that the Programmer Response: Report the problem to the
coupling-facility structure used for the queue is at the operator or administrator, who should use the MQSC
level required to support the capabilities that the queue command RECOVER CFSTRUCT to initiate recovery of
provides. the coupling-facility structure
2367 (X'093F') MQRC_CONFIG_CREATE_OBJECT 2374 (X'0946') MQRC_API_EXIT_ERROR

Explanation: This condition is detected when an object Explanation: An API exit function returned an invalid
is created. response code, or failed in some other way.
Completion Code: MQCC_WARNING This reason code occurs in the following environments:
AIX, HP-UX, Solaris, Windows.
only used to identify the corresponding event message. Completion Code: MQCC_FAILED
Programmer Response: Check the exit logic to ensure
2368 (X'0940') MQRC_CONFIG_CHANGE_OBJECT that the exit is returning valid values in the
ExitResponse and ExitResponse2 fields of the MQAXP
Explanation: This condition is detected when an object
structure. Consult the FFST record to see if it contains
is changed.
more detail about the problem.
Programmer Response: None. This reason code is 2375 (X'0947') MQRC_API_EXIT_INIT_ERROR
Explanation: The queue manager encountered an error
while attempting to initialize the execution
2369 (X'0941') MQRC_CONFIG_DELETE_OBJECT environment for an API exit function.
Explanation: This condition is detected when an object This reason code occurs in the following environments:
is deleted. AIX, HP-UX, Solaris, Windows.
Completion Code: MQCC_WARNING Completion Code: MQCC_FAILED
Programmer Response: None. This reason code is Programmer Response: Consult the FFST record to
only used to identify the corresponding event message. obtain more detail about the problem.
2370 (X'0942') MQRC_CONFIG_REFRESH_OBJECT 2376 (X'0948') MQRC_API_EXIT_TERM_ERROR

Explanation: This condition is detected when an object Explanation: The queue manager encountered an error
is refreshed. while attempting to terminate the execution
environment for an API exit function.
Programmer Response: None. This reason code is AIX, HP-UX, Solaris, Windows.
2371 (X'0943') MQRC_CHANNEL_SSL_ERROR Programmer Response: Consult the FFST record to
obtain more detail about the problem.
connection cannot be established due to an SSL
key-exchange or authentication failure.

specified by one of the following:

2377 (X'0949') MQRC_EXIT_REASON_ERROR
v The value of the MQSSLKEYR environment variable
Explanation: An MQXEP call was issued by an API (MQCONN or MQCONNX call), or
exit function, but the value specified for the ExitReason
v The value of the KeyRepository field in the MQSCO
parameter is either not valid, or not supported for the
structure (MQCONNX call only).
specified function identifier Function.
This reason code occurs in the following environments: For the MQCONNX call, if both MQSSLKEYR and
AIX, HP-UX, Solaris, Windows. KeyRepository are specified, the latter is used.
Programmer Response: Modify the exit function to AIX, HP-UX, Solaris, Windows.
specify a value for ExitReason that is valid for the
specified value of Function. Completion Code: MQCC_FAILED
Programmer Response: Specify a valid location for the
2378 (X'094A') MQRC_RESERVED_VALUE_ERROR key repository.
Explanation: An MQXEP call was issued by an API

exit function, but the value specified for the Reserved 2382 (X'094E')
parameter is not valid. The value must be the null MQRC_CRYPTO_HARDWARE_ERROR
pointer. Explanation: On an MQCONN or MQCONNX call,
This reason code occurs in the following environments: the configuration string for the cryptographic hardware
AIX, HP-UX, Solaris, Windows. is not valid, or results in an error when used to
configure the cryptographic hardware. The
Completion Code: MQCC_FAILED configuration string is specified by one of the
following:
Programmer Response: Modify the exit to specify the
null pointer as the value of the Reserved parameter. v The value of the MQSSLCRYP environment variable
(MQCONN or MQCONNX call), or
v The value of the CryptoHardware field in the MQSCO
2379 (X'094B') MQRC_NO_DATA_AVAILABLE
structure (MQCONNX call only).
Explanation: This reason should be returned by the
MQZ_ENUMERATE_AUTHORITY_DATA installable For the MQCONNX call, if both MQSSLCRYP and
service component when there is no more authority CryptoHardware are specified, the latter is used.
data to return to the invoker of the service component.
v On z/OS, this reason code does not occur. This reason code occurs in the following environments:
Programmer Response: None.
Programmer Response: Specify a valid configuration
string for the cryptographic hardware.
2380 (X'094C') MQRC_SCO_ERROR
Explanation: On an MQCONNX call, the MQSCO 2383 (X'094F')
structure is not valid for one of the following reasons: MQRC_AUTH_INFO_REC_COUNT_ERROR
v The StrucId field is not MQSCO_STRUC_ID.
v The Version field is not MQSCO_VERSION_1. AuthInfoRecCount field in the MQSCO structure
specifies a value that is less than zero.
AIX, HP-UX, Solaris, Windows. This reason code occurs in the following environments:
Programmer Response: Correct the definition of the
MQSCO structure. Programmer Response: Specify a value for
AuthInfoRecCount that is zero or greater.
2381 (X'094D') MQRC_KEY_REPOSITORY_ERROR

2384 (X'0950') MQRC_AUTH_INFO_REC_ERROR
Explanation: On an MQCONN or MQCONNX call,
the location of the key repository is either not specified, Explanation: On an MQCONNX call, the MQSCO
not valid, or results in an error when used to access the structure does not specify the address of the MQAIR
key repository. The location of the key repository is records correctly. One of the following applies:

v AuthInfoRecCount is greater than zero, but

2388 (X'0954') MQRC_LDAP_USER_NAME_ERROR
AuthInfoRecOffset is zero and AuthInfoRecPtr is the
null pointer. Explanation: On an MQCONNX call, an LDAP user
v AuthInfoRecOffset is not zero and AuthInfoRecPtr is name in an MQAIR record is not specified correctly.
not the null pointer. One of the following applies:
v AuthInfoRecPtr is not a valid pointer. v LDAPUserNameLength is greater than zero, but
LDAPUserNameOffset is zero and LDAPUserNamePtr is
v AuthInfoRecOffset or AuthInfoRecPtr points to
the null pointer.
storage that is not accessible.
v LDAPUserNameOffset is nonzero and LDAPUserNamePtr
This reason code occurs in the following environments: is not the null pointer.
AIX, HP-UX, Solaris, Windows. v LDAPUserNamePtr is not a valid pointer.
Completion Code: MQCC_FAILED v LDAPUserNameOffset or LDAPUserNamePtr points to
storage that is not accessible.
Programmer Response: Ensure that one of
AuthInfoRecOffset or AuthInfoRecPtr is zero and the This reason code occurs in the following environments:
other nonzero. Ensure that the field used points to AIX, HP-UX, Solaris, Windows.
accessible storage.
2385 (X'0951') MQRC_AIR_ERROR Programmer Response: Ensure that one of

LDAPUserNameOffset or LDAPUserNamePtr is zero and the
Explanation: On an MQCONNX call, an MQAIR other nonzero. Ensure that the field used points to
record is not valid for one of the following reasons: accessible storage.
v The StrucId field is not MQAIR_STRUC_ID.
v The Version field is not MQAIR_VERSION_1. 2389 (X'0955')
MQRC_LDAP_USER_NAME_LENGTH_ERR
AIX, HP-UX, Solaris, Windows. Explanation: On an MQCONNX call, the
LDAPUserNameLength field in an MQAIR record specifies
Completion Code: MQCC_FAILED a value that is less than zero.
Programmer Response: Correct the definition of the This reason code occurs in the following environments:
MQAIR record. AIX, HP-UX, Solaris, Windows.
2386 (X'0952') MQRC_AUTH_INFO_TYPE_ERROR
Programmer Response: Specify a value for
Explanation: On an MQCONNX call, the LDAPUserNameLength that is zero or greater.
AuthInfoType field in an MQAIR record specifies a
value that is not valid.
2390 (X'0956') MQRC_LDAP_PASSWORD_ERROR
AIX, HP-UX, Solaris, Windows. Explanation: On an MQCONNX call, the
LDAPPassword field in an MQAIR record specifies a
Completion Code: MQCC_FAILED value when no value is allowed.
Programmer Response: Specify MQAIT_CRL_LDAP This reason code occurs in the following environments:
for AuthInfoType. AIX, HP-UX, Solaris, Windows.
2387 (X'0953')
MQRC_AUTH_INFO_CONN_NAME_ERROR Programmer Response: Specify a value that is blank
or null.
AuthInfoConnName field in an MQAIR record specifies a
value that is not valid. 2391 (X'0957') MQRC_SSL_ALREADY_INITIALIZED
This reason code occurs in the following environments: Explanation: An MQCONN or MQCONNX call was
AIX, HP-UX, Solaris, Windows. issued with SSL configuration options specified, but the
SSL environment had already been initialized. The
Completion Code: MQCC_FAILED connection to the queue manager completed
successfully, but the SSL configuration options specified
Programmer Response: Specify a valid connection
on the call were ignored; the existing SSL environment
name.
was used instead.

AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED

Completion Code: MQCC_WARNING Programmer Response: Redefine the queue to have an
IndexType of MQIT_GROUP_ID. Alternatively, modify
Programmer Response: If the application must be run
the application to avoid using the options listed above.
with the SSL configuration options defined on the
MQCONN or MQCONNX call, use the MQDISC call to
sever the connection to the queue manager and then 1 2395 (X'095B') MQRC_CFBS_ERROR
terminate the application. Alternatively run the
application later when the SSL environment has not
1 Explanation: An MQPUT or MQPUT1 call was issued,
been initialized.
1 but the message data contains an MQCFBS structure
1 that is not valid.
1 This reason code occurs in the following environments:
2392 (X'0958') MQRC_SSL_CONFIG_ERROR
1 AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus
Explanation: On an MQCONNX call, the MQCNO 1 WebSphere MQ clients connected to these systems.
structure does not specify the MQSCO structure
correctly. One of the following applies:
v SSLConfigOffset is nonzero and SSLConfigPtr is not 1 Programmer Response: Check that the fields in the
the null pointer. 1 structure are set correctly.
v SSLConfigPtr is not a valid pointer.
v SSLConfigOffset or SSLConfigPtr points to storage 2396 (X'095C') MQRC_SSL_NOT_ALLOWED
that is not accessible. Explanation: A connection to a queue manager was
requested, specifying SSL encryption. However, the
This reason code occurs in the following environments: connection mode requested is one that does not
AIX, HP-UX, Solaris, Windows. support SSL (for example, bindings connect).
Completion Code: MQCC_FAILED This reason code occurs only with Java applications.
Programmer Response: Ensure that one of Completion Code: MQCC_FAILED
SSLConfigOffset or SSLConfigPtr is zero and the other
nonzero. Ensure that the field used points to accessible Programmer Response: Modify the application to
storage. request client connection mode, or to disable SSL
encryption.
2393 (X'0959')
MQRC_SSL_INITIALIZATION_ERROR 2397 (X'095D') MQRC_JSSE_ERROR
Explanation: An MQCONN or MQCONNX call was Explanation: JSSE reported an error (for example,
issued with SSL configuration options specified, but an while connecting to a queue manager using SSL
error occurred during the initialization of the SSL encryption). The MQException object containing this
environment. reason code references the Exception thrown by JSSE;
this can be obtained by using the
This reason code occurs in the following environments: MQException.getCause() method. From JMS, the
AIX, HP-UX, Solaris, Windows. MQException is linked to the thrown JMSException.
Completion Code: MQCC_FAILED This reason code occurs only with Java applications.
Programmer Response: Check that the SSL installation Completion Code: MQCC_FAILED
is correct.
Programmer Response: Inspect the causal exception to
determine the JSSE error.
2394 (X'095A') MQRC_Q_INDEX_TYPE_ERROR
Explanation: An MQGET call was issued specifying 2398 (X'095E')
one or more of the following options: MQRC_SSL_PEER_NAME_MISMATCH
MQGMO_ALL_MSGS_AVAILABLE
MQGMO_ALL_SEGMENTS_AVAILABLE Explanation: The application attempted to connect to
MQGMO_COMPLETE_MSG the queue manager using SSL encryption, but the
MQGMO_LOGICAL_ORDER distinguished name presented by the queue manager
does not match the specified pattern.
but the call failed because the queue is not indexed by
group identifier. These options require the queue to This reason code occurs only with Java applications.
have an IndexType of MQIT_GROUP_ID. Completion Code: MQCC_FAILED
This reason code occurs only on z/OS. Programmer Response: Check the certificates used to
identify the queue manager. Also check the value of the

sslPeerName property specified by the application. exception is a java.lang.NoSuchElementException,

ensure that your application is not specifying an empty
collection of CertStore objects.
2399 (X'095F') MQRC_SSL_PEER_NAME_ERROR
Explanation: The application specified a peer name of
1 2406 (X'0966') MQRC_CLIENT_EXIT_LOAD_ERROR
incorrect format.
1 Explanation: The external user exit required for a
This reason code occurs only with Java applications.
1 client connection could not be loaded because the
Completion Code: MQCC_FAILED 1 shared library specified for it cannot be found, or the
1 entry point specified for it cannot be found.
Programmer Response: Check the value of the
sslPeerName property specified by the application. 1 This reason code occurs only with Java applications.
2400 (X'0960')
1 Programmer Response: Ensure that the correct library
MQRC_UNSUPPORTED_CIPHER_SUITE
1 has been specified, and that the path variable for the
Explanation: A connection to a queue manager was 1 machine environment includes the relevant directory.
requested, specifying SSL encryption. However, JSSE 1 Ensure also that the entry point has been named
reported that it does not support the CipherSuite 1 properly and that the named library does export it.
specified by the application.
This reason code occurs only with Java applications. 1 2407 (X'0967') MQRC_CLIENT_EXIT_ERROR
Completion Code: MQCC_FAILED 1 Explanation: A failure occured while executing a
1 non-Java user exit for a client connection.
Programmer Response: Check the CipherSuite
specified by the application. Note that the names of 1 This reason code occurs only with Java applications.
JSSE CipherSuites differ from their equivalent
CipherSpecs used by the queue manager.
1 Programmer Response: Check that the non-Java user
Also, check that JSSE is correctly installed.
1 exit can accept the parameters and message being
1 passed to it and that it can handle error conditions, and
2401 (X'0961') 1 that any information that the exit requires, such as user
MQRC_SSL_CERTIFICATE_REVOKED 1 data, is correct and available.
Explanation: A connection to a queue manager was
requested, specifying SSL encryption. However, the 1 2409 (X'0969') MQRC_SSL_KEY_RESET_ERROR
certificate presented by the queue manager was found
1 Explanation: On an MQCONN or MQCONNX call,
to be revoked by one of the specified CertStores.
1 the value of the SSL key reset count is not in the valid
This reason code occurs only with Java applications. 1 range of 0 through 999 999 999.
Completion Code: MQCC_FAILED 1 The value of the SSL key reset count is specified by
1 either the value of the MQSSLRESET environment
Programmer Response: Check the certificates used to 1 variable (MQCONN or MQCONNX call), or the value
identify the queue manager. 1 of the KeyResetCount field in the MQSCO structure
1 (MQCONNX call only). For the MQCONNX call, if
2402 (X'0962') MQRC_SSL_CERT_STORE_ERROR 1 both MQSSLRESET and KeyResetCount are specified,
1 the latter is used. MQCONN or MQCONNX
Explanation: A connection to a queue manager was
requested, specifying SSL encryption. However, none of 1 Completion Code: MQCC_FAILED
the CertStore objects provided by the application could 1 Programmer Response: Check that the fields in the
be searched for the certificate presented by the queue 1 structure and the MQSSLRESET environment variable
manager. The MQException object containing this 1 are set correctly.
reason code references the Exception encountered when
searching the first CertStore; this can be obtained using
the MQException.getCause() method. From JMS, the 1 2411 (X'096B') MQRC_LOGGER_STATUS
MQException is linked to the thrown JMSException.
1 Explanation: This condition is detected when a logger
This reason code occurs only with Java applications. 1 event occurs.
Completion Code: MQCC_FAILED 1 Completion Code: MQCC_WARNING
Programmer Response: Inspect the causal exception to 1 Programmer Response: None. This reason code is
determine the underlying error. Check the CertStore 1 only used to identify the corresponding event message.
objects provided by your application. If the causal

1 2412 (X'096C') MQRC_COMMAND_MQSC 1 2417 (X'0971')

1 MQRC_MSG_NOT_ALLOWED_IN_GROUP
1 Explanation: This condition is detected when an
1 MQSC command is executed. 1 Explanation: An MQPUT or MQPUT1 call was issued
1 to put a message in a group but it is not valid to put
1 Completion Code: MQCC_WARNING 1 such a message in a group. An example of an invalid
1 Programmer Response: None. This reason code is 1 message is a PCF message where the Type is
1 only used to identify the corresponding event message. 1 MQCFT_TRACE_ROUTE.
1 2413 (X'096D') MQRC_COMMAND_PCF 1 Programmer Response: Remove the invalid message
1 Explanation: This condition is detected when a PCF 1 from the group.
1 command is executed.
1 Completion Code: MQCC_WARNING 1 2418 (X'0972') MQRC_FILTER_OPERATOR_ERROR
1 Programmer Response: None. This reason code is 1 Explanation: The Operator parameter supplied is not
1 only used to identify the corresponding event message. 1 valid.
1 If it is an input variable then the value is not one of the
1 2414 (X'096E') MQRC_CFIF_ERROR 1 MQCFOP_* constant values. If it is an output variable
1 then the parameter pointer is not valid, or it points to
1 Explanation: An MQPUT or MQPUT1 call was issued, 1 read-only storage. (It is not always possible to detect
1 but the message data contains an MQCFIF structure 1 parameter pointers that are not valid; if not detected,
1 that is not valid. 1 unpredicatable results occur.)
1 This reason code occurs in the following environments: 1 Completion Code: MQCC_FAILED
1 AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows,
1 plus WebSphere MQ clients connected to these systems. 1 Programmer Response: Correct the parameter.
1 2419 (X'0973') MQRC_NESTED_SELECTOR_ERROR
1 Programmer Response: Check that the fields in the
1 structure are set correctly. 1 Explanation: An mqAddBag call was issued, but the
1 bag to be nested contained a data item with an
1 inconsistent selector. This reason only occurs if the bag
1 2415 (X'096F') MQRC_CFSF_ERROR 1 into which the nested bag was to be added was created
1 Explanation: An MQPUT or MQPUT1 call was issued, 1 with the MQCBO_CHECK_SELECTORS option.
1 but the message data contains an MQCFSF structure 1 Completion Code: MQCC_FAILED
1 Programmer Response: Ensure that all data items
1 This reason code occurs in the following environments: 1 within the bag to be nested have selectors that are
1 AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, 1 consistent with the data type implied by the item.
1 plus WebSphere MQ clients connected to these systems.
1 Completion Code: MQCC_FAILED 1 2420 (X'0974') MQRC_EPH_ERROR
1 Programmer Response: Check that the fields in the 1 Explanation: An MQPUT or MQPUT1 call was issued,
1 structure are set correctly. 1 but the message data contains an MQEPH structure
1 that is not valid. Possible errors include the following:
1 2416 (X'0970') MQRC_CFGR_ERROR 1 v The StrucId field is not MQEPH_STRUC_ID.
1 v The Version field is not MQEPH_VERSION_1.
1 Explanation: An MQPUT or MQPUT1 call was issued, 1 v The StrucLength field specifies a value that is too
1 but the message data contains an MQCFGR structure 1 small to include the structure plus the
1 that is not valid. 1 variable-length data at the end of the structure.
1 This reason code occurs in the following environments: 1 v The CodedCharSetId field is zero, or a negative value
1 AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, 1 that is not valid.
1 plus WebSphere MQ clients connected to these systems. 1 v The Flags field contains an invalid combination of
1 MQEPH_* values.
1 Completion Code: MQCC_FAILED 1 v The BufferLength parameter of the call has a value
1 Programmer Response: Check that the fields in the 1 that is too small to accommodate the structure, so the
1 structure are set correctly. 1 structure extends beyond the end of the message.

1 structure are set correctly. Ensure that the application This reason code occurs in the WebSphere MQ C++
1 sets the CodedCharSetId field to a valid value; note that environment.
1 MQCCSI_DEFAULT, MQCCSI_EMBEDDED,
1 MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not
1 valid in this field. Programmer Response: Set the open options explicitly
to cover all eventualities so that implicit reopening is
not required.
1 2421 (X'0975') MQRC_RFH_FORMAT_ERROR
1 Explanation: The message contains an MQRFH
6101 (X'17D5') MQRC_REOPEN_INQUIRE_ERROR
1 structure, but its format is incorrect. If you are using
1 WebSphere MQ SOAP, the error is in an incoming Explanation: An open object does not have the correct
1 SOAP/MQ request message. ImqObject open options and requires one or more
additional options. An implicit reopen is required but
closure has been prevented.
1 Programmer Response: If you are using WebSphere
Closure has been prevented because one or more
1 MQ SOAP with the IBM-supplied sender, contact your
characteristics of the object need to be checked
1 IBM support center. If you are using WebSphere MQ
dynamically prior to closure, and the open options do
1 SOAP with a bespoke sender, check that the RFH2
not already include MQOO_INQUIRE.
1 section of the SOAP/MQ request message is in valid
1 RFH2 format. This reason code occurs in the WebSphere MQ C++
environment.
1 2422 (X'0976') MQRC_CFBF_ERROR Completion Code: MQCC_FAILED
1 Explanation: An MQPUT or MQPUT1 call was issued, Programmer Response: Set the open options explicitly
1 but the message data contains an MQCFBF structure to include MQOO_INQUIRE.
1 This reason code occurs in the following environments: 6102 (X'17D6')
1 AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus MQRC_REOPEN_SAVED_CONTEXT_ERR
1 WebSphere MQ clients connected to these systems.
Explanation: An open object does not have the correct
1 Completion Code: MQCC_FAILED ImqObject open options and requires one or more
additional options. An implicit reopen is required but
1 structure are set correctly.
Closure has been prevented because the queue is open
with MQOO_SAVE_ALL_CONTEXT, and a destructive
1 2423 (X'0977')
get has been performed previously. This has caused
1 MQRC_CLIENT_CHANNEL_CONFLICT
retained state information to be associated with the
1 Explanation: A client channel definition table was open queue and this information would be destroyed
1 specified for determining the name of the channel, but by closure.
1 the name has already been defined.
This reason code occurs in the WebSphere MQ C++
1 This reason code occurs only with Java applications. environment.
1 Completion Code: MQCC_FAILED Completion Code: MQCC_FAILED
1 Programmer Response: Change the channel name to Programmer Response: Set the open options explicitly
1 blank and try again. to cover all eventualities so that implicit reopening is
not required.
6100 (X'17D4')
MQRC_REOPEN_EXCL_INPUT_ERROR 6103 (X'17D7')
MQRC_REOPEN_TEMPORARY_Q_ERROR
Explanation: An open object does not have the correct
ImqObject open options and requires one or more Explanation: An open object does not have the correct
additional options. An implicit reopen is required but ImqObject open options and requires one or more
closure has been prevented. additional options. An implicit reopen is required but
Closure has been prevented because the queue is open
for exclusive input and closure might result in the Closure has been prevented because the queue is a
queue being accessed by another process or thread, local queue of the definition type
before the queue is reopened by the process or thread MQQDT_TEMPORARY_DYNAMIC, that would be
that presently has access. destroyed by closure.

This reason code occurs in the WebSphere MQ C++ This reason code occurs in the WebSphere MQ C++
environment. environment.
Programmer Response: Set the open options explicitly
to cover all eventualities so that implicit reopening is 6108 (X'17DC') MQRC_NULL_POINTER
not required.
Explanation: A null pointer has been supplied where
a nonnull pointer is either required or implied.
6104 (X'17D8') MQRC_ATTRIBUTE_LOCKED
Explanation: An attempt has been made to change the environment.
value of an attribute of an object while that object is
open, or, for an ImqQueueManager object, while that
object is connected. Certain attributes cannot be
changed in these circumstances. Close or disconnect the 6109 (X'17DD')
object (as appropriate) before changing the attribute MQRC_NO_CONNECTION_REFERENCE
value.
Explanation: The connection reference is null. A
An object may have been connected and/or opened connection to an ImqQueueManager object is required.
unexpectedly and implicitly in order to perform an
MQINQ call. Check the attribute cross-reference table This reason code occurs in the WebSphere MQ C++
in the WebSphere MQ Using C++ book to determine environment.
whether any of your method invocations result in an Completion Code: MQCC_FAILED
MQINQ call.
This reason code occurs in the WebSphere MQ C++ 6110 (X'17DE') MQRC_NO_BUFFER
environment.
Explanation: No buffer is available. For an ImqCache
Completion Code: MQCC_FAILED object, one cannot be allocated, denoting an internal
Programmer Response: Include MQOO_INQUIRE in inconsistency in the object state that should not occur.
the ImqObject open options and set them earlier. This reason code occurs in the WebSphere MQ C++
environment.
6105 (X'17D9') MQRC_CURSOR_NOT_VALID Completion Code: MQCC_FAILED
Explanation: The browse cursor for an open queue
has been invalidated since it was last used by an 6111 (X'17DF')
implicit reopen. MQRC_BINARY_DATA_LENGTH_ERROR
This reason code occurs in the WebSphere MQ C++ Explanation: The length of the binary data is
environment. inconsistent with the length of the target attribute. Zero
Completion Code: MQCC_FAILED is a correct length for all attributes.
v The correct length for an accounting token is
Programmer Response: Set the ImqObject open MQ_ACCOUNTING_TOKEN_LENGTH.
options explicitly to cover all eventualities so that
implicit reopening is not required. v The correct length for an alternate security id is
MQ_SECURITY_ID_LENGTH.
v The correct length for a correlation id is
6106 (X'17DA') MQRC_ENCODING_ERROR MQ_CORREL_ID_LENGTH.
Explanation: The encoding of the (next) message item v The correct length for a facility token is
needs to be MQENC_NATIVE for pasting. MQ_FACILITY_LENGTH.
This reason code occurs in the WebSphere MQ C++ v The correct length for a group id is
environment. MQ_GROUP_ID_LENGTH.
v The correct length for a message id is
MQ_MSG_ID_LENGTH.
v The correct length for an instance id is
6107 (X'17DB') MQRC_STRUC_ID_ERROR MQ_OBJECT_INSTANCE_ID_LENGTH.
Explanation: The structure id for the (next) message v The correct length for a transaction instance id is
item, which is derived from the 4 characters beginning MQ_TRAN_INSTANCE_ID_LENGTH.
at the data pointer, is either missing or is inconsistent v The correct length for a message token is
with the class of object into which the item is being MQ_MSG_TOKEN_LENGTH.
pasted.


6117 (X'17E5') MQRC_NEGATIVE_LENGTH
environment.
Explanation: A negative length has been supplied
where a zero or positive length is required.
6112 (X'17E0') MQRC_BUFFER_NOT_AUTOMATIC
environment.
Explanation: A user-defined (and managed) buffer
cannot be resized. A user-defined buffer can only be
replaced or withdrawn. A buffer must be automatic
(system-managed) before it can be resized. 6118 (X'17E6') MQRC_NEGATIVE_OFFSET
This reason code occurs in the WebSphere MQ C++ Explanation: A negative offset has been supplied
environment. where a zero or positive offset is required.
Completion Code: MQCC_FAILED This reason code occurs in the WebSphere MQ C++
environment.
Programmer Response:
6113 (X'17E1') MQRC_INSUFFICIENT_BUFFER
6119 (X'17E7') MQRC_INCONSISTENT_FORMAT
Explanation: There is insufficient buffer space
available after the data pointer to accommodate the Explanation: The format of the (next) message item is
request. This might be because the buffer cannot be inconsistent with the class of object into which the item
resized. is being pasted.
This reason code occurs in the WebSphere MQ C++ This reason code occurs in the WebSphere MQ C++
environment. environment.
6114 (X'17E2') MQRC_INSUFFICIENT_DATA 6120 (X'17E8')

MQRC_INCONSISTENT_OBJECT_STATE
Explanation: There is insufficient data after the data
pointer to accommodate the request. Explanation: There is an inconsistency between this
object, which is open, and the referenced
ImqQueueManager object, which is not connected.
environment.
environment.
6115 (X'17E3') MQRC_DATA_TRUNCATED
Explanation: Data has been truncated when copying
6121 (X'17E9')
from one buffer to another. This might be because the
MQRC_CONTEXT_OBJECT_NOT_VALID
target buffer cannot be resized, or because there is a
problem addressing one or other buffer, or because a Explanation: The ImqPutMessageOptions context
buffer is being downsized with a smaller replacement. reference does not reference a valid ImqQueue object.
The object has been previously destroyed.
environment. This reason code occurs in the WebSphere MQ C++
environment.
6116 (X'17E4') MQRC_ZERO_LENGTH
6122 (X'17EA') MQRC_CONTEXT_OPEN_ERROR
Explanation: A zero length has been supplied where a
positive length is either required or implied. Explanation: The ImqPutMessageOptions context
reference references an ImqQueue object that could not
be opened to establish a context. This may be because
environment.
the ImqQueue object has inappropriate open options.
Completion Code: MQCC_FAILED Inspect the referenced object reason code to establish
the cause.
environment.

Completion Code: MQCC_FAILED reopened implicitly because the IMQ_IMPL_OPEN flag

of the ImqObject behavior class attribute is false.
6123 (X'17EB') MQRC_STRUC_LENGTH_ERROR This reason code occurs in the WebSphere MQ C++
environment.
Explanation: The length of a data structure is
inconsistent with its content. For an MQRMH, the Completion Code: MQCC_FAILED
length is insufficient to contain the fixed fields and all
Programmer Response: Open the object with
offset data.
appropriate ImqObject open options and retry.
environment.
6128 (X'17FO') MQRC_WRONG_VERSION
Explanation: A method failed because a version
number specified or encountered is either incorrect or
6124 (X'17EC') MQRC_NOT_CONNECTED not supported.
Explanation: A method failed because a required For the ImqCICSBridgeHeader class, the problem is
connection to a queue manager was not available, and with the version attribute.
a connection cannot be established implicitly because
the IMQ_IMPL_CONN flag of the ImqQueueManager
environment.
behavior class attribute is FALSE.
environment. Programmer Response: If you are specifying a version
number, use one that is supported by the class. If you
are receiving message data from another program,
Programmer Response: Establish a connection to a ensure that both programs are using consistent and
queue manager and retry. supported version numbers.
6125 (X'17ED') MQRC_NOT_OPEN 6129 (X'17F1') MQRC_REFERENCE_ERROR

Explanation: A method failed because an object was Explanation: An object reference is invalid.
not open, and opening cannot be accomplished
There is a problem with the address of a referenced
implicitly because the IMQ_IMPL_OPEN flag of the
object. At the time of use, the address of the object is
ImqObject behavior class attribute is FALSE.
nonnull, but is invalid and cannot be used for its
This reason code occurs in the WebSphere MQ C++ intended purpose.
environment.
Completion Code: MQCC_FAILED environment.
Programmer Response: Open the object and retry. Completion Code: MQCC_FAILED
Programmer Response: Check that the referenced
6126 (X'17EE') object is neither deleted nor out of scope, or remove the
MQRC_DISTRIBUTION_LIST_EMPTY reference by supplying a null address value.
Explanation: An ImqDistributionList failed to open
because there are no ImqQueue objects referenced.
environment.
Programmer Response: Establish at least one
ImqQueue object in which the distribution list
reference addresses the ImqDistributionList object, and
retry.
6127 (X'17EF')
MQRC_INCONSISTENT_OPEN_OPTIONS
Explanation: A method failed because the object is
open, and the ImqObject open options are inconsistent
with the required operation. The object cannot be

Reason code cross reference

The following is a list of reason codes, in alphabetic order, cross referenced to the
full description in numeric order.
2129 (X'0851') MQRC_ADAPTER_CONN_LOAD_ERROR
2133 (X'0855') MQRC_ADAPTER_CONV_LOAD_ERROR
2131 (X'0853') MQRC_ADAPTER_DEFS_ERROR
2132 (X'0854') MQRC_ADAPTER_DEFS_LOAD_ERROR
2138 (X'085A') MQRC_ADAPTER_DISC_LOAD_ERROR
2204 (X'089C') MQRC_ADAPTER_NOT_AVAILABLE
2130 (X'0852') MQRC_ADAPTER_SERV_LOAD_ERROR
2127 (X'084F') MQRC_ADAPTER_STORAGE_SHORTAGE
2385 (X'0951') MQRC_AIR_ERROR
2001 (X'07D1') MQRC_ALIAS_BASE_Q_TYPE_ERROR
2002 (X'07D2') MQRC_ALREADY_CONNECTED
2103 (X'0837') MQRC_ANOTHER_Q_MGR_CONNECTED
2374 (X'0946') MQRC_API_EXIT_ERROR
2375 (X'0947') MQRC_API_EXIT_INIT_ERROR
2183 (X'0887') MQRC_API_EXIT_LOAD_ERROR
2376 (X'0948') MQRC_API_EXIT_TERM_ERROR
900 (X'0384') MQRC_APPL_FIRST
999 (X'03E7') MQRC_APPL_LAST
2157 (X'086D') MQRC_ASID_MISMATCH
6104 (X'17D8') MQRC_ATTRIBUTE_LOCKED
2387 (X'0953') MQRC_AUTH_INFO_CONN_NAME_ERROR
2383 (X'094F') MQRC_AUTH_INFO_REC_COUNT_ERROR
2384 (X'0950') MQRC_AUTH_INFO_REC_ERROR
2386 (X'0952') MQRC_AUTH_INFO_TYPE_ERROR
2003 (X'07D3') MQRC_BACKED_OUT
2362 (X'093A') MQRC_BACKOUT_THRESHOLD_REACHED
2303 (X'08FF') MQRC_BAG_CONVERSION_ERROR
2326 (X'0916') MQRC_BAG_WRONG_TYPE
6111 (X'17DF') MQRC_BINARY_DATA_LENGTH_ERROR
2134 (X'0856') MQRC_BO_ERROR
2125 (X'084D') MQRC_BRIDGE_STARTED
2126 (X'084E') MQRC_BRIDGE_STOPPED
2004 (X'07D4') MQRC_BUFFER_ERROR
2005 (X'07D5') MQRC_BUFFER_LENGTH_ERROR
6112 (X'17E0') MQRC_BUFFER_NOT_AUTOMATIC
2219 (X'08AB') MQRC_CALL_IN_PROGRESS
2277 (X'08E5') MQRC_CD_ERROR
2345 (X'0929') MQRC_CF_NOT_AVAILABLE
2348 (X'092C') MQRC_CF_STRUC_AUTH_FAILED
2349 (X'092D') MQRC_CF_STRUC_ERROR
2373 (X'0945') MQRC_CF_STRUC_FAILED
2346 (X'092A') MQRC_CF_STRUC_IN_USE
2347 (X'092B') MQRC_CF_STRUC_LIST_HDR_IN_USE
2422 (X'0976') MQRC_CFBF_ERROR
2395 (X'095B') MQRC_CFBS_ERROR
2416 (X'0970') MQRC_CFGR_ERROR
2235 (X'08BB') MQRC_CFH_ERROR
2414 (X'096E') MQRC_CFIF_ERROR
2236 (X'08BC') MQRC_CFIL_ERROR
2237 (X'08BD') MQRC_CFIN_ERROR
2415 (X'096F') MQRC_CFSF_ERROR
2238 (X'08BE') MQRC_CFSL_ERROR

2239 (X'08BF') MQRC_CFST_ERROR

2295 (X'08F7') MQRC_CHANNEL_ACTIVATED
2234 (X'08BA') MQRC_CHANNEL_AUTO_DEF_ERROR
2233 (X'08B9') MQRC_CHANNEL_AUTO_DEF_OK
2284 (X'08EC') MQRC_CHANNEL_CONV_ERROR
2296 (X'08F8') MQRC_CHANNEL_NOT_ACTIVATED
2371 (X'0943') MQRC_CHANNEL_SSL_ERROR
2282 (X'08EA') MQRC_CHANNEL_STARTED
2283 (X'08EB') MQRC_CHANNEL_STOPPED
2279 (X'08E7') MQRC_CHANNEL_STOPPED_BY_USER
2006 (X'07D6') MQRC_CHAR_ATTR_LENGTH_ERROR
2007 (X'07D7') MQRC_CHAR_ATTRS_ERROR
2008 (X'07D8') MQRC_CHAR_ATTRS_TOO_SHORT
2340 (X'0924') MQRC_CHAR_CONVERSION_ERROR
2187 (X'088B') MQRC_CICS_BRIDGE_RESTRICTION
2140 (X'085C') MQRC_CICS_WAIT_FAILED
2423 (X'0977') MQRC_CLIENT_CHANNEL_CONFLICT
2278 (X'08E6') MQRC_CLIENT_CONN_ERROR
2407 (X'0967') MQRC_CLIENT_EXIT_ERROR
2406 (X'0966') MQRC_CLIENT_EXIT_LOAD_ERROR
2266 (X'08DA') MQRC_CLUSTER_EXIT_ERROR
2267 (X'08DB') MQRC_CLUSTER_EXIT_LOAD_ERROR
2268 (X'08DC') MQRC_CLUSTER_PUT_INHIBITED
2189 (X'088D') MQRC_CLUSTER_RESOLUTION_ERROR
2269 (X'08DD') MQRC_CLUSTER_RESOURCE_ERROR
2322 (X'0912') MQRC_CMD_SERVER_NOT_AVAILABLE
2139 (X'085B') MQRC_CNO_ERROR
2106 (X'083A') MQRC_COD_NOT_VALID_FOR_XCF_Q
2330 (X'091A') MQRC_CODED_CHAR_SET_ID_ERROR
2412 (X'096C') MQRC_COMMAND_MQSC
2413 (X'096D') MQRC_COMMAND_PCF
2300 (X'08FC') MQRC_COMMAND_TYPE_ERROR
2368 (X'0940') MQRC_CONFIG_CHANGE_OBJECT
2367 (X'093F') MQRC_CONFIG_CREATE_OBJECT
2369 (X'0941') MQRC_CONFIG_DELETE_OBJECT
2370 (X'0942') MQRC_CONFIG_REFRESH_OBJECT
2160 (X'0870') MQRC_CONN_ID_IN_USE
2271 (X'08DF') MQRC_CONN_TAG_IN_USE
2344 (X'0928') MQRC_CONN_TAG_NOT_RELEASED
2350 (X'092E') MQRC_CONN_TAG_NOT_USABLE
2009 (X'07D9') MQRC_CONNECTION_BROKEN
2273 (X'08E1') MQRC_CONNECTION_ERROR
2217 (X'08A9') MQRC_CONNECTION_NOT_AUTHORIZED
2202 (X'089A') MQRC_CONNECTION_QUIESCING
2203 (X'089B') MQRC_CONNECTION_STOPPING
2097 (X'0831') MQRC_CONTEXT_HANDLE_ERROR
2098 (X'0832') MQRC_CONTEXT_NOT_AVAILABLE
6121 (X'17E9') MQRC_CONTEXT_OBJECT_NOT_VALID
6122 (X'17EA') MQRC_CONTEXT_OPEN_ERROR
2120 (X'0848') MQRC_CONVERTED_MSG_TOO_BIG
2190 (X'088E') MQRC_CONVERTED_STRING_TOO_BIG
2207 (X'089F') MQRC_CORREL_ID_ERROR
2382 (X'094E') MQRC_CRYPTO_HARDWARE_ERROR
2357 (X'0935') MQRC_CURRENT_RECORD_ERROR
6105 (X'17D9') MQRC_CURSOR_NOT_VALID
2010 (X'07DA') MQRC_DATA_LENGTH_ERROR

6115 (X'17E3') MQRC_DATA_TRUNCATED

2150 (X'0866') MQRC_DBCS_ERROR
2342 (X'0926') MQRC_DB2_NOT_AVAILABLE
2198 (X'0896') MQRC_DEF_XMIT_Q_TYPE_ERROR
2199 (X'0897') MQRC_DEF_XMIT_Q_USAGE_ERROR
2263 (X'08D7') MQRC_DEST_ENV_ERROR
2264 (X'08D8') MQRC_DEST_NAME_ERROR
2135 (X'0857') MQRC_DH_ERROR
6126 (X'17EE') MQRC_DISTRIBUTION_LIST_EMPTY
2141 (X'085D') MQRC_DLH_ERROR
2163 (X'0873') MQRC_DUPLICATE_RECOV_COORD
2011 (X'07DB') MQRC_DYNAMIC_Q_NAME_ERROR
6106 (X'17DA') MQRC_ENCODING_ERROR
2308 (X'0904') MQRC_ENCODING_NOT_SUPPORTED
2012 (X'07DC') MQRC_ENVIRONMENT_ERROR
2420 (X'0974') MQRC_EPH_ERROR
2377 (X'0949') MQRC_EXIT_REASON_ERROR
2013 (X'07DD') MQRC_EXPIRY_ERROR
2014 (X'07DE') MQRC_FEEDBACK_ERROR
2208 (X'08A0') MQRC_FILE_SYSTEM_ERROR
2418 (X'0972') MQRC_FILTER_OPERATOR_ERROR
2110 (X'083E') MQRC_FORMAT_ERROR
2317 (X'090D') MQRC_FORMAT_NOT_SUPPORTED
2281 (X'08E9') MQRC_FUNCTION_ERROR
2298 (X'08FA') MQRC_FUNCTION_NOT_SUPPORTED
2016 (X'07E0') MQRC_GET_INHIBITED
2351 (X'092F') MQRC_GLOBAL_UOW_CONFLICT
2186 (X'088A') MQRC_GMO_ERROR
2258 (X'08D2') MQRC_GROUP_ID_ERROR
2353 (X'0931') MQRC_HANDLE_IN_USE_FOR_UOW
2017 (X'07E1') MQRC_HANDLE_NOT_AVAILABLE
2320 (X'0910') MQRC_HBAG_ERROR
2280 (X'08E8') MQRC_HCONFIG_ERROR
2018 (X'07E2') MQRC_HCONN_ERROR
2142 (X'085E') MQRC_HEADER_ERROR
2019 (X'07E3') MQRC_HOBJ_ERROR
2148 (X'0864') MQRC_IIH_ERROR
2241 (X'08C1') MQRC_INCOMPLETE_GROUP
2242 (X'08C2') MQRC_INCOMPLETE_MSG
2259 (X'08D3') MQRC_INCONSISTENT_BROWSE
2243 (X'08C3') MQRC_INCONSISTENT_CCSIDS
2244 (X'08C4') MQRC_INCONSISTENT_ENCODINGS
6119 (X'17E7') MQRC_INCONSISTENT_FORMAT
2313 (X'0909') MQRC_INCONSISTENT_ITEM_TYPE
6120 (X'17E8') MQRC_INCONSISTENT_OBJECT_STATE
6127 (X'17EF') MQRC_INCONSISTENT_OPEN_OPTIONS
2185 (X'0889') MQRC_INCONSISTENT_PERSISTENCE
2245 (X'08C5') MQRC_INCONSISTENT_UOW
2314 (X'090A') MQRC_INDEX_ERROR
2306 (X'0902') MQRC_INDEX_NOT_PRESENT
2020 (X'07E4') MQRC_INHIBIT_VALUE_ERROR
2286 (X'08EE') MQRC_INITIALIZATION_FAILED
2324 (X'0914') MQRC_INQUIRY_COMMAND_ERROR
6113 (X'17E1') MQRC_INSUFFICIENT_BUFFER
6114 (X'17E2') MQRC_INSUFFICIENT_DATA
2021 (X'07E5') MQRC_INT_ATTR_COUNT_ERROR

2022 (X'07E6') MQRC_INT_ATTR_COUNT_TOO_SMALL

2023 (X'07E7') MQRC_INT_ATTRS_ARRAY_ERROR
2246 (X'08C6') MQRC_INVALID_MSG_UNDER_CURSOR
2316 (X'090C') MQRC_ITEM_COUNT_ERROR
2327 (X'0917') MQRC_ITEM_TYPE_ERROR
2319 (X'090F') MQRC_ITEM_VALUE_ERROR
2364 (X'093C') MQRC_JMS_FORMAT_ERROR
2397 (X'095D') MQRC_JSSE_ERROR
2381 (X'094D') MQRC_KEY_REPOSITORY_ERROR
2390 (X'0956') MQRC_LDAP_PASSWORD_ERROR
2388 (X'0954') MQRC_LDAP_USER_NAME_ERROR
2389 (X'0955') MQRC_LDAP_USER_NAME_LENGTH_ERR
2352 (X'0930') MQRC_LOCAL_UOW_CONFLICT
2411 (X'096B') MQRC_LOGGER_STATUS
2247 (X'08C7') MQRC_MATCH_OPTIONS_ERROR
2025 (X'07E9') MQRC_MAX_CONNS_LIMIT_REACHED
2026 (X'07EA') MQRC_MD_ERROR
2248 (X'08C8') MQRC_MDE_ERROR
2027 (X'07EB') MQRC_MISSING_REPLY_TO_Q
2332 (X'091C') MQRC_MISSING_WIH
2249 (X'08C9') MQRC_MSG_FLAGS_ERROR
2206 (X'089E') MQRC_MSG_ID_ERROR
2417 (X'0971') MQRC_MSG_NOT_ALLOWED_IN_GROUP
2363 (X'093B') MQRC_MSG_NOT_MATCHED
2250 (X'08CA') MQRC_MSG_SEQ_NUMBER_ERROR
2331 (X'091B') MQRC_MSG_TOKEN_ERROR
2218 (X'08AA') MQRC_MSG_TOO_BIG_FOR_CHANNEL
2030 (X'07EE') MQRC_MSG_TOO_BIG_FOR_Q
2031 (X'07EF') MQRC_MSG_TOO_BIG_FOR_Q_MGR
2029 (X'07ED') MQRC_MSG_TYPE_ERROR
2301 (X'08FD') MQRC_MULTIPLE_INSTANCE_ERROR
2136 (X'0858') MQRC_MULTIPLE_REASONS
2201 (X'0899') MQRC_NAME_IN_USE
2194 (X'0892') MQRC_NAME_NOT_VALID_FOR_TYPE
6117 (X'17E5') MQRC_NEGATIVE_LENGTH
6118 (X'17E6') MQRC_NEGATIVE_OFFSET
2325 (X'0915') MQRC_NESTED_BAG_NOT_SUPPORTED
2419 (X'0973') MQRC_NESTED_SELECTOR_ERROR
2358 (X'0936') MQRC_NEXT_OFFSET_ERROR
2361 (X'0939') MQRC_NEXT_RECORD_ERROR
6110 (X'17DE') MQRC_NO_BUFFER
6109 (X'17DD') MQRC_NO_CONNECTION_REFERENCE
2379 (X'094B') MQRC_NO_DATA_AVAILABLE
2270 (X'08DE') MQRC_NO_DESTINATIONS_AVAILABLE
2121 (X'0849') MQRC_NO_EXTERNAL_PARTICIPANTS
2033 (X'07F1') MQRC_NO_MSG_AVAILABLE
2209 (X'08A1') MQRC_NO_MSG_LOCKED
2034 (X'07F2') MQRC_NO_MSG_UNDER_CURSOR
2359 (X'0937') MQRC_NO_RECORD_AVAILABLE
0 (X'0000') MQRC_NONE
2035 (X'07F3') MQRC_NOT_AUTHORIZED
6124 (X'17EC') MQRC_NOT_CONNECTED
2119 (X'0847') MQRC_NOT_CONVERTED
6125 (X'17ED') MQRC_NOT_OPEN
2036 (X'07F4') MQRC_NOT_OPEN_FOR_BROWSE
2037 (X'07F5') MQRC_NOT_OPEN_FOR_INPUT

2038 (X'07F6') MQRC_NOT_OPEN_FOR_INQUIRE

2039 (X'07F7') MQRC_NOT_OPEN_FOR_OUTPUT
2093 (X'082D') MQRC_NOT_OPEN_FOR_PASS_ALL
2094 (X'082E') MQRC_NOT_OPEN_FOR_PASS_IDENT
2040 (X'07F8') MQRC_NOT_OPEN_FOR_SET
2095 (X'082F') MQRC_NOT_OPEN_FOR_SET_ALL
2096 (X'0830') MQRC_NOT_OPEN_FOR_SET_IDENT
6108 (X'17DC') MQRC_NULL_POINTER
2100 (X'0834') MQRC_OBJECT_ALREADY_EXISTS
2041 (X'07F9') MQRC_OBJECT_CHANGED
2101 (X'0835') MQRC_OBJECT_DAMAGED
2042 (X'07FA') MQRC_OBJECT_IN_USE
2360 (X'0938') MQRC_OBJECT_LEVEL_INCOMPATIBLE
2152 (X'0868') MQRC_OBJECT_NAME_ERROR
2343 (X'0927') MQRC_OBJECT_NOT_UNIQUE
2153 (X'0869') MQRC_OBJECT_Q_MGR_NAME_ERROR
2155 (X'086B') MQRC_OBJECT_RECORDS_ERROR
2043 (X'07FB') MQRC_OBJECT_TYPE_ERROR
2044 (X'07FC') MQRC_OD_ERROR
2251 (X'08CB') MQRC_OFFSET_ERROR
2137 (X'0859') MQRC_OPEN_FAILED
2274 (X'08E2') MQRC_OPTION_ENVIRONMENT_ERROR
2045 (X'07FD') MQRC_OPTION_NOT_VALID_FOR_TYPE
2046 (X'07FE') MQRC_OPTIONS_ERROR
2252 (X'08CC') MQRC_ORIGINAL_LENGTH_ERROR
2310 (X'0906') MQRC_OUT_SELECTOR_ERROR
2123 (X'084B') MQRC_OUTCOME_MIXED
2124 (X'084C') MQRC_OUTCOME_PENDING
2193 (X'0891') MQRC_PAGESET_ERROR
2192 (X'0890') MQRC_PAGESET_FULL
2321 (X'0911') MQRC_PARAMETER_MISSING
2272 (X'08E0') MQRC_PARTIALLY_CONVERTED
2122 (X'084A') MQRC_PARTICIPANT_NOT_AVAILABLE
2149 (X'0865') MQRC_PCF_ERROR
2047 (X'07FF') MQRC_PERSISTENCE_ERROR
2048 (X'0800') MQRC_PERSISTENT_NOT_ALLOWED
2173 (X'087D') MQRC_PMO_ERROR
2158 (X'086E') MQRC_PMO_RECORD_FLAGS_ERROR
2050 (X'0802') MQRC_PRIORITY_ERROR
2049 (X'0801') MQRC_PRIORITY_EXCEEDS_MAXIMUM
2051 (X'0803') MQRC_PUT_INHIBITED
2159 (X'086F') MQRC_PUT_MSG_RECORDS_ERROR
2290 (X'08F2') MQRC_Q_ALREADY_EXISTS
2052 (X'0804') MQRC_Q_DELETED
2224 (X'08B0') MQRC_Q_DEPTH_HIGH
2225 (X'08B1') MQRC_Q_DEPTH_LOW
2053 (X'0805') MQRC_Q_FULL
2394 (X'095A') MQRC_Q_INDEX_TYPE_ERROR
2222 (X'08AE') MQRC_Q_MGR_ACTIVE
2058 (X'080A') MQRC_Q_MGR_NAME_ERROR
2223 (X'08AF') MQRC_Q_MGR_NOT_ACTIVE
2059 (X'080B') MQRC_Q_MGR_NOT_AVAILABLE
2161 (X'0871') MQRC_Q_MGR_QUIESCING
2162 (X'0872') MQRC_Q_MGR_STOPPING
2055 (X'0807') MQRC_Q_NOT_EMPTY
2226 (X'08B2') MQRC_Q_SERVICE_INTERVAL_HIGH

2227 (X'08B3') MQRC_Q_SERVICE_INTERVAL_OK

2056 (X'0808') MQRC_Q_SPACE_NOT_AVAILABLE
2057 (X'0809') MQRC_Q_TYPE_ERROR
2229 (X'08B5') MQRC_RAS_PROPERTY_ERROR
2154 (X'086A') MQRC_RECS_PRESENT_ERROR
6129 (X'17F1') MQRC_REFERENCE_ERROR
2184 (X'0888') MQRC_REMOTE_Q_NAME_ERROR
6100 (X'17D4') MQRC_REOPEN_EXCL_INPUT_ERROR
6101 (X'17D5') MQRC_REOPEN_INQUIRE_ERROR
6102 (X'17D6') MQRC_REOPEN_SAVED_CONTEXT_ERR
6103 (X'17D7') MQRC_REOPEN_TEMPORARY_Q_ERROR
2061 (X'080D') MQRC_REPORT_OPTIONS_ERROR
2378 (X'094A') MQRC_RESERVED_VALUE_ERROR
2102 (X'0836') MQRC_RESOURCE_PROBLEM
2156 (X'086C') MQRC_RESPONSE_RECORDS_ERROR
2336 (X'0920') MQRC_RFH_COMMAND_ERROR
2338 (X'0922') MQRC_RFH_DUPLICATE_PARM
2334 (X'091E') MQRC_RFH_ERROR
2421 (X'0975') MQRC_RFH_FORMAT_ERROR
2228 (X'08B4') MQRC_RFH_HEADER_FIELD_ERROR
2337 (X'0921') MQRC_RFH_PARM_ERROR
2339 (X'0923') MQRC_RFH_PARM_MISSING
2335 (X'091F') MQRC_RFH_STRING_ERROR
2220 (X'08AC') MQRC_RMH_ERROR
2380 (X'094C') MQRC_SCO_ERROR
2062 (X'080E') MQRC_SECOND_MARK_NOT_ALLOWED
2063 (X'080F') MQRC_SECURITY_ERROR
2253 (X'08CD') MQRC_SEGMENT_LENGTH_ZERO
2365 (X'093D') MQRC_SEGMENTS_NOT_SUPPORTED
2065 (X'0811') MQRC_SELECTOR_COUNT_ERROR
2067 (X'0813') MQRC_SELECTOR_ERROR
2066 (X'0812') MQRC_SELECTOR_LIMIT_EXCEEDED
2068 (X'0814') MQRC_SELECTOR_NOT_FOR_TYPE
2309 (X'0905') MQRC_SELECTOR_NOT_PRESENT
2318 (X'090E') MQRC_SELECTOR_NOT_SUPPORTED
2305 (X'0901') MQRC_SELECTOR_NOT_UNIQUE
2304 (X'0900') MQRC_SELECTOR_OUT_OF_RANGE
2299 (X'08FB') MQRC_SELECTOR_TYPE_ERROR
2312 (X'0908') MQRC_SELECTOR_WRONG_TYPE
2289 (X'08F1') MQRC_SERVICE_ERROR
2285 (X'08ED') MQRC_SERVICE_NOT_AVAILABLE
2069 (X'0815') MQRC_SIGNAL_OUTSTANDING
2070 (X'0816') MQRC_SIGNAL_REQUEST_ACCEPTED
2099 (X'0833') MQRC_SIGNAL1_ERROR
2211 (X'08A3') MQRC_SOAP_AXIS_ERROR
2210 (X'08A2') MQRC_SOAP_DOTNET_ERROR
2212 (X'08A4') MQRC_SOAP_URL_ERROR
2145 (X'0861') MQRC_SOURCE_BUFFER_ERROR
2111 (X'083F') MQRC_SOURCE_CCSID_ERROR
2113 (X'0841') MQRC_SOURCE_DECIMAL_ENC_ERROR
2114 (X'0842') MQRC_SOURCE_FLOAT_ENC_ERROR
2112 (X'0840') MQRC_SOURCE_INTEGER_ENC_ERROR
2143 (X'085F') MQRC_SOURCE_LENGTH_ERROR
2261 (X'08D5') MQRC_SRC_ENV_ERROR
2262 (X'08D6') MQRC_SRC_NAME_ERROR
2391 (X'0957') MQRC_SSL_ALREADY_INITIALIZED

2402 (X'0962') MQRC_SSL_CERT_STORE_ERROR

2401 (X'0961') MQRC_SSL_CERTIFICATE_REVOKED
2392 (X'0958') MQRC_SSL_CONFIG_ERROR
2409 (X'0969') MQRC_SSL_KEY_RESET_ERROR
2393 (X'0959') MQRC_SSL_INITIALIZATION_ERROR
2396 (X'095C') MQRC_SSL_NOT_ALLOWED
2399 (X'095F') MQRC_SSL_PEER_NAME_ERROR
2398 (X'095E') MQRC_SSL_PEER_NAME_MISMATCH
2188 (X'088C') MQRC_STOPPED_BY_CLUSTER_EXIT
2105 (X'0839') MQRC_STORAGE_CLASS_ERROR
2192 (X'0890') MQRC_STORAGE_MEDIUM_FULL
2071 (X'0817') MQRC_STORAGE_NOT_AVAILABLE
2307 (X'0903') MQRC_STRING_ERROR
2323 (X'0913') MQRC_STRING_LENGTH_ERROR
2311 (X'0907') MQRC_STRING_TRUNCATED
6107 (X'17DB') MQRC_STRUC_ID_ERROR
6123 (X'17EB') MQRC_STRUC_LENGTH_ERROR
2109 (X'083D') MQRC_SUPPRESSED_BY_EXIT
2024 (X'07E8') MQRC_SYNCPOINT_LIMIT_REACHED
2072 (X'0818') MQRC_SYNCPOINT_NOT_AVAILABLE
2315 (X'090B') MQRC_SYSTEM_BAG_NOT_ALTERABLE
2328 (X'0918') MQRC_SYSTEM_BAG_NOT_DELETABLE
2302 (X'08FE') MQRC_SYSTEM_ITEM_NOT_ALTERABLE
2329 (X'0919') MQRC_SYSTEM_ITEM_NOT_DELETABLE
2146 (X'0862') MQRC_TARGET_BUFFER_ERROR
2115 (X'0843') MQRC_TARGET_CCSID_ERROR
2117 (X'0845') MQRC_TARGET_DECIMAL_ENC_ERROR
2118 (X'0846') MQRC_TARGET_FLOAT_ENC_ERROR
2116 (X'0844') MQRC_TARGET_INTEGER_ENC_ERROR
2144 (X'0860') MQRC_TARGET_LENGTH_ERROR
2287 (X'08EF') MQRC_TERMINATION_FAILED
2265 (X'08D9') MQRC_TM_ERROR
2191 (X'088F') MQRC_TMC_ERROR
2075 (X'081B') MQRC_TRIGGER_CONTROL_ERROR
2076 (X'081C') MQRC_TRIGGER_DEPTH_ERROR
2077 (X'081D') MQRC_TRIGGER_MSG_PRIORITY_ERR
2078 (X'081E') MQRC_TRIGGER_TYPE_ERROR
2079 (X'081F') MQRC_TRUNCATED_MSG_ACCEPTED
2080 (X'0820') MQRC_TRUNCATED_MSG_FAILED
2341 (X'0925') MQRC_UCS2_CONVERSION_ERROR
2195 (X'0893') MQRC_UNEXPECTED_ERROR
2232 (X'08B8') MQRC_UNIT_OF_WORK_NOT_STARTED
2082 (X'0822') MQRC_UNKNOWN_ALIAS_BASE_Q
2197 (X'0895') MQRC_UNKNOWN_DEF_XMIT_Q
2292 (X'08F4') MQRC_UNKNOWN_ENTITY
2085 (X'0825') MQRC_UNKNOWN_OBJECT_NAME
2086 (X'0826') MQRC_UNKNOWN_OBJECT_Q_MGR
2288 (X'08F0') MQRC_UNKNOWN_Q_NAME
2294 (X'08F6') MQRC_UNKNOWN_REF_OBJECT
2087 (X'0827') MQRC_UNKNOWN_REMOTE_Q_MGR
2104 (X'0838') MQRC_UNKNOWN_REPORT_OPTION
2196 (X'0894') MQRC_UNKNOWN_XMIT_Q
2400 (X'0960') MQRC_UNSUPPORTED_CIPHER_SUITE
2297 (X'08F9') MQRC_UOW_CANCELED
2354 (X'0932') MQRC_UOW_ENLISTMENT_ERROR
2128 (X'0850') MQRC_UOW_IN_PROGRESS

2355 (X'0933') MQRC_UOW_MIX_NOT_SUPPORTED

2255 (X'08CF') MQRC_UOW_NOT_AVAILABLE
2291 (X'08F3') MQRC_USER_ID_NOT_AVAILABLE
2090 (X'082A') MQRC_WAIT_INTERVAL_ERROR
2333 (X'091D') MQRC_WIH_ERROR
2366 (X'093E') MQRC_WRONG_CF_LEVEL
2256 (X'08D0') MQRC_WRONG_GMO_VERSION
2257 (X'08D1') MQRC_WRONG_MD_VERSION
6128 (X'17FO') MQRC_WRONG_VERSION
2356 (X'0934') MQRC_WXP_ERROR
2091 (X'082B') MQRC_XMIT_Q_TYPE_ERROR
2092 (X'082C') MQRC_XMIT_Q_USAGE_ERROR
2260 (X'08D4') MQRC_XQH_ERROR
2107 (X'083B') MQRC_XWAIT_CANCELED
2108 (X'083C') MQRC_XWAIT_ERROR
6116 (X'17E4') MQRC_ZERO_LENGTH

Chapter 9. PCF reason codes
Reason codes might be returned by a broker in response to a command message in
PCF format, depending on the parameters used in that message.
For more information about PCF, see the WebSphere MQ Publish/Subscribe User’s
Guide.
Reason codes
The following is a list of PCF reason codes, in numeric order, providing detailed
information to help you understand them, including:
v An explanation of the circumstances that have caused the code to be raised
v The associated completion code
v Suggested programmer actions in response to the code
See “Reason code cross reference” on page 354 for a list of PCF reason codes in
alphabetic order.
Programmer Response: Specify a valid control option.

3001 (X'0BB9') MQRCCF_CFH_TYPE_ERROR
Explanation: Type not valid.
3006 (X'0BBE')
The MQCFH Type field value was not valid. MQRCCF_CFH_PARM_COUNT_ERROR
Programmer Response: Specify a valid type. Explanation: Parameter count not valid.
The MQCFH ParameterCount field value was not valid.
3002 (X'0BBA') MQRCCF_CFH_LENGTH_ERROR
Programmer Response: Specify a valid parameter
Explanation: Structure length not valid. count.
The MQCFH StrucLength field value was not valid.
3007 (X'0BBF') MQRCCF_CFH_COMMAND_ERROR
Programmer Response: Specify a valid structure
length. Explanation: Command identifier not valid.
The MQCFH Command field value was not valid.
3003 (X'0BBB') MQRCCF_CFH_VERSION_ERROR
Programmer Response: Specify a valid command
Explanation: Structure version number is not valid. identifier.
The MQCFH Version field value was not valid.
3008 (X'0BC0') MQRCCF_COMMAND_FAILED
version number. Explanation: Command failed.
The command has failed.
3004 (X'0BBC')
Programmer Response: Refer to the previous error
MQRCCF_CFH_MSG_SEQ_NUMBER_ERR
messages for this command.
Explanation: Message sequence number not valid.
The MQCFH MsgSeqNumber field value was not valid. 3009 (X'0BC1') MQRCCF_CFIN_LENGTH_ERROR
Programmer Response: Specify a valid message Explanation: Structure length not valid.
sequence number.
The MQCFIN or MQCFIN64 StrucLength field value
was not valid.
3005 (X'0BBD') MQRCCF_CFH_CONTROL_ERROR
Explanation: Control option not valid. length.
The MQCFH Control field value was not valid.

PCF reason codes
3010 (X'0BC2') MQRCCF_CFST_LENGTH_ERROR 3016 (X'0BC8') MQRCCF_MSG_LENGTH_ERROR

Explanation: Structure length not valid. Explanation: Message length not valid.
The MQCFST StrucLength field value was not valid. The message data length was inconsistent with the
The value was not a multiple of four or was length implied by the parameters in the message, or a
inconsistent with the MQCFST StringLength field positional parameter was out of sequence.
value.
Programmer Response: Specify a valid message
Programmer Response: Specify a valid structure length, and check that positional parameters are in the
length. correct sequence.
3011 (X'0BC3') 3017 (X'0BC9') MQRCCF_CFIN_DUPLICATE_PARM

MQRCCF_CFST_STRING_LENGTH_ERR
Explanation: Duplicate parameter.
Explanation: String length not valid.
Two MQCFIN or MQCFIN64 or MQCFIL or MQCFIL64
The MQCFST StringLength field value was not valid. structures, or any two of those types of structure, with
The value was negative or greater than the maximum the same parameter identifier were present.
permitted length of the parameter specified in the
Programmer Response: Check for and remove
Parameter field.
duplicate parameters.
Programmer Response: Specify a valid string length
for the parameter.
3018 (X'0BCA') MQRCCF_CFST_DUPLICATE_PARM
Explanation: Duplicate parameter.
3012 (X'0BC4') MQRCCF_FORCE_VALUE_ERROR
Two MQCFST structures, or an MQCFSL followed by
Explanation: Force value not valid.
an MQCFST structure, with the same parameter
The force value specified was not valid. identifier were present.
Programmer Response: Specify a valid force value. Programmer Response: Check for and remove
3013 (X'0BC5')
MQRCCF_STRUCTURE_TYPE_ERROR 3019 (X'0BCB')
MQRCCF_PARM_COUNT_TOO_SMALL
Explanation: Structure type not valid.
Explanation: Parameter count too small.
The structure Type value was not valid.
The MQCFH ParameterCount field value was less than
Programmer Response: Specify a valid structure type.
the minimum required for the command.
Programmer Response: Specify a parameter count that
3014 (X'0BC6') MQRCCF_CFIN_PARM_ID_ERROR
is valid for the command.
Explanation: Parameter identifier is not valid.
The MQCFIN or MQCFIN64 Parameter field value was 3020 (X'0BCC') MQRCCF_PARM_COUNT_TOO_BIG
not valid.
Explanation: Parameter count too big.
The MQCFH ParameterCount field value was more than
identifier.
the maximum for the command.
Programmer Response: Specify a parameter count that
3015 (X'0BC7') MQRCCF_CFST_PARM_ID_ERROR
is valid for the command.
The MQCFST Parameter field value was not valid. 3021 (X'0BCD') MQRCCF_Q_ALREADY_IN_CELL
Programmer Response: Specify a valid parameter Explanation: Queue already exists in cell.
identifier.
An attempt was made to define a queue with cell
scope, or to change the scope of an existing queue from
queue-manager scope to cell scope, but a queue with
that name already existed in the cell.
Programmer Response: Do one of the following:
v Delete the existing queue and retry the operation.

PCF reason codes
v Change the scope of the existing queue from cell to

3028 (X'0BD4') MQRCCF_CFIL_LENGTH_ERROR
queue-manager and retry the operation.
v Create the new queue with a different name. Explanation: Structure length not valid.
The MQCFIL or MQCFIL64 StrucLength field value
3022 (X'0BCE') MQRCCF_Q_TYPE_ERROR was not valid.
Explanation: Queue type not valid. Programmer Response: Specify a valid structure
length.
The QType value was not valid.
Programmer Response: Specify a valid queue type.
3029 (X'0BD5') MQRCCF_MODE_VALUE_ERROR
Explanation: Mode value not valid.
3023 (X'0BCF') MQRCCF_MD_FORMAT_ERROR
The Mode value was not valid.
Explanation: Format not valid.
Programmer Response: Specify a valid mode value.
The MQMD Format field value was not
MQFMT_ADMIN.
3029 (X'0BD5') MQRCCF_QUIESCE_VALUE_ERROR
Programmer Response: Specify the valid format.
Explanation: Former name for
MQRCCF_MODE_VALUE_ERROR.
3024 (X'0BD0') MQRCCF_CFSL_LENGTH_ERROR
Explanation: Structure length not valid.
3030 (X'0BD6')
The MQCFSL StrucLength field value was not valid. MQRCCF_MSG_SEQ_NUMBER_ERROR
The value was not a multiple of four or was
Explanation: Message sequence number not valid.
inconsistent with the MQCFSL StringLength field
value. The message sequence number parameter value was
not valid.
length. Programmer Response: Specify a valid message
sequence number.
3025 (X'0BD1') MQRCCF_REPLACE_VALUE_ERROR
3031 (X'0BD7')
Explanation: Replace value not valid.
MQRCCF_PING_DATA_COUNT_ERROR
The Replace value was not valid.
Explanation: Data count not valid.
Programmer Response: Specify a valid replace value.
The Ping Channel DataCount value was not valid.
Programmer Response: Specify a valid data count
3026 (X'0BD2') MQRCCF_CFIL_DUPLICATE_VALUE
value.
Explanation: Duplicate parameter value.
In the MQCFIL or MQCFIL64 structure, there was a 3032 (X'0BD8')
duplicate parameter value in the list. MQRCCF_PING_DATA_COMPARE_ERROR
Programmer Response: Check for and remove Explanation: Ping Channel command failed.
duplicate parameter values.
The Ping Channel command failed with a data
compare error. The data offset that failed is returned in
3027 (X'0BD3') MQRCCF_CFIL_COUNT_ERROR the message (with parameter identifier
MQIACF_ERROR_OFFSET).
Explanation: Count of parameter values not valid.
Programmer Response: Consult your systems
The MQCFIL or MQCFIL64 Count field value was not administrator.
valid. The value was negative or greater than the
maximum permitted for the parameter specified in the
Parameter field. 3033 (X'0BD9') MQRCCF_CFSL_PARM_ID_ERROR
Programmer Response: Specify a valid count for the Explanation: Parameter identifier is not valid.
parameter.
The MQCFSL Parameter field value was not valid.
identifier.
Chapter 9. PCF reason codes 331

PCF reason codes
Programmer Response: Specify a valid short timer

3034 (X'0BDA') MQRCCF_CHANNEL_TYPE_ERROR
value.
Explanation: Channel type not valid.
The ChannelType specified was not valid, or did not 3041 (X'0BE1') MQRCCF_LONG_RETRY_ERROR
match the type of an existing channel being copied,
Explanation: Long retry count not valid.
changed or replaced, or the command and the specified
disposition cannot be used with that type of channel. The long retry count value specified was not valid.
Programmer Response: Specify a valid channel name, Programmer Response: Specify a valid long retry
type, or disposition. count value.
3035 (X'0BDB') 3042 (X'0BE2') MQRCCF_LONG_TIMER_ERROR

MQRCCF_PARM_SEQUENCE_ERROR
Explanation: Long timer not valid.
Explanation: Parameter sequence not valid.
The long timer (long retry wait interval) value specified
The sequence of parameters is not valid for this was not valid.
command.
Programmer Response: Specify a valid long timer
Programmer Response: Specify the positional value.
parameters in a valid sequence for the command.
3043 (X'0BE3')
3036 (X'0BDC') MQRCCF_SEQ_NUMBER_WRAP_ERROR
MQRCCF_XMIT_PROTOCOL_TYPE_ERR
Explanation: Sequence wrap number not valid.
Explanation: Transmission protocol type not valid.
The SeqNumberWrap value was not valid.
The TransportType value was not valid.
Programmer Response: Specify a valid sequence wrap
Programmer Response: Specify a valid transmission number.
protocol type.
3044 (X'0BE4')
3037 (X'0BDD') MQRCCF_BATCH_SIZE_ERROR MQRCCF_MAX_MSG_LENGTH_ERROR
Explanation: Batch size not valid. Explanation: Maximum message length not valid.
The batch size specified was not valid. The maximum message length value specified was not
valid.
Programmer Response: Specify a valid batch size
value. Programmer Response: Specify a valid maximum
message length.
3038 (X'0BDE') MQRCCF_DISC_INT_ERROR
3045 (X'0BE5') MQRCCF_PUT_AUTH_ERROR
Explanation: Disconnection interval not valid.
Explanation: Put authority value not valid.
The disconnection interval specified was not valid.
The PutAuthority value was not valid.
Programmer Response: Specify a valid disconnection
interval. Programmer Response: Specify a valid authority
value.
3039 (X'0BDF') MQRCCF_SHORT_RETRY_ERROR
3046 (X'0BE6') MQRCCF_PURGE_VALUE_ERROR
Explanation: Short retry count not valid.
Explanation: Purge value not valid.
The ShortRetryCount value was not valid.
The Purge value was not valid.
Programmer Response: Specify a valid short retry
count value. Programmer Response: Specify a valid purge value.
3040 (X'0BE0') MQRCCF_SHORT_TIMER_ERROR 3047 (X'0BE7') MQRCCF_CFIL_PARM_ID_ERROR

Explanation: Short timer value not valid. Explanation: Parameter identifier is not valid.
The ShortRetryInterval value was not valid. The MQCFIL or MQCFIL64 Parameter field value was
not valid, or specifies a parameter that cannot be

PCF reason codes
filtered, or that is also specified as a parameter to select

3052 (X'0BEC')
a subset of objects.
MQRCCF_DATA_CONV_VALUE_ERROR
Explanation: Data conversion value not valid.
identifier.
The value specified for DataConversion is not valid.
3048 (X'0BE8') MQRCCF_MSG_TRUNCATED Programmer Response: Specify a valid value.
Explanation: Message truncated.
3053 (X'0BED')
The command server received a message that is larger
MQRCCF_INDOUBT_VALUE_ERROR
than its maximum valid message size.
Explanation: In-doubt value not valid.
Programmer Response: Check the message contents
are correct. The value specified for InDoubt is not valid.
3049 (X'0BE9') MQRCCF_CCSID_ERROR
Explanation: Coded character-set identifier error. 3054 (X'0BEE') MQRCCF_ESCAPE_TYPE_ERROR
In a command message, one of the following occurred: Explanation: Escape type not valid.
v The CodedCharSetId field in the message descriptor The value specified for EscapeType is not valid.
of the command does not match the coded
character-set identifier of the queue manager at Programmer Response: Specify a valid value.
which the command is being processed, or
v The CodedCharSetId field in a string parameter 3062 (X'0BF6') MQRCCF_CHANNEL_TABLE_ERROR
structure within the message text of the command is
not Explanation: Channel table value not valid.
– MQCCSI_DEFAULT, or The ChannelTable specified was not valid, or was not
– the coded character-set identifier of the queue appropriate for the channel type specified on an
manager at which the command is being Inquire Channel or Inquire Channel Names command.
processed, as in the CodedCharSetId field in the
message descriptor. Programmer Response: Specify a valid channel table
value.
The error response message contains the correct value.
This reason can also occur if a ping cannot be 3063 (X'0BF7') MQRCCF_MCA_TYPE_ERROR
performed because the coded character-set identifiers Explanation: Message channel agent type not valid.
are not compatible. In this case the correct value is not
returned. The MCAType value specified was not valid.
Programmer Response: Construct the command with Programmer Response: Specify a valid value.
the correct coded character-set identifier, and specify
this in the message descriptor when sending the 3064 (X'0BF8') MQRCCF_CHL_INST_TYPE_ERROR
command. For ping, use a suitable coded character-set
identifier. Explanation: Channel instance type not valid.
The ChannelInstanceType specified was not valid.
3050 (X'0BEA') MQRCCF_ENCODING_ERROR Programmer Response: Specify a valid channel
Explanation: Encoding error. instance type.
The Encoding field in the message descriptor of the

command does not match that required for the 3065 (X'0BF9')
platform at which the command is being processed. MQRCCF_CHL_STATUS_NOT_FOUND
Programmer Response: Construct the command with Explanation: Channel status not found.
the correct encoding, and specify this in the message For Inquire Channel Status, no channel status is
descriptor when sending the command. available for the specified channel. This may indicate
that the channel has not been used.
Programmer Response: None, unless this is
unexpected, in which case consult your systems
administrator.

PCF reason codes
3066 (X'0BFA') MQRCCF_CFSL_DUPLICATE_PARM 3071 (X'0BFF') MQRCCF_STREAM_ERROR

Explanation: Duplicate parameter. Explanation: Stream name is not valid.
Two MQCFSL structures, or an MQCFST followed by The stream name parameter is not valid. Stream names
an MQCFSL structure, with the same parameter must obey the same naming rules as for WebSphere
identifier were present. MQ queues.
Programmer Response: Check for and remove Programmer Response: Retry the command with a
duplicate parameters. valid stream name parameter.
3067 (X'0BFB') 3072 (X'0C00') MQRCCF_TOPIC_ERROR

MQRCCF_CFSL_TOTAL_LENGTH_ERROR
Explanation: Topic name is invalid.
Explanation: Total string length error.
A command has been sent to the broker containing a
The total length of the strings (not including trailing topic name that is not valid. Note that wildcard topic
blanks) in a MQCFSL structure exceeds the maximum names are not allowed for Register Publisher and
allowable for the parameter. Publish commands.
Programmer Response: Check that the structure has Programmer Response: Retry the command with a
been specified correctly, and if so reduce the number of valid topic name parameter. Up to 256 characters of the
strings. topic name in question are returned with the error
response message. If the topic name contains a null
character, this is assumed to terminate the string and is
3068 (X'0BFC') MQRCCF_CFSL_COUNT_ERROR
not considered to be part of it. A zero length topic
Explanation: Count of parameter values not valid. name is not valid, as is one that contains an escape
sequence that is not valid.
The MQCFSL Count field value was not valid. The
value was negative or greater than the maximum
permitted for the parameter specified in the Parameter 3073 (X'0C01') MQRCCF_NOT_REGISTERED
field.
Explanation: Subscriber or publisher is not registered.
Programmer Response: Specify a valid count for the
A Deregister command has been issued to remove
parameter.
registrations for a topic, or topics, for which the
publisher or subscriber is not registered. If multiple
3069 (X'0BFD') topics were specified on the command, it fails with a
MQRCCF_CFSL_STRING_LENGTH_ERR completion code of MQCC_WARNING if the publisher
or subscriber was registered for some, but not all, of
Explanation: String length not valid. the topics specified. This error code is also returned to
The MQCFSL StringLength field value was not valid. a subscriber issuing a Request Update command for a
The value was negative or greater than the maximum topic for which he does not have a subscription.
permitted length of the parameter specified in the Programmer Response: Investigate why the publisher
Parameter field. or subscriber is not registered. In the case of a
Programmer Response: Specify a valid string length subscriber, the subscriptions might have expired, or
for the parameter. been removed automatically by the broker if the
subscriber is no longer authorized.
3070 (X'0BFE') MQRCCF_BROKER_DELETED

3074 (X'0C02') MQRCCF_Q_MGR_NAME_ERROR
Explanation: Broker has been deleted.
Explanation: An invalid or unknown queue manager
When a broker is deleted using the dltmqbrk command, name has been supplied.
all broker queues created by the broker are deleted.
Before this can be done the queues are emptied of all A queue manager name has been supplied as part of a
command messages; any that are found are placed on publisher or subscriber identity. This might have been
the dead-letter queue with this reason code. supplied as an explicit parameter or in the ReplyToQMgr
field in the message descriptor of the command. Either
Programmer Response: Process the command the queue manager name is not valid, or in the case of
messages that were placed on the dead-letter queue. a subscriber identity, the subscriber’s queue could not
be resolved because the remote queue manager is not
known to the broker queue manager.
Programmer Response: Retry the command with a

PCF reason codes
valid queue manager name. If appropriate, the broker assigned only to one user ID at a time. While the
includes a further error reason code within the error identity is registered with the broker all commands
response message. If one is supplied, follow the wanting to use it must specify the correct user ID.
guidance for that reason code in WebSphere MQ When a publisher or a subscriber no longer has any
Application Programming Reference to resolve the registrations with the broker the identity can be used
problem. by another user ID.
Programmer Response: Either retry the command
3075 (X'0C03') MQRCCF_INCORRECT_STREAM using a different identity or remove all registrations
associated with the identity so that it can be used by a
Explanation: Stream name does not match the stream
different user ID. The user ID to which the identity is
queue it was sent to.
currently assigned is returned within the error response
A command has been sent to a stream queue that message. A Deregister command could be issued to
specified a different stream name parameter. remove these registrations. If the user ID in question
cannot be used to execute such a command, you need
Programmer Response: Retry the command either by to have the necessary authority to open the
sending it to the correct stream queue or by modifying SYSTEM.BROKER.CONTROL.QUEUE using the
the command so that the stream name parameter MQOO_ALTERNATE_USER_AUTHORITY option.
matches.
3079 (X'0C07') MQRCCF_INCORRECT_Q

3076 (X'0C04') MQRCCF_Q_NAME_ERROR
Explanation: Command sent to wrong broker queue.
Explanation: An invalid or unknown queue name has
been supplied. The command is a valid broker command but the
queue it has been sent to is incorrect. Publish and
A queue name has been supplied as part of a publisher Delete Publication commands need to be sent to the
or subscriber identity. This might have been supplied stream queue, all other commands need to be sent to
as an explicit parameter or in the ReplyToQ field in the the SYSTEM.BROKER.CONTROL.QUEUE.
message descriptor of the command. Either the queue
name is not valid, or in the case of a subscriber Programmer Response: Retry the command by
identity, the broker has failed to open the queue. sending it to the correct queue.
Programmer Response: Retry the command with a
valid queue name. If appropriate, the broker includes a 3080 (X'0C08') MQRCCF_CORREL_ID_ERROR
further error reason code within the error response
Explanation: Correlation identifier used as part of an
message. If one is supplied, follow the guidance for
identity is all binary zeroes.
that reason code in WebSphere MQ Application
Programming Reference to resolve the problem. Each publisher and subscriber is identified by a queue
manager name, a queue name, and optionally a
correlation identifier. The correlation identifier is
3077 (X'0C05') MQRCCF_NO_RETAINED_MSG
typically used to allow multiple subscribers to share the
Explanation: No retained message exists for the topic same subscriber queue. In this instance a publisher or
specified. subscriber has indicated within the Registration or
Publication options supplied on the command that
A Request Update command has been issued to request their identity does include a correlation identifier, but a
the retained message associated with the specified valid identifier has not been supplied.
topic. No retained message exists for that topic.
Programmer Response: Retry the command ensuring
Programmer Response: If the topic or topics in that the correlation identifier supplied in the message
question should have retained messages, the publishers descriptor of the command message is not all binary
of these topics might not be publishing with the correct zeroes.
publication options to cause their publications to be
retained.
3081 (X'0C09') MQRCCF_NOT_AUTHORIZED
3078 (X'0C06') MQRCCF_DUPLICATE_IDENTITY Explanation: Subscriber has insufficient authority.
Explanation: Publisher or subscriber identity already To receive publications a subscriber application needs
assigned to another user ID. both browse authority for the stream queue that it is
subscribing to, and put authority for the queue that
Each publisher and subscriber has a unique identity publications are to be sent to. Subscriptions are rejected
consisting of a queue manager name, a queue name, if the subscriber does not have both authorities. In
and optionally a correlation identifier. Associated with addition to having browse authority for the stream
each identity is the user ID under which that publisher queue, a subscriber would also require altusr authority
or subscriber first registered. A given identity can be for the stream queue to subscribe to certain topics that

PCF reason codes
the broker itself publishes information on. These topics from the network ensure that the channels between the
start with the MQ/SA/ prefix. two related brokers in question are active.
Programmer Response: Ensure that the subscriber has
the necessary authorities and reissue the request. The 3086 (X'0C0E') MQRCCF_Q_MGR_CCSID_ERROR
problem might occur because the subscriber’s user ID
Explanation: Queue manager coded character set
is not known to the broker. This can be identified if a
identifier error.
further error reason code of
MQRC_UNKNOWN_ENTITY is returned within the The coded character set value for the queue manager
error response message. was not valid.
3082 (X'0C0A') MQRCCF_UNKNOWN_STREAM
Explanation: Stream is not known by the broker or 3087 (X'0C0F') MQRCCF_DEL_OPTIONS_ERROR
Explanation: Invalid delete options have been
A command message has been put to the supplied.
SYSTEM.BROKER.CONTROL.QUEUE for an unknown
stream. This error code is also returned if dynamic The options provided with a Delete Publication
stream creation is enabled and the broker failed to command are not valid.
create a stream queue for the new stream using the Programmer Response: Retry the command with a
SYSTEM.BROKER.MODEL.STREAM queue. valid combination of options.
Programmer Response: Retry the command for a
stream that the broker supports. If the broker should 3088 (X'0C10')
support the stream, either define the stream queue MQRCCF_CLUSTER_NAME_CONFLICT
manually, or correct the problem that prevented the
broker from creating the stream queue itself. Explanation: ClusterName and ClusterNamelist
attributes conflict.
3083 (X'0C0B') MQRCCF_REG_OPTIONS_ERROR The command was rejected because it would have
resulted in the ClusterName attribute and the
Explanation: Invalid registration options have been ClusterNamelist attribute both being nonblank. At least
supplied. one of these attributes must be blank.
The registration options provided on a command are Programmer Response: If the command specified one
not valid. of these attributes only, you must also specify the other
Programmer Response: Retry the command with a one, but with a value of blanks. If the command
valid combination of options. specified both attributes, ensure that one of them has a
value of blanks.
3084 (X'0C0C') MQRCCF_PUB_OPTIONS_ERROR

3089 (X'0C11') MQRCCF_REPOS_NAME_CONFLICT
Explanation: Invalid publication options have been
supplied. Explanation: RepositoryName and RepositoryNamelist
attributes conflict.
The publication options provided on a Publish
command are not valid. Either:
v The command was rejected because it would have
Programmer Response: Retry the command with a resulted in the RepositoryName and
valid combination of options. RepositoryNamelist attributes both being nonblank.
At least one of these attributes must be blank.
3085 (X'0C0D') MQRCCF_UNKNOWN_BROKER v For a Reset Queue Manager Cluster command, the
queue manager does not provide a full repository
Explanation: Command received from an unknown
management service for the specified cluster. That is,
broker.
the RepositoryName attribute of the queue manager is
Within a multi-broker network, related brokers pass not the specified cluster name, or the namelist
subscriptions and publications between each other as a specified by the RepositoryNamelist attribute does
series of command messages. One such command not contain the cluster name.
message has been received from a broker that is not, or
Programmer Response: Reissue the command with
is no longer, related to the detecting broker.
the correct values or on the correct queue manager.
Programmer Response: his situation can occur if the
broker network is not quiesced while topology changes
are made to the network. When removing a broker

PCF reason codes
3090 (X'0C12') 3094 (X'0C16')

MQRCCF_CLUSTER_Q_USAGE_ERROR MQRCCF_BROKER_COMMAND_FAILED
Explanation: Queue cannot be a cluster queue. Explanation: The broker command failed to complete.
The command was rejected because it would have A broker command was issued but it failed to
resulted in a cluster queue also being a transmission complete.
queue, which is not permitted, or because the queue in
Programmer Response: Diagnose the problem using
question cannot be a cluster queue.
the provided information and issue a corrected
Programmer Response: Ensure that the command command.
specifies either:
v The Usage parameter with a value of 3095 (X'0C17')
MQUS_NORMAL, or MQRCCF_CFST_CONFLICTING_PARM
v The ClusterName and ClusterNamelist parameters
Explanation: Conflicting parameters.
with values of blanks.
v A QName parameter with a value that is not one of The command was rejected because the parameter
these reserved queues: identified in the error response was in conflict with
SYSTEM.CHANNEL.INITQ another parameter in the command.
SYSTEM.CHANNEL.SYNCQ Programmer Response: Consult the description of the
SYSTEM.CLUSTER.COMMAND.QUEUE parameter identified to ascertain the nature of the
SYSTEM.CLUSTER.REPOSITORY.QUEUE conflict, and the correct command.
SYSTEM.COMMAND.INPUT
SYSTEM.QSG.CHANNEL.SYNCQ
SYSTEM.QSG.TRANSMIT.QUEUE 3096 (X'0C18') MQRCCF_PATH_NOT_VALID
Explanation: Path not valid.
3091 (X'0C13') MQRCCF_ACTION_VALUE_ERROR
The path specified was not valid.
Explanation: Action value not valid.
Programmer Response: Specify a valid path.
The value specified for Action is not valid. There is
only one valid value.
3097 (X'0C19') MQRCCF_PARM_SYNTAX_ERROR
Explanation: Syntax error found in parameter.
MQACT_FORCE_REMOVE as the value of the Action
parameter. The parameter specified contained a syntax error.
Programmer Response: Check the syntax for this
3092 (X'0C14') parameter.
MQRCCF_COMMS_LIBRARY_ERROR
Explanation: Library for requested communications 3098 (X'0C1A') MQRCCF_PWD_LENGTH_ERROR
protocol could not be loaded.
Explanation: Password length error.
The library needed for the requested communications
The password string length is rounded up by to the
protocol could not be loaded.
nearest eight bytes. This rounding causes the total
Programmer Response: Install the library for the length of the SSLCryptoHardware string to exceed its
required communications protocol, or specify a maximum.
communications protocol that has already been
Programmer Response: Decrease the size of the
installed.
password, or of earlier fields in the SSLCryptoHardware
string.
3093 (X'0C15') MQRCCF_NETBIOS_NAME_ERROR
Explanation: NetBIOS listener name not defined. 1 3150 (X'0C4E') MQRCCF_FILTER_ERROR
The NetBIOS listener name is not defined. 1 Explanation: Filter not valid.
Programmer Response: Add a local name to the 1 Either:
configuration file and retry the operation. 1 1. In an inquire command message, the specification
1 of a filter is not valid.
1 2. In a publish/subscribe command message, the
1 content-based filter expression supplied in the

PCF reason codes
1 publish/subscribe command message contains Programmer Response: Either correct the identity
1 invalid syntax, and cannot be used. value or specify a Join registration option to add this
identity to the identity set for this subscription.
1 Programmer Response:
1 1. Correct the specification of the filter parameter
1 structure in the inquire command message. 3155 (X'0C53') MQRCCF_SUBSCRIPTION_IN_USE
1 2. Correct the syntax of the filter expression in the Explanation: The subscription is in use.
1 publish/subscribe command message. The filter
An attempt to modify or deregister a subscription was
1 expression is the value of the Filter tag in the psc
attempted by a member of the identity set when they
1 folder in the MQRFH2 structure. See the Websphere
were not the only member of this set.
1 MQ Integrator V2 Programming Guidefor details of
1 valid syntax. Programmer Response: Reissue the command when
you are the only member of the identity set. To avoid
the identity set check and force the modification or
3151 (X'0C4F') MQRCCF_WRONG_USER
deregistration remove the subscription identity from
Explanation: Wrong user. the command message and reissue the command.
A publish/subscribe command message cannot be
executed on behalf of the requesting user because the 3156 (X'0C54') MQRCCF_SUBSCRIPTION_LOCKED
subscription that it would update is already owned by
Explanation: The subscription is locked.
a different user. A subscription can be updated or
deregistered only by the user that originally registered The subscription is currently exclusively locked by
the subscription. another identity.
Programmer Response: Ensure that applications that Programmer Response: Wait for this identity to
need to issue commands against existing subscriptions release the exclusive lock.
are running under the user identifier that originally
registered the subscription. Alternatively, use different
subscriptions for different users. 3157 (X'0C55') MQRCCF_ALREADY_JOINED
Explanation: The identity already has an entry for this
3152 (X'0C50') subscription.
MQRCCF_DUPLICATE_SUBSCRIPTION A Join registration option was specified but the
Explanation: The subscription already exists. subscriber identity was already a member of the
subscription’s identity set.
A matching subscription already exists.
Programmer Response: None. The command
Programmer Response: Either modify the new completed, this reason code is a warning.
subscription properties to distinguish it from the
existing subscription or deregister the existing
subscription. Then reissue the command. 1 3160 (X'0C58') MQRCCF_OBJECT_IN_USE
1 Explanation: Object in use by another command.
3153 (X'0C51') MQRCCF_SUB_NAME_ERROR 1 A modification of an object was attempted while the
Explanation: The subscription name parameter is in 1 object was being modified by another command.
error. 1 Programmer Response: Retry the command.
Either the subscription name is of an invalid format or
a matching subscription already exists with no 1 3161 (X'0C59') MQRCCF_UNKNOWN_FILE_NAME
subscription name.
1 Explanation: File not defined to CICS.
Programmer Response: Either correct the subscription
name or remove it from the command and reissue the 1 A file name parameter identifies a file that is not
command. 1 defined to CICS.
1 Programmer Response: Provide a valid file name or
3154 (X'0C52') MQRCCF_SUB_IDENTITY_ERROR 1 create a CSD definition for the required file.
Explanation: The subscription identity parameter is in
error. 1 3162 (X'0C5A') MQRCCF_FILE_NOT_AVAILABLE
Either the supplied value exceeds the maximum length 1 Explanation: File not available to CICS.
allowed or the subscription identity is not currently a 1 A file name parameter identifies a file that is defined to
member of the subscription’s identity set and a Join 1 CICS, but is not available.
registration option was not specified.

PCF reason codes
1 Programmer Response: Check that the CSD definition

1 3170 (X'0C62') MQRCCF_PROFILE_NAME_ERROR
1 for the file is correct and enabled.
1 Explanation: Profile name not valid.
1 3163 (X'0C5B') MQRCCF_DISC_RETRY_ERROR 1 A profile name is not valid. Profile names may include
1 wildcard characters or may be given explicitly. If you
1 Explanation: Disconnection retry count not valid. 1 give an explicit profile name, then the object identified
1 The DiscRetryCount value was not valid. 1 by the profile name must exist. This error may also
1 occur if you specify more than one double asterisk in a
1 Programmer Response: Specify a valid count. 1 profile name.
1 Programmer Response: Specify a valid name.
1 3164 (X'0C5C') MQRCCF_ALLOC_RETRY_ERROR
1 Explanation: Allocation retry count not valid. 1 3171 (X'0C63') MQRCCF_AUTH_VALUE_ERROR
1 The AllocRetryCount value was not valid. 1 Explanation: Authorization value not valid.
1 Programmer Response: Specify a valid count. 1 A value for the AuthorizationList or AuthorityRemove
1 or AuthorityAdd parameter was not valid.
1 3165 (X'0C5D') 1 Programmer Response: Specify a valid value.
1 MQRCCF_ALLOC_SLOW_TIMER_ERROR
1 Explanation: Allocation slow retry timer value not 1 3172 (X'0C64') MQRCCF_AUTH_VALUE_MISSING
1 valid.
1 Explanation: Authorization value required but
1 The AllocRetrySlowTimer value was not valid. 1 missing.
1 Programmer Response: Specify a valid timer value. 1 A parameter specifying authorization values must be
1 supplied.
1 3166 (X'0C5E') 1 Programmer Response: Specify the required
1 MQRCCF_ALLOC_FAST_TIMER_ERROR 1 parameter.
1 Explanation: Allocation fast retry timer value not
1 valid. 1 3173 (X'0C65') MQRCCF_OBJECT_TYPE_MISSING
1 The AllocRetryFastTimer value was not valid. 1 Explanation: Object type value required but missing.
1 Programmer Response: Specify a valid value. 1 A parameter specifying the object type must be
1 supplied.
1 3167 (X'0C5F') MQRCCF_PORT_NUMBER_ERROR 1 Programmer Response: Specify the required
1 Explanation: Port number value not valid. 1 parameter.
1 The PortNumber value was not valid.
1 3174 (X'0C66') MQRCCF_CONNECTION_ID_ERROR
1 Programmer Response: Specify a valid port number
1 value. 1 Explanation: Error in connection id parameter.
1 The ConnectionId specified was not valid.
1 3168 (X'0C60') 1 Programmer Response: Specify a valid connection id.
1 MQRCCF_CHL_SYSTEM_NOT_ACTIVE
1 Explanation: Channel system is not active. 1 3175 (X'0C67') MQRCCF_LOG_TYPE_ERROR
1 An attempt was made to start a channel while the 1 Explanation: Log type not valid.
1 channel system was inactive.
1 The log type value specified was not valid.
1 Programmer Response: Activate the channel system
1 before starting a channel. 1 Programmer Response: Specify a valid log type value.
1 3169 (X'0C61') MQRCCF_ENTITY_NAME_MISSING 1 3176 (X'0C68')

1 MQRCCF_PROGRAM_NOT_AVAILABLE
1 Explanation: Entity name required but missing.
1 Explanation: Program not available.
1 A parameter specifying entity names must be supplied.
1 A request to start or stop a service failed because the
1 Programmer Response: Specify the required 1 request to start the program failed. This could be
1 parameter.

PCF reason codes
1 because the program could not be found at the 1 v The RACF z/OS router table is incorrect
1 specified location, or that insufficient system resources
1 Programmer Response: For information about
1 are available currently to start it.
1 resolving the problem, see the explanations of messages
1 Programmer Response: Check that the correct name is 1 CSQH003I and CSQH004I.
1 specified in the definition of the service, and that the
1 program is in the appropriate libraries, before retrying
1 3203 (X'0C83') MQRCCF_PARM_CONFLICT
1 the request.
1 Explanation: Incompatible parameters or parameter
1 values.
1 3177 (X'0C69')
1 MQRCCF_PROGRAM_AUTH_FAILED 1 The parameters or parameter values for a command are
1 incompatible. One of the following occurred:
1 Explanation: Program not available.
1 v A parameter was not specified that is required by
1 A request to start or stop a service failed because the 1 another parameter or parameter value.
1 user does not have sufficient access authority to start 1 v A parameter or parameter value was specified that is
1 the program at the specified location. 1 not allowed with some other parameter or parameter
1 value.
1 Programmer Response: Correct the progam name and 1 v The values for two specified parameters were not
1 location, and the user’s authority, before retrying the 1 both blank or non-blank.
1 request. 1 v The values for two specified parameters were
1 incompatible.
1 3200 (X'0C80') MQRCCF_NONE_FOUND 1 The parameters in question may be returned in the
1 Explanation: No items found matching request 1 message (with parameter identifiers
1 criteria. 1 MQIACF_PARAMETER_ID).
1 An Inquire command found no items that matched the 1 Programmer Response: Reissue the command with
1 specified name and satisfied any other criteria 1 correct parameters and values.
1 requested.
1 3204 (X'0C84') MQRCCF_COMMAND_INHIBITED
1 3201 (X'0C81') MQRCCF_SECURITY_SWITCH_OFF 1 Explanation: Commands not allowed at present time.
1 Explanation: Security refresh or reverification not 1 The queue manager cannot accept commands at the
1 processed, security switch set OFF. 1 present time, because it is restarting or terminating, or
1 Either 1 because the command server is not running.
1 v a Reverify Security command was issued, but the
1 subsystem security switch is off, so there are no
1 3205 (X'0C85') MQRCCF_OBJECT_BEING_DELETED
1 internal control tables to flag for reverification; or
1 v a Refresh Security command was issued, but the 1 Explanation: Object is being deleted.
1 security switch for the requested class or the
1 The object specified on a command is in the process of
1 subsystem security switch is off.
1 being deleted, so the command is ignored.
1 The switch in question may be returned in the message
1 (with parameter identifier
1 3207 (X'0C87')
1 MQIACF_SECURITY_SWITCH).
1 MQRCCF_STORAGE_CLASS_IN_USE
1 Explanation: Storage class is active or queue is in use.
1 3202 (X'0C82')
1 MQRCCF_SECURITY_REFRESH_FAILED 1 The command for a local queue involved a change to
1 the StorageClass value, but there are messages on the
1 Explanation: Security refresh did not take place.
1 queue, or other threads have the queue open.
1 A SAF RACROUTE REQUEST=STAT call to your
1 Programmer Response: Remove the messages from
1 external security manager (ESM) returned a non-zero
1 the queue, or wait until any other threads have closed
1 return code. In consequence, the requested security
1 the queue.
1 refresh could not be done. The security item affected
1 may be returned in the message (with parameter
1 identifier MQIACF_SECURITY_ITEM). 1 3208 (X'0C88')
1 MQRCCF_OBJECT_NAME_RESTRICTED
1 Possible causes of this problem are:
1 v The class is not installed 1 Explanation: Incompatible object name and type.
1 v The class is not active
1 v The external security manager (ESM) is not active 1 The command used a reserved object name with an
1 incorrect object type or subtype. The object is only

PCF reason codes
1 allowed to be of a predetermined type, as listed in the

1 3212 (X'0C8C') MQRCCF_Q_MGR_NOT_IN_QSG
1 explanation of message CSQM108I.
1 Explanation: Queue manager is not in a
1 queue-sharing group.
1 3209 (X'0C89')
1 MQRCCF_OBJECT_LIMIT_EXCEEDED 1 The command or its parameters are not allowed when
1 the queue manager is not in a queue-sharing group.
1 Explanation: Local queue limit exceeded. 1 The parameter in question may be returned in the
1 The command failed because no more local queues 1 message (with parameter identifier
1 could be defined. There is an implementation limit of 1 MQIACF_PARAMETER_ID).
1 524 287 for the total number of local queues that can
1 Programmer Response: Reissue the command
1 exist. For shared queues, there is a limit of 512 queues
1 correctly.
1 in a single coupling facility structure.
1 Programmer Response: Delete any existing queues 1 3213 (X'0C8D') MQRCCF_ATTR_VALUE_FIXED
1 that are no longer required.
1 Explanation: Parameter value cannot be changed.
1 3210 (X'0C8A') MQRCCF_OBJECT_OPEN_FORCE 1 The value for a parameter cannot be changed. The
1 parameter in question may be returned in the message
1 Explanation: Object is in use, but could be changed 1 (with parameter identifier MQIACF_PARAMETER_ID).
1 specifying Force as MQFC_YES.
1 Programmer Response: To change the parameter, the
1 The object specified is in use. This could be because it
1 object must be deleted and then created again with the
1 is open through the API, or for certain parameter
1 new value.
1 changes, because there are messages currently on the
1 queue. The requested changes can be made by
1 specifying Force as MQFC_YES on a Change 1 3215 (X'0C8F') MQRCCF_NAMELIST_ERROR
1 command.
1 Explanation: Namelist is empty or wrong type.
1 Programmer Response: Wait until the object is not in
1 A namelist used to specify a list of clusters has no
1 use. Alternatively specify Force as MQFC_YES for a
1 names in it or does not have type MQNT_CLUSTER or
1 change command.
1 MQNT_NONE.
1 Programmer Response: Reissue the command
1 3211 (X'0C8B') MQRCCF_DISPOSITION_CONFLICT
1 specifying a namelist that is not empty and has a
1 Explanation: Parameters are incompatible with 1 suitable type.
1 disposition.
1 The parameters or parameter values for a command are 1 3217 (X'0C91')
1 incompatible with the disposition of an object. One of 1 MQRCCF_NO_CHANNEL_INITIATOR
1 the following occurred:
1 Explanation: Channel initiator not active.
1 v A value specified for the object name or other
1 parameter is not allowed for a local queue whose 1 The command requires the channel initiator to be
1 disposition is shared or a model queue used to create 1 started.
1 a dynamic queue that is shared.
1 v A value specified for a parameter is not allowed for
1 an object with such disposition. 1 3218 (X'0C93')
1 v A value specified for a parameter must be non-blank 1 MQRCCF_CHANNEL_INITIATOR_ERROR
1 for an object with such disposition. 1 Explanation: Channel initiator cannot be started, or no
1 v The CommandScope and QSGDisposition or 1 suitable channel initiator is available.
1 ChannelDisposition parameter values are
1 incompatible. 1 One of the following:
1 v The action requested for a channel cannot be 1 v The channel initiator cannot be started because:
1 performed because it has the wrong disposition. 1 – It is already active.
1 – There are insufficient system resources.
1 The parameter and disposition in question may be 1 – The queue manager was shutting down.
1 returned in the message (with parameter identifiers
1 MQIACF_PARAMETER_ID and MQIA_QSG_DISP). 1 v The shared channel cannot be started because there
1 was no suitable channel initiator available for any
1 Programmer Response: Reissue the command with 1 active queue manager in the queue-sharing group.
1 correct parameters and values. 1 This could be because:
1 – No channel initiators are running.

PCF reason codes
1 – The channel initiators that are running are too

1 3227 (X'0C9B') MQRCCF_FUNCTION_RESTRICTED
1 busy to allow any channel, or a channel of the
1 particular type, to be started. 1 Explanation: Restricted command or parameter value
1 used.
1 3222 (X'0C96') 1 The command, or the value specified for one of its
1 MQRCCF_COMMAND_LEVEL_CONFLICT1 parameters, is not allowed because the installation and
1 customization options chosen do not allow all functions
1 Explanation: Incompatible queue manager command 1 to be used. The parameter in question may be returned
1 levels. 1 in the message (with parameter identifier
1 Changing the CFLevel parameter of a CF structure, or 1 MQIACF_PARAMETER_ID).
1 deleting a CF structure, requires that all queue
1 managers in the queue-sharing group have a command 1 3228 (X'0C9C') MQRCCF_PARM_MISSING
1 level of at least 530. Some of the queue managers have
1 a lower level. 1 Explanation: Required parameter not specified.
1 The command did not specify a parameter or
1 3223 (X'0C97') MQRCCF_Q_ATTR_CONFLICT 1 parameter value that was required. It may be:
1 v A parameter that is always required.
1 Explanation: Queue attributes are incompatible. 1 v A parameter that is one of a set of two or more
1 The queues involved in a Move Queue command have 1 alternative required parameters.
1 different values for one or more of these attributes: 1 v A parameter that is required because some other
1 DefinitionType, HardenGetBackout, Usage. Messages 1 parameter was specified.
1 cannot be moved safely if these attributes differ. 1 v A parameter that is a list of values which has too
1 few values.
1 3224 (X'0C98') MQRCCF_EVENTS_DISABLED 1 The parameter in question may be returned in the

1 message (with parameter identifier
1 Explanation: Events not enabled. 1 MQIACF_PARAMETER_ID).
1 The command required performance or configuration 1 Programmer Response: Reissue the command with
1 events to be enabled. 1 correct parameters and values.
1 Programmer Response: Use the Change Queue
1 manager command to enable the events if required. 1 3229 (X'0C9D') MQRCCF_PARM_VALUE_ERROR
1 Explanation: Parameter value invalid.
1 3225 (X'0C99')
1 MQRCCF_COMMAND_SCOPE_ERROR 1 The value specified for a parameter was not acceptable.
1 It may be:
1 Explanation: Queue-sharing group error. 1 v Outside the acceptable numeric range for the
1 While processing a command that used the 1 parameter.
1 CommandScope parameter, an error occurred while trying 1 v Not one of a list of acceptable values for the
1 to send data to the coupling facility. 1 parameter.
1 v Using characters that are invalid for the parameter.
1 Programmer Response: Notify your system 1 v Completely blank, when such is not allowed for the
1 programmer. 1 parameter.
1 v A filter value that is invalid for the parameter being
1 3226 (X'0C9A') 1 filtered.
1 MQRCCF_COMMAND_REPLY_ERROR 1 The parameter in question may be returned in the
1 Explanation: Error saving command reply 1 message (with parameter identifier
1 information. 1 MQIACF_PARAMETER_ID).
1 While processing a command that used the 1 Programmer Response: Reissue the command with
1 CommandScope parameter, or a command for the channel 1 correct parameters and values.
1 initiator, an error occurred while trying to save
1 information about the command. 1 3230 (X'0C9E')
1 Programmer Response: The most likely cause is 1 MQRCCF_COMMAND_LENGTH_ERROR
1 insufficient storage. If the problem persists, you may 1 Explanation: Command exceeds allowable length.
1 need to restart the queue manager after making more
1 storage available. 1 The command is so large that its internal form has
1 exceeded the maximum length allowed. The size of the
1 internal form of the command is affected by both the

PCF reason codes
1 length, and the complexity of the command. 1 Programmer Response: For information about the
1 error, see the explanation of the corresponding error
1 message. Error nnn generally corresponds to message
1 3231 (X'0C9F') 1 CSQXnnn, although there are some exceptions. The
1 MQRCCF_COMMAND_ORIGIN_ERROR
1 section Distributed queuing message codes in the
1 Explanation: Command issued incorrectly. 1 WebSphere MQ for z/OS Messages and Codes book gives
1 full details.
1 The command cannot be issued using command server.
1 This is an internal error.
1 3236 (X'0CA4') MQRCCF_CF_STRUC_ERROR
1 Programmer Response: Notify your system
1 programmer. 1 Explanation: CF structure error.
1 A command could not be processed because of a
1 3232 (X'0CA0') MQRCCF_LISTENER_CONFLICT 1 coupling facility or CF structure error. It may be:
1 v A Backup CF Structure or Recover CF Structure
1 Explanation: Address conflict for listener. 1 command when the status of the CF structure is
1 A listener was already active for a port and IP address 1 unsuitable. In this case, the CF structure status may
1 combination that conflicted with the Port and 1 be returned in the message together with the CF
1 IPAddress values specified by a Start Channel Listener 1 structure name (with parameter identifiers
1 or Stop Channel Listener command. The Port and 1 MQIACF_CF_STRUC_STATUS and
1 IPAddress value combination specified must match a 1 MQCA_CF_STRUC_NAME).
1 combination for which the listener is active. It cannot 1 v A command could not access an object because of an
1 be a superset or a subset of that combination. 1 error in the coupling facility information, or because
1 a CF structure has failed. In this case, the name of
1 Programmer Response: Reissue the command with 1 the object involved may be returned in the message
1 correct values, if required. 1 (with parameter identifier MQCA_Q_NAME, for
1 example).
1 3233 (X'0CA1') MQRCCF_LISTENER_STARTED 1 v A command involving a shared channel could not
1 access the channel status or synchronization key
1 Explanation: Listener is started. 1 information.
1 An attempt was made to start a listener, but it is 1 Programmer Response: In the case of a Backup CF
1 already active for the requested TransportType, 1 Structure or Recover CF Structure command, take
1 InboundDisposition, Port, and IPAddress values. The 1 action appropriate to the CF struture status reported.
1 requested parameter values may be returned in the
1 message, if applicable (with parameter identifiers 1 In other cases, check for error messages on the console
1 MQIACH_XMIT_PROTOCOL_TYPE, 1 log that might relate to the problem. Check whether the
1 MQIACH_INBOUND_DISP, 1 coupling facility structure has failed and check that
1 MQIACH_PORT_NUMBER, MQCACH_IP_ADDRESS). 1 DB2 is available.
1 3234 (X'0CA2') MQRCCF_LISTENER_STOPPED 1 3237 (X'0CA5') MQRCCF_UNKNOWN_USER_ID
1 Explanation: Listener is stopped. 1 Explanation: User identifier not found.
1 An attempt was made to stop a listener, but it is not 1 A user identifier specified in a Reverify Security
1 active or already stopping for the requested 1 command was not valid because there was no entry
1 TransportType, InboundDisposition, Port, and 1 found for it in the internal control table. This could be
1 IPAddress values. The requested parameter values may 1 because the identifier was entered incorrectly in the
1 be returned in the message, if applicable (with 1 command, or because it was not in the table (for
1 parameter identifiers 1 example, because it had timed-out). The user identifier
1 MQIACH_XMIT_PROTOCOL_TYPE, 1 in question may be returned in the message (with
1 MQIACH_INBOUND_DISP, 1 parameter identifier MQCACF_USER_IDENTIFIER).
1 MQIACH_PORT_NUMBER, MQCACH_IP_ADDRESS).
1 3238 (X'0CA6') MQRCCF_UNEXPECTED_ERROR
1 3235 (X'0CA3') MQRCCF_CHANNEL_ERROR 1 Explanation: Unexpected or severe error.
1 Explanation: Channel command failed. 1 An unexpected or severe error or other failure
1 A channel command failed because of an error in the 1 occurred. A code associated with the error may be
1 channel definition, or at the remote end of the channel, 1 returned in the message (with parameter identifier
1 or in the communications system. An error identifier 1 MQIACF_ERROR_ID).
1 value nnn may be returned in the message (with 1 Programmer Response: Notify your system
1 parameter identifier MQIACF_ERROR_ID). 1 programmer.
PCF reason codes
1 Programmer Response: Specify a valid structure

1 3239 (X'0CA7') MQRCCF_NO_XCF_PARTNER
1 length.
1 Explanation: MQ is not connected to the XCF partner.
1 The command involving the IMS Bridge cannot be 1 3246 (X'0CAE')
1 processed because MQ is not connected to the XCF 1 MQRCCF_CFSF_OPERATOR_ERROR
1 partner. The group and member names of the XCF
1 Explanation: Parameter count not valid.
1 partner in question may be returned in the message
1 (with parameter identifiers 1 The MQCFSF Operator field value was not valid.
1 MQCA_XCF_GROUP_NAME and
1 MQCA_XCF_MEMBER_NAME). 1 Programmer Response: Specify a valid operator value.
1 3240 (X'0CA8') MQRCCF_CFGR_PARM_ID_ERROR 1 3247 (X'0CAF') MQRCCF_CFSF_PARM_ID_ERROR
1 Explanation: Parameter identifier is not valid. 1 Explanation: Parameter identifier is not valid.
1 The MQCFGR Parameter field value was not valid. 1 The MQCFSF Parameter field value was not valid.
1 Programmer Response: Specify a valid parameter 1 Programmer Response: Specify a valid parameter
1 identifier. 1 identifier.
1 3241 (X'0CA9') MQRCCF_CFIF_LENGTH_ERROR 1 3248 (X'0CB0') MQRCCF_TOO_MANY_FILTERS
1 Explanation: Structure length not valid. 1 Explanation: Too many filters.
1 The MQCFIF StrucLength field value was not valid. 1 The command contained more than the maximum
1 permitted number of filter structures.
1 length. 1 Programmer Response: Specify the command
1 correctly.
1 3242 (X'0CAA') MQRCCF_CFIF_OPERATOR_ERROR

1 3249 (X'0CB1') MQRCCF_LISTENER_RUNNING
1 Explanation: Parameter count not valid.
1 Explanation: Listener is running.
1 The MQCFIF Operator field value was not valid.
1 An attempt was made to perform an operation on a
1 Programmer Response: Specify a valid operator value. 1 listener, but it is currently active.
1 Programmer Response: Stop the listener if required.
1 3243 (X'0CAB') MQRCCF_CFIF_PARM_ID_ERROR
1 Explanation: Parameter identifier is not valid. 1 3250 (X'0CB2')
1 MQRCCF_LSTR_STATUS_NOT_FOUND
1 The MQCFIF Parameter field value was not valid, or
1 specifies a parameter that cannot be filtered, or that is 1 Explanation: Listener status not found.
1 also specified as a parameter to select a subset of
1 objects. 1 For Inquire Listener Status, no listener status is
1 available for the specified listener. This may indicate
1 Programmer Response: Specify a valid parameter 1 that the listener has not been used.
1 identifier.
1 Programmer Response: None, unless this is
1 unexpected, in which case consult your systems
1 3244 (X'0CAC') 1 administrator.
1 MQRCCF_CFSF_FILTER_VAL_LEN_ERR
1 Explanation: Filter value length not valid. 1 3251 (X'0CB3') MQRCCF_SERVICE_RUNNING
1 The MQCFSF FilterValueLength field value was not 1 Explanation: Service is running.
1 valid.
1 An attempt was made to perform an operation on a
1 Programmer Response: Specify a valid length. 1 service, but it is currently active.
1 Programmer Response: Stop the service if required.
1 3245 (X'0CAD') MQRCCF_CFSF_LENGTH_ERROR
1 Explanation: Structure length not valid.
1 The MQCFSF StrucLength field value was not valid.

PCF reason codes
1 3252 (X'0CB4') 3258 (X'0CBA') MQRCCF_CFGR_LENGTH_ERROR

1 MQRCCF_SERV_STATUS_NOT_FOUND
Explanation: Structure length not valid.
1 Explanation: Service status not found.
The MQCFGR StrucLength field value was not valid.
1 For Inquire Service Status, no service status is available
1 for the specified service. This may indicate that the
length.
1 service has not been used.
1 Programmer Response: None, unless this is
3259 (X'0CBB')
1 unexpected, in which case consult your systems
MQRCCF_CFGR_PARM_COUNT_ERROR
1 administrator.
Explanation: Parameter count not valid.
1 3253 (X'0CB5') MQRCCF_SERVICE_STOPPED The MQCFGR ParameterCount field value was not
valid. The value was negative or greater than the
1 Explanation: Service is stopped.
maximum permitted for the parameter identifier
1 An attempt was made to stop a service, but it is not specified in the Parameter field.
1 active or already stopping.
Programmer Response: Specify a valid count for the
parameter.
3254 (X'0CB6') MQRCCF_CFBS_DUPLICATE_PARM
Explanation: Duplicate parameter. 1 3260 (X'0CBC') MQRCCF_CONN_NOT_STOPPED
Two MQCFBS structures with the same parameter 1 Explanation: Connection not stopped.
identifier were present.
1 The Stop Connection command could not be executed,
Programmer Response: Check for and remove 1 so the connection was not stopped.
3261 (X'0CBD')
3255 (X'0CB7') MQRCCF_CFBS_LENGTH_ERROR MQRCCF_SERVICE_REQUEST_PENDING
Explanation: Structure length not valid. Explanation: A Suspend or Resume Queue Manager
command was issued, or a Refresh Security command,
The MQCFBS StrucLength field value was not valid.
but such a command is currently in progress.
Programmer Response: Wait until the current request
length.
completes, then reissue the command if necessary.
3256 (X'0CB8') MQRCCF_CFBS_PARM_ID_ERROR

1 3262 (X'0CBE') MQRCCF_NO_START_CMD
1 Explanation: No start command.
The MQCFBS Parameter field value was not valid.
1 The service cannot be started because no start
Programmer Response: Specify a valid parameter 1 command is specified in the service definition.
identifier.
1 Programmer Response: Correct the definition of the
1 service.
3257 (X'0CB9')
MQRCCF_CFBS_STRING_LENGTH_ERR
1 3263 (X'0CBF') MQRCCF_NO_STOP_CMD
Explanation: String length not valid.
1 Explanation: No stop command.
The MQCFBS StringLength field value was not valid.
1 The service cannot be stopped because no stop
The value was negative or greater than the maximum
1 command is specified in the service definition.
permitted length of the parameter specified in the
Parameter field. 1 Programmer Response: Correct the definition of the
1 service.
Programmer Response: Specify a valid string length
for the parameter.
1 3264 (X'0CC0') MQRCCF_CFBF_LENGTH_ERROR
1 Explanation: Structure length not valid.
1 The MQCFBF StrucLength field value was not valid.

PCF reason codes

4003 (X'0FA3')
1 length. MQRCCF_LIKE_OBJECT_WRONG_TYPE
Explanation: New and existing objects have different
1 3265 (X'0CC1') MQRCCF_CFBF_PARM_ID_ERROR subtype.
1 Explanation: Parameter identifier is not valid. An attempt was made to create an object based on the
1 The MQCFBF Parameter field value was not valid. definition of an existing object, but the new and
existing objects had different subtypes.
1 Programmer Response: Specify a valid parameter
1 identifier. Programmer Response: Ensure that the new object has
the same subtype as the one on which it is based.
1 3266 (X'0CC2')
1 MQRCCF_CFBF_FILTER_VAL_LEN_ERR 4004 (X'0FA4') MQRCCF_OBJECT_OPEN
1 Explanation: Filter value length not valid. Explanation: Object is open.
1 The MQCFBF FilterValueLength field value was not An attempt was made to operate on an object that was
1 valid. in use.
1 Programmer Response: Specify a valid length. Programmer Response: Wait until the object is not in
use, and then retry the operation. Alternatively specify
Force as MQFC_YES for a change command.
1 3267 (X'0CC3') MQRCCF_CFBF_OPERATOR_ERROR
1 Explanation: Parameter count not valid. 4005 (X'0FA5') MQRCCF_ATTR_VALUE_ERROR
1 The MQCFBF Operator field value was not valid. Explanation: Attribute value not valid or repeated.
1 Programmer Response: Specify a valid operator value. One or more of the attribute values specified was not
valid or was repeated. The error response message
1 3268 (X'0CC4') contains the failing attribute selectors (with parameter
1 MQRCCF_LISTENER_STILL_ACTIVE identifier MQIACF_PARAMETER_ID).
1 Explanation: Listener still active. Programmer Response: Specify the attribute values
correctly.
1 An attempt mas made to stop a listener, but it failed
1 and the listener is still active. For example, the the
1 listener may still have active channels. 4006 (X'0FA6') MQRCCF_UNKNOWN_Q_MGR
1 Programmer Response: Wait for the active connections Explanation: Queue manager not known.
1 to the listener to complete before retrying the request. The queue manager specified was not known.
Programmer Response: Specify the name of the queue
4001 (X'0FA1') manager to which the command is sent, or blank.
MQRCCF_OBJECT_ALREADY_EXISTS
Explanation: Object already exists. 4007 (X'0FA7') MQRCCF_Q_WRONG_TYPE
An attempt was made to create an object, but the object Explanation: Action not valid for the queue of
already existed and the Replace parameter was not specified type.
specified as MQRP_YES.
An attempt was made to perform an action on a queue
Programmer Response: Specify Replace as of the wrong type.
MQRP_YES, or use a different name for the object to be
created. Programmer Response: Specify a queue of the correct
type.
4002 (X'0FA2') MQRCCF_OBJECT_WRONG_TYPE
4008 (X'0FA8') MQRCCF_OBJECT_NAME_ERROR
Explanation: Object has wrong type or disposition.
Explanation: Name not valid.
An object already exists with the same name but a
different subtype or disposition from that specified by An object or other name name was specified using
the command. characters that were not valid.
Programmer Response: Ensure that the specified Programmer Response: Specify only valid characters
object is the same subtype and disposition. for the name.

PCF reason codes
v For TCP the remote system might not recognize the

4009 (X'0FA9') MQRCCF_ALLOCATE_FAILED
local system as valid, or the TCP listener program
Explanation: Allocation failed. might not be started.
An attempt to allocate a conversation to a remote Programmer Response: Correct the error or restart the
system failed. The error may be due to an entry in the listener program.
channel definition that is not valid, or it might be that
the listening program at the remote system is not
4013 (X'0FAD') MQRCCF_ENTRY_ERROR
running.
Explanation: Connection name not valid.
Programmer Response: Ensure that the channel
definition is correct, and start the listening program if The connection name in the channel definition could
necessary. If the error persists, consult your systems not be resolved into a network address. Either the
administrator. name server does not contain the entry, or the name
server was not available.
4010 (X'0FAA') MQRCCF_HOST_NOT_AVAILABLE Programmer Response: Ensure that the connection
name is correctly specified and that the name server is
Explanation: Remote system not available.
available.
An attempt to allocate a conversation to a remote
system was unsuccessful. The error might be transitory,
4014 (X'0FAE') MQRCCF_SEND_FAILED
and the allocate might succeed later. This reason can
occur if the listening program at the remote system is Explanation: Send failed.
not running.
An error occurred while sending data to a remote
Programmer Response: Ensure that the listening system. This might be caused by a communications
program is running, and retry the operation. failure.
4011 (X'0FAB') administrator.
MQRCCF_CONFIGURATION_ERROR
Explanation: Configuration error. 4015 (X'0FAF') MQRCCF_RECEIVED_DATA_ERROR
There was a configuration error in the channel Explanation: Received data error.
definition or communication subsystem, and allocation
of a conversation was not possible. This might be An error occurred while receiving data from a remote
caused by one of the following: system. This might be caused by a communications
failure.
v For LU 6.2, either the ModeName or the TpName is
incorrect. The ModeName must match that on the Programmer Response: Consult your systems
remote system, and the TpName must be specified. administrator.
(On OS/400, these are held in the communications
Side Object.)
4016 (X'0FB0') MQRCCF_RECEIVE_FAILED
v For LU 6.2, the session might not be established.
Explanation: Receive failed.
v For TCP, the ConnectionName in the channel
definition cannot be resolved to a network address. The receive operation failed.
This might be because the name has not been
correctly specified, or because the name server is not
operation.
available.
v The requested communications protocol might not be
supported on the platform. 4017 (X'0FB1') MQRCCF_CONNECTION_CLOSED
Programmer Response: Identify the error and take Explanation: Connection closed.
appropriate action. An error occurred while receiving data from a remote
system. The connection to the remote system has
4012 (X'0FAC') MQRCCF_CONNECTION_REFUSED unexpectedly terminated.
Explanation: Connection refused. Programmer Response: Contact your systems

administrator.
The attempt to establish a connection to a remote
system was rejected. The remote system might not be
configured to allow a connection from this system.
v For LU 6.2 either the user ID or the password
supplied to the remote system is incorrect.

PCF reason codes
4018 (X'0FB2') MQRCCF_NO_STORAGE 4027 (X'0FBB') MQRCCF_MQOPEN_FAILED

Explanation: Not enough storage available. Explanation: MQOPEN call failed.
Insufficient storage is available. Programmer Response: Check whether the queue
manager is active, and the queues involved are
correctly set up.
administrator.
4028 (X'0FBC') MQRCCF_MQGET_FAILED

4019 (X'0FB3') MQRCCF_NO_COMMS_MANAGER
Explanation: MQGET call failed.
Explanation: Communications manager not available.
Programmer Response: Check whether the queue
The communications subsystem is not available.
Programmer Response: Ensure that the correctly set up, and enabled for MQGET.
communications subsystem has been started.
4029 (X'0FBD') MQRCCF_MQPUT_FAILED
4020 (X'0FB4')
Explanation: MQPUT call failed.
MQRCCF_LISTENER_NOT_STARTED
Explanation: Listener not started.
The listener program could not be started. Either the correctly set up, and not inhibited for puts.
communications subsystem has not been started, or the
number of current channels using the communications
4030 (X'0FBE') MQRCCF_PING_ERROR
subsystem is the maximum allowed, or there are too
many jobs waiting in the queue. Explanation: Ping error.
Programmer Response: Ensure the communications A ping operation can only be issued for a sender or
subsystem is started or retry the operation later. server channel. If the local channel is a receiver
Increase the number of current channels allowed, if channel, you must issue the ping from a remote queue
appropriate. manager.
Programmer Response: Reissue the ping request for a
4024 (X'0FB8') MQRCCF_BIND_FAILED different channel of the correct type, or for a receiver
channel from a different queue manager.
Explanation: Bind failed.
The bind to a remote system during session negotiation
4031 (X'0FBF') MQRCCF_CHANNEL_IN_USE
has failed.
Explanation: Channel in use.
administrator. An attempt was made to perform an operation on a
channel, but the channel is currently active.
4025 (X'0FB9') MQRCCF_CHANNEL_INDOUBT Programmer Response: Stop the channel or wait for it
to terminate.
Explanation: Channel in-doubt.
The requested operation cannot complete because the
4032 (X'0FC0') MQRCCF_CHANNEL_NOT_FOUND
channel is in doubt.
Explanation: Channel not found.
Programmer Response: Examine the status of the
channel, and either restart a channel to resolve the The channel specified does not exist.
in-doubt state, or resolve the channel.
Programmer Response: Specify the name of a channel
which exists.
4026 (X'0FBA') MQRCCF_MQCONN_FAILED
Explanation: MQCONN call failed. 4033 (X'0FC1')
MQRCCF_UNKNOWN_REMOTE_CHANNEL
manager is active. Explanation: Remote channel not known.
There is no definition of the referenced channel at the
remote system.
Programmer Response: Ensure that the local channel
is correctly defined. If it is, add an appropriate channel

PCF reason codes
definition at the remote system.

4040 (X'0FC8') MQRCCF_COMMIT_FAILED
Explanation: Commit failed.
4034 (X'0FC2')
MQRCCF_REMOTE_QM_UNAVAILABLE An error was received when an attempt was made to
commit a unit of work.
Explanation: Remote queue manager not available.
The channel cannot be started because the remote
administrator.
queue manager is not available.
Programmer Response: Start the remote queue
4041 (X'0FC9') MQRCCF_WRONG_CHANNEL_TYPE
manager.
Explanation: Parameter not allowed for this channel
type.
4035 (X'0FC3')
MQRCCF_REMOTE_QM_TERMINATING The parameter is not allowed for the type of channel
being created, copied, or changed. Refer to the
Explanation: Remote queue manager terminating.
description of the parameter in error to determine the
The channel is ending because the remote queue types of channel for which the parameter is valid
manager is terminating.
Programmer Response: Remove the parameter.
Programmer Response: Restart the remote queue
manager.
4042 (X'0FCA')
MQRCCF_CHANNEL_ALREADY_EXISTS
4036 (X'0FC4') MQRCCF_MQINQ_FAILED
Explanation: Channel already exists.
Explanation: MQINQ call failed.
An attempt was made to create a channel but the
Programmer Response: Check whether the queue channel already existed and Replace was not specified
manager is active. as MQRP_YES.
Programmer Response: Specify Replace as
4037 (X'0FC5') MQRCCF_NOT_XMIT_Q MQRP_YES or use a different name for the channel to
be created.
Explanation: Queue is not a transmission queue.
The queue specified in the channel definition is not a 4043 (X'0FCB') MQRCCF_DATA_TOO_LARGE
transmission queue, or is in use.
Explanation: Data too large.
Programmer Response: Ensure that the queue is
specified correctly in the channel definition, and that it The data to be sent exceeds the maximum that can be
is correctly defined to the queue manager. supported for the command.
Programmer Response: Reduce the size of the data.
4038 (X'0FC6') MQRCCF_CHANNEL_DISABLED
Explanation: Channel disabled. 4044 (X'0FCC')
MQRCCF_CHANNEL_NAME_ERROR
An attempt was made to use a channel, but the channel
was disabled (that is, stopped). Explanation: Channel name error.
Programmer Response: Start the channel. The ChannelName parameter contained characters that
are not allowed for channel names.
4039 (X'0FC7') Programmer Response: Specify a valid name.
MQRCCF_USER_EXIT_NOT_AVAILABLE
Explanation: User exit not available. 4045 (X'0FCD') MQRCCF_XMIT_Q_NAME_ERROR
The channel was terminated because the user exit Explanation: Transmission queue name error.
specified does not exist.
The XmitQName parameter contains characters that are
Programmer Response: Ensure that the user exit is not allowed for queue names. This reason code also
correctly specified and the program is available. occurs if the parameter is not present when a sender or
server channel is being created, and no default value is
available.
Programmer Response: Specify a valid name, or add
the parameter.

PCF reason codes
4047 (X'0FCF') MQRCCF_MCA_NAME_ERROR 4053 (X'0FD5')

MQRCCF_MCA_NAME_WRONG_TYPE
Explanation: Message channel agent name error.
Explanation: Message channel agent name not
The MCAName value contained characters that are not
allowed for this channel type.
allowed for program names on the platform in
question. The MCAName parameter is only allowed for sender,
server or requester channel types.
Programmer Response: Specify a valid name.
4048 (X'0FD0')
MQRCCF_SEND_EXIT_NAME_ERROR 4054 (X'0FD6') MQRCCF_DISC_INT_WRONG_TYPE
Explanation: Channel send exit name error. Explanation: Disconnection interval not allowed for
this channel type.
The SendExit value contained characters that are not
allowed for program names on the platform in The DiscInterval parameter is only allowed for sender
question. or server channel types.
Programmer Response: Specify a valid name. Programmer Response: Remove the parameter.
4049 (X'0FD1') MQRCCF_SEC_EXIT_NAME_ERROR 4055 (X'0FD7')

MQRCCF_SHORT_RETRY_WRONG_TYPE
Explanation: Channel security exit name error.
Explanation: Short retry parameter not allowed for
The SecurityExit value contained characters that are
this channel type.
not allowed for program names on the platform in
question. The ShortRetryCount parameter is only allowed for
sender or server channel types.
4050 (X'0FD2')
MQRCCF_MSG_EXIT_NAME_ERROR 4056 (X'0FD8')
MQRCCF_SHORT_TIMER_WRONG_TYPE
Explanation: Channel message exit name error.
Explanation: Short timer parameter not allowed for
The MsgExit value contained characters that are not
this channel type.
question. The ShortRetryInterval parameter is only allowed for
4051 (X'0FD3') MQRCCF_RCV_EXIT_NAME_ERROR
4057 (X'0FD9')
Explanation: Channel receive exit name error.
MQRCCF_LONG_RETRY_WRONG_TYPE
The ReceiveExit value contained characters that are not
Explanation: Long retry parameter not allowed for
this channel type.
question.
The LongRetryCount parameter is only allowed for
4052 (X'0FD4')
MQRCCF_XMIT_Q_NAME_WRONG_TYPE
4058 (X'0FDA')
Explanation: Transmission queue name not allowed
MQRCCF_LONG_TIMER_WRONG_TYPE
for this channel type.
Explanation: Long timer parameter not allowed for
The XmitQName parameter is only allowed for sender or
this channel type.
server channel types.
The LongRetryInterval parameter is only allowed for

PCF reason codes
MQSCO_CELL, but this is not allowed for a dynamic

4059 (X'0FDB')
queue.
MQRCCF_PUT_AUTH_WRONG_TYPE
Programmer Response: Predefine the queue if it is to
Explanation: Put authority parameter not allowed for
have cell scope.
this channel type.
The PutAuthority parameter is only allowed for
4068 (X'0FE4')
receiver or requester channel types.
MQRCCF_CELL_DIR_NOT_AVAILABLE
Explanation: Cell directory is not available.
The Scope attribute of the queue is to be
4061 (X'0FDD') MQRCCF_MISSING_CONN_NAME
MQSCO_CELL, but no name service supporting a cell
Explanation: Connection name parameter required but directory has been configured.
missing.
Programmer Response: Configure the queue manager
The ConnectionName parameter is required for sender or with a suitable name service.
requester channel types, but is not present.
Programmer Response: Add the parameter. 4069 (X'0FE5') MQRCCF_MR_COUNT_ERROR
Explanation: Message retry count not valid.
4062 (X'0FDE') MQRCCF_CONN_NAME_ERROR
The MsgRetryCount value was not valid.
Explanation: Error in connection name parameter.
The ConnectionName parameter contains one or more 0-999 999 999.
blanks at the start of the name.
Programmer Response: Specify a valid connection 4070 (X'0FE6')
name. MQRCCF_MR_COUNT_WRONG_TYPE
Explanation: Message-retry count parameter not
4063 (X'0FDF') MQRCCF_MQSET_FAILED allowed for this channel type.
Explanation: MQSET call failed. The MsgRetryCount parameter is allowed only for
receiver and requester channels.
manager is active. Programmer Response: Remove the parameter.
4064 (X'0FE0') MQRCCF_CHANNEL_NOT_ACTIVE 4071 (X'0FE7') MQRCCF_MR_EXIT_NAME_ERROR

Explanation: Channel not active. Explanation: Channel message-retry exit name error.
An attempt was made to stop a channel, but the The MsgRetryExit value contained characters that are
channel was already stopped. not allowed for program names on the platform in
question.
Programmer Response: No action is required.
4065 (X'0FE1')
MQRCCF_TERMINATED_BY_SEC_EXIT 4072 (X'0FE8')
MQRCCF_MR_EXIT_NAME_WRONG_TYPE
Explanation: Channel terminated by security exit.
Explanation: Message-retry exit parameter not
A channel security exit terminated the channel.
allowed for this channel type.
Programmer Response: Check that the channel is
The MsgRetryExit parameter is allowed only for
attempting to connect to the correct queue manager,
and if so that the security exit is specified correctly, and
is working correctly, at both ends. Programmer Response: Remove the parameter.
4067 (X'0FE3') 4073 (X'0FE9') MQRCCF_MR_INTERVAL_ERROR

MQRCCF_DYNAMIC_Q_SCOPE_ERROR
Explanation: Message retry interval not valid.
Explanation: Dynamic queue scope error.
The MsgRetryInterval value was not valid.
The Scope attribute of the queue is to be

PCF reason codes

4080 (X'0FF0') MQRCCF_CHAD_WRONG_TYPE
0-999 999 999.
Explanation: Channel automatic definition parameter
not allowed for this channel type.
4074 (X'0FEA')
MQRCCF_MR_INTERVAL_WRONG_TYPE The ChannelAutoDef parameter is allowed only for
receiver and server-connection channels.
Explanation: Message-retry interval parameter not
allowed for this channel type. Programmer Response: Remove the parameter.
The MsgRetryInterval parameter is allowed only for
receiver and requester channels. 4081 (X'0FF1') MQRCCF_CHAD_EVENT_ERROR
Programmer Response: Remove the parameter. Explanation: Channel automatic definition event error.
The ChannelAutoDefEvent value was not valid.
4075 (X'0FEB') MQRCCF_NPM_SPEED_ERROR
Programmer Response: Specify MQEVR_ENABLED
Explanation: Nonpersistent message speed not valid. or MQEVR_DISABLED.
The NonPersistentMsgSpeed value was not valid.
4082 (X'0FF2')
Programmer Response: Specify MQNPMS_NORMAL
MQRCCF_CHAD_EVENT_WRONG_TYPE
or MQNPMS_FAST.
Explanation: Channel automatic definition event
parameter not allowed for this channel type.
4076 (X'0FEC')
MQRCCF_NPM_SPEED_WRONG_TYPE The ChannelAutoDefEvent parameter is allowed only for
Explanation: Nonpersistent message speed parameter
not allowed for this channel type. Programmer Response: Remove the parameter.
The NonPersistentMsgSpeed parameter is allowed only
for sender, receiver, server, requester, cluster sender, 4083 (X'0FF3') MQRCCF_CHAD_EXIT_ERROR
and cluster receiver channels.
Explanation: Channel automatic definition exit name
Programmer Response: Remove the parameter. error.
The ChannelAutoDefExit value contained characters
4077 (X'0FED') MQRCCF_HB_INTERVAL_ERROR that are not allowed for program names on the
platform in question.
Explanation: Heartbeat interval not valid.
The HeartbeatInterval value was not valid.
4084 (X'0FF4')
0-999 999.
MQRCCF_CHAD_EXIT_WRONG_TYPE
Explanation: Channel automatic definition exit
4078 (X'0FEE')
parameter not allowed for this channel type.
MQRCCF_HB_INTERVAL_WRONG_TYPE
The ChannelAutoDefExit parameter is allowed only for
Explanation: Heartbeat interval parameter not allowed
The HeartbeatInterval parameter is allowed only for
4085 (X'0FF5') MQRCCF_SUPPRESSED_BY_EXIT
Explanation: Action suppressed by exit program.
4079 (X'0FEF') MQRCCF_CHAD_ERROR An attempt was made to define a channel
automatically, but this was inhibited by the channel
Explanation: Channel automatic definition error.
automatic definition exit. The AuxErrorDataInt1
The ChannelAutoDef value was not valid. parameter contains the feedback code from the exit
indicating why it inhibited the channel definition.
Programmer Response: Specify MQCHAD_ENABLED
or MQCHAD_DISABLED. Programmer Response: Examine the value of the
AuxErrorDataInt1 parameter, and take any action that
is appropriate.

PCF reason codes
4086 (X'0FF6') MQRCCF_BATCH_INT_ERROR 4094 (X'0FFE')

MQRCCF_SSL_CLIENT_AUTH_ERROR
Explanation: Batch interval not valid.
Explanation: SSL client authentication not valid.
The batch interval specified was not valid.
The SSLClientAuth specified is not valid.
Programmer Response: Specify a valid batch interval
value. Programmer Response: Specify a valid client
authentication.
4087 (X'0FF7')
MQRCCF_BATCH_INT_WRONG_TYPE 1 4095 (X'0FFF')
1 MQRCCF_RETAINED_NOT_SUPPORTED
Explanation: Batch interval parameter not allowed for
this channel type. 1 Explanation: Retained messages used on restricted
1 stream.
The BatchInterval parameter is allowed only for
sender and server channels. 1 An attempt has been made to use retained messages on
1 a publish/subscribe stream defined to be restricted to
1 JMS usage. JMS does not support the concept of
1 retained messages and the request is rejected.
4088 (X'0FF8') MQRCCF_NET_PRIORITY_ERROR
1 Programmer Response: Either modify the application
Explanation: Network priority value is not valid. 1 not to use retained messages, or modify the broker
1 JmsStreamPrefix configuration parameter so that this
Programmer Response: Specify a valid value. 1 stream is not treated as a JMS stream.
4089 (X'0FF9')
MQRCCF_NET_PRIORITY_WRONG_TYPE
Explanation: Network priority parameter not allowed
The NetworkPriority parameter is allowed for sender
and server channels only.
4090 (X'0FFA') MQRCCF_CHANNEL_CLOSED

Explanation: Channel closed.
The channel was closed prematurely. This can occur
because a user stopped the channel while it was
running, or a channel exit decided to close the channel.
Programmer Response: Determine the reason that the
channel was closed prematurely. Restart the channel if
required.
4092 (X'0FFC')
MQRCCF_SSL_CIPHER_SPEC_ERROR
Explanation: SSL cipher specification not valid.
The SSLCipherSpec specified is not valid.
Programmer Response: Specify a valid cipher
specification.
4093 (X'0FFD') MQRCCF_SSL_PEER_NAME_ERROR

Explanation: SSL peer name not valid.
The SSLPeerName specified is not valid.
Programmer Response: Specify a valid peer name.

PCF reason codes
Reason code cross reference

The following is a list of reason codes, in alphabetic order, cross referenced to the
full description in numeric order.
3091 (X'0C13') MQRCCF_ACTION_VALUE_ERROR
3166 (X'0C5E') MQRCCF_ALLOC_FAST_TIMER_ERROR
3164 (X'0C5C') MQRCCF_ALLOC_RETRY_ERROR
3165 (X'0C5D') MQRCCF_ALLOC_SLOW_TIMER_ERROR
4009 (X'0FA9') MQRCCF_ALLOCATE_FAILED
3157 (X'0C55') MQRCCF_ALREADY_JOINED
4005 (X'0FA5') MQRCCF_ATTR_VALUE_ERROR
3213 (X'0C8D') MQRCCF_ATTR_VALUE_FIXED
3171 (X'0C63') MQRCCF_AUTH_VALUE_ERROR
3172 (X'0C64') MQRCCF_AUTH_VALUE_MISSING
4086 (X'0FF6') MQRCCF_BATCH_INT_ERROR
4087 (X'0FF7') MQRCCF_BATCH_INT_WRONG_TYPE
3037 (X'0BDD') MQRCCF_BATCH_SIZE_ERROR
4024 (X'0FB8') MQRCCF_BIND_FAILED
3094 (X'0C16') MQRCCF_BROKER_COMMAND_FAILED
3070 (X'0BFE') MQRCCF_BROKER_DELETED
3049 (X'0BE9') MQRCCF_CCSID_ERROR
4068 (X'0FE4') MQRCCF_CELL_DIR_NOT_AVAILABLE
3236 (X'0CA4') MQRCCF_CF_STRUC_ERROR
3266 (X'0CC2') MQRCCF_CFBF_FILTER_VAL_LEN_ERR
3264 (X'0CC0') MQRCCF_CFBF_LENGTH_ERROR
3267 (X'0CC3') MQRCCF_CFBF_OPERATOR_ERROR
3265 (X'0CC1') MQRCCF_CFBF_PARM_ID_ERROR
3254 (X'0CB6') MQRCCF_CFBS_DUPLICATE_PARM
3255 (X'0CB7') MQRCCF_CFBS_LENGTH_ERROR
3256 (X'0CB8') MQRCCF_CFBS_PARM_ID_ERROR
3257 (X'0CB9') MQRCCF_CFBS_STRING_LENGTH_ERR
3258 (X'0CBA') MQRCCF_CFGR_LENGTH_ERROR
3259 (X'0CBB') MQRCCF_CFGR_PARM_COUNT_ERROR
3240 (X'0CA8') MQRCCF_CFGR_PARM_ID_ERROR
3007 (X'0BBF') MQRCCF_CFH_COMMAND_ERROR
3005 (X'0BBD') MQRCCF_CFH_CONTROL_ERROR
3002 (X'0BBA') MQRCCF_CFH_LENGTH_ERROR
3004 (X'0BBC') MQRCCF_CFH_MSG_SEQ_NUMBER_ERR
3006 (X'0BBE') MQRCCF_CFH_PARM_COUNT_ERROR
3001 (X'0BB9') MQRCCF_CFH_TYPE_ERROR
3003 (X'0BBB') MQRCCF_CFH_VERSION_ERROR
3241 (X'0CA9') MQRCCF_CFIF_LENGTH_ERROR
3242 (X'0CAA') MQRCCF_CFIF_OPERATOR_ERROR
3243 (X'0CAB') MQRCCF_CFIF_PARM_ID_ERROR
3027 (X'0BD3') MQRCCF_CFIL_COUNT_ERROR
3026 (X'0BD2') MQRCCF_CFIL_DUPLICATE_VALUE
3028 (X'0BD4') MQRCCF_CFIL_LENGTH_ERROR
3047 (X'0BE7') MQRCCF_CFIL_PARM_ID_ERROR
3017 (X'0BC9') MQRCCF_CFIN_DUPLICATE_PARM
3009 (X'0BC1') MQRCCF_CFIN_LENGTH_ERROR
3014 (X'0BC6') MQRCCF_CFIN_PARM_ID_ERROR
3244 (X'0CAC') MQRCCF_CFSF_FILTER_VAL_LEN_ERR
3245 (X'0CAD') MQRCCF_CFSF_LENGTH_ERROR
3246 (X'0CAE') MQRCCF_CFSF_OPERATOR_ERROR
3247 (X'0CAF') MQRCCF_CFSF_PARM_ID_ERROR
3068 (X'0BFC') MQRCCF_CFSL_COUNT_ERROR

PCF reason codes
3066 (X'0BFA') MQRCCF_CFSL_DUPLICATE_PARM

3024 (X'0BD0') MQRCCF_CFSL_LENGTH_ERROR
3033 (X'0BD9') MQRCCF_CFSL_PARM_ID_ERROR
3069 (X'0BFD') MQRCCF_CFSL_STRING_LENGTH_ERR
3067 (X'0BFB') MQRCCF_CFSL_TOTAL_LENGTH_ERROR
3095 (X'0C17') MQRCCF_CFST_CONFLICTING_PARM
3018 (X'0BCA') MQRCCF_CFST_DUPLICATE_PARM
3010 (X'0BC2') MQRCCF_CFST_LENGTH_ERROR
3015 (X'0BC7') MQRCCF_CFST_PARM_ID_ERROR
3011 (X'0BC3') MQRCCF_CFST_STRING_LENGTH_ERR
4079 (X'0FEF') MQRCCF_CHAD_ERROR
4081 (X'0FF1') MQRCCF_CHAD_EVENT_ERROR
4082 (X'0FF2') MQRCCF_CHAD_EVENT_WRONG_TYPE
4083 (X'0FF3') MQRCCF_CHAD_EXIT_ERROR
4084 (X'0FF4') MQRCCF_CHAD_EXIT_WRONG_TYPE
4080 (X'0FF0') MQRCCF_CHAD_WRONG_TYPE
4042 (X'0FCA') MQRCCF_CHANNEL_ALREADY_EXISTS
4090 (X'0FFA') MQRCCF_CHANNEL_CLOSED
4038 (X'0FC6') MQRCCF_CHANNEL_DISABLED
3235 (X'0CA3') MQRCCF_CHANNEL_ERROR
4031 (X'0FBF') MQRCCF_CHANNEL_IN_USE
4025 (X'0FB9') MQRCCF_CHANNEL_INDOUBT
3218 (X'0C93') MQRCCF_CHANNEL_INITIATOR_ERROR
4044 (X'0FCC') MQRCCF_CHANNEL_NAME_ERROR
4064 (X'0FE0') MQRCCF_CHANNEL_NOT_ACTIVE
4032 (X'0FC0') MQRCCF_CHANNEL_NOT_FOUND
3062 (X'0BF6') MQRCCF_CHANNEL_TABLE_ERROR
3034 (X'0BDA') MQRCCF_CHANNEL_TYPE_ERROR
3064 (X'0BF8') MQRCCF_CHL_INST_TYPE_ERROR
3065 (X'0BF9') MQRCCF_CHL_STATUS_NOT_FOUND
3168 (X'0C60') MQRCCF_CHL_SYSTEM_NOT_ACTIVE
3088 (X'0C10') MQRCCF_CLUSTER_NAME_CONFLICT
3090 (X'0C12') MQRCCF_CLUSTER_Q_USAGE_ERROR
3008 (X'0BC0') MQRCCF_COMMAND_FAILED
3204 (X'0C84') MQRCCF_COMMAND_INHIBITED
3230 (X'0C9E') MQRCCF_COMMAND_LENGTH_ERROR
3222 (X'0C96') MQRCCF_COMMAND_LEVEL_CONFLICT
3231 (X'0C9F') MQRCCF_COMMAND_ORIGIN_ERROR
3226 (X'0C9A') MQRCCF_COMMAND_REPLY_ERROR
3225 (X'0C99') MQRCCF_COMMAND_SCOPE_ERROR
4040 (X'0FC8') MQRCCF_COMMIT_FAILED
3092 (X'0C14') MQRCCF_COMMS_LIBRARY_ERROR
4011 (X'0FAB') MQRCCF_CONFIGURATION_ERROR
4062 (X'0FDE') MQRCCF_CONN_NAME_ERROR
3260 (X'0CBC') MQRCCF_CONN_NOT_STOPPED
4017 (X'0FB1') MQRCCF_CONNECTION_CLOSED
3174 (X'0C66') MQRCCF_CONNECTION_ID_ERROR
4012 (X'0FAC') MQRCCF_CONNECTION_REFUSED
3080 (X'0C08') MQRCCF_CORREL_ID_ERROR
3052 (X'0BEC') MQRCCF_DATA_CONV_VALUE_ERROR
4043 (X'0FCB') MQRCCF_DATA_TOO_LARGE
3087 (X'0C0F') MQRCCF_DEL_OPTIONS_ERROR
3038 (X'0BDE') MQRCCF_DISC_INT_ERROR
4054 (X'0FD6') MQRCCF_DISC_INT_WRONG_TYPE
3163 (X'0C5B') MQRCCF_DISC_RETRY_ERROR
3211 (X'0C8B') MQRCCF_DISPOSITION_CONFLICT

PCF reason codes
3078 (X'0C06') MQRCCF_DUPLICATE_IDENTITY

3152 (X'0C50') MQRCCF_DUPLICATE_SUBSCRIPTION
4067 (X'0FE3') MQRCCF_DYNAMIC_Q_SCOPE_ERROR
3050 (X'0BEA') MQRCCF_ENCODING_ERROR
3169 (X'0C61') MQRCCF_ENTITY_NAME_MISSING
4013 (X'0FAD') MQRCCF_ENTRY_ERROR
3054 (X'0BEE') MQRCCF_ESCAPE_TYPE_ERROR
3224 (X'0C98') MQRCCF_EVENTS_DISABLED
3162 (X'0C5A') MQRCCF_FILE_NOT_AVAILABLE
3150 (X'0C4E') MQRCCF_FILTER_ERROR
3012 (X'0BC4') MQRCCF_FORCE_VALUE_ERROR
3227 (X'0C9B') MQRCCF_FUNCTION_RESTRICTED
4077 (X'0FED') MQRCCF_HB_INTERVAL_ERROR
4078 (X'0FEE') MQRCCF_HB_INTERVAL_WRONG_TYPE
4010 (X'0FAA') MQRCCF_HOST_NOT_AVAILABLE
3079 (X'0C07') MQRCCF_INCORRECT_Q
3075 (X'0C03') MQRCCF_INCORRECT_STREAM
3053 (X'0BED') MQRCCF_INDOUBT_VALUE_ERROR
4003 (X'0FA3') MQRCCF_LIKE_OBJECT_WRONG_TYPE
3232 (X'0CA0') MQRCCF_LISTENER_CONFLICT
4020 (X'0FB4') MQRCCF_LISTENER_NOT_STARTED
3249 (X'0CB1') MQRCCF_LISTENER_RUNNING
3233 (X'0CA1') MQRCCF_LISTENER_STARTED
3268 (X'0CC4') MQRCCF_LISTENER_STILL_ACTIVE
3234 (X'0CA2') MQRCCF_LISTENER_STOPPED
3175 (X'0C67') MQRCCF_LOG_TYPE_ERROR
3041 (X'0BE1') MQRCCF_LONG_RETRY_ERROR
4057 (X'0FD9') MQRCCF_LONG_RETRY_WRONG_TYPE
3042 (X'0BE2') MQRCCF_LONG_TIMER_ERROR
4058 (X'0FDA') MQRCCF_LONG_TIMER_WRONG_TYPE
3250 (X'0CB2') MQRCCF_LSTR_STATUS_NOT_FOUND
3044 (X'0BE4') MQRCCF_MAX_MSG_LENGTH_ERROR
4047 (X'0FCF') MQRCCF_MCA_NAME_ERROR
4053 (X'0FD5') MQRCCF_MCA_NAME_WRONG_TYPE
3063 (X'0BF7') MQRCCF_MCA_TYPE_ERROR
3023 (X'0BCF') MQRCCF_MD_FORMAT_ERROR
4061 (X'0FDD') MQRCCF_MISSING_CONN_NAME
3029 (X'0BD5') MQRCCF_MODE_VALUE_ERROR
4026 (X'0FBA') MQRCCF_MQCONN_FAILED
4028 (X'0FBC') MQRCCF_MQGET_FAILED
4036 (X'0FC4') MQRCCF_MQINQ_FAILED
4027 (X'0FBB') MQRCCF_MQOPEN_FAILED
4029 (X'0FBD') MQRCCF_MQPUT_FAILED
4063 (X'0FDF') MQRCCF_MQSET_FAILED
4069 (X'0FE5') MQRCCF_MR_COUNT_ERROR
4070 (X'0FE6') MQRCCF_MR_COUNT_WRONG_TYPE
4071 (X'0FE7') MQRCCF_MR_EXIT_NAME_ERROR
4072 (X'0FE8') MQRCCF_MR_EXIT_NAME_WRONG_TYPE
4073 (X'0FE9') MQRCCF_MR_INTERVAL_ERROR
4074 (X'0FEA') MQRCCF_MR_INTERVAL_WRONG_TYPE
4050 (X'0FD2') MQRCCF_MSG_EXIT_NAME_ERROR
3016 (X'0BC8') MQRCCF_MSG_LENGTH_ERROR
3030 (X'0BD6') MQRCCF_MSG_SEQ_NUMBER_ERROR
3048 (X'0BE8') MQRCCF_MSG_TRUNCATED
3215 (X'0C8F') MQRCCF_NAMELIST_ERROR
4088 (X'0FF8') MQRCCF_NET_PRIORITY_ERROR

PCF reason codes
4089 (X'0FF9') MQRCCF_NET_PRIORITY_WRONG_TYPE

3093 (X'0C15') MQRCCF_NETBIOS_NAME_ERROR
3217 (X'0C91') MQRCCF_NO_CHANNEL_INITIATOR
4019 (X'0FB3') MQRCCF_NO_COMMS_MANAGER
3077 (X'0C05') MQRCCF_NO_RETAINED_MSG
3262 (X'0CBE') MQRCCF_NO_START_CMD
3263 (X'0CBF') MQRCCF_NO_STOP_CMD
4018 (X'0FB2') MQRCCF_NO_STORAGE
3239 (X'0CA7') MQRCCF_NO_XCF_PARTNER
3200 (X'0C80') MQRCCF_NONE_FOUND
3081 (X'0C09') MQRCCF_NOT_AUTHORIZED
3073 (X'0C01') MQRCCF_NOT_REGISTERED
4037 (X'0FC5') MQRCCF_NOT_XMIT_Q
4075 (X'0FEB') MQRCCF_NPM_SPEED_ERROR
4076 (X'0FEC') MQRCCF_NPM_SPEED_WRONG_TYPE
4001 (X'0FA1') MQRCCF_OBJECT_ALREADY_EXISTS
3205 (X'0C85') MQRCCF_OBJECT_BEING_DELETED
3160 (X'0C58') MQRCCF_OBJECT_IN_USE
3209 (X'0C89') MQRCCF_OBJECT_LIMIT_EXCEEDED
4008 (X'0FA8') MQRCCF_OBJECT_NAME_ERROR
3208 (X'0C88') MQRCCF_OBJECT_NAME_RESTRICTED
4004 (X'0FA4') MQRCCF_OBJECT_OPEN
3210 (X'0C8A') MQRCCF_OBJECT_OPEN_FORCE
3173 (X'0C65') MQRCCF_OBJECT_TYPE_MISSING
4002 (X'0FA2') MQRCCF_OBJECT_WRONG_TYPE
3203 (X'0C83') MQRCCF_PARM_CONFLICT
3020 (X'0BCC') MQRCCF_PARM_COUNT_TOO_BIG
3019 (X'0BCB') MQRCCF_PARM_COUNT_TOO_SMALL
3228 (X'0C9C') MQRCCF_PARM_MISSING
3035 (X'0BDB') MQRCCF_PARM_SEQUENCE_ERROR
3097 (X'0C19') MQRCCF_PARM_SYNTAX_ERROR
3229 (X'0C9D') MQRCCF_PARM_VALUE_ERROR
3096 (X'0C18') MQRCCF_PATH_NOT_VALID
3032 (X'0BD8') MQRCCF_PING_DATA_COMPARE_ERROR
3031 (X'0BD7') MQRCCF_PING_DATA_COUNT_ERROR
4030 (X'0FBE') MQRCCF_PING_ERROR
3167 (X'0C5F') MQRCCF_PORT_NUMBER_ERROR
3170 (X'0C62') MQRCCF_PROFILE_NAME_ERROR
3177 (X'0C69') MQRCCF_PROGRAM_AUTH_FAILED
3176 (X'0C68') MQRCCF_PROGRAM_NOT_AVAILABLE
3084 (X'0C0C') MQRCCF_PUB_OPTIONS_ERROR
3046 (X'0BE6') MQRCCF_PURGE_VALUE_ERROR
3045 (X'0BE5') MQRCCF_PUT_AUTH_ERROR
4059 (X'0FDB') MQRCCF_PUT_AUTH_WRONG_TYPE
3098 (X'0C1A') MQRCCF_PWD_LENGTH_ERROR
3021 (X'0BCD') MQRCCF_Q_ALREADY_IN_CELL
3223 (X'0C97') MQRCCF_Q_ATTR_CONFLICT
3086 (X'0C0E') MQRCCF_Q_MGR_CCSID_ERROR
3074 (X'0C02') MQRCCF_Q_MGR_NAME_ERROR
3212 (X'0C8C') MQRCCF_Q_MGR_NOT_IN_QSG
3076 (X'0C04') MQRCCF_Q_NAME_ERROR
3022 (X'0BCE') MQRCCF_Q_TYPE_ERROR
4007 (X'0FA7') MQRCCF_Q_WRONG_TYPE
3029 (X'0BD5') MQRCCF_QUIESCE_VALUE_ERROR
4051 (X'0FD3') MQRCCF_RCV_EXIT_NAME_ERROR
4016 (X'0FB0') MQRCCF_RECEIVE_FAILED

PCF reason codes
4015 (X'0FAF') MQRCCF_RECEIVED_DATA_ERROR

3083 (X'0C0B') MQRCCF_REG_OPTIONS_ERROR
4035 (X'0FC3') MQRCCF_REMOTE_QM_TERMINATING
4034 (X'0FC2') MQRCCF_REMOTE_QM_UNAVAILABLE
3025 (X'0BD1') MQRCCF_REPLACE_VALUE_ERROR
3089 (X'0C11') MQRCCF_REPOS_NAME_CONFLICT
4095 (X'0FFF') MQRCCF_RETAINED_NOT_SUPPORTED
4049 (X'0FD1') MQRCCF_SEC_EXIT_NAME_ERROR
3202 (X'0C82') MQRCCF_SECURITY_REFRESH_FAILED
3201 (X'0C81') MQRCCF_SECURITY_SWITCH_OFF
4048 (X'0FD0') MQRCCF_SEND_EXIT_NAME_ERROR
4014 (X'0FAE') MQRCCF_SEND_FAILED
3043 (X'0BE3') MQRCCF_SEQ_NUMBER_WRAP_ERROR
3252 (X'0CB4') MQRCCF_SERV_STATUS_NOT_FOUND
3261 (X'0CBD') MQRCCF_SERVICE_REQUEST_PENDING
3251 (X'0CB3') MQRCCF_SERVICE_RUNNING
3253 (X'0CB5') MQRCCF_SERVICE_STOPPED
3039 (X'0BDF') MQRCCF_SHORT_RETRY_ERROR
4055 (X'0FD7') MQRCCF_SHORT_RETRY_WRONG_TYPE
3040 (X'0BE0') MQRCCF_SHORT_TIMER_ERROR
4056 (X'0FD8') MQRCCF_SHORT_TIMER_WRONG_TYPE
4092 (X'0FFC') MQRCCF_SSL_CIPHER_SPEC_ERROR
4094 (X'0FFE') MQRCCF_SSL_CLIENT_AUTH_ERROR
4093 (X'0FFD') MQRCCF_SSL_PEER_NAME_ERROR
3207 (X'0C87') MQRCCF_STORAGE_CLASS_IN_USE
3071 (X'0BFF') MQRCCF_STREAM_ERROR
3013 (X'0BC5') MQRCCF_STRUCTURE_TYPE_ERROR
3154 (X'0C52') MQRCCF_SUB_IDENTITY_ERROR
3153 (X'0C51') MQRCCF_SUB_NAME_ERROR
3155 (X'0C53') MQRCCF_SUBSCRIPTION_IN_USE
3156 (X'0C54') MQRCCF_SUBSCRIPTION_LOCKED
4085 (X'0FF5') MQRCCF_SUPPRESSED_BY_EXIT
4065 (X'0FE1') MQRCCF_TERMINATED_BY_SEC_EXIT
3248 (X'0CB0') MQRCCF_TOO_MANY_FILTERS
3072 (X'0C00') MQRCCF_TOPIC_ERROR
3238 (X'0CA6') MQRCCF_UNEXPECTED_ERROR
3085 (X'0C0D') MQRCCF_UNKNOWN_BROKER
3161 (X'0C59') MQRCCF_UNKNOWN_FILE_NAME
4006 (X'0FA6') MQRCCF_UNKNOWN_Q_MGR
4033 (X'0FC1') MQRCCF_UNKNOWN_REMOTE_CHANNEL
3082 (X'0C0A') MQRCCF_UNKNOWN_STREAM
3237 (X'0CA5') MQRCCF_UNKNOWN_USER_ID
4039 (X'0FC7') MQRCCF_USER_EXIT_NOT_AVAILABLE
4041 (X'0FC9') MQRCCF_WRONG_CHANNEL_TYPE
3151 (X'0C4F') MQRCCF_WRONG_USER
3036 (X'0BDC') MQRCCF_XMIT_PROTOCOL_TYPE_ERR
4045 (X'0FCD') MQRCCF_XMIT_Q_NAME_ERROR
4052 (X'0FD4') MQRCCF_XMIT_Q_NAME_WRONG_TYPE

Chapter 10. Secure Sockets Layer (SSL) return codes
The table in this appendix documents the return codes, in decimal form, from the
Secure Sockets Layer (SSL) that can be returned in messages from the distributed
queuing component.
If the return code is not listed, or if you want more information, refer to
Cryptographic Services SSL Programming
Table 1. SSL return codes
Return code Explanation
(decimal)
1 Handle is not valid.
3 An internal error has occured.
4 Insufficient storage is available
5 Handle is in the incorrect state.
6 Key label is not found.
7 No certificates available.
8 Certificate validation error.
9 Cryptographic processing error.
10 ASN processing error.
11 LDAP processing error.
12 An unexpected error has occurred.
102 Error detected while reading key database or SAF key ring.
103 Incorrect key database record format.
106 Incorrect key database password.
109 No certification authority certificates.
201 No key database password supplied.
202 Error detected while opening the key database.
203 Unable to generate temporary key pair
204 Key database password is expired.
302 Connection is active.
401 Certificate is expired or is not valid yet.
402 No SSL cipher specifications.
403 No certificate received from partner.
405 Certificate format is not supported.
406 Error while reading or writing data.
407 Key label does not exist.
408 Key database password is not correct.
410 SSL message format is incorrect.
411 Message authentication code is incorrect.
412 SSL protocol or certificate type is not supported.

Table 1. SSL return codes (continued)
Return code Explanation
(decimal)
413 Certificate signature is incorrect.
414 Certificate is not valid.
415 SSL protocol violation.
416 Permission denied.
417 Self-signed certificate cannot be validated.
420 Socket closed by remote partner.
421 SSL V2 cipher is not valid.
422 SSL V3 cipher is not valid.
427 LDAP is not available.
428 Key entry does not contain a private key.
429 SSL V2 header is not valid.
431 Certificate is revoked.
432 Session renegotiation is not allowed.
433 Key exceeds allowable export size.
434 Certificate key is not compatible with cipher suite.
435 Certification authority is unknown.
436 Certificate revocation list cannot be processed.
437 Connection closed.
438 Internal error reported by remote partner.
439 Unknown alert received from remote partner.
501 Buffer size is not valid.
502 Socket request would block.
503 Socket read request would block.
504 Socket write request would block.
505 Record overflow.
601 Protocol is not SSL V3 or TLS V1.
602 Function identifier is not valid.
701 Attribute identifier is not valid.

Appendix. Notices
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
information in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply
that only that IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any IBM intellectual
property right may be used instead. However, it is the user’s responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this information. The furnishing of this information does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the information. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
information at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Notices
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM United Kingdom Laboratories,
Mail Point 151,
Hursley Park,
Winchester,
Hampshire,
England
SO21 2JN.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Programming License Agreement, or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM’s application programming interfaces.

Notices
Trademarks
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
AIX IMS OS/400

AS/400 iSeries SupportPac
CICS Language Environment VSE/ESA
DB2 MQSeries WebSphere
FFST OS/2 z/OS
IBM OS/390 zSeries
IBMLink
Intel is a registered trademark of Intel Corporation in the United States, other

countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
Appendix. Notices 363

Sending your comments to IBM
If you especially like or dislike anything about this book, please use one of the
methods listed below to send your comments to IBM.
Feel free to comment on what you regard as specific errors or omissions, and on
the accuracy, organization, subject matter, or completeness of this book.
Please limit your comments to the information in this book and the way in which
the information is presented.
To make comments about the functions of IBM products or systems, talk to your
IBM representative or to your IBM authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or
distribute your comments in any way it believes appropriate, without incurring
any obligation to you.
You can send your comments to IBM in any of the following ways:
v By mail, to this address:
User Technologies Department (MP095)
IBM United Kingdom Laboratories
Hursley Park
WINCHESTER,
Hampshire
SO21 2JN
United Kingdom
v By fax:
– From outside the U.K., after your international access code use
44–1962–816151
– From within the U.K., use 01962–816151
v Electronically, use the appropriate network ID:
– IBM Mail Exchange: GBIBM2Q9 at IBMMAIL
– IBMLink™: HURSLEY(IDRCF)
– Internet: idrcf@hursley.ibm.com
Whichever method you use, ensure that you include:

v The publication title and order number
v The topic to which your comment applies
v Your name and address/telephone number/fax number/network ID.


GC34-6601-00
Spine information:
WebSphere MQ WebSphere MQ Messages

Amqzao05 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amqzao05 PDF

Uploaded by

Copyright:

Available Formats

WebSphere MQ

First edition (May 2005)

Chapter 2. 4000-4999 - User interface Chapter 9. PCF reason codes . . . . 329

Chapter 4. 6000-6999 - Common

© Copyright IBM Corp. 1997, 2005 iii

References to WebSphere MQ for UNIX® systems include:

Who this book is for

How to use this book

© Copyright IBM Corp. 1997, 2005 v

© Copyright IBM Corp. 1997, 2005 vii

viii WebSphere MQ Messages

© Copyright IBM Corp. 1997, 2005 1

In some cases a message might have variables in the Explanation or Response.

The majority of messages in this numerical range come from WebSphere MQ

WebSphere MQ Explorer messages

AMQ4006 WebSphere MQ successfully sent data

© Copyright IBM Corp. 1997, 2005 3

received the data returned.

Explanation: The CLEAR command completed

be resolved later. Select No if you want to correct the

Response: You cannot issue any more MQI calls.

AMQ4048 The request received an unexpected

AMQ4050 Allocation failed. An attempt to allocate AMQ4058 Connection closed.

AMQ4066 Message truncated because it is larger

AMQ4067 Communications manager not available.

Explanation: An unmatched quotation mark has been

Response: Specify a file in the correct format.

Response: Configure your Java security environment

Response: Ensure that the Mozilla browser is correctly

AMQ4137 The default remote administration

AMQ4145 An error occurred connecting to the

or inconsistent attributes when trying create or update

AMQ4169 WebSphere MQ failed to set the object

AMQ4183 Query failed because the queue

AMQ4179 WebSphere MQ cannot process your

AMQ4181 WebSphere MQ is not responding. Do

deleted and cannot be removed from the cluster in the

Severity: 0 : Information Explanation: The queue manager’s cluster workload

AMQ4510 The request to resume membership of AMQ4519 No destinations are available.

AMQ4587 The attempt to read from URL

AMQ4589 No connection was found to application AMQ4800 Error initializing <insert_0>.

AMQ4802 Error launching the help system.

AMQ4803 Error starting the help system.

AMQ4805 Error saving the history log file.

AMQ4806 Error reading the history log.

AMQ4807 The message size specified (<insert_0>)

Other user interface messages

4200-4217 - WebSphere MQ Default Configuration

AMQ4208 Show this panel again the next time the

AMQ4212 Unable to complete this task because

AMQ4213 Unable to delete the queue manager

AMQ4214 The computer ’%1’ is not known on the

AMQ4215 Upgrade of the default configuration

AMQ4216 The WebSphere MQ services component

AMQ4217 The MQSeriesServices component does

4235-4238 - Prepare WebSphere MQ Wizard

AMQ4236 WebSphere MQ running on this

AMQ4237 WebSphere MQ running on this

AMQ4238 You are not authorized to run the

4250-4274 - ’Postcard’ messages

AMQ4253 Cannot get fully qualified TCP/IP

Response: Try to send the postcard again. If the

AMQ4273 Unable to contact the target mailbox