Hello,
We use SMPE USERMODs to maintain a SYSRES based filesystem model for /etc and
/var.
At system upgrade time, we have a job that does a rename of existing
filesystems, and a DFDSS copy/rename to build new filesystems based on the
SYSRES based model.
Found that this works for us. many s
gt; > > On occasion, I tried the USS diff to evaluate my running /etc against
> > > > > a new serverpac version. And sometimes to compare the previous
> > > > > serverpac version with the new one.
> > > > >
> > > > > The utility of thi
Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On
Behalf Of kekronbekron
Sent: Tuesday, June 6, 2023 7:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Best practice for /etc and /var when upgrading
Integrating git is not something we as customers need to take on ourselves
(for system upgrade w
On Wed, 7 Jun 2023 12:31:43 +, Seymour J Metz wrote:
>Even if you don't call it service, IBM has updated IPO1.PARMLIB.
>
>
When you order a new serverpac or portable instance. These days it is
called CPAC.PARMLIB. It is customized based on your order. For example,
you won't find Netview d
gt; > -Original Message-
> > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On
> > > > Behalf Of kekronbekron
> > > > Sent: Tuesday, June 6, 2023 7:36 PM
> > > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > > Subject: Re
ew one.
The utility of this exercise varied.
-Original Message-
From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On
Behalf Of kekronbekron
Sent: Tuesday, June 6, 2023 7:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Best practice for /etc and /var when upgrading
Integrating git
une 6, 2023 12:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Best practice for /etc and /var when upgrading
On Tue, 6 Jun 2023 11:26:02 +, Seymour J Metz wrote:
>So not "the generic IBM-provided versions, without any of our
>customizations.". Applying an installation delta to
nal Message-
> > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On
> > Behalf Of kekronbekron
> > Sent: Tuesday, June 6, 2023 7:36 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Best practice for /etc and /var when upgrading
> >
> > In
Behalf Of kekronbekron
> Sent: Tuesday, June 6, 2023 7:36 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Best practice for /etc and /var when upgrading
>
> Integrating git is not something we as customers need to take on ourselves
> (for system upgrade workflows like this).
>
Integrating git is not something we as customers need to take on ourselves (for
system upgrade workflows like this).
It's something best given in a polished manner by IBM, as a part of zOSMF.
And again, getting git ourself is another thing; so the suggestion on IBM
establishing a dependency on gi
I don't know git so I can't really comment. I did google gif diff and see what
you mean
now by a patch.
For one, it seems like overkill. Two, I don't have git diff on z/OS so somehow
I'd have to
get all my existing /etc (and /var) out there to compare what IBM would put out
there
that match
Consider, for example, you upgrade from Ubuntu 20.04 to 22.04, and have updated
the sudoers file.
When upgrading, you get a prompt showing a diff between the new version and
your customized version.
And quoting a bit from your reply...
> compare the distributed /etc to what you already have to s
Thanks to everyone who has replied. I’m saving your responses for the meeting
we’re having with the service provider’s management on Friday. (This was far
from the only issue we had with the upgrade.)
On Jun 6, 2023, at 11:01 AM, Mark Zelden
mailto:m...@mzelden.com>> wrote:
No service ever hi
On Tue, 6 Jun 2023 11:26:02 +, Seymour J Metz wrote:
>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
On Tue, 6 Jun 2023 03:15:46 +, kekronbekron
wrote:
>I do wonder... with git now available, and this being normal USS, maybe zOSMF
>can start formally adopting/requiring git.
>Then, moving updates from these files onto newer versions is a matter of
>applying git patches on the new ones, whe
ubject: 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 eve
eymour 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.U
@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
I do a lot of upgrades for many sites and it's pretty rare that I replace /etc
or /var. I would never do it causally and It does happen VERY occasionally,
but normally you can tell in the apply jobs (for maintenace updates) what has
changed and running DIFF is always a good idea, but I really d
List IBM-MAIN@LISTSERV.UA.EDU On
> > Behalf Of Pew, Curtis G
> > Sent: Monday, June 5, 2023 11:01 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Best practice for /etc and /var when upgrading
> >
> > [EXTERNAL EMAIL]
> >
> > How do people handle /SY
No
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Pew, Curtis G
> Sent: Monday, June 5, 2023 11:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Best practice for /etc and /var when upgrading
>
> [EXTERNAL EMAIL]
>
> How do
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
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.
We use the same physical file systems from release to release and only update
individual files/directories when necessary.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
--- Ori
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 th
25 matches
Mail list logo
