Home

 

Return codes

 

These are the return codes specific to clusters.

MQRC_CLUSTER_EXIT_ERROR (2266 X'8DA')

Occurs when an MQOPEN, MQPUT, or MQPUT1 call is issued to open a cluster queue or put a message on it, and the cluster workload exit defined by the queue-manager’s ClusterWorkloadExit attribute fails unexpectedly or does not respond in time.

On WebSphere MQ for z/OS a message is written to the system log giving more information about this error.

Subsequent MQOPEN, MQPUT, and MQPUT1 calls for this queue handle are processed as though the ClusterWorkloadExit attribute were blank.

MQRC_CLUSTER_EXIT_LOAD_ERROR (2267 X'8DB')

On z/OS, if the cluster workload exit cannot be loaded, a message is written to the system log and processing continues as though the ClusterWorkloadExit attribute is blank. On platforms other than z/OS, when an MQCONN or MQCONNX call is issued to connect to a queue manager, but the call fails because the cluster workload exit defined by the queue-manager’s ClusterWorkloadExit attribute cannot be loaded.

MQRC_CLUSTER_PUT_INHIBITED (2268 X'8DC')

Occurs when an MQOPEN call with the MQOO_OUTPUT and MQOO_BIND_ON_OPEN options in effect is issued for a cluster queue, but all the instances of the queue in the cluster are currently put-inhibited, that is, all the queue instances have the InhibitPut attribute set to MQQA_PUT_INHIBITED. Because there are no queue instances available to receive messages, the MQOPEN call fails.

This reason code occurs only when both of the following are true:

• There is no local instance of the queue. (If there is a local instance, the MQOPEN call succeeds, even if the local instance is put-inhibited.)

• There is no cluster workload exit for the queue, or there is a cluster workload exit but it does not choose a queue instance. (If the cluster workload exit chooses a queue instance, the MQOPEN call succeeds, even if that instance is put-inhibited.)

If the MQOO_BIND_NOT_FIXED option is specified on the MQOPEN call, the call can succeed even if all the queues in the cluster are put-inhibited. However, a subsequent MQPUT call may fail if all the queues are still put-inhibited at the time of that call.

MQRC_CLUSTER_RESOLUTION_ERROR (2189 X'88D')

Occurs when an MQOPEN, MQPUT, or MQPUT1 call is issued to open a cluster queue or put a message on it, and the queue definition cannot be resolved correctly because a response is required from the full repository queue manager but none is available.

MQRC_CLUSTER_RESOURCE_ERROR (2269 X'8DD')

Occurs when an MQOPEN, MQPUT, or MQPUT1 call is issued for a cluster queue, but an error occurs while trying to use a resource required for clustering.

MQRC_NO_DESTINATIONS_AVAILABLE (2270 X'8DE')

Occurs when an MQPUT or MQPUT1 call is issued to put a message on a cluster queue, but at the time of the call there are no longer any instances of the queue in the cluster. The PUT fails and the message is not 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.

MQRC_STOPPED_BY_CLUSTER_EXIT (2188 X'88C')

Occurs when an MQOPEN, MQPUT, or MQPUT1 call is issued to open or put a message on a cluster queue, but the cluster workload exit rejects the call.

 

Parent topic:

Using clusters for workload management

qc11090_

 

Home