Platform LSF Administration Guide Version 6.2

Using Job Groups
Administering Platform LSF
154
% bjobs -l -g /risk_group
Job <101>, User <user1>, Project <default>, Job Group
</risk_group>, Status <RUN>, Queue <normal>, Command <myjob>
Tue Jun 17 16:21:49: Submitted from host <hostA>, CWD
</home/user1;
Tue Jun 17 16:22:01: Started on <hostA>;
...
Controlling jobs in job groups
Stopping (bstop)
Use the -g option of bstop and specify a job group path to suspend jobs in a job group
% bstop -g /risk_group 106
Job <106> is being stopped
Use job ID 0 (zero) to suspend all jobs in a job group:
% bstop -g /risk_group/consolidate 0
Job <107> is being stopped
Job <108> is being stopped
Job <109> is being stopped
Resuming
(bresume)
Use the -g option of bresume and specify a job group path to resume suspended jobs
in a job group:
% bresume -g /risk_group 106
Job <106> is being resumed
Use job ID 0 (zero) to resume all jobs in a job group:
% bresume -g /risk_group 0
Job <109> is being resumed
Job <110> is being resumed
Job <112> is being resumed
Modifying (bmod)
Use the -g option of bmod and specify a job group path to move a job or a job array
from one job group to another. For example:
% bmod -g /risk_group/portfolio2/monthly 105
moves job 105 to job group /risk_group/portfolio2/monthly.
Like
bsub -g, if the job group does not exist, LSF creates it.
bmod -g cannot be combined with other bmod options. It can operate on finished,
running, and pending jobs.
You can modify your own job groups and job groups that other users create under your
job groups. The LSF administrator can modify job groups of all users.
You cannot move job array elements from one job group to another, only entire job
arrays. A job array can only belong to one job group at a time. You cannot modify the
job group of a job attached to a service class.
bhist -l shows job group modification information: