That old serverpac process is what I still use for /etc and /var.
Here is a stripped down version of my doc with the steps from z/OS 2.4 to
z/OS 2.5 upgrades. This is for /etc, but /var is the exact same thing. I
actually
do all of this in batch jobs that I mass update from version to version and the
job names are in my doc, but I removed that part.
=============================================================
Copy new /etc into copy of existing etc without overlaying
any existing files.
=============================================================
*** MAKE SURE YOU ARE RUNNING AS SUPERUSER ***
a) Create a copy of physical etc file system, mount at /servz25
b) Mount serverpac ETC at: /service
c) To see differences:
diff -r /service /servz25
d) To do actual copy:
(MAKE SURE YOU ARE RUNNING AS SUPERUSER!)
cd /service
pax -rvwkC -pe * /servz25
e) When done you can compare "live" etc to the
new etc for z/OS 2.5
diff -r /etc /servz25
f) Other manual /etc changes:
** below changes for JAVA_HOME and PFA not needed for
this upgrade, but left steps in as a place holder.
(can do updates to /servz25 while mounted)
Change JAVA_HOME in /servz25/profile (/etc/profile)
from "J8.0" to "Jv.v"
JAVA_HOME=/usr/lpp/java/J8.0
Change /servz25/PFA/ini (/etc/PFA/ini)
from "J8.0" to "Jv.v"
(this is not optional, PFA requires 8.0 31-bit)
g) Unmount the CPAC etc at /service
Unmount the newly created 2.4 etc at /servz25
Best Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
On Mon, 5 Jun 2023 13:41:38 -0500, Michael Babcock <[email protected]>
wrote:
>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 <[email protected]>
>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
>> [email protected]
>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] 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 [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
