Reason code list

The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including:

See Reason code cross reference for a list of reason codes in alphabetic order.

0 (X'0000')
MQRC_NONE
Explanation:

The call completed normally. The completion code (CompCode) is MQCC_OK.

Completion Code:

MQCC_OK

Programmer Response:

None.

900 (X'0384')
MQRC_APPL_FIRST
Explanation:

This is the lowest value for an application-defined reason code returned by a data-conversion exit. Data-conversion exits can return reason codes in the range MQRC_APPL_FIRST through MQRC_APPL_LAST to indicate particular conditions that the exit has detected.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

As defined by the writer of the data-conversion exit.

999 (X'03E7')
MQRC_APPL_LAST
Explanation:

This is the highest value for an application-defined reason code returned by a data-conversion exit. Data-conversion exits can return reason codes in the range MQRC_APPL_FIRST through MQRC_APPL_LAST to indicate particular conditions that the exit has detected.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

As defined by the writer of the data-conversion exit.

2001 (X'07D1')
MQRC_ALIAS_BASE_Q_TYPE_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued specifying an alias queue as the destination, but the BaseQName in the alias queue definition resolves to a queue that is not a local queue, a local definition of a remote queue, or a cluster queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the queue definitions.

2002 (X'07D2')
MQRC_ALREADY_CONNECTED
Explanation:

An MQCONN or MQCONNX call was issued, but the application is already connected to the queue manager.

  • On z/OS, this reason code occurs for batch and IMS applications only; it does not occur for CICS applications.

  • On AIX, HP-UX, i5/OS, Solaris, Windows, this reason code occurs if the application attempts to create a nonshared handle when a nonshared handle already exists for the thread. A thread can have no more than one nonshared handle.

  • On Windows, MTS objects do not receive this reason code, as additional connections to the queue manager are allowed.

Completion Code:

MQCC_WARNING

Programmer Response:

None. The Hconn parameter returned has the same value as was returned for the previous MQCONN or MQCONNX call.

An MQCONN or MQCONNX call that returns this reason code does not mean that an additional MQDISC call must be issued in order to disconnect from the queue manager. If this reason code is returned because the application has been called in a situation where the connect has already been done, a corresponding MQDISC should not be issued, because this will cause the application that issued the original MQCONN or MQCONNX call to be disconnected as well.

2003 (X'07D3')
MQRC_BACKED_OUT
Explanation:

The current unit of work encountered a fatal error or was backed out. This occurs in the following cases:

  • On an MQCMIT or MQDISC call, when the commit operation has failed and the unit of work has been backed out. All resources that participated in the unit of work have been returned to their state at the start of the unit of work. The MQCMIT or MQDISC call completes with MQCC_WARNING in this case.

    • On z/OS, this reason code occurs only for batch applications.

  • On an MQGET, MQPUT, or MQPUT1 call that is operating within a unit of work, when the unit of work has already encountered an error that prevents the unit of work being committed (for example, when the log space is exhausted). The application must issue the appropriate call to back out the unit of work. (For a unit of work coordinated by the queue manager, this call is the MQBACK call, although the MQCMIT call has the same effect in these circumstances.) The MQGET, MQPUT, or MQPUT1 call completes with MQCC_FAILED in this case.

    • On z/OS, this case does not occur.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed.

2004 (X'07D4')
MQRC_BUFFER_ERROR
Explanation:

The Buffer parameter is not valid for one of the following reasons:

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The parameter pointer points to storage that cannot be accessed for the entire length specified by BufferLength.

  • For calls where Buffer is an output parameter: the parameter pointer points to read-only storage.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2005 (X'07D5')
MQRC_BUFFER_LENGTH_ERROR
Explanation:

The BufferLength parameter is not valid, or the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

This reason can also be returned to an MQ client program on the MQCONN or MQCONNX call if the negotiated maximum message size for the channel is smaller than the fixed part of any call structure.

This reason should also be returned by the MQZ_ENUMERATE_AUTHORITY_DATA installable service component when the AuthorityBuffer parameter is too small to accommodate the data to be returned to the invoker of the service component.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value that is zero or greater. For the mqAddString and mqSetString calls, the special value MQBL_NULL_TERMINATED is also valid.

2006 (X'07D6')
MQRC_CHAR_ATTR_LENGTH_ERROR
Explanation:

CharAttrLength is negative (for MQINQ or MQSET calls), or is not large enough to hold all selected attributes (MQSET calls only). 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 detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value large enough to hold the concatenated strings for all selected attributes.

2007 (X'07D7')
MQRC_CHAR_ATTRS_ERROR
Explanation:

CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2008 (X'07D8')
MQRC_CHAR_ATTRS_TOO_SHORT
Explanation:

For MQINQ calls, CharAttrLength is not large enough to contain all of the character attributes for which MQCA_* selectors are specified in the Selectors parameter.

The call still completes, with the CharAttrs parameter string filled in with as many character attributes as there is room for. Only complete attribute strings are returned: if there is insufficient space remaining to accommodate an attribute in its entirety, that attribute and subsequent character attributes are omitted. Any space at the end of the string not used to hold an attribute is unchanged.

An attribute that represents a set of values (for example, the namelist Names attribute) is treated as a single entity--either all of its values are returned, or none.

Completion Code:

MQCC_WARNING

Programmer Response:

Specify a large enough value, unless only a subset of the values is needed.

2009 (X'07D9')
MQRC_CONNECTION_BROKEN
Explanation:

Connection to the queue manager has been lost. This can occur because the queue manager has ended. If the call is an MQGET call with the MQGMO_WAIT option, the wait has been canceled. All connection and object handles are now invalid.

For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED.

Completion Code:

MQCC_FAILED

Programmer Response:

Applications can attempt to reconnect to the queue manager by issuing the MQCONN or MQCONNX call. It may be necessary to poll until a successful response is received.

  • On z/OS for CICS applications, it is not necessary to issue the MQCONN or MQCONNX call, because CICS applications are connected automatically.

Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.

2010 (X'07DA')
MQRC_DATA_LENGTH_ERROR
Explanation:

The DataLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

This reason can also be returned to an MQ client program on the MQGET, MQPUT, or MQPUT1 call, if the BufferLength parameter exceeds the maximum message size that was negotiated for the client channel.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

If the error occurs for an MQ client program, also check that the maximum message size for the channel is big enough to accommodate the message being sent; if it is not big enough, increase the maximum message size for the channel.

2011 (X'07DB')
MQRC_DYNAMIC_Q_NAME_ERROR
Explanation:

On the MQOPEN call, a model queue is specified in the ObjectName field of the ObjDesc parameter, but the DynamicQName field is not valid, for one of the following reasons:

  • DynamicQName is completely blank (or blank up to the first null character in the field).

  • Characters are present that are not valid for a queue name.

  • An asterisk is present beyond the 33rd position (and before any null character).

  • An asterisk is present followed by characters that are not null and not blank.

This reason code can also sometimes occur when a server application opens the reply queue specified by the ReplyToQ and ReplyToQMgr fields in the MQMD of a message that the server has just received. In this case the reason code indicates that the application that sent the original message placed incorrect values into the ReplyToQ and ReplyToQMgr fields in the MQMD of the original message.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid name.

2012 (X'07DC')
MQRC_ENVIRONMENT_ERROR
Explanation:

The call is not valid for the current environment.

  • On z/OS, one of the following applies:

    • An MQCONN or MQCONNX call was issued, but the application has been linked with an adapter that is not supported in the environment in which the application is running. For example, this can arise when the application is linked with the MQ RRS adapter, but the application is running in a DB2 Stored Procedure address space. RRS is not supported in this environment. Stored Procedures wishing to use the MQ RRS adapter must run in a DB2 WLM-managed Stored Procedure address space.

    • An MQCMIT or MQBACK call was issued, but the application has been linked with the RRS batch adapter CSQBRSTB. This adapter does not support the MQCMIT and MQBACK calls.

    • An MQCMIT or MQBACK call was issued in the CICS or IMS environment.

    • The RRS subsystem is not up and running on the z/OS system that ran the application.

  • On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, UNIX systems, and Windows, one of the following applies:

    • The application is linked to the wrong libraries (threaded or nonthreaded).

    • An MQBEGIN, MQCMIT, or MQBACK call was issued, but an external unit-of-work manager is in use. For example, this reason code occurs on Windows when an MTS object is running as a DTC transaction. This reason code also occurs if the queue manager does not support units of work.

    • The MQBEGIN call was issued in an MQ client environment.

    • An MQXCLWLN call was issued, but the call did not originate from a cluster workload exit.

Completion Code:

MQCC_FAILED

Programmer Response:

Do one of the following (as appropriate):

  • On z/OS:

    • Link the application with the correct adapter.

    • Modify the application to use the SRRCMIT and SRRBACK calls in place of the MQCMIT and MQBACK calls. Alternatively, link the application with the RRS batch adapter CSQBRRSI. This adapter supports MQCMIT and MQBACK in addition to SRRCMIT and SRRBACK.

    • For a CICS or IMS application, issue the appropriate CICS or IMS call to commit or backout the unit of work.

    • Start the RRS subsystem on the z/OS system that is running the application.

  • In the other environments:

    • Link the application with the correct libraries (threaded or nonthreaded).

    • Remove from the application the call that is not supported.

2013 (X'07DD')
MQRC_EXPIRY_ERROR
Explanation:

On an MQPUT or MQPUT1 call, the value specified for the Expiry field in the message descriptor MQMD is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value that is greater than zero, or the special value MQEI_UNLIMITED.

2014 (X'07DE')
MQRC_FEEDBACK_ERROR
Explanation:

On an MQPUT or MQPUT1 call, the value specified for the Feedback field in the message descriptor MQMD is not valid. The value is not MQFB_NONE, and is outside both the range defined for system feedback codes and the range defined for application feedback codes.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQFB_NONE, or a value in the range MQFB_SYSTEM_FIRST through MQFB_SYSTEM_LAST, or MQFB_APPL_FIRST through MQFB_APPL_LAST.

2016 (X'07E0')
MQRC_GET_INHIBITED
Explanation:

MQGET calls are currently inhibited for the queue, or for the queue to which this queue resolves.

Completion Code:

MQCC_FAILED

Programmer Response:

If the system design allows get requests to be inhibited for short periods, retry the operation later.

2017 (X'07E1')
MQRC_HANDLE_NOT_AVAILABLE
Explanation:

An MQOPEN or MQPUT1 call was issued, but the maximum number of open handles allowed for the current task has already been reached. Be aware that when a distribution list is specified on the MQOPEN or MQPUT1 call, each queue in the distribution list uses one handle.

  • On z/OS, "task" means a CICS task, a z/OS task, or an IMS-dependent region.

Completion Code:

MQCC_FAILED

Programmer Response:

Check whether the application is issuing MQOPEN calls without corresponding MQCLOSE calls. If it is, modify the application to issue the MQCLOSE call for each open object as soon as that object is no longer needed.

Also check whether the application is specifying a distribution list containing a large number of queues that are consuming all of the available handles. If it is, increase the maximum number of handles that the task can use, or reduce the size of the distribution list. The maximum number of open handles that a task can use is given by the MaxHandles queue manager attribute.

2018 (X'07E2')
MQRC_HCONN_ERROR
Explanation:

The connection handle Hconn is not valid, for one of the following reasons:

  • The parameter pointer is not valid, or (for the MQCONN or MQCONNX call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The value specified was not returned by a preceding MQCONN or MQCONNX call.

  • The value specified has been made invalid by a preceding MQDISC call.

  • The handle is a shared handle that has been made invalid by another thread issuing the MQDISC call.

  • The handle is a shared handle that is being used on the MQBEGIN call (only nonshared handles are valid on MQBEGIN).

  • The handle is a nonshared handle that is being used a thread that did not create the handle.

  • 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; note that passing the handle between library packages is supported).

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that a successful MQCONN or MQCONNX call is performed for the queue manager, and that an MQDISC call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQCONN in the WebSphere MQ Application Programming Guide).

  • On z/OS, also check that the application has been linked with the correct stub; this is CSQCSTUB for CICS applications, CSQBSTUB for batch applications, and CSQQSTUB for IMS applications. Also, the stub used must not belong to a release of the queue manager that is more recent than the release on which the application will run.

2019 (X'07E3')
MQRC_HOBJ_ERROR
Explanation:

The object handle Hobj is not valid, for one of the following reasons:

  • The parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The value specified was not returned by a preceding MQOPEN call.

  • The value specified has been made invalid by a preceding MQCLOSE call.

  • The handle is a shared handle that has been made invalid by another thread issuing the MQCLOSE call.

  • The handle is a nonshared handle that is being used by a thread that did not create the handle.

  • The call is MQGET or MQPUT, but the object represented by the handle is not a queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that a successful MQOPEN call is performed for this object, and that an MQCLOSE call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQOPEN in the WebSphere MQ Application Programming Guide).

2020 (X'07E4')
MQRC_INHIBIT_VALUE_ERROR
Explanation:

On an MQSET call, the value specified for either the MQIA_INHIBIT_GET attribute or the MQIA_INHIBIT_PUT attribute is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value for the InhibitGet or InhibitPut queu attribute.

2021 (X'07E5')
MQRC_INT_ATTR_COUNT_ERROR
Explanation:

On an MQINQ or MQSET call, the IntAttrCount parameter is negative (MQINQ or MQSET), or smaller than the number of integer attribute selectors (MQIA_*) specified in the Selectors parameter (MQSET only). 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 detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value large enough for all selected integer attributes.

2022 (X'07E6')
MQRC_INT_ATTR_COUNT_TOO_SMALL
Explanation:

On an MQINQ call, the IntAttrCount parameter is smaller than the number of integer attribute selectors (MQIA_*) specified in the Selectors parameter.

The call completes with MQCC_WARNING, with the IntAttrs array filled in with as many integer attributes as there is room for.

Completion Code:

MQCC_WARNING

Programmer Response:

Specify a large enough value, unless only a subset of the values is needed.

2023 (X'07E7')
MQRC_INT_ATTRS_ARRAY_ERROR
Explanation:

On an MQINQ or MQSET call, the IntAttrs parameter is not valid. The parameter pointer is not valid (MQINQ and MQSET), or points to read-only storage or to storage that is not as long as indicated by the IntAttrCount parameter (MQINQ only). (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2024 (X'07E8')
MQRC_SYNCPOINT_LIMIT_REACHED
Explanation:

An MQGET, MQPUT, or MQPUT1 call 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 MaxUncommittedMsgs queue-manager attribute). The number of uncommitted messages is the sum of the following since the start of the current unit of work:

  • Messages put by the application with the MQPMO_SYNCPOINT option

  • Messages retrieved by the application with the MQGMO_SYNCPOINT option

  • Trigger messages and COA report messages generated by the queue manager for messages put with the MQPMO_SYNCPOINT option

  • COD report messages generated by the queue manager for messages retrieved with the MQGMO_SYNCPOINT option

  • On Compaq NonStop Kernel, this reason code occurs when the maximum number of I/O operations in a single TM/MP transaction has been exceeded.

Completion Code:

MQCC_FAILED

Programmer Response:

Check whether the application is looping. If it is not, consider reducing the complexity of the application. Alternatively, increase the queue-manager limit for the maximum number of uncommitted messages within a unit of work.

  • On z/OS, the limit for the maximum number of uncommitted messages can be changed by using the ALTER QMGR command.

  • On i5/OS, the limit for the maximum number of uncommitted messages can be changed by using the CHGMQM command.

  • On Compaq NonStop Kernel, the application should cancel the transaction and retry with a smaller number of operations in the unit of work. See the MQSeries for Tandem NonStop Kernel System Management Guide for more details.

2025 (X'07E9')
MQRC_MAX_CONNS_LIMIT_REACHED
Explanation:

The MQCONN or MQCONNX call was rejected because the maximum number of concurrent connections has been exceeded.

  • On z/OS, connection limits are applicable only to TSO and batch requests. The limits are determined by the customer using the following parameters of the CSQ6SYSP macro:

    • For TSO: IDFORE

    • For batch: IDBACK

    For more information, see the WebSphere MQ for z/OS System Setup Guide.

  • On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, UNIX systems, and Windows, this reason code can also occur on the MQOPEN call.

  • When using Java applications, a limit to the number of concurrent connections may be defined by the connection manager.

Completion Code:

MQCC_FAILED

Programmer Response:

Either increase the size of the appropriate parameter value, or reduce the number of concurrent connections.

2026 (X'07EA')
MQRC_MD_ERROR
Explanation:

The MQMD structure is not valid, for one of the following reasons:

  • The StrucId field is not MQMD_STRUC_ID.

  • The Vfield specifies a value that is not valid or not supported.

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQMD structure are set correctly.

2027 (X'07EB')
MQRC_MISSING_REPLY_TO_Q
Explanation:

On an MQPUT or MQPUT1 call, the ReplyToQ field in the message descriptor MQMD is blank, but one or both of the following is true:

  • A reply was requested (that is, MQMT_REQUEST was specified in the MsgType field of the message descriptor).

  • A report message was requested in the Report field of the message descriptor.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the name of the queue to which the reply message or report message is to be sent.

2029 (X'07ED')
MQRC_MSG_TYPE_ERROR
Explanation:

Either:

  • On an MQPUT or MQPUT1 call, the value specified for the MsgType field in the message descriptor (MQMD) is not valid.

  • A message processing program received a message that does not have the expected message type. For example, if the WebSphere MQ command server receives a message which is not a request message (MQMT_REQUEST) then it rejects the request with this reason code.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value for the MsgType field. In the case where a request is rejected by a message processing program, refer to the documentation for that program for details of the message types that it supports.

2030 (X'07EE')
MQRC_MSG_TOO_BIG_FOR_Q
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 MQMF_SEGMENTATION_ALLOWED was not specified in the MsgFlags field in MQMD. If segmentation is not allowed, the length of the message cannot exceed the lesser of the queue MaxMsgLength attribute and queue-manager MaxMsgLength attribute.

  • On z/OS, the queue manager does not support the segmentation of messages; if MQMF_SEGMENTATION_ALLOWED is specified, it is accepted but ignored.

This reason code can also occur when MQMF_SEGMENTATION_ALLOWED is specified, but 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:

  • For a user-defined format, the smallest segment that the queue manager can create is 16 bytes.

  • For a built-in format, the smallest segment that the queue manager can create depends on the particular format, but is greater than 16 bytes in all cases other than MQFMT_STRING (for MQFMT_STRING the minimum segment size is 16 bytes).

MQRC_MSG_TOO_BIG_FOR_Q can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Check whether the BufferLength parameter is specified correctly; if it is, do one of the following:

  • Increase the value of the queue's MaxMsgLength attribute; the queue-manager's MaxMsgLength attribute may also need increasing.

  • Break the message into several smaller messages.

  • Specify MQMF_SEGMENTATION_ALLOWED in the MsgFlags field in MQMD; this will allow the queue manager to break the message into segments.

2031 (X'07EF')
MQRC_MSG_TOO_BIG_FOR_Q_MGR
Explanation:

An MQPUT or MQPUT1 call was issued to put a message on a queue, but the message was too long for the queue manager and MQMF_SEGMENTATION_ALLOWED was not specified in the MsgFlags field in MQMD. If segmentation is not allowed, the length of the message cannot exceed the lesser of the queue-manager MaxMsgLength attribute and queue MaxMsgLength attribute.

This reason code can also occur when MQMF_SEGMENTATION_ALLOWED is specified, but the nature of the data present in the message prevents the queue manager splitting it into segments that are small enough for the queue-manager limit:

  • For a user-defined format, the smallest segment that the queue manager can create is 16 bytes.

  • For a built-in format, the smallest segment that the queue manager can create depends on the particular format, but is greater than 16 bytes in all cases other than MQFMT_STRING (for MQFMT_STRING the minimum segment size is 16 bytes).

MQRC_MSG_TOO_BIG_FOR_Q_MGR can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

This reason also occurs if a channel, through which the message is to pass, has restricted the maximum message length to a value that is actually less than that supported by the queue manager, and the message length is greater than this value.

  • On z/OS, this return code is issued only if you are using CICS for distributed queuing. Otherwise, MQRC_MSG_TOO_BIG_FOR_CHANNEL is issued.

Completion Code:

MQCC_FAILED

Programmer Response:

Check whether the BufferLength parameter is specified correctly; if it is, do one of the following:

  • Increase the value of the queue-manager's MaxMsgLength attribute; the queue's MaxMsgLength attribute may also need increasing.

  • Break the message into several smaller messages.

  • Specify MQMF_SEGMENTATION_ALLOWED in the MsgFlags field in MQMD; this will allow the queue manager to break the message into segments.

  • Check the channel definitions.

2033 (X'07F1')
MQRC_NO_MSG_AVAILABLE
Explanation:

An MQGET call was issued, but there is no message on the queue satisfying the selection criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval specified by the WaitInterval field in MQGMO has expired. This reason is also returned for an MQGET call for browse, when the end of the queue has been reached.

This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is similar to MQGET. For the mqExecute call, the completion code can be either MQCC_WARNING or MQCC_FAILED:

  • If the completion code is MQCC_WARNING, some response messages were received during the specified wait interval, but not all. The response bag contains system-generated nested bags for the messages that were received.

  • If the completion code is MQCC_FAILED, no response messages were received during the specified wait interval.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

If this is an expected condition, no corrective action is required.

