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



NNAAMMEE
       qstat - show the status of Grid Engine jobs and queues

SSYYNNTTAAXX
       qqssttaatt  [  --eexxtt ] [ --ff ] [ --FF [rreessoouurrccee__nnaammee,,......]  ] [ --gg {{cc||dd||tt}}[[++]] ] [
       --hheellpp ] [ --jj [[jjoobb__lliisstt]] ] [ --ll  rreessoouurrccee==vvaall,,......   ]  [  --nnee  ]  [  --ppee
       ppee__nnaammee,,......     ]   [   --pprrii   ]   [   --qq   wwcc__qquueeuuee__lliisstt   ]   [   --qqss
       {{aa||cc||dd||oo||ss||uu||AA||CC||DD||EE||SS}} ] [ --rr ] [ --ss {{rr||pp||ss||zz||hhuu||hhoo||hhss||hhjj||hhaa||hh||aa}}[[++]] ]
       [ --tt ] [ --UU uusseerr,,......  ] [ --uu uusseerr,,......  ] [ --uurrgg ] [ --xxmmll ]

DDEESSCCRRIIPPTTIIOONN
       _q_s_t_a_t  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
       _q_s_t_a_t will display only a list of jobs with no  queue  status  informa-
       tion.

       The  administrator  and  the  user may define files (see _s_g_e___q_s_t_a_t(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 higher
       precedence than the cluster global file.  Command line can be  used  to
       override the flags contained in the files.

OOPPTTIIOONNSS
       --eexxppllaaiinn aa||AA||cc||EE
              '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  FFuullll
              FFoorrmmaatt in section OOUUTTPPUUTT FFOORRMMAATTSS below.

       --eexxtt   Displays  additional information for each job related to the job
              ticket policy scheme (see OUTPUT FORMATS below).

       --ff     Specifies a "full" format display of information.  The --ff option
              causes  summary  information on all queues to be displayed along
              with the queued job list.

       --FF [ rreessoouurrccee__nnaammee,,...... ]
              Like in the case of --ff information is displayed on all  jobs  as
              well as queues. In addition, _q_s_t_a_t 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 FFuullll FFoorrmmaatt in section
              OOUUTTPPUUTT FFOORRMMAATTSS below for further detail.

       --gg {{cc||dd||tt}}[[++]]
              The --gg option  allows  for  controlling  grouping  of  displayed
              objects.

              With  --gg  cc  a  cluster  queue  summary is displayed. Find  more
              information in the section OOUUTTPPUUTT FFOORRMMAATTSS.

              With --gg dd array 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 OOUUTTPPUUTT  FFOORRMMAATTSS)  specifies  the  corre-
              sponding set of tasks.

              With  --gg  tt  parallel 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 --gg tt option the func-
              tion of each parallel task is displayed  rather  than  the  jobs
              slot amount (see section OOUUTTPPUUTT FFOORRMMAATTSS).


       --hheellpp  Prints a listing of all options.

       --jj [[jjoobb__lliisstt]]
              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 wildcard expression _s_g_e___t_y_p_e_s(1).

              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
              _s_c_h_e_d___c_o_n_f(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.

       --ll rreessoouurrccee[==vvaalluuee],...
              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.

       --nnee    In  combination  with  --ff  the  option suppresses the display of
              empty queues. This means all queues where actually no  jobs  are
              running are not displayed.

       --ppee ppee__nnaammee,,......
              Displays  status  information  with  respect to queues which are
              attached to at least one of the parallel environments listed  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.


       --pprrii   Displays additional information for each job related to the  job
              priorities in general.  (see OUTPUT FORMATS below).

       --qq wwcc__qquueeuuee__lliisstt
              Specifies a wildcard expression queue list to which job informa-
              tion is to be displayed. Find the definition of wwcc__qquueeuuee__lliisstt in
              _s_g_e___t_y_p_e_s(1).

       --qqss {{aa||cc||dd||oo||ss||uu||AA||CC||DD||EE||SS}}
              Allows  for the filtering of queue instances according to state.

       --rr     Prints extended information about the resource  requirements  of
              the  displayed jobs. Please refer to the OOUUTTPPUUTT FFOORRMMAATTSS sub-sec-
              tion EExxppaannddeedd FFoorrmmaatt below for detailed information.

       --ss {{pp||rr||ss||zz||hhuu||hhoo||hhss||hhjj||hhaa||hh||aa}}[[++]]

              Prints only jobs in the  specified  state,  any  combination  of
              states is possible. --ss pprrss corresponds to the regular _q_s_t_a_t out-
              put without --ss at all. To show recently finished jobs, use --ss zz.
              To  display  jobs  in  user/operator/system  hold,  use  the  --ss
              hhuu//hhoo//hhss option. The --ss hhaa option shows jobs which where submit-
              ted  with  the  _q_s_u_b  --aa command.  _q_s_t_a_t --ss hhjj displays all jobs
              which are not eligible for execution unless the job has  entries
              in  the  job dependency list.  _q_s_t_a_t --ss hh is an abbreviation for
              _q_s_t_a_t --ss hhuuhhoohhsshhjjhhaa and _q_s_t_a_t --ss aa is an abbreviation for  _q_s_t_a_t
              --ss ppssrr (see --aa and --hhoolldd__jjiidd option to _q_s_u_b(1)).

       --tt     Prints  extended  information  about the controlled sub-tasks of
              the displayed parallel jobs. Please refer to the OOUUTTPPUUTT  FFOORRMMAATTSS
              sub-section  RReedduucceedd FFoorrmmaatt below for detailed information. Sub-
              tasks of parallel jobs should not be  confused  with  array  job
              tasks (see --gg option above and --tt option to _q_s_u_b(1)).

       --UU uusseerr,,......
              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.

       --uu uusseerr,,......
              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 --ff or --FF options are specified
              additionally and if the user runs jobs in those queues.

              The string  $$uusseerr is a placeholder for the current username.  An
              asterisk  "*"  can  be  used as username wildcard to request any
              users' jobs be displayed. The default value for this  switch  is
              --uu $$uusseerr.


       --uurrgg   Displays  additional information for each job related to the job
              urgency policy scheme (see OUTPUT FORMATS below).

       --xxmmll   This 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.

OOUUTTPPUUTT FFOORRMMAATTSS
       Depending on the presence or absence of the --eexxppllaaiinn, --ff,  --FF,  or  --qqss
       and --rr and --tt option three output formats need to be differentiated.

       The --eexxtt and --uurrgg options may be used to display additional information
       for each job.

   CClluusstteerr QQuueeuuee FFoorrmmaatt ((wwiitthh --gg cc))
       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 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  --gg cc option can be used in combination with --eexxtt. In this case,
          additional columns are added to the output. Each column contains the
          slot count for one of the available queue states.

   RReedduucceedd FFoorrmmaatt ((wwiitthhoouutt --ff,, --FF,, aanndd --qqss))
       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 _s_g_e___p_r_i_o_r_i_t_y(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 _q_d_e_l(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  _q_m_o_d(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 _q_u_e_u_e___c_o_n_f(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
          _q_s_u_b(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 _q_h_o_l_d(1), _q_a_l_t_e_r(1) or
          the  _q_s_u_b(1)  --hh option or that the job is waiting for completion of
          the jobs to which job dependencies have been assigned to the job via
          the --hhoolldd__jjiidd option of _q_s_u_b(1) or _q_a_l_t_e_r(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
          _q_s_t_a_t(1) --jj jjoobb__lliisstt option.

       +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  --gg
          tt is specified.

          Without  --gg  tt  option  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 --gg tt option 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 --tt
          option to _q_s_u_b(1) and the --gg above for additional information.

       If the --tt option is supplied, each status line always contains parallel
       job  task  information as if --gg tt were 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.

   FFuullll FFoorrmmaatt ((wwiitthh --ff aanndd --FF))
       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
          _s_g_e___e_x_e_c_d(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 _l_o_a_d___t_h_r_e_s_h_o_l_d_s list of the queue configuration (see _q_u_e_u_e___c_o_n_f(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 _q_u_e_u_e___c_o_n_f(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 _q_m_o_d(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 _c_a_l_e_n_d_a_r___c_o_n_f(5)), while the S(ubordinate) state
       indicates, that the queue has been suspend via subordination to another
       queue (see _q_u_e_u_e___c_o_n_f(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, _s_g_e___e_x_e_c_d(8) on that host
       was unable to locate the _s_g_e___s_h_e_p_h_e_r_d(8) executable  on  that  host  in
       order  to  start  a  job.  Please  check  the  error  logfile  of  that
       _s_g_e___e_x_e_c_d(8) for leads on how to resolve the problem. Please enable the
       queue afterwards via the --cc option of the _q_m_o_d(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  _s_g_e___c_o_n_f(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  _s_g_e___q_m_a_s_t_e_r(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 not yet  finished  jobs  are  still
       associated  with  it,  and  it will vanish from qstat output when these
       jobs have finished. To quicken vanishing of an orphaned queue  instance
       associated  job(s)  can  be deleted using _q_d_e_l(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 --FF option was used, resource availability information is printed
       following  the  queue status line. For each resource (as selected in an
       option argument to --FF or 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
          `gg' - a cluster global,
          `hh' - a host total or
          `qq' - a queue related resource consumption.

       +o  a second one letter specifier indicating the source for the  current
          resource availability value, being one of
          `ll' - a load value reported for the resource,
          `LL' - a load value for the resource after administrator defined load
          scaling has been applied,
          `cc' - availability derived from the  consumable  resources  facility
          (see _c_o_m_p_l_e_x_e_s(5)),
          `ff'  - 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 --eexxppllaaiinn option 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 --FF option 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 --ff) or the resource availabil-
       ity information (in case of --FF) 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 _s_g_e___p_r_i_o_r_i_t_y(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
          RReedduucceedd FFoorrmmaatt section 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 --gg
          tt is specified.

          Without --gg tt option 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  --gg tt option the function of the running jobs (MASTER
          or SLAVE - the latter for parallel jobs only) is displayed.

       If the --tt option 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
          RReedduucceedd FFoorrmmaatt section 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 _P_E_N_D_I_N_G _J_O_B_S 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 _s_g_e___q_m_a_s_t_e_r(8) starts up from an inconsis-
       tent state in the job or queue spool files or if the cclleeaann qquueeuuee  (--ccqq)
       option of _q_c_o_n_f(1) is used, _q_s_t_a_t 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 _E_R_R_O_R  _J_O_B_S  sec-
       tion  at the very end of the output. The ERROR JOBS section should dis-
       appear upon restart of _s_g_e___q_m_a_s_t_e_r(8).  Please contact your Grid Engine
       support representative if you feel uncertain about the cause or effects
       of such jobs.

   EExxppaannddeedd FFoorrmmaatt ((wwiitthh --rr))
       If the --rr option was  specified  together  with  _q_s_t_a_t,  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  _q_s_u_b(1) --ll option. The per resource addend when determining the
          jobs urgency contribution value  is  printed  (see  also  _s_g_e___p_r_i_o_r_-
          _i_t_y(5)).

       +o  The  requested parallel environment including the desired queue slot
          range (see --ppee option of _q_s_u_b(1)).

       +o  The requested checkpointing environment of the job (see the  _q_s_u_b(1)
          --cckkpptt option).

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

   EEnnhhaanncceedd OOuuttppuutt ((wwiitthh --eexxtt))
       For each job the following additional items are displayed:

       nnttcckkttss The total number of tickets in normalized fashion.

       pprroojjeecctt
              The project to which the job is assigned  as  specified  in  the
              _q_s_u_b(1) --PP option.

       ddeeppaarrttmmeenntt
              The  department, to which the user belongs (use the --ssuull and --ssuu
              options of _q_c_o_n_f(1) to display the  current  department  defini-
              tions).

       ccppuu    The current accumulated CPU usage of the job in seconds.

       mmeemm    The  current  accumulated memory usage of the job in Gbytes sec-
              onds.

       iioo     The current accumulated IO usage of the job.

       ttcckkttss  The total number of tickets assigned to the job currently

       oovvrrttss  The override tickets as assigned by the --oott option of _q_a_l_t_e_r(1).

       oottcckktt  The  override portion of the total number of tickets assigned to
              the job currently

       ffttcckktt  The functional portion of the total number of  tickets  assigned
              to the job currently

       ssttcckktt  The share portion of the total number of tickets assigned to the
              job currently

       sshhaarree  The share of the total system to which the job is entitled  cur-
              rently.

   EEnnhhaanncceedd OOuuttppuutt ((wwiitthh --uurrgg))
       For  each job the following additional urgency policy related items are
       displayed (see also _s_g_e___p_r_i_o_r_i_t_y(5)):

       nnuurrgg   The jobs total urgency value in normalized fashion.

       uurrgg    The jobs total urgency value.

       rrrrccoonnttrr
              The urgency value contribution that reflects the urgency that is
              related to the jobs overall resource requirement.

       wwttccoonnttrr
              The urgency value contribution that reflects the urgency related
              to the jobs waiting time.

       ddllccoonnttrr
              The urgency value contribution that reflects the urgency related
              to the jobs deadline initiation time.

       ddeeaaddlliinnee
              The  deadline  initiation  time of the job as specified with the
              _q_s_u_b(1) --ddll option.

   EEnnhhaanncceedd OOuuttppuutt ((wwiitthh --pprrii))
       For each job, the following additional job priority related  items  are
       displayed (see also _s_g_e___p_r_i_o_r_i_t_y(5)):

       nnuurrgg   The job's total urgency value in normalized fashion.

       nnpppprriioorr
              The job's --pp priority in normalized fashion.

       nnttcckkttss The job's ticket amount in normalized fashion.

       pppprrii   The job's --pp priority as specified by the user.

EENNVVIIRROONNMMEENNTTAALL VVAARRIIAABBLLEESS
       SSGGEE__RROOOOTT       Specifies  the location of the Grid Engine standard con-
                      figuration files.

       SSGGEE__CCEELLLL       If set, specifies  the  default  Grid  Engine  cell.  To
                      address  a  Grid Engine cell _q_s_t_a_t 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. ddeeffaauulltt.


       SSGGEE__DDEEBBUUGG__LLEEVVEELL
                      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.

       SSGGEE__QQMMAASSTTEERR__PPOORRTT
                      If  set,  specifies the tcp port on which _s_g_e___q_m_a_s_t_e_r(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.

       SSGGEE__LLOONNGG__QQNNAAMMEESS
                      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.

FFIILLEESS
       _$_S_G_E___R_O_O_T_/_$_S_G_E___C_E_L_L_/_c_o_m_m_o_n_/_a_c_t___q_m_a_s_t_e_r
                      Grid Engine master host file
       _$_S_G_E___R_O_O_T_/_$_S_G_E___C_E_L_L_/_c_o_m_m_o_n_/_s_g_e___q_s_t_a_t
                      cluster qstat default options
       _$_H_O_M_E_/_._s_g_e___q_s_t_a_t
                      user qstat default options

SSEEEE AALLSSOO
       _s_g_e___i_n_t_r_o(1),   _q_a_l_t_e_r(1),   _q_c_o_n_f(1),   _q_h_o_l_d(1),  _q_h_o_s_t(1),  _q_m_o_d(1),
       _q_s_u_b(1), _q_u_e_u_e___c_o_n_f(5), _s_g_e___e_x_e_c_d(8), _s_g_e___q_m_a_s_t_e_r(8),  _s_g_e___s_h_e_p_h_e_r_d(8).

CCOOPPYYRRIIGGHHTT
       See _s_g_e___i_n_t_r_o(1) for a full statement of rights and permissions.



GE 6.1                   $Date: 2007/11/06 18:18:12 $                 QSTAT(1)
