There are two types of CAXALOAD control files:
The base control file identifies the base and component control files that update an IBM LOADLIST for a particular VM operating system release. It contains the filenames of base and component control files. The base and component control files contain statements to control the changes applied to a particular IBM LOADLIST. The component control file contains CA ACF2 for z/VM control statements to implement CA ACF2 for z/VM on a specific VM operating system base release and implement site operating system dependencies or customization requirements.
To generate an CA ACF2 for z/VM protected CP and CMS nucleus on a base VM operating system release with no site‑developed system dependencies, use the unmodified distributed CAXALOAD control files. (See the Bundle Control Statement into Control Files section for information about site‑developed system dependencies.) CA ACF2 for z/VM selects the appropriate control files for you. You do not need to understand the CAXALOAD control statement syntax or how to bundle these control statements into control files.
If you do have site dependencies, CA ACF2 for z/VM can still select the appropriate control files for your release. It automatically tailors your base control file for these dependencies and prompts you for your site dependencies. You do not need to fully understand control statement syntax or packaging.
To customize your CP and CMS nucleus, you need to understand CAXALOAD control file syntax and how to bundle control statements. Put your customized control statement in a component file named USER CAXALOAD or in a USERCMS file for CMS. Then uncomment the component filename in the base control file. Never change the CA ACF2 for z/VM distributed base and component files.
The rest of the sections in this chapter explain:
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|