Installing a Disaster Recovery CPUID

VM Contact your Select Business Solutions Sales office to obtain a disaster recovery CPUID by requesting a Backup Computer Designation form and providing the required information. The sales representative will then provide a CPUID for the machine to be used as a disaster recovery machine. Edit $NOMOPTS ASSEMBLE, adding temporary CPUID to existing CPUID(s). Note that the temporary CPUID for the backup CPU should precede any permanent CPUIDs, and that CPUIDs must be separated by commas, and the entire group of CPUIDs must be enclosed in parentheses. Please note that if using version 7.00 for your disaster recovery test, the CPUEXT must also be updated with the value provided along with your CPUID. (See chapter 3 of the VM Installation Guide, Version 6.50 or version 7.00.) Assemble $NOMOPTS, using N2ASM. Run NOM2INST to reinstall NOMAD. If a completely new NOMAD segment is to be installed for the backup CPU, then this installation must be treated as a new installation, and all the steps in Chapter 3 of the VM Installation Guide, Version 6.50 are required to complete the install.

MVS Contact your Select Business Solutions Sales office to obtain a disaster recovery CPUID by requesting a Backup Computer Designation form and providing the required information. The sales representative will then provide a CPUID for the machine to be used as a disaster recovery machine. Restore to an unmodified (i.e. no usermods applied) NOMAD Software Environment. There are several ways in which this restore can be accomplished:   restore from a backup tape generated during the install of NOMAD, prior to applying the usermods use the SMP RESTORE facility and use the SMP REJECT function to remove the usermods currently applied to the software environment. Edit the $NOMOPTS member of INSTLIB, adding the temporary CPUID for the backup CPU. The temporary CPUID must precede any permanent CPUIDs, the CPUIDs must be comma delimited and in upper case, and the group of CPUIDs must be enclosed within parentheses. Please note that if using version 7.00 for your disaster recovery test, the CPUEXT must also be updated with the value provided along with your CPUID. (See chapter 5 in the MVS Installation Guide, Version 6.50 or version 7.00 for additional documentation.) Apply the usermods using the DBCAUME JCL. (If the NOMAD software environment has existing USERMODs the REWORK parameter must be included on the USERMOD in order to re-RECEIVE the updated version. In addition The APPLY command must include the REDO parameter.)

Sites without a NOMAD Software Environment

If the backup/disaster recovery CPU does not have a NOMAD Software Environment, the JCL which follows can be used to incorporate the disaster recovery CPU password. When the load library has been modified using this procedure NOMAD will only function on the disaster recovery CPU. In addition, without a NOMAD Software Environment no further software maintenance can be applied. Please carefully note the NOMAD version that you are running and select the appropriate JCL job stream below. Each JCL job stream will only properly install on it's intended target version!!

	NOMAD 7.00 and later versions Size: 3 kilobytes NOMAD 6.52 and earlier versions Size: 3 kilobytes

Learn More

To find out more about how Select Business Solutions can help you Contact Us today.