Re: Serverpac installs January 2022 and beyond - Issues Updated

[Marna WALLE]

Hi Bob,
Yes, the z/OS V2.5 Upgrade Workflow is available in PTF(s) on z/OS V2.3 and 
V2.4, and in V2.5, and can be found in /usr/lpp/bcp/upgrade/.  It is no longer 
in github. The latest level of the Workflow is found in APAR OA61406 - which is 
the level that contains all the links to the GA z/OS V2.5 books.  It also 
contains some comments that our early customers had, which we wanted to include 
in that refresh.  PTFs will close any day now!

All the PTFs associated with the z/OS V2.5 Upgrade Workflow will be identified 
with the FIXCAT IBM.Coexistence.z/OS.V2R5, so you can easily install them along 
with any applicable release coexistence necessary.  If you've already installed 
coexistence PTFs, chances are you have the initial release of the Workflow 
(APAR OA60711) which was available right at the z/OS V2.5 Preview announce.  
The initial release only could use the z/OS V2.4 book links, since the V2.5 
books were not yet available.  

This z/OS Upgrade Workflow is intended to be used before you do the z/OS V2.5 
installation.  With that in mind, it is not included in the z/OS V2.5 
ServerPac-supplied workflows (unless you count included in the V2.5 root zFS, 
which is a little too late to start looking at upgrade actions). 

Remember, as we refresh the Upgrade Workflow with new or changed information in 
PTFs, you do not need to restart the Workflow from scratch and lose your 
progress. Use the "Create new based on existing" option z/OSMF Workflows.  That 
will take your partially (or fully) completed Workflow from before, and create 
a new "merged" Workflow for you.  Your steps you have completed and which were 
not changed, will remain completed.   

-Marna WALLE
z/OS System Installation 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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Kurt J. Quackenbush]

> What about datasets that are not in the CSI, e.g., CPAC.*?

When you use a model to initialize the deployment configuration, data sets 
not managed by SMP/E, like the CPAC.* data sets, won't be initialized to 
your existing data set naming conventions.  The same is true for new data 
sets that don't have a match in the model.  They get initialized with the 
data set name used by the ServerPac production process.  On the Data Sets 
page in the deployment configuration wizard data sets that did not have a 
match in the model are identified by a message in the row, so its easy to 
determine which data sets need some attention.  However, those data sets 
should be few in comparison to all of those that will get matched with the 
model.

> > > I do echo Terri's sentiments that there should be a way to mostly
> > > seed a new z/OSMF instance whether there is a utility that reads the
> > > last saved custompac config or somehow scans your sysres.
> > 
> > That is exactly what z/OSMF offers!  You can "model" your installation
> > configuration on your existing installed software.  For example when
> > installing z/OS 2.5, simply define your existing z/OS 2.4 (or 2.3) as 
a
> > Software Instance.  (Use the Software Instance -> Add action, specify 
the
> > global zone CSI, select the target zones from that global, and that's 
it!)
> >  During the deployment you can select this Software Instance as your 
model
> > and z/OSMF will analyze your DDDEF entries in your existing CSI to
> > determine your desired data set names and match them up with the new
> > software as much as possible.
> > 
> > Honestly, we did try to help you avoid a bunch of changes in the
> > configuration.  Perhaps we need to advertise it more, but the Model
> > function is your friend.

Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management
Chuck Norris never uses CHECK when he applies PTFs.


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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Seymour J Metz]

What about datasets that are not in the CSI, e.g., CPAC.*?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Kurt J. Quackenbush 
Sent: Wednesday, October 27, 2021 3:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

> I too ordered V2.5 in the "window" where you still have a choice on
> custompac dialogs or z/OSMF.   I opted to go custompac one more time.
>
> I do echo Terri's sentiments that there should be a way to mostly
> seed a new z/OSMF instance whether there is a utility that reads the
> last saved custompac config or somehow scans your sysres.

That is exactly what z/OSMF offers!  You can "model" your installation
configuration on your existing installed software.  For example when
installing z/OS 2.5, simply define your existing z/OS 2.4 (or 2.3) as a
Software Instance.  (Use the Software Instance -> Add action, specify the
global zone CSI, select the target zones from that global, and that's it!)
 During the deployment you can select this Software Instance as your model
and z/OSMF will analyze your DDDEF entries in your existing CSI to
determine your desired data set names and match them up with the new
software as much as possible.

Honestly, we did try to help you avoid a bunch of changes in the
configuration.  Perhaps we need to advertise it more, but the Model
function is your friend.

Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management
Chuck Norris never uses CHECK when he applies PTFs.


--
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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Kurt J. Quackenbush]

> I too ordered V2.5 in the "window" where you still have a choice on 
> custompac dialogs or z/OSMF.   I opted to go custompac one more time.
> 
> I do echo Terri's sentiments that there should be a way to mostly 
> seed a new z/OSMF instance whether there is a utility that reads the
> last saved custompac config or somehow scans your sysres.