If this is an unexpected condition, check that:

  • The message was put on the queue successfully.

  • The unit of work (if any) used for the MQPUT or MQPUT1 call was committed successfully.

  • The options controlling the selection criteria are specified correctly. All of the following can affect the eligibility of a message for return on the MQGET call:

    • MQGMO_LOGICAL_ORDER

    • MQGMO_ALL_MSGS_AVAILABLE

    • MQGMO_ALL_SEGMENTS_AVAILABLE

    • MQGMO_COMPLETE_MSG

    • MQMO_MATCH_MSG_ID

    • MQMO_MATCH_CORREL_ID

    • MQMO_MATCH_GROUP_ID

    • MQMO_MATCH_MSG_SEQ_NUMBER

    • MQMO_MATCH_OFFSET

    • Value of MsgId field in MQMD

    • Value of CorrelId field in MQMD

Consider waiting longer for the message.

2034 (X'07F2')
MQRC_NO_MSG_UNDER_CURSOR
Explanation:

An MQGET call was issued with either the MQGMO_MSG_UNDER_CURSOR or the MQGMO_BROWSE_MSG_UNDER_CURSOR option. However, the browse cursor is not positioned at a retrievable message. This is caused by one of the following:

  • The cursor is positioned logically before the first message (as it is before the first MQGET call with a browse option has been successfully performed).

  • The message the browse cursor was positioned on has been locked or removed from the queue (probably by some other application) since the browse operation was performed.

  • The message the browse cursor was positioned on has expired.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the application logic. This may be an expected reason if the application design allows multiple servers to compete for messages after browsing. Consider also using the MQGMO_LOCK option with the preceding browse MQGET call.

2035 (X'07F3')
MQRC_NOT_AUTHORIZED
Explanation:

The user is not authorized to perform the operation attempted:

  • On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue manager.

    • On z/OS, for CICS applications, MQRC_CONNECTION_NOT_AUTHORIZED is issued instead.

  • On an MQOPEN or MQPUT1 call, the user is not authorized to open the object for the option(s) specified.

    • On z/OS, if the object being opened is a model queue, this reason also arises if the user is not authorized to create a dynamic queue with the required name.

  • On an MQCLOSE call, the user is not authorized to delete the object, which is a permanent dynamic queue, and the Hobj parameter specified on the MQCLOSE call is not the handle returned by the MQOPEN call that created the queue.

  • On a command, the user is not authorized to issue the command, or to access the object it specifies.

This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct queue manager or object was specified, and that appropriate authority exists.

2036 (X'07F4')
MQRC_NOT_OPEN_FOR_BROWSE
Explanation:

An MQGET call was issued with one of the following options:

  • MQGMO_BROWSE_FIRST

  • MQGMO_BROWSE_NEXT

  • MQGMO_BROWSE_MSG_UNDER_CURSOR

  • MQGMO_MSG_UNDER_CURSOR

but the queue had not been opened for browse.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_BROWSE when the queue is opened.

2037 (X'07F5')
MQRC_NOT_OPEN_FOR_INPUT
Explanation:

An MQGET call was issued to retrieve a message from a queue, but the queue had not been opened for input.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify one of the following when the queue is opened:

  • MQOO_INPUT_SHARED

  • MQOO_INPUT_EXCLUSIVE

  • MQOO_INPUT_AS_Q_DEF

2038 (X'07F6')
MQRC_NOT_OPEN_FOR_INQUIRE
Explanation:

An MQINQ call was issued to inquire object attributes, but the object had not been opened for inquire.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_INQUIRE when the object is opened.

2039 (X'07F7')
MQRC_NOT_OPEN_FOR_OUTPUT
Explanation:

An MQPUT call was issued to put a message on a queue, but the queue had not been opened for output.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_OUTPUT when the queue is opened.

2040 (X'07F8')
MQRC_NOT_OPEN_FOR_SET
Explanation:

An MQSET call was issued to set queue attributes, but the queue had not been opened for set.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_SET when the object is opened.

2041 (X'07F9')
MQRC_OBJECT_CHANGED
Explanation:

Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call. See the description of MQOPEN in the WebSphere MQ Application Programming Guide for more information.

This reason does not occur if the object handle is specified in the Context field of the PutMsgOpts parameter on the MQPUT or MQPUT1 call.

Completion Code:

MQCC_FAILED

Programmer Response:

Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and retry the operation. However, if the object definitions are critical to the application logic, an MQINQ call can be used after reopening the object, to obtain the new values of the object attributes.

2042 (X'07FA')
MQRC_OBJECT_IN_USE
Explanation:

An MQOPEN call was issued, but the object in question has already been opened by this or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input; it also arises if the request is for exclusive input, but the object is already open for input (of any sort).

MCAs for receiver channels, or the intra-group queuing agent (IGQ agent), may keep the destination queues open even when messages are not being transmitted; this results in the queues appearing to be "in use". Use the MQSC command DISPLAY QSTATUS to find out who is keeping the queue open.

  • On z/OS, this reason can also occur for an MQOPEN or MQPUT1 call, if the object to be opened (which can be a queue, or for MQOPEN a namelist or process object) is in the process of being deleted.

Completion Code:

MQCC_FAILED

Programmer Response:

System design should specify whether an application is to wait and retry, or take other action.

2043 (X'07FB')
MQRC_OBJECT_TYPE_ERROR
Explanation:

On the MQOPEN or MQPUT1 call, the ObjectType field in the object descriptor MQOD specifies a value that is not valid. For the MQPUT1 call, the object type must be MQOT_Q.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid object type.

2044 (X'07FC')
MQRC_OD_ERROR
Explanation:

On the MQOPEN or MQPUT1 call, the object descriptor MQOD is not valid, for one of the following reasons:

  • The StrucId field is not MQOD_STRUC_ID.

  • The Vfield specifies a value that is not valid or not supported.

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQOD structure are set correctly.

2045 (X'07FD')
MQRC_OPTION_NOT_VALID_FOR_TYPE
Explanation:

On an MQOPEN or MQCLOSE call, an option is specified that is not valid for the type of object or queue being opened or closed.

For the MQOPEN call, this includes the following cases:

  • An option that is inappropriate for the object type (for example, MQOO_OUTPUT for an MQOT_PROCESS object).

  • An option that is unsupported for the queue type (for example, MQOO_INQUIRE for a remote queue that has no local definition).

  • One or more of the following options:

    • MQOO_INPUT_AS_Q_DEF

    • MQOO_INPUT_SHARED

    • MQOO_INPUT_EXCLUSIVE

    • MQOO_BROWSE

    • MQOO_INQUIRE

    • MQOO_SET

    when either:

    • the queue name is resolved through a cell directory, or

    • ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in order to specify a queue-manager alias), and the queue named in the RemoteQMgrName attribute of the definition is the name of the local queue manager.

For the MQCLOSE call, this includes the following case:

  • 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 MQOT_Q_MGR, but the ObjectQMgrName field in MQOD is neither blank nor the name of the local queue manager.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the correct option. For the MQOPEN call, ensure that the ObjectQMgrName field is set correctly. For the MQCLOSE call, either correct the option or change the definition type of the model queue that is used to create the new queue.

2046 (X'07FE')
MQRC_OPTIONS_ERROR
Explanation:

The Options parameter or field contains options that are not valid, or a combination of options that is not valid.

  • For the MQOPEN, MQCLOSE, MQXCNVC, mqBagToBuffer, mqBufferToBag, mqCreateBag, and mqExecute calls, Options is a separate parameter on the call.

    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 detected, unpredictable results occur.)

  • For the MQBEGIN, MQCONNX, MQGET, MQPUT, and MQPUT1 calls, Options is a field in the relevant options structure (MQBO, MQCNO, MQGMO, or MQPMO).

Completion Code:

MQCC_FAILED

Programmer Response:

Specify valid options. Check the description of the Options parameter or field to determine which options and combinations of options are valid. If multiple options are being set by adding the individual options together, ensure that the same option is not added twice.

2047 (X'07FF')
MQRC_PERSISTENCE_ERROR
Explanation:

On an MQPUT or MQPUT1 call, the value specified for the Persistence field in the message descriptor MQMD is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify one of the following values:

  • MQPER_PERSISTENT

  • MQPER_NOT_PERSISTENT

  • MQPER_PERSISTENCE_AS_Q_DEF

2048 (X'0800')
MQRC_PERSISTENT_NOT_ALLOWED
Explanation:

On an MQPUT or MQPUT1 call, the 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 placed on temporary dynamic queues.

This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQPER_NOT_PERSISTENT if the message is to be placed on a temporary dynamic queue. If persistence is required, use a permanent dynamic queue or predefined queue in place of a temporary dynamic queue.

Be aware that server applications are recommended to send reply messages (message type MQMT_REPLY) with the same persistence as the original request message (message type MQMT_REQUEST). If the request message is persistent, the reply queue specified in the ReplyToQ field in the message descriptor MQMD cannot be a temporary dynamic queue. Use a permanent dynamic queue or predefined queue as the reply queue in this situation.

2049 (X'0801')
MQRC_PRIORITY_EXCEEDS_MAXIMUM
Explanation:

An MQPUT or MQPUT1 call was issued, but the value of the Priority field in the message descriptor MQMD exceeds the maximum priority supported by the local queue manager, as shown by the MaxPriority queue-manager attribute. The message is accepted by the queue manager, but is placed on the queue at the queue manager's maximum priority. The Priority field in the message descriptor retains the value specified by the application that put the message.

Completion Code:

MQCC_WARNING

Programmer Response:

None required, unless this reason code was not expected by the application that put the message.

2050 (X'0802')
MQRC_PRIORITY_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the value of the Priority field in the message descriptor MQMD is not valid. The maximum priority supported by the queue manager is given by the MaxPriority queue-manager attribute.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value in the range zero through MaxPriority, or the special value MQPRI_PRIORITY_AS_Q_DEF.

2051 (X'0803')
MQRC_PUT_INHIBITED
Explanation:

MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves.

This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

Completion Code:

MQCC_FAILED

Programmer Response:

If the system design allows put requests to be inhibited for short periods, retry the operation later.

2052 (X'0804')
MQRC_Q_DELETED
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 MQCLOSE in the WebSphere MQ Application Programming Guide for information about the deletion of dynamic queues.)

  • On z/OS, this can also occur with the MQOPEN and MQPUT1 calls if a dynamic queue is being opened, but the queue is in a logically-deleted state. See MQCLOSE for more information about this.

Completion Code:

MQCC_FAILED

Programmer Response:

Issue an MQCLOSE call to return the handle and associated resources to the system (the MQCLOSE call will succeed in this case). Check the design of the application that caused the error.

2053 (X'0805')
MQRC_Q_FULL
Explanation:

An MQPUT or MQPUT1 call, or a command, failed because the queue is full, that is, it already contains the maximum number of messages possible, as specified by the MaxQDepth queue attribute.

This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Retry the operation later. Consider increasing the maximum depth for this queue, or arranging for more instances of the application to service the queue.

2055 (X'0807')
MQRC_Q_NOT_EMPTY
Explanation:

An MQCLOSE call was issued for a permanent dynamic queue, but the call failed because the queue is not empty or still in use. One of the following applies:

  • The MQCO_DELETE option was specified, but there are messages on the queue.

  • The MQCO_DELETE or MQCO_DELETE_PURGE option was specified, but there are uncommitted get or put calls outstanding against the queue.

See the usage notes pertaining to dynamic queues for the MQCLOSE call for more information.

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 case of delete queue without the purge option).

Completion Code:

MQCC_FAILED

Programmer Response:

Check why there might be messages on the queue. Be aware that the CurrentQDepth queue attribute might be zero even though there are one or more messages on the queue; this can happen if the messages have been retrieved as part of a unit of work that has not yet been committed. If the messages can be discarded, try using the MQCLOSE call with the MQCO_DELETE_PURGE option. Consider retrying the call later.

2056 (X'0808')
MQRC_Q_SPACE_NOT_AVAILABLE
Explanation:

An MQPUT or MQPUT1 call was issued, but there is no space available for the queue on disk or other storage device.

This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Check whether an application is putting messages in an infinite loop. If not, make more disk space available for the queue.

2057 (X'0809')
MQRC_Q_TYPE_ERROR
Explanation:

One of the following occurred:

  • On an MQOPEN call, the ObjectQMgrName field in the object descriptor MQOD or object record MQOR 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 WebSphere MQ Application Programming Guide for more information.

  • On an MQPUT1 call, the object descriptor MQOD or object record MQOR specifies the name of a model queue.

  • On a previous MQPUT or MQPUT1 call, the ReplyToQ field in the message descriptor specified the name of a model queue, but a model queue cannot be specified as the destination for reply or report messages. Only the name of a predefined queue, or the name of the dynamic queue created from the model queue, can be specified as the destination. In this situation the reason code MQRC_Q_TYPE_ERROR is returned in the Reason field of the MQDLH structure when the reply message or report message is placed on the dead-letter queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid queue.

2058 (X'080A')
MQRC_Q_MGR_NAME_ERROR
Explanation:

On an MQCONN or MQCONNX call, the value specified for the QMgrName parameter is not 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 detected, unpredictable results occur.)

  • On z/OS for CICS applications, this reason can occur on any call if the original connect specified an incorrect or unrecognized name.

This reason code can also occur if an MQ client application attempts to connect to a queue manager within an MQ-client queue-manager group (see the QMgrName parameter of MQCONN), and either:

  • Queue-manager groups are not supported.

  • There is no queue-manager group with the specified name.

Completion Code:

MQCC_FAILED

Programmer Response:

Use an all-blank name if possible, or verify that the name used is valid.

2059 (X'080B')
MQRC_Q_MGR_NOT_AVAILABLE
Explanation:

This occurs:

  1. On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName parameter is not available for connection.

    • On z/OS:

      • For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed.

      • For CICS applications, this reason can occur on any call if the original connect specified a queue manager whose name was recognized, but which is not available.

    • On i5/OS, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHC_DEF_HCONN is specified for the Hconn parameter by an application running in compatibility mode.

  2. On an MQCONN or MQCONNX call from an MQ client application:

    • Attempting to connect to a queue manager within an MQ-client queue-manager group when none of the queue managers in the group is available for connection (see the QMgrName parameter of the MQCONN call).

    • If there is an error with the client-connection or the corresponding server-connection channel definitions.

    • On z/OS, if the optional OS/390 client attachment feature has not been installed.

  3. If a command uses the CommandScope parameter specfying a queue manager that is not active in the queue-sharing group.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions.

2061 (X'080D')
MQRC_REPORT_OPTIONS_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD contains one or more options that are not recognized by the local queue manager. The options that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details.

This reason code can also occur in the Feedback field in the MQMD of a report message, or in the Reason field 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 report options specified by the sender of the message.

Completion Code:

MQCC_FAILED

Programmer Response:

Do the following:

  • Ensure that the Report field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Specify MQRO_NONE if no report options are required.

  • Ensure that the report options specified are valid; see the Report field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid report options.

  • If multiple report options are being set by adding the individual report options together, ensure that the same report option is not added twice.

  • Check that conflicting report options are not specified. For example, do not add both MQRO_EXCEPTION and MQRO_EXCEPTION_WITH_DATA to the Report field; only one of these can be specified.

2062 (X'080E')
MQRC_SECOND_MARK_NOT_ALLOWED
Explanation:

An MQGET call was issued specifying the MQGMO_MARK_SKIP_BACKOUT option in the Options field of MQGMO, but a message has already been marked within the current unit of work. Only one marked message is allowed within each unit of work.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application so that no more than one message is marked within each unit of work.

2063 (X'080F')
MQRC_SECURITY_ERROR
Explanation:

An MQCONN, MQCONNX, MQOPEN, MQPUT1, or MQCLOSE call was issued, but it failed because a security error occurred.

  • On z/OS, the security error was returned by the External Security Manager.

Completion Code:

MQCC_FAILED

Programmer Response:

Note the error from the security manager, and contact your system programmer or security administrator.

  • On i5/OS, the FFST log will contain the error information.

2065 (X'0811')
MQRC_SELECTOR_COUNT_ERROR
Explanation:

On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is not valid. 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 detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value in the range 0 through 256.

2066 (X'0812')
MQRC_SELECTOR_LIMIT_EXCEEDED
Explanation:

On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is larger than the maximum supported (256).

Completion Code:

MQCC_FAILED

Programmer Response:

Reduce the number of selectors specified on the call; the valid range is 0 through 256.

2067 (X'0813')
MQRC_SELECTOR_ERROR
Explanation:

An MQINQ or MQSET call was issued, but the Selectors array contains a selector that is not valid for one of the following reasons:

  • The selector is not supported or out of range.

  • The selector is not applicable to the type of object whose attributes are being inquired or set.

  • The selector is for an attribute that cannot be set.

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 detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the value 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 be set.

2068 (X'0814')
MQRC_SELECTOR_NOT_FOR_TYPE
Explanation:

On the MQINQ call, one or more 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 queue that resolved to a remote instance of the queue. In this case only a subset of the attributes that are valid for local queues can be inquired. See the usage notes in the description of MQINQ in the WebSphere MQ Application Programming Guide for further details.

The call completes with MQCC_WARNING, with the attribute values for the inapplicable selectors set as follows:

  • For integer attributes, the corresponding elements of IntAttrs are set to MQIAV_NOT_APPLICABLE.

  • For character attributes, the appropriate parts of the CharAttrs string are set to a character string consisting entirely of asterisks (*).

Completion Code:

MQCC_WARNING

Programmer Response:

Verify that the selector specified is the one that was intended.

If the queue is a cluster queue, specifying one of the MQOO_BROWSE, MQOO_INPUT_*, or MQOO_SET options in addition to MQOO_INQUIRE forces the queue to resolve to the local instance of the queue. However, if there is no local instance of the queue the MQOPEN call fails.

2069 (X'0815')
MQRC_SIGNAL_OUTSTANDING
Explanation:

An MQGET call was issued with either the MQGMO_SET_SIGNAL or MQGMO_WAIT option, but there is already a signal outstanding for the queue handle Hobj.

This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the application logic. If it is necessary to set a signal or wait when there is a signal outstanding for the same queue, a different object handle must be used.

2070 (X'0816')
MQRC_SIGNAL_REQUEST_ACCEPTED
Explanation:

An MQGET call was issued specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but no suitable message was available; the call returns immediately. The application can now wait for the signal to be delivered.

  • On z/OS, the application should wait on the Event Control Block pointed to by the Signal1 field.

  • On Windows 95, Windows 98, the application should wait for the signal Windows message to be delivered.

This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98.

Completion Code:

MQCC_WARNING

Programmer Response:

Wait for the signal; when it is delivered, check the signal to ensure that a message is now available. If it is, reissue the MQGET call.

  • On z/OS, wait on the ECB pointed to by the Signal1 field and, when it is posted, check it to ensure that a message is now available.

  • On Windows 95, Windows 98, the application (thread) should continue executing its message loop.

2071 (X'0817')
MQRC_STORAGE_NOT_AVAILABLE
Explanation:

The call failed because there is insufficient main storage available.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that active applications are behaving correctly, for example, that they are not looping unexpectedly. If no problems are found, make more main storage available.

  • On z/OS, if no application problems are found, ask your system programmer to increase the size of the region in which the queue manager runs.

2072 (X'0818')
MQRC_SYNCPOINT_NOT_AVAILABLE
Explanation:

Either MQGMO_SYNCPOINT was specified on an MQGET call or MQPMO_SYNCPOINT was specified on an MQPUT or MQPUT1 call, but the local queue manager was unable to honor the request. If the queue manager does not support units of work, the SyncPoint queue-manager attribute will have the value MQSP_NOT_AVAILABLE.

This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an external unit-of-work coordinator is being used. If that 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 MQRC_SYNCPOINT_NOT_AVAILABLE is returned.

  • On i5/OS, this reason codes means that i5/OS Commitment Control is not started, or is unavailable for use by the queue manager.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as appropriate.

  • On i5/OS, ensure that Commitment Control has been started. If this reason code occurs after Commitment Control has been started, contact your system programmer.

2075 (X'081B')
MQRC_TRIGGER_CONTROL_ERROR
Explanation:

On an MQSET call, the value specified for the MQIA_TRIGGER_CONTROL attribute selector is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value.

2076 (X'081C')
MQRC_TRIGGER_DEPTH_ERROR
Explanation:

On an MQSET call, the value specified for the MQIA_TRIGGER_DEPTH attribute selector is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value that is greater than zero.

2077 (X'081D')
MQRC_TRIGGER_MSG_PRIORITY_ERR
Explanation:

On an MQSET call, the value specified for the MQIA_TRIGGER_MSG_PRIORITY attribute selector is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value in the range zero through the value of MaxPriority queue-manager attribute.

2078 (X'081E')
MQRC_TRIGGER_TYPE_ERROR
Explanation:

On an MQSET call, the value specified for the MQIA_TRIGGER_TYPE attribute selector is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value.

2079 (X'081F')
MQRC_TRUNCATED_MSG_ACCEPTED
Explanation:

On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was specified, so the call completes. The message is removed from the queue (subject to unit-of-work considerations), or, if this was a browse operation, the browse cursor is advanced to this message.

The DataLength parameter is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in.

Completion Code:

MQCC_WARNING

Programmer Response:

None, because the application expected this situation.

2080 (X'0820')
MQRC_TRUNCATED_MSG_FAILED
Explanation:

On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was not specified, so the message has not been removed from the queue. If this was a browse operation, the browse cursor remains where it was before this call, but if MQGMO_BROWSE_FIRST was specified, the browse cursor is positioned logically before the highest-priority message on the queue.

The DataLength field is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in.

Completion Code:

MQCC_WARNING

Programmer Response:

Supply a buffer that is at least as large as DataLength, or specify MQGMO_ACCEPT_TRUNCATED_MSG if not all of the message data is required.

2082 (X'0822')
MQRC_UNKNOWN_ALIAS_BASE_Q
Explanation:

An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseQName in the alias queue attributes is not recognized as a queue name.

This reason code can also occur when BaseQName is the name of a cluster queue that cannot be resolved successfully.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the queue definitions.

