Administering Platform LSF - SAS

Submitting and Controlling Chunk Jobs
Controlling chunk jobs
Job controls affect the state of the members of a chunk job. You can perform
the following actions on jobs in a chunk job:
Rerunnable chunk jobs
Checkpointing chunk jobs
Action (Command) Job Effect on Job (State)
State
Suspend (bstop) PEND Removed from chunk (PSUSP)
RUN All jobs in the chunk are suspended
(NRUN -1, NSUSP +1)
USUSP No change
WAIT Removed from chunk (PSUSP)
Kill (bkill) PEND Removed from chunk (NJOBS -1, PEND -1)
RUN Job finishes, next job in the chunk starts if one exists
(NJOBS -1, PEND -1)
USUSP Job finishes, next job in the chunk starts if one exists
(NJOBS -1, PEND -1, SUSP -1, RUN +1)
WAIT Job finishes (NJOBS-1, PEND -1)
Resume
USUSP Entire chunk is resumed (RUN +1, USUSP -1)
(bresume)
Migrate (bmig) WAIT Removed from chunk
Switch queue
(bswitch)
Checkpoint
(bchkpnt)
RUN
WAIT
RUN
Job is removed from the chunk and switched; all
other WAIT jobs are requeued to PEND
Only the WAIT job is removed from the chunk and
switched, and requeued to PEND
Job is checkpointed normally
Modify (bmod) PEND Removed from the chunk to be scheduled later
Migrating jobs with bmig will change the dispatch sequence of the chunk job
members. They will not be redispatched in the order they were originally
submitted.
If the execution host becomes unavailable, rerunnable chunk job members are
removed from the queue and dispatched to a different execution host.
See Chapter 22, “Job Requeue and Job Rerun” for more information about
rerunnable jobs.
Only running chunk jobs can be checkpointed. If bchkpnt -k is used, the job
is also killed after the checkpoint file has been created. If chunk job in WAIT
state is checkpointed, mbatchd rejects the checkpoint request.
See Chapter 23, “Job Checkpoint, Restart, and Migration” for more information
about checkpointing jobs.
328
Administering Platform LSF