× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



So long as you "blow them away" with DLTLICPGM or option 12 of GO LICPGM
then I don't believe there is any contradiction.  I would not just delete
the libraries though as some traces of that option might be retained.

Bruce Vining

>
>I saw this thread and it got me to thinking.  We are getting a bit short
>on DASD on our older machine (V3R2M0) and I noted that QSYSV3R1M0,
>QSYSV2R3M0, and QSYSV3R0M5 are all in the top 10 of our largest
>libraries by size.  It was noted by some on this list that these
>libraries should NOT be deleted.  Others indicated that it was okay,
>except not to delete them, but rather to "remove" them.
>
>So I called IBM and they said as long as you had no intentions of saving
>and restoring anything from that machine to a machine on an earlier
>release... blow them away!
>
>Can someone please tell me why they think IBM may be wrong?
>I really would like to off these things if I don't need them.
>
>Thank you for your help!
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.