2085 (X'0825')
MQRC_UNKNOWN_OBJECT_NAME
Explanation:

An MQOPEN or MQPUT1 call was issued, but the object identified by the ObjectName and ObjectQMgrName fields in the object descriptor MQOD cannot be found. One of the following applies:

  • The ObjectQMgrName field is one of the following:

    • Blank

    • The name of the local queue manager

    • The name of a local definition of a remote queue (a queue-manager alias) in which the RemoteQMgrName attribute is the name of the local queue manager

    but no object with the specified ObjectName and ObjectType exists on the local queue manager.

  • The object being opened is a cluster queue that is hosted on a remote queue manager, but the local queue manager does not have a defined route to the remote queue manager.

  • The object being opened is a queue definition that has QSGDISP(GROUP). Such definitions cannot be used with the MQOPEN and MQPUT1 calls.

This can also occur in response to a command that specifies the name of an object or other item that does not exist.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid object name. Ensure that the name is padded to the right with blanks if necessary. If this is correct, check the object definitions.

2086 (X'0826')
MQRC_UNKNOWN_OBJECT_Q_MGR
Explanation:

On an MQOPEN or MQPUT1 call, the ObjectQMgrName field in the object descriptor MQOD does not satisfy the naming rules for objects. For more information, see the WebSphere MQ Application Programming Guide.

This reason also occurs if the ObjectType field in the object descriptor has the value MQOT_Q_MGR, and the ObjectQMgrName field is not blank, but the name specified is not the name of the local queue manager.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid queue manager name. To refer to the local queue manager, a name consisting entirely of blanks or beginning with a null character can be used. Ensure that the name is padded to the right with blanks or terminated with a null character if necessary.

2087 (X'0827')
MQRC_UNKNOWN_REMOTE_Q_MGR
Explanation:

On an MQOPEN or MQPUT1 call, an error occurred with the queue-name resolution, for one of the following reasons:

  • ObjectQMgrName is blank or the name of the local queue manager, ObjectName is the name of a local definition of a remote queue (or an alias to one), and one of the following is true:

    • RemoteQMgrName is blank or the name of the local queue manager. Note that this error occurs even if XmitQName is not blank.

    • XmitQName is blank, but there is no transmission queue defined with the name of RemoteQMgrName, and the DefXmitQName queue-manager attribute is blank.

    • RemoteQMgrName and RemoteQName specify a cluster queue that cannot be resolved successfully, and the DefXmitQName queue-manager attribute is blank.

  • ObjectQMgrName is the name of a local definition of a remote queue (containing a queue-manager alias definition), and one of the following is true:

    • RemoteQName is not blank.

    • XmitQName is blank, but there is no transmission queue defined with the name of RemoteQMgrName, and the DefXmitQName queue-manager attribute is blank.

  • ObjectQMgrName is not:

    • Blank

    • The name of the local queue manager

    • The name of a transmission queue

    • The name of a queue-manager alias definition (that is, a local definition of a remote queue with a blank RemoteQName)

    but the DefXmitQName queue-manager attribute is blank and the queue manager is not part of a queue-sharing group with intra-group queuing enabled.

  • ObjectQMgrName is the name of a model queue.

  • The queue name is resolved through a cell directory. However, there is no queue defined with the same name as the remote queue manager name obtained from the cell directory, and the DefXmitQName queue-manager attribute is blank.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the values specified for ObjectQMgrName and ObjectName. If these are correct, check the queue definitions.

2090 (X'082A')
MQRC_WAIT_INTERVAL_ERROR
Explanation:

On the MQGET call, the value specified for the WaitInterval field in the GetMsgOpts parameter is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value greater than or equal to zero, or the special value MQWI_UNLIMITED if an indefinite wait is required.

2091 (X'082B')
MQRC_XMIT_Q_TYPE_ERROR
Explanation:

On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition:

  • XmitQName is not blank, but specifies a queue that is not a local queue

  • XmitQName is blank, but RemoteQMgrName specifies a queue that is not a local queue

This reason also occurs if the queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a queue, but this is not a local queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide.

2092 (X'082C')
MQRC_XMIT_Q_USAGE_ERROR
Explanation:

On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager, but one of the following occurred:

  • ObjectQMgrName specifies the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION.

  • The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition:

    • XmitQName is not blank, but specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION

    • XmitQName is blank, but RemoteQMgrName specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION

    • XmitQName specifies the queue SYSTEM.QSG.TRANSMIT.QUEUE the IGQ queue manager attribute indicates that IGQ is DISABLED.

  • The queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide.

2093 (X'082D')
MQRC_NOT_OPEN_FOR_PASS_ALL
Explanation:

An MQPUT call was issued with the MQPMO_PASS_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_PASS_ALL_CONTEXT option.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_PASS_ALL_CONTEXT (or another option that implies it) when the queue is opened.

2094 (X'082E')
MQRC_NOT_OPEN_FOR_PASS_IDENT
Explanation:

An MQPUT call was issued with the MQPMO_PASS_IDENTITY_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_PASS_IDENTITY_CONTEXT option.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_PASS_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened.

2095 (X'082F')
MQRC_NOT_OPEN_FOR_SET_ALL
Explanation:

An MQPUT call was issued with the MQPMO_SET_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_ALL_CONTEXT option.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_SET_ALL_CONTEXT when the queue is opened.

2096 (X'0830')
MQRC_NOT_OPEN_FOR_SET_IDENT
Explanation:

An MQPUT call was issued with the MQPMO_SET_IDENTITY_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_IDENTITY_CONTEXT option.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_SET_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened.

2097 (X'0831')
MQRC_CONTEXT_HANDLE_ERROR
Explanation:

On an MQPUT or MQPUT1 call, MQPMO_PASS_IDENTITY_CONTEXT or MQPMO_PASS_ALL_CONTEXT was specified, but the handle specified in the Context field of the PutMsgOpts parameter is either not a valid queue handle, or it is a valid queue handle but the queue was not opened with MQOO_SAVE_ALL_CONTEXT.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQOO_SAVE_ALL_CONTEXT when the queue referred to is opened.

2098 (X'0832')
MQRC_CONTEXT_NOT_AVAILABLE
Explanation:

On an MQPUT or MQPUT1 call, MQPMO_PASS_IDENTITY_CONTEXT or 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. This arises if no message has yet been successfully retrieved with the queue handle referred to, or if the last successful MQGET call was a browse.

This condition does not arise if the message that was last retrieved had no context associated with it.

  • On z/OS, if a message is received by a message channel agent that is putting messages with the authority of the user identifier in the message, this code is returned in the Feedback field of an exception report if the message has no context associated with it.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that a successful nonbrowse get call has been issued with the queue handle referred to.

2099 (X'0833')
MQRC_SIGNAL1_ERROR
Explanation:

An MQGET call was issued, specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but the Signal1 field is not valid.

  • 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 not valid; if not detected, unpredictable results occur.)

  • On Windows 95, Windows 98, the window handle in the Signal1 field is not valid.

This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the setting of the Signal1 field.

2100 (X'0834')
MQRC_OBJECT_ALREADY_EXISTS
Explanation:

An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists.

  • On z/OS, a rare "race condition" can also give rise to this reason code; see the description of reason code MQRC_NAME_IN_USE for more details.

Completion Code:

MQCC_FAILED

Programmer Response:

If supplying a dynamic queue name in full, ensure that it obeys the naming conventions for dynamic queues; if it does, either supply a different name, or delete the existing queue if it is no longer required. Alternatively, allow the queue manager to generate the name.

If the queue manager is generating the name (either in part or in full), reissue the MQOPEN call.

2101 (X'0835')
MQRC_OBJECT_DAMAGED
Explanation:

The object accessed by the call is damaged and cannot be used. For example, this may be because the definition of the object in main storage is not consistent, or because it differs from the definition of the object on disk, or because the definition on disk cannot be read. The object can be deleted, although it may not be possible to delete the associated user space.

  • On z/OS, this reason occurs when the DB2 list header or structure number associated with a shared queue is zero. This situation arises as a result of using the MQSC command DELETE CFSTRUCT to delete the DB2 structure definition. The command resets the list header and structure number to zero for each of the shared queues that references the deleted CF strcture.

Completion Code:

MQCC_FAILED

Programmer Response:

It may be necessary to stop and restart the queue manager, or to restore the queue-manager data from back-up storage.

  • On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem.

  • On z/OS, delete the shared queue and redefine it using the MQSC command DEFINE QLOCAL. This will automatically define a CF structure and allocate list headers for it.

2102 (X'0836')
MQRC_RESOURCE_PROBLEM
Explanation:

There are insufficient system resources to complete the call successfully.

Completion Code:

MQCC_FAILED

Programmer Response:

Run the application when the machine is less heavily loaded.

  • On z/OS, check the operator console for messages that may provide additional information.

  • On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem.

2103 (X'0837')
MQRC_ANOTHER_Q_MGR_CONNECTED
Explanation:

An MQCONN or MQCONNX call was issued, but the thread or process is already connected to a different queue manager. The thread or process can connect to only one queue manager at a time.

  • On z/OS, this reason code does not occur.

  • On Windows, MTS objects do not receive this reason code, as connections to other queue managers are allowed.

Completion Code:

MQCC_FAILED

Programmer Response:

Use the MQDISC call to disconnect from the queue manager that is already connected, and then issue the MQCONN or MQCONNX call to connect to the new queue manager.

Disconnecting from the existing queue manager will close any queues that are currently open; it is recommended that any uncommitted units of work should be committed or backed out before the MQDISC call is issued.

2104 (X'0838')
MQRC_UNKNOWN_REPORT_OPTION
Explanation:

An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD contains one or more options that are not recognized by the local queue manager. The options are accepted.

The options that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details.

Completion Code:

MQCC_WARNING

Programmer Response:

If this reason code is expected, no corrective action is required. If this reason code is not expected, do the following:

  • Ensure that the Report field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call.

  • Ensure that the report options specified are valid; see the Report field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid report options.

  • If multiple report options are being set by adding the individual report options together, ensure that the same report option is not added twice.

  • Check that conflicting report options are not specified. For example, do not add both MQRO_EXCEPTION and MQRO_EXCEPTION_WITH_DATA to the Report field; only one of these can be specified.

2105 (X'0839')
MQRC_STORAGE_CLASS_ERROR
Explanation:

The MQPUT or MQPUT1 call was issued, but the storage-class object defined for the queue does not exist.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Create the storage-class object required by the queue, or modify the queue definition to use an existing storage class. The name of the storage-class object used by the queue is given by the StorageClass queue attribute.

2106 (X'083A')
MQRC_COD_NOT_VALID_FOR_XCF_Q
Explanation:

An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD specifies one of the MQRO_COD_* options and the target queue is an XCF queue. MQRO_COD_* options cannot be specified for XCF queues.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the relevant MQRO_COD_* option.

2107 (X'083B')
MQRC_XWAIT_CANCELED
Explanation:

An MQXWAIT call was issued, but the call has been canceled because a STOP CHINIT command has been issued (or the queue manager has been stopped, which causes the same effect). Refer to the WebSphere MQ Intercommunication book for details of the MQXWAIT call.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Tidy up and terminate.

2108 (X'083C')
MQRC_XWAIT_ERROR
Explanation:

An MQXWAIT call was issued, but the invocation was not valid for one of the following reasons:

  • The wait descriptor MQXWD contains data that is not valid.

  • The linkage stack level is not valid.

  • The addressing mode is not valid.

  • There are too many wait events outstanding.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Obey the rules for using the MQXWAIT call. Refer to the WebSphere MQ Intercommunication book for details of this call.

2109 (X'083D')
MQRC_SUPPRESSED_BY_EXIT
Explanation:

On any call other than MQCONN or MQDISC, the API crossing exit suppressed the call.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Obey the rules for MQI calls that the exit enforces. To find out the rules, see the writer of the exit.

2110 (X'083E')
MQRC_FORMAT_ERROR
Explanation:

An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but the message cannot be converted successfully due to an error associated with the message format. Possible errors include:

  • The format name in the message is MQFMT_NONE.

  • A user-written exit with the name specified by the Format field in the message cannot be found.

  • 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 CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING.

If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.

Completion Code:

MQCC_WARNING

Programmer Response:

Check the format name that was specified when the message was put. If this is not one of the built-in formats, check that a suitable exit with the same name as the format is available for the queue manager to load. Verify that the data in the message corresponds to the format expected by the exit.

2111 (X'083F')
MQRC_SOURCE_CCSID_ERROR
Explanation:

The coded character-set identifier from which character data is to be converted is not valid or not supported.

This can occur on the MQGET call when the MQGMO_CONVERT option is included in the GetMsgOpts parameter; the coded character-set identifier in error is the CodedCharSetId field in the message being retrieved. In this case, the message data is 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 with MQCC_WARNING.

This reason can also occur on the MQGET call when the message contains one or more MQ header structures (MQCIH, MQDLH, MQIIH, MQRMH), and the CodedCharSetId field in the message specifies a character set that does not have SBCS characters for the characters that are valid in queue names. MQ header structures containing such characters are not valid, and so the message is returned unconverted. The Unicode character set UCS-2 is an example of such a character set.

If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.

This reason can also occur on the MQXCNVC call; the coded character-set identifier in error is the SourceCCSID parameter. Either the SourceCCSID parameter specifies a value that is not valid or not supported, or the SourceCCSID parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_WARNING or MQCC_FAILED

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 MQXCNVC call. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the specified character set, conversion must be carried out by the application.

2112 (X'0840')
MQRC_SOURCE_INTEGER_ENC_ERROR
Explanation:

On an MQGET call, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies an integer encoding that is not recognized. The message data is 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 with MQCC_WARNING.

If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.

This reason code can also occur on the MQXCNVC call, when the Options parameter contains an unsupported MQDCC_SOURCE_* value, or when MQDCC_SOURCE_ENC_UNDEFINED is specified for a UCS-2 code page.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Check the integer encoding 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 not supported for the required integer encoding, conversion must be carried out by the application.

2113 (X'0841')
MQRC_SOURCE_DECIMAL_ENC_ERROR
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies a decimal encoding that is not recognized. The message data is 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 with MQCC_WARNING.

If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.

Completion Code:

MQCC_WARNING

Programmer Response:

Check the decimal encoding 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 not supported for the required decimal encoding, conversion must be carried out by the application.

2114 (X'0842')
MQRC_SOURCE_FLOAT_ENC_ERROR
Explanation:

On an MQGET call, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies a floating-point encoding that is not recognized. The message data is 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 with MQCC_WARNING.

If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.

Completion Code:

MQCC_WARNING

Programmer Response:

Check the floating-point encoding 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 not supported for the required floating-point encoding, conversion must be carried out by the application.

2115 (X'0843')
MQRC_TARGET_CCSID_ERROR
Explanation:

The coded character-set identifier to which character data is to be converted is not valid or not supported.

This can occur on the MQGET call when the MQGMO_CONVERT option is included in the GetMsgOpts parameter; the coded character-set identifier in error is the CodedCharSetId field in the MsgDesc parameter. In this case, the message data is 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 with MQCC_WARNING.

This reason can also occur on the MQGET call when the message contains one or more MQ header structures (MQCIH, MQDLH, MQIIH, MQRMH), and the CodedCharSetId field in the MsgDesc parameter specifies a character set that does not have SBCS characters for the characters that are valid in queue names. The Unicode character set UCS-2 is an example of such a character set.

This reason can also occur on the MQXCNVC call; the coded character-set identifier in error is the TargetCCSID parameter. Either the TargetCCSID parameter specifies a value that is not valid or not supported, or the TargetCCSID parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Check the character-set identifier that was specified for the CodedCharSetId field in the MsgDesc parameter on the MQGET call, or that was specified for the SourceCCSID parameter on the MQXCNVC call. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the specified character set, conversion must be carried out by the application.

2116 (X'0844')
MQRC_TARGET_INTEGER_ENC_ERROR
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies an integer encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message being retrieved, and the call completes with MQCC_WARNING.

This reason code can also occur on the MQXCNVC call, when the Options parameter contains an unsupported MQDCC_TARGET_* value, or when MQDCC_TARGET_ENC_UNDEFINED is specified for a UCS-2 code page.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Check the integer encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required integer encoding, conversion must be carried out by the application.

2117 (X'0845')
MQRC_TARGET_DECIMAL_ENC_ERROR
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies a decimal encoding that is not recognized. The message data is 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 with MQCC_WARNING.

Completion Code:

MQCC_WARNING

Programmer Response:

Check the decimal encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required decimal encoding, conversion must be carried out by the application.

2118 (X'0846')
MQRC_TARGET_FLOAT_ENC_ERROR
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies a floating-point encoding that is not recognized. The message data is 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 with MQCC_WARNING.

Completion Code:

MQCC_WARNING

Programmer Response:

Check the floating-point encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required floating-point encoding, conversion must be carried out by the application.

2119 (X'0847')
MQRC_NOT_CONVERTED
Explanation:

An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but an error occurred during conversion of the data in the message. The message data is 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 with MQCC_WARNING.

If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.

This error may also indicate that a parameter to the data-conversion service is not supported.

Completion Code:

MQCC_WARNING

Programmer Response:

Check that the message data is correctly described by the Format, CodedCharSetId and Encoding parameters that were specified when the 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 queue-manager conversion. If the required conversion is not supported, conversion must be carried out by the application.

2120 (X'0848')
MQRC_CONVERTED_MSG_TOO_BIG
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the message data expanded during data conversion and exceeded the size of the buffer provided by the application. However, the message had already been removed from the queue because prior to conversion the message data could be accommodated in the application buffer without truncation.

The message is returned unconverted, with the CompCode parameter of the MQGET call set to MQCC_WARNING. If the message consists of several parts, each of which is described by its own character-set and encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various character-set and encoding fields always correctly describe the relevant message data.

This reason can also occur on the MQXCNVC call, when the TargetBuffer parameter is too small too 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 the case of a DBCS string or mixed SBCS/DBCS string, this length may be less than the length of TargetBuffer.

Completion Code:

MQCC_WARNING

Programmer Response:

For the MQGET call, check that the exit is converting the message data correctly and setting the output length DataLength to the appropriate value. If it is, the application issuing the MQGET call must provide a larger buffer for the Buffer parameter.

For the MQXCNVC call, if the string must be converted without truncation, provide a larger output buffer.

2121 (X'0849')
MQRC_NO_EXTERNAL_PARTICIPANTS
Explanation:

An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but no participating resource managers have been registered with the queue manager. As a result, only changes to MQ resources can be coordinated by the queue manager in the unit of work.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows.

Completion Code:

MQCC_WARNING

Programmer Response:

If the application does not require non-MQ resources to participate in the unit of work, this reason code can be ignored or the MQBEGIN call removed. Otherwise consult your system programmer to determine why the required resource managers have not been registered with the queue manager; the queue manager's configuration file may be in error.

2122 (X'084A')
MQRC_PARTICIPANT_NOT_AVAILABLE
Explanation:

An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but one or more of the participating resource managers that had been registered with the queue manager is not available. As a result, changes to those resources cannot be coordinated by the queue manager in the unit of work.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows.

Completion Code:

MQCC_WARNING

Programmer Response:

If the application does not require non-MQ resources to participate in the unit of work, this reason code can be ignored. Otherwise consult your system programmer to determine why the required resource managers are not available. The resource manager may have been halted temporarily, or there may be an error in the queue manager's configuration file.

2123 (X'084B')
MQRC_OUTCOME_MIXED
Explanation:

The queue manager is acting as the unit-of-work coordinator for a unit of work that involves other resource managers, but one of the following occurred:

  • 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 of work instead of committing it. As a result, the outcome of the unit of work is mixed.

  • An MQBACK call was issued to back out a unit of work, but one or more of the participating resource managers had already committed the unit of work.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Examine the queue-manager error logs for messages relating to the mixed outcome; these messages identify the resource managers that are affected. Use procedures local to the affected resource managers to resynchronize the resources.

This reason code does not prevent the application initiating further units of work.

2124 (X'084C')
MQRC_OUTCOME_PENDING
Explanation:

The queue manager is acting as the unit-of-work coordinator for a unit of work that involves other resource managers, and an MQCMIT or MQDISC call was issued to commit the unit of work, but one or more of the participating resource managers has not confirmed that the unit of work was committed successfully.

The completion of the commit operation will happen at some point in the future, but there remains the possibility that the outcome will be mixed.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows.

Completion Code:

MQCC_WARNING

Programmer Response:

Use the normal error-reporting mechanisms to determine whether the outcome was mixed. If it was, take appropriate action to resynchronize the resources.

This reason code does not prevent the application initiating further units of work.

2125 (X'084D')
MQRC_BRIDGE_STARTED
Explanation:

The IMS bridge has been started.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2126 (X'084E')
MQRC_BRIDGE_STOPPED
Explanation:

The IMS bridge has been stopped.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2127 (X'084F')
MQRC_ADAPTER_STORAGE_SHORTAGE
Explanation:

On an MQCONN call, the adapter was unable to acquire storage.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Notify the system programmer. The system programmer should determine why the system is short on storage, and take appropriate action, for example, increase the region size on the step or job card.

2128 (X'0850')
MQRC_UOW_IN_PROGRESS
Explanation:

An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but a unit of work is already in existence for the connection handle specified. This may be a global unit of work started by a previous MQBEGIN call, or a unit of work that is local to the queue manager or one of the cooperating resource managers. No more than one unit of work can exist concurrently for a connection handle.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Review the application logic to determine why there is a unit of work already in existence. Move the MQBEGIN call to the appropriate place in the application.

2129 (X'0851')
MQRC_ADAPTER_CONN_LOAD_ERROR
Explanation:

