QSTAT(1)                   Grid Engine User Commands                  QSTAT(1)



[1mNAME[0m
       qstat - show the status of Grid Engine jobs and queues

[1mSYNTAX[0m
       [1mqstat  [22m[  [1m-ext [22m] [ [1m-f [22m] [ [1m-F [22m[[1mresource_name,...[22m]  ] [ [1m-g {c|d|t}[+] [22m] [
       [1m-help [22m] [ [1m-j [job_list] [22m] [ [1m-l  resource=val,...   [22m]  [  [1m-ne  [22m]  [  [1m-pe[0m
       [1mpe_name,...     [22m]   [   [1m-pri   [22m]   [   [1m-q   wc_queue_list   [22m]   [   [1m-qs[0m
       [1m{a|c|d|o|s|u|A|C|D|E|S} [22m] [ [1m-r [22m] [ [1m-s {r|p|s|z|hu|ho|hs|hj|ha|h|a}[+] [22m]
       [ [1m-t [22m] [ [1m-U user,...  [22m] [ [1m-u user,...  [22m] [ [1m-urg [22m] [ [1m-xml [22m]

[1mDESCRIPTION[0m
       [4mqstat[24m  shows the current status of the available Grid Engine queues and
       the jobs associated with the queues. Selection options allow you to get
       information  about  specific jobs, queues or users.  Without any option
       [4mqstat[24m will display only a list of jobs with no  queue  status  informa-
       tion.

       The  administrator  and  the  user may define files (see [4msge_qstat[24m(5)),
       which can contain any of the options described  below.  A  cluster-wide
       sge_qstat   file   may   be    placed   under  $SGE_ROOT/$SGE_CELL/com-
       mon/sge_qstat The user  private   file  is  searched  at  the  location
       $HOME/.sge_qstat.   The  home  directory  request  file has the highest
       precedence over the cluster global file.  Command line can be  used  to
       override the flags contained in the files.

[1mOPTIONS[0m
       [1m-explain a|A|c|E[0m
              'c'  displays the reason for the c(onfiguration ambiguous) state
              of a queue instance. 'a' shows the reason for the  alarm  state.
              Suspend  alarm  state reasons will be displayed by 'A'. 'E' dis-
              plays the reason for a queue instance error state.

              The output format for the alarm reasons is one line  per  reason
              containing  the  resource value and threshold. For details about
              the resource value please refer to the description of  the  [1mFull[0m
              [1mFormat [22min section [1mOUTPUT FORMATS [22mbelow.

       [1m-ext   [22mDisplays  additional information for each job related to the job
              ticket policy scheme (see OUTPUT FORMATS below).

       [1m-f     [22mSpecifies a "full" format display of information.  The [1m-f [22moption
              causes  summary  information on all queues to be displayed along
              with the queued job list.

       [1m-F [22m[ [1mresource_name,... [22m]
              Like in the case of [1m-f [22minformation is displayed on all  jobs  as
              well as queues. In addition, [4mqstat[24m will present a detailed list-
              ing of the current resource availability per queue with  respect
              to  all  resources  (if  the option argument is omitted) or with
              respect to those resources contained in the resource_name  list.
              Please  refer  to  the description of the [1mFull Format [22min section
              [1mOUTPUT FORMATS [22mbelow for further detail.

       [1m-g {c|d|t}[+][0m
              The [1m-g [22moption  allows  for  controlling  grouping  of  displayed
              objects.

              With  [1m-g  c  [22ma  cluster  queue  summary is displayed. Find  more
              information in the section [1mOUTPUT FORMATS[22m.

              With [1m-g d [22marray jobs are displayed verbosely in a one  line  per
              job  task  fashion.  By  default, array jobs are grouped and all
              tasks with the same status (for pending  tasks  only)  are  dis-
              played  in  a  single line. The array job task id range field in
              the output (see section [1mOUTPUT  FORMATS[22m)  specifies  the  corre-
              sponding set of tasks.

              With  [1m-g  t  [22mparallel jobs are displayed verbosely in a one line
              per parallel job task fashion. By  default, parallel  job  tasks
              are  displayed in a single line. Also with [1m-g t [22moption the func-
              tion of each parallel task is displayed  rather  than  the  jobs
              slot amount (see section [1mOUTPUT FORMATS[22m).


       [1m-help  [22mPrints a listing of all options.

       [1m-j [job_list][0m
              Prints  either  for  all  pending  jobs or the jobs contained in
              job_list various information. The job_list can contain  job_ids,
              job_names, or patterns.

              For  jobs  in  E(rror)  state the error reason is displayed. For
              jobs that could not be dispatched during in the last  scheduling
              interval  the  obstacles  are  shown,  if  'schedd_job_info'  in
              [4msched_conf[24m(5) is configured accordingly.

              For running jobs available information on  resource  utilization
              is  shown  about  consumed  cpu time in seconds, integral memory
              usage in Gbytes seconds, amount of data transferred in io opera-
              tions, current virtual memory utilization in Mbytes, and maximum
              virtual memory utilization in Mbytes. This  information  is  not
              available if resource utilization retrieval is not supported for
              the OS platform where the job is hosted.

       [1m-l resource[22m[[1m=value[22m],...
              Defines the resources required by the jobs  or  granted  by  the
              queues  on which information is requested. Matching is performed
              on queues based on non-mutable resource availability information
              only.  That  means load values are always ignored except the so-
              called static load values (i.e. "arch", "num_proc", "mem_total",
              "swap_total"  and  "virtual_total") ones. Consumable utilization
              is also ignored.  The pending jobs are restricted to  jobs  that
              might  run in one of the above queues. In a similar fashion also
              the queue-job matching bases only on non-mutable resource avail-
              ability information.

       [1m-ne    [22mIn  combination  with  [1m-f  [22mthe  option suppresses the display of
              empty queues. This means all queues where actually no  jobs  are
              running are not displayed.

       [1m-pe pe_name,...[0m
              Displays  status  information  with  respect to queues which are
              attached to at least one of the parallel  environments  enlisted
              in  the  comma separated option argument. Status information for
              jobs is displayed either for those which execute in one  of  the
              selected  queues or which are pending and might get scheduled to
              those queues in principle.


       [1m-pri   [22mDisplays additional information for each job related to the  job
              priorities in general.  (see OUTPUT FORMATS below).

       [1m-q wc_queue_list[0m
              Specifies  a  wildcard queue list to which job information is to
              be  displayed.  Find  the   definition   of   [1mwc_queue_list   [22min
              [4msge_types[24m(1).

       [1m-qs {a|c|d|o|s|u|A|C|D|E|S}[0m
              Similar  to  [1m-f[22m. It generates the same output, but allows allows
              for the filtering of queue instances according to state.

       [1m-r     [22mPrints extended information about the resource  requirements  of
              the  displayed jobs. Please refer to the [1mOUTPUT FORMATS [22msub-sec-
              tion [1mExpanded Format [22mbelow for detailed information.

       [1m-s {p|r|s|z|hu|ho|hs|hj|ha|h|a}[+][0m

              Prints only jobs in the  specified  state,  any  combination  of
              states is possible. [1m-s prs [22mcorresponds to the regular [4mqstat[24m out-
              put without [1m-s [22mat all. To show recently finished jobs, use [1m-s z[22m.
              To  display  jobs  in  user/operator/system  hold,  use  the  [1m-s[0m
              [1mhu/ho/hs [22moption. The [1m-s ha [22moption shows jobs which where submit-
              ted  with  the  [4mqsub[24m  [1m-a [22mcommand.  [4mqstat[24m [1m-s hj [22mdisplays all jobs
              which are not eligible for execution unless the job has  entries
              in  the  job dependency list.  [4mqstat[24m [1m-s h [22mis an abbreviation for
              [4mqstat[24m [1m-s huhohshjha [22mand [4mqstat[24m [1m-s a [22mis an abbreviation for  [4mqstat[0m
              [1m-s psr [22m(see [1m-a [22mand [1m-hold_jid [22moption to [4mqsub[24m(1)).

       [1m-t     [22mPrints  extended  information  about the controlled sub-tasks of
              the displayed parallel jobs. Please refer to the [1mOUTPUT  FORMATS[0m
              sub-section  [1mReduced Format [22mbelow for detailed information. Sub-
              tasks of parallel jobs should not be  confused  with  array  job
              tasks (see [1m-g [22moption above and [1m-t [22moption to [4mqsub[24m(1)).

       [1m-U user,...[0m
              Displays  status information with respect to queues to which the
              specified users have access. Status information for jobs is dis-
              played  either  for  those  which execute in one of the selected
              queues or which are pending and might  get  scheduled  to  those
              queues in principle.

       [1m-u user,...[0m
              Display  information only on those jobs and queues being associ-
              ated with the users from the  given  user  list.   Queue  status
              information  is  displayed if the [1m-f [22mor [1m-F [22moptions are specified
              additionally and if the user runs jobs in those queues.

              The string  [1m$user [22mis a placeholder for the current username.  An
              asterisk  "*"  can  be  used as username wildcard to request any
              user's jobs be displayed.


       [1m-urg   [22mDisplays additional information for each job related to the  job
              urgency policy scheme (see OUTPUT FORMATS below).

       [1m-xml   [22mThis  option  can be used with all other options and changes the
              output to XML. The used schemas are referenced in the  XML  out-
              put. The output is printed to stdout.

[1mOUTPUT FORMATS[0m
       Depending  on  the  presence or absence of the [1m-explain[22m, [1m-f[22m, [1m-F[22m, or [1m-qs[0m
       and [1m-r [22mand [1m-t [22moption three output formats need to be differentiated.

       The [1m-ext [22mand [1m-urg [22moptions may be used to display additional information
       for each job.

   [1mCluster Queue Format (with -g c)[0m
       Following the header line a section for each cluster queue is provided.
       When queue instances selection are applied (-l -pe, -q, -U) the cluster
       format   contains  only  cluster  queues  of  the  corresponding  queue
       instances.

       +o  the cluster queue name.

       +o  an average of the normalized load average of  all  queue  hosts.  In
          order  to  reflect  each  hosts different significance the number of
          configured slots is used as  a  weighting  factor  when  determining
          cluster   queue   load.    Please   note  that  only  hosts  with  a
          np_load_value are considered for this value. When queue selection is
          applied  only  data about selected queues is considered in this for-
          mula. If the load value is not available at any of the hosts  '-NA-'
          is  printed  instead of the value from the complex attribute defini-
          tion.

       +o  the number of currently used slots.

       +o  the number of currently available slots.

       +o  the total number of slots.

       +o  the number of slots which is in  at  least  in  one  of  the  states
          'aoACDS' and in none of the states 'cdsuE'

       +o  the number of slots which are in one of these states or in any  com-
          bination of them: 'cdsuE'

       +o  the [1m-g c [22moption can be used in combination with [1m-ext[22m. In this  case,
          additional columns are added to the output. Each column contains the
          slot count for one of the available queue states.

   [1mReduced Format (without -f, -F, and -qs)[0m
       Following the header line a line is printed for each job consisting of

       +o  the job ID.

       +o  the priority of the job determining its position in the pending jobs
          list.   The priority value is determined dynamically based on ticket
          and urgency policy set-up (see also [4msge_priority[24m(5) ).

       +o  the name of the job.

       +o  the user name of the job owner.

       +o  the status  of  the  job  -  one  of  d(eletion),  E(rror),  h(old),
          r(unning),  R(estarted),  s(uspended),  S(uspended),  t(ransfering),
          T(hreshold) or w(aiting).

          The state d(eletion) indicates that a [4mqdel[24m(1) has been used to  ini-
          tiate job deletion.  The states t(ransfering) and r(unning) indicate
          that a job is about to be executed or is already executing,  whereas
          the  states  s(uspended),  S(uspended)  and T(hreshold) show that an
          already running jobs has been suspended. The  s(uspended)  state  is
          caused   by   suspending  the  job  via  the  [4mqmod[24m(1)  command,  the
          S(uspended) state indicates that the queue  containing  the  job  is
          suspended  and  therefore the job is also suspended and the T(hresh-
          old) state shows that at least one suspend threshold of  the  corre-
          sponding queue was exceeded (see [4mqueue_conf[24m(5)) and that the job has
          been suspended as a consequence.  The  state  R(estarted)  indicates
          that the job was restarted. This can be caused by a job migration or
          because of one of the reasons described in the  -r  section  of  the
          [4mqsub[24m(1) command.

          The  states  w(aiting)  and h(old) only appear for pending jobs. The
          h(old) state indicates that a job currently is not eligible for exe-
          cution due to a hold state assigned to it via [4mqhold[24m(1), [4mqalter[24m(1) or
          the [4mqsub[24m(1) [1m-h [22moption or that the job is waiting for  completion  of
          the jobs to which job dependencies have been assigned to the job via
          the [1m-hold_jid [22moption of [4mqsub[24m(1) or [4mqalter[24m(1).

          The state E(rror) appears for pending jobs that couldn't be  started
          due  to job properties. The reason for the job error is shown by the
          [4mqstat[24m(1) [1m-j job_list [22moption.

       +o  the submission or start time and date of the job.

       +o  the queue the job is assigned to  (for  running  or  suspended  jobs
          only).

       +o  the  number of job slots or the function of parallel job tasks if [1m-g[0m
          [1mt [22mis specified.

          Without [1m-g t  [22moption  the  total  number  of  slots  occupied  resp.
          requested  by the job is displayed. For pending parallel jobs with a
          PE slot range request, the assumed future slot  allocation  is  dis-
          played.   With  [1m-g t [22moption the function of the running jobs (MASTER
          or SLAVE - the latter for parallel jobs only) is displayed.

       +o  the array job task id. Will be empty for non-array jobs. See the  [1m-t[0m
          option to [4mqsub[24m(1) and the [1m-g [22mabove for additional information.

       If the [1m-t [22moption is supplied, each status line always contains parallel
       job task information as if [1m-g t [22mwere specified and each  line  contains
       the following parallel job subtask information:

       +o  the  parallel  task ID (do not confuse parallel tasks with array job
          tasks),

       +o  the status of the parallel task -  one  of  r(unning),  R(estarted),
          s(uspended),   S(uspended),   T(hreshold),   w(aiting),  h(old),  or
          x(exited).

       +o  the cpu, memory, and I/O usage,

       +o  the exit status of the parallel task,

       +o  and the failure code and message for the parallel task.

   [1mFull Format (with -f and -F)[0m
       Following the header line a section for each queue separated by a hori-
       zontal  line  is  provided. For each queue the information printed con-
       sists of

       +o  the queue name,

       +o  the queue type - one  of  B(atch),  I(nteractive),  C(heckpointing),
          P(arallel), T(ransfer) or combinations thereof or N(one),

       +o  the number of used and available job slots,

       +o  the load average of the queue host,

       +o  the architecture of the queue host and

       +o  the  state  of  the  queue  -  one of u(nknown) if the corresponding
          [4msge_execd[24m(8) cannot be contacted, a(larm), A(larm),  C(alendar  sus-
          pended), s(uspended), S(ubordinate), d(isabled), D(isabled), E(rror)
          or combinations thereof.

       If the state is a(larm) at least on of the load thresholds  defined  in
       the [4mload_thresholds[24m list of the queue configuration (see [4mqueue_conf[24m(5))
       is currently exceeded, which prevents from scheduling further  jobs  to
       that queue.

       As  opposed  to  this, the state A(larm) indicates that at least one of
       the suspend thresholds of the queue (see  [4mqueue_conf[24m(5))  is  currently
       exceeded.  This will result in jobs running in that queue being succes-
       sively suspended until no threshold is violated.

       The states s(uspended) and d(isabled) can be  assigned  to  queues  and
       released  via  the  [4mqmod[24m(1)  command. Suspending a queue will cause all
       jobs executing in that queue to be suspended.

       The states D(isabled) and C(alendar suspended) indicate that the  queue
       has  been disabled or suspended automatically via the calendar facility
       of Grid Engine (see [4mcalendar_conf[24m(5)), while  the  S(ubordinate)  state
       indicates, that the queue has been suspend via subordination to another
       queue (see [4mqueue_conf[24m(5) for details). When suspending a queue (regard-
       less  of the cause) all jobs executing in that queue are suspended too.

       If an E(rror) state is displayed for a queue, [4msge_execd[24m(8) on that host
       was  unable  to  locate  the [4msge_shepherd[24m(8) executable on that host in
       order  to  start  a  job.  Please  check  the  error  logfile  of  that
       [4msge_execd[24m(8) for leads on how to resolve the problem. Please enable the
       queue afterwards via the [1m-c [22moption of the [4mqmod[24m(1) command manually.

       If the  c(onfiguration  ambiguous)  state  is  displayed  for  a  queue
       instance this indicates that the configuration specified for this queue
       instance in [4msge_conf[24m(5) is ambiguous. This state is  cleared  when  the
       configuration  becomes  unambiguous  again. This state prevents further
       jobs from being scheduled to that queue instance. Detailed reasons  why
       a  queue  instance  entered  the c(onfiguration ambiguous) state can be
       found in the [4msge_qmaster[24m(8) messages file and are shown  by  the  qstat
       -explain  switch. For queue instances in this state the cluster queue's
       default settings are used for the ambiguous attribute.

       If an o(rphaned) state is displayed for a queue instance, it  indicates
       that  the  queue  instance is no longer demanded by the current cluster
       queue's configuration or  the  host  group  configuration.   The  queue
       instance  is  kept  because  jobs which have not yet finished are still
       associated with it, and it will vanish from the qstat output when these
       jobs  have finished. To quicken vanishing of an orphaned queue instance
       associated job(s) can be deleted using [4mqdel[24m(1).  A  queue  instance  in
       (o)rphaned  state can be revived by changing the cluster queue configu-
       ration accordingly to cover that queue instance.  This  state  prevents
       from scheduling further jobs to that queue instance.

       If the [1m-F [22moption was used, resource availability information is printed
       following the queue status line. For each resource (as selected  in  an
       option  argument  to [1m-F [22mor for all resources if the option argument was
       omitted) a single line is displayed with the following format:

       +o  a one letter  specifier  indicating  whether  the  current  resource
          availability value was dominated by either
          `[1mg[22m' - a cluster global,
          `[1mh[22m' - a host total or
          `[1mq[22m' - a queue related resource consumption.

       +o  a  second one letter specifier indicating the source for the current
          resource availability value, being one of
          `[1ml[22m' - a load value reported for the resource,
          `[1mL[22m' - a load value for the resource after administrator defined load
          scaling has been applied,
          `[1mc[22m'  -  availability  derived from the consumable resources facility
          (see [4mcomplexes[24m(5)),
          `[1mf[22m' - a fixed availability definition derived from a  non-consumable
          complex attribute or a fixed resource limit.

       +o  after  a colon the name of the resource on which information is dis-
          played.

       +o  after an equal sign the current resource availability value.

       The displayed availability values  and  the  sources  from  which  they
       derive  are  always  the  minimum  values of all possible combinations.
       Hence, for example, a line of the form "qf:h_vmem=4G" indicates that  a
       queue currently has a maximum availability in virtual memory of 4 Giga-
       byte, where this value is a fixed value (e.g. a resource limit  in  the
       queue  configuration) and it is queue dominated, i.e. the host in total
       may have more virtual memory available than this, but the queue doesn't
       allow for more. Contrarily a line "hl:h_vmem=4G" would also indicate an
       upper bound of 4 Gigabyte virtual memory availability,  but  the  limit
       would  be derived from a load value currently reported for the host. So
       while the queue  might  allow  for  jobs  with  higher  virtual  memory
       requirements, the host on which this particular queue resides currently
       only has 4 Gigabyte available.

       If the [1m-explain [22moption was used with the character 'a' or 'A', informa-
       tion about resources is displayed, that violate load or suspend thresh-
       olds.
       The same format as with the [1m-F [22moption is  used  with  following  exten-
       sions:

       +o  the line starts with the keyword `alarm'

       +o  appended  to  the resource value is the type and value of the appro-
          priate threshold

       After the queue status line (in case of [1m-f[22m) or the resource  availabil-
       ity  information  (in case of [1m-F[22m) a single line is printed for each job
       running currently in this queue. Each job status line contains

       +o  the job ID,

       +o  the priority of the job determining its position in the pending jobs
          list.   The priority value is determined dynamically based on ticket
          and urgency policy set-up (see also [4msge_priority[24m(5) ).

       +o  the job name,

       +o  the job owner name,

       +o  the  status  of  the  job  -  one   of   t(ransfering),   r(unning),
          R(estarted),   s(uspended),  S(uspended)  or  T(hreshold)  (see  the
          [1mReduced Format [22msection for detailed information),

       +o  the submission or start time and date of the job.

       +o  the number of job slots or the function of parallel job tasks if  [1m-g[0m
          [1mt [22mis specified.

          Without  [1m-g  t  [22moption  the number of slots occupied per queue resp.
          requested by the job is displayed. For pending parallel jobs with  a
          PE  slot  range  request, the assumed future slot allocation is dis-
          played.  With [1m-g t [22moption the function of the running  jobs  (MASTER
          or SLAVE - the latter for parallel jobs only) is displayed.

       If the [1m-t [22moption is supplied, each job status line also contains

       +o  the task ID,

       +o  the status of the task - one of r(unning), R(estarted), s(uspended),
          S(uspended), T(hreshold), w(aiting), h(old), or x(exited)  (see  the
          [1mReduced Format [22msection for detailed information),

       +o  the cpu, memory, and I/O usage,

       +o  the exit status of the task,

       +o  and the failure code and message for the task.

       Following the list of queue sections a [4mPENDING[24m [4mJOBS[24m list may be printed
       in case jobs are waiting for being assigned to a queue.  A status  line
       for each waiting job is displayed being similar to the one for the run-
       ning jobs. The differences are that the status for the jobs  is  w(ait-
       ing)  or  h(old), that the submit time and date is shown instead of the
       start time and that no function is displayed for the jobs.

       In very rare cases, e.g. if [4msge_qmaster[24m(8) starts up from an  inconsis-
       tent  state in the job or queue spool files or if the [1mclean queue [22m([1m-cq[22m)
       option of [4mqconf[24m(1) is used, [4mqstat[24m cannot assign jobs to either the run-
       ning  or pending jobs section of the output. In this case as job status
       inconsistency (e.g. a job has a running status but is not assigned to a
       queue)  has  been detected. Such jobs are printed in an [4mERROR[24m [4mJOBS[24m sec-
       tion at the very end of the output. The ERROR JOBS section should  dis-
       appear upon restart of [4msge_qmaster[24m(8).  Please contact your Grid Engine
       support representative if you feel uncertain about the cause or effects
       of such jobs.

   [1mExpanded Format (with -r)[0m
       If  the  [1m-r  [22moption  was  specified  together with [4mqstat[24m, the following
       information for each displayed job is printed (a single line  for  each
       of the following job characteristics):

       +o  The job and master queue name.

       +o  The hard and soft resource requirements of the job as specified with
          the [4mqsub[24m(1) [1m-l [22moption. The per resource addend when determining  the
          jobs  urgency  contribution  value  is  printed (see also [4msge_prior-[0m
          [4mity[24m(5)).

       +o  The requested parallel environment including the desired queue  slot
          range (see [1m-pe [22moption of [4mqsub[24m(1)).

       +o  The  requested checkpointing environment of the job (see the [4mqsub[24m(1)
          [1m-ckpt [22moption).

       +o  In case of running jobs, the granted parallel environment  with  the
          granted number of queue slots.

   [1mEnhanced Output (with -ext)[0m
       For each job the following additional items are displayed:

       [1mntckts [22mThe total number of tickets in normalized fashion.

       [1mproject[0m
              The  project  to  which  the job is assigned as specified in the
              [4mqsub[24m(1) [1m-P [22moption.

       [1mdepartment[0m
              The department, to which the user belongs (use the [1m-sul [22mand  [1m-su[0m
              options  of  [4mqconf[24m(1)  to display the current department defini-
              tions).

       [1mcpu    [22mThe current accumulated CPU usage of the job in seconds.

       [1mmem    [22mThe current accumulated memory usage of the job in  Gbytes  sec-
              onds.

       [1mio     [22mThe current accumulated IO usage of the job.

       [1mtckts  [22mThe total number of tickets assigned to the job currently

       [1movrts  [22mThe override tickets as assigned by the [1m-ot [22moption of [4mqalter[24m(1).

       [1motckt  [22mThe override portion of the total number of tickets assigned  to
              the job currently

       [1mftckt  [22mThe  functional  portion of the total number of tickets assigned
              to the job currently

       [1mstckt  [22mThe share portion of the total number of tickets assigned to the
              job currently

       [1mshare  [22mThe  share of the total system to which the job is entitled cur-
              rently.

   [1mEnhanced Output (with -urg)[0m
       For each job the following additional urgency policy related items  are
       displayed (see also [4msge_priority[24m(5)):

       [1mnurg   [22mThe jobs total urgency value in normalized fashion.

       [1murg    [22mThe jobs total urgency value.

       [1mrrcontr[0m
              The urgency value contribution that reflects the urgency that is
              related to the jobs overall resource requirement.

       [1mwtcontr[0m
              The urgency value contribution that reflects the urgency related
              to the jobs waiting time.

       [1mdlcontr[0m
              The urgency value contribution that reflects the urgency related
              to the jobs deadline initiation time.

       [1mdeadline[0m
              The deadline initiation time of the job as  specified  with  the
              [4mqsub[24m(1) [1m-dl [22moption.

   [1mEnhanced Output (with -pri)[0m
       For  each  job, the following additional job priority related items are
       displayed (see also [4msge_priority[24m(5)):

       [1mnurg   [22mThe job's total urgency value in normalized fashion.

       [1mnpprior[0m
              The job's [1m-p [22mpriority in normalized fashion.

       [1mntckts [22mThe job's ticket amount in normalized fashion.

       [1mppri   [22mThe job's [1m-p [22mpriority as specified by the user.

[1mENVIRONMENTAL VARIABLES[0m
       [1mSGE_ROOT       [22mSpecifies the location of the Grid Engine standard  con-
                      figuration files.

       [1mSGE_CELL       [22mIf  set,  specifies  the  default  Grid  Engine cell. To
                      address a Grid Engine cell [4mqstat[24m uses (in the  order  of
                      precedence):

                             The name of the cell specified in the environment
                             variable SGE_CELL, if it is set.

                             The name of the default cell, i.e. [1mdefault[22m.


       [1mSGE_DEBUG_LEVEL[0m
                      If set, specifies that debug information should be writ-
                      ten  to stderr. In addition the level of detail in which
                      debug information is generated is defined.

       [1mSGE_QMASTER_PORT[0m
                      If set, specifies the tcp port on  which  [4msge_qmaster[24m(8)
                      is  expected to listen for communication requests.  Most
                      installations will use a services map entry for the ser-
                      vice "sge_qmaster" instead to define that port.

       [1mSGE_LONG_QNAMES[0m
                      Qstat  does  display queue names up to 30 characters. If
                      that is to much or not enough,  one  can  set  a  custom
                      length with this variable. The minimum display length is
                      10 characters. If one does not  know  the  best  display
                      length, one can set SGE_LONG_QNAMES to -1 and qstat will
                      figure out the best length.

[1mFILES[0m
       [4m<sge_root>/<cell>/common/act_qmaster[0m
                       Grid Engine master host file
       [4m<sge_root>/<cell>/common/sge_qstat[0m
                       cluster qstat default options
       [4m$HOME/.sge_qstat[0m
          user qstat default options

[1mSEE ALSO[0m
       [4msge_intro[24m(1),  [4mqalter[24m(1),  [4mqconf[24m(1),   [4mqhold[24m(1),   [4mqhost[24m(1),   [4mqmod[24m(1),
       [4mqsub[24m(1),  [4mqueue_conf[24m(5), [4msge_execd[24m(8), [4msge_qmaster[24m(8), [4msge_shepherd[24m(8).

[1mCOPYRIGHT[0m
       See [4msge_intro[24m(1) for a full statement of rights and permissions.



GE 6.0                   $Date: 2007/01/05 20:35:38 $                 QSTAT(1)
