Customizing after installation
When the CHECK PLUS for DB2 product is installed by using the BMC Software Installation System, the customization process generates a customized installation data set. This data set contains customized jobs that are created to install CHECK PLUS into your specific Db2 environment. The following jobs establish the default processing option values that CHECK PLUS uses:
Job | Macro name | Description | Reference |
|---|---|---|---|
$732DOP2 | $ACKOPTS | Establishes the defaults for the basic processing options | |
$532SOPT | $AUPSMAC | Contains BMCSORT and dynamic work file allocation options |
These jobs assemble options macros. The macros contain the CHECK PLUS processing options and the values for those options that are shipped with CHECK PLUS and BMCSORT. When an Installation System-generated customization job is submitted, it links the ACK$OPTS installation options module in the APF-authorized library that is designated by your site. If any values for these options were changed during customization, the new values override the values from the options macro.
You can customize the installation of CHECK PLUS by changing the values for the CHECK PLUS installation options. However, if you change any of the values in $730DOP2 or $532SOPT after the CHECK PLUS has been installed, you must rerun the jobs for these changes to take effect.
You can also create additional options modules that allow you to use different values for these options for different runs of CHECK PLUS. For example, you might use the default installation options module for most jobs, but create another options module with customized values for certain options for special situations.
For information about specifying an options module at execution time, see Building-CHECK-PLUS-jobs. For more information about customizing your installation of CHECK PLUS, see Customizing after installation
Basic CHECK PLUS installation options
The following table provides information about the values that are shipped with this version of CHECK PLUS for the options contained in the $ACKOPTS macro in $C30DOPT. Value for each option that ships with this version of CHECK PLUS (or lowercase none for no value).
- Brief description
- Hyperlink to more details
If an option is shipped with no value, the table shows a recommended value or example value.
Option | Shipped value | Brief description | Reference |
|---|---|---|---|
ACFORTSS | YES | Whether or not to use CA ACF2 or CA Top Secret | |
DRNDELAY | 1 | Minimum number of seconds to wait before the next attempt to obtain a drain | |
DRNRETRY | 255 | Maximum number of times to attempt to obtain a drain before terminating | |
DRNWAIT | NONE | Timeout value for object drains | |
DSER | NO | Whether to write discard serialization records | |
DSPLOCKS | DRNFAIL | How to display locks if the drain times out | |
FILECHK | FAIL | Which action to take when encountering a temporary work file | |
HISTORY | YES | Whether to update the BMCHIST table during the UTILTERM phase | |
LOADDECP | NO | Whether to use a DSNHDECP other than the local subsystem default | |
LOCKROW | YES | Serialization method for BMCSYNC and BMCUTIL | |
MAXP | 5 | Maximum number of partitions to check concurrently | |
MSGLEVEL | 1 | Default for the message-level execution parameter | |
MSGSEV | () | Severity code to assign to the specified message | |
OPNDB2ID | YES | Whether to use the user’s RACF ID instead of the DB2 RACF ID | |
PLAN | ACK1010 | Product plan name | |
SMAX | 16 | Maximum number of sort processes to invoke concurrently | |
SMCORE | (0K,0K) | Maximum amount of sort memory | |
SORTNUM | 32 | Number of sort work files per sort task for BMCSORT to allocate dynamically | |
SQLDELAY | 3 | Number of seconds between retry attempts after SQLCODE –911 | |
SQLRETRY | 100 | Number of retry attempts after SQLCODE -911 | |
UXSTATE | SUP | How to invoke Db2 user exits | |
WBUFFS | 20 | Multiplier for the amount of buffer pool storage for work data sets | |
WORKUNIT | SYSALLDA | Temporary unit for work data sets | |
XBLKS | 3 | Number of blocks for key data transfer | |
XBMID | None Example value: XBMA | XBM subsystem that UNLOAD PLUS accesses when it uses XBM or SUF | |
ZIIP | ENABLED | Whether to enable zIIP processing |
This section contains the following topics:
Related topics