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
> 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
@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
> 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
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
> 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
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
>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
-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
, 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 ec
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 "w
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
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 En
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
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
-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 custom
> 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
> 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
-
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
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
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.
21 matches
Mail list logo
