NetBatch-Plus Reference Manual

Setting Up the Processing Environment
NetBatch-Plus Reference Manual—522461-002
4-14
7. Plan for Bulk Submit Processing
•
One way to identify job groups is by listing, in date order, the run dates for your
jobs. This process suggests obvious job groupings (all jobs due to run on the
same date) you might decide are sufficient.
•
To take the grouping process one step further, look for specific groups among
jobs with common run dates. For example, jobs with a run date of Monday 15
might be daily jobs, jobs that run every Monday, or jobs that run every month
on the fifteenth. The relationship between jobs does not have to be calendar-
based. The relationship might result from a similar function or purpose. For
example, some of the jobs due to run on Monday 15 might be jobs from a
particular department.
2. After you identify appropriate job groups, plan the selection criteria for those jobs.
Selection criteria are the means by which the bulk submit program selects and
submits the jobs for execution. The program can select jobs by a date or category.
For jobs grouped by function or purpose, choose a suitable category name for the
group. For example, ADMIN might be the name for jobs originating from your
administration department. For jobs grouped by date, you can specify the selection
date explicitly for each job or implicitly via a calendar category. For more
information on selection criteria, selection dates, and calendar categories, see Bulk
Job Selection Criteria on page 6-6 and Calendar on page 6-23.
3. Establish information about the bulk submit control job. (The control job submits
jobs in a bulk submit run to their respective schedulers.) To plan the environment,
determine the control job’s scheduler, class, owner, and window (both the retention
period for temporary output files created during bulk submit runs and the period
before execution that users can schedule those runs). The environment also
specifies the default output file for bulk submit reports. You therefore need to
choose an appropriate location for these reports.
Example
Figure 4-7 on page 4-15 gives an example of a table showing information used to
determine calendar categories and other bulk job selection criteria. The table lists and
describes jobs, their run dates, and their originating departments.
From the information in the table, you can identify various selection criteria for the jobs.
For example, you could create a calendar category called MONTH15 containing the
run dates for Job M. For the backup jobs (Jobs N and O), you could use the names
BACKUP or OPERATIONS as the selection criterion for those jobs. (BACKUP would
be for backups specifically whereas OPERATIONS would be for other jobs from the
operations department besides backups.)
Similarly, you could use the name CUSTSERV as the selection criterion for jobs from
the customer services department (Jobs K and U).
An alternative to using CUSTSERV is to create a calendar category called FIRSTDAY.
This category would contain all first-day-of-month dates. You could use it without
qualification for the monthly statements produced by Job U. For Job K, however, you
would need to exclude from the job’s selection criteria dates other than 01 January and