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.SICELPA SYS1SSA.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 <IBM-MAIN@LISTSERV.UA.EDU> 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 disclaimers....etc
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 <IBM-MAIN@LISTSERV.UA.EDU> 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 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]
<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
