On Fri, 4 Feb 2011 01:08:38 -0800, Walter Marguccio wrote: >If neither LLA nor XCFAS have their hands on old.linklib, you can >delete the dataset.
No. You can do a SETPROG LNKLST,UNALLOCATE to free the ENQ that XCFAS has and you can either stop LLA or otherwise get it to release the old.linklib data set. That does *NOT* mean that it is save to delete the data set. That does nothing to remove it from use as a LNKLST data set. In order to make it inactive as a LNKLST data set, a new LNKLST set must be activated and all running address spaces that started before activating the new LNKLST set must be told to use the new LNKLST set using LNKLST UPDATE. This is somewhat dangerous and should only be done if you are prepared to IPL. Be aware, though, that SYS1.LINKLIB, SYS1.MIGLIB, SYS1.CSSLIB, SYS1.SIEALNKE and SYS1.SIEAMIGE are always included in the LNKLST concatenation unless specifically overridden by SYSLIB statements. >However, I seem to remember that either LLA or XCFAS are not >really happy to see old.linklib being deleted under their nose. XCFAS is not the one using the LNKLST data sets. It is just a convenient place to hang the ENQ. Search the archives. -- Tom Marchant ---------------------------------------------------------------------- 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
