>True, but the APF list entries include the volume serial on which the data > set resides, or they specify "SMS". In either case, the catalog entries are > not needed at IPL time, so APF listed data sets can be cataloged in a > user catalog.
How do you build the DEB for the link list when LNKAUTH=APFTAB is specified if the volume serial is not specified and the data set is cataloged in a user catalog? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Tom Marchant <[email protected]> Sent: Wednesday, May 2, 2018 9:42 AM To: [email protected] Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias On Wed, 2 May 2018 08:14:43 +0000, Gibney, Dave wrote: >Well, you can't (to the best of my knowledge) use things depending on >user catalogs at the time that the IPL LPA or Linklst are built. And the >name in the APF list has to be the real name on the volume. True, but the APF list entries include the volume serial on which the data set resides, or they specify "SMS". In either case, the catalog entries are not needed at IPL time, so APF listed data sets can be cataloged in a user catalog. >I don't know the effect of STEPLIBing a job or STC via an non-VSAM >alias to a dataset that is correctly APF authorized by it's real name. >I think that should actually work. It does. >Playing post IPL games with SETPROG might get you what you want, >but will be need additional attention maintaining the Commands and >likely be more prone to error. I wouldn't call it "games". I have created a new LNKLST set after IPL and it works quite well. There is no reason the OP couldn't create a PROGxx member that contains, for example, LNKLST DEFINE NAME(ADD.USERCAT.DS) COPYFROM(CURRENT) LNKLST ADD NAME(ADD.USERCAT.DS) DSNAME(B.LOAD) LNKLST ACTIVATE NAME(ADD.USERCAT.DS) and issue SET PROG=xx. From then on, any new address space uses the new LNKLST set, and have the added library available. I would expect that the system is up far enough for this to work correctly at the time COMMNDxx members are processed, so that the SET PROG=xx command can be in COMMNDxx. I don't know if my expectation would be correct. Note that as coded above, the ADD puts the data set at the bottom of the LNKLST. You can put it somewhere else. -- Tom Marchant > >> -----Original Message----- >> From: IBM Mainframe Discussion List <[email protected]> On >> Behalf Of Sankaranarayanan, Vignesh >> Sent: Tuesday, May 01, 2018 8:12 PM >> To: [email protected] >> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias >> >> Hi Dave, >> >> I wouldn’t dare change the structuring at this point without fully >> understanding why it is the way it is; which may very well be because of >> something that happened twenty years ago. >> >> – Vignesh >> Mainframe Infrastructure >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] >> On Behalf Of Gibney, Dave >> Sent: Wednesday 02-May-2018 03:00 >> To: [email protected] >> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias >> >> 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 ---------------------------------------------------------------------- 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
