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.
The call completed normally. The completion code (CompCode) is MQCC_OK.
MQCC_OK
None.
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.
MQCC_WARNING or MQCC_FAILED
As defined by the writer of the data-conversion exit.
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.
MQCC_WARNING or MQCC_FAILED
As defined by the writer of the data-conversion exit.
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.
MQCC_FAILED
Correct the queue definitions.
An MQCONN or MQCONNX call was issued, but the application is already connected to the queue manager.
MQCC_WARNING
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.
The current unit of work encountered a fatal error or was backed out. This occurs in the following cases:
MQCC_WARNING or MQCC_FAILED
Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed.
The Buffer parameter is not valid for one of the following reasons:
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
Specify a value that is zero or greater. For the mqAddString and mqSetString calls, the special value MQBL_NULL_TERMINATED is also valid.
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.)
MQCC_FAILED
Specify a value large enough to hold the concatenated strings for all selected attributes.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_WARNING
Specify a large enough value, unless only a subset of the values is needed.
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.
MQCC_FAILED
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.
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.
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
Specify a valid name.
The call is not valid for the current environment.
MQCC_FAILED
Do one of the following (as appropriate):
On an MQPUT or MQPUT1 call, the value specified for the Expiry field in the message descriptor MQMD is not valid.
MQCC_FAILED
Specify a value that is greater than zero, or the special value MQEI_UNLIMITED.
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.
MQCC_FAILED
Specify MQFB_NONE, or a value in the range MQFB_SYSTEM_FIRST through MQFB_SYSTEM_LAST, or MQFB_APPL_FIRST through MQFB_APPL_LAST.
MQGET calls are currently inhibited for the queue, or for the queue to which this queue resolves.
MQCC_FAILED
If the system design allows get requests to be inhibited for short periods, retry the operation later.
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.
MQCC_FAILED
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.
The connection handle Hconn is not valid, for one of the following reasons:
MQCC_FAILED
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).
The object handle Hobj is not valid, for one of the following reasons:
MQCC_FAILED
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).
On an MQSET call, the value specified for either the MQIA_INHIBIT_GET attribute or the MQIA_INHIBIT_PUT attribute is not valid.
MQCC_FAILED
Specify a valid value for the InhibitGet or InhibitPut queu attribute.
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.)
MQCC_FAILED
Specify a value large enough for all selected integer attributes.
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.
MQCC_WARNING
Specify a large enough value, unless only a subset of the values is needed.
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.)
MQCC_FAILED
Correct the parameter.
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:
MQCC_FAILED
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.
The MQCONN or MQCONNX call was rejected because the maximum number of concurrent connections has been exceeded.
For more information, see the WebSphere MQ for z/OS System Setup Guide.
MQCC_FAILED
Either increase the size of the appropriate parameter value, or reduce the number of concurrent connections.
The MQMD structure is not valid, for one of the following reasons:
MQCC_FAILED
Ensure that input fields in the MQMD structure are set correctly.
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:
MQCC_FAILED
Specify the name of the queue to which the reply message or report message is to be sent.
Either:
MQCC_FAILED
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.
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.
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:
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.
MQCC_FAILED
Check whether the BufferLength parameter is specified correctly; if it is, do one of the following:
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:
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.
MQCC_FAILED
Check whether the BufferLength parameter is specified correctly; if it is, do one of the following:
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:
MQCC_WARNING or MQCC_FAILED
If this is an expected condition, no corrective action is required.
If this is an unexpected condition, check that:
Consider waiting longer for the message.
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:
MQCC_FAILED
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.
The user is not authorized to perform the operation attempted:
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.
MQCC_FAILED
Ensure that the correct queue manager or object was specified, and that appropriate authority exists.
An MQGET call was issued with one of the following options:
but the queue had not been opened for browse.
MQCC_FAILED
Specify MQOO_BROWSE when the queue is opened.
An MQGET call was issued to retrieve a message from a queue, but the queue had not been opened for input.
MQCC_FAILED
Specify one of the following when the queue is opened:
An MQINQ call was issued to inquire object attributes, but the object had not been opened for inquire.
MQCC_FAILED
Specify MQOO_INQUIRE when the object is opened.
An MQPUT call was issued to put a message on a queue, but the queue had not been opened for output.
MQCC_FAILED
Specify MQOO_OUTPUT when the queue is opened.
An MQSET call was issued to set queue attributes, but the queue had not been opened for set.
MQCC_FAILED
Specify MQOO_SET when the object is opened.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
System design should specify whether an application is to wait and retry, or take other action.
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.
MQCC_FAILED
Specify a valid object type.
On the MQOPEN or MQPUT1 call, the object descriptor MQOD is not valid, for one of the following reasons:
MQCC_FAILED
Ensure that input fields in the MQOD structure are set correctly.
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:
For the MQCLOSE call, this includes the following case:
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.
MQCC_FAILED
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.
The Options parameter or field contains options that are not valid, or a combination of options 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.)
MQCC_FAILED
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.
On an MQPUT or MQPUT1 call, the value specified for the Persistence field in the message descriptor MQMD is not valid.
MQCC_FAILED
Specify one of the following values:
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.
MQCC_FAILED
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.
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.
MQCC_WARNING
None required, unless this reason code was not expected by the application that put the message.
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.
MQCC_FAILED
Specify a value in the range zero through MaxPriority, or the special value MQPRI_PRIORITY_AS_Q_DEF.
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.
MQCC_FAILED
If the system design allows put requests to be inhibited for short periods, retry the operation later.
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.)
MQCC_FAILED
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.
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.
MQCC_FAILED
Retry the operation later. Consider increasing the maximum depth for this queue, or arranging for more instances of the application to service the queue.
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:
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).
MQCC_FAILED
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.
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.
MQCC_FAILED
Check whether an application is putting messages in an infinite loop. If not, make more disk space available for the queue.
One of the following occurred:
MQCC_FAILED
Specify a valid queue.
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.)
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:
MQCC_FAILED
Use an all-blank name if possible, or verify that the name used is valid.
This occurs:
MQCC_FAILED
Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions.
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.
MQCC_FAILED
Do the following:
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.
MQCC_FAILED
Modify the application so that no more than one message is marked within each unit of work.
An MQCONN, MQCONNX, MQOPEN, MQPUT1, or MQCLOSE call was issued, but it failed because a security error occurred.
MQCC_FAILED
Note the error from the security manager, and contact your system programmer or security administrator.
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.)
MQCC_FAILED
Specify a value in the range 0 through 256.
On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is larger than the maximum supported (256).
MQCC_FAILED
Reduce the number of selectors specified on the call; the valid range is 0 through 256.
An MQINQ or MQSET call was issued, but the Selectors array contains a selector that is not valid for one of the following reasons:
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.)
MQCC_FAILED
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.
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:
MQCC_WARNING
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.
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.
MQCC_FAILED
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.
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.
This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98.
MQCC_WARNING
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.
The call failed because there is insufficient main storage available.
MQCC_FAILED
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.
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.
MQCC_FAILED
Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as appropriate.
On an MQSET call, the value specified for the MQIA_TRIGGER_CONTROL attribute selector is not valid.
MQCC_FAILED
Specify a valid value.
On an MQSET call, the value specified for the MQIA_TRIGGER_DEPTH attribute selector is not valid.
MQCC_FAILED
Specify a value that is greater than zero.
On an MQSET call, the value specified for the MQIA_TRIGGER_MSG_PRIORITY attribute selector is not valid.
MQCC_FAILED
Specify a value in the range zero through the value of MaxPriority queue-manager attribute.
On an MQSET call, the value specified for the MQIA_TRIGGER_TYPE attribute selector is not valid.
MQCC_FAILED
Specify a valid value.
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.
MQCC_WARNING
None, because the application expected this situation.
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.
MQCC_WARNING
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.
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.
MQCC_FAILED
Correct the queue definitions.
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:
This can also occur in response to a command that specifies the name of an object or other item that does not exist.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
On an MQOPEN or MQPUT1 call, an error occurred with the queue-name resolution, for one of the following reasons:
MQCC_FAILED
Check the values specified for ObjectQMgrName and ObjectName. If these are correct, check the queue definitions.
On the MQGET call, the value specified for the WaitInterval field in the GetMsgOpts parameter is not valid.
MQCC_FAILED
Specify a value greater than or equal to zero, or the special value MQWI_UNLIMITED if an indefinite wait is required.
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:
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.
MQCC_FAILED
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.
On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager, but one of the following occurred:
MQCC_FAILED
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.
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.
MQCC_FAILED
Specify MQOO_PASS_ALL_CONTEXT (or another option that implies it) when the queue is opened.
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.
MQCC_FAILED
Specify MQOO_PASS_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened.
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.
MQCC_FAILED
Specify MQOO_SET_ALL_CONTEXT when the queue is opened.
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.
MQCC_FAILED
Specify MQOO_SET_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened.
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.
MQCC_FAILED
Specify MQOO_SAVE_ALL_CONTEXT when the queue referred to is opened.
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.
MQCC_FAILED
Ensure that a successful nonbrowse get call has been issued with the queue handle referred to.
An MQGET call was issued, specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but the Signal1 field is not valid.
This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98.
MQCC_FAILED
Correct the setting of the Signal1 field.
An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists.
MQCC_FAILED
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.
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.
MQCC_FAILED
It may be necessary to stop and restart the queue manager, or to restore the queue-manager data from back-up storage.
There are insufficient system resources to complete the call successfully.
MQCC_FAILED
Run the application when the machine is less heavily loaded.
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.
MQCC_FAILED
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.
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.
MQCC_WARNING
If this reason code is expected, no corrective action is required. If this reason code is not expected, do the following:
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Remove the relevant MQRO_COD_* option.
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.
MQCC_FAILED
Tidy up and terminate.
An MQXWAIT call was issued, but the invocation was not valid for one of the following reasons:
This reason code occurs only on z/OS.
MQCC_FAILED
Obey the rules for using the MQXWAIT call. Refer to the WebSphere MQ Intercommunication book for details of this call.
On any call other than MQCONN or MQDISC, the API crossing exit suppressed the call.
This reason code occurs only on z/OS.
MQCC_FAILED
Obey the rules for MQI calls that the exit enforces. To find out the rules, see the writer of the exit.
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 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.
MQCC_WARNING
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.
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.)
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_WARNING
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.
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.
MQCC_WARNING
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.
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.)
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_WARNING
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.
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.
MQCC_WARNING
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.
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.
MQCC_WARNING
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.
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.
MQCC_WARNING
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.
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.
MQCC_WARNING
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.
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.
MQCC_WARNING
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.
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:
This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows.
MQCC_FAILED
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.
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.
MQCC_WARNING
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.
The IMS bridge has been started.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
The IMS bridge has been stopped.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
On an MQCONN call, the adapter was unable to acquire storage.
This reason code occurs only on z/OS.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL.
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.
MQCC_FAILED
Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL.
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.
MQCC_FAILED
Check your library concatenation. If this is correct, check that the CSQBDEFV or CSQQDEFV module contains the required subsystem ID.
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.
MQCC_FAILED
Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL.
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.
MQCC_FAILED
Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL.
On an MQBEGIN call, the begin-options structure MQBO is not valid, for one of the following reasons:
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.
MQCC_FAILED
Ensure that input fields in the MQBO structure are set correctly.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQDH structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
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).
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:
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.
MQCC_WARNING or MQCC_FAILED
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.
A queue or other MQ object could not be opened successfully, for one of the following reasons:
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.
MQCC_FAILED
Do one of the following:
STRMQM -c qmgrwhere qmgr should be replaced by the name of the queue manager.
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.
MQCC_FAILED
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.
On an MQCONNX call, the connect-options structure MQCNO is not valid, for one of the following reasons:
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.
MQCC_FAILED
Ensure that input fields in the MQCNO structure are set correctly.
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.
MQCC_FAILED
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.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQDLH structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
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).
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:
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.
MQCC_FAILED
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 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.
MQCC_WARNING or MQCC_FAILED
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.
On the MQXCNVC call, the TargetLength parameter is not valid for one of the following reasons:
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.
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_WARNING or MQCC_FAILED
Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct.
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.
MQCC_WARNING or MQCC_FAILED
Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQIIH structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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:
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.
MQCC_FAILED
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.
An error was encountered attempting to convert a double-byte character set (DBCS) string. This can occur in the following cases:
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
An MQOPEN or MQPUT1 call was issued, but the call failed for one of the following reasons:
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
Ensure that one of ObjectRecOffset and ObjectRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage.
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:
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.
MQCC_FAILED
Ensure that at least one of ResponseRecOffset and ResponseRecPtr is zero. Ensure that the field used points to accessible storage.
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
Ensure that at least one of PutMsgRecOffset and PutMsgRecPtr is zero. Ensure that the field used points to accessible storage.
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:
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.
MQCC_FAILED
Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict.
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:
Specifying these options enables the application to become aware that the queue manager is preparing to shut down.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict.
On an MQPUT or MQPUT1 call, the MQPMO structure is not valid, for one of the following reasons:
MQCC_FAILED
Ensure that input fields in the MQPMO structure are set correctly.
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.
MQCC_FAILED
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.
On an MQOPEN or MQPUT1 call, one of the following occurred:
MQCC_FAILED
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.
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.
MQCC_WARNING or MQCC_FAILED
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.
On an MQGET call, the MQGMO structure is not valid, for one of the following reasons:
MQCC_FAILED
Ensure that input fields in the MQGMO structure are set correctly.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Check the cluster workload exit to ensure that it has been written correctly. Determine why it rejected the call and correct the problem.
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.
MQCC_FAILED
Check that the repository manager is operating and that the queue and channel definitions are correct.
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.
MQCC_WARNING
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.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQTMC2 structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
Former name for MQRC_STORAGE_MEDIUM_FULL.
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:
This reason code occurs only on z/OS.
MQCC_FAILED
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.
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.
MQCC_FAILED
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:
An MQOPEN call was issued to open the queue manager definition, but the ObjectName field in the ObjDesc parameter is not blank.
MQCC_FAILED
Ensure that the ObjectName field is set to blanks.
The call was rejected because an unexpected error occurred.
MQCC_FAILED
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 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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Correct the queue definitions, or the queue-manager attribute. See the WebSphere MQ Application Programming Guide for more information.
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.
MQCC_FAILED
Do one of the following:
See the WebSphere MQ Application Programming Guide for more information.
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.
MQCC_FAILED
Do one of the following:
See the WebSphere MQ Application Programming Guide for more information.
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.
MQCC_FAILED
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.
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:
MQRC_CONNECTION_QUIESCING is also issued by the message channel agent (MCA) when the queue manager is in quiescing state.
MQCC_FAILED
The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Do one of the following:
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.
MQCC_FAILED
Do one of the following:
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.
MQCC_FAILED
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.
An MQGET call was issued with the MQGMO_UNLOCK option, but no message was currently locked.
MQCC_WARNING
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.
An exception from the .NET environment (as opposed to WebSphere MQ .NET) has been received and is included as an inner exception.
MQCC_FAILED
Refer to the .NET documentation for details about the inner exception. Follow the corrective action recommended there.
An exception from the Axis environment has been received and is included as a chained exception.
MQCC_FAILED
Refer to the Axis documentation for details about the chained exception. Follow the corrective action recommended there.
The SOAP URL has been specified incorrectly.
MQCC_FAILED
Correct the SOAP URL and rerun.
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.
MQCC_FAILED
Ensure that the subsystem is authorized to connect to the queue manager.
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.
MQCC_FAILED
Check the channel definitions. Increase the maximum message length that the channel can accept, or break the message into several smaller messages.
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.
MQCC_FAILED
Ensure that an MQI call cannot be issued while another one is active. Do not issue MQI calls from within a data-conversion exit.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQRMH structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
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).
This condition is detected when a queue manager becomes active.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when a queue manager is requested to stop or quiesce.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
An MQPUT or MQPUT1 call has caused the queue depth to be incremented to or above the limit specified in the QDepthHighLimit attribute.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
An MQGET call has caused the queue depth to be decremented to or below the limit specified in the QDepthLowLimit attribute.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
No successful gets or puts have been detected within an interval that is greater than the limit specified in the QServiceInterval attribute.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
A successful get has been detected within an interval that is less than or equal to the limit specified in the QServiceInterval attribute.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Look at the associated error message, which will explain the error in detail. Correct the error and retry.
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.
MQCC_FAILED
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.
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.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_WARNING
Examine the additional information returned in the event message to determine the reason for the failure.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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:
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.
MQCC_WARNING or MQCC_FAILED
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.
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:
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.
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_WARNING
Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one.
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.
MQCC_WARNING
Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one.
One of the following applies:
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.
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.
MQCC_WARNING or MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
Ensure that only valid options are specified for the field.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQMDE structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
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).
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.
MQCC_FAILED
Do the following:
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
Specify a value that is greater than zero. Zero is valid only for the last segment.
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.
MQCC_FAILED
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.
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:
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Modify the application to pass a version-2 MQGMO. Check the application logic to ensure that the Version field in MQGMO has been set to MQGMO_VERSION_2. Alternatively, remove the option that requires the version-2 MQGMO.
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.
MQCC_FAILED
Modify the application to pass a version-2 MQMD. Check the application logic to ensure that the Version field in MQMD has been set to MQMD_VERSION_2. Alternatively, remove the option that requires the version-2 MQMD.
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:
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQXQH structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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:
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.
MQCC_FAILED
Specify the source environment data correctly.
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:
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.
MQCC_FAILED
Specify the source name data correctly.
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:
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.
MQCC_FAILED
Specify the destination environment data correctly.
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:
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.
MQCC_FAILED
Specify the destination name data correctly.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQTM structure that is not valid. Possible errors include the following:
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
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.
MQCC_FAILED
Check the cluster workload exit to ensure that it has been written correctly.
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.
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.
MQCC_WARNING
Ensure that the queue-manager's ClusterWorkloadExit attribute has the correct value, and that the exit has been installed into the correct location.
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:
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Do the following:
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
The problem is likely to be transitory. The application should wait a short while and then retry the operation.
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.
MQCC_FAILED
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.
An MQCONN or MQCONNX call failed for one of the following reasons:
This reason code occurs only on z/OS.
MQCC_FAILED
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.
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.
MQCC_FAILED
Remove the MQGMO_MARK_SKIP_BACKOUT option from the MQGET call.
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.
MQCC_FAILED
Ensure that input fields in the MQCD structure are set correctly.
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:
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.
MQCC_FAILED
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.
This condition is detected when the channel has been stopped by an operator. The reason qualifier identifies the reasons for stopping.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_FAILED
Specify the configuration handle that was provided by the queue manager:
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.
MQCC_FAILED
Do the following:
One of the following has occurred:
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when the channel has been stopped. The reason qualifier identifies the reasons for stopping.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_FAILED
Make the underlying service available.
This reason should be returned by an installable service component when the component is unable to complete initialization successfully.
MQCC_FAILED
Correct the error and retry the operation.
This reason should be returned by an installable service component when the component is unable to complete termination successfully.
MQCC_FAILED
Correct the error and retry the operation.
This reason should be returned by the MQZ_LOOKUP_NAME installable service component when the name specified for the QName parameter is not recognized.
MQCC_FAILED
None. See the WebSphere MQ System Administration Guide book for information about installable services.
This reason should be returned by an installable service component when the component encounters an unexpected error.
MQCC_FAILED
Correct the error and retry the operation.
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.
MQCC_FAILED
None. See the WebSphere MQ System Administration Guide book for information about installable service.
This reason should be returned by the MQZ_FIND_USERID installable service component when the user ID cannot be determined.
MQCC_FAILED
None. See the WebSphere MQ System Administration Guide book for information about installable services.
This reason should be returned by the authority installable service component when the name specified by the EntityName parameter is not recognized.
MQCC_FAILED
Ensure that the entity is defined.
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.
MQCC_FAILED
Ensure that the reference object is defined. See the WebSphere MQ System Administration Guide book for information about installable services.
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.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
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.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_FAILED
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.
The function requested is not available in the current environment.
MQCC_FAILED
Remove the call from the application.
The Selector parameter has the wrong data type; it must be of type Long.
MQCC_FAILED
Declare the Selector parameter as Long.
The mqExecute call was issued, but the value of the MQIASY_TYPE data item in the administration bag is not MQCFT_COMMAND.
MQCC_FAILED
Ensure that the MQIASY_TYPE data item in the administration bag has the value MQCFT_COMMAND.
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.
MQCC_FAILED
Specify MQIND_NONE for the ItemIndex parameter.
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.
MQCC_FAILED
Specify the selector of a user-defined data item, or remove the call.
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.
MQCC_FAILED
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:
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:
If the bag was not created with the MQCBO_CHECK_SELECTORS option:
MQCC_FAILED
Specify a valid value.
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.
MQCC_FAILED
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.
The specified index is not present:
MQCC_FAILED
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.
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.)
MQCC_FAILED
Correct the parameter.
The Encoding field in the message descriptor MQMD contains a value that is not supported:
MQCC_FAILED
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:
The Selector parameter specifies a selector that does not exist in the bag.
MQCC_FAILED
Specify a selector that does exist in the bag.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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:
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:
MQCC_FAILED
Specify a valid value.
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.
MQCC_FAILED
Specify the handle of a bag created by the application, or remove the call.
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.)
MQCC_FAILED
Specify a valid value. Use the mqCountItems call to determine the number of user-defined data items in the bag.
The Format field in the message descriptor MQMD contains a value that is not supported:
MQCC_FAILED
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:
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.
MQCC_FAILED
Specify a selector value that is supported.
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.)
MQCC_FAILED
Correct the parameter.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
Review the description of the administration command being issued, and ensure that all required parameters are present in the bag.
The command server that processes administration commands is not available.
MQCC_FAILED
Start the command server.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
Remove the mqAddInquiry calls and use instead the mqAddInteger call with the appropriate MQIACF_*_ATTRS or MQIACH_*_ATTRS selectors.
A bag that is input to the call contains nested bags. Nested bags are supported only for bags that are output from the call.
MQCC_FAILED
Use a different bag as input to the call.
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.
MQCC_FAILED
Specify the MQCBO_ADMIN_BAG option when the bag is created.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
Specify the handle of a bag created by the application, or remove the call.
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.
MQCC_FAILED
Specify the selector of a user-defined data item, or remove the call.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
Remove the MQMO_MATCH_MSG_TOKEN option from the MQGET call.
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.
MQCC_FAILED
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.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQWIH structure that is not valid. Possible errors include the following:
MQCC_FAILED
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).
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:
MQCC_FAILED
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).
The contents of the NameValueString field in the MQRFH structure are not valid. NameValueString must adhere to the following rules:
The following is a valid NameValueString:
Famous_Words "The program displayed ""Hello World"""
MQCC_FAILED
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.
The message contains an MQRFH structure, but the command name contained in the NameValueString field is not valid.
MQCC_FAILED
Modify the application that generated the message to ensure that it places in the NameValueString field a command name that is valid.
The message contains an MQRFH structure, but a parameter name contained in the NameValueString field is not valid for the command specified.
MQCC_FAILED
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.
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.
MQCC_FAILED
Modify the application that generated the message to ensure that it places in the NameValueString field only one occurrence of the parameter.
The message contains an MQRFH structure, but the command specified in the NameValueString field requires a parameter that is not present.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Configure the DB2 subsystem so that the queue manager can connect to it.
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.
MQCC_FAILED
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.
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.
MQCC_WARNING
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
The problem is temporary; wait a short while and then retry the operation.
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.
MQCC_FAILED
The problem is temporary; wait a short while and then retry the operation.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Modify the queue definition to specify the name of a coupling-facility list structure that is defined in the CFRM data set.
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.
MQCC_FAILED
The problem is likely to persist. Consult the system programmer to ascertain the cause of the problem.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Check the DTC "Transaction timeout" value. If necessary, verify the NT installation order.
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.
MQCC_FAILED
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.
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:
MQCC_FAILED
Ensure that the parameter specified for ExitParms is the MQWXP structure that was passed to the exit when the exit was invoked.
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.
MQCC_FAILED
Ensure that the cluster workload exit passes the address of a valid record residing in the cluster cache.
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:
MQCC_FAILED
Ensure that the value specified for the NextOffset parameter is the value of one of the fields listed above.
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.
MQCC_FAILED
None.
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.
MQCC_FAILED
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.
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.)
MQCC_FAILED
Specify a valid address for the NextRecord parameter.
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.
None
Investigate the cause of the backout count being greater than the threshold. To correct this, define the backout queue for the queue concerned.
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.
None
To correct this, ensure that the ConnectionConsumers monitoring the queue provide a complete set of selectors. Alternatively, set the QueueConnectionFactory to retain messages.
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.
None
Investigate the origin of the message.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Ensure that the coupling-facility structure used for the queue is at the level required to support the capabilities that the queue provides.
This condition is detected when an object is created.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when an object is changed.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when an object is deleted.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when an object is refreshed.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when a connection cannot be established due to an SSL key-exchange or authentication failure.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_FAILED
Report the problem to the operator or administrator, who should use the MQSC command RECOVER CFSTRUCT to initiate recovery of the coupling-facility structure
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Consult the FFST record to obtain more detail about the problem.
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.
MQCC_FAILED
Consult the FFST record to obtain more detail about the problem.
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.
MQCC_FAILED
Modify the exit function to specify a value for ExitReason that is valid for the specified value of Function.
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.
MQCC_FAILED
Modify the exit to specify the null pointer as the value of the Reserved parameter.
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.
MQCC_FAILED
None.
On an MQCONNX call, the MQSCO structure is not valid for one of the following reasons:
This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.
MQCC_FAILED
Correct the definition of the MQSCO structure.
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:
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.
MQCC_FAILED
Specify a valid location for the key repository.
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:
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.
MQCC_FAILED
Specify a valid configuration string for the cryptographic hardware.
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.
MQCC_FAILED
Specify a value for AuthInfoRecCount that is zero or greater.
On an MQCONNX call, the MQSCO structure does not specify the address of the MQAIR records correctly. One of the following applies:
This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.
MQCC_FAILED
Ensure that one of AuthInfoRecOffset or AuthInfoRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage.
On an MQCONNX call, an MQAIR record is not valid for one of the following reasons:
This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.
MQCC_FAILED
Correct the definition of the MQAIR record.
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.
MQCC_FAILED
Specify MQAIT_CRL_LDAP for AuthInfoType.
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.
MQCC_FAILED
Specify a valid connection name.
On an MQCONNX call, an LDAP user name in an MQAIR record is not specified correctly. One of the following applies:
This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.
MQCC_FAILED
Ensure that one of LDAPUserNameOffset or LDAPUserNamePtr is zero and the other nonzero. Ensure that the field used points to accessible storage.
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.
MQCC_FAILED
Specify a value for LDAPUserNameLength that is zero or greater.
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.
MQCC_FAILED
Specify a value that is blank or null.
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.
MQCC_WARNING
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.
On an MQCONNX call, the MQCNO structure does not specify the MQSCO structure correctly. One of the following applies:
This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows.
MQCC_FAILED
Ensure that one of SSLConfigOffset or SSLConfigPtr is zero and the other nonzero. Ensure that the field used points to accessible storage.
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.
MQCC_FAILED
Check that the SSL installation is correct.
An MQGET call was issued specifying one or more of the following options:
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.
MQCC_FAILED
Redefine the queue to have an IndexType of MQIT_GROUP_ID. Alternatively, modify the application to avoid using the options listed above.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Modify the application to request client connection mode, or to disable SSL encryption.
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.
MQCC_FAILED
Inspect the causal exception to determine the JSSE error.
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.
MQCC_FAILED
Check the certificates used to identify the queue manager. Also check the value of the sslPeerName property specified by the application.
The application specified a peer name of incorrect format.
This reason code occurs only with Java applications.
MQCC_FAILED
Check the value of the sslPeerName property specified by the application.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Check the certificates used to identify the queue manager.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
A failure occured while executing a non-Java user exit for a client connection.
This reason code occurs only with Java applications.
MQCC_FAILED
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.
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
MQCC_FAILED
Check that the fields in the structure and the MQSSLRESET environment variable are set correctly.
This condition is detected when a logger event occurs.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when an MQSC command is executed.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
This condition is detected when a PCF command is executed.
MQCC_WARNING
None. This reason code is only used to identify the corresponding event message.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Remove the invalid message from the group.
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.)
MQCC_FAILED
Correct the parameter.
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.
MQCC_FAILED
Ensure that all data items within the bag to be nested have selectors that are consistent with the data type implied by the item.
An MQPUT or MQPUT1 call was issued, but the message data contains an MQEPH structure that is not valid. Possible errors include the following:
MQCC_FAILED
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.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Check that the fields in the structure are set correctly.
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.
MQCC_FAILED
Change the channel name to blank and try again.
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.
MQCC_FAILED
Set the open options explicitly to cover all eventualities so that implicit reopening is not required.
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.
MQCC_FAILED
Set the open options explicitly to include MQOO_INQUIRE.
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.
MQCC_FAILED
Set the open options explicitly to cover all eventualities so that implicit reopening is not required.
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.
MQCC_FAILED
Set the open options explicitly to cover all eventualities so that implicit reopening is not required.
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.
MQCC_FAILED
Include MQOO_INQUIRE in the ImqObject open options and set them earlier.
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.
MQCC_FAILED
Set the ImqObject open options explicitly to cover all eventualities so that implicit reopening is not required.
The encoding of the (next) message item needs to be MQENC_NATIVE for pasting.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
The connection reference is null. A connection to an ImqQueueManager object is required.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
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.
MQCC_FAILED
The length of the binary data is inconsistent with the length of the target attribute. Zero is a correct length for all attributes.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
There is insufficient data after the data pointer to accommodate the request.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
A negative length has been supplied where a zero or positive length is required.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
A negative offset has been supplied where a zero or positive offset is required.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
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.
MQCC_FAILED
Establish a connection to a queue manager and retry.
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.
MQCC_FAILED
Open the object and retry.
An ImqDistributionList failed to open because there are no ImqQueue objects referenced.
This reason code occurs in the WebSphere MQ C++ environment.
MQCC_FAILED
Establish at least one ImqQueue object in which the distribution list reference addresses the ImqDistributionList object, and retry.
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.
MQCC_FAILED
Open the object with appropriate ImqObject open options and retry.
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.
MQCC_FAILED
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.
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.
MQCC_FAILED
Check that the referenced object is neither deleted nor out of scope, or remove the reference by supplying a null address value.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq05rea3 |