Hi Mark, Not local rules, really. I could update the LNKLST dynamically.However, that won't be useful unless it is backed by the same changes done statically (which will be taking effect during the next IPL ). The problem is ... the change management procedures come into the scene here and I failed to include the PARMLIB changes that should have been made for the new release. (Though , there are no new PARMLIB changes ). I have been playing on a test system till now . So, I could do just anything .
Anyways, I'll be doing the renames during the change window only ,just before the IPL of the production system. So, I'm sure that will do the trick. I was curious to learn if the seniors on the list could advise of a good trick (if it exists ) that could work in a situation like this. I appreciate the response. Thanks to all who have responded to my queries. Raj -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- 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
