Basically, this does come down to "cannot vary offline if there is a data set on the volume that is in the IPL-time LNKLST". And that comes down to "the IPL-time LNKLST DCB is never closed even when there are no longer any users of it, as might happen after LNKLST UPDATE JOB(*)" And that comes down to "we dare not free the DCB/DEB of the IPL-time LNKLST for compatibility reasons, which close would do" because we're worried about really old code that might be doing something it shouldn't, looking at control structures pointed to via CVTLINK (which remains the address of the IPL-time LNKLST DCB).
Having said all that, we are looking at addressing the issue in the future , and we have hopes that if you do happen to do a LNKLST UPDATE JOB(*) after creating a new LNKLST so that no one is using the IPL-time LNKLST (and, presuming that your system doesn't experience anything too catastrophic because you have done that) then you would be able to vary offline the volume and would be able to delete a PDSE data set that is no longer in an active LNKLST. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
