Dazzo, Matt wrote:
Software upgrade, the previous install was not used as a model.
Software Upgrade is really intended to be used only when you will keep
things on the same relative target volumes. That is, the same data sets
that are on the first volume on your existing system will still be
Software upgrade, the previous install was not used as a model.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Eells
Sent: Tuesday, June 28, 2016 12:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZOS 2.2 Install - Alias to
Are you using the Full System Replacement or Software Upgrade
installation path? If the latter, did you use your prior saved
configuration to model the new one after?
Dazzo, Matt wrote:
I am working on a software upgrade install of zos 2.2 and have a question about
what catalog to use in the
oing wrong? Thanks Matt
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of retired mainframer
Sent: Tuesday, June 28, 2016 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZOS 2.2 Install - Alias to Catalog
How do you intend to handle the
LISTSERV.UA.EDU
> Subject: ZOS 2.2 Install - Alias to Catalog
>
> I am working on a software upgrade install of zos 2.2 and have a question
about what
> catalog to use in the 'ALIAS TO CATALOG' cpp install panel. After the
install is complete
> I'd like to continue to
I am working on a software upgrade install of zos 2.2 and have a question about
what catalog to use in the 'ALIAS TO CATALOG' cpp install panel. After the
install is complete I'd like to continue to us my current master catalog for
zos 2.2. So do I create a new temporary user catalog as the zos
