×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Ok, I do these all the time, as I am sure others on this list do. I assume you mean a Previous release to current release migration.
Load the LIC and OS only on the new system (If it came preloaded, then IPL to DST, Clear ASP Data). Load the OS of the new release. Now, do a SAVE 21 on your old system. Then on your new system, do a RESTORE 21 (Check the not same system so as not to restore the System Resource Database). Then go through each step (if any cancel out figure out why and either fix and proceed or proceed. Too much detail to go into if you are doing this you ought to know what you are doing). Then at the end of the restore, do not start the controlling subsystem. Insure you do a UPDSYSINF. Then immediately upgrade all the existing LPPs on the machine to the new release. Change any of the lInes and controllers to match the new resource, Load the PTFs, and IPL.
Done. I do this all the time, and it works perfectly.
Pete
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, December 12, 2014 2:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Why isn't go restore opt 21 used with previous-to-current
Honestly I've never done a 'previous-to-current'.
and I've had one lump of a week and as soon as I shutdown I'm outta here.
Don't expect much details... :-)
If it wasn't for the 80% probability of getting called by work tonight, I'd be making like Jimmy Buffett.
Rob Berendt
midrange.com
