> I'm looking for a spreadsheet, action plan, or simple list of steps I nee > d > to do in order to upgrade my VM ESA 2.2 system to Z/VM 5.x and at the sam > e > time move from an old multiprise 2003/103 to a shiney new IBM Z9.
Given the enormous increase in horsepower you're getting, you're probably wise to split up the two processes into 1) doing the hardware swap, and 2) doing the OS update. Running the 2.2 system 2nd level V=V will likely be a snap on that iron. I'd suggest the following high-level plan: 1) obtain the current IOCP from the 2.2 system. 2) research any hardware support PTFs for that system (may be an issue for a system that old if you're getting new disks at the same time) and apply same. 3) Build a virtual machine directory entry equivalent to the existing IOCP using DEDICATE statements for the disks and the other devices 4) Bring in the z9, and cable it up in parallel with the existing processor if possible. 5) build and load a new IOCP for the new hardware. 6) Install z/VM 5.2 native on the z9 7) Add the directory entry you created to the 5.2 system. 8) If you hooked up the old disks, make sure they're online to the 5.2 system. 9) Bring up the 2.2 system 2nd level. At this point your users can get on with life. 10) Migrate guests to the 5.2 system ASAP. 3rd level SIE will probably be the biggest problem in this configuration, so moving these guests is a bigger bang for the buck. 11) Migrate CMS users to the 5.2 system at your leisure. If you're short on network devices, you can put the 2.2 system behind a VSWITCH or CTC connection and allow the 5.2 system to route for it. This way, you change only one thing at a time, and limit your outage to a short period to get the 2nd level system online. You also have a quick/easy fallback if there's a problem, given that 2.2 is pretty ancient and likely to be a little cranky on hardware that new.