That is exactly what z/OSMF offers!  You can "model" your installation 
configuration on your existing installed software.  For example when 
installing z/OS 2.5, simply define your existing z/OS 2.4 (or 2.3) as a 
Software Instance.  (Use the Software Instance -> Add action, specify the 
global zone CSI, select the target zones from that global, and that's it!) 
 During the deployment you can select this Software Instance as your model 
and z/OSMF will analyze your DDDEF entries in your existing CSI to 
determine your desired data set names and match them up with the new 
software as much as possible.

Honestly, we did try to help you avoid a bunch of changes in the 
configuration.  Perhaps we need to advertise it more, but the Model 
function is your friend.

Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management
Chuck Norris never uses CHECK when he applies PTFs.


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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Keith Gooding]

Hi Kurt. In answer to your question about my previous post:

We put the SMP/E target zone datasets on the target volume. The names in this 
case are SMPE.ZOS250.MVST250.* which are unique in the system. The CSI is VSAM 
so it is directly cataloged. The installation process indirectly catalogs the 
non-VSAM ones and I assume that the DdDEFs for them include the specific 
volser. However when handling these datasets it is more convenient if they are 
directly cataloged. It is possible, so that is what we do (post install).

I also mentioned that I would like to be able to create a 2-level alias and 
associated catalog. That is because we use OMVS.ZOS250 as the qualifier for 
target zone file systems, and OMVS for most other file systems.

Not necessarily all logical or the best practice but we are where we are. 

Keith Gooding

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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Kurt J. Quackenbush]

> Wanted to add a few other comments
> Since IBM is forcing everyone to z/OSMF with 2.5, not excited for 
> this but It seems to work pretty well, except for everything that 
> cant see it doing behind the scenes. It seems this is a ton of 
> catalog look-ups to validate nothing exist.
> 
> But then in the IZUD04UZ job you delete everything anyhow. So why 
> validate it in the workflows?  I fail because my SMPE datasets are 
> already allocated, because I installed thru a SERVERPAC.

When you use the z/OSMF Deployment action to install a ServerPac, you're 
telling z/OSMF you want to install the software provided in that 
ServerPac.  To "install software" means z/OSMF will create data sets. 
Therefore, before it attempts to create any data sets, it ensures there 
are no unintended collisions with existing data sets on your specified 
volumes and in the catalogs.  You either have to modify the data set names 
in the configuration, or rename or delete the existing data sets so there 
are no unintended collisions.

If you want z/OSMF to consider such collisions to be intended, then tell 
z/OSMF to delete the existing data sets.  You do this either by selecting 
a software instance to be replaced that contains the subject data sets, or 
by indicating the target volume that contains the subject data sets will 
be initialized.  Both options result in z/OSMF considering such collisions 
to be intended, and the existing data sets will get deleted explicitly.

> Lastly since the direction in 2.5 for z/OSMF, now everyone will have
> a valid instance going forward.  So you should still provide a way 
> to extract the migration action XML, so that for 2.5 only its 
> available outside.

What "migration action XML" are you talking about?  The customization 
workflows supplied in the ServerPac?  If so, those workflows are not 
designed to be performed stand alone.  They are designed to be performed 
from Software Management when you install the ServerPac PSWI.

Kurt Quackenbush -- IBM,  z/OS SMP/E and z/OSMF Software Management
Chuck Norris never uses CHECK when he applies PTFs.



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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Dave Jousma]

Oh, and in the custompac dialogs, there are exactly 4 jobs that I run after 
resolving new datasets that came along with the new release.

- allocate and catalog the datasets (ALLOCDS)
- restore the datasets (RESTORE)
- update SMPE DDDEFS (UP)
- and a modified version of RECATALOG datasets to Target(RECATDS) to only run 
the IEHPROGM steps

Then onto applying any usermods.

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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Dave Jousma]

>Hey Dave
> I ordered both, and you are right in 4 hours I had my z/OS loaded and IPLed 
> at least the initial IPL in test.  However
>
>I wanted to try z/OSMF and I actually like the dataset naming flexibility, 
>much better than the dialogs and Alias's discovery.
>
>But all the background dataset checking that use to be done in the first 
>SERVERPAC job, IE validate your configuration/Catalog setup, that is driving 
>me insane.
>
>That and in my mind when I build a software instance, not everything that the 
>SERVERPAC downloads is copied/used.
>
>IBM seems to force copying the CPAC and SMPE files, when I only want the SYS1 
>datasets and OMVS.
>
>Lastly and there are many takes on this from SYSTEM Programmers, But I only 
>ever have one DISTRIBUTION zone and it matches my 2-3 target zones/RES vol 
>sets.
>
>This is because I always want to make sure no-one restores from the wrong 
>DLIBS..  So I don’t ever copy these when I clone either.

