>No. SETPROG LNKLST is doing what it was advertised to do, but remember >that changes to the active linklist only take effect for address spaces >started after you issue SETPROG. Batch jobs run in initiators and they >live a very long time. So chances are your job is trying to fetch the >module using the original IPL-time linklist and barfing because that >extent is no longer valid. >
Not very often that I would disagree with both Chris and Barabara, but a quick test on a sandbox system I have that still runs JES2 inits tells me that batch jobs running in an init do indeed pick up a the new LNKLST set (without using SETPROG LNKLST,UPDATE). I used my IPLINFO EXEC in batch and only had one init started and ran it both before and after a dynamic addition to the lnklst. I also ran a job that actually used a module in the library I added. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