On an MQCONN call, the connection handling module (CSQBCON for batch and CSQQCONN for IMS) could not be loaded, so the adapter could not link to it.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL.

2130 (X'0852')
MQRC_ADAPTER_SERV_LOAD_ERROR
Explanation:

On an MQI call, the batch adapter could not load the API service module CSQBSRV, and so could not link to it.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL.

2131 (X'0853')
MQRC_ADAPTER_DEFS_ERROR
Explanation:

On an MQCONN call, the subsystem definition module (CSQBDEFV for batch and CSQQDEFV for IMS) does not contain the required control block identifier.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Check your library concatenation. If this is correct, check that the CSQBDEFV or CSQQDEFV module contains the required subsystem ID.

2132 (X'0854')
MQRC_ADAPTER_DEFS_LOAD_ERROR
Explanation:

On an MQCONN call, the subsystem definition module (CSQBDEFV for batch and CSQQDEFV for IMS) could not be loaded.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL.

2133 (X'0855')
MQRC_ADAPTER_CONV_LOAD_ERROR
Explanation:

On an MQGET call, the adapter (batch or IMS) could not load the data conversion services modules.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library concatenation has been specified in the batch 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 structure MQBO is not valid, for one of the following reasons:

  • The StrucId field is not MQBO_STRUC_ID.

  • The Vfield is not MQBO_VERSION_1.

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQBO structure are set correctly.

2135 (X'0857')
MQRC_DH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQDH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQDH_STRUC_ID.

  • The Vfield is not MQDH_VERSION_1.

  • The StrucLength field specifies a value that is too small to include the structure plus the arrays of MQOR and MQPMR records.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

2136 (X'0858')
MQRC_MULTIPLE_REASONS
Explanation:

An MQOPEN, MQPUT or MQPUT1 call was issued to open a distribution list or put a message to a distribution list, but the result of the call was not the same for all of the destinations in the list. One of the following applies:

  • The call succeeded for some of the destinations but not others. The completion code is MQCC_WARNING in this case.

  • The call failed for all of the destinations, but for differing reasons. The completion code is MQCC_FAILED in this case.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Examine the MQRR response records to identify the destinations for which the call failed, and the reason for the failure. Ensure that sufficient response records are provided by the application on the call to enable the error(s) to be determined. For the MQPUT1 call, the response records must be specified using the MQOD structure, and not the MQPMO structure.

2137 (X'0859')
MQRC_OPEN_FAILED
Explanation:

A queue or other MQ object could not be opened successfully, for one of the following reasons:

  • An MQCONN or MQCONNX call was issued, but 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.

  • An MQPUT call was issued to put a message to a distribution list, but the message could not be sent to 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 Reason field of the MQRR response record.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Do one of the following:

  • If the error occurred on the MQCONN or MQCONNX call, ensure that the required objects exist by running the following command and then retrying the application: 

    STRMQM -c qmgr
    where

    qmgr should be replaced by the name of the queue manager.

  • If the error occurred on the MQPUT call, examine the MQRR response records specified on the MQOPEN call to determine the reason that the queue failed to open. Ensure that sufficient response records are provided by the application on the call to enable the error(s) to be determined.

2138 (X'085A')
MQRC_ADAPTER_DISC_LOAD_ERROR
Explanation:

On an MQDISC call, the disconnect handling module (CSQBDSC for batch and CSQQDISC for IMS) could not be loaded, so the adapter could not link to it.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.

2139 (X'085B')
MQRC_CNO_ERROR
Explanation:

On an MQCONNX call, the connect-options structure MQCNO is not valid, for one of the following reasons:

  • The StrucId field is not MQCNO_STRUC_ID.

  • The Vfield specifies a value that is not valid or not supported.

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the parameter pointer points to read-only storage.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQCNO structure are set correctly.

2140 (X'085C')
MQRC_CICS_WAIT_FAILED
Explanation:

On any MQI call, the CICS adapter issued an EXEC CICS WAIT request, but the request was rejected by CICS.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Examine the CICS trace data for actual response codes. The most likely cause is that the task has been canceled by the operator or by the system.

2141 (X'085D')
MQRC_DLH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQDLH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQDLH_STRUC_ID.

  • The Vfield is not MQDLH_VERSION_1.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

2142 (X'085E')
MQRC_HEADER_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQ header structure that is not valid. Possible errors include the following:

  • The StrucId field is not valid.

  • The Vfield is not valid.

  • The StrucLength field specifies a value that is too small.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

2143 (X'085F')
MQRC_SOURCE_LENGTH_ERROR
Explanation:

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

This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_SOURCE_LENGTH_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit.

Completion Code:

MQCC_WARNING or 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 correct.

2144 (X'0860')
MQRC_TARGET_LENGTH_ERROR
Explanation:

On the MQXCNVC call, the TargetLength parameter is not valid for one of the following reasons:

  • TargetLength is less than zero.

  • The TargetLength parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The MQDCC_FILL_TARGET_BUFFER option is specified, but the value of TargetLength is such that the target buffer cannot be filled completely with valid characters. This can occur when TargetCCSID is a pure DBCS character set (such as UCS-2), but TargetLength specifies a length that is an odd number of bytes.

This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_TARGET_LENGTH_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit.

Completion Code:

MQCC_WARNING or 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.

If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct.

2145 (X'0861')
MQRC_SOURCE_BUFFER_ERROR
Explanation:

On the MQXCNVC call, the SourceBuffer parameter pointer is not valid, or points to storage that cannot be accessed for the entire length specified by SourceLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_SOURCE_BUFFER_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct.

2146 (X'0862')
MQRC_TARGET_BUFFER_ERROR
Explanation:

On the MQXCNVC call, the TargetBuffer parameter pointer is not valid, or points to read-only storage, or to storage that cannot be accessed for the entire length specified by TargetLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_TARGET_BUFFER_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct.

2148 (X'0864')
MQRC_IIH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQIIH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQIIH_STRUC_ID.

  • The Vfield is not MQIIH_VERSION_1.

  • The StrucLength field is not MQIIH_LENGTH_1.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2149 (X'0865')
MQRC_PCF_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued to put a message containing PCF data, but the length of the message does not equal the sum of the lengths of the PCF structures present in the message. This can occur for messages with the following format names:

  • MQFMT_ADMIN

  • MQFMT_EVENT

  • MQFMT_PCF

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the length of the message specified on the MQPUT or MQPUT1 call equals the sum of the lengths of the PCF structures 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:

  • On the MQXCNVC call, when the SourceCCSID parameter specifies the coded character-set identifier of a double-byte character set, but the SourceBuffer parameter does not contain a valid DBCS string. This may be because the string contains characters that are not valid DBCS characters, or because the string is a mixed SBCS/DBCS string and the shift-out/shift-in characters are not correctly paired. The completion code is MQCC_FAILED in this case.

  • On the MQGET call, when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_DBCS_ERROR reason code was returned by an MQXCNVC call issued by the data conversion exit. The completion code is MQCC_WARNING in this case.

Completion Code:

MQCC_WARNING or MQCC_FAILED

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
Explanation:

An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the ObjectName field is neither blank nor the null string.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

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 distribution list, set the RecsPresent field to zero.

2153 (X'0869')
MQRC_OBJECT_Q_MGR_NAME_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the ObjectQMgrName field is neither blank nor the null string.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

If it is intended to open a distribution list, set the ObjectQMgrName field to blanks or the null string. If it is not intended to open a distribution list, set the RecsPresent field to zero.

2154 (X'086A')
MQRC_RECS_PRESENT_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued, but the call failed for one of the following reasons:

  • RecsPresent in MQOD is less than zero.

  • ObjectType in MQOD is not MQOT_Q, and RecsPresent is not zero. RecsPresent must be zero if the object being opened is not a queue.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

If it is intended to open a distribution list, set the ObjectType field to MQOT_Q and RecsPresent to the number of destinations in the list. If it is not intended to open a distribution list, set the RecsPresent field to zero.

2155 (X'086B')
MQRC_OBJECT_RECORDS_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the MQOR object records are not specified correctly. One of the following applies:

  • ObjectRecOffset is zero and ObjectRecPtr is zero or the null pointer.

  • ObjectRecOffset is not zero and ObjectRecPtr is not zero and not the null pointer.

  • ObjectRecPtr is not a valid pointer.

  • ObjectRecPtr or ObjectRecOffset points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that one of ObjectRecOffset and ObjectRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage.

2156 (X'086C')
MQRC_RESPONSE_RECORDS_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the MQRR response records are not specified correctly. One of the following applies:

  • ResponseRecOffset is not zero and ResponseRecPtr is not zero and not the null pointer.

  • ResponseRecPtr is not a valid pointer.

  • ResponseRecPtr or ResponseRecOffset points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that at least one of ResponseRecOffset and ResponseRecPtr is zero. Ensure that the field used points to accessible storage.

2157 (X'086D')
MQRC_ASID_MISMATCH
Explanation:

On any MQI call, the caller's primary ASID was found to be different from the home ASID.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the application (MQI calls cannot be issued in cross-memory mode). Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.

2158 (X'086E')
MQRC_PMO_RECORD_FLAGS_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued to put a message, but the PutMsgRecFields field in the MQPMO structure is not valid, for one of the following reasons:

  • The field contains flags that are not valid.

  • The message is being put to a distribution list, and put message records have been provided (that is, RecsPresent is greater than zero, and one of PutMsgRecOffset or PutMsgRecPtr is nonzero), but PutMsgRecFields has the value MQPMRF_NONE.

  • MQPMRF_ACCOUNTING_TOKEN is specified without either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that PutMsgRecFields is set with the appropriate MQPMRF_* flags to indicate which fields are present in the put message records. If MQPMRF_ACCOUNTING_TOKEN is specified, ensure that either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT is also specified. Alternatively, set both PutMsgRecOffset and PutMsgRecPtr to zero.

2159 (X'086F')
MQRC_PUT_MSG_RECORDS_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued to put a message to a distribution list, but the MQPMR put message records are not specified correctly. One of the following applies:

  • PutMsgRecOffset is not zero and PutMsgRecPtr is not zero and not the null pointer.

  • PutMsgRecPtr is not a valid pointer.

  • PutMsgRecPtr or PutMsgRecOffset points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that at least one of PutMsgRecOffset and PutMsgRecPtr is zero. Ensure that the field used points to accessible storage.

2160 (X'0870')
MQRC_CONN_ID_IN_USE
Explanation:

On an MQCONN call, the connection identifier assigned by the queue manager to the connection between a CICS or IMS allied address space and the queue manager conflicts with the connection identifier of another connected CICS or IMS system. The connection identifier assigned is as follows:

  • For CICS, the applid

  • For IMS, the IMSID parameter on the IMSCTRL (sysgen) macro, or the IMSID parameter on the execution parameter (EXEC card in IMS control region JCL)

  • For batch, the job name

  • For TSO, the user ID

A conflict arises only if there are two CICS systems, two IMS systems, or one each of CICS and IMS, having the same connection identifiers. Batch and TSO connections need not have unique identifiers.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict.

2161 (X'0871')
MQRC_Q_MGR_QUIESCING
Explanation:

An MQI call was issued, but the call failed because the queue manager is quiescing (preparing to shut down).

When the queue manager is quiescing, the MQOPEN, MQPUT, MQPUT1, and MQGET calls can still complete successfully, but the application can request that they fail by specifying the appropriate option on the call:

  • MQOO_FAIL_IF_QUIESCING on MQOPEN

  • MQPMO_FAIL_IF_QUIESCING on MQPUT or MQPUT1

  • MQGMO_FAIL_IF_QUIESCING on MQGET

Specifying these options enables the application to become aware that the queue manager is preparing to shut down.

  • On z/OS:

    • For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed.

    • For CICS applications, this reason can be returned when no connection was established.

  • On i5/OS for applications running in compatibility mode, this reason can be returned when no connection was established.

Completion Code:

MQCC_FAILED

Programmer Response:

The application should tidy up and end. If the application specified the MQOO_FAIL_IF_QUIESCING, MQPMO_FAIL_IF_QUIESCING, or MQGMO_FAIL_IF_QUIESCING option on the failing call, the relevant option can be removed and the call reissued. By omitting these options, the application can continue working in order to complete and commit the current unit of work, but the application should not start a new unit of work.

2162 (X'0872')
MQRC_Q_MGR_STOPPING
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. No more MQI calls can be issued.

For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED.

  • On z/OS, the MQRC_CONNECTION_BROKEN reason may be returned instead if, as a result of system scheduling factors, the queue manager shuts down before the call completes.

Completion Code:

MQCC_FAILED

Programmer Response:

The application should tidy up and end. If the application is in the middle of a unit of work coordinated by an external unit-of-work coordinator, the application should issue the appropriate call to back out the unit of work. Any unit of work that is coordinated by the queue manager is backed out automatically.

2163 (X'0873')
MQRC_DUPLICATE_RECOV_COORD
Explanation:

On an MQCONN or MQCONNX call, a recovery coordinator already exists for the connection name specified on the connection call issued by the adapter.

A conflict arises only if there are two CICS systems, two IMS systems, or one each of CICS and IMS, having the same connection identifiers. Batch and TSO connections need not have unique identifiers.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict.

2173 (X'087D')
MQRC_PMO_ERROR
Explanation:

On an MQPUT or MQPUT1 call, the MQPMO structure is not valid, for one of the following reasons:

  • The StrucId field is not MQPMO_STRUC_ID.

  • The Vfield specifies a value that is not valid or not supported.

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQPMO structure are set correctly.

2183 (X'0887')
MQRC_API_EXIT_LOAD_ERROR
Explanation:

The API crossing exit module could not be linked. If this reason is returned when the API crossing exit is invoked after the call has been executed, the call itself may have executed correctly.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library concatenation has been specified, and that the API crossing exit module is executable and correctly named. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.

2184 (X'0888')
MQRC_REMOTE_Q_NAME_ERROR
Explanation:

On an MQOPEN or MQPUT1 call, one of the following occurred:

  • 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 that this error occurs even if the XmitQName in the definition is not blank.

  • The ObjectQMgrName field in the object descriptor is not blank and not the name of the local queue manager, but the ObjectName field is blank.

Completion Code:

MQCC_FAILED

Programmer Response:

Alter the local definition of the remote queue and supply a valid remote queue name, or supply a nonblank ObjectName in the object descriptor, as appropriate.

2185 (X'0889')
MQRC_INCONSISTENT_PERSISTENCE
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 field in MQMD is not consistent with the current group and segment information retained by the queue manager for the queue handle. All messages in a group and all segments in a logical message must have the same value for persistence, that is, all must be persistent, or all must be nonpersistent.

If the current call specifies MQPMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did, the call succeeds with completion code MQCC_WARNING.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Modify the application to ensure that the same value of persistence is used for all messages in the group, or all segments of the logical message.

2186 (X'088A')
MQRC_GMO_ERROR
Explanation:

On an MQGET call, the MQGMO structure is not valid, for one of the following reasons:

  • The StrucId field is not MQGMO_STRUC_ID.

  • The Vfield specifies a value that is not valid or not supported.

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQGMO structure are set correctly.

2187 (X'088B')
MQRC_CICS_BRIDGE_RESTRICTION
Explanation:

It is not permitted to issue MQI calls from user transactions that are run in an MQ/CICS-bridge environment where the bridge exit also issues MQI calls. The MQI call fails. If this occurs in the bridge exit, it will result in a transaction abend. If it occurs in the user transaction, this may result in a transaction abend.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The transaction cannot be run using the MQ/CICS bridge. Refer to the appropriate CICS manual for information about restrictions in the MQ/CICS bridge environment.

2188 (X'088C')
MQRC_STOPPED_BY_CLUSTER_EXIT
Explanation:

An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the cluster workload exit rejected the call.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the cluster workload exit to ensure that it has been written correctly. Determine why it rejected the call and correct the problem.

2189 (X'088D')
MQRC_CLUSTER_RESOLUTION_ERROR
Explanation:

An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the queue definition could not be resolved correctly because a response was required from the repository manager but none was available.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the repository manager is operating and that the queue and channel definitions are correct.

2190 (X'088E')
MQRC_CONVERTED_STRING_TOO_BIG
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, a string in a fixed-length field in the message expanded during data conversion and exceeded the size of the field. When this happens, the queue manager tries discarding trailing blank characters and characters following the first null character in order to make the string fit, but in this case there were insufficient characters that could be discarded.

This reason code can also occur for messages with a format name of MQFMT_IMS_VAR_STRING. When this happens, it indicates that the IMS variable string expanded such that its length exceeded the capacity of 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 variable string.)

The message is returned unconverted, with the CompCode parameter of the MQGET call set to MQCC_WARNING. If the message consists of several parts, each of which is described by its own character-set and encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various character-set and encoding fields always correctly describe the relevant message data.

This reason code does not occur if the string could be made to fit by discarding trailing blank characters.

Completion Code:

MQCC_WARNING

Programmer Response:

Check that the fields in the message contain the correct values, and that the character-set identifiers specified by the sender and receiver of the message are correct. If they are, the 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 converted.

2191 (X'088F')
MQRC_TMC_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQTMC2 structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQTMC_STRUC_ID.

  • The Vfield is not MQTMC_VERSION_2.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2192 (X'0890')
MQRC_PAGESET_FULL
Explanation:

Former name for MQRC_STORAGE_MEDIUM_FULL.

2192 (X'0890')
MQRC_STORAGE_MEDIUM_FULL
Explanation:

An MQI call or command was issued to operate on an object, but the call failed because the external storage medium is full. One of the following applies:

  • A page-set data set is full (nonshared queues only).

  • A coupling-facility structure is full (shared queues only).

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Check which queues contain messages and look for applications that might be filling the queues unintentionally. Be aware that the queue that has caused the page set or coupling-facility structure to become full is not necessarily the queue referenced by the MQI call that returned MQRC_STORAGE_MEDIUM_FULL.

Check that all of the usual server applications are operating correctly and processing the messages on the queues.

If the applications and servers are operating correctly, increase the number of server applications to cope with the message load, or request the system programmer to increase the size of the page-set data sets.

2193 (X'0891')
MQRC_PAGESET_ERROR
Explanation:

An error was encountered with the page set while attempting to access it for a locally defined queue. This could be because the queue is on a page set that does not exist. A console message is issued that tells you the number of the page set in error. For example if the error occurred in the TEST job, and your user identifier is ABCDEFG, the message is: 

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.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the storage class for the queue maps to a valid page set using the DISPLAY Q(xx) STGCLASS, DISPLAY STGCLASS(xx), and DISPLAY USAGE PSID commands. If you are unable to resolve the problem, notify the system programmer who should:

  • Collect the following diagnostic information:

    • A description of the actions that led to the error

    • A listing of the application program being run at the time of the error

    • Details of the page sets defined for use by the queue manager

  • Attempt to re-create the problem, and take a system dump immediately after the error occurs

  • Contact your IBM Support Center

2194 (X'0892')
MQRC_NAME_NOT_VALID_FOR_TYPE
Explanation:

An MQOPEN call was issued to open the queue manager definition, but the ObjectName field in the ObjDesc parameter is not blank.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the ObjectName field is set to blanks.

2195 (X'0893')
MQRC_UNEXPECTED_ERROR
Explanation:

The call was rejected because an unexpected error occurred.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the application's parameter list to ensure, for example, that the correct number of parameters was passed, and that data pointers and storage keys are valid. If the problem cannot be resolved, contact your system programmer.

  • On z/OS, check whether any information has been displayed on the console. If this error occurs on an 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 the problem cannot be resolved, rerun the application with a CSQSNAP DD card (if you have not already got a dump) and send the resulting dump to IBM.

  • On OS/2 and i5/OS, consult the FFST record to obtain more detail about the problem.

  • On HP OpenVMS, Compaq NonStop Kernel, and UNIX systems, consult the FDC file to obtain more detail about the problem.

2196 (X'0894')
MQRC_UNKNOWN_XMIT_Q
Explanation:

On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or the ObjectQMgrName in the object 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 definition is not blank and not the name of a locally-defined queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide.

2197 (X'0895')
MQRC_UNKNOWN_DEF_XMIT_Q
Explanation:

An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. If a local definition of the remote queue was specified, or if a queue-manager alias is being resolved, the XmitQName attribute in the local definition is blank.

Because there is no queue defined with the same name as the destination queue manager, the queue manager has attempted to use the default transmission queue. However, the name defined by the DefXmitQName queue-manager attribute is not the name of a locally-defined queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the queue definitions, or the queue-manager attribute. See the WebSphere MQ Application Programming Guide for more information.

2198 (X'0896')
MQRC_DEF_XMIT_Q_TYPE_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. Either a local definition of the remote queue was specified, or a queue-manager alias was being resolved, but in either case the XmitQName attribute in the local definition is blank.

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 transmission queue. However, although there is a queue defined by the DefXmitQName queue-manager attribute, it is not a local queue.

Completion Code:

MQCC_FAILED

Programmer Response:

Do one of the following:

  • Specify a local transmission queue as the value of the XmitQName attribute in the local definition of the remote queue.

  • Define a local transmission queue with a name that is the same as that of the remote queue manager.

  • Specify a local transmission queue as the value of the DefXmitQName queue-manager attribute.

See the WebSphere MQ Application Programming Guide for more information.

2199 (X'0897')
MQRC_DEF_XMIT_Q_USAGE_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. Either a local definition of the remote queue was specified, or a queue-manager alias was being resolved, but in either case the XmitQName attribute in the local definition is blank.

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 transmission queue. However, the queue defined by the DefXmitQName queue-manager attribute does not have a Usage attribute of MQUS_TRANSMISSION.

Completion Code:

MQCC_FAILED

Programmer Response:

