|
>
>Probably the most reasonable request to IBM would be to do SAVSYS to save
>files. However SAVSYS writes a series of tape files, and the current save
>file implementation is one tape file per *SAVF. As a *SAVF is really just
>like a single member 528 byte PF, it might be reasonable to ask IBM to
>implement a multimembered SAVF, however IMHO, I do not think that they will
>feel that this is not strategic enough for their investment..
>
>Al
>
would a multivolume savf also enable:
savlib ( lib1 lib2 ... ) dev(*Savf)
or savlib (*all) dev(*Savf) ??
and would it also enable an unattended release install from a savf?
If so, does that justify the investment?
I'll do it for 50k.
Steve Richter
+---
| 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 mailing list archive is Copyright 1997-2025 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.