We maintain in concatenation order: SYS1.&SYSCLONE.PARMLIB<-- Does Not Roll SYS1.&SYSPLEX.PARMLIB<-- Does Not Roll SYS1.PARMLIB<-- Common Routines or altered routines from IBM.PARMLIB, Rolls SYS1.IBM.PARMLIB<-- Vanilla IBM Shipped Parmlib members NEVER Edited. Rolls SYS1.SYSPROG.PARMLIB<-- Sysprogs testing parmlib at bottom of concatenation so it can never override IPL parms (Note Not all Sysprogs have update access to libraries above this level, only the core MVS team do. Those that don't can use this library )
Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 623 869 5523 Corporate Tieline - 85523 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Nims,Alva John (Al) Sent: Friday, February 17, 2017 10:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL: Re: maintaining PARMLIBs over several sysplexes We have a Sandbox system in it's own sysplex and a primary sysplex with two LPARS. Each LPAR has it's own SYS1.PARMLIB, it used to share and they used the LPAR # as part of the suffix to members, i.e., COMMND10 for LPAR 1, COMMND20 for LPAR 2, .... it is still used that way, but now the SYS1.PARMLIB is unique. We also have a SYS1.SYSRES.PARMLIB that is on the SYSRES volume, cataloged with "******" for the VOLSER, so I can put specific changes based on which set of volumes are IPL'd. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Cairns Sent: Friday, February 17, 2017 10:24 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