Again,  I havent played with the zOSMF version yet, but it sounds like we do a 
similar cloning process.   My SYSRES volumes are mod-54's and ONLY contain the 
target datasets including OMVS with sysres volser as part of the dsn.   All the 
SMPE, CPAC, junk I just dont need get installed on the DLIB volume.

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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Completely agree mostly..  I just want the option of some flexibility so I can 
still manipulate my layout after the fact not in the workflows.

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  On Behalf Of 
Richards, Robert B. (CTR)
Sent: Wednesday, October 27, 2021 1:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Shields up!

This old dog wants to learn a new trick. I'm tired of the ISPF-based dialog 
install after doing ServerPac installs for several decades. Marna's NewEra 
two-part presentations were outstanding.

She spoke of taking a coworker with no experience with either and getting a 
running system up in three days! Granted, she mentored the individual, but 
still!

And aren't the migration workflows available as PTFs separate from the Software 
Instance? I am currently waiting for that PTF to close to get the most updated 
version of the workflow to review prior to actually ordering and downloading 
z/OS 2.5.

Bob



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Dave Jousma
Sent: Wednesday, October 27, 2021 1:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

I too ordered V2.5 in the "window" where you still have a choice on custompac 
dialogs or z/OSMF.   I opted to go custompac one more time.

I do echo Terri's sentiments that there should be a way to mostly seed a new 
z/OSMF instance whether there is a utility that reads the last saved custompac 
config or somehow scans your sysres.   That will definitely soften the blow for 
moving over.Us old timers, can whip through the old dialogs in less than a 
day, and be pretty much ready to IPL.  I understand the need to modernize the 
environment for the next wave.

--
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

 [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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Hey Dave
 I ordered both, and you are right in 4 hours I had my z/OS loaded and IPLed at 
least the initial IPL in test.  However

I wanted to try z/OSMF and I actually like the dataset naming flexibility, much 
better than the dialogs and Alias's discovery.

But all the background dataset checking that use to be done in the first 
SERVERPAC job, IE validate your configuration/Catalog setup, that is driving me 
insane.

That and in my mind when I build a software instance, not everything that the 
SERVERPAC downloads is copied/used.

IBM seems to force copying the CPAC and SMPE files, when I only want the SYS1 
datasets and OMVS.

Lastly and there are many takes on this from SYSTEM Programmers, But I only 
ever have one DISTRIBUTION zone and it matches my 2-3 target zones/RES vol sets.

This is because I always want to make sure no-one restores from the wrong 
DLIBS..  So I don’t ever copy these when I clone either.

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  On Behalf Of 
Dave Jousma
Sent: Wednesday, October 27, 2021 1:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


I too ordered V2.5 in the "window" where you still have a choice on custompac 
dialogs or z/OSMF.   I opted to go custompac one more time.

I do echo Terri's sentiments that there should be a way to mostly seed a new 
z/OSMF instance whether there is a utility that reads the last saved custompac 
config or somehow scans your sysres.   That will definitely soften the blow for 
moving over.Us old timers, can whip through the old dialogs in less than a 
day, and be pretty much ready to IPL.  I understand the need to modernize the 
environment for the next wave.

--
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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Richards, Robert B. (CTR)]

Shields up!

This old dog wants to learn a new trick. I'm tired of the ISPF-based dialog 
install after doing ServerPac installs for several decades. Marna's NewEra 
two-part presentations were outstanding.

She spoke of taking a coworker with no experience with either and getting a 
running system up in three days! Granted, she mentored the individual, but 
still!

And aren't the migration workflows available as PTFs separate from the Software 
Instance? I am currently waiting for that PTF to close to get the most updated 
version of the workflow to review prior to actually ordering and downloading 
z/OS 2.5.

Bob



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Dave Jousma
Sent: Wednesday, October 27, 2021 1:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

I too ordered V2.5 in the "window" where you still have a choice on custompac 
dialogs or z/OSMF.   I opted to go custompac one more time.

I do echo Terri's sentiments that there should be a way to mostly seed a new 
z/OSMF instance whether there is a utility that reads the last saved custompac 
config or somehow scans your sysres.   That will definitely soften the blow for 
moving over.Us old timers, can whip through the old dialogs in less than a 
day, and be pretty much ready to IPL.  I understand the need to modernize the 
environment for the next wave.

--
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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Dave Jousma]

I too ordered V2.5 in the "window" where you still have a choice on custompac 
dialogs or z/OSMF.   I opted to go custompac one more time.

I do echo Terri's sentiments that there should be a way to mostly seed a new 
z/OSMF instance whether there is a utility that reads the last saved custompac 
config or somehow scans your sysres.   That will definitely soften the blow for 
moving over.Us old timers, can whip through the old dialogs in less than a 
day, and be pretty much ready to IPL.  I understand the need to modernize the 
environment for the next wave.

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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Also Kurt, again I have never used software deployment, but the only datasets I 
ever replicate for a close are SYS1.* and my OMVS files.

