Knowing almost nothing about workflows, let me shoot from the hip here...can you inquire on a namelist where the NL entry is the name of the cluster you want to resolve to?
SYSTEM.CLUSTER.ENV.NL = LAB SYSTEM.CLUSTER.ENV.NL = DEV SYSTEM.CLUSTER.ENV.NL = QA SYSTEM.CLUSTER.ENV.NL = PROD I think namelists are quite underused - they are the user-definable fields for MQ. For example, way back before BlockIP2, I modified BlockIP to look in a namelist for IP address masks. You could have an unlimited number of name-value pairs stashed away in namelists to represent various attributes of the QMgr, broker, cluster, etc. -- T.Rob -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: Wednesday, July 20, 2005 5:06 PM To: [email protected] Subject: What cluster am I in? With 2 or more brokers in the same MQ cluster, I would like to have the outgoing Request flow produce a message whose Reply To QM field contains the name of the MQ Cluster, so that when the reply message comes back, it can go to any of my brokers, and not be obligated to going back to the Broker that processed the request. Since the Cluster names change between LAB, DEV, QA and PROD, I need a way for the flow to find out what environment it is in, so that it can dynamically set the MQMD_ReplyToQManager field to the proper cluster name depending on what environment it is in. Any ideas? > Peter Potkay > ISD MQSeries Support Manager > The Hartford Financial Services > [EMAIL PROTECTED] > x77906 > IBM MQSeries Certified > ************************************************************************* PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************************* Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
