I prefer to have a rotating list of TARGET/DLIB pairs, with symbols keyed to the IPL volser. When I want to promote a configuration from, e.g., TEST to QA, I just IPL.
Note that whatever methodology you you, there will be some bookkeeping associated with it, and cutting corners can be fatal. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Jousma, David [[email protected]] Sent: Thursday, June 11, 2020 12:17 PM To: [email protected] Subject: Re: Separate SMPe environments for maintenance levels I do a similar process. One global zone for a z/os ver.rel, a "maintenance zone", and then a target zone that matches every active SYSRES in my environment. One DLIB zone. Maintenance is only actively applied to the maintenance zone, and when ready to promote that level into use, I have a set of standard cloning jobs that copies the actual sysres to the new SYSRES with appropriate renameu (sysres volser is a part of ZFS container names), copy the SMPE support datasets with renames, and SMPE ZONECOPY from the maintenance zone to a new target zone named to match the sysres describes, and then appropriate zone edits to change dddef volser's/pathnames to match the sysres. This way, you are only every applying maintenance once, you have a target zone that matches the running sysres in the event a fix needs to be applied, etc. Accept processing only occurs AFTER the last system in my complex is running that level of maintenance. SET BDY (&TARGET.TG) . ZCOPY (&SRCZONE.) INTO(&TARGET.TG) . SET BDY(&TARGET.TG) . ZEDIT DDDEF . CHANGE VOLUME(&SOURCE.A, &TARGET.A) . CHANGE PATH('/&SOURCE.A'*, '/&TARGET.A'*). CHANGE DA(SMPE.&ZOSLVL..&SRCZONE..SMPLTS, SMPE.&ZOSLVL..&TARGET.TG.SMPLTS). CHANGE DA(SMPE.&ZOSLVL..&SRCZONE..SMPMTS, SMPE.&ZOSLVL..&TARGET.TG.SMPMTS) . CHANGE DA(SMPE.&ZOSLVL..&SRCZONE..SMPSCDS, SMPE.&ZOSLVL..&TARGET.TG.SMPSCDS) . CHANGE DA(SMPE.&ZOSLVL..&SRCZONE..SMPSTS, SMPE.&ZOSLVL..&TARGET.TG.SMPSTS) . CHANGE DA(SMPE.&ZOSLVL..&SRCZONE..SMPTLOG, SMPE.&ZOSLVL..&TARGET.TG.SMPTLOG) . CHANGE DA(SMPE.&ZOSLVL..&SRCZONE..SMPTLOGA, SMPE.&ZOSLVL..&TARGET.TG.SMPTLOGA) . ENDZONEEDIT . _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 From: "Bill Giannelli" <[email protected]> To: [email protected] Sent: Thursday, June 11, 2020 10:38:23 AM Subject: Separate SMPe environments for maintenance levels I want to setup separate SMPe environments, say 3 for different maintenance levels. One matching production then 2 others for maintenance levels "coming next". My question is, when I what to update my PROD environment with one of the other maintenance levels, do I need to go thru receive, apply, accept that I would have done in the "prior" SMPe environment? Or is there a quicker way to "synch" up the 2 environments? thanks Bill This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- 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
