Statements in a DASD MANAGER PLUS job
Building a DASD MANAGER PLUS job requires creating the following JCL statements:
- A JOB statement
- An EXEC statement with the appropriate utility parameters
- STEPLIB of JOBLIB DD statements
- DD statements for the appropriate number and size of data sets
CPU authorization passwords
BMC authorizes its products to run on specific CPUs and controls this authorization with CPU authorization passwords. After you install a permanent CPU authorization password for your processor, you do not need the password again unless you change processors.
DASD MANAGER PLUS usually stores your password in the STEPLIB or LINKLST. If the password is not in the STEPLIB or LINKLST, you can add a BMCPSWD DD statement to the JCL to identify the password location. The product attempts to locate authorization modules in the BMCPSWD DD statement (if you have allocated a BMCPSWD DD statement) before searching in the STEPLIB or LINKLST.
Following is an example of a BMCPSWD DD statement:
JOB statement
You need to include a DASD MANAGER PLUS JOB statement that conforms to your site’s standards.
You can include the REGION parameter to specify the region size (the amount of virtual storage that the utility uses) on either your JOB statement or your EXEC statement. For recommendations, see REGION parameter.
EXEC statement and utilities parameters
The DASD MANAGER PLUS EXEC statement specifies the following parameters:
- The module to be run for the DASD MANAGER PLUS utility
- The utility parameters
The following table shows the utility names with their associated module names:
Utilities and associated module names
Utility name | Associated module name |
|---|---|
BMCSTATS | ASUSMAIN |
BMCTRIG | ASUSTRIG |
BMCCPRS | ASUSCPRS |
BMCUPRS | ASUSUPRS |
The EXEC statement includes the following utility parameters:
- SSID (the Db2 subsystem ID or group attach name)
- Plan name
- Db2 catalog VCAT name
- Installation options module name
- Work ID (Service Action)
- Utility ID
- Restart parameter
Following is the format of the EXEC statement:
//PARM='<ssid>,<planName>,<VCATName>,<installationOptionsModule>,<workID>,<utilityID>,<restartParm>'
The variable module is the name of the module associated with the utility (such as ASUSMAIN for BMCSTATS).
The DASD MANAGER PLUS utility parameters are positional. If you do not specify a value for a parameter (which is the default value), you must substitute a comma for that parameter if additional parameters follow. The comma indicates that a parameter was omitted.
Db2 subsystem identifier (ssid)
The ssid parameter specifies the Db2 subsystem ID (SSID) to indicate where the object (table space, index, storage group, or object set) resides.
If you do not specify ssid, DASD MANAGER PLUS uses the Db2 installation default, which is found in the DSNHDECP module.
DASD MANAGER PLUS supports the Db2 group attachment name capability. When you supply a group attachment name as the SSID, DASD MANAGER PLUS uses the name to connect all plans; the product then determines the actual Db2 SSID from within that group to use for the current job.
Plan name (planName)
The planName parameter allows you to identify the name of the plan for the functionality that you are executing.
DASD MANAGER PLUS provides specific plans for action generation, online reports display, statistics collection, catalog update, BMCTRIG execution, and statistics display and catalog browsing. If you do not specify a plan name, DASD MANAGER PLUS uses the plan specified in the SPLAN installation option.
Db2 catalog VCAT name (VCATName)
The VCATName parameter allows you to specify the name of the Integrated Catalog Facility (ICF).This catalog is used for data set allocation for the Db2 catalog and directory table spaces and indexes.
The ICF catalog is used for data set allocation for the Db2 catalog and directory table spaces and indexes.
Default options module name (installationOptionsModule)
The installationOptionsModule parameter allows you to identify which installation options module to use.
If you include this parameter, you must specify the full name of the options module. If you omit this parameter, DASD MANAGER PLUS uses the ASUDOPT module by default.
Work ID (workID) or Service Action
The workID parameter specifies the 20-character action that generated the job. This parameter is used to populate the EVENTS and WL_SYNC tables. In DASD MANAGER PLUS, the Service Action is synonymous with the Work ID.
This parameter is required only when you do the following:
- Specify EVENT Y
- Execute the utility under AEXEMAIN (Db2 Execution Monitor)
Utility ID (utilityID)
(BMCSTATS only) TheutilityID parameter specifies the 16-character utility ID that gives a unique name to a utility job.
If you omit this parameter, DASD MANAGER PLUS uses the default, userID.jobName. Each BMC utility job should have a unique ID. If you use the HISTOGRAM or IXNUMQUANTILES keyword, the utility ID must be valid for IBM DSNUTILB.
Restart parameter (restartParm)
(BMCSTATS only) This topic describes therestartParm values. The following table lists the values that a restartParm can have:
Restart parameter values
Value | Description |
|---|---|
Blank, not specified, NEW, or NEW/RESET | Starts a new DASD MANAGER PLUS utility execution or job step and allows you to reuse a BMCSTATS utility ID that already exists in the BMCUTIL table. However, if the utility ID being reused is active (determined by MVS enqueue), the new job fails and DASD MANAGER PLUS issues a message. |
TERM or TERM/RESET | Terminates the existing BMCSTATS utility and removes the utility ID from the BMCUTIL and BMCSYNC tables without further processing - DASD MANAGER PLUS terminates with return code 0, whether or not the utility ID exists. |
MAINT | Causes DASD MANAGER PLUS to print additional information in your SYSPRINT. When you specify the MAINT parameter, the job ends without affecting any utility that is running. DASD MANAGER PLUS prints a summary report of the products fixes that you have applied. |
REGION parameter
Include the REGION parameter on either your JOB statement or your EXEC statement to specify the region size (the amount of virtual storage used by the utility).
For more information about setting these parameters, see Post-installation-considerations.
STEPLIB DD statement
The DASD MANAGER PLUS STEPLIB DD statement specifies the following libraries, unless they are included in your system’s LINKLIST or in a JOBLIB statement:
- Load library or libraries that contain the files for the following products and components:
- DASD MANAGER PLUS
DB2 Solution Common Code (SCC) DBLINK
The Installation System copies this data set into the runtime library.
Security modules (SEC) BBLINK
The Installation System copies this data set into the runtime library.
- Libraries that contain any DB2 user exits (EDITPROCs, VALIDPROCs, FIELDPROCs, and user-written conversion routines)
- DB2 load library
All load libraries in the STEPLIB or JOBLIB concatenation must be APF authorized.
BMCPSWD DD statement
In the past, DASD MANAGER always obtained licensing authorization from the data set allocation using the DDNAME of STEPLIB. The DASD MANAGER BMCPSWD DD statement lets you obtain licensing authorization from an allocated DDNAME other than the STEPLIB DD.
The DASD MANAGER authorization check routine determines whether the product has allocated a DDNAME of BMCPSWD.
- If BMCPSWD is allocated, DASD performs authorization checking against the contents of the data sets that the BMCPSWD DD references.
- If the DD is not allocated, DASD MANAGER checks the STEPLIB DD allocation.
This change provides provides an alternative method for security checking.