New dsn's go down as SSA.SYS1.LINKLIB. Then later get renamed to SYS1.LINKLIB on the new res volume without updating the catalog? That would leave the indirect catalog entry for SYS1.LINKLIB pointing to the new res volume at IPL. Then there is a cleanup of SSA.* dsn's. Where am I going 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 DSNs that are common when the datasets are not, e.g., SYS1.LINKLIB? > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Dazzo, Matt > Sent: Tuesday, June 28, 2016 8:41 AM > To: IBM-MAIN@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 us my current master catalog for zos 2.2. So > do I create a new > temporary user catalog as the zos 2.2 mcat and plug that name in that panel entry or do I put > my current master cat name in the panel entry? Below is a snip it of > the panel. > > Thanks Matt > > > S Alias STA Target System Catalog Data Set Name Type > - -------- --- -------------------------------------------- ---- > AOP CATALOG.Z22MCAT MCAT > ASM M CATALOG.Z22MCAT MCAT ---------------------------------------------------------------------- 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
