We run with multiple maintenance levels, and clone to active environments as required.
1. multiple GLOBAL zones - one per product subsystem, some for specific vendors, and others as required. 2. each global zone has multiple target/dlib sets. 3. multiple maintenance target/dlib sets, with a unique HLQ, not SYS%, so that enqueues are never a problem. 4. multiple IPL volume target sets, with one DLIB set per base product level. 5. dynamically generated jobstreams to clone from a maintenance/IPL set to an IPL set, either local or remote. 6. dynamically generated joibstreams to handle changes required when doing upgrade or backout of a new iPL set. currently using 6xMod27 target and 6xMod27 DLIB volumes per set. Have z/OS 2.3 and z/OS 2.4 configurations active running with 6xMod54 volumes for SMPE Global zone support datasets including SMPPTS. Target/DLIB SMPE datasets reside on matching target/dlib volume, names matching VOLSER for unqueueness. All local system changes are coded in USERMODs tied to maintenance environment cycle. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
