|
Then there is always SAVRSTLIB. Art_Baker@baan.com on 08/23/99 11:25:28 AM Please respond to MIDRANGE-L@midrange.com@Internet To: MIDRANGE-L@midrange.com@Internet cc: Fax to: Subject: RE: as400 to as400 Thanks Sam and Carl, Good advice on transferring files between AS400's. However my e-mail went down Friday and I ended up using STRTCPFTP. It worked but this CL program would have been a lot cleaner to use. Art -----Original Message----- From: Sam Kanakanui [mailto:kanakanuis@mindspring.com] Sent: Saturday, August 21, 1999 8:06 AM To: MIDRANGE-L@midrange.com Subject: RE: as400 to as400 Well Art, I'm no expert but all you need to do is SAVLIB to a SAVF and FTP it over to the other machine. You will need a SAVF on the Target box first. If this is something you do on a regular basis you could try the following: CL program: CLRSAVF FILE(MOVE2PROD/TRANSFER) CLRPFM FILE(QGPL/QCLSRC) MBR(FTPLOG) SAVLIB LIB(MOVE2PROD) DEV(*SAVF) + SAVF(MOVE2PROD/TRANSFER) + UPDHST(*NO) ACCPTH(*YES) OVRDBF FILE(INPUT) TOFILE(QGPL/QCLSRC) + MBR(FTPCMDS) OVRDBF FILE(OUTPUT) TOFILE(QGPL/QCLSRC) + MBR(FTPLOG) FTP RMTSYS(DEV400) /* (FTP CL Program) */ DLTOVR FILE(INPUT OUTPUT) Then an empty member in QGPL/QCLSRC (this example) called FTPLOG, Then a member called FTPCMDS like this: temp **** close open as400 user dataxfer dataxfer binary put move2prod/transfer fromdev/transfer close quit where dataxfer is a valid user id on the target machine, transfer is a *SAVF in library MOVE2PROD(Sending box) and library FROMDEV(Target box) If you need any advice on this method, contact me offline. Does anyone else have an easier way??? Sam Kanakanui Borg Systems Inc. Kanakanuis@mindspring.com -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com] On Behalf Of Art Baker Sent: Friday, August 20, 1999 12:20 PM To: 'MIDRANGE-L@midrange.com' Subject: as400 to as400 Hello people, Can someone point me in the right direction for a procedure to transfer a library from one AS400 to another AS400. Thanks, Art +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.