Three parmlibs: SYS1.IBM.PARMLIB: The same across 50-odd LPARs across 3 plexes. IBM/usermod maintained. SYS1.PARMLIB: same story. Site maintained. SYS1.PARMLIB.<PLEX> is specific to the plex, but except for the mount statements in BPXPRMxx there's only some transient SLIP members in there. The first two are refreshed monthly from a common source so we're 100% sure they're consistent.
DIAGxx and DEVSUPxx use <plex> suffixes, LOADxx and IEASYMxx have all the LPARs listed. Everything else is through system symbols. Most other products use common parmlibs and system symbols (TWS, TCPIP, JES, SA, etc). And then there's Omegamon... Who knows what's what there... Bart -----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
