Specifying Job and JCL Generation options
The following figure shows the Job and JCL Generation options:
Default Action . . (Default corrective action to generate)
AUTOSUBMIT . . . . N (Y/N - Automatically Submit the Util DSN)
Worklist only . . N (Y/N - Generate only the worklist)
When No Objects S (S/C - S-Stop, C-Continue)
-------------------------- Standard JCL Options ------------------------------
Standard JCL . . . N (Y/N - Y=Standard JCL, N=Worklist JCL)
Max Objects . . . 20 (1-255 - Maximum number of objects per job)
Max Steps . . . . 255 (1-255 - Maximum number of steps per job)
Number of Jobs (0-46655 - Number of jobs to generate)
Workload Balance N (Y/N - Balance work across jobs)
-------------------------- Output Dataset Options ----------------------------
Util DSN . . . . .
Interim WL DSN . .
Note : Interim WL DSN is required when Standard JCL=Y.
Util DSN (JCL target dataset) is always required.
-------------------------- Jobcard(s) for BMCTRIG generated jobs(s) ----------
Job Sequence Type N (N/A/blank - N=Numeric A=Alpha blank=Numeric)
Beginning Seq . . (1-999/ZZZ Starting sequence value for &JOBSEQ)
Jobcard1 . . . . . //JOBC JOB (&ZACCTNUM),'&PGMR',
Jobcard2 . . . . . // CLASS=A,MSGLEVEL=(1,1)
Jobcard3 . . . . . //*
Jobcard4 . . . . . //*
Jobcard5 . . . . . //*
If you are generating corrective actions, you can specify job processing options.
To specify a data set name to hold the JCL
- In the Standard JCL field, type N for worklist format.For information about all of the other JCL generation options, see Worklist-JCL-Generation.
- In the Util DSN field, specify a data set name to hold the JCL that BMCTRIG generates.For more information, see To specify data set names (Util DSN).
To specify the maximum number of Db2 objects (Max Objects)
Max Objects specifies the maximum number of Db2 objects to place in each generated job.
In the Max Objects option on the JCL Generation panel, type one the following values:
User Input | Description |
|---|---|
1 | Generates one object for each job |
User specified number | When the number that you specify is reached, a new job is generated. |
Blank | The default number of objects, 20, will be placed in the job |
To specify data set names (Util DSN)
Specify data set names, as follows:
Util DSN is the name of the data set in which to place the generated utility jobs. When Standard JCL is Yes, Util DSN must be an existing partitioned data set. You do not have to specify a member name because BMCTRIG automatically generates the name based on the job name from the job card option. If Standard JCL is No, you must specify a PDS with a member or specify a sequential data set.
Before generating a BMCTRIG job that uses standard JCL, allocate this data set by using the following parameters:
DCB=(LRECL=80,BLKSIZE=23440,RECFM=FB,DSORG=PO)Interim WL DSN is the name of the data set into which to place the interim worklist statements when Standard JCL is Yes. BMCTRIG generates the interim worklist statements and inputs them to batch JCL generation.
Interim WL DSN must be a sequential data set or a partitioned data set with a member name. Before generating a BMCTRIG job that uses standard JCL, allocate this data set by using the following parameters:
DCB=(LRECL=80,BLKSIZE=23440,RECFM=FB,DSORG=PS or PO)
To specify the minimum number of jobs (Number of Jobs)
When generating standard JCL, you can specify the minimum number of jobs to generate (Number of Jobs). This option is useful when registering the generated utility jobs in a job scheduling package. Blank is the default. Blank or 0 generates as many jobs as needed to process all of the objects that meet the exception criteria. For workload balancing, this option must be greater than 1. The option indicates the maximum and minimum number of concurrent jobs that are generated for each action.
Enter the number of jobs that you require the job scheduler to generate.
You must match the jobnaming convention that the job card uses. BMCTRIG ensures that all matching jobs are current and accurate, based on the newest exceptions.
If not enough objects receive exceptions to require the specified minimum number of jobs, BMCTRIG places IEFBR14 utilities in the extra jobs.
If BMCTRIG encounters more exceptions than the specified minimum number of jobs can contain, BMCTRIG responds as follows:
- If you are not using workload balancing, BMCTRIG continues producing jobs with the naming convention from the job card until it has placed all objects with exceptions in jobs.
- If you are using workload balancing, BMCTRIG generates only the number of concurrent jobs that you specify per action. As stated earlier, BMCTRIG might also generate a grouped object job before and after the concurrent jobs and a rebind job after the concurrent jobs.
For objects that BMCTRIG cannot fit into jobs, it does not generate them and their exceptions remain active.
If more jobs exist than the minimum number of jobs that you specified, you have the following choices:
- Change Number of Jobs to the number of jobs generated for future executions of the same BMCTRIG action.
- Treat the extra jobs as one-time-only request jobs.
Ignore the extra jobs in the schedule and delete them from the utility job data set (Util DSN).
If you ignore the extra jobs, the next time that BMCTRIG runs, it identifies the objects in these jobs as exceptions and builds the utility jobs again.
If specific BMCTRIG jobs regularly exceed the Number of Jobs value, perform one of the following actions:
- Increase the Number of Jobs value to create more jobs.
Increase the Max Objects per job value to perform more work in each job.
- Refine the thresholds so that fewer objects meet exceptions.
- Use priorities on thresholds and object-actions to order important work.