So not "the generic IBM-provided versions, without any of our customizations.". Applying an installation delta to copiesof the IBM /etc and /var as part of the installation process sounds like best practice to me. Of course, you also need procedures for service that hits them.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of rpinion865 [0000042a019916dd-dmarc-requ...@listserv.ua.edu] Sent: Tuesday, June 6, 2023 7:05 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Best practice for /etc and /var when upgrading I came to a new shop at this time last year. Me predecessor did all of the heavy lifting to install z/OS 2.4. Basically, I had to do a little customization, and roll 2.4 into TECH, DEV, and PROD. Fortunately my predecessor documented everything he had done, which made my job much easier. His documentation regarding /etc & /var showed much the same information that Mark Zelden shared earlier, up to showing the output of the diff commands. To answer your question, my predecessor started with the virgin 2.4 /etc and /var and applied all of the changes from the previously customized z/OS 2.2 /etc and /var. Sent with Proton Mail secure email. ------- Original Message ------- On Tuesday, June 6th, 2023 at 6:56 AM, Seymour J Metz <sme...@gmu.edu> wrote: > Then what did he to about the functionality previously done by the > customizations? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of > Pew, Curtis G [curtis....@austin.utexas.edu] > Sent: Monday, June 5, 2023 2:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Best practice for /etc and /var when upgrading > > How do people handle /SYSTEM/etc and /SYSTEM/var when upgrading z/OS? In the > past we’ve had these filesystems on an auxiliary volume, so that they > remained the same during any upgrades unless we deliberately changed > something. For our last upgrade (this past weekend) our management outsourced > the upgrade to a 3rd party service provider, and the sysprog doing it > configured completely new filesystems for these that were the generic > IBM-provided versions, without any of our customizations. He claims this is a > best practice. What say ye? > > > -- > Curtis Pew > ITS Campus Solutions > curtis....@austin.utexas.edu > > > > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
