<snip> You don't need to IPL to add or remove datasets from linklist.
You can create a new PROGxx member that uses another linklist name (other than your default 00), and then issue the "T PROG=xx" that points to that new linklist, then you can issue the SETPROG command to make the new linklist the active one to all tasks (JOB=*), then the old dataset can be deleted without it being part of the active linklist. <end-snip> This is all true, but don't forget also to remove that data set from LLA management and also don't forget that "make the new linklist the active one to all tasks" is the UPDATE function which is unpredictably dangerous. It may work for you (it usually will); it may not. There is no way of fully knowing, and any errors (whether abends, program interrupts, or incorrect behavior) that result are yours to live with. You will not get any sympathy from me (or IBM service). If you do use it, you should probably use the DELAY operand of LNKLST UPDATE (the UPDATE will happen immediately, but the tail end processing, which includes freeing old structures, will be delayed which might give a work unit time to complete its usage of the old LNKLST set before it's too late). It might well be worth trying LNKLST UPDATE before re-IPLing, but don't bet your house on its working. The only thing that is truly safe is to let new address spaces and jobs use the new lnklst while old ones continue to use the old one. But that will not let you delete a data set that was in the old lnklst. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
