Re: 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?

one thing you can do, that's kind of squirley, but it does work, is copy the 
members to
qs36src, and then do a savs36libm.  then you can rsts36libm on the v2r3 system. 
 at least
it will get them over to the other system.

nj

+---
| 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
+---