On Mon, 30 Apr 2018 10:57:21 -0700, Lizette Koehler wrote: >It is best to keep everything in the same UCAT. Makes for a happy system > IBM should emphasize happy customers above happy systems.
If the OP had created B.DATA.SET, listed it and noted the catalog then deleted it and created the alias in that catalog, RELATEd to A.DATA.SET, would it have worked cleanly? >> -----Original Message----- >> From: IBM Mainframe Discussion List Sankaranarayanan, Vignesh >> Sent: Monday, April 30, 2018 9:35 AM >> >> 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 -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
