On Tue, May 1, 2018 at 2:47 PM, Tom Marchant < [email protected]> wrote:
> 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. > Hum, now you _can_ do that -- have a DSN on the LNKLST in a UCAT without specifying the VOLSER in the PROGnn member. But __ONLY IF__ you do a SETPROG after IPL which creates a new LNKLST to be used by address spaces which start _after_ the SETPROG is done. This does not help with LPA modules or with modules which need to be available (perhaps via IEFSSN) earlier in the IPL. > > -- > Tom Marchant > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