Do one of the following:

  • Specify a local transmission queue as the value of the XmitQName attribute in the local definition of the remote queue.

  • Define a local transmission queue with a name that is the same as that of the remote queue manager.

  • Specify a different local transmission queue as the value of the DefXmitQName queue-manager attribute.

  • Change the Usage attribute of the DefXmitQName queue to MQUS_TRANSMISSION.

See the WebSphere MQ Application Programming Guide for more information.

2201 (X'0899')
MQRC_NAME_IN_USE
Explanation:

An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists. The existing queue is one that is logically deleted, but for which there are still one or more open handles. For more information, see the description of MQCLOSE in the WebSphere MQ Application Programming Guide.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Either ensure that all handles for the previous dynamic queue are closed, or ensure that the name of the new queue is unique; see the description for reason code MQRC_OBJECT_ALREADY_EXISTS.

2202 (X'089A')
MQRC_CONNECTION_QUIESCING
Explanation:

This reason code is issued when the connection to the queue manager is in quiescing state, and an application issues one of the following calls:

  • MQCONN or MQCONNX

  • MQOPEN, with no connection established, or with MQOO_FAIL_IF_QUIESCING included in the Options parameter

  • MQGET, with MQGMO_FAIL_IF_QUIESCING included in the Options field of the GetMsgOpts parameter

  • MQPUT or MQPUT1, with MQPMO_FAIL_IF_QUIESCING included in the Options field of the PutMsgOpts parameter

MQRC_CONNECTION_QUIESCING is also issued by the message channel agent (MCA) when the queue manager is in quiescing state.

Completion Code:

MQCC_FAILED

Programmer Response:

The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out.

2203 (X'089B')
MQRC_CONNECTION_STOPPING
Explanation:

This reason code is issued when the connection to the queue manager is shutting down, and the application issues an MQI call. No more message-queuing calls can be issued. For the MQGET call, if the MQGMO_WAIT option was specified, the wait is canceled.

Note that the MQRC_CONNECTION_BROKEN reason may be returned instead if, as a result of system scheduling factors, the queue manager shuts down before the call completes.

MQRC_CONNECTION_STOPPING is also issued by the message channel agent (MCA) when the queue manager is shutting down.

For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED.

Completion Code:

MQCC_FAILED

Programmer Response:

The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.

2204 (X'089C')
MQRC_ADAPTER_NOT_AVAILABLE
Explanation:

This is issued only for CICS applications, if any call is issued and the CICS adapter (a Task Related User Exit) has been disabled, or has not been enabled.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically.

2206 (X'089E')
MQRC_MSG_ID_ERROR
Explanation:

An MQGET call was issued to retrieve a message using the message identifier as a selection criterion, but the call failed because selection by message identifier is not supported on this queue.

  • On z/OS, the queue is a shared queue, but the IndexType queue attribute does not have an appropriate value:

    • If selection is by message identifier alone, IndexType must have the value MQIT_MSG_ID.

    • If selection is by message identifier and correlation identifier combined, IndexType must have the value MQIT_MSG_ID or MQIT_CORREL_ID.

  • On Compaq NonStop Kernel, a key file is required but has not been defined.

Completion Code:

MQCC_FAILED

Programmer Response:

Do one of the following:

  • Modify the application so that it does not use selection by message identifier: set the MsgId field to MQMI_NONE and do not specify MQMO_MATCH_MSG_ID in MQGMO.

  • On z/OS, change the IndexType queue attribute to MQIT_MSG_ID.

  • On Compaq NonStop Kernel, define a key file.

2207 (X'089F')
MQRC_CORREL_ID_ERROR
Explanation:

An MQGET call was issued to retrieve a message using the correlation identifier as a selection criterion, but the call failed because selection by correlation identifier is not supported on this queue.

  • On z/OS, the queue is a shared queue, but the IndexType queue attribute does not have an appropriate value:

    • If selection is by correlation identifier alone, IndexType must have the value MQIT_CORREL_ID.

    • If selection is by correlation identifier and message identifier combined, IndexType must have the value MQIT_CORREL_ID or MQIT_MSG_ID.

  • On Compaq NonStop Kernel, a key file is required but has not been defined.

Completion Code:

MQCC_FAILED

Programmer Response:

Do one of the following:

  • On z/OS, change the IndexType queue attribute to MQIT_CORREL_ID.

  • On Compaq NonStop Kernel, define a key file.

  • Modify the application so that it does not use selection by correlation identifier: set the CorrelId field to MQCI_NONE and do not specify MQMO_MATCH_CORREL_ID in MQGMO.

2208 (X'08A0')
MQRC_FILE_SYSTEM_ERROR
Explanation:

An unexpected return code was received from the file system, in attempting to perform an operation on a queue.

This reason code occurs only on VSE/ESA.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the file system definition for the queue that was being accessed. For a VSAM file, check that the control interval is large enough for the maximum message length allowed for the queue.

2209 (X'08A1')
MQRC_NO_MSG_LOCKED
Explanation:

An MQGET call was issued with the MQGMO_UNLOCK option, but no message was currently locked.

Completion Code:

MQCC_WARNING

Programmer Response:

Check that a message was locked by an earlier MQGET call with the MQGMO_LOCK option for the same handle, and that no intervening call has caused the message to become unlocked.

2210 (X'08A2')
MQRC_SOAP_DOTNET_ERROR
Explanation:

An exception from the .NET environment (as opposed to WebSphere MQ .NET) has been received and is included as an inner exception.

Completion Code:

MQCC_FAILED

Programmer Response:

Refer to the .NET documentation for details about the inner exception. Follow the corrective action recommended there.

2211 (X'08A3')
MQRC_SOAP_AXIS_ERROR
Explanation:

An exception from the Axis environment has been received and is included as a chained exception.

Completion Code:

MQCC_FAILED

Programmer Response:

Refer to the Axis documentation for details about the chained exception. Follow the corrective action recommended there.

2212 (X'08A4')
MQRC_SOAP_URL_ERROR
Explanation:

The SOAP URL has been specified incorrectly.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the SOAP URL and rerun.

2217 (X'08A9')
MQRC_CONNECTION_NOT_AUTHORIZED
Explanation:

This reason code arises only for CICS applications. For these, connection to the queue manager is done by the adapter. If that connection fails because the CICS subsystem is not authorized to connect to the queue manager, this reason code is issued whenever an application running under that subsystem subsequently issues an MQI call.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the subsystem is authorized to connect to the queue manager.

2218 (X'08AA')
MQRC_MSG_TOO_BIG_FOR_CHANNEL
Explanation:

A message was put to a remote queue, but the message is larger than the maximum message length allowed by the channel. This reason code is returned in the Feedback field in the message descriptor of a report message.

  • On z/OS, this return code is issued only if you are not using CICS for distributed queuing. Otherwise, MQRC_MSG_TOO_BIG_FOR_Q_MGR is issued.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the channel definitions. Increase the maximum message length that the channel can accept, or break the message into several smaller messages.

2219 (X'08AB')
MQRC_CALL_IN_PROGRESS
Explanation:

The application issued an MQI call whilst another MQI call was already being processed for that connection. Only one call per application connection can be processed at a time.

Concurrent calls can arise when an application uses multiple threads, or when an exit is invoked as part of the processing of an MQI call. For example, a data-conversion exit invoked as part of the processing of the MQGET call may try to issue an MQI call.

  • On z/OS, concurrent calls can arise only with batch or IMS applications; an example is when a subtask ends while an MQI call is in progress (for example, an MQGET that is waiting), and there is an end-of-task exit routine that issues another MQI call.

  • On OS/2 and Windows, concurrent calls can also arise if an MQI call is issued in response to a user message while another MQI call is in progress.

  • If the application is using multiple threads with shared handles, MQRC_CALL_IN_PROGRESS occurs when the handle specified on the call is already in use by another thread and MQCNO_HANDLE_SHARE_NO_BLOCK was specified on the MQCONNX call.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that an MQI call cannot be issued while another one is active. Do not issue MQI calls from within a data-conversion exit.

  • On z/OS, if you want to provide a subtask to allow an application that is waiting for a message to arrive to be canceled, wait for the message by using MQGET with MQGMO_SET_SIGNAL, rather than MQGMO_WAIT.

2220 (X'08AC')
MQRC_RMH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQRMH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQRMH_STRUC_ID.

  • The Vfield is not MQRMH_VERSION_1.

  • The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

2222 (X'08AE')
MQRC_Q_MGR_ACTIVE
Explanation:

This condition is detected when a queue manager becomes active.

  • On z/OS, this event is not generated for the first start of a queue manager, only on subsequent restarts.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2223 (X'08AF')
MQRC_Q_MGR_NOT_ACTIVE
Explanation:

This condition is detected when a queue manager is requested to stop or quiesce.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2224 (X'08B0')
MQRC_Q_DEPTH_HIGH
Explanation:

An MQPUT or MQPUT1 call has caused the queue depth to be incremented to or above the limit specified in the QDepthHighLimit attribute.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2225 (X'08B1')
MQRC_Q_DEPTH_LOW
Explanation:

An MQGET call has caused the queue depth to be decremented to or below the limit specified in the QDepthLowLimit attribute.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2226 (X'08B2')
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.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

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.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2228 (X'08B4')
MQRC_RFH_HEADER_FIELD_ERROR
Explanation:

An expected RFH header field was not found or had an invalid value. If this error occurs in a WebSphere MQ SOAP listener, the missing or erroneous field is either the contentType field or the transportVersion field or both.

Completion Code:

MQCC_FAILED

Programmer Response:

If this error occurs in a WebSphere MQ SOAP listener, and you are using the IBM-supplied sender, contact your IBM Support Center. If you are using a bespoke sender, check the associated error message, and that the RFH2 section of the SOAP/MQ request message contains all the mandatory fields, and that these fields have valid values.

2229 (X'08B5')
MQRC_RAS_PROPERTY_ERROR
Explanation:

There is an error related to the RAS property file. The file may be missing, it may be not accessible, or the commands in the file may be incorrect.

Completion Code:

MQCC_FAILED

Programmer Response:

Look at the associated error message, which will explain the error in detail. Correct 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 MQGET, or MQPMO_NO_SYNCPOINT is not specified on MQPUT or MQPUT1 (the default), the call requires a unit of work.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure a TM/MP transaction is available, or issue the MQGET call with the MQGMO_NO_SYNCPOINT option, or the MQPUT or MQPUT1 call with the MQPMO_NO_SYNCPOINT option, which will cause a transaction to be started automatically.

2233 (X'08B9')
MQRC_CHANNEL_AUTO_DEF_OK
Explanation:

This condition is detected when the automatic definition of a channel is successful. The channel is defined by the MCA.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2234 (X'08BA')
MQRC_CHANNEL_AUTO_DEF_ERROR
Explanation:

This condition is detected when the automatic definition of a channel fails; this may be because an error occurred during the definition process, or because the channel automatic-definition exit inhibited the definition. Additional information is returned in the event message indicating the reason for the failure.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING

Programmer Response:

Examine the additional information returned in the event message to determine the reason for the failure.

2235 (X'08BB')
MQRC_CFH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFH structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2236 (X'08BC')
MQRC_CFIL_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIL or MQRCFIL64 structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2237 (X'08BD')
MQRC_CFIN_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIN or MQCFIN64 structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2238 (X'08BE')
MQRC_CFSL_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFSL structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2239 (X'08BF')
MQRC_CFST_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFST structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2241 (X'08C1')
MQRC_INCOMPLETE_GROUP
Explanation:

An operation was attempted on a queue using a queue handle that had an incomplete message group. This reason code can arise in the following situations:

  • On the MQPUT call, when the application specifies MQPMO_LOGICAL_ORDER and attempts to put a message that is not in a group. The completion code is MQCC_FAILED in this case.

  • On the MQPUT call, when the application does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did specify MQPMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case.

  • On the MQGET call, when the application does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did specify MQGMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case.

  • On the MQCLOSE call, when the application attempts to close the queue that has the incomplete message group. The completion code is MQCC_WARNING in this case.

If there is an incomplete logical message as well as an incomplete message group, reason code MQRC_INCOMPLETE_MSG is returned in preference to MQRC_INCOMPLETE_GROUP.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

If this reason code is expected, no corrective action is required. Otherwise, ensure that the MQPUT call for the last message in the group specifies MQMF_LAST_MSG_IN_GROUP.

2242 (X'08C2')
MQRC_INCOMPLETE_MSG
Explanation:

An operation was attempted on a queue using a queue handle that had an incomplete logical message. This reason code can arise in the following situations:

  • On the MQPUT call, when the application specifies MQPMO_LOGICAL_ORDER and attempts to put a message that is not a segment, or that has a setting for the MQMF_LAST_MSG_IN_GROUP flag that is different from the previous message. The completion code is MQCC_FAILED in this case.

  • On the MQPUT call, when the application does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did specify MQPMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case.

  • On the MQGET call, when the application does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did specify MQGMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case.

  • On the MQCLOSE call, when the application attempts to close the queue that has the incomplete logical message. The completion code is MQCC_WARNING in this case.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

If this reason code is expected, no corrective action is required. Otherwise, ensure that the MQPUT call for the last segment specifies MQMF_LAST_SEGMENT.

2243 (X'08C3')
MQRC_INCONSISTENT_CCSIDS
Explanation:

An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option, but the message to be retrieved consists of two or more segments that have differing values for the CodedCharSetId field in MQMD. This can arise when the segments take different paths through the network, and some of those paths have MCA sender conversion enabled. The call succeeds with a completion code of MQCC_WARNING, but only the first few segments that have identical character-set identifiers are returned.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING

Programmer Response:

Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one.

2244 (X'08C4')
MQRC_INCONSISTENT_ENCODINGS
Explanation:

An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option, but the message to be retrieved consists of two or more segments that have differing values for the Encoding field in MQMD. This can arise when the segments take different paths through the network, and some of those paths have MCA sender conversion enabled. The call succeeds with a completion code of MQCC_WARNING, but only the first few segments that have identical encodings are returned.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING

Programmer Response:

Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one.

2245 (X'08C5')
MQRC_INCONSISTENT_UOW
Explanation:

One of the following applies:

  • 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 MQPMO_SYNCPOINT option is not consistent with the current group and segment information retained by the queue manager for the queue handle.

    If the current call specifies MQPMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did, the call succeeds with completion code MQCC_WARNING.

  • An MQGET call was issued to remove from the queue a message in a group or a segment of a logical message, but the value specified or defaulted for the MQGMO_SYNCPOINT option is not consistent with the current group and segment information retained by the queue manager for the queue handle.

    If the current call specifies MQGMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did, the call succeeds with completion code MQCC_WARNING.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING or MQCC_FAILED

Programmer Response:

Modify the application to ensure that the same unit-of-work specification is used for all messages in the group, or all segments of the logical message.

2246 (X'08C6')
MQRC_INVALID_MSG_UNDER_CURSOR
Explanation:

An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option with either MQGMO_MSG_UNDER_CURSOR or 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.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Reposition the browse cursor so that it is located on a message whose Offset field in MQMD is zero. Alternatively, remove the MQGMO_COMPLETE_MSG option.

2247 (X'08C7')
MQRC_MATCH_OPTIONS_ERROR
Explanation:

An MQGET call was issued, but the value of the MatchOptions field in the GetMsgOpts parameter is not valid, for one of the following reasons:

  • An undefined option is specified.

  • All of the following are true:

    • MQGMO_LOGICAL_ORDER is specified.

    • There is a current message group or logical message for the queue handle.

    • Neither MQGMO_BROWSE_MSG_UNDER_CURSOR nor MQGMO_MSG_UNDER_CURSOR is specified.

    • One or more of the MQMO_* options is specified.

    • The values of the fields in the MsgDesc parameter corresponding to the MQMO_* options specified, differ from the values of those fields in the MQMD for the message to be returned next.

  • On z/OS, one or more of the options specified is not valid for the index type of the queue.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that only valid options are specified for the field.

2248 (X'08C8')
MQRC_MDE_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQMDE structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQMDE_STRUC_ID.

  • The Vfield is not MQMDE_VERSION_2.

  • The StrucLength field is not MQMDE_LENGTH_2.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

2249 (X'08C9')
MQRC_MSG_FLAGS_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the MsgFlags field in the message descriptor MQMD contains one or more message flags that are not recognized by the local queue manager. The message flags that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details.

This reason code can also occur in the Feedback field in the MQMD of a report message, or in the Reason field 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.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Do the following:

  • Ensure that the MsgFlags field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Specify MQMF_NONE if no message flags are needed.

  • Ensure that the message flags specified are valid; see the MsgFlags field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid message flags.

  • If multiple message flags are being set by adding the individual message flags together, ensure that the same message flag is not added twice.

  • On z/OS, ensure that the message flags specified are valid for the index type of the queue; see the description of the MsgFlags field in MQMD for further details.

2250 (X'08CA')
MQRC_MSG_SEQ_NUMBER_ERROR
Explanation:

An MQGET, MQPUT, or MQPUT1 call was issued, but the value of the MsgSeqNumber field in the MQMD or MQMDE structure is less than one or greater than 999 999 999.

This error can also occur on the MQPUT call if the MsgSeqNumber field would have become greater than 999 999 999 as a result of the call.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

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

2251 (X'08CB')
MQRC_OFFSET_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the value of the Offset field in the MQMD or MQMDE structure is less than zero or greater than 999 999 999.

This error can also occur on the MQPUT call if the Offset field would have become greater than 999 999 999 as a result of the call.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value in the range 0 through 999 999 999. Do not attempt to create a message segment that would extend beyond an offset of 999 999 999.

2252 (X'08CC')
MQRC_ORIGINAL_LENGTH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued to put a report message that is a segment, but the OriginalLength field in the MQMD or MQMDE structure is either:

  • Less than the length of data in the message, or

  • Less than one (for a segment that is not the last segment), or

  • Less than zero (for a segment that is the last segment)

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value that is greater than zero. Zero is valid only for the last segment.

2253 (X'08CD')
MQRC_SEGMENT_LENGTH_ZERO
Explanation:

An MQPUT or MQPUT1 call was issued to put the first or an intermediate segment of a logical message, but the length of the application message data in the segment (excluding any MQ headers that may be present) is zero. The length must be at least one for the first or intermediate segment.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the application logic to ensure that segments are put with a length of one or greater. Only the last segment of a logical message is permitted to have a length of zero.

2255 (X'08CF')
MQRC_UOW_NOT_AVAILABLE
Explanation:

An MQGET, MQPUT, or MQPUT1 call was issued to get or put a message outside a unit of work, but the options specified on the call required the queue manager to process the call within a unit of work. Because there is already a user-defined unit of work in existence, the queue manager was unable to create a temporary unit of work for the duration of the call.

This reason occurs in the following circumstances:

  • On an MQGET call, when the MQGMO_COMPLETE_MSG option is specified in MQGMO and the logical message to be retrieved is persistent and consists of two or more segments.

  • On an MQPUT or MQPUT1 call, when the MQMF_SEGMENTATION_ALLOWED flag is specified in MQMD and the message requires segmentation.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Issue the MQGET, MQPUT, or MQPUT1 call inside the user-defined unit of work. Alternatively, for the MQPUT or MQPUT1 call, reduce the size of the message so that it does not require segmentation by the queue manager.

2256 (X'08D0')
MQRC_WRONG_GMO_VERSION
Explanation:

An MQGET call was issued specifying options that required an MQGMO with a version number not less than MQGMO_VERSION_2, but the MQGMO supplied did not satisfy this condition.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application to pass a version-2 MQGMO. Check the application logic to ensure that the Vfield in MQGMO has been set to MQGMO_VERSION_2. Alternatively, remove the option that requires the version-2 MQGMO.

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 MQMD_VERSION_2, but the MQMD supplied did not satisfy this condition.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application to pass a version-2 MQMD. Check the application logic to ensure that the Vfield in MQMD has been set to MQMD_VERSION_2. Alternatively, remove the option that requires the version-2 MQMD.

2258 (X'08D2')
MQRC_GROUP_ID_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued to put a distribution-list message that is also a message in a group, a message segment, or has segmentation allowed, but an invalid combination of options and values was specified. All of the following are true:

  • MQPMO_LOGICAL_ORDER is not specified in the Options field in MQPMO.

  • Either there are too few MQPMR records provided by MQPMO, or the GroupId field is not present in the MQPMR records.

  • One or more of the following flags is specified in the MsgFlags field in MQMD or MQMDE:

    • MQMF_SEGMENTATION_ALLOWED

    • MQMF_*_MSG_IN_GROUP

    • MQMF_*_SEGMENT

  • The GroupId field in MQMD or MQMDE is not MQGI_NONE.

This combination of options and values would result in the same group identifier being used for all of the destinations in the distribution list; this is not permitted by the queue manager.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQGI_NONE for the GroupId field in MQMD or MQMDE. Alternatively, if the call is MQPUT specify MQPMO_LOGICAL_ORDER in the Options field in MQPMO.

2259 (X'08D3')
MQRC_INCONSISTENT_BROWSE
Explanation:

An MQGET call was issued with the MQGMO_BROWSE_NEXT option specified, but the specification of the MQGMO_LOGICAL_ORDER 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 MQGMO_LOGICAL_ORDER, or neither call must specify MQGMO_LOGICAL_ORDER.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Add or remove the MQGMO_LOGICAL_ORDER option as appropriate. Alternatively, to switch between logical order and physical order, specify the MQGMO_BROWSE_FIRST option to restart the scan from the beginning of the queue, omitting or specifying MQGMO_LOGICAL_ORDER as required.

2260 (X'08D4')
MQRC_XQH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQXQH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQXQH_STRUC_ID.

  • The Vfield is not MQXQH_VERSION_1.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2261 (X'08D5')
MQRC_SRC_ENV_ERROR
Explanation:

