RE: Moving large libraries to another system:

Would SAVRSTLIB work in your situation?

"The SAVRSTLIB command saves and restores the entire library; this
includes the library description, the object descriptions, and the
contents of the objects in the library.  For job queues, message
queues, output queues, data queues, and logical files, only the
object definitions are saved and restored, not the contents.
Logical file access paths can be saved and restored by specifying
ACCPTH(*YES).  The contents of a save file can be saved by using the
Save Save File Data (SAVSAVFDTA) command.  By specifying
SAVFDTA(*YES) on the SAVRSTLIB command, the contents of a save file
can be saved and restored." (From the online help for savrstlib command.)

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Matt Patee
Sent: Friday, January 11, 2002 4:47 PM
To: midrange-l@midrange.com
Subject: Moving large libraries to another system:



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

_______________________________________________
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.