|
Is there an ECS modem on each box? If so, setup an SNA connection via the ECS modems then SNADS them across. Many of the old ECS modems are only 9600bps, but it can run all night. And source members don't tend to be large anyway. I don't mean save to a savefile and then sndnetf, but sndnetf each member and then rcvnetf on the v2r3 box. This can be automated quite simply (a bit of CL on each end). Another approach is find somebody on V3R1 and another somebody on V3R2/V3R6/V3R7. The V3R2,6 & 7 box's can all target to V3R1. Soo... You save your source files & target V3R2. V3R2,6 or 7 system restores your source files and then saves them targeting V3R1. V3R1 system then restores and resaves them targeting V2R3. This isn't bad one time, but it is a bit of a pain. If your source code is constantly changing, the ECS option above is probably better. Bob -----Original Message----- From: Ira Chandler [SMTP:ira@roiconnect.com] Sent: Monday, October 19, 1998 3:35 PM To: MIDRANGE-L@midrange.com Subject: Moving all source - 4.2.0 -> 2.3.0 We have a customer needing an update of our software for their obsolete 2.3.0 box. Our source is NOW on our S20 at 4.2.0. Our old 2.3.0 box has ONLY twinax attached terminals, QIC tape, and no other connectivity. Our 4.2.0 box has QIC tape also, as well as full TCP/IP functionality. The challenge: Moving all source files (QRPGSRC, QDDSSRC, etc., each with hundreds of members,) from the 4.2 box to the 2.3 box in an automated fashion. We may need to do this multiple times over the next 6 months. (Yes, we will *eventually* drop support for pre-3.2.0) While we can use CPYTOTAP, it is a manual operation and cannot be automated without significant coding. The individual members are treated as one, or, we must perform the operation for each member. We will write the code if we HAVE TO, but, is there an off-the-shelf utility that would ease this task? Ira Chandler, Technical Services, ROI Corporation ira@roiconnect.com 800-396-7641 x512 http://roiconnect.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.