This reason occurs when a channel exit that processes reference messages detects an error in the source environment data of a reference message header (MQRMH). One of the following is true:

  • SrcEnvLength is less than zero.

  • SrcEnvLength is greater than zero, but there is no source environment data.

  • SrcEnvLength is greater than zero, but SrcEnvOffset is negative, zero, or less than the length of the fixed part of MQRMH.

  • SrcEnvLength is greater than zero, but SrcEnvOffset plus SrcEnvLength is greater than StrucLength.

The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the source environment data correctly.

2262 (X'08D6')
MQRC_SRC_NAME_ERROR
Explanation:

This reason occurs when a channel exit that processes reference messages detects an error in the source name data of a reference message header (MQRMH). One of the following is true:

  • SrcNameLength is less than zero.

  • SrcNameLength is greater than zero, but there is no source name data.

  • SrcNameLength is greater than zero, but SrcNameOffset is negative, zero, or less than the length of the fixed part of MQRMH.

  • SrcNameLength is greater than zero, but SrcNameOffset plus SrcNameLength is greater than StrucLength.

The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the source name data correctly.

2263 (X'08D7')
MQRC_DEST_ENV_ERROR
Explanation:

This reason occurs when a channel exit that processes reference messages detects an error in the destination environment data of a reference message header (MQRMH). One of the following is true:

  • DestEnvLength is less than zero.

  • DestEnvLength is greater than zero, but there is no destination environment data.

  • DestEnvLength is greater than zero, but DestEnvOffset is negative, zero, or less than the length of the fixed part of MQRMH.

  • DestEnvLength is greater than zero, but DestEnvOffset plus DestEnvLength is greater than StrucLength.

The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the destination environment data correctly.

2264 (X'08D8')
MQRC_DEST_NAME_ERROR
Explanation:

This reason occurs when a channel exit that processes reference messages detects an error in the destination name data of a reference message header (MQRMH). One of the following is true:

  • DestNameLength is less than zero.

  • DestNameLength is greater than zero, but there is no destination name data.

  • DestNameLength is greater than zero, but DestNameOffset is negative, zero, or less than the length of the fixed part of MQRMH.

  • DestNameLength is greater than zero, but DestNameOffset plus DestNameLength is greater than StrucLength.

The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the destination name data correctly.

2265 (X'08D9')
MQRC_TM_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQTM structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQTM_STRUC_ID.

  • The Vfield is not MQTM_VERSION_1.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2266 (X'08DA')
MQRC_CLUSTER_EXIT_ERROR
Explanation:

An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the cluster workload exit defined by the queue-manager's ClusterWorkloadExit attribute failed unexpectedly or did not respond in time. Subsequent MQOPEN, MQPUT, and MQPUT1 calls for this queue handle are processed as though the ClusterWorkloadExit attribute were blank.

  • On z/OS, a message giving more information about the error is written to the system log, for example message CSQV455E or CSQV456E.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the cluster workload exit to ensure that it has been written correctly.

2267 (X'08DB')
MQRC_CLUSTER_EXIT_LOAD_ERROR
Explanation:

An MQCONN or MQCONNX call was issued to connect to a queue manager, but the queue manager was unable to load the cluster workload exit. Execution continues without the cluster workload exit.

  • 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 though the ClusterWorkloadExit attribute had been blank.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_WARNING

Programmer Response:

Ensure that the queue-manager's ClusterWorkloadExit attribute has the correct value, and that the exit has been installed into the correct location.

2268 (X'08DC')
MQRC_CLUSTER_PUT_INHIBITED
Explanation:

An MQOPEN call with the 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:

  • All instances of the cluster queue are currently put-inhibited (that is, all of the queue instances have the InhibitPut attribute set to MQQA_PUT_INHIBITED).

  • There is no local instance of the queue. (If there is a local instance, the MQOPEN call succeeds, even if the local instance is put-inhibited.)

  • There is no cluster workload exit for the queue, or there is a cluster workload exit but it did not choose a queue instance. (If the cluster workload exit does choose a queue instance, the MQOPEN call succeeds, even if that instance is put-inhibited.)

If the MQOO_BIND_NOT_FIXED option is specified on the MQOPEN call, the call can succeed even if all of the queues in the cluster are put-inhibited. However, a subsequent MQPUT call may fail if all of the queues are still put-inhibited at the time of the MQPUT call.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

If the system design allows put requests to be inhibited for short periods, retry the operation later. If the problem persists, determine why all of the queues in the cluster are put-inhibited.

2269 (X'08DD')
MQRC_CLUSTER_RESOURCE_ERROR
Explanation:

An MQOPEN, MQPUT, or MQPUT1 call was issued for a cluster queue, but an error occurred whilst trying to use a resource required for clustering.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Do the following:

  • Check that the SYSTEM.CLUSTER.* queues are not put inhibited or full.

  • Check the event queues for any events relating to the SYSTEM.CLUSTER.* queues, as these may give guidance as to the nature of the failure.

  • Check that the repository queue manager is available.

  • On z/OS, check the console for signs of the failure, such as full page sets.

2270 (X'08DE')
MQRC_NO_DESTINATIONS_AVAILABLE
Explanation:

An MQPUT or MQPUT1 call was issued to put a message on a cluster queue, but at the time of the call there were no longer any instances of the queue in the cluster. The message therefore could not be sent.

This situation can occur when MQOO_BIND_NOT_FIXED is specified on the MQOPEN call that opens the queue, or MQPUT1 is used to put the message.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the queue definition and queue status to determine why all instances of the queue were removed from the cluster. Correct the problem and rerun the application.

2271 (X'08DF')
MQRC_CONN_TAG_IN_USE
Explanation:

An MQCONNX call was issued specifying one of the MQCNO_*_CONN_TAG_* options, but the call failed because the connection tag specified by ConnTag in MQCNO is in use by an active process or thread, or there is an unresolved unit of work that references this connection tag.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The problem is likely to be transitory. The application should wait a short while and then retry the operation.

2272 (X'08E0')
MQRC_PARTIALLY_CONVERTED
Explanation:

On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, one or more MQ header structures in the message data could not be converted to the specified target character set or encoding. In this situation, the MQ header structures are converted to the queue-manager's character set and encoding, and the application data in the message is converted to the target character set and encoding. On return from the call, the values returned in the various CodedCharSetId and Encoding fields in the MsgDesc parameter and MQ header structures indicate the character set and encoding that apply to each part of the message. The call completes with MQCC_WARNING.

This reason code usually occurs when the specified target character set is one that causes the character strings in the MQ header structures to expand beyond the lengths of their fields. Unicode character set UCS-2 is an example of a character set that causes this to happen.

Completion Code:

MQCC_FAILED

Programmer Response:

If this is an expected situation, no corrective action is required.

If this is an unexpected situation, check that the MQ header structures contain valid data. If they do, specify as the target character set a character set that does not cause the strings to expand.

2273 (X'08E1')
MQRC_CONNECTION_ERROR
Explanation:

An MQCONN or MQCONNX call failed for one of the following reasons:

  • The installation and customization options chosen for WebSphere MQ do not allow connection by the type of application being used.

  • The system parameter module is not at the same release level as the queue manager.

  • The channel initiator is not at the same release level as the queue manager.

  • An internal error was detected by the queue manager.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

None, if the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

Otherwise, if this occurs while starting the channel initiator, ensure that the queue manager and the channel initiator are both at the same release level and that their started task JCL procedures both specify the same level of WebSphere MQ program libraries; if this occurs while starting the queue manager, relinkedit the system parameter module (CSQZPARM) to ensure that it is at the correct level. If the problem persists, contact your IBM support center.

2274 (X'08E2')
MQRC_OPTION_ENVIRONMENT_ERROR
Explanation:

An MQGET call with the MQGMO_MARK_SKIP_BACKOUT option specified was issued from a DB2 Stored Procedure. The call failed because the MQGMO_MARK_SKIP_BACKOUT option cannot be used from a DB2 Stored Procedure.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the MQGMO_MARK_SKIP_BACKOUT option from the MQGET call.

2277 (X'08E5')
MQRC_CD_ERROR
Explanation:

An MQCONNX call was issued to connect to a queue manager, but the MQCD channel definition structure addressed by the ClientConnOffset or ClientConnPtr field in MQCNO contains data that is not valid. Consult the error log for more information about the nature of the error.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that input fields in the MQCD structure are set correctly.

2278 (X'08E6')
MQRC_CLIENT_CONN_ERROR
Explanation:

An MQCONNX call was issued to connect to a queue manager, but the MQCD channel definition structure is not specified correctly. One of the following applies:

  • ClientConnOffset is not zero and ClientConnPtr is not zero and not the null pointer.

  • ClientConnPtr is not a valid pointer.

  • ClientConnPtr or ClientConnOffset points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. It also occurs in Java applications when a client channel definition table is specified to determine the name of the channel, but the table itself cannot be found.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that at least one of ClientConnOffset and ClientConnPtr is zero. Ensure that the field used points to accessible storage. Ensure that the URL of the client channel definition table is correct.

2279 (X'08E7')
MQRC_CHANNEL_STOPPED_BY_USER
Explanation:

This condition is detected when the channel has been stopped by an operator. The reason qualifier identifies the reasons for stopping.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2280 (X'08E8')
MQRC_HCONFIG_ERROR
Explanation:

The configuration handle Hconfig specified on the MQXEP call or MQZEP call is not valid. The MQXEP call is issued by an API exit function; the MQZEP call is issued by an installable service.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the configuration handle that was provided by the queue manager:

  • On the MQXEP call, use the handle passed in the Hconfig field of the MQAXP structure.

  • On the MQZEP call, use the handle passed to the installable service's configuration function on the component initialization call. See the WebSphere MQ System Administration Guide book for information about installable services.

2281 (X'08E9')
MQRC_FUNCTION_ERROR
Explanation:

An MQXEP or MQZEP call was issued, but the function identifier Function specified on the call is not valid, or not supported by the installable service being configured.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Do the following:

  • For the MQXEP call, specify one of the MQXF_* values.

  • For the MQZEP call, specify an MQZID_* value that is valid for the installable service being configured. Refer to the description of the MQZEP call in the WebSphere MQ System Administration Guide book to determine which values are valid.

2282 (X'08EA')
MQRC_CHANNEL_STARTED
Explanation:

One of the following has occurred:

  • An operator has issued a Start Channel command.

  • An instance of a channel has been successfully established. This condition is detected when Initial Data negotiation is complete and resynchronization has been performed where necessary such that message transfer can proceed.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2283 (X'08EB')
MQRC_CHANNEL_STOPPED
Explanation:

This condition is detected when the channel has been stopped. The reason qualifier identifies the reasons for stopping.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2284 (X'08EC')
MQRC_CHANNEL_CONV_ERROR
Explanation:

This condition is detected when a channel is unable to do data conversion and the MQGET call to get a message from the transmission queue resulted in a data conversion error. The conversion reason code identifies the reason for the failure.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2285 (X'08ED')
MQRC_SERVICE_NOT_AVAILABLE
Explanation:

This reason should be returned by an installable service component when the requested action cannot be performed because the required underlying service is not available.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Make the underlying service available.

2286 (X'08EE')
MQRC_INITIALIZATION_FAILED
Explanation:

This reason should be returned by an installable service component when the component is unable to complete initialization successfully.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the error and retry the operation.

2287 (X'08EF')
MQRC_TERMINATION_FAILED
Explanation:

This reason should be returned by an installable service component when the component is unable to complete termination successfully.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the error and retry the operation.

2288 (X'08F0')
MQRC_UNKNOWN_Q_NAME
Explanation:

This reason should be returned by the MQZ_LOOKUP_NAME installable service component when the name specified for the QName parameter is not recognized.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

None. See the WebSphere MQ System Administration Guide book for information about installable services.

2289 (X'08F1')
MQRC_SERVICE_ERROR
Explanation:

This reason should be returned by an installable service component when the component encounters an unexpected error.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the error and retry the operation.

2290 (X'08F2')
MQRC_Q_ALREADY_EXISTS
Explanation:

This reason should be returned by the MQZ_INSERT_NAME installable service component when the queue specified by the QName parameter is already defined to the name service.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

None. See the WebSphere MQ System Administration Guide book for information about installable service.

2291 (X'08F3')
MQRC_USER_ID_NOT_AVAILABLE
Explanation:

This reason should be returned by the MQZ_FIND_USERID installable service component when the user ID cannot be determined.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

None. See the WebSphere MQ System Administration Guide book for information about installable services.

2292 (X'08F4')
MQRC_UNKNOWN_ENTITY
Explanation:

This reason should be returned by the authority installable service component when the name specified by the EntityName parameter is not recognized.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the entity is defined.

2294 (X'08F6')
MQRC_UNKNOWN_REF_OBJECT
Explanation:

This reason should be returned by the MQZ_COPY_ALL_AUTHORITY installable service component when the name specified by the RefObjectName parameter is not recognized.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the reference object is defined. See the WebSphere MQ System Administration Guide book for information about installable services.

2295 (X'08F7')
MQRC_CHANNEL_ACTIVATED
Explanation:

This condition is detected when a channel that has been waiting to become active, and for which a Channel Not Activated event has been generated, is now able to become active because an active slot has been released by another channel.

This event is not generated for a channel that is able to become active without waiting for an active slot to be released.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2296 (X'08F8')
MQRC_CHANNEL_NOT_ACTIVATED
Explanation:

This condition is detected when a channel is required to become active, either because it is starting or because it is about to make another attempt to establish connection with its partner. However, it is unable to do so because the limit on the number of active channels has been reached.

  • On z/OS, the maximum number of active channels is given by the ACTCHL queue manager attribute.

  • In other environments, the maximum number of active channels is given by the MaxActiveChannels parameter in the qm.ini file.

The channel waits until it is able to take over an active slot released when another channel ceases to be active. At that time a Channel Activated event is generated.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2297 (X'08F9')
MQRC_UOW_CANCELED
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 by TM/MP itself (for example, due to the transaction running for too long, or exceeding audit trail sizes), or by the application program issuing an ABORT_TRANSACTION. All updates performed to resources owned by the queue manager are backed out.

Completion Code:

MQCC_FAILED

Programmer Response:

Refer to the operating system's Transaction Management Operations Guide to determine how the Transaction Manager can be tuned to avoid the problem of system limits being exceeded.

2298 (X'08FA')
MQRC_FUNCTION_NOT_SUPPORTED
Explanation:

The function requested is not available in the current environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the call from the application.

2299 (X'08FB')
MQRC_SELECTOR_TYPE_ERROR
Explanation:

The Selector parameter has the wrong data type; it must be of type

Long.

Completion Code:

MQCC_FAILED

Programmer Response:

Declare the Selector parameter as Long.

2300 (X'08FC')
MQRC_COMMAND_TYPE_ERROR
Explanation:

The mqExecute call was issued, but the value of the MQIASY_TYPE data item in the administration bag is not MQCFT_COMMAND.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the MQIASY_TYPE data item in the administration bag has the value MQCFT_COMMAND.

2301 (X'08FD')
MQRC_MULTIPLE_INSTANCE_ERROR
Explanation:

The Selector parameter specifies a system selector (one of the MQIASY_* values), but the value of the ItemIndex parameter is not MQIND_NONE. Only one instance of each system selector can exist in the bag.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQIND_NONE for the ItemIndex parameter.

2302 (X'08FE')
MQRC_SYSTEM_ITEM_NOT_ALTERABLE
Explanation:

A call was issued to modify the value of a system data item in a bag (a data item with one of the MQIASY_* selectors), but the call failed because the data item is one that cannot be altered by the application.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the selector of a user-defined data item, or remove the call.

2303 (X'08FF')
MQRC_BAG_CONVERSION_ERROR
Explanation:

The mqBufferToBag or mqGetBag call was issued, but the data in the buffer or message could not be converted into a bag. This occurs when the data to be converted is not valid PCF.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the logic of the application that created the buffer or message to ensure that the buffer or message contains valid PCF.

If the message contains PCF that is not valid, the message cannot be retrieved using the mqGetBag call:

  • If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call.

  • In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call.

2304 (X'0900')
MQRC_SELECTOR_OUT_OF_RANGE
Explanation:

The Selector parameter has a value that is outside the valid range for the call. If the bag was created with the MQCBO_CHECK_SELECTORS option:

  • For the mqAddInteger call, the value must be within the range MQIA_FIRST through MQIA_LAST.

  • For the mqAddString call, the value must be within the range MQCA_FIRST through MQCA_LAST.

If the bag was not created with the MQCBO_CHECK_SELECTORS option:

  • The value must be zero or greater.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value.

2305 (X'0901')
MQRC_SELECTOR_NOT_UNIQUE
Explanation:

The ItemIndex parameter has the value MQIND_NONE, but the bag contains more than one data item with the selector value specified by the Selector parameter. MQIND_NONE requires that the bag contain only one occurrence of the specified selector.

This reason code also occurs on the mqExecute call when the administration bag contains two or more occurrences of a selector for a required parameter that permits only one occurrence.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the logic of the application that created the bag. If correct, specify for ItemIndex a value that is zero or greater, and add application logic to process all of the occurrences of the selector in the bag.

Review the description of the administration command being issued, and ensure that all required parameters are defined correctly in the bag.

2306 (X'0902')
MQRC_INDEX_NOT_PRESENT
Explanation:

The specified index is not present:

  • For a bag, this means that the bag contains one or more data items that have the selector value specified by the Selector parameter, but none of them has the index value specified by the ItemIndex parameter. The data item identified by the Selector and ItemIndex parameters must exist in the bag.

  • For a namelist, this means that the index parameter value is too large, and outside the range of valid values.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the index of a data item that does exist in the bag or namelist. Use the mqCountItems call to determine the number of data items with the specified selector that exist in the bag, or the nameCount method to determine the number of names in the namelist.

2307 (X'0903')
MQRC_STRING_ERROR
Explanation:

The String parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2308 (X'0904')
MQRC_ENCODING_NOT_SUPPORTED
Explanation:

The Encoding field in the message descriptor MQMD contains a value that is not supported:

  • For the mqPutBag call, the field in error resides in the MsgDesc parameter of the call.

  • For the mqGetBag call, the field in error resides in:

    • The MsgDesc parameter of the call if the MQGMO_CONVERT option was specified.

    • The message descriptor of the message about to be retrieved if MQGMO_CONVERT was not specified.

Completion Code:

MQCC_FAILED

Programmer Response:

The value must be MQENC_NATIVE.

If the value of the Encoding field in the message is not valid, the message cannot be retrieved using the mqGetBag call:

  • If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call.

  • In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call.

2309 (X'0905')
MQRC_SELECTOR_NOT_PRESENT
Explanation:

The Selector parameter specifies a selector that does not exist in the bag.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a selector that does exist in the bag.

2310 (X'0906')
MQRC_OUT_SELECTOR_ERROR
Explanation:

The OutSelector parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2311 (X'0907')
MQRC_STRING_TRUNCATED
Explanation:

The string returned by the call is too long to fit in the buffer provided. The string has been truncated to fit in the buffer.

Completion Code:

MQCC_FAILED

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 the size of the buffer required to accommodate the string without truncation.

2312 (X'0908')
MQRC_SELECTOR_WRONG_TYPE
Explanation:

A data item with the specified selector exists in the bag, but has a data type that conflicts with the data type implied by the call being used. For example, the data item might have an integer data type, but the call being used might be mqSetString, which implies a character data type.

This reason code also occurs on the mqBagToBuffer, mqExecute, and mqPutBag calls when mqAddString or mqSetString was used to add the MQIACF_INQUIRY data item to the bag.

Completion Code:

MQCC_FAILED

Programmer Response:

For the mqSetInteger and mqSetString calls, specify MQIND_ALL for the ItemIndex parameter to delete from the bag all existing occurrences of the specified selector before creating the new occurrence with the required data type.

For the mqInquireBag, mqInquireInteger, and mqInquireString calls, use the mqInquireItemInfo call to determine the data type of the item with the specified selector, and then use the appropriate call to determine the value of the data item.

For the mqBagToBuffer, mqExecute, and mqPutBag calls, ensure that the MQIACF_INQUIRY data item is added to the bag using the mqAddInteger or mqSetInteger calls.

2313 (X'0909')
MQRC_INCONSISTENT_ITEM_TYPE
Explanation:

The mqAddInteger or mqAddString call was issued to add another occurrence of the specified selector to the bag, but the data type of this occurrence differed from the data type of the first occurrence.

This reason can also occur on the mqBufferToBag and mqGetBag calls, where it indicates that the PCF in the buffer or message contains a selector that occurs more than once but with inconsistent data types.

Completion Code:

MQCC_FAILED

Programmer Response:

For the mqAddInteger and mqAddString calls, use the call appropriate to the data type of the first occurrence of that selector in the bag.

For the mqBufferToBag and mqGetBag calls, check the logic of the application that created the buffer or sent the message to ensure that multiple-occurrence selectors occur with only one data type. A message that contains a mixture of data types for a selector cannot be retrieved using the mqGetBag call:

  • If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call.

  • In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call.

2314 (X'090A')
MQRC_INDEX_ERROR
Explanation:

An index parameter to a call or method has a value that is not valid. The value must be zero or greater. For bag calls, certain MQIND_* values can also be specified:

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value.

2315 (X'090B')
MQRC_SYSTEM_BAG_NOT_ALTERABLE
Explanation:

A call was issued to add a data item to a bag, modify the value of an existing data item in a bag, or retrieve a message into a bag, but the call failed because the bag is one that had been created by the system as a result of a previous mqExecute call. System bags cannot be modified by the application.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the handle of a bag created by the application, or remove 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 valid. The value is either less than zero, or greater than the number of user-defined data items in the bag.

This reason also occurs on the mqCountItems call if the parameter pointer is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid value. Use the mqCountItems call to determine the number of user-defined data items in the bag.

