-----Otlist riginal Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Peter Relson Sent: Saturday, May 28, 2022 7:40 AM To: [email protected] Subject: Re: data set deletion problem
DO NOT DO WHAT I HAVE SEEN DISCUSSED, unless you don't mind re-IPLing. You have, for some reason, placed this data set into the LNKLST. If you delete the data set, don't count on your system staying up. The ENQs on LNKLST data sets are to stop you from doing the harm to your system that deleting the data set could cause. It is never OK to delete a LNKLST data set. LNKLST UNALLOCATE is NOT provided to help you delete such a data set. It is provided so that you can manipulate an uncataloged data set of the same name. If you must try to delete a data set that is currently in the LNKLST, then your first steps are to get it out of all active LNKLST sets. This, in and of itself, is unpredictably dangerous and you should not expect success, but you might indeed succeed. One way to do this is * Define a new LNKLST set copied from the current (LNKLST DEFINE ...) * Delete the problem data set from that LNKLST set (LNKLST DELETE ...) * Stop LLA * Activate the new LNKLST set (LNKLST ACTIVATE ...) * LNKLST UPDATE JOB(*) to get all address spaces using the new LNKLST set. This is the unpredictably dangerous step and should never be done unless you are willing to experience abends and re-IPL. In many cases it will work. But it really is not knowable if and/or when. * Restart LLA This has all been discussed multiple times before. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
