On Thu, 22 Feb 2007 02:35:11 +0530, Rajesh Dharia <[EMAIL PROTECTED]> wrote:
>Thanks for your response , John :-) . > > You are right . I know, the proper way would have been to update the >LNKLST with a new loadlib name or a different VOLSER ,at least . >Considering the situation that a dynamic LNKLST change is not to be made >, do you think IPLing the system will be the only option ? >OR Why can't dynamic LNKLST update be done? Local rules? If so, seems strange that local rules will let you rename a live LNKLST lib (which should never be done) and not do a dynamic lnklst update. Or are you on a release below OS/390 1.3 (IIRC, that is when dynamic LNKLST became available)? So if you can do the dynamic LNKLST update, then yes... IPL is what you have to do. > Is there anything else that can be done ? I tried recycling the VLF . It >did not really work . (Silly me :-) ) > Never had a prayer to work. VLF works with LLA. LLA is getting those modules from the LNKLST. Renaming the library didn't change the LNKLST. BTW, how did you do that while the dsn was ENQed, did you use SETPROG to release the ENQ? Again... seems strange if you can do that but not a dynamic LNKLST update. You could update LLA with your new library (CSVLLAxx) but that won't change where modules are getting loaded from unless you use a steplib. And even then there is no guarantee the modules will come from VLF. 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
