The following sections explain how to use the base and component control files to customize your system.
CA ACF2 for z/VM automatically builds base control files for you or you can build your own. Each base control filename identifies the CP or CMS release. These files contain a list of component control filenames that the CA loader program (CAXALOAD) processes. Each CA ACF2 for z/VM component control file may be required, depending on your CP or CMS release, generation level, and your site dependencies. Site‑dependent component control files define options that CA ACF2 for z/VM must know about (for example, user‑selected VSAM database sharing).
CA ACF2 for z/VM prompts for information regarding your CP and CMS release and site dependencies, then tailors your base control file for you. Edit the base control file to make necessary modifications (such as adding a component file).
The following is a diagram showing you how CA ACF2 for z/VM builds the base control file:
LISTTYPE CONTROL component control filename . . . component control filenamex
In the previous example,
Must be the first uncommented statement (identifies this file as a base control file)
Component CAXALOAD control statement files. Options of the CA ACF2 for z/VM component files name the option they provide. CA ACF2 for z/VM selects the appropriate component files for you. See your base control file (ACFCP or ACFCMS) for the component files that apply to your CP and CMS release.
When you run a CA loader program, it processes the base control file base and component CAXALOAD files and builds an incore table of CAXALOAD control statements. Component control files that appear lower in the base control file can override or augment previously listed component control files. As CA ACF2 for z/VM reads each CAXALOAD statement, it replaces or adds duplicate entries to the table, as required by the control statement syntax. See the Add and Relocate Modules section for this syntax. The combined CAXALOAD incore table drives your CA ACF2 for z/VM CP/CMS nucleus generation.
The following is an example of a CP CAXALOAD base control file:
LISTTYPE CONTROL * ACFCP630 * VM 6.3.0 CAXALOAD component file for CP UCENGRES * Optional uppercase English lang support *USER * User maintenance override file ***
We do not supply the USER component control file. The USER component control file should be last.
If you create a USER component control file, uncomment the USER statement in the base control file. To uncomment the USER statement, remove the asterisk preceding USER.
The following is an example of a CMS CAXALOAD base control file:
LISTTYPE CONTROL ACFCMS27 * VM CMS 27 CAXALOAD component file *USERCMS * User maintenance component file ***
We do not supply the USERCMS component control file. The USER component control file should be last.
If you create a USERCMS component control file, uncomment the USERCMS statement in the base control file. To uncomment this statement, remove the asterisk preceding USERCMS.
Component control files contain functional statements for module names required for your VM operating system release. Do not change these files. Use the USER component files to make changes.
The optional features of the component control files or an IBM APAR categorize optional statements they provide (such as shared database support). They can be the ones shipped with CA ACF2 for z/VM or user‑generated.
Listed below is a sample module for the upper case English language support:
*** * Following module added for uppercase English language support * CPPAG HCPAL0 ***
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|