I tried to build a new instance and again it fails.  Why are you validating in 
the workflows???

At this point I give up..

error
Generation of the deployment jobs failed. Target data set "CPAC.ZOS25.SAMPLIB" 
has the same name as a data set already cataloged on the target system.
IZUD9702E
Oct 27, 2021, 1:04:35 PM
error
Generation of the deployment jobs failed. Target data set "CPAC.ZOS25.LINKLIB" 
has the same name as a data set already cataloged on the target system.
IZUD9702E
Oct 27, 2021, 1:04:34 PM

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  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, October 27, 2021 12:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


NVM,  It how you select/filter the names that changes if you can modify or not..

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  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, October 27, 2021 12:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Wanted to add a few other comments
Since IBM is forcing everyone to z/OSMF with 2.5, not excited for this but It 
seems to work pretty well, except for everything that cant see it doing behind 
the scenes. It seems this is a ton of catalog look-ups to validate nothing 
exist.

But then in the IZUD04UZ job you delete everything anyhow. So why validate it 
in the workflows?  I fail because my SMPE datasets are already allocated, 
because I installed thru a SERVERPAC.

This would be all good, because I just wasn't planning on running any of the 
jobs, unless I saw something I needed for customizations.

But again you don't allow that and stop with errors.

Lastly since the direction in 2.5 for z/OSMF, now everyone will have a valid 
instance going forward.  So you should still provide a way to extract the 
migration action XML, so that for 2.5 only its available outside.

PPS..  If you do respond how do the workflow variables for in install portable 
instance to mirror a production names??

I cant use a filter to change the dataset names, However if I select each one 
separately, I can which would take forever.

Software Management > Portable Software Instances > Deployments > Deployment 
Checklist > Configure Deployment >Modify Modify Data Sets Enter the data set 
name or qualifiers to use for the selected data sets.
Common data set qualifiers: Example data set name:
From:   SYS1SSA.SYS1.SICELPASYS1SSA.SYS1.SICELPA
To:
SYS1.SICELPA


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  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, October 27, 2021 9:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Hi Kurt,
  There are lots of things I dislike about black boxes and not being able to 
take things on blind faith.

In my 39 years as a system programmer that's gotten me into trouble exactly 
once before I said I just will not run anything without seeing the JCL.

So I pity the newer z/OS folks, because you have puts steps in to validate what 
you generate should run. But that's not always a good assumption. 
Invalid/duplicate issue might only be a temporary condition.

I use a process to roll out software by having my clone jobs already setup, 
between ZA2x11T and ZB2x11T zones for the last 21 years very successfully.

I control the software names in my batch jobs, because of nuances in the 
serverpac dialogs. Now you have removed most of those issues in z/OSMF but you 
added new stops to verify/validate all datasets names being allocated.  Good, 
or Bad, I might want to change things AFTER the fact that I missed, instead of 
re-driving thru the dialogs/screens.  I would be nice here to just generate the 
jobs period with no validation steps as you generate the jobs.

You could always have an option to validate whats generated or NOT. With all 
the standard disclaimersetc

So having NEVER used z/OSMF for software deployments because it was just way to 
cumbersome and time consuming to build for 107 LPARS, like at chase or even 
here at ACI, I have 6 lpars.  Again build once and clone X number of times.

So I am stuck in the z/OSMF now, because I cant build/use the instance of z/OS 

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

NVM,  It how you select/filter the names that changes if you can modify or not..

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  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, October 27, 2021 12:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Wanted to add a few other comments
Since IBM is forcing everyone to z/OSMF with 2.5, not excited for this but It 
seems to work pretty well, except for everything that cant see it doing behind 
the scenes. It seems this is a ton of catalog look-ups to validate nothing 
exist.

But then in the IZUD04UZ job you delete everything anyhow. So why validate it 
in the workflows?  I fail because my SMPE datasets are already allocated, 
because I installed thru a SERVERPAC.

This would be all good, because I just wasn't planning on running any of the 
jobs, unless I saw something I needed for customizations.

But again you don't allow that and stop with errors.

Lastly since the direction in 2.5 for z/OSMF, now everyone will have a valid 
instance going forward.  So you should still provide a way to extract the 
migration action XML, so that for 2.5 only its available outside.

PPS..  If you do respond how do the workflow variables for in install portable 
instance to mirror a production names??

I cant use a filter to change the dataset names, However if I select each one 
separately, I can which would take forever.

Software Management > Portable Software Instances > Deployments > Deployment 
Checklist > Configure Deployment >Modify Modify Data Sets Enter the data set 
name or qualifiers to use for the selected data sets.
Common data set qualifiers: Example data set name:
From:   SYS1SSA.SYS1.SICELPASYS1SSA.SYS1.SICELPA
To:
SYS1.SICELPA


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  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, October 27, 2021 9:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Hi Kurt,
  There are lots of things I dislike about black boxes and not being able to 
