What it means
When a message is meant for another queue manager, the local queue manager needs a route: a transmission queue with the same name, a queue manager alias, a cluster route, or a default transmission queue. If none fits, MQOPEN or MQPUT1 fails with 2087. It is also the Unknown Remote Queue Manager event.
Typical causes
- ObjectQMgrName has a typo or names a queue manager that has no route from here.
- A remote queue definition points to a queue manager with no matching transmission queue and no default transmission queue.
- A queue manager alias is defined wrongly.
- On z/OS, the target is a queue sharing group member but intra-group queuing is off.
How to fix it
- Check the ObjectName and ObjectQMgrName the program uses.
- Display the remote queue definition (DISPLAY QREMOTE(name) RQMNAME XMITQ).
- Check that a transmission queue with that name exists, or that DEFXMITQ is set on purpose.
- For clusters, check the target queue manager is in the cluster and visible here.
Example
Illustrative only; names and values are invented.
MQOPEN failed CompCode=2 Reason=2087 Queue=APP.REMOTE.QUEUE RemoteQMgr=QM02
DISPLAY QREMOTE(APP.REMOTE.QUEUE) RQMNAME XMITQ