We use a common parmlib for those members that can be the same and concatenate an lpar specific one for those that can't. However, we only have to manage 4 lpars, so it's not too onerous a task.
-- Donald Grinsell, Systems Programmer Enterprise Technology Services Bureau SITSD/Montana Department of Administration 406.444.2983 (D) "In the end, we will remember not the words of our enemies, but the silence of our friends." ~ Martin Luther King, Jr. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Mike Cairns > Sent: Friday, February 17, 2017 8: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
