Posted: Sun Apr 25, 2004 10:31 am Post subject: Queue Manager Aliasing
Newbie
Joined: 25 Apr 2004 Posts: 5
I work on z/os 1.4 and my level of MQ Series is 5.3 I am implementing shared queues. I have two systems in a sysplex, SYSA and SYSB. On each system we have a production queue manager, QMA on SYSA and QMB on SYSB. We want to be able to run a job on either system and have it work. My problem is we have applications already coded with the MQCONN to the queue manager names (QMA or QMB). When I tested the shared queues I can connect to both systems using the queue sharing group name no problem. But what do I do when QMB has been coded in the MQCONN and the job runs on SYSA? It fails with a 2058. Would a queue manager alias solve this problem? Can you do an MQCONN call to a queue manager alias? Any ideas?
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
QueueManager Alias is a bit misleading name.
QMA can only be used to 'replace' or reset the QueueManager name on a message itself by using a remote queue definition. (you can look this up in the manual)
Not for 'renaming'/'aliassing' connections to an existing QueueManager. _________________ Michael
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
eh.. Clustering is also not what it seems ... (whole different subject...)
The only way to have the QueueManager name be 'transparant' to the application is using
'default' QueueManagers when in 'server-binding' mode
or
use a client channel table when in 'client' mode and use *QueueManager name in you connection parameters. _________________ Michael
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