NetBatch Manual

Commands
NetBatch Manual—522460-004
6-33
ACTIVATE JOB Command
filter
specifies one of these job-selection criteria (see STATUS JOB Command on
page 6-165):
A[TTACHMENT]-S[ET]BBC[( AALVS1([ ( user-ID ) ] attachment-
set-
ID,#CURRENT) )
CL[ASS] class-ID
IN file-ID
STATE state
U[SER] user-ID
WAITO[N] master-job
Considerations
•
The ACTIVATE JOB command is available to all users, but:
°
NetBatch supervisors can reactivate jobs belonging to any user.
°
Users who are not NetBatch supervisors can reactivate any job whose input
file is a disk file to which they have write access. If the input file does not exist
or is a device or process, only the owner and NetBatch supervisors can
reactivate the job.
If you are not a NetBatch supervisor, an ACTIVATE JOB command that
specifies job-ID with wild-card characters reactivates only your own jobs. To
reactivate another user’s job if you have write access to its input file, specify
the job’s full name or number in job-ID.
•
A suspended job whose attributes include EVERY accumulates a run backlog if
suspended for longer than the EVERY interval and the scheduler has the attribute
CATCHUP ON. When you reactivate the job, it runs repeatedly until the backlog
clears. For example, an hourly 10-minute job submitted at 0900 should run three
times before 1200 (at 0900, 1000, and 1100). If suspended at 0905, then
reactivated at 1105, the job finishes executing and runs twice more before running
again at 1200.
To stop a suspended job’s processes and to stop its backlog running:
1. Change the suspended job’s HOLDAFTER attribute to HOLDAFTER ON by
using the ALTER JOB command.
2. Stop the suspended job’s processes and delete the job from its scheduler by
using the STOP JOB command.
3. Change the scheduling attributes of the recurring job by using the ALTER JOB
command. (Alternatively, delete the job by using the DELETE JOB command.)
4. Change the recurring job’s HOLD and HOLDAFTER attributes to OFF.
•
A suspended job whose attributes include CALENDAR does not accumulate a run
backlog while suspended. When you reactivate the job, it finishes executing but
does not run again until the next future CALENDAR time.