I have been in shops where there is a "standard user loadlib chain" managed by LLA (separate from the system linklist). Linklist was specified in IEASYS00 as PROG=(00,UU). In my case, the list was "standard" and an F LLA,UPDATE=UU was issued by automation every 15 minutes to allow for program migrations throughout the day.
HTH, <snip> This is puzzling to me. Are you advocating having JOBLIB/STEPLIBs that specify every single library that your particular jobs needs to access? This seems to me to be (no offense) nuts! I am of the total opposite inclination. I would much prefer to have a "system search chain", as it were, that contains all of the libraries that have load modules that need to be executed. As a developer I, in fact, would prefer to have our application loadlib's also in LINKLIST. The only reason I gave up on asking for that is because of the whole "need to refresh the LLA" thing. VSE is so much simpler in this regard. There is a "permanent search chain" that has all of the standard "load libraries" in it. Things such as TCP/IP, DB2, DL/I, etc., as well as our production application library. Then in your job's JCL if you wanted, say, to execute the test version of a program which needs to call the production version of a subroutine you need only specify an "override" library. This li! brary will be searched first, and if a module is not found then it will search the system search chain. </snip> ---------------------------------------------------------------------- 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
