NetBatch-Plus Reference Manual
Setting Up the Processing Environment
NetBatch-Plus Reference Manual—522461-002
4-3
1. Identify Existing and Potential Batch Jobs
You can usually derive the data you record on screen copies from information in one or 
more of your tables. For example, you can derive detailed setup information about 
schedulers from the table you create listing general scheduler information. 
As well as offering you a convenient means of recording setup information, screen 
copies let you keep hard copy records of your setup data. These records are useful, for 
example, as reference aids when you want to reset part or all of the processing 
environment to its original configuration. 
1. Identify Existing and Potential Batch Jobs
Create a table listing general information about your organization’s existing and 
potential batch jobs. This table helps you identify job types (for example, program 
compilations and backups), shared attributes, and CPU-resource and I/O-resource 
requirements. This information also helps you complete all other planning activities.
Example
Figure 4-1 is an example of a batch job table you can adapt for your own use. In the 
example, the Job Description column lists actual jobs (for example, Daylog) as well as 
job types (for example, COBOL Compiles). The remaining columns list information 
about the jobs. In your table, you can have extra columns listing estimated number of 
jobs within a type, job duration and frequency, and job priority, and so on.
Figure 4-1. Example of a Job Table
Backups—
Daily
Backups—
Weekly
Backups—
Monthly
COBOL
Compiles
Daylog
End-of-Period
Reports
File Copies
to Tape
Interest
Calculations
Job
Description
205, 255
19, 255
255, 255
Various
255, 205
19, 4
205, 70
25, 5
Owner
GOGO
AG--
AGG-
GOGO
GGGO
AAAA
GOO-
Job
Security
OOOO TACL
TACL
TACL
COBOL
TACL
ENFORM
FUP
TACL
Executor
Program
x
x
CPU-
Bound
x
x
x
x
x
x
I/O-
Bound
1
2
3
Nil
Nil
Nil
1
Nil
Tape
Drives
$S.#DLYBKUP
$S.#WKBKUP
$S.#MTHBKUP
$S.#COMPILE
$FPP.SPRVSR.DLOG
$S.#ADMIN
$S.#TCOPY
\ADMIN.$T4.#A
Output File
\DEVELOP
\ADMIN
\DEVELOP
\DEVELOP
\WORLD
\ADMIN
\DEVELOP
\WORLD
Executor
Program
Nodes
\ADMIN
\DEVELOP
\WORLD
VST007.vsd