take things on blind faith.

In my 39 years as a system programmer that's gotten me into trouble exactly 
once before I said I just will not run anything without seeing the JCL.

So I pity the newer z/OS folks, because you have puts steps in to validate what 
you generate should run. But that's not always a good assumption. 
Invalid/duplicate issue might only be a temporary condition.

I use a process to roll out software by having my clone jobs already setup, 
between ZA2x11T and ZB2x11T zones for the last 21 years very successfully.

I control the software names in my batch jobs, because of nuances in the 
serverpac dialogs. Now you have removed most of those issues in z/OSMF but you 
added new stops to verify/validate all datasets names being allocated.  Good, 
or Bad, I might want to change things AFTER the fact that I missed, instead of 
re-driving thru the dialogs/screens.  I would be nice here to just generate the 
jobs period with no validation steps as you generate the jobs.

You could always have an option to validate whats generated or NOT. With all 
the standard disclaimersetc

So having NEVER used z/OSMF for software deployments because it was just way to 
cumbersome and time consuming to build for 107 LPARS, like at chase or even 
here at ACI, I have 6 lpars.  Again build once and clone X number of times.

So I am stuck in the z/OSMF now, because I cant build/use the instance of z/OS 
2.5 because everything still has the SYS1SSA or SMPESSA, etc HLQ's.  I have 
already renamed everything to SYS1., SMPE. Or CPAC.  So its ready for 
production, but the workflows and variables don't reflect the PROD names.

In-Fact even if I say build a NEW instance I cant change the source so it fails 
because those names don't exist.  I have tried a few things and cant get around 
this.

Lastly all I really want is the migration actions, but instead you hid, it 
seems until sometime later in the workflows.

You also for the customer to define their previous release 2.3 and 2.4 in my 
case, so that you can build a checklist.  I sortof get that, but since I don't 
have anything primed its extra steps to get it to work.

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  On Behalf Of 
Kurt J. Quackenbush
Sent: Wednesday, October 27, 2021 8:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Wanted to add a few other comments
Since IBM is forcing everyone to z/OSMF with 2.5, not excited for this but It 
seems to work pretty well, except for everything that cant see it doing behind 
the scenes. It seems this is a ton of catalog look-ups to validate nothing 
exist.

But then in the IZUD04UZ job you delete everything anyhow. So why validate it 
in the workflows?  I fail because my SMPE datasets are already allocated, 
because I installed thru a SERVERPAC.

This would be all good, because I just wasn't planning on running any of the 
jobs, unless I saw something I needed for customizations.

But again you don't allow that and stop with errors.

Lastly since the direction in 2.5 for z/OSMF, now everyone will have a valid 
instance going forward.  So you should still provide a way to extract the 
migration action XML, so that for 2.5 only its available outside.

PPS..  If you do respond how do the workflow variables for in install portable 
instance to mirror a production names??

I cant use a filter to change the dataset names, However if I select each one 
separately, I can which would take forever.

Software Management > Portable Software Instances > Deployments > Deployment 
Checklist > Configure Deployment >Modify
Modify Data Sets
Enter the data set name or qualifiers to use for the selected data sets.
Common data set qualifiers: Example data set name:
From:   SYS1SSA.SYS1.SICELPASYS1SSA.SYS1.SICELPA
To:
SYS1.SICELPA


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  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, October 27, 2021 9:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Hi Kurt,
  There are lots of things I dislike about black boxes and not being able to 
take things on blind faith.

In my 39 years as a system programmer that's gotten me into trouble exactly 
once before I said I just will not run anything without seeing the JCL.

So I pity the newer z/OS folks, because you have puts steps in to validate what 
you generate should run. But that's not always a good assumption. 
Invalid/duplicate issue might only be a temporary condition.

I use a process to roll out software by having my clone jobs already setup, 
between ZA2x11T and ZB2x11T zones for the last 21 years very successfully.

I control the software names in my batch jobs, because of nuances in the 
serverpac dialogs. Now you have removed most of those issues in z/OSMF but you 
added new stops to verify/validate all datasets names being allocated.  Good, 
or Bad, I might want to change things AFTER the fact that I missed, instead of 
re-driving thru the dialogs/screens.  I would be nice here to just generate the 
jobs period with no validation steps as you generate the jobs.

You could always have an option to validate whats generated or NOT. With all 
the standard disclaimersetc

So having NEVER used z/OSMF for software deployments because it was just way to 
cumbersome and time consuming to build for 107 LPARS, like at chase or even 
here at ACI, I have 6 lpars.  Again build once and clone X number of times.

So I am stuck in the z/OSMF now, because I cant build/use the instance of z/OS 
2.5 because everything still has the SYS1SSA or SMPESSA, etc HLQ's.  I have 
already renamed everything to SYS1., SMPE. Or CPAC.  So its ready for 
production, but the workflows and variables don't reflect the PROD names.