2317 (X'090D')
MQRC_FORMAT_NOT_SUPPORTED
Explanation:

The Format field in the message descriptor MQMD contains a value that is not supported:

  • In an administration message, the format value must be one of the following: MQFMT_ADMIN, MQFMT_EVENT, MQFMT_PCF. For the mqPutBag call, the field in error resides in the MsgDesc parameter of the call. For the mqGetBag call, the field in error resides in the message descriptor of the message about to be retrieved.

  • On z/OS, the message was put to the command input queue with a format value of MQFMT_ADMIN, but the version of MQ being used does not support that format for commands.

Completion Code:

MQCC_FAILED

Programmer Response:

If the error occurred when putting a message, correct the format value.

If the error occurred when getting a message, the message cannot be retrieved using the mqGetBag call:

  • If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call.

  • In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call.

2318 (X'090E')
MQRC_SELECTOR_NOT_SUPPORTED
Explanation:

The Selector parameter specifies a value that is a system selector (a value that is negative), but the system selector is not one that is supported by the call.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a selector value that is supported.

2319 (X'090F')
MQRC_ITEM_VALUE_ERROR
Explanation:

The mqInquireBag or mqInquireInteger call was issued, but the ItemValue parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2320 (X'0910')
MQRC_HBAG_ERROR
Explanation:

A call was issued that has a parameter that is a bag handle, but the handle is not valid. For output parameters, this reason also occurs if the parameter pointer is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2321 (X'0911')
MQRC_PARAMETER_MISSING
Explanation:

An administration message requires a parameter that is not present in the administration bag. This reason code occurs only for bags created with the MQCBO_ADMIN_BAG or MQCBO_REORDER_AS_REQUIRED options.

Completion Code:

MQCC_FAILED

Programmer Response:

Review the description of the administration command being issued, and ensure that all required parameters are present in the bag.

2322 (X'0912')
MQRC_CMD_SERVER_NOT_AVAILABLE
Explanation:

The command server that processes administration commands is not available.

Completion Code:

MQCC_FAILED

Programmer Response:

Start the command server.

2323 (X'0913')
MQRC_STRING_LENGTH_ERROR
Explanation:

The StringLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2324 (X'0914')
MQRC_INQUIRY_COMMAND_ERROR
Explanation:

The mqAddInquiry call was used previously to add attribute selectors to the bag, but the command code to be used for the mqBagToBuffer, mqExecute, or mqPutBag call is not recognized. As a result, the correct PCF message cannot be generated.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the mqAddInquiry calls and use instead the mqAddInteger call with the appropriate MQIACF_*_ATTRS or MQIACH_*_ATTRS selectors.

2325 (X'0915')
MQRC_NESTED_BAG_NOT_SUPPORTED
Explanation:

A bag that is input to the call contains nested bags. Nested bags are supported only for bags that are output from the call.

Completion Code:

MQCC_FAILED

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 of a bag that has the wrong type for the call. The bag must be an administration bag, that is, it must be created with the MQCBO_ADMIN_BAG option specified on the mqCreateBag call.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the MQCBO_ADMIN_BAG option when the bag is created.

2327 (X'0917')
MQRC_ITEM_TYPE_ERROR
Explanation:

The mqInquireItemInfo call was issued, but the ItemType parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2328 (X'0918')
MQRC_SYSTEM_BAG_NOT_DELETABLE
Explanation:

An mqDeleteBag call was issued to delete a bag, but the call failed because the bag is one that had been created by the system as a result of a previous mqExecute call. System bags cannot be deleted by the application.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the handle of a bag created by the application, or remove the call.

2329 (X'0919')
MQRC_SYSTEM_ITEM_NOT_DELETABLE
Explanation:

A call was issued to delete a system data item from a bag (a data item with one of the MQIASY_* selectors), but the call failed because the data item is one that cannot be deleted by the application.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify the selector of a user-defined data item, or remove the call.

2330 (X'091A')
MQRC_CODED_CHAR_SET_ID_ERROR
Explanation:

The CodedCharSetId parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2331 (X'091B')
MQRC_MSG_TOKEN_ERROR
Explanation:

An MQGET call was issued to retrieve a message using the message token as a selection criterion, but the options specified are not valid, because MQMO_MATCH_MSG_TOKEN was specified with either MQGMO_WAIT or MQGMO_SET_SIGNAL.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the MQMO_MATCH_MSG_TOKEN option from the MQGET call.

2332 (X'091C')
MQRC_MISSING_WIH
Explanation:

An MQPUT or MQPUT1 call was issued to put a message on a queue whose IndexType attribute had the value MQIT_MSG_TOKEN, but the Format field in the MQMD was not MQFMT_WORK_INFO_HEADER. This error occurs only when the message arrives at the destination queue manager.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application to ensure that it places an MQWIH structure at the start of the message data, and sets the Format field in the MQMD to MQFMT_WORK_INFO_HEADER. Alternatively, change the ApplType attribute of the 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.

2333 (X'091D')
MQRC_WIH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQWIH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQWIH_STRUC_ID.

  • The Vfield is not MQWIH_VERSION_1.

  • The StrucLength field is not MQWIH_LENGTH_1.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

  • On z/OS, this error also occurs when the IndexType attribute of the queue is MQIT_MSG_TOKEN, but the message data does not begin with an MQWIH structure.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

  • On z/OS, if the queue has an IndexType of MQIT_MSG_TOKEN, ensure that the message data begins with an MQWIH structure.

2334 (X'091E')
MQRC_RFH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQRFH or MQRFH2 structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQRFH_STRUC_ID.

  • The Vfield is not MQRFH_VERSION_1 (MQRFH), or MQRFH_VERSION_2 (MQRFH2).

  • The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field).

2335 (X'091F')
MQRC_RFH_STRING_ERROR
Explanation:

The contents of the NameValueString field in the MQRFH structure are not valid. NameValueString must adhere to the following rules:

  • The string must consist of zero or more name/value pairs separated from each other by one or more blanks; the blanks are not significant.

  • If a name or value contains blanks that are significant, the name or value must be enclosed in double-quote characters.

  • If a name or value itself contains one or more double-quote characters, the name or value must be enclosed in double-quote characters, and each embedded double-quote character must be doubled.

  • A name or value can contain any characters other than the null, which acts as a delimiter. The null and characters following it, up to the defined length of NameValueString, are ignored.

The following is a valid NameValueString: 

Famous_Words "The program displayed ""Hello World"""
Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application that generated the message to ensure that it places in the NameValueString field data that adheres to the rules listed above. Check that the StrucLength field is set to the correct value.

2336 (X'0920')
MQRC_RFH_COMMAND_ERROR
Explanation:

The message contains an MQRFH structure, but the command name contained in the NameValueString field is not valid.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application that generated the message to ensure that it places in the NameValueString field a command name that is valid.

2337 (X'0921')
MQRC_RFH_PARM_ERROR
Explanation:

The message contains an MQRFH structure, but a parameter name contained in the NameValueString field is not valid for the command specified.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application that generated the message to ensure that it places in the NameValueString field only parameters that are valid for the specified command.

2338 (X'0922')
MQRC_RFH_DUPLICATE_PARM
Explanation:

The message contains an MQRFH structure, but a parameter occurs more than once in the NameValueString field when only one occurrence is valid for the specified command.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application that generated the message to ensure that it places in the NameValueString field only one occurrence of the parameter.

2339 (X'0923')
MQRC_RFH_PARM_MISSING
Explanation:

The message contains an MQRFH structure, but the command specified in the NameValueString field requires a parameter that is not present.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application that generated the message to ensure that it places in the NameValueString field all parameters that are required for the specified command.

2340 (X'0924')
MQRC_CHAR_CONVERSION_ERROR
Explanation:

This reason code is returned by the Java MQQueueManager constructor when a required character-set conversion is not available. The conversion required is between two nonUnicode character sets.

This reason code occurs in the following environment: MQ Classes for Java on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the National Language Resources component of the OS/390 Language Environment is installed, and that conversion between the IBM-1047 and ISO8859-1 character sets is available.

2341 (X'0925')
MQRC_UCS2_CONVERSION_ERROR
Explanation:

This reason code is returned by the Java MQQueueManager constructor when a required character-set conversion is not available. The conversion required is between the UCS-2 Unicode character set and the queue-manager's character set. 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: MQ Classes for Java on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the relevant Unicode conversion tables are installed, and that they are available to the z/OS Language Environment. The conversion tables should be installed as part of the z/OS C/C++ optional feature. Refer to the z/OS C/C++ Programming Guide for more information about enabling UCS-2 conversions.

2342 (X'0926')
MQRC_DB2_NOT_AVAILABLE
Explanation:

An MQOPEN, MQPUT1, or MQSET call, or a command, was issued to access a shared queue, but it failed because the queue manager is not connected to a DB2 subsystem. As a result, the queue manager is unable to access the object definition relating to the shared queue.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Configure the DB2 subsystem so that the queue manager can connect to it.

2343 (X'0927')
MQRC_OBJECT_NOT_UNIQUE
Explanation:

An MQOPEN or MQPUT1 call, or a command, was issued to access a queue, but the call failed because the queue specified cannot be resolved unambiguously. There exists a shared queue with the specified name, and a nonshared queue with the same name.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

One of the queues must be deleted. If the queue to be deleted contains messages, use the MQSC command MOVE QLOCAL to move the messages to a different queue, and then use the command DELETE QLOCAL to delete the queue.

2344 (X'0928')
MQRC_CONN_TAG_NOT_RELEASED
Explanation:

An MQDISC call was issued when there was a unit of work outstanding for the connection handle. For CICS, IMS, and RRS connections, the MQDISC call does not commit or back out the unit of work. As a result, the connection tag associated with the unit of work is not yet available for reuse. The tag becomes available for reuse only when processing of the unit of work has been completed.

This reason code occurs only on z/OS.

Completion Code:

MQCC_WARNING

Programmer Response:

Do not try to reuse the connection tag immediately. If the MQCONNX call is issued with the same connection tag, and that tag is still in use, the call fails with reason code MQRC_CONN_TAG_IN_USE.

2345 (X'0929')
MQRC_CF_NOT_AVAILABLE
Explanation:

An MQOPEN or MQPUT1 call was issued to access a shared queue, but the allocation of the coupling-facility structure specified in the queue definition failed because there is no suitable coupling facility to hold the structure, based on the preference list in the active CFRM policy.

This reason code can also occur when the API call requires a capability that is not supported by the CF level defined in the coupling-facility structure object. For example, this reason code is returned by an attempt 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.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Make available a coupling facility with one of the names specified in the CFRM policy, or modify the CFRM policy to specify the names of coupling facilities that are available.

2346 (X'092A')
MQRC_CF_STRUC_IN_USE
Explanation:

An MQI call or command was issued to operate on a shared queue, but the call failed because the coupling-facility structure specified in the queue definition is temporarily unavailable. The coupling-facility structure can be unavailable because a structure dump is in progress, or new connectors to the structure are currently inhibited, or an existing connector to the structure failed or disconnected abnormally and clean-up is not yet complete.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The problem is temporary; wait a short while and then retry the operation.

2347 (X'092B')
MQRC_CF_STRUC_LIST_HDR_IN_USE
Explanation:

An MQGET, MQOPEN, MQPUT1, or MQSET call was issued to access a shared queue, but the call failed because the list header associated with the coupling-facility structure specified in the queue definition is temporarily unavailable. The list header is unavailable because it is undergoing recovery processing.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The problem is temporary; wait a short while and then retry the operation.

2348 (X'092C')
MQRC_CF_STRUC_AUTH_FAILED
Explanation:

An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the user is not authorized to access the coupling-facility structure specified in the queue definition.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the security profile for the user identifier used by the application so that the application can access the coupling-facility structure specified in the queue definition.

2349 (X'092D')
MQRC_CF_STRUC_ERROR
Explanation:

An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the coupling-facility structure name specified in the queue definition is not defined in the CFRM data set, or is not the name of a list structure.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the queue definition to specify the name of a coupling-facility list structure that is defined in the CFRM data set.

2350 (X'092E')
MQRC_CONN_TAG_NOT_USABLE
Explanation:

An MQCONNX call was issued specifying one of the MQCNO_*_CONN_TAG_* options, but the call failed because the connection tag specified by ConnTag in MQCNO is being used by the queue manager for recovery processing, and this processing is delayed pending recovery of the coupling facility.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The problem is likely to persist. Consult the system programmer to ascertain the cause of the problem.

2351 (X'092F')
MQRC_GLOBAL_UOW_CONFLICT
Explanation:

An attempt was made to use inside a global unit of work a connection handle that is participating in another global unit of work. This can occur when an application passes connection handles between objects where the objects are involved in different DTC transactions. 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 does not occur for nontransactional MQI calls.

This reason code occurs only on Windows and z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work.

2352 (X'0930')
MQRC_LOCAL_UOW_CONFLICT
Explanation:

An attempt was made to use inside a global unit of work a connection handle that is participating in a queue-manager coordinated local unit of work. This can occur when an application passes connection handles between objects where one object is involved in a DTC transaction and the other is not.

This error does not occur for nontransactional MQI calls.

This reason code occurs only on Windows and z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work.

2353 (X'0931')
MQRC_HANDLE_IN_USE_FOR_UOW
Explanation:

An attempt was made to use outside a unit of work a connection handle that is participating in a global unit of work.

This error can occur when an application passes connection handles between objects where one object is involved in a DTC transaction and the other is not. 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 created and associated with the transaction loses that association whilst the object is running. The association is lost when DTC terminates the transaction independently of MTS. This might be because the transaction timed out, or because DTC shut down.

This error does not occur for nontransactional MQI calls.

This reason code occurs only on Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that objects executing within different units of work do not try to use the same connection handle.

2354 (X'0932')
MQRC_UOW_ENLISTMENT_ERROR
Explanation:

This reason code can occur for a variety of reasons. The most likely reason is that an object created by a DTC transaction does not issue a transactional MQI call until after the DTC transaction has timed out. (If the DTC transaction times out after a transactional MQI call has been issued, reason code MQRC_HANDLE_IN_USE_FOR_UOW is returned by the failing MQI call.)

Another cause of MQRC_UOW_ENLISTMENT_ERROR is incorrect installation; Windows NT Service pack must be installed after the Windows NT Option pack.

This reason code occurs only on Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the DTC "Transaction timeout" value. If necessary, verify the NT installation order.

2355 (X'0933')
MQRC_UOW_MIX_NOT_SUPPORTED
Explanation:

The mixture of calls used by the application to perform operations within a unit of work is not supported. In particular, it is not possible to mix within the same process a local unit of work coordinated by the queue manager with a global unit of work coordinated by DTC (Distributed Transaction Coordinator).

An application may cause this mixture to arise if some objects in a package are coordinated by DTC and others are not. It can also occur if transactional MQI calls from an MTS client are mixed with transactional MQI calls from a library package transactional MTS object.

No problem arises if all transactional MQI calls originate from transactional MTS objects, or all transactional MQI calls originate from nontransactional MTS objects. But when a mixture of styles is used, the first style used fixes the style for the unit of work, and subsequent attempts to use the other style within the process fail with reason code MQRC_UOW_MIX_NOT_SUPPORTED.

When an application is run twice, scheduling factors in the operating system mean that it is possible for the queue-manager-coordinated transactional calls to fail in one run, and for the DTC-coordinated transactional calls to fail in the other run.

This reason code occurs only on Windows when running a version of the queue manager prior to version 5.2.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that objects executing within different units of work do not try to use the same connection handle.

2356 (X'0934')
MQRC_WXP_ERROR
Explanation:

An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the workload exit parameter structure ExitParms is not valid, for one of the following reasons:

  • The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

  • The StrucId field is not MQWXP_STRUC_ID.

  • The Vfield is not MQWXP_VERSION_2.

  • The CacheContext field does not contain the value passed to the exit by the queue manager.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the parameter specified for ExitParms is the MQWXP structure that was passed to the exit when the exit was invoked.

2357 (X'0935')
MQRC_CURRENT_RECORD_ERROR
Explanation:

An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the address specified by the CurrentRecord parameter is not the address of a valid record. CurrentRecord must be the address of a destination record (MQWDR), queue record (MQWQR), or cluster record (MQWCR) residing within the cluster cache.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the cluster workload exit passes the address of a valid record residing in the cluster cache.

2358 (X'0936')
MQRC_NEXT_OFFSET_ERROR
Explanation:

An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the offset specified by the NextOffset parameter is not valid. NextOffset must be the value of one of the following fields:

  • ChannelDefOffset field in MQWDR

  • ClusterRecOffset field in MQWDR

  • ClusterRecOffset field in MQWQR

  • ClusterRecOffset field in MQWCR

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the value specified for the NextOffset parameter is the value of one of the fields listed above.

2359 (X'0937')
MQRC_NO_RECORD_AVAILABLE
Explanation:

An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the current record is the last record in the chain.

Completion Code:

MQCC_FAILED

Programmer Response:

None.

2360 (X'0938')
MQRC_OBJECT_LEVEL_INCOMPATIBLE
Explanation:

An MQOPEN or MQPUT1 call, or a command, was issued, but the definition of the object to be accessed is not compatible with the queue manager to which the application has connected. The object definition was created or modified by a different version of the queue manager.

If the object to be accessed is a queue, the incompatible object definition could be the object specified, or one of the object definitions used to resolve the specified object (for example, the base queue to which an alias queue resolves, or the transmission queue to which a remote queue or queue-manager alias resolves).

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

The application must be run on a queue manager that is compatible with the object definition. Refer to the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about compatibility and migration between different versions of the queue manager.

2361 (X'0939')
MQRC_NEXT_RECORD_ERROR
Explanation:

An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the address specified for the NextRecord parameter is either null, not valid, or the address of read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid address for the NextRecord parameter.

2362 (X'093A')
MQRC_BACKOUT_THRESHOLD_REACHED
Explanation:

This reason code occurs only in the Reason field in an MQDLH structure, or in the Feedback field in the MQMD of a report message.

A JMS ConnectionConsumer found a message that exceeds the queue's backout threshold. The queue does not have a backout requeue queue defined, so the message was processed as specified by the disposition options in the Report field in the MQMD of the message.

On queue managers that do not support the BackoutThreshold and BackoutRequeueQName queue attributes, JMS ConnectionConsumer uses a value of 20 for the backout threshold. When the BackoutCount of a message reaches this threshold, the message is processed as specified by the disposition options.

If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH.

Completion Code:

None

Programmer Response:

Investigate the cause of the backout count being greater than the threshold. To correct this, define the backout queue for the queue concerned.

2363 (X'093B')
MQRC_MSG_NOT_MATCHED
Explanation:

This reason code occurs only in the Reason field in an MQDLH structure, or in the Feedback field in the MQMD of a report message.

While performing Point-to-Point messaging, JMS encountered a message matching none of the selectors of ConnectionConsumers monitoring the queue. To maintain performance, the message was processed as specified by the disposition options in the Report field in the MQMD of the message.

If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH.

Completion Code:

None

Programmer Response:

To correct this, ensure that the ConnectionConsumers monitoring the queue provide a complete set of selectors. Alternatively, set the QueueConnectionFactory to retain messages.

2364 (X'093C')
MQRC_JMS_FORMAT_ERROR
Explanation:

This reason code is generated when JMS encounters a message that it is unable to parse. If such a message is encountered by a JMS ConnectionConsumer, the message is processed as specified by the disposition options in the Report field in the MQMD of the message.

If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH.

Completion Code:

None

Programmer Response:

Investigate the origin of the message.

2365 (X'093D')
MQRC_SEGMENTS_NOT_SUPPORTED
Explanation:

An MQPUT call was issued to put a segment of a logical message, but the queue on which the message is to be placed has an IndexType of MQIT_GROUP_ID. Message segments cannot be placed on queues with this index type.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

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 of the queue.

2366 (X'093E')
MQRC_WRONG_CF_LEVEL
Explanation:

An MQOPEN or MQPUT1 call was issued specifying a shared queue, but the queue requires a coupling-facility structure with a different level of capability.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the coupling-facility structure used for the queue is at the level required to support the capabilities that the queue provides.

2367 (X'093F')
MQRC_CONFIG_CREATE_OBJECT
Explanation:

This condition is detected when an object is created.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2368 (X'0940')
MQRC_CONFIG_CHANGE_OBJECT
Explanation:

This condition is detected when an object is changed.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2369 (X'0941')
MQRC_CONFIG_DELETE_OBJECT
Explanation:

This condition is detected when an object is deleted.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2370 (X'0942')
MQRC_CONFIG_REFRESH_OBJECT
Explanation:

This condition is detected when an object is refreshed.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2371 (X'0943')
MQRC_CHANNEL_SSL_ERROR
Explanation:

This condition is detected when a connection cannot be established due to an SSL key-exchange or authentication failure.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2373 (X'0945')
MQRC_CF_STRUC_FAILED
Explanation:

An MQI call or command was issued to access a shared queue, but the call failed because the coupling-facility structure used for the shared queue had failed.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Report the problem to the operator or administrator, who should use the MQSC command RECOVER CFSTRUCT to initiate recovery of the coupling-facility structure

2374 (X'0946')
MQRC_API_EXIT_ERROR
Explanation:

An API exit function returned an invalid response code, or failed in some other way.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the exit logic to ensure that the exit is returning valid values in the ExitResponse and ExitResponse2 fields of the MQAXP structure. Consult the FFST record to see if it contains more detail about the problem.

2375 (X'0947')
MQRC_API_EXIT_INIT_ERROR
Explanation:

The queue manager encountered an error while attempting to initialize the execution environment for an API exit function.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Consult the FFST record to obtain more detail about the problem.

