I hate to add to the complexity. I don't like the OP's naming plans/conventions at all.
But, he can have what he wants. It is the IPL time linklst that isn't going to have such fancy thigs and access to usercats available. He can IPL with a minimal, perhaps even IBM only LPA/LINKLST/APF and then, once the system is far enough up that that full catalog services are available, use SETPROG to "enhance" these resources. I am not saying this is a good idea, although I have considered using this idea in a more limited manner for a couple ISV's > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Tom Marchant > Sent: Tuesday, May 01, 2018 12:47 PM > To: [email protected] > Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias > > On Tue, 1 May 2018 10:37:37 -0500, Paul Gilmartin > <[email protected]> wrote: > > >On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote: > >> > >>However, with a bit of extra work you can use SYMBOLICRELATE type > >>alias > >instead and that is allowed to go in a different catalog (see OA52218). ... > >> > >And to this end catalog should support specifying SYMBOLICRELATE with > >no need to have an actual substitutable symbol in the alias name. That > >would eliminate the need for (some of) the extra work. > > Not for the OP's problem. He wants to define most of his data sets in a > Usercat, but those that are in LNKLST, he wants to define in the Master > Catalog. He could create an alias in the master using SYMBOLICRELATE, but he > cannot include that alias in the LNKLST. > > -- > Tom Marchant > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
