All queues are defined with DEFBIND(NOTFIXED)...and the appl has MQOO_BIND_NOT_FIXED
specified. What could be causing the error?
If a clustered queue manager is unreachable or unavailable due to a network error or a QMGR going down or a server crashing... whatever scenario you can think of that would
make a QMGR 'unavailable', the cluster channels to the unavailable QMGR go into a
retrying state. Workload continues to be 'destined' to this unavailable
QMGR. The channels being in a retrying state is not treated as an 'error' condition
and therefore the cluster workload balancing (round-robin) contines to consider this QMGR
as available.
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
Yes. If you are issuing the MQOPEN and specifying a QMGR/Queuename pair instead of just the queuename, it will always resolve to that instance of the queue, and no workload balancing will occur.
_________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum