|
Or it could all be done in CL with a script sitting in a source member. Piece of cake. Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell pnelson@xxxxxxxxxx "Courage is contagious. When a brave man takes a stand, the spines of others are often stiffened." ~~ Billy Graham "Steve Landess" <sjl_123@xxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/23/2004 03:34 PM Please respond to Midrange Systems Technical Discussion To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc: Subject: Re: SAVRSTLIB - how to set up the network over ethernet And you could "Roll your own" command fairly easily by writing some code using Scott Klement's FTPAPI... CL CPP and an RPGIV Program that: 1) CL pgm creates a save file on this system 2) CL pgm saves the library to the save file on this system 3) CL calls RPGIV pgm that: i) calls the FTPAPI routines to send the save file to the other system ii) then calls the FTPAPI routine to run the RSTLIB command on the other system to restore the save file to a library Or it could all be done in an RPGIV program, I know that's what Rob would say... Steve ----- Original Message ----- From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Friday, January 23, 2004 1:35 PM Subject: Re: SAVRSTLIB - how to set up the network over ethernet > Hi, Scott: > > You could "mess with" setting up AnyNet/400, which requires changing the > system-wide > network attribute of Allow AnyNet to *YES (CHGNETA ALWANYNET(*YES)), on > both systems, (this may requre an IPL to activate), and then you have to > configure both > systems to use SNA-over-TCP/IP... not easy. It does work, but it is not > pretty. > > Or, since you have FTP working, you could just create a save file, save the > library in > the save file, use FTP to send that save file across, then restore from that > save file, and > delete the save file when you are done. (Of course, you need to ensure that > all the > object owners' user profiles exist before restoring the objects on the > target system). > > That's how SAVRSTLIB works, "under the covers" as far as I can recall. > > HTH, > > Mark S. Waterbury > > ----- Original Message ----- > > From: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> > > To: <midrange-l@xxxxxxxxxxxx> > > Sent: Friday, January 23, 2004 12:23 PM > > Subject: RE: SAVRSTLIB - how to set up the network over ethernet > > > > > I'm pretty sure you need an SNA connection. The remote location name is > the > > SNA short name. > > > > Regards, > > > > Scott Ingvaldson > > AS/400 System Administrator > > GuideOne Insurance Group > > > > -----Original Message----- > > > > date: Fri, 23 Jan 2004 13:46:36 -0500 > > from: "Shea, David" <DShea@xxxxxxxxxxxx> > > subject: SAVRSTLIB - how to set up the network over ethernet > > > > I have two AS/400's on my network. Both with Ethernet. One is > > 192.168.0.150, the second is at 192.168.0.151. I want to use SAVRSTLIB > > across the two. I'm having trouble finding the instructions for setting > > things up. SAVRSTLIB is asking for a remote location name. This is where > > I'm getting fuzzy. > > > > Can anyone point me in the direction of how to set up my 2 boxes so that > > this function will work? Telnet, FTP, even DDM work fine between the two > > machines. > > > > Thanks. > > > > > > This message and accompanying documents are covered by the Electronic > > Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains > information > > intended for the specified individual(s) only. This information is > > confidential. If you are not the intended recipient or an agent > responsible > > for delivering it to the intended recipient, you are hereby notified that > > you have received this document in error and that any review, > dissemination, > > copying, or the taking of any action based on the contents of this > > information is strictly prohibited. If you have received this > communication > > in error, please notify us immediately by e-mail, and delete the original > > message. > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.