1QMOD(1)                    Grid Engine User Commands                   QMOD(1)
2
3
4

NAME

6       qmod - modify a Grid Engine queue
7

SYNTAX

9       qmod [ options ] [ wc_job_range_list | wc_queue_list ]
10

DESCRIPTION

12       qmod enables users classified as owners (see queue_conf(5) for details)
13       of a machine to modify the state of  Grid  Engine  queues  for  his/her
14       machine  as  well as the state of his/her own jobs.  A manager/operator
15       or root can execute qmod for any queue and job in a cluster. Find addi‐
16       tional   information   concerning   wc_queue_list  and  wc_job_list  in
17       sge_types(1).
18

OPTIONS

20       -c     Clears the error state of the  specified  jobs(s)/queue(s).   Do
21              not use this switch anymore, use -cj / -cq instead.
22
23       -cj    Clears the error state of the specified jobs(s).
24
25       -cq    Clears the error state of the specified queue(s).
26
27       -d     Disables  the  queue(s),  i.e. no further jobs are dispatched to
28              disabled queues while jobs already executing in these queues are
29              allowed to finish.
30
31       -e     Enables the queue(s).
32
33       -f     Force the modification action for the queue despite the apparent
34              current state of the queue. For example if a queue appears to be
35              suspended  but the job execution seems to be continuing the man‐
36              ager/operator can force a suspend operation which  will  send  a
37              SIGSTOP  to  the jobs. In any case, the queue or job status will
38              be set even if the sge_execd(8) controlling the queues/jobs can‐
39              not be reached. Requires manager/operator privileges.
40
41       -help  Prints a listing of all options.
42
43       -r     If  applied to queues, reschedules all jobs currently running in
44              this queue.  If applied to running jobs, reschedules  the  jobs.
45              Requires root or manager privileges. Do not use this switch any‐
46              more.  Use -rj /-rq instead.  In order for a job to be  resched‐
47              uled,  it  or  the  queue in which it is executing must have the
48              rerun flag activated.  (See -r option in the  qsub(1)  man  page
49              and  the  rerun  option  in  the queue_conf(5) man page for more
50              information.)  Additional restrictions apply  for  parallel  and
51              checkpointing  jobs.  (See the reschedule_unknown description in
52              the sge_conf(5) man page for details).
53
54       -rj    If applied to running jobs, reschedules the jobs. Requires  root
55              or manager privileges.
56
57       -rq    If  applied to queues, reschedules all jobs currently running in
58              this queue.  Requires root or manager privileges.
59
60       -s     If applied to queues, suspends the queues  and  any  jobs  which
61              might  be active. If applied to running jobs, suspends the jobs.
62              Use of this switch is now deprecated. -sj / -sq should  be  used
63              instead.
64
65       -sj    If  applied to running jobs, suspends the jobs. If a job is both
66              suspended explicitly and via suspension of its queue, a  follow‐
67              ing unsuspend of the queue will not release the suspension state
68              on the job.
69
70       -sq    If applied to queues, suspends the queues  and  any  jobs  which
71              might be active.
72
73       -us    If  applied  to queues, unsuspends the queues and any jobs which
74              might be active. If applied to jobs, unsuspends the jobs. Do not
75              use this switch anymore, use -usj / -usq instead.
76
77       -usj   If  applied  to jobs, unsuspends the jobs. If a job is both sus‐
78              pended explicitly and via suspension of its queue,  a  following
79              unsuspend  of the queue will not release the suspension state on
80              the job.
81
82       -usq   If applied to queues, unsuspends the queues and any  jobs  which
83              might be active.
84

ENVIRONMENTAL VARIABLES

86       SGE_ROOT       Specifies  the location of the Grid Engine standard con‐
87                      figuration files.
88
89       SGE_CELL       If set, specifies  the  default  Grid  Engine  cell.  To
90                      address  a  Grid  Engine cell qmod uses (in the order of
91                      precedence):
92
93                             The name of the cell specified in the environment
94                             variable SGE_CELL, if it is set.
95
96                             The name of the default cell, i.e. default.
97
98
99       SGE_DEBUG_LEVEL
100                      If set, specifies that debug information should be writ‐
101                      ten to stderr. In addition the level of detail in  which
102                      debug information is generated is defined.
103
104       SGE_QMASTER_PORT
105                      If  set,  specifies the tcp port on which sge_qmaster(8)
106                      is expected to listen for communication requests.   Most
107                      installations will use a services map entry for the ser‐
108                      vice "sge_qmaster" instead to define that port.
109

FILES

111       $SGE_ROOT/$SGE_CELL/common/act_qmaster
112                      Grid Engine master host file
113

SEE ALSO

115       sge_intro(1),  sge_ckpt(1),  qstat(1),   queue_conf(5),   sge_execd(8),
116       sge_types(1).
117
119       See sge_intro(1) for a full statement of rights and permissions.
120
121
122
123GE 6.1                   $Date: 2007/06/26 22:21:06 $                  QMOD(1)
Impressum