Installing a Disaster Recovery CPUID

Please select which operating system you use: z/VM or z/OS


z/VM

Contact your Select Business Solutions Account Manager or Support (888-328-7806) to obtain a disaster recovery CPUID. Please provide the start and end dates of your DR test, and your account number.
 

Install the DR CPUID using one of the following methods:

 1. If you are using an External NLICENSE file for CPUIDs/CPUEXTS.

Update the filename NLICENSE file used for production, adding the DR CPUID and DR CPUEXTs. Invoke NOMAD using the DIAGL parameter (e.g NOMAD2 (DIAGL), which will display all the CPUIDs and CPUEXTs installed. You should see all CPUIDs and CPUEXTs included in the external NLICENSE, including the DR CPUID and CPUEXTs.    

2. If you installed CPUID/CPUEXTs using $NOMOPTS  

Edit $NOMOPTS ASSEMBLE, adding DR CPUID to existing CPUID(s), preceding the CPUIDEND. Add the CPUEXTs provided with the DR CPUID, preceding the CPUEXEND. 

Assemble $NOMOPTS, using N2ASM.

If the work files were saved on the install disk during the NOMAD install, reinstall by running NOM2INST. If the work files were not saved, reinstall beginning with N2PREP, then NOM2INST.

 Again, invoke NOMAD using the (DIAGL parameter to display all the CPUIDs and CPUEXTs, including those for the DR that are now installed.

 For additional information, see the UltraQuest & NOMAD Products Installation Guide-VM, or contact Select Business Solutions Support.

 

 

   
 




z/OS

Contact your Select Business Solutions Account Manager or Support (888-328-7806) to obtain a disaster recovery CPUID. Please provide the start and end dates of your DR test, and your account number.

Reinstall NOMAD using one of the following methods:

1. If you installed CPUID/CPUEXTs using the LICENSE=External, use the following steps.

Add the DR CPUID and DR CPUEXTs to the PARMLIB member allocated to the NLICENSE DD in the NLICENSE STC.

Run NLICENSE STC with PARM=’INSTALL’ to update CPUIDs/CPUEXTs.

Invoke NOMAD using the (DIAGL parameter, which will display all CPUIDs and CPUEXTs installed.

2. If you installed CPUID/CPUEXTs using the MNOMOPTS usermod, use the following steps: 

Edit the MNOMOPTS member of INSTLIB, adding the DR CPUID to existing CPUID(s), preceding the CPUIDEND. Add the CPUEXTs provided with the DR CPUID, preceding the CPUEXEND.  

Re-apply the MNOMOPT usermod using the DBCAUME member of INSTLIB. Add the REWORK parameter to the ++USERMOD statement: ++USERMOD(MNOMOPT) REWORK(yyyyddd). 

On the APPLY command in the DBCAUME JCL, add: REDO SELECT(MNOMOPT).

Run DBCAUME. Expected Condition codes are 0/4. See Chapter 18 of the NOMAD & UltraQuest Products Installation Guide-z/OS for additional information, or contact Support.

Invoke NOMAD using the (DIAGL parameter, which will display all CPUIDs and CPUEXTs installed.



z/OS 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 implement the disaster recovery CPU password. When the NOMAD linklib 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.