NetBatch-Plus Reference Manual

NetBatch-Plus Screens
NetBatch-Plus Reference Manual—522461-002
6-167
Functions
F8–Delete Deletes the selected job if it is not executing or suspended.
You can delete jobs with a state of EVENT, READY, RUNNEXT,
RUNNOW, SPECIAL-n, TAPE, or TIME. To delete jobs with a state of
EXECUTING or SUSPENDED, you must use F12–Stop instead.
F8–Delete cancels a recurrent job (a recurrent job has the CALENDAR or
EVERY attribute). Canceled recurrent jobs are not rescheduled for
execution.
You can delete a job on this screen only if you previously validated one of
these Guardian user IDs:
•
The ID of a super-group user (255, n). Super-group users can delete
any job.
•
The ID of the job owner.
•
The ID of a user who has write access to the job input file. If the input
file does not exist or if the file is a device or process, only the owner
or a super-group user can delete the job.
F10–Activate Resumes execution of a suspended job. (F10 is the same as the
BATCHCOM command ACTIVATE JOB.)
A job with the EVERY attribute might accumulate a job backlog while it is
suspended. When you activate the job, it runs repeatedly until the
backlog is cleared. To prevent the backlog from running, before you press
F10:
1. Use the Class Details screen to set the INITIATION attribute of the
job’s class to OFF.
2. Use the F12–Stop function on the Job Status screen to stop the
suspended job and all its processes.
3. Use the F6–Alter function on the Job Info screen to alter the
scheduling attributes of the job. Also consider deleting the job using
the F8–Delete function on the Job Info or Job Status screens.
4. Use the Class Details screen to reset the INITIATION attribute of the
class to ON.
A job with the CALENDAR attribute does not accumulate a job backlog
while it is suspended. When you activate the job, it runs only when the
attribute condition is next satisfied.
You can activate a job only if you previously validated one of these
Guardian user IDs:
•
The ID of a super-group user (255, n). Super-group users can
activate any job.
•
The ID of the job owner.
•
The ID of a user who has write access to the job input file. If the input
file does not exist or if the file is a device or process, only the owner
or a super-group user can activate the job.
Function Description
* Function is available on screen, but not displayed,