Not the best practice. There are steps in the old ServerPac upgrade process that basically says: copy ServerPac supplied etc, run diff against the copy and your existing etc and copy your customized parms/settings to the copy. Mount the copy to use during the upgrade. Or something like that.
On Mon, Jun 5, 2023 at 1:01 PM Pew, Curtis G <curtis....@austin.utexas.edu> wrote: > 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 > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
