| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Relationship of MQ, CICS and batch job |
« View previous topic :: View next topic » |
| Author |
Message
|
| karmen |
 Posted: Sat Mar 19, 2011 3:38 am Post subject: Relationship of MQ, CICS and batch job |
 |
|
Newbie
Joined: 29 Sep 2009
Posts: 9
|
When perform MQ upgrade in z/OS, as LPA should placed the latest one, so in SYS1.PARMLIB(LPALSTxx), the libraries of SCSQLINK and SCSQSNLE already changed from V6 to V7. But as the MQs in the same LPAR will be upgraded one by one (control by the STEPLIB of the MSTR and CHIN), that means in a period of time, 2 versions of MQ will be coexist and the libraries placed in the LNKLST will be kept in V6 until all MQ have been upgraded to V7.
So I would like to know:
1. If a CICS directly connected to a MQ, if that MQ perform upgrade, does the MQ libraries concat in the CICS's STEPLIB and DFHRPL can still keep in V6 or it must also need to change to V7?
2. If a MQ need to fallback, any actions that need to perform in CICS at the same time?
3. When I should change the version of the MQ libraries concat in the batch job?
Thanks. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat Mar 19, 2011 7:47 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The WMQ modules that live in LPA are the WMQ early code. In order to run multiple versions/releases of WMQ, the early code must be at the most current WMQ version/release. If you are to run V6 and V7 concurrently, then the early code must be V7.
WMQ dataset DD statements are version-specific. The WMQ startup procs DD statements for MSTR and CHIN need to be those of the WMQ version/release for that queue manager. So, for a V6 qmgr, the DD statements in STEPLIB need to be V6.
The CICS startup procs WMQ DD statements need to be those of the WMQ version/release of the queue manager the CICS region connects to. So, if CICS is connecting to a V6 queue manager, the WMQ DD statements need to be V6.
Please refer to the WMQ for z/OS System Setup manual on how to set up WMQ and CICS.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| karmen |
| Posted: Sat Mar 19, 2011 7:11 pm Post subject: |
|
|
Newbie
Joined: 29 Sep 2009
Posts: 9
|
Based on the reply, if CICS is connecting to a V6 queue manager, the WMQ DD statements concat in CICS need to be V6. That means if CICS is connecting to a V7 QM, the WMQ DD statements concat in CICS also need to be V7.
How about the batch job? As we are using MQ to perform batch file transfer, so does the WMQ DD statments of the JCL also need to depend on to the WMQ version/release of the QM the batch job connects to? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Mar 19, 2011 10:25 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Having read the relevant sections of the WMQ for z/OS System Setup manual, what did you discover about setting up WMQ for batch?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Mar 20, 2011 11:46 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
in addition, read also the migration guide. it tells you how to deal with that.
in your case, i would keep LNKLST to MQV6 till all queuemanagers in that LPAR are migrated to V7, then switch LNKLST (as the migration document reads that the programs compiles with v6 will run with v7 without recompile) to V7.
however, its up to you 
and consume the migration information ....
_________________
Regards, Butcher |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Mar 21, 2011 4:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Karmen, I'm not sure about your knowledge and experience with z/OS. LNKLST is very different from LPA.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Mar 21, 2011 5:18 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
he described the situation very well. he has updated lpalst with the mqv7 early code, and now he is talking about the lnklst .... so i think he knows the difference. its just about the lnklst now.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| karmen |
| Posted: Mon Mar 21, 2011 5:30 am Post subject: |
|
|
Newbie
Joined: 29 Sep 2009
Posts: 9
|
Thanks for your information, Mr Butcher. In my case, I plan to use the following approach.
As there are several WMQ libraries concat in the STEPLIB of the CICS's JCL and the application job's JCL, e.g. SCSQAUTH, SCSQANLE, SCSQLOAD... etc. So I will:
1. Change the MQ version to V7 in LPA
2. Place both WMQ V6 and V7 libraries in APF
3. Keep the WMQ V6 in LNKLST
During QM migration:
1. Change the WMQ libraries concat in CICS to V7
2. Keep the WMQ libraries concat in the application job's JCL in V6
When confirm migration success:
1. Remove all V6 libraries in APF
2. Change the LNKLST version to V7
3. Change the WMQ libraries concat in the application job's JCL to V7
** Besides, I know the application program compile in V6 is upward compatible, so I no need to compile or linkedit any applications during migration.
Last edited by karmen on Mon Mar 21, 2011 6:17 am; edited 2 times in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Mar 21, 2011 5:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Yep, I suppose.
Many shops are running more than one version/release of CICS, MQ, and other subsystems.
I don't put any of the product-related datasets in LNKLST. Rather, I STEPLIB them in the startup procs.
As Mr. Butcher says, it's a choice.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mainopr |
| Posted: Mon Mar 21, 2011 5:52 am Post subject: |
|
|
Newbie
Joined: 21 Mar 2011
Posts: 1
|
When there is hundred of startup procs / batch jobs, it may not be a good idea to "STEPLIB" them.  |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Mar 21, 2011 5:58 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
in a different shop they used alias names to point either to this or to that mq version. in combination with steplibs you can switch from one version to the other without touching a single line of jcl.
however, this can also be archieved with the lnklst and no steplib. just a different approach.
however, for the mq started tasks and for everything, that is "very close" to the queuemanager, i have a steplib (e.g. for the DLQ Handler, trigger monitor). For everything else (application jobs), we dont use steplib but lnklst.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Mar 21, 2011 8:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mainopr wrote: |
| When there is hundred of startup procs / batch jobs, it may not be a good idea to "STEPLIB" them. |
Why? The device allocation process is identical whether JOBLIB'd, STEPLIB'd or LNKLST'd.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Tue Mar 22, 2011 7:29 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Lot's a different ways to fry this chicken.
We LNKLST the MQ libs. For CICS and IMS DD's for module searches (like DFHRPL) the datasets never change. SYS1.SCSQLOAD, SYS1.SCSQAUTH, etc. So CICS and IMS always pickup the version MQ is running with no JCL changes. Batch jobs pickup the required modules because of the LNKLST libs for MQ.
Another division in our company sets the MQ version number in the user defined SYSTEM SYMBOLICs. So in the started tasks like MQ, CICS, IMS all reference datasets like SYS1.SCSQLOAD..&MQREL where &MQREL is a site SYSTEM SYMBOLIC set at IPL for the MQ release contained in the datasets. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 22, 2011 8:12 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Generally, no animals are injured or killed in this process.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Tue Mar 22, 2011 8:14 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
