NetBatch-Plus Reference Manual

NetBatch-Plus Screens
NetBatch-Plus Reference Manual—522461-002
6-78
Field Descriptions
An executor name can contain from 1 through 24 letters and numbers. It can also
contain hyphens (-). The name must begin with a letter and can end with any letter or
number but not with a hyphen.
CPU
Use the CPU field to set the CPU attribute of the executor named in the Executor
Name field. The attribute specifies the CPU where the executor program process of
any job associated with the executor runs. Other processes started by the job also run
in the CPU unless otherwise specified.
To set the CPU attribute, enter an integer in the range 0 through 15 identifying a CPU
available on your system. An executor can have only one CPU assigned to it, but that
CPU can be shared by other executors. You cannot leave the CPU field blank when
you add or update the executor.
When a CPU fails, the state of any executor to which it is assigned changes to DOWN.
A job whose executor program process is running in the CPU is stopped if that process
has no backup. If the job has the attribute RESTART ON, it is restarted when the CPU
becomes available. If the stopped job is a recurrent job (a recurrent job is one that has
the CALENDAR or EVERY attribute), it is rescheduled as usual. If the executor
program process has a backup, the backup takes over and the job continues to run
without interruption.
State
The State field shows the processing state of the executor named in the Executor
Name field. (For a list and descriptions of processing states, see Table 6-3 on
page 6-83.) You cannot enter information in the State field.
Jobno
If an executor named in the Executor Name field is running a job, the Jobno field
shows the job number. You cannot enter information in the Jobno field.
Classes
Use the fields in the Classes column to assign up to eight classes to the executor
named in the Executor Name field. These classes form the CLASS executor attribute.
The attribute links the classes (and therefore the jobs belonging to them) to the CPU
associated with the executor.
Caution. If a TACL process is the executor program and has a backup process, it initializes
itself when the CPU fails and reprocesses the job input file from the beginning of the file. To
avoid possibly damaging your scheduler database in these circumstances, do not specify a
backup process for a TACL process that is an executor program. This does not apply if your
input file includes the logic to ensure execution restarts in the correct place.