In-Fact even if I say build a NEW instance I cant change the source so it fails 
because those names don't exist.  I have tried a few things and cant get around 
this.

Lastly all I really want is the migration actions, but instead you hid, it 
seems until sometime later in the workflows.

You also for the customer to define their previous release 2.3 and 2.4 in my 
case, so that you can build a checklist.  I sortof get that, but since I don't 
have anything primed its extra steps to get it to work.

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  On Behalf Of 
Kurt J. Quackenbush
Sent: Wednesday, October 27, 2021 8:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


> Actually now I was totally able to customize all my dataset names,
> which is really great. It is time consuming because I basically had to
> change everything.

Glad to hear you were able to customize the data set names to your liking.
 As already mentioned, next time I encourage you to use a Model and z/OSMF will 
use your existing data set name conventions as much as possible.

&g

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Hi Kurt,
  There are lots of things I dislike about black boxes and not being able to 
take things on blind faith.

In my 39 years as a system programmer that's gotten me into trouble exactly 
once before I said I just will not run anything without seeing the JCL.

So I pity the newer z/OS folks, because you have puts steps in to validate what 
you generate should run. But that's not always a good assumption. 
Invalid/duplicate issue might only be a temporary condition.

I use a process to roll out software by having my clone jobs already setup, 
between ZA2x11T and ZB2x11T zones for the last 21 years very successfully.

I control the software names in my batch jobs, because of nuances in the 
serverpac dialogs. Now you have removed most of those issues in z/OSMF but you 
added new stops to verify/validate all datasets names being allocated.  Good, 
or Bad, I might want to change things AFTER the fact that I missed, instead of 
re-driving thru the dialogs/screens.  I would be nice here to just generate the 
jobs period with no validation steps as you generate the jobs.

You could always have an option to validate whats generated or NOT. With all 
the standard disclaimersetc

So having NEVER used z/OSMF for software deployments because it was just way to 
cumbersome and time consuming to build for 107 LPARS, like at chase or even 
here at ACI, I have 6 lpars.  Again build once and clone X number of times.

So I am stuck in the z/OSMF now, because I cant build/use the instance of z/OS 
2.5 because everything still has the SYS1SSA or SMPESSA, etc HLQ's.  I have 
already renamed everything to SYS1., SMPE. Or CPAC.  So its ready for 
production, but the workflows and variables don't reflect the PROD names.

In-Fact even if I say build a NEW instance I cant change the source so it fails 
because those names don't exist.  I have tried a few things and cant get around 
this.

Lastly all I really want is the migration actions, but instead you hid, it 
seems until sometime later in the workflows.

You also for the customer to define their previous release 2.3 and 2.4 in my 
case, so that you can build a checklist.  I sortof get that, but since I don't 
have anything primed its extra steps to get it to work.

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  On Behalf Of 
Kurt J. Quackenbush
Sent: Wednesday, October 27, 2021 8:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


> Actually now I was totally able to customize all my dataset names,
> which is really great. It is time consuming because I basically had to
> change everything.

Glad to hear you were able to customize the data set names to your liking.
 As already mentioned, next time I encourage you to use a Model and z/OSMF will 
use your existing data set name conventions as much as possible.

> Now I hit a few things, because its always checking names in the
> background..  So when it says its going to build jobs, it lies, its
> actually verifying names first.  So because I already installed z/OS
> 2.5 with a serverpac, I would like to bypass a few things and it will
> not let me.  So back to adding a SSA for my duplicates to get thru the
> screens.

I'd like to understand this comment better.  z/OSMF does indeed verify the 
information you specified in the configuration before generating the jobs, such 
as data set names and locations.  Mostly it ensures there is not already a same 
named data set on a specified volume or in a catalog.  Are you saying z/OSMF 
found a volume or catalog collision when in fact there was no collision?  If 
so, can you elaborate?  For example, did you select to create a new master 
catalog?  Are you using indirect cataloging for your existing data sets, and 
did you tell z/OSMF you want to indirectly catalog the new data sets?  Did you 
tell z/OSMF to create data sets on a particular volume?

Kurt Quackenbush -- IBM,  z/OS SMP/E and z/OSMF Software Management

Chuck Norris never uses CHECK when he applies PTFs.

>



--
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 

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Kurt J. Quackenbush]

> I still have some gripes but these occurred also with the old dialogue:

> - SMPE.ZOS250.* non-VSAM datasets on the sysres are indirectly 
> cataloged because indirect cataloging by the installation dialogue 
> works at the volume level.

Can you expound on this comment a bit?  Are you saying you'd like some of 
the data sets on a particular volume to be indirectly cataloged, but 
others on that same volume to be directly cataloged?  Interesting. 
Curious, why not indirectly catalog all?

Kurt Quackenbush -- IBM,  z/OS SMP/E and z/OSMF Software Management
Chuck Norris never uses CHECK when he applies PTFs.



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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Kurt J. Quackenbush]

