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

NAME

6       qrls - release Grid Engine jobs from previous hold states
7

SYNTAX

9       qrls [ -h {u|o|s},...  ] [ -help ] [ job/task_id_list ]
10
11       qrls [ -h {u|o|s},...  ] [ -help ] -u user_list
12

DESCRIPTION

14       Qrls  provides a means for a user/operator/manager to release so called
15       holds from one or more jobs pending to be scheduled for execution.   As
16       long  as any type of hold is assigned to a job, the job is not eligible
17       for scheduling.
18
19       Holds can be assigned to jobs with the qhold(1), qsub(1)  or  the  qal‐
20       ter(1) command.
21
22       There are three different types of holds:
23
24       user   User  holds  can  be assigned and removed by managers, operators
25              and the owner of the jobs.
26
27       operator
28              Operator holds can be assigned and removed by managers and oper‐
29              ators.
30
31       system System holds can be assigned and removed by managers only.
32
33       If  no  hold  type is specified with the -h option (see below) the user
34       hold is assumed by default.
35
36       An alternate way to release holds is the qalter(1) command (see the  -h
37       option).
38

OPTIONS

40       -h {u|o|s},...
41              Releases a u(ser), o(perator) or s(system) hold or a combination
42              thereof from one or more jobs.
43
44       -help  Prints a listing of all options.
45
46       -u username,...
47              Modifies the hold state of those jobs which  were  submitted  by
48              users  specified in the list of usernames.  Managers are allowed
49              to use the qrls -u "*" command to modify the hold state for jobs
50              of all users.
51
52              If a user uses the -u switch, the user may specify an additional
53              job/task_id_list.
54
55       job/task_id_list
56              Specified by the following form:
57
58                  job_id[.task_range][,job_id[.task_range],...]
59
60              If present, the task_range restricts the effect of the operation
61              to  the  array  job task range specified as suffix to the job id
62              (see the -t option to  qsub(1)  for  further  details  on  array
63              jobs).
64
65              The  task  range specifier has the form n[-m[:s]]. The range may
66              be a single number, a  simple range  of the form n-m or a  range
67              with a step size.
68
69              Instead  of  job/task_id_list  it is possible to use the keyword
70              'all' to modify all jobs of the current user.
71

ENVIRONMENTAL VARIABLES

73       GE_ROOT        Specifies the location of the Grid Engine standard  con‐
74                      figuration files.
75
76       GE_CELL        If  set,  specifies  the  default  Grid  Engine cell. To
77                      address a Grid Engine cell qrls uses (in  the  order  of
78                      precedence):
79
80                             The name of the cell specified in the environment
81                             variable GE_CELL, if it is set.
82
83                             The name of the default cell, i.e. default.
84
85
86       GE_DEBUG_LEVEL If set, specifies that debug information should be writ‐
87                      ten  to stderr. In addition the level of detail in which
88                      debug information is generated is defined.
89
90       GE_QMASTER_PORT
91                      If set, specifies the tcp port on which ge_qmaster(8) is
92                      expected  to  listen  for  communication requests.  Most
93                      installations will use a services map entry for the ser‐
94                      vice "sge_qmaster" instead to define that port.
95

SEE ALSO

97       ge_intro(1), qalter(1), qhold(1), qsub(1).
98

100       See ge_intro(1) for a full statement of rights and permissions.
101
102
103
104GE 6.2u5                 $Date: 2007/01/05 19:56:11 $                  QRLS(1)
Impressum