SAVRSTOBJ does even a library save step by step, so it transfers while it is saving which reduces the amount of needed temporary storage. But there is a performance degradation compared to SAVLIB + FTP, and I saw several issues within the last years so we use this only in several cases.
Von: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von rob@xxxxxxxxx
Gesendet: Montag, 14. Oktober 2013 13:26
An: Midrange Systems Technical Discussion
Betreff: Re: replicate PROD iseries box to distant TEST box cross-country
How does SAVRSTOBJ use less storage? Doesn't it still save it first? Just
not to anything you can see but instead something in temporary storage?
It's not like it initiates communications before the entire object is
saved, eh? It doesn't start transmission until the entire object is first
saved into temporary storage, right?