Hi
Dave,
If
your queue managers are defined in queue sharing groups, your MQCONN can be to
the group name (e.g. M000). It doesn't matter if your application doesn't
use any shared queues. Connecting to the group automatically connects you
to the local queue manager. Jobs can thus run on any member of the
sysplex. However, if you aren't into QSG's, other solutions are likely to
be easier.
Regards, Alan
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Adiraju, Rao
Sent: 29 January 2004 21:41
To: [EMAIL PROTECTED]
Subject: Re: T-Rex distributed systemsLuckily on z/OS only batch jobs/applications need to establish the connections to the Queue Managers (in CICS it's done at the CICS region level) and hence the need to know the QMGR name.This as suggested earlier, can be driven by a Dataset / Loadmodule or DB2 table.The sites that I have worked in the past are either put their QMGR names in a DB2 table (DB2 subsystem switching is done at the JCL level anyway) or put in a QSAM file and every MQ program is supposed to read a file using a standard DD name that provides the QMGR name.When the code gets migrated through SCLM phases, it used to pick up the appropriate subsystem or QSAM qualifiers for the environment.Regarding security, it was controlled by RACF / ACF2. Because most of the sites I have worked, batch user-ids in production are different from other environments including stress testing.Rao Adiraju
WebSphere MQ Specialist
The National Bank of NZ Ltd.
Tel: +64-4-494 4299
Fax: +64-4-802 8509
Mbl: +64-211-216-116
From: Dave Adam [mailto:[EMAIL PROTECTED]
Sent: 30 January 2004 10:05 AM
To: [EMAIL PROTECTED]
Subject: Re: T-Rex distributed systems
I must not be explaining this right
our production QMGR's are on another pair of ZOS images and are called P001 and P002
our test machine has 2 cloned QMGR's that replicate production on a different pair of ZOS images D001 and D002
our development brainstorming test QMGR's are on the same pair of test machine QMGR's and they are called M001 and M002
SYSPlex Distributor will put the iteration on one of the pairs (M001 or M002)
the program has to determine on which ZOS image it is running to do the MQCONN
Dave Adam
Supervalu Home Office
Project Specialist
(952) 828-4736
[EMAIL PROTECTED]
A lone amateur built the Ark.
A large group of professionals built the Titanic
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>01/29/2004 02:15 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: T-Rex distributed systems
Dave,
Two things:
1. The apps should probably be getting the queue manager name form some
external source, e.g. file, table, etc.
2. Test apps that attempt to connect to prod queue managers should probably
be stopped by your security system, e.g. RACF, ACF2, ...
Dave Adam
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
ERVALU.COM> cc:
Sent by: Subject: Re: T-Rex distributed systems
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
01/29/2004 02:51
PM
Please respond
to MQSeries List
the issue is with the playground M00n QMGR's
if they fail to identify the M, then they will be in the clones of
production
Dave Adam
Supervalu Home Office
Project Specialist
(952) 828-4736
[EMAIL PROTECTED]
A lone amateur built the Ark.
A large group of professionals built the Titanic
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rick Tsujimoto
<[EMAIL PROTECTED]> To:
Sent by: MQSeries List [EMAIL PROTECTED]
<[EMAIL PROTECTED]> cc:
Subject: Re:
T-Rex distributed systems
01/29/2004 01:30 PM
Please respond to MQSeries List
If you simply want to connect to the default QMGR on each LPAR, you could
genrate the load module that defines the default queue manager and add that
library to the application's STEPLIB.
Dave Adam
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
ERVALU.COM> cc:
Sent by: Subject: Re: T-Rex
distributed systems
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
01/29/2004 02:19
PM
Please respond
to MQSeries List
here would be a simplistic view of the 2 LPAR's
LPAR D001 D002
QMGR's (1) D001 D002 (both
full repositories for cluster TST1 )
QMGR's(2) M001 M002 (both
full repositories for cluster TST2 )
the default QMGR is D00n on each ZOS image
the low level qualifier is the "n" numeric
by getting the sysname symbolic, all we have to do is overlay the 4th
character to get the MQCONN name
there are partial repositories under the full repositories (that are not
cloned) and they float between LPAR's
this requires additional logic to resolve
not sure if there is an easier way to attack this
D00n QMGR's are clones of production
M00n QMGR's are a playground for programmers
Dave Adam
Supervalu Home Office
Project Specialist
(952) 828-4736
[EMAIL PROTECTED]
A lone amateur built the Ark.
A large group of professionals built the Titanic
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rick Tsujimoto
<[EMAIL PROTECTED]> To:
Sent by: MQSeries List [EMAIL PROTECTED]
<[EMAIL PROTECTED]> cc:
Subject: Re:
T-Rex distributed systems
01/29/2004 10:18 AM
Please respond to MQSeries List
Dave,
What exactly are you referring to when you mention "low level qualifier"?
Is (QMGR name) it the low level qualifier of a data set name? Could you
give an example of the naming convention you're using?
Dave Adam
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
ERVALU.COM> cc:
Sent by: Subject: T-Rex distributed
systems
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
01/29/2004 09:46
AM
Please respond
to MQSeries List
I think the majority of the list'rs are not ZOS based but I have a simple
question about our big PC
when you have multiple cluster environments across multiple LPAR's and the
QMGR's are split up by naming conventions
is a simple check on the low level qualifier the easiest way to
programmatically do MQCONN's
especially when the default QMGR's cannot be resolved in system symbolics
(this does work for the highest level QMGR)
Dave Adam
Supervalu Home Office
Project Specialist
(952) 828-4736
[EMAIL PROTECTED]
A lone amateur built the Ark.
A large group of professionals built the Titanic
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
This communication is confidential and may contain privileged material. If you are not the intended recipient you must not use, disclose, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails.
Thank you.
