|
from: bryan dietz <bdietz400@xxxxxxxxx>
Do you know if the SAVRSTxxx commands work this way?
Meaning that they do not consume(much) DASD on the source
system but do on the target.
from: "Evan Harris" <spanner@xxxxxxxxxx>
Hi Bryan
I don't know if they use the same API, but some testing I
did for a SAVRST scenario indicated that as data was
restored it was removed from whatever buffer the saved data
was held in. The storage used never went as high as doing a
complete save of the library in question. In fact it didn't
take a lot of storage at all, but that might be dependent
on what was being saved
The scenario I tested was doing a SAVRST to a different
library on the same machine so the amount actually used may
vary depending on how fast the link is and how fast the
restore occurs.
Regards
Evan Harris
As an Amazon Associate we earn from qualifying purchases.
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.