2376 (X'0948')
MQRC_API_EXIT_TERM_ERROR
Explanation:

The queue manager encountered an error while attempting to terminate the execution environment for an API exit function.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Consult the FFST record to obtain more detail about the problem.

2377 (X'0949')
MQRC_EXIT_REASON_ERROR
Explanation:

An MQXEP call was issued by an API exit function, but the value specified for the ExitReason parameter is either not valid, or not supported for the specified function identifier Function.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the exit function to specify a value for ExitReason that is valid for the specified value of Function.

2378 (X'094A')
MQRC_RESERVED_VALUE_ERROR
Explanation:

An MQXEP call was issued by an API exit function, but the value specified for the Reserved parameter is not valid. The value must be the null pointer.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the exit to specify the null pointer as the value of the Reserved parameter.

2379 (X'094B')
MQRC_NO_DATA_AVAILABLE
Explanation:

This reason should be returned by the MQZ_ENUMERATE_AUTHORITY_DATA installable service component when there is no more authority data to return to the invoker of the service component.

  • On z/OS, this reason code does not occur.

Completion Code:

MQCC_FAILED

Programmer Response:

None.

2380 (X'094C')
MQRC_SCO_ERROR
Explanation:

On an MQCONNX call, the MQSCO structure is not valid for one of the following reasons:

  • The StrucId field is not MQSCO_STRUC_ID.

  • The Vfield is not MQSCO_VERSION_1.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the definition of the MQSCO structure.

2381 (X'094D')
MQRC_KEY_REPOSITORY_ERROR
Explanation:

On an MQCONN or MQCONNX call, the location of the key repository is either not specified, not valid, or results in an error when used to access the key repository. The location of the key repository is specified by one of the following:

  • The value of the MQSSLKEYR environment variable (MQCONN or MQCONNX call), or

  • The value of the KeyRepository field in the MQSCO structure (MQCONNX call only).

For the MQCONNX call, if both MQSSLKEYR and KeyRepository are specified, the latter is used.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid location for the key repository.

2382 (X'094E')
MQRC_CRYPTO_HARDWARE_ERROR
Explanation:

On an MQCONN or MQCONNX call, the configuration string for the cryptographic hardware is not valid, or results in an error when used to configure the cryptographic hardware. The configuration string is specified by one of the following:

  • The value of the MQSSLCRYP environment variable (MQCONN or MQCONNX call), or

  • The value of the CryptoHardware field in the MQSCO structure (MQCONNX call only).

For the MQCONNX call, if both MQSSLCRYP and CryptoHardware are specified, the latter is used.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid configuration string for the cryptographic hardware.

2383 (X'094F')
MQRC_AUTH_INFO_REC_COUNT_ERROR
Explanation:

On an MQCONNX call, the AuthInfoRecCount field in the MQSCO structure specifies a value that is less than zero.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value for AuthInfoRecCount that is zero or greater.

2384 (X'0950')
MQRC_AUTH_INFO_REC_ERROR
Explanation:

On an MQCONNX call, the MQSCO structure does not specify the address of the MQAIR records correctly. One of the following applies:

  • AuthInfoRecCount is greater than zero, but AuthInfoRecOffset is zero and AuthInfoRecPtr is the null pointer.

  • AuthInfoRecOffset is not zero and AuthInfoRecPtr is not the null pointer.

  • AuthInfoRecPtr is not a valid pointer.

  • AuthInfoRecOffset or AuthInfoRecPtr points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that one of AuthInfoRecOffset or AuthInfoRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage.

2385 (X'0951')
MQRC_AIR_ERROR
Explanation:

On an MQCONNX call, an MQAIR record is not valid for one of the following reasons:

  • The StrucId field is not MQAIR_STRUC_ID.

  • The Vfield is not MQAIR_VERSION_1.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the definition of the MQAIR record.

2386 (X'0952')
MQRC_AUTH_INFO_TYPE_ERROR
Explanation:

On an MQCONNX call, the AuthInfoType field in an MQAIR record specifies a value that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify MQAIT_CRL_LDAP for AuthInfoType.

2387 (X'0953')
MQRC_AUTH_INFO_CONN_NAME_ERROR
Explanation:

On an MQCONNX call, the AuthInfoConnName field in an MQAIR record specifies a value that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a valid connection name.

2388 (X'0954')
MQRC_LDAP_USER_NAME_ERROR
Explanation:

On an MQCONNX call, an LDAP user name in an MQAIR record is not specified correctly. One of the following applies:

  • LDAPUserNameLength is greater than zero, but LDAPUserNameOffset is zero and LDAPUserNamePtr is the null pointer.

  • LDAPUserNameOffset is nonzero and LDAPUserNamePtr is not the null pointer.

  • LDAPUserNamePtr is not a valid pointer.

  • LDAPUserNameOffset or LDAPUserNamePtr points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that one of LDAPUserNameOffset or LDAPUserNamePtr is zero and the other nonzero. Ensure that the field used points to accessible storage.

2389 (X'0955')
MQRC_LDAP_USER_NAME_LENGTH_ERR
Explanation:

On an MQCONNX call, the LDAPUserNameLength field in an MQAIR record specifies a value that is less than zero.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value for LDAPUserNameLength that is zero or greater.

2390 (X'0956')
MQRC_LDAP_PASSWORD_ERROR
Explanation:

On an MQCONNX call, the LDAPPassword field in an MQAIR record specifies a value when no value is allowed.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Specify a value that is blank or null.

2391 (X'0957')
MQRC_SSL_ALREADY_INITIALIZED
Explanation:

An MQCONN or MQCONNX call was issued with SSL configuration options specified, but the SSL environment had already been initialized. The connection to the queue manager completed successfully, but the SSL configuration options specified on the call were ignored; the existing SSL environment was used instead.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_WARNING

Programmer Response:

If the application must be run 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 terminate the application. Alternatively run the application later when the SSL environment has not been initialized.

2392 (X'0958')
MQRC_SSL_CONFIG_ERROR
Explanation:

On an MQCONNX call, the MQCNO structure does not specify the MQSCO structure correctly. One of the following applies:

  • SSLConfigOffset is nonzero and SSLConfigPtr is not the null pointer.

  • SSLConfigPtr is not a valid pointer.

  • SSLConfigOffset or SSLConfigPtr points to storage that is not accessible.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that one of SSLConfigOffset or SSLConfigPtr is zero and the other nonzero. Ensure that the field used points to accessible storage.

2393 (X'0959')
MQRC_SSL_INITIALIZATION_ERROR
Explanation:

An MQCONN or MQCONNX call was issued with SSL configuration options specified, but an error occurred during the initialization of the SSL environment.

This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the SSL installation is correct.

2394 (X'095A')
MQRC_Q_INDEX_TYPE_ERROR
Explanation:

An MQGET call was issued specifying one or more of the following options:

  • MQGMO_ALL_MSGS_AVAILABLE

  • MQGMO_ALL_SEGMENTS_AVAILABLE

  • MQGMO_COMPLETE_MSG

  • MQGMO_LOGICAL_ORDER

but the call failed because the queue is not indexed by group identifier. These options require the queue to have an IndexType of MQIT_GROUP_ID.

This reason code occurs only on z/OS.

Completion Code:

MQCC_FAILED

Programmer Response:

Redefine the queue to have an IndexType of MQIT_GROUP_ID. Alternatively, modify the application to avoid using the options listed above.

2395 (X'095B')
MQRC_CFBS_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFBS structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2396 (X'095C')
MQRC_SSL_NOT_ALLOWED
Explanation:

A connection to a queue manager was requested, specifying SSL encryption. However, the connection mode requested is one that does not support SSL (for example, bindings connect).

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Modify the application to request client connection mode, or to disable SSL encryption.

2397 (X'095D')
MQRC_JSSE_ERROR
Explanation:

JSSE reported an error (for example, while connecting to a queue manager using SSL encryption). The MQException object containing this reason code references the Exception thrown by JSSE; this can be obtained by using the MQException.getCause() method. From JMS, the MQException is linked to the thrown JMSException.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Inspect the causal exception to determine the JSSE error.

2398 (X'095E')
MQRC_SSL_PEER_NAME_MISMATCH
Explanation:

The application attempted to connect to the queue manager using SSL encryption, but the distinguished name presented by the queue manager does not match the specified pattern.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the certificates used to identify the queue manager. Also check the value of the sslPeerName property specified by the application.

2399 (X'095F')
MQRC_SSL_PEER_NAME_ERROR
Explanation:

The application specified a peer name of incorrect format.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the value of the sslPeerName property specified by the application.

2400 (X'0960')
MQRC_UNSUPPORTED_CIPHER_SUITE
Explanation:

A connection to a queue manager was requested, specifying SSL encryption. However, JSSE reported that it does not support the CipherSuite specified by the application.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the CipherSuite specified by the application. Note that the names of JSSE CipherSuites differ from their equivalent CipherSpecs used by the queue manager.

Also, check that JSSE is correctly installed.

2401 (X'0961')
MQRC_SSL_CERTIFICATE_REVOKED
Explanation:

A connection to a queue manager was requested, specifying SSL encryption. However, the certificate presented by the queue manager was found to be revoked by one of the specified CertStores.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Check the certificates used to identify the queue manager.

2402 (X'0962')
MQRC_SSL_CERT_STORE_ERROR
Explanation:

A connection to a queue manager was requested, specifying SSL encryption. However, none of the CertStore objects provided by the application could be searched for the certificate presented by the queue manager. The MQException object containing this reason code references the Exception encountered when searching the first CertStore; this can be obtained using the MQException.getCause() method. From JMS, the MQException is linked to the thrown JMSException.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Inspect the causal exception to determine the underlying error. Check the CertStore objects provided by your application. If the causal exception is a java.lang.NoSuchElementException, ensure that your application is not specifying an empty collection of CertStore objects.

2406 (X'0966')
MQRC_CLIENT_EXIT_LOAD_ERROR
Explanation:

The external user exit required for a client connection could not be loaded because the shared library specified for it cannot be found, or the entry point specified for it cannot be found.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that the correct library has been specified, and that the path variable for the machine environment includes the relevant directory. Ensure also that the entry point has been named properly and that the named library does export it.

2407 (X'0967')
MQRC_CLIENT_EXIT_ERROR
Explanation:

A failure occured while executing a non-Java user exit for a client connection.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the non-Java user exit can accept the parameters and message being passed to it and that it can handle error conditions, and that any information that the exit requires, such as user data, is correct and available.

2409 (X'0969')
MQRC_SSL_KEY_RESET_ERROR
Explanation:

On an MQCONN or MQCONNX call, the value of the SSL key reset count is not in the valid range of 0 through 999 999 999.

The value of the SSL key reset count is specified by either the value of the MQSSLRESET environment variable (MQCONN or MQCONNX call), or the value of the KeyResetCount field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLRESET and KeyResetCount are specified, the latter is used. MQCONN or MQCONNX

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure and the MQSSLRESET environment variable are set correctly.

2411 (X'096B')
MQRC_LOGGER_STATUS
Explanation:

This condition is detected when a logger event occurs.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2412 (X'096C')
MQRC_COMMAND_MQSC
Explanation:

This condition is detected when an MQSC command is executed.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2413 (X'096D')
MQRC_COMMAND_PCF
Explanation:

This condition is detected when a PCF command is executed.

Completion Code:

MQCC_WARNING

Programmer Response:

None. This reason code is only used to identify the corresponding event message.

2414 (X'096E')
MQRC_CFIF_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIF structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2415 (X'096F')
MQRC_CFSF_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFSF structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2416 (X'0970')
MQRC_CFGR_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFGR structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2417 (X'0971')
MQRC_MSG_NOT_ALLOWED_IN_GROUP
Explanation:

An MQPUT or MQPUT1 call was issued to put a message in a group but it is not valid to put such a message in a group. An example of an invalid message is a PCF message where the Type is MQCFT_TRACE_ROUTE.

Completion Code:

MQCC_FAILED

Programmer Response:

Remove the invalid message from the group.

2418 (X'0972')
MQRC_FILTER_OPERATOR_ERROR
Explanation:

The Operator parameter supplied is not valid.

If it is an input variable then the value is not one of the MQCFOP_* constant values. If it is an output variable then the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredicatable results occur.)

Completion Code:

MQCC_FAILED

Programmer Response:

Correct the parameter.

2419 (X'0973')
MQRC_NESTED_SELECTOR_ERROR
Explanation:

An mqAddBag call was issued, but the bag to be nested contained a data item with an inconsistent selector. This reason only occurs if the bag into which the nested bag was to be added was created with the MQCBO_CHECK_SELECTORS option.

Completion Code:

MQCC_FAILED

Programmer Response:

Ensure that all data items within the bag to be nested have selectors that are consistent with the data type implied by the item.

2420 (X'0974')
MQRC_EPH_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQEPH structure that is not valid. Possible errors include the following:

  • The StrucId field is not MQEPH_STRUC_ID.

  • The Vfield is not MQEPH_VERSION_1.

  • The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure.

  • The CodedCharSetId field is zero, or a negative value that is not valid.

  • The Flags field contains an invalid combination of MQEPH_* values.

  • The BufferLength parameter of the call has a value that is too small to accommodate the structure, so the structure extends beyond the end of the message.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value; note that MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field.

2421 (X'0975')
MQRC_RFH_FORMAT_ERROR
Explanation:

The message contains an MQRFH structure, but its format is incorrect. If you are using WebSphere MQ SOAP, the error is in an incoming SOAP/MQ request message.

Completion Code:

MQCC_FAILED

Programmer Response:

If you are using WebSphere MQ SOAP with the IBM-supplied sender, contact your IBM support center. If you are using WebSphere MQ SOAP with a bespoke sender, check that the RFH2 section of the SOAP/MQ request message is in valid RFH2 format.

2422 (X'0976')
MQRC_CFBF_ERROR
Explanation:

An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFBF structure that is not valid.

This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the fields in the structure are set correctly.

2423 (X'0977')
MQRC_CLIENT_CHANNEL_CONFLICT
Explanation:

A client channel definition table was specified for determining the name of the channel, but the name has already been defined.

This reason code occurs only with Java applications.

Completion Code:

MQCC_FAILED

Programmer Response:

Change the channel name to blank and try again.

6100 (X'17D4')
MQRC_REOPEN_EXCL_INPUT_ERROR
Explanation:

An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented.

Closure has been prevented because the queue is open for exclusive input and closure might result in the queue being accessed by another process or thread, before the queue is reopened by the process or thread that presently has access.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Set the open options explicitly to cover all eventualities so that implicit reopening is not required.

6101 (X'17D5')
MQRC_REOPEN_INQUIRE_ERROR
Explanation:

An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented.

Closure has been prevented because one or more characteristics of the object need to be checked dynamically prior to closure, and the open options do not already include MQOO_INQUIRE.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Set the open options explicitly to include MQOO_INQUIRE.

6102 (X'17D6')
MQRC_REOPEN_SAVED_CONTEXT_ERR
Explanation:

An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented.

Closure has been prevented because the queue is open with MQOO_SAVE_ALL_CONTEXT, and a destructive get has been performed previously. This has caused retained state information to be associated with the open queue and this information would be destroyed by closure.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Set the open options explicitly to cover all eventualities so that implicit reopening is not required.

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 additional options. An implicit reopen is required but closure has been prevented.

Closure has been prevented because the queue is a local queue of the definition type MQQDT_TEMPORARY_DYNAMIC, that would be destroyed by closure.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Set the open options explicitly to cover all eventualities so that implicit reopening is not required.

6104 (X'17D8')
MQRC_ATTRIBUTE_LOCKED
Explanation:

An attempt has been made to change the 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 object (as appropriate) before changing the attribute value.

An object may have been connected and/or opened unexpectedly and implicitly in order to perform an MQINQ call. Check the attribute cross-reference table in the WebSphere MQ Using C++ book to determine whether any of your method invocations result in an MQINQ call.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Include MQOO_INQUIRE in the ImqObject open options and set them earlier.

6105 (X'17D9')
MQRC_CURSOR_NOT_VALID
Explanation:

The browse cursor for an open queue has been invalidated since it was last used by an implicit reopen.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Set the ImqObject open options explicitly to cover all eventualities so that implicit reopening is not required.

6106 (X'17DA')
MQRC_ENCODING_ERROR
Explanation:

The encoding of the (next) message item needs to be MQENC_NATIVE for pasting.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6107 (X'17DB')
MQRC_STRUC_ID_ERROR
Explanation:

The structure id for the (next) message item, which is derived from the 4 characters beginning at the data pointer, is either missing or is inconsistent with the class of object into which the item is being pasted.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6108 (X'17DC')
MQRC_NULL_POINTER
Explanation:

A null pointer has been supplied where a nonnull pointer is either required or implied.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6109 (X'17DD')
MQRC_NO_CONNECTION_REFERENCE
Explanation:

The connection reference is null. A connection to an ImqQueueManager object is required.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6110 (X'17DE')
MQRC_NO_BUFFER
Explanation:

No buffer is available. For an ImqCache object, one cannot be allocated, denoting an internal inconsistency in the object state that should not occur.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6111 (X'17DF')
MQRC_BINARY_DATA_LENGTH_ERROR
Explanation:

The length of the binary data is inconsistent with the length of the target attribute. Zero is a correct length for all attributes.

  • The correct length for an accounting token is MQ_ACCOUNTING_TOKEN_LENGTH.

  • The correct length for an alternate security id is MQ_SECURITY_ID_LENGTH.

  • The correct length for a correlation id is MQ_CORREL_ID_LENGTH.

  • The correct length for a facility token is MQ_FACILITY_LENGTH.

  • The correct length for a group id is MQ_GROUP_ID_LENGTH.

  • The correct length for a message id is MQ_MSG_ID_LENGTH.

  • The correct length for an instance id is MQ_OBJECT_INSTANCE_ID_LENGTH.

  • The correct length for a transaction instance id is MQ_TRAN_INSTANCE_ID_LENGTH.

  • The correct length for a message token is MQ_MSG_TOKEN_LENGTH.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6112 (X'17E0')
MQRC_BUFFER_NOT_AUTOMATIC
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.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:
6113 (X'17E1')
MQRC_INSUFFICIENT_BUFFER
Explanation:

There is insufficient buffer space available after the data pointer to accommodate the request. This might be because the buffer cannot be resized.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6114 (X'17E2')
MQRC_INSUFFICIENT_DATA
Explanation:

There is insufficient data after the data pointer to accommodate the request.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6115 (X'17E3')
MQRC_DATA_TRUNCATED
Explanation:

Data has been truncated when copying from one buffer to another. This might be because the target buffer cannot be resized, or because there is a problem addressing one or other buffer, or because a buffer is being downsized with a smaller replacement.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6116 (X'17E4')
MQRC_ZERO_LENGTH
Explanation:

A zero length has been supplied where a positive length is either required or implied.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6117 (X'17E5')
MQRC_NEGATIVE_LENGTH
Explanation:

A negative length has been supplied where a zero or positive length is required.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6118 (X'17E6')
MQRC_NEGATIVE_OFFSET
Explanation:

A negative offset has been supplied where a zero or positive offset is required.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6119 (X'17E7')
MQRC_INCONSISTENT_FORMAT
Explanation:

The format of the (next) message item is inconsistent with the class of object into which the item is being pasted.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6120 (X'17E8')
MQRC_INCONSISTENT_OBJECT_STATE
Explanation:

There is an inconsistency between this object, which is open, and the referenced ImqQueueManager object, which is not connected.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6121 (X'17E9')
MQRC_CONTEXT_OBJECT_NOT_VALID
Explanation:

The ImqPutMessageOptions context reference does not reference a valid ImqQueue object. The object has been previously destroyed.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6122 (X'17EA')
MQRC_CONTEXT_OPEN_ERROR
Explanation:

The ImqPutMessageOptions context reference references an ImqQueue object that could not be opened to establish a context. This may be because the ImqQueue object has inappropriate open options. Inspect the referenced object reason code to establish the cause.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6123 (X'17EB')
MQRC_STRUC_LENGTH_ERROR
Explanation:

The length of a data structure is inconsistent with its content. For an MQRMH, the length is insufficient to contain the fixed fields and all offset data.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

6124 (X'17EC')
MQRC_NOT_CONNECTED
Explanation:

A method failed because a required connection to a queue manager was not available, and a connection cannot be established implicitly because the IMQ_IMPL_CONN flag of the ImqQueueManager behavior class attribute is FALSE.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Establish a connection to a queue manager and retry.

6125 (X'17ED')
MQRC_NOT_OPEN
Explanation:

A method failed because an object was not open, and opening cannot be accomplished implicitly because the IMQ_IMPL_OPEN flag of the ImqObject behavior class attribute is FALSE.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Open the object and retry.

6126 (X'17EE')
MQRC_DISTRIBUTION_LIST_EMPTY
Explanation:

An ImqDistributionList failed to open because there are no ImqQueue objects referenced.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

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 reopened implicitly because the IMQ_IMPL_OPEN flag of the ImqObject behavior class attribute is false.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Open the object with appropriate ImqObject open options and retry.

6128 (X'17FO')
MQRC_WRONG_VERSION
Explanation:

A method failed because a version number specified or encountered is either incorrect or not supported.

For the ImqCICSBridgeHeader class, the problem is with the version attribute.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

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, ensure that both programs are using consistent and supported version numbers.

6129 (X'17F1')
MQRC_REFERENCE_ERROR
Explanation:

An object reference is invalid.

There is a problem with the address of a referenced object. At the time of use, the address of the object is nonnull, but is invalid and cannot be used for its intended purpose.

This reason code occurs in the WebSphere MQ C++ environment.

Completion Code:

MQCC_FAILED

Programmer Response:

Check that the referenced object is neither deleted nor out of scope, or remove the reference by supplying a null address value.