Re: ftp versions of SAVRST...

Doug

Err... someone building a copy of a production box for Y2K testing ? <g>

I did in fact do this after omitting a few libraries from the save and had
to do what Rob is looking to do: batch up saving the libraries, then
FTP'ing them.

As I recall the method I used was to save them one at a time then initiate
the FTP in batch and go on to saving the next one. I still have the code
somewhere though it was kind of ugly as it was thrown together over a
couple of days....

One thing to watch for with all those sav files: diskspace. Most probably
you have this covered.

I guess this means that a generic tool ought to provide for sending the FTP
in "background" or for  FTP'ing each file then deleting it before
proceeding to the next one.

It should also quite probably check disk space to avoid an overflow as it
goes along although the IBM versions may well do this for you; SNADS
failures once the storage threshold has been exceeded have been known to
trip me up occasionally over the years.

I hate the idea that a password that has save/restore capability ends up in
a script, no matter how short the time frame.

Cheers
Evan Harris

>Rob,
>
> >Interesting point on the number of libraries.  Who the blazes would use
> >SAVRSTLIB to send *NONSYS?
>
>Certainly not me.  But I do often want to name multiple, specific libraries.
>However, having it iterate over them is definately doable.  I was mostly just
>pointing out it is not necessarily quite as simple as a single SAVxxx to a
>SAVF,
>followed by FTP and a RSTxxx.
>
>Doug
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.