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 Is there anything else that can be done ? I tried recycling the VLF . It did not really work . (Silly me :-) )
Raj > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Rajesh Dharia > Sent: Wednesday, February 21, 2007 11:49 AM > To: [email protected] > Subject: UPDATING VLF data objects without an IPL --a query > for the list, please > > > Hi All, > Could someone please enlighten me on the below query ? : > > Q. I have renamed a LNKLSTed load library ( say , > ABC.LOAD on VOLSER = > XXXXXX ) to ABC.LOAD.OLD . I have then named a new version of the same > product load library to the same name ( ABC.LOAD.NEW on > VOLSER=XXXXXX > to ABC.LOAD ; yes it is on the same volser). Keeping in mind > the VLF must > be using the old copy of the load modules contained in > ABC.LOAD . Is it > possible that VLF be made to include the load modules from > the new load > library in its dataspaces without having to IPL the system ? > > Note : I cannot copy the members of the new load-library > into the old load > library as the old one does not have enough space .The new > load library > has additional number of members in it with the new release > that I have. > > Thanks in advance. > Raj Well, I have done this by doing a T PROG=xx to respecify the entire LNKLST concatenation. Doing the renames as you have could result in a problem. Not guaranteed to cause a problem, but not guaranteed to not cause a problem either. It is a lottery. Usually, I change the IPL linklst to point to the new dataset and then do the dynamic LNKLST update. I just live with the fact that the name of the DSN changed. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 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
