Ah Ha!!! The doc I have for "Removing or Compressing a Dataset in an Active LNKLST" did not discuss using the UNALLOCATE for LINKLIB, MIGLIB, etc.
That worked. I was able to delete and reallocate a larger SYS1.MIGLIB on my target SYSRES. These systems are not production environments. Thank you for assist. S. Veryl Ellis -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of John McKown Sent: Tuesday, June 11, 2019 3:11 PM To: [email protected] Subject: Re: SYS1.MIGLIB and LNKLST On Tue, Jun 11, 2019 at 1:59 PM Veryl Ellis <[email protected]> wrote: > I'm applying maintenance to my target SYSRES and the target > SYS1.MIGLIB ran out of space (S/D37). > Can anyone tell me how to get SYS1.MIGLIB out of the running Link List > concatenation, so I can delete and reallocate a larger target SYS1.MIGLIB? > The standard SETPROG LNKLST stuff to delete a DSN from the link list > doesn't work on SYS1.MIGLIB. > Interesting. You did a SETPROG UNALLOCATE and it remained allocated? You also need to STOP LLA since that address space also allocates all the LNKLST data sets + any others you put in the PARMLIB member. > > Thanks for any assist. > > > > S. Veryl Ellis > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown ---------------------------------------------------------------------- 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
