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
