IBM Mainframe Discussion List <[email protected]> wrote on 04/20/2010 07:24:56 AM: > > Yes to all of that .... Puzzled me too ... Never seen it before .... I am > > aware of the concatenation restriction on APF authorised load libraries > > (and the integrity reasoning behind it), but there are no steplibs in the > > job and the Joblib is, obviously, the same for all steps. > > > What is that "integrity reasoning"? Doesn't LINKLIST nowadays support > a mixture of authorized and unauthorized libraries, with the authorization > of the step depending on the status of the individual data set from > which the module was loaded? > > Is it merely that since the programmer controls the content of STEPLIB > there's little utility in supporting similar behavior in STEPLIB?
For an ordinary concatenation, contents supervisor knows only whether the entire concatenation is authorized, via a bit in the DEB which is set by OPEN processing. For LNKLST, contents supervisor built the concatenation and did the OPEN, so it can be aware of the authorization separately for each data set. The isn't much value in having that granularity for STEPLIB, since an authorized jobstep can't load anything from an unauthorized library. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
