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:[email protected]] On Behalf Of Mike Cairns Sent: Friday, February 17, 2017 10:24 AM 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 IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
