NetBatch-Plus Reference Manual

Setting Up the Processing Environment
NetBatch-Plus Reference Manual—522461-002
4-8
4. Plan Defaults Sets
As well as showing the executors assigned to each CPU, it also illustrates class
distribution among those executors. For example, classes C1 through C4 are
assigned, in different order, to four executors (E1, E4, E8, and E12), each of which is
assigned to a different CPU. Jobs in classes C1 through C4 have equal processing
opportunities because each class appears once at the top of a class list, once in
second position, and so on.
4. Plan Defaults Sets
After identifying existing and potential batch jobs and planning schedulers, classes,
and executors, you can plan the defaults sets for your system. As with schedulers,
classes, and executors, you get some of your information from your original job table.
This time, however, you use information from all of the other tables created so far.
Planning Considerations and Recommendations
The objective in planning defaults sets is to plan only those sets needed to set up jobs
identified in your job table. Because that table highlights similarities between jobs, it
helps you identify jobs that can share a common defaults set. Each job you define
must have a defaults set.
Users can add their own defaults sets after setup of the initial processing environment.
For example, a department manager could define a set for use by all members of the
department. Users could also create defaults sets for jobs with similar functions such
as payroll or accounts payable jobs.
Example
Figure 4-4 is an example of a table recording planning information about defaults sets.
The table contains information derived mainly from the job table. It also contains some
information from the scheduler table and classes and executors table.
The example illustrates how features common to jobs running in the same scheduler
help you identify defaults sets. In the example, most jobs running in the scheduler
\ADMIN.$MGR have the same class, owner, executor program, and output file. These
jobs have enough characteristics in common to warrant having their own defaults set.
Similarly, you could create a second defaults set for use by jobs B, F, and G, which
have most characteristics in common except their executor programs.