![[University of Arkansas]](./pic/uabanner.gif)
![[Computing Services]](./pic/ua-comp.gif)
The following steps document the process for bringing up a mainframe environment that closely resembles the environment that existed prior to the disaster event. Every attempt should be made to acquire hardware that is as close as possible to that documented in this plan. Any differences may cause trouble with the pre-configured IOCP definitions.
Tapes referred to in the following steps are contained in the Disaster Recovery lockbox.
Reference information:
DRPDR016: Disaster Lock Box Contents.
The process begins at the point where the hardware install technicians
have completed their testing and have turned the new machine over for
use. At this point, there may be an adequate IOCP in place due to
the testing done by the vendor. If not, one must be loaded that will
provide for:
Reference information:
This step prepares two 3380-E disk volumes to receive the VM Starter System.
Reference information:
This step loads the VM Starter System from DDR formatted tapes onto disk. Please note that the DASD type that you are restoring to must match the type for which the tapes were generated.
Reference information:
IPL the VM Starter System from disk volume EV2RES that was just restored.
Using the IOCP command under VM, store the two full IOCP definition files for the system into separate IOCDS files. Both contain definitions for all I/O devices present on the system, but one is for running the CPU in native mode and the other is for LPAR mode. It is recommended that you store the native-mode IOCP in IOCDS A1, and the LPAR-mode IOCP in IOCDS A2. Be sure to specify which IOCDS to use when IMLing the CPU later.
Reference information:
After shutting down the VM Starter System, select the IOCDS containing the full native-mode IOCP and IML the CPU in native mode.
IPL the VM Starter System again using disk volume EV2RES. At this point the VM system will have access to all devices defined in the full native-mode IOCP.
Using the ICKDSF utility program running under CMS, do the INSTALL and INIT/CPFORMAT commands to initialize all of the other disk volumes for the system. Since the ICKDSF INSTALLs can take up to an hour per volume, you can save time by defining several "worker" virtual machines and running concurrent ICKDSF INSTALLs. The list of volumes is documented in :
Reference information:
After shutting the VM Starter System down again, select the IOCDS containing the full LPAR-mode IOCP and IML the CPU in LPAR mode. This will permit bringing up separate VM and MVS systems so that continued work with each platform can continue in parallel.
The MVS Minimal System is a previously configured MVS/ESA operating system that runs off disk volumes named MVM201, MVM202, and MVM203. MVM201 and MVM203 are IPL volumes for the MVSMAINT system. This system will be used to restore all MVS volumes using the FDR utility.
The procedure for restoring the MVS systems is as follows:
A USERID and PASSWORD for TSO or Batch use may be found in the Disaster Recovery Lock Box in the envelope marked UAFMVS1. Take care when keying the USERID/PASSWORD to avoid security lockout.
Reference information:
Reference information:
The CA-1 Tape management and Innovation Scheduling software require passwords that are dependent on CPU serial number. The passwords must be obtained from the vendor(s).
TCPIP requires IP Address and Domain name information in PDS SYS1.TCPPARMS in member TCPDATA. This should be updated with TSO before bringing up TCPIP.
Reference information:
Reference information:
![[Home Page]](./pic/bhome.gif)
![[Table of Contents]](./pic/btoc.gif)
![[Send Mail]](./pic/bmail.gif)