CHECK PLUS installation options
You must be using a version of your security product that enables external security calls for Db2. If you have one of these security products installed, but the version does not support external security, specify NO for this option.
For more information, see Required authorization.
BMCSYSADM=adminuser
If the installation practice is to remove authority from the Install SYSADM, the installation can specify an alternate user ID for this access using the BMCSYSADM user options parameter.
By default, the Install SYSADM user performs the dynamic bind process.
To use a different user other than the one specified in DB2 ZPARM, you can use BMCSYSADM user options parameter to assign a different user with SYSADM authority. This option does not give the user any additional Db2 authority and is specified only in the user options.
Overriding this option
There is no command to override BMCSYSADM option.
DRNDELAY=1
After a drain time out, the DRNDELAY option specifies the minimum number of seconds that CHECK PLUS waits before it tries again to obtain the drain. The number of seconds can range from 1 through 1800.
Overriding this option
To override the option value, use the RETRY_DELAY command option (RETRY_DELAY).
DRNRETRY=255
The DRNRETRY option specifies the maximum number of times that CHECK PLUS attempts to obtain a drain before it terminates the job. The number of retry attempts can range from 0 through 255.
Overriding this option
To override the option value, use the RETRY command option (DRNRETRY=255 ).
DRNWAIT=NONE
The DRNWAIT option specifies the drain timeout value that you want CHECK PLUS to use. The wait time applies to each object involved in the check. The value NONE tells CHECK PLUS to time out immediately if the drain cannot acquire the lock. NONE prevents any application transactions from being queued during the drain process. We recommend that you specify NONE in high-transaction environments, such as SAP.
If you specify UTIL, CHECK PLUS uses the standard Db2 utility timeout value defined in DSNZPARMS for your site (IRLMRWT multiplied by UTIMOUT).
If you specify SQL, CHECK PLUS uses the standard SQL timeout value (IRLMRWT) as the drain timeout value. The wait time applies to each object involved in the check.
If CHECK PLUS cannot drain all of the objects within the time period specified by DRNWAIT, CHECK PLUS releases the drains it has obtained so far, waits the time that you specified in DRNDELAY, and tries to drain the objects again for the number of times that you specified in DRNRETRY.
Overriding this option
To override the option value, use the DRAIN_WAIT command option (DRNWAIT ).
DSER=NO
The DSER option tells CHECK PLUS whether to write discard serialization records to enable the ACKESQL program to reset CHKP status, lock tables during processing, or do both. For more information about these options in the ACKESQL program, see SQL-batch-execution-program.
Overriding this option
To override the option value, use the DISCARDSERIALIZE command option (DISCARDSERIALIZE).
DSPLOCKS=DRNFAIL
The DSPLOCKS option tells CHECK PLUS what action to take regarding displaying claims and locks if a drain attempt times out. The value DRNFAIL tells CHECK PLUS to display the claims and locks once, after the final attempt to obtain the drain times out.
If you specify NONE, CHECK PLUS does not display any claims or locks.
If you specify RETRY, CHECK PLUS displays the claims and locks after each drain timeout.
Overriding this option
To override the option value, use the DSPLOCKS command option (DSPLOCKS).
FILECHK=FAIL
The FILECHK option specifies the action that CHECK PLUS should take when SYSERR has been allocated as a temporary data set:
FILECHK=FAIL tells CHECK PLUS to terminate.
FILECHK=WARN tells CHECK PLUS to issue a warning message and continue processing.
For a definition of temporary data sets within CHECK PLUS, see Work-file-validity-checks.
HISTORY=YES
The HISTORY option specifies whether to update the BMCHIST table. If you specify YES, CHECK PLUS updates the BMCHIST table during the UTILTERM phase. If you specify NO for this option, CHECK PLUS bypasses any updates to the BMCHIST table.
LOADDECP=NO
CHECK PLUS always loads a copy of DSNHDECP from the STEPLIB so that the utility can obtain the Db2 subsystem ID value if it is not specified in the JCL. If you specify YES, CHECK PLUS obtains all Db2 installation default values from the STEPLIB copy. If you specify LOADDECP=NO, CHECK PLUS locates DSNHDECP in Db2 subsystem memory to obtain Db2 installation default values (other than the SSID).
LOCKROW=YES
The LOCKROW option tells CHECK PLUS which serialization method to use when updating the BMCSYNC and BMCUTIL tables:
- LOCKROW=YES tells CHECK PLUS to use MVS enqueues instead of the SQL LOCK TABLE statements for serialization. Using LOCKROW=YES should prevent most SQL –911 return codes from occurring as a result of multiple BMC products concurrently updating the BMCSYNC and BMCUTIL tables.
- LOCKROW=NO tells CHECK PLUS to use the SQL LOCK TABLE statements for serialization when updating the BMCSYNC and BMCUTIL tables.
The following considerations apply to the LOCKROW option:
- Using LOCKROW=YES requires row-level locking. You must define the BMCSYNC and BMCUTIL tables with LOCKSIZE ROW to achieve row-level locking.
- The following BMC products must use the same LOCKROW value within a subsystem: CHECK PLUS, BMC AMI Copy, LOADPLUS, BMC AMI Recover, REORG PLUS, and UNLOAD PLUS. Regardless of the value assigned for LOCKROW, COPY PLUS and RECOVER PLUS always behave as if LOCKROW=YES.
- In a future release, CHECK PLUS will no longer require support for the LOCKROW installation option.
MAXP=5
The MAXP option specifies the maximum number of partitions to check concurrently.
MSGLEVEL=1
This option controls which messages CHECK PLUS returns in the SYSPRINT data set. MSGLEVEL=0 returns minimal messages. MSGLEVEL=1 returns additional messages to help you diagnose problems and fine-tune performance.
Overriding this option
To override the option value, use the MSGLEVEL parameter on the EXEC statement. For information about this parameter, see Message level (MSGLEVEL).
MSGSEV=( )
The MSGSEV option tells CHECK PLUS to use the severity indicator that you have assigned to the specified messages in this option rather than the default. You can change the severity indicator for one or more of the messages from BMC52401 through BMC52599 to any of the severity indicators listed.
MSGSEV severity codes
Severity code | Meaning | Return code | Description |
|---|---|---|---|
I | Informational | 0 | The message is issued for informational purposes only and does not mean that an error occurred. |
W | Warning | 4 | The utility encountered a condition that allows it to proceed, but you might have to take additional action. |
E | Error | 8 | An error occurred that is probably a command error, JCL specification error, or other error that requires your attention. |
S | Severe | 12 | The utility encountered an unexpected processing error that does not preclude the utility from terminating in an orderly fashion. |
U | Unrecoverable | 16 | The utility encountered an error that makes it impossible to continue processing (for example, an abnormal termination). |
The format for specifying a message is MSGSEV=(nnnnni, nnnnni, . . .), where nnnnn is the five-digit message number and i is the severity indicator or O.
If you specify MSGLEVEL(1) in the EXEC statement (or MSGLEVEL=1 in the installation options), CHECK PLUS issues the message BMC50471I in the SYSPRINT output and lists the messages whose severity indicators have been changed.
NEWFUNC=COMPAT
The NEWFUNC=COMPAT parameter determines whether the CHECK PLUS uses BMCSORT or AMISORT when sorting is required.
Value | Description |
|---|---|
COMPAT | (Default) CHECK PLUS uses BMCSORT. |
ENABLE | CHECK PLUS uses AMISORT. |
Overriding this option
You can override the installation option value NEWFUNC=ENABLE at the JOBSTEP level by using NONEWFNC DD, which is NONEWFNC DD DUMMY. Before enabling AMISORT, you might need to configure a specific DFSMS STORCLAS for dynamic allocation of SORTWORKs. If there is no DFSMS STORCLAS dictated by your installation for allocation of SORTWORKs, you might omit this step, otherwise refer to the specific DYNALOC SORTCLAS parameter at the product level or CHECK SORTSTCLAS keyword.
OPNDB2ID=YES
The OPNDB2ID installation option tells the utility which user ID to use when opening or performing Access Method Services (AMS) functions on Db2 data sets:
- OPNDB2ID=YES tells the utility to use the Db2 DBM1 user ID.
- OPNDB2ID=NO tells the utility to use the user ID that is running the utility. If you specify NO, the user ID must have the appropriate authorization.
For any security system other than RACF or ACF2, the submitting user ID is always used and the OPNDB2ID installation option is ignored.
PLAN=ACK1310
The PLAN option specifies the name of the product plan. This plan contains the packages that provide the various capabilities of CHECK PLUS.
SMAX=16
The SMAX option specifies the maximum number of sort tasks that can run concurrently during a check. If sorting is required to perform the check, this value also limits the number of concurrent sorts. This can have a significant impact on performance because sort requires a substantial amount of system resources. For more information, see Controlling the number of sort processes (SMAX and MAXTASKS).
SMCORE=(0K,0K)
SMCORE specifies the amount of memory that you want each invocation of BMCSORT to use. We strongly recommend that you use the values 0K and 0K for this option. For more information, see Tuning-to-improve-memory-use.
The values 0K and 0K tell CHECK PLUS to determine the appropriate amount of memory to use for each sort based on the following criteria:
- Number of sorts to process
- Value that you specify for REGION in either your JCL or system exits
- Amount of memory that is available during optimization
The first value specifies the total amount of memory to use both above and the 16-megabyte line for each sort. You can specify this value in either kilobytes or megabytes. The following values are valid for this parameter:
- 0K (or 0M) tells CHECK PLUS to determine the appropriate amount.
- Any value from 4,096K through 6,5536K (or 4 MB through 64 MB) tells CHECK PLUS to use the specified amount.
The second value specifies the amount of memory that is required for the 16-megabyte line for each sort process. You can specify this value in either kilobytes or megabytes. The values are valid for this parameter:
- 0K (or 0M) tells CHECK PLUS to determine the appropriate amount.
- Any value from 256 KB through 4,096 KB (or 1M through 4M) tells CHECK PLUS to use the specified amount.
SORTNUM=32
The SORTNUM option affects the allocation of sort work files when BMCSORT is allocating your sort work files dynamically. You can specify any integer value from 0 through 255.
The following table describes the action that BMCSORT takes for each value that you can specify for this option. The table also provides any additional considerations for these values.
Value | Description | Additional considerations |
|---|---|---|
0 | BMCSORT honors the value of the third parameter of the BMCSORT DYNALOC installation option. (This parameter tells BMCSORT whether to dynamically allocate sort work files.) | For more information about this parameter, see DYNALOC-installation-option. |
1–32 | BMCSORT dynamically allocates the number of sort work files that it needs, up to 32 minus any sort work files that are allocated in your JCL. This number is per sort task. | None |
33–255 | BMCSORT dynamically allocates the number of sort work files that it needs, up to the number that you specify minus any sort work files that are allocated in your JCL. This number is per sort task. | None |
Specifying a value greater than 0 for this option also produces the following results:
- If the value of the third parameter in the BMCSORT DYNALOC installation option is OFF, specifying a value greater than 0 for the SORTNUM option turns BMCSORT dynamic allocation on, and BMCSORT allocates sort work files as needed.
- SORTNUM provides the information that lets CHECK PLUS run multiple concurrent sort tasks when applicable. If you do not specify a value greater than 0 for this option and only BMCSORT is allocating your sort work files, CHECK PLUS uses a single sort task.
Overriding this option
To override the option value, use the SORTNUM command option.
SORTSTCLAS=STORCLAS
The SORTSTCLAS option affects what STORCLAS AMISORT uses when dynamically allocating sort work files. You can specify a valid DFSMS STORCLAS.
SQLDELAY=3
The SQLDELAY option specifies the number of seconds that CHECK PLUS should wait between retry attempts after receiving an SQL –911 return code. This interval is in addition to the time that elapses when Db2 waits for a timeout or deadlock. The number of seconds can range from 1 through 655.
SQLRETRY=100
SQLRETRY specifies the number of times that CHECK PLUS should retry an SQL statement after it receives an SQL –911 return code. The number of retries can range from 1 through 255.
UXSTATE=SUP
The UXSTATE option tells CHECK PLUS how to invoke Db2 exits:
- UXSTATE=SUP indicates that CHECK PLUS should call Db2 EDITPROCs in supervisor state (and PSW key=7).
- UXSTATE=PROB tells CHECK PLUS to call Db2 EDITPROCs in the problem state (and PSW key=7).
The requirements of the EDITPROC dictate the UXSTATE setting. Check with the EDITPROC author (or vendor) before changing to UXSTATE=PROB.
WBUFFS=20
The WBUFFS option specifies a multiple of 32 KB to use to define the amount of buffer pool storage for each of the work files, SYSERR and SYSDISC.
WORKUNIT=SYSALLDA
The WORKUNIT option specifies the unit to use for a temporary work data set. VIO is an acceptable value for this option.
XBLKS=3
The XBLKS option specifies the number of blocks used for transferring key data.
XBMID=
The XBMID option specifies the SUF (also known as XBM) subsystem ID (SSID) to be active when using SUF (also known as XBM) with CHECK PLUS. If you do not specify the SSID as an installation option, you must specify it as a command option in either of the following cases:
- You are specifying SHRLEVEL CHANGE (which uses the snapshot-processing functionality of SUF (also known as XBM)).
- You want to use a specific SUF (also known as XBM) subsystem for zIIP processing.
The SSID is the unique identifier that was specified when SUF (also known as XBM) was installed. If you are using SUF (also known as XBM) in a Db2 data sharing environment, you can use the value of the XBMGROUP parameter instead of the SUF (also known as XBM) SSID. The XBMGROUP name is the name of the cross-system coupling facility (XCF) group that is defined to the SUF (also known as XBM) subsystem, and its default value is XBMGROUP.
zIIP processing
If you specify an SUF (also known as XBM) subsystem and ZIIP ENABLED is in effect, CHECK PLUS attempts to use that subsystem to enable zIIP processing. If that subsystem is not available or not at the correct maintenance level, zIIP processing is not enabled.
If you do not specify an SUF (also known as XBM) subsystem (either here or with the XBMID command option), CHECK PLUS searches for an SUF (also known as XBM) subsystem at the appropriate maintenance level to enable zIIP processing.
Overriding this option
To override the option value, use the XBMID command option.
ZIIP=ENABLED
The ZIIP option tells CHECK PLUS whether to attempt to use IBM System z Integrated Information Processors (zIIPs). CHECK PLUS can use enclave service request blocks (SRBs) to enable zIIP processing automatically while running jobs. Using zIIP processing can reduce the overall CPU time for CHECK PLUS jobs.
You can specify one of the following values:
- ENABLED tells CHECK PLUS to attempt to offload eligible processing to an available zIIP. If the zIIP is busy or not available, normal processing continues on a general-purpose processor.
- DISABLED tells CHECK PLUS to not attempt to use zIIP processing.
To enable and use zIIP processing with CHECK PLUS, you must:
- Have an installed authorized version of SUF (also known as XBM)
- Start and maintain an SUF (also known as XBM) subsystem in your environment
- Have a zIIP available in your environment
Using SUF (also known as XBM)
You can specify a particular SUF (also known as XBM) subsystem to use for zIIP processing by specifying a value for the XBMID installation or command option. For more information, see XBMID=.
SUF (also known as XBM) are licensed, installed, and maintained separately from CHECK PLUS. You can use either SUF (also known as XBM), depending on the license that you have obtained:
- License for the full version of the SUF (also known as XBM) product authorizes you to use all features of SUF (also known as XBM).
- License for SUF (also known as XBM) authorizes you to use only the snapshot and zIIP processing features of SUF (also known as XBM).
For more information about SUF (also known as XBM), see the SNAPSHOT UPGRADE FEATURE for DB2 documentation.
Overriding this option
To override the option value, use the ZIIP command option.