> Actually now I was totally able to customize all my dataset names, 
> which is really great. It is time consuming because I basically had 
> to change everything.

Glad to hear you were able to customize the data set names to your liking. 
 As already mentioned, next time I encourage you to use a Model and z/OSMF 
will use your existing data set name conventions as much as possible.

> Now I hit a few things, because its always checking names in the 
> background..  So when it says its going to build jobs, it lies, its 
> actually verifying names first.  So because I already installed z/OS
> 2.5 with a serverpac, I would like to bypass a few things and it 
> will not let me.  So back to adding a SSA for my duplicates to get 
> thru the screens.

I'd like to understand this comment better.  z/OSMF does indeed verify the 
information you specified in the configuration before generating the jobs, 
such as data set names and locations.  Mostly it ensures there is not 
already a same named data set on a specified volume or in a catalog.  Are 
you saying z/OSMF found a volume or catalog collision when in fact there 
was no collision?  If so, can you elaborate?  For example, did you select 
to create a new master catalog?  Are you using indirect cataloging for 
your existing data sets, and did you tell z/OSMF you want to indirectly 
catalog the new data sets?  Did you tell z/OSMF to create data sets on a 
particular volume?

Kurt Quackenbush -- IBM,  z/OS SMP/E and z/OSMF Software Management

Chuck Norris never uses CHECK when he applies PTFs.

> 



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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Thanks for the input.

Actually now I was totally able to customize all my dataset names, which is 
really great. It is time consuming because I basically had to change 
everything.. My dlibs are on a dedicated volume and my RES datasets on another 
volume.

Then they changed all the ZFS dataset names, so they not end with ZFS now, so 
that required updates, because this then effects my BPXPRMxx member.  I might 
change things to the new IBM names in 2.6, but small changes now.

So my OMVS files are on a secondary RES, but cataloged as 
SYSAOP.ZA2511.  datasets.

SMPE, I use SMS, so I had to use a ton of filtering to place those.

Lastly the CPAC datasets, are my SAVE-OFF's.  I really never use them in 
production because I do system upgrades, but I do reference them for changes 
that I might  have to propagate to my Parmlib/proclibs.

This is why I use CPAC.ZOS25.xx and SMPE.MVS.ZOS25.   this allows 
me to not have to deal with alias's.

All my SYS1.x are SYS1SSA, which SMS has special rules for that allow me to 
direct to volumes of my doing.

So far I like that part in z/OSMF.

Now I hit a few things, because its always checking names in the background..  
So when it says its going to build jobs, it lies, its actually verifying names 
first.  So because I already installed z/OS 2.5 with a serverpac, I would like 
to bypass a few things and it will not let me.  So back to adding a SSA for my 
duplicates to get thru the screens.

I understand IBM is trying to make this idiot/Beginner proof, but I wish there 
was and advanced I know what I am doing option.

Heck even with my serverpac this time, I modified every job, because it didn’t 
allow me to build what I wanted as a configuration.

At least z/OSMF seems to allow name changes, but before it builds jobs it goes 
and validates all the names.  I wish that was a batch job, but such as life..

So the saga continues..

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  On Behalf Of 
Keith Gooding
Sent: Tuesday, October 26, 2021 3:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated

External Email


Hi Terri.

I had a more positive experience with z/osmf installation of a z/os serverpac 
after some initial confusion.

A long time ago I had created a ‘software instance’ from a pair of z/os 2.4 
target/dlib zones. I used this as a model for my 2.5 installation and was very 
surprised when z/osmf proceeded to tailor the dataset names like the 2.4 
instance - surprised because I expected that the model had to be an instance 
created by a z/osmf installation. I now see that it probably looks for matching 
DDDEFs and adjusts the new dataset names accordingly.

I had to adjust the names for new datasets and operational datasets. Here I 
found that z/osmf appears to look for common HLQs in a dataset filter list and 
gives the opportunity to change that common HLQ to something else. I did this 
for instance for some CPAC datasets where we want the HLQ to be SYS1.CPAC 
instead of CPAC - I filtered on HLQs to get a list of all CPAC datasets and 
excluded the ones I did not want to change.

If you do not have a model instance then of course to change all HLQs to SYS1 
you would have to change each HLQ (CEe, ISF etc) separately.

I still have some gripes but these occurred also with the old dialogue:
- only single level aliases are supported. We want to use OMVS.ZOS250 as a 2 
level alias pointing to a new catalog on sysres but this has to be done 
post-install.

- SMPE.ZOS250.* non-VSAM datasets on the sysres are indirectly cataloged 
because indirect cataloging by the installation dialogue works at the volume 
level.

