NetBatch-Plus Reference Manual

Introducing NetBatch-Plus
NetBatch-Plus Reference Manual—522461-002
1-6
Storing NetBatch Job Descriptions in the NetBatch-
Plus Database
Storing NetBatch Job Descriptions in the
NetBatch-Plus Database
One of the main functions of the NetBatch-Plus application is to store descriptions of
NetBatch jobs in its database. You can select jobs from the database as often as you
need and submit them to NetBatch schedulers for execution.
When you submit a job from the NetBatch-Plus database, the job becomes an object of
the scheduler and, as such, is stored in the scheduler’s database. The scheduler
deletes the job from its database when execution finishes unless the job has an
attribute specifying automatic rescheduling. The job’s description, however, remains in
the NetBatch-Plus database; you can therefore select it for submission to a scheduler
whenever necessary.
The NetBatch-Plus application offers easy entry and maintenance of job descriptions
through its defaults set, catalog attachment, and dependency facilities. This subsection
briefly describes these facilities.
Using Defaults Sets
Defaults sets are the source of default attributes for all job descriptions in the
NetBatch-Plus database. They also specify other job-related information such as
scheduler names.
You can assign a single defaults set to any number of jobs. This simplifies entry of jobs
having attributes in common because you enter the attributes only once rather than
many times. Similarly, maintenance of jobs sharing a defaults set is easy because you
need only update the defaults set.
You can override defaults set attributes for individual jobs if necessary. When you
override a defaults set attribute for a job, you can no longer maintain that attribute for
the job through its defaults set. By defining appropriate defaults sets, however, you can
ensure that all or most attributes default, saving you time and effort in entering new
jobs.
Figure 1-3 on page 1-7 shows jobs in the NetBatch-Plus database adopting their
attributes from the defaults set they use.
For example, job DAILY-BACKUP adopts all its attributes from defaults set
DEVLP-SET. Job MKTG-REPORTS, however, adopts some of its attributes from
defaults set SALES-SET but overrides the executor program and output file specified
by that set. Similarly, jobs DAYLOG and TIDY-UP adopt some of their attributes from
their respective defaults sets but override others.