Hi Paul, I know, it's just a site practice I guess.
- Vignesh Mainframe Infrastructure -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Feller, Paul Sent: Tuesday 01-May-2018 07:55 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias "A.**" and "B.**" can be in the same catalog. The datasets that are in the linklst or lpalist do not have to be in the master catalog. You can use VOLSER to point to the datasets. LPALIST could look like this. A.B.C.SOFTWARE(VOLSR1) A.B.D.SOFTWARE(VOLSR2) LINKLST could look like this. LNKLST ADD NAME(PROGPL) DSN(A.C.D.SOFTWARE) VOLUME(VOLSR3) LNKLST ADD NAME(PROGPL) DSN(A.C.E.SOFTWARE) VOLUME(VOLSR4) Thanks.. Paul Feller AGT Mainframe Technical Support paul.fel...@transamerica.com Work: (319)-355-7824 Cell: (319)-573-4821 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sankaranarayanan, Vignesh Sent: Monday, April 30, 2018 20:55 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias What am I trying to do? Let's say a product installation/customisation allows only for 1 HLQ, so I choose B for it because A.** is used to host datasets that need to be LNK/LPAd. B.** is used to host datasets that need to be APFd or nothing at all (just run-time). A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT Because I mentioned the 1 HLQ in product customisation, I need to make sure that if the files are looked for in B.**, the A.** files need to be reachable via their alises in B.**. Makes sense? - Vignesh Mainframe Infrastructure -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Monday 30-Apr-2018 23:27 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias It is best to keep everything in the same UCAT. Makes for a happy system Could you explain what you are trying to do? I have used SYMBLICREALTES and SYSTEM SYMBOLS to add things like release levels in datasets, without the user having to change the JCL For example. A.R111.B.C would be related to A.B.C which the end user always uses and the R111 could be a system symbol that could be dynamically changed as need. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Sankaranarayanan, Vignesh > Sent: Monday, April 30, 2018 9:35 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: IEFA107I when pointing to dataset alias > > Hello All, > > Let's say I have A.DATA.SET in APF and LNK. > I then create B.DATA.SET as an alias to A.DATA.SET > > NONVSAM ------- A.DATA.SET > IN-CAT --- CATALOG.MASTER.CAT > HISTORY > DATASET-OWNER-----(NULL) CREATION--------2018.120 > RELEASE----------------2 EXPIRATION------0000.000 > VOLUMES > VOLSER------------VOL001 DEVTYPE------X'3010200F' FSEQN------- > -----------0 > ASSOCIATIONS > ALIAS----B.DATA.SET > ATTRIBUTES > > ALIAS --------- B.DATA.SET > IN-CAT --- CATALOG.MASTER.CAT > HISTORY > RELEASE----------------2 CREATION--------2018.120 > ASSOCIATIONS > NONVSAM-A.DATA.SET > > > But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get > --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND > > What gives.. ? > > - Vignesh > Mainframe Infrastructure > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN MARKSANDSPENCER.COM ________________________________ Unless otherwise stated above: Marks and Spencer plc Registered Office: Waterside House 35 North Wharf Road London W2 1NW Registered No. 214436 in England and Wales. Telephone (020) 7935 4422 Facsimile (020) 7487 2670 www.marksandspencer.com Please note that electronic mail may be monitored. This e-mail is confidential. If you received it by mistake, please let us know and then delete it from your system; you should not copy, disclose, or distribute its contents to anyone nor act in reliance on this e-mail, as this is prohibited and may be unlawful. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
