When I am trying to open a queue in a cics program it is failing with 2196 which is something to do with unknwon XMITQ .The XMITQ('xxxx') (For example) is already present while defining the queue of similar kind.But irrespective of that I get the error unknown xmit queue where as the other queue which has same xmit queue as the above queue is working fine but the other is not.
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.
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.
Joined: 20 Oct 2006 Posts: 6968 Location: porcelain throne
all these obj handle errors are a result of one reason:
what you are passing to the mqs open does not match the mqs set-up/definitons.....................period
either because you have garbaged it up in your program
what you think the name is (what you have for your program)
does not match the mqs set-up.
nothing magical about it.
calling a program that does not exist in the loadlib
selecting a column that does not exist in your db2 dsn
selecting from a table that does not exist in your db2 dsn
trying to use a db2 plan that does not exist
use your mqs utilities and determine that associated names with queues
and compare with what you are passing to your mqs module.
i would not suggest asking someone what the names are,
find out yourself.
i know that you are relatively new to mqs, so you have a learning curve.
you should spend the time to acquaint yourself with the mqs utilities installed at your site.
usage of the utilities to determine the queue name/queue manager relationships
will save you a lot of time.