NetBatch Manual

Commands
NetBatch Manual—522460-004
6-187
SUBMIT JOB Command
Considerations
•
The SUBMIT JOB command is available to all users.
•
When the scheduler accepts a submitted job, BATCHCOM displays a message
that includes the scheduler-generated job number. For example:
Job ZBAT-0088 Jobnumber 88 submitted
You can use the job’s number instead of its name in commands that require you to
specify a job. For example, to list the attributes of the job identified in the preceding
message, enter INFO JOB ZBAT-0088 or INFO JOB 88.
•
The scheduler assigns job numbers consecutively in the range 1 through 32767 for
systems running G-series RVUs, and 1 through 9999 for systems running H-series
RVUs. But it skips the numbers already assigned. These job numbering
considerations also apply:
°
Numbering continues from where it left off when you warm start a stopped
scheduler. For example, if the last number assigned before scheduler
shutdown was 361, the first number assigned after warm start would be 362.
°
Numbering starts at 1 when you cold start a scheduler, regardless of whether
the scheduler has run in the past.
°
Numbering is cyclic, beginning again at 1 after reaching the maximum job
number (32767 for system running G-series RVUs, and 9999 for systems
running H-series RVUs). The maximum number of job records the scheduler
can store in its database is 32767 for systems running G-series RVUs and
9999 for systems running H-series RVUs.
•
A job is eligible for execution on acceptance by the scheduler unless delayed by
time, HOLD, TAPEDRIVES, or WAITON attributes. (Time attributes are AFTER, AT,
CALENDAR, EVERY, and WAIT.) The scheduler executes the job on satisfaction of
all attribute conditions and if these conditions exist:
°
The job’s class and the scheduler have the attribute INITIATION ON.
°
An available, started executor is associated with the job’s class. If the job’s
attributes include AT or the job was operated on by the RUNNOW JOB
command, the scheduler creates a temporary executor that it deletes when the
job finishes. For more information about temporary executors, see RUNNOW
JOB Command on page 6-128 and AT Job Attribute on page 7-15.
•
The scheduler assigns job ownership to the user logged on at job submission time.
To display the ID of this user, execute a SHOW JOB command.
•
This consideration discusses how daylight-saving time (DST) transitions affect
jobs. It applies only to nodes loaded with DST transition tables. It does not apply
where system times change by means of the TACL SETTIME command. To avoid
unexpected results, do not submit a job to run in the period lost at the start or
gained at the end of DST. If you must submit jobs to run in these periods: