These are the return codes specific to clusters.
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.
On z/OS(R), 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.This reason code occurs only when both 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 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.
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.
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.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzah0739 |