Customizing after installation of CHANGE ACCUMULATION PLUS

The BMC Change Accumulation utility is shipped with internal defaults that were carefully chosen to be optimal for most installations. You cannot change these default values, but you can override them by creating a global options module or by using keywords on control statements. If you do not create a global options module, the Change Accumulation utility uses the internal default values for the change accumulation run. There is a default value for every processing option. If the default is none, then blanks are considered the default value for that option.

Before you change the default value of a keyword, you should have a general understanding of that keyword. All of the keywords included in a global options module are included in the ISPF panels documented in Using-the-ISPF-interface. Also, CAPSYSIN-keywords tells you whether a keyword is used in the global options module.

Global options modules

A global options module replaces the Change Accumulation utility internal defaults and contains keyword values you want to use for most change accumulation runs.

To create a global options module, use the ISPF interface or assemble and link the CAPPARMS source module provided on the product distribution tape. BMC recommends that you use ISPF panels to create your global options modules because this method of creating and controlling your options modules is quick and easy. The panels are documented in Using-the-ISPF-interface.

You can create several global options modules, each with a different name, a different set of values, and/or a different purpose. You can create one for your production system and another for your test system. If you have several IMS systems, you can have a global options module—each with a different set of values—for each system. You can create global options modules with the following names:

CAPPARMS

Create a global options module named CAPPARMS to contain your installation’s most used default values.

In this module, change any values that your entire installation uses all the time. For example, since the default for the name that appears on the banner page of output reports is BMC, Inc., you may want to change the name. This could be the only options module you need, if the number of changes you need to make to the default values is small.

CAP@imsi

Create global options modules named CAP@imsi (where imsi reflects different IMSIDs) when you want each of your IMS systems to have different default values.

You might create two CAP@ imsi modules; the first one named CAP@TEST for your test system, and the other named CAP@PROD for your production system.

CAP@xxxx

Create modules named CAP@xxxx (wherexxxx is any four-character identifier) when you want to create global options modules for other purposes, such as testing various Change Accumulation utility features.

Specify that appears on the banner page of output reports on the GLBL control statement to request a global options module named this way.

CAPPARMS sample

The product sample library, included on the product distribution tape, has two members that you use when you want to create a global options module in batch rather than using the ISPF interface: CAPPARMS and CAPASML.

The CAPPARMS member is a prototype for creating the global options module in batch. The keywords in this member match the internal defaults. Modify these keywords as you wish. You can also change the name CAPPARMS to any other valid name (CAP@xxxx). When you complete the modifications, use Assembler Level H to assemble CAPPARMS and then link-edit the CAPPARMS into the product load library.

The CAPASML member assembles and link-edits the CAPPARMS member for you. Modify the CAPASML JCL to reflect the product sample and load libraries at your installation.

The global options module is available for use by any job executed after you link-edit it into the product load library.

Keywords on control statements

Even though you use a global options module for most of your runs, for certain change accumulation runs, you might want to use a different value for a few keywords.

Set these values by including keywords on the control statements in the CAPSYSIN data set. A keyword value included on a control statement overrides the corresponding keyword value on the CAP@xxxx, CAP@imsi, CAPPARMS global options modules or the internal default.

Processing hierarchy

The Change Accumulation utility obtains run options from the internal defaults or a global options modules, and control statement keywords. The first step in a run is building an options table. The options table is a control block that contains all of the options. This table is internally generated and exists only for the duration of the run. Information in the options table is built by merging the following:

• Keywords on the control statements
• Internal defaults or global option modules (CAPPARMS, CAP@imsi, or CAP@xxxx)

Merge options

The following figure shows how the Change Accumulation utility builds the options table at the beginning of each change accumulation run.

The following steps describe how the Change Accumulation utility builds the options table:

1. Build the global portion of the options table. The Change Accumulation utility builds the global portion as follows:
   • PARMBLK Keyword. The utility looks for the PARMBLK keyword on the GLBL statement. You can use the PARMBLK keyword to specify a specific option module to use when building the option table. If the PARMBLK keyword is not found, the utility looks for a CAP@imsi module.
   • CAP@imsi Module. The utility looks for a module called CAP@imsi in the STEPLIB library, where imsi is the IMSID stored in RESLIB. If it finds CAP@imsi, the utility uses the values specified in the module. If the CAP@imsi module is not found, the utility looks for a CAPPARMS module.
   • CAPPARMS Module. The utility looks for a module called CAPPARMS in the STEPLIB concatenation. If the CAPPARMS module is not found, the utility uses the internal defaults.
   • Internal Defaults. The utility uses the internal defaults if it does not locate a PARMBLK keyword, a CAP@imsi module, or a CAPPARMS module. The defaults are listed in the documentation for individual keywords.
2. Merge any other keyword values specified on the GLBL control statement into the options table. Keywords used on the GLBL control statement override the corresponding internal defaults, and keywords specified in the global options module.
3. Merge keywords values specified on the LOG and SORT control statements. Keywords specified on the LOG and SORT control statements override corresponding internal defaults, keywords specified in the global options module, and on the GLBL control statement.
4. Merge any keyword values specified on the GROUP control statement. Keywords on the GROUP control statement are effective until the next GROUP control statement is encountered or until the end of the job step. GROUP control statement keywords override corresponding internal defaults, and keywords specified in the global options module or on the GLBL control statement.
5. Merge CA or IIC control statement keyword values. Keywords used on a CA and IIC control statements override the corresponding keywords specified on the GLBL and GROUP control statements, the global options module, and the internal defaults.