| Author |
Message
|
| ctefehinoz |
 Posted: Mon Jul 26, 2010 5:17 pm Post subject: |
 |
|
Apprentice
Joined: 27 Oct 2003
Posts: 29
Location: Australia
|
Bruce,
Hmm..good idea  . I like it because of the blatantly visible versioning factor and I can include it in upgrade doco. Helps too if we have to run mixed versions.
Regards
Ctefehinoz |
|
| Back to top |
|
 |
| JoePanjang |
| Posted: Mon Jul 26, 2010 6:04 pm Post subject: |
|
|
Voyager
Joined: 10 Jul 2002
Posts: 88
Location: Dengkil MALAYSIA
|
'The start of course needs a START QMGR PARM(qmgrZPRM)'
I believed on v7 you have a choice to start qmgr by
/+QMNAME START QMGR. The parm itself included on the mq master proclib.
Havent done the upgrade to v7 but going to start in Oct 2010.
_________________
Every good deed is charity... |
|
| Back to top |
|
|
| ctefehinoz |
| Posted: Mon Jul 26, 2010 6:17 pm Post subject: |
|
|
Apprentice
Joined: 27 Oct 2003
Posts: 29
Location: Australia
|
JoePanjang,
Your syntax is correct, but our shop prefers to use the MVS start -> :Qmname START QMGR PARM(Qmgrparm) so that automation can take of it and no unruly people can issue START's if they aren't "in the know" so to speak.
":qmname" is actually whatever the shop's selected command prefix is.
Regards
Ctefehinoz |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 26, 2010 6:20 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| 'The start of course needs a START QMGR PARM(qmgrZPRM)' |
ZPRM in the member name is not required. From the v6 InfoCenter (and elsewhere):
START QMGR
>>-START QMGR--+-------------------------------------+---------->
'-ENVPARM--(--jcl-substitution--)-----'
.-PARM(CSQZPARM)----------.
>--+-------------------------+---------------------------------><
'-PARM--(--member-name--)-'
PARM(member-name)
The load module that contains the queue manager initialization parameters. member-name is the name of a load module provided by the installation.
_________________
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 |
|
|
| Vitor |
| Posted: Mon Jul 26, 2010 7:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The other common way of achieving much the same thing is to have the version as part of the DSN and include these as a STEPLIB in the queue manager proc.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Tue Aug 10, 2010 11:56 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
| You could also add a USERMOD to SMPE and have your ZPARMs re-assembled when mainteance is applied to MQ. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Thu Aug 12, 2010 10:40 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
In my shop we have a APF loadlib called:
MQSERIES.MQxx.USERLIB
We assemble all the particlulars MQM unique modules into this loadlib. This way we don't have to specify what ZPARM to use. xxxxMSTR and xxxxCHIN steplib to this dataset. So do the IMS MPR's and any batch job using default MQM in their API. The IBM runtimes are LNKLIST'ed and are not required in the STEPLIB's for MSTR and CHIN.
BROWSE MQSERIES.MQL0.USERLIB
Command ===>
Name Prompt Alias-of
_________ CSQBDEFV
_________ CSQQDEFV
_________ CSQZPARM
**End** |
|
| Back to top |
|
|
|
|
