Re: V2R3 CISC to V4R2 RISC - Do we dare?

[Pete Hall <peteh@xxxxxxxxxx>]

At 22:47 07/29/98 -0700, you wrote:
>Well folks, I think we have talked about this, but I just wasn't paying
>attention.
>Has anyone run into any difficulties with the one step upgrade from V2R3
>to V4R2. In this case, the box is also being replaced, so we are hoping
>to get to a point where only data will be tranfereed over a three day
>weekend, with all other objects handled prior to the weekend.
>
>All programs now have observability. New versions of third party
>utilities have been ordered.
>The home-grown applications are a variety of S/36 converted to S/38,
>S/38. and a couple of ILE programs.
>
Don't forget about configuration objects (including subsystems, job queues, 
line, controller and device descriptions - may or may not be identical), system 
values, job descriptions, classes of service, user objects in QGPL, QUSRSYS, 
QSYS, etc, host table entries, job schedule entries, stored procedure 
definitions, user profiles, system directory entries, document library objects, 
differences in licensed program products, user programs that access system 
tables (they've changed - QADBXREF now has an enormous record length) and hard 
coded device names in programs. We recently did an upgrade similar to yours and 
successfully went from V3R1 to V4R2 without a hitch after a disk crash on the 
old box. Luckily, my partner in crime had a couple of weeks of up-front work 
already done though and we were pretty well ready to do it anyway. Don't tell 
Al, but even though we couldn't follow the roadmap, no important anatomical 
parts fell off. Did some serious homework first though.




Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

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