Job generation options
This topic shows the job generation options that set rules for how to build the jobs that BMCTRIG generates.
The following figure shows the syntax for Job generation options.
Job generation options
The following table lists the job generation options, showing the availability by object type (INDEX (IX), INDEXSPACE (IS), TABLE SPACE (TS), and TABLE SPACE SET (TT)). Values in boldface are the default values.
Job generation options
Option name | Value | Description | Object type | |
|---|---|---|---|---|
TT, TS | IX, IS | |||
AUTOSUBMIT | Y N (default) | Indicates whether to automatically submit the generated JCL | X | X |
BEGJOBSEQ | 001 (default) through 999 ZZZ | Specifies the starting sequence value for the JOBSEQ/&JS1/&JS2 parameter that is used as part of the job name and member name Use this option to change the starting sequence number. If JOBSEQTYPE is A, BEGJOBSEQ can contain alphanumeric values. | X | X |
ELIMDUPACTS | Y N (default) | Specifies whether to remove an action if it is fully duplicated within the services of another action The services must also have the same syntax names. If BMCTRIG eliminates an action that has a higher priority than the remaining action, BMCTRIG escalates the priority of the remaining action. When BMCTRIG eliminates an action, it issues an informational message. | X | X |
ELIMDUPOPTS | Y N (default) | Indicates whether BMCTRIG should eliminate actions if they are functionally duplicated by an inline option of another service The services must also have the same syntax names. If BMCTRIG eliminates an action that has a higher priority than the remaining action, BMCTRIG escalates the priority of the remaining action. When BMCTRIG eliminates an action, it issues an informational message. This option detects inline copies and statistics collection when generating BMCREORG or IBM REORG. BMCREORG statistics collection will not eliminate RUNSTATS or BMCSTATS because it does not collect the same set of statistics. | X | X |
EVENTS | Y (default) N | Specifies whether to inserts rows into the EVENTS TABLE for BMCTRIG execution, and insert commands into the generated job stream that cause the Execution program (AEXEMAIN) to insert entries in the EVENTS table when used with the worklist format | X | X |
GENPRIORITY | 0 (default) through 255 | Specifies the occurrence priority value below which objects and their actions are eliminated This option is applied to the list of objects and their actions. If the objects and actions are eliminated from the work that is being generated, BMCTRIG issues an informational message. | X | X |
GROUP | Y N (default) | When generating corrective actions, specifies whether to include all objects in a single invocation of a utility if possible or in a single automation registration If the objects are treated as a group, they receive the priority of the object that has the highest priority in the group. BMCTRIG generates all objects for the action in a single invocation of a service. However, not all services allow grouping. For more information, see Analyzing-objects-by-using-BMCTRIG. | X | X |
JCLGEN | Y N | Specifies whether to generate jobs for corrective actions that are defined for exceptions for objects that meet or exceed thresholds that you define | X | X |
JCLWLB | Y N (default) | Specifies whether to balance the objects and corrective actions between the number of jobs that you specify in the NUMJOBS option Workload balancing takes into account object dependencies, work priority, and object size when distributing work among jobs. If you have specified priorities, BMCTRIG performs work according to priority order and secondarily balances the work. For more information, see Workload balancing. This option is valid only when you specify STDJCLY. | X | X |
JOBSEQTYPE | N (default) A | Specifies the job sequence numbers for generated JCL and determines the allowable values for BEGJOBSEQ Specify N for numeric values or A for alphanumeric values. | X | X |
MAXOBJECTS | 1-255 20 (default) | Specifies the maximum number of Db2 objects that the product can place in each generated job When the product reaches the number that you specify, it generates a new job. This option is ignored if you specify JCLWLB Y or RESIZEJOBS Y. This option is valid only when you specify STDJCLY. | X | X |
MAXREORGPARTS | 0 (default) through 4096 | Limits the number of partitions that will be combined into a single REORG or BMCREORG utility invocation If 0 is specified, no limit on the number of partitions is set. For table space partitions, the index partition is also reorganized, but the index partition is not included in the count for limiting the number of partitions in the table space. | X | X |
MAXSTEPS | 1 through 255 (default) | Specifies the maximum number of steps for a job 255 is the maximum number and the default value. When the job steps reach the maximum number, BMCTRIG begins to generate a subsequent job. If you use this option with workload balancing, limiting the number of jobs steps might result in BMCTRIG not generating all of the work. This option is valid only when you specify STDJCLY. | X | X |
NUMJOBS or MINJOBS | 0 (default) through 999 | Identifies the minimum number of jobs to generate. Specifying 0 generates as many jobs as needed to process all objects that meet the exception criteria. When you use this option with workload balancing, the option specifies the number of concurrent jobs that BMCTRIG will use to disperse work. This option is valid only when you specify STDJCLY. | X | X |
PARTLVL | Y N (default) | Indicates whether to generate a utility job for each partition that receives an exception or triggers (Y), or generate a utility job for the entire table space or index (N) This option also affects the level of some threshold evaluation and exclusion rules | X | X |
REBIND | Y N (default) PG PL | Indicates whether to generate rebinds of affected packages or plans that are associated with objects that are affected by generated corrective actions An affected object is one for which the Db2 catalog statistics are updated during execution of the corrective action (for example, BMCREORG with UPDATEDB2 Y). The following values are valid:
| X | X |
REBVER | L (default) A | Indicates whether to include the latest (L) version or all (A) versions for the value that is selected for REBIND | X | X |
REGISTER | Y N (default) | Indicates whether to register objects and identified corrective actions to the automation components of the BMC Database Performance for DB2 solution If you have a license for BMC Database Performance for DB2, this option registers the corrective actions in the Automation candidate table. You can then execute the corrective actions by using the Automation component of BMC Database Performance for DB2. | X | X |
STDJCL | Y N (default) | Indicates whether to generate worklist JCL (N) or standard JCL (Y). This option is valid only when you specify JCLGEN Y. If you specify this option, you must also specify STDJCLDSN. | X | X |
STDJCLDSN | Data set name up to 46 characters | Specifies the data set into which jobs will be generated when STDJCLis Y Specify the data set without a member name (the generated member name will match the name of each generated job). This data set name can contain the symbolic variables &SSID and/or &WKID and/or POF user variables that will be resolved at the time the trigger job runs. | X | X |
TRIGJC n | Job cards | Specifies the default job card statement to use when submitting a BMCTRIG job DASD MANAGER PLUS uses the job cards when generating JCL. The job card value must follow the keyword on a separate line, and the entire line is taken as the job card image. The job card options must be the last options in the syntax for the command. When you specify TRIGJC1, if STDJCL Y, the job name (member name) must contain a job sequence variable such as &JS2 | X | X |
UTILDSN | Data set name up to 56 characters | Identifies the name of the data set to contain the generated worklist This can contain the variables &SSID and/or &WKID or POF user variables that will be resolved at the time the trigger job is executed. If STDJCLis N, it also contains the JCL. This data set must exist and can be partitioned or sequential. If the data set does not exist, allocate a sequential or partitioned data set as fixed block with a logical record size of 80. STDJCL has the following effect on UTILDSN:
| X | X |
UTILJOB | action | Identifies the name of a BMC Database Performance for DB2 action that the product generates for those objects with exceptions This corrective action specifies database utilities and command syntax but usually does not specify object names. If you are using system triggers, this option specifies the default corrective action for exceptions that do not have a corrective action specified in the Corrective Actions table. BMCTRIG tries to enforce the rules that apply to BMC and Db2 utilities, which might change some parameters in the service syntax. For example, if you specify SHRLEVEL CHANGE and COPYPENDING YES, the job is generated with SHRLEVEL REFERENCE. For more information about the utilities, refer to the BMC utility product spaces and the IBM DB2 Utility Guide and Reference | X | X |
WHENNOOBJECTS | S (default) C | Specifies whether to stop or continue to generate BR14 jobs when no objects are found | X | X |