For us, both /etc and /var live their own respective file systems that are not touched by standard migration from SMPE install to prod. Hence there's no danger of overlaying installation values. OTOH, as Shmuel says, the problem is how to propagate an updated install value into production. First of all it would have to be a manual process, but how to know when/whether to perform such an update? I can't suggest an algorithmic way to do this, but I'm not an OMVS whiz by any means.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, February 08, 2018 12:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Best Practices for z/OS Maintenance SMP should not be pointing at the live Unix directories. The real question is how to merge new/changed files in the target file system with production files, whether in /etc and /var or elsewhere. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Dyck, Lionel B. (TRA) <lionel.d...@va.gov> Sent: Thursday, February 8, 2018 2:36 PM To: IBM-MAIN@listserv.ua.edu Subject: Best Practices for z/OS Maintenance A question was asked what the best practices are for installing z/OS maintenance to make sure that the /etc and /var files are not replaced by IBM maintenance? (cross posting to MVS OpenEdition and IBM-Main Listservs) Thank you -------------------------------------------------------------------------- Lionel B. Dyck <sdg>< Mainframe Systems Programmer - TRA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
