We have one parmlib for all our LPARs (actually 2, one for prod lpars, one for 
test/install/sandbox lpars). 
We try to keep the contents of the members equal for all LPARs and specify 
differences b.m.o. system symbolics. 
To facilitate this as much as possible, we added a number of system symbolic to 
the different LPARNAME sections of IEASYM00. E.g. if LPARX runs Subarea 50 and 
LPARY runs Subarea 51, we specify &SA in the parmlib members and the &SA system 
symbolic in the MVSX and MVSY LPARNAME sections of IEASYM00.

Kees.

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Mike Cairns
> Sent: 17 February, 2017 16:24
> To: [email protected]
> Subject: maintaining PARMLIBs over several sysplexes
> 
> Hi all - it's been a long time since I posted a question here, looking
> forward to hearing from you all.
> 
> Question about your local policy/practice:
> 
> When faced with the task of maintaining multiple PARMLIBS over a few
> related sysplexes (sandpit, development, production), do you:
> 
> Prefer to try and keep the contents of each PARMLIB dataset separate,
> and only containing members that are actually referred to on each
> specific sysplex, or
> 
> Prefer to keep all PARMLIB members related to any of the sysplexes
> synchronised across all the copies of PARMLIB - effectively keeping
> PARMLIB contents the same, wherever they are found?
> 
> Some other option?
> 
> 
> Thanks for taking the time,
> 
> Regards - Mike Cairns
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to