I am in applications, not systems, so I don't understand all of this. Could someone briefly (and simplistically!) explain what advantages (and disadvantages) there might be in having a user lib managed by LLA?
Thanks! Frank >________________________________ > From: Peter Relson <rel...@us.ibm.com> >To: IBM-MAIN@LISTSERV.UA.EDU >Sent: Thursday, January 9, 2014 5:38 AM >Subject: Re: LLA/VLF -- NAMED LNKLST? > > >I'm not sure what named lnklst has to do with user libraries in LLA. > >LNKLSTs are defined in "sets". Each "set" has a name. One "set" is >current. Others (previously "current") may still be active. The name is >the handle by which the set can be referred to in the SETPROG and DISPLAY >PROG commands and LNKLST statements within PROGxx. > >LLA manages all LNKLST data set by default. Any user load lib can be added >to LLA management whether it is in a LNKLST or not. > >Peter Relson >z/OS Core Technology Design > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN