Re: Data Migration from a V5R1 model 600 to a V5R4 520

Although restoring only user data might seems acceptable, doing the migration ensures some things which were not accounted for in planning [e.g. unregistered external stored procedures, distribution queues, job schedule entries, etc.] should not end up being an "Oops! I did not consider that." Using a full system restore in that migration can also serve as an effective DR test; even if to a different release and only the first steps. With the migration path there is also no concern for what of OMIT() and OPTION(*NEW) will not have restored into QGPL & QUSRSYS since the full libraries would be restored with the old-release objects.data; also ensuring that nobody messes up the system by forgetting OPTION(*NEW) and using ALWOBJDIF(*ALL). RSTCFG, RDBDIRE, and System Values are the only things I can think of at the moment [I did not review the migration path documentation] which are required to be moved/corrected in the migration scenario, and the other noted considerations [e.g. directory entries and tcp/ip configurations] should be automatically updated as part of [what appears to be to the install code for v5r3m0] a supported N+2 upgrade over v5r1m0.

Regards, Chuck