Installation Procedure › Test System Installation Tasks › Maintenance ID Installation Steps › Step 7: Generate and Test the CMS Nucleus

Step 7: Generate and Test the CMS Nucleus

This step describes the procedures for generating and testing the CMS nucleus.

Step 7 is starting.
Generate the CMS nucleus with CA ACF2 for z/VM intercepts.
IPL CMS and test the new CMS nucleus.
 
Do this step under the same second‑level CP you previously
generated with CA ACF2 for z/VM protection.
 
Reply ? (for more information), EXIT, or COMPLETE to this step prompt.
Reply COMPLETE only if you have already generated the new CMS nucleus
and tested CMS.

This is a manual step you must perform outside of the exec. When the following manual procedures instruct you to invoke the CAXABLD EXEC, the intention for most sites is that the CAXABLD command replaces the VMFBLD command in your existing system generation procedures.

The prompts that CA ACF2 for z/VM displays depend on your responses to previous questions.

1. Ensure that you properly updated your system's CNTRL file for CMS. See “Step 5: Preliminary CMS Installation Steps” for information.
2. To access the disks required to generate your CMS nucleus, enter the following command:

   For the test system, enter

   VMFSETUP ppfname CMSTEST
   

   For the production system, enter

   VMFSETUP ppfname CMS
   

   ppfname

   The name of your PPF file. The filename for the PPF file is ACFZnnn.

   where nnn is the version and release of VM

3. You must perform this step on a CP system with CA ACF2 for z/VM for VM r12 installed. Use the CAXABLD EXEC to invoke your normal system generation command. For example, if you currently generate your system with the VMFBLD $ppfname CMS (PUNCH command, enter the following command:

   For the test system, enter:

   CAXABLD ACFCMS VMFBLD PPF ACFZnnn CMSTEST CMSLOAD (ALL
   

   For the production system, enter:

   CAXABLD ACFCMS VMFBLD PPF ACFZnnn CMS CMSLOAD (ALL
   

   where nnn is the version and release of VM

4. Review the CMS nucleus load map. There should be no undefined external references. The following intercepted modules are in the CMS nucleus map:

   DMSCIT

   DMSEXI

   DMSSOP

   DMSSVT

   Review the CAXALOAD Summary Log for CMS that contains information reflecting the new references the CAXALOAD control file changed. This log is in the CAXALOAD SUMMARY A1 file. Rename this file so future nucleus generations do not erase the old file to create another with the same name.

5. To IPL the new CMS system, enter the following command:
6. Ensure that the new CMS system works correctly. For example, XEDIT a file or issue an ACCESS command. If these commands work as expected, continue installing CA ACF2 for z/VM. If they do not work, verify Steps 4, 5, and 6 completed successfully.
7. If you selected the optional CMS/DOS protection, issue the following command based on your VM release:

   For the test system, enter:

   VMFBLD PPF ACFZnnn CMSTEST DMSBLDOS (ALL
   

   For the production system, enter:

   VMFBLD PPF ACFZnnn CMS DMSBLDOS (ALL
   

   Where nnn is the version and release of VM

8. If you are installing CMS/DOS protection, see the IBM Service Guide for information on how to generate your CMS/DOS and related segments. If you are installing CA ACF2 for z/VM for VM VSAM AMSERV support, see the “Installation Options” chapter before resaving your VSAM segments.
9. To install CA ACF2 for z/VM support for VSAM AMSERV, See the “Installation Options” chapter.

When you respond with COMPLETE, you see the following information:

Step 7 is complete.