Re: Moving large libraries to another system:

How 'bout 2 programs:  At the sending end, it does a DSPOBJD to an
outfile, reads the outfile, and saves each object -individually- to a
tiny SAVF.  Then send the SAVF to the other end.

At the receiving end, RSTOBJ to the receiving library.

This avoids the problem of duplicating the entire library to a save file.

For sending, how 'bout SNADS and SNDNETF over an SNA link.  SNADS
guarantees that the object will get there.  Eventually.  (:

--Paul E Musselman
PaulMmn@ix.netcom.nospam.com






>I looked in the archives and did not find anything very apparent. I would
>appreciate any suggestions:
>
>Without using tape (don't ask), what is the best way to transfer a large
>library (40gb) from one system to another? It doesn't have to be fast, but
>I need it to not affect the performance of my production system (where I'm
>sending from).
>
>I tried FTP, but it ended up slowing the production box. Any help would be
>appreciated.
>
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Matthew Patee
>Midrange Systems Manager
>ABM Industries
>(415) 351-4309
>fax:(415) 351-4331