- I always do what used to be called an ‘upgrade install’.  With z/osmf I 
instead answered ‘no’ to ‘do you want to create operational datasets’. In both 
cases we still get some operational datasets such as CPAC.PARMLIB. Most of 
these are not required but to avoid clashing with existing datasets of the same 
name I rename them as SYS!.CPAC.* and indirectly catalog them on sysres.

Keith GOODING


> On 26 Oct 2021, at 18:05, Shaffer, Terri 
> <017d5f778222-dmarc-requ...@listserv.ua.edu> wrote:
>
> Okay I am going to retract the dataset names issue.  Either my z/OSMF 
> decided to play nice now, or I did something wrong.
>
> I can modify all the names to my preferred names and HLQ..
>
> So let me continue to see what happens.. It sure would have been nice to just 
> retrieve my CPAC.SAVE.CONFIG file.
>
> But okay..
>
> Ms Terri E Shaffer
> Senior Systems Engineer,
> z/OS Support:
> ACIWorldwide – Telecommuter
> H(412-766-2697) C(412-519-2592)
> terri.shaf...@aciworldwide.com
>

-

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Keith Gooding]

Hi Terri.

I had a more positive experience with z/osmf installation of a z/os serverpac 
after some initial confusion. 

A long time ago I had created a ‘software instance’ from a pair of z/os 2.4 
target/dlib zones. I used this as a model for my 2.5 installation and was very 
surprised when z/osmf proceeded to tailor the dataset names like the 2.4 
instance - surprised because I expected that the model had to be an instance 
created by a z/osmf installation. I now see that it probably looks for matching 
DDDEFs and adjusts the new dataset names accordingly. 

I had to adjust the names for new datasets and operational datasets. Here I 
found that z/osmf appears to look for common HLQs in a dataset filter list and 
gives the opportunity to change that common HLQ to something else. I did this 
for instance for some CPAC datasets where we want the HLQ to be SYS1.CPAC 
instead of CPAC - I filtered on HLQs to get a list of all CPAC datasets and 
excluded the ones I did not want to change.

If you do not have a model instance then of course to change all HLQs to SYS1 
you would have to change each HLQ (CEe, ISF etc) separately.

I still have some gripes but these occurred also with the old dialogue:
- only single level aliases are supported. We want to use OMVS.ZOS250 as a 2 
level alias pointing to a new catalog on sysres but this has to be done 
post-install.

- SMPE.ZOS250.* non-VSAM datasets on the sysres are indirectly cataloged 
because indirect cataloging by the installation dialogue works at the volume 
level.

- I always do what used to be called an ‘upgrade install’.  With z/osmf I 
instead answered ‘no’ to ‘do you want to create operational datasets’. In both 
cases we still get some operational datasets such as CPAC.PARMLIB. Most of 
these are not required but to avoid clashing with existing datasets of the same 
name I rename them as SYS!.CPAC.* and indirectly catalog them on sysres. 

Keith GOODING


> On 26 Oct 2021, at 18:05, Shaffer, Terri 
> <017d5f778222-dmarc-requ...@listserv.ua.edu> wrote:
> 
> Okay I am going to retract the dataset names issue.  Either my z/OSMF 
> decided to play nice now, or I did something wrong.
> 
> I can modify all the names to my preferred names and HLQ..
> 
> So let me continue to see what happens.. It sure would have been nice to just 
> retrieve my CPAC.SAVE.CONFIG file.
> 
> But okay..
> 
> Ms Terri E Shaffer
> Senior Systems Engineer,
> z/OS Support:
> ACIWorldwide – Telecommuter
> H(412-766-2697) C(412-519-2592)
> terri.shaf...@aciworldwide.com
> 

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

Re: Serverpac installs January 2022 and beyond - Issues Updated

[Shaffer, Terri]

Okay I am going to retract the dataset names issue.  Either my z/OSMF decided 
to play nice now, or I did something wrong.

I can modify all the names to my preferred names and HLQ..

So let me continue to see what happens.. It sure would have been nice to just 
retrieve my CPAC.SAVE.CONFIG file.

But okay..

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  On Behalf Of 
Shaffer, Terri
Sent: Tuesday, October 26, 2021 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Serverpac installs January 2022 and beyond - Issues

External Email


Well I tried, but there are way to many issues with using z/OSMF in my 
installation.

First you cant fix the dataset names, you can only change the prefix, We use 
SYS1.qualifier for all datasets.
When I run the server it just appends SYS1SSA as a HLQ and I am off running.

Next SMPE datasets, I use SMPE.ZOS2x.qualifier and then for my Targets I add in 
the Zone name.

z/OSMF insist on adding SYS1 to it, which stuffs in into the wrong catalog for 
renames.

Then there are no work-arounds, if the panels don’t build what you want, your 
done.

And to be honest I already have z/OS 2.5 installed and IPLed, but you have 
buried the migration guide, so I can guess but would like to have that as the 
first think I see when I install.  Unless it someplace else less obvious.

Will revisit in 2+ years...

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


 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
 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

 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 

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