Its interesting, because I don’t have any products that give me extra extents 
except what SMS does for me space wise, and I have never increased my dataset 
size allocations.

That being said, my cloning process copies my res volume and ZFS datasets to 
new volumes and resets extents to current used, which is why I never used the 
software deployment and NEVER will in z/OSMF.

I also DEFRAG my RES volumes after an apply and with my 2 - MOD-27, have always 
had enough room, for my 2.2, 2.3 and 2.4 and hopefully for 2.5.  My z/OS 2.2, 
will be replaced in the SYSPLEX.

I apply around 1000 PTF each time, I do RSU upgrades normally twice a year over 
the life of a z/OS release and can say I might have had 10 datasets/ZFS 
expansion, I needed to expand during an APPLY.

This is the least of my concerns/issues for the serverpac.

I think, to say the Saved Config is out of date, is short sided and in 20 years 
I have always used it since serverpac gave me the MERGE and UPGRADE option.  
Fixed anything new to the Serverpac order and was ready to install in a short 
time.    This saves SO MUCH TIME with installation as all I have to do verify, 
make very few updates and install.

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide – Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Marna WALLE
Sent: Tuesday, July 20, 2021 12:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Requests

External Email


Hi Terri,
When adding an Software Instance that you already have (say, z/OS V2.4), you 
are telling z/OSMF the CSI and zones to use.  Those DDDEFs, presumably, will be 
correct with the data set names, volumes, and paths.  Those DDDEFs will be used 
as a model on the incoming z/OS CSI DDDEFs.  That will save you hundreds of 
customizations to do for z/OS V2.5 and beyond.  I've seen many ServerPac saved 
configurations that are stale, and the CSI DDDEFs are the correct and current 
values.  Meaning, that the ServerPac saved configuration can "drift" out of 
accuracy over time, but the CSI DDDEFs had better not. That is what I mean by 
saving time.  Especially when you are basing on a known, accurate, SMP/E 
configuration.

For the shipped configuration data sets (like CPAC.*):  if you add those data 
sets to that Software Instance, then those data sets can be modelled too.  If 
you choose not to, the worst thing is that the 16 CPAC data sets shipped with 
z/OS V2.5, can be modified *en masse* within the z/OSMF interface.  Since they 
are all shipped with a HLQ of CPAC, it is very easy to filter, select, move, 
rename them as a group.  With the z/OS V2.5 Software Instance, they then become 
known and can be modelled with future z/OS Portable Software Instances.

For the catalog:  depending on what catalog options you want - new master cat, 
existing master cat and the data set names you select - the existing structure 
you have on your driving system can be used and detected, should you wish to 
use it.  If you want a new master cat, you will need to supply the name and the 
temporary catalog alias of your choice (aka SSA), just like in the old 
ServerPac.  If you want all your data sets to begin with "ZOSV25", and you have 
that existing HLQ alias going to an existing usercat today, no problem, that 
will be used.  If you want to create a new master catalog, and use "MYSSA" as 
the temporary catalog alias, you'll need to supply that, just like in the old 
ServerPac.  The catalog structure, I see, is similar to how the old ServerPac 
did it.  Although, there is a lot more flexibility, because you can rename any 
data set, and put it in any catalog you want, with only VSAM (including zFS) 
forced to be cataloged.  The old ServerPac had lots of restrictions on what 
could be renamed, and where it had to be cataloged.

-Marna WALLE
z/OS System Install and Upgrade
IBM Poughkeepsie

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
________________________________
 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com>
This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to