PSTAT(l)                                                              PSTAT(l)



NAME
       pstat - List attributes of jobs under control of the LCRM

SYNOPSIS
       pstat [-b bank] [-u user] [ -c constraint | -m host]
             [-D] [-H] [-L] [-M] [-R] [-T] [-v | -f | -o outspec]
             [-s sort_order]
       pstat [jobid | -n jobid_list] [-H] [-L] [-M] [-T]
             [-v | -f | -o outspec] [-s sort_order]
       pstat -A [-D] [-H] [-L] [-M] [-R] [-T] [-v | -f | -o outspec]
             [-s sort_order]
       pstat -h

DESCRIPTION
       The  pstat  command  is used to display the attributes of selected jobs
       under control of the LCRM. The command line options are used to delimit
       or  qualify  the set of jobs to be listed except for the -M, -f, -H, -v
       and -o options which are used to  control  the  amount  of  information
       shown.  All  display data is written to standard output. All error data
       is written to standard error. If there are no jobs to show, pstat  ter-
       minates with no data written to standard out.

       When  pstat  is  invoked  with no arguments the output is restricted to
       jobs that are under the control of the calling user.

       Normally only jobs that are running or are  waiting  to  run  are  dis-
       played.  With  the use of the -T option, you may see the data regarding
       jobs that have run and have subsequently terminated.  (Jobs  that  have
       not run before being removed cannot be displayed.) Terminated jobs will
       have one of two statuses. If the status is REMOVED, the job was  force-
       fully  removed  from  running  via  the  utility  prm or by LCRM itself
       because of the job reached a resource limit. Otherwise, the status will
       be COMPLETE.

       Default  output  has  a  heading  line. Then, on one line for each job,
       pstat displays the LCRM jobid (JID), the job or  request  name  (NAME),
       owner  name  (USER),  account  name (ACCOUNT), bank name (BANK), status
       (STATUS), executing or candidate host (EXEHOST), and job class (CL).

OPTIONS
       Command line options that govern output detail:

       -f            Displays all known information about the job.  The  ouput
                     from  this  option is multiple lines. This option may not
                     be used in conjuction with the -o or -v options.

       -H            Turns off the header display.

       -h            Causes a usage message to be printed to standard error.

       -L            Completely lists long bank and user names without trunca-
                     tion

       -o  outspec   List  only  the  fields specified by outspec. This option
                     may not be used in conjuction with the -f or -v  options.
                     outspec  may  specify  multiple  fields, comma separated.
                     Valid field specifications include: account,  aging_time,
                     bank,  batchid,  cl,  constraint, cpn, depend, ecomptime,
                     earliest_start,  exehost,  highwater,  jid,   maxcputime,
                     maxmem,  maxphyss,  maxrss,  maxruntime, memint, memsize,
                     name, nodes, preempted_by, priority, runtime,  sid,  sta-
                     tus,  stoptime,  submitted, tasks, timecharged, timeleft,
                     used, user, and vmemint. If no output  format  specifica-
                     tion is supplied (no -f, -o, or -v options), the environ-
                     ment variable  PSTAT_CONFIG  may  specify  output  format
                     (e.g.,  "setenv  PSTAT_CONFIG name,user"). One additional
                     possible value for outspec is "default", which  means  to
                     use the pstat default output format. Field specifications
                     may be abbreviated. Fields specified by the -o option  or
                     via  the PSTAT_CONFIG environment variable will be listed
                     in the order specified.

       -s  sort_order
                     This option determines the order in  which  job  statuses
                     are  displayed.  The  default  order is in jid order. The
                     sort_order is specified by naming a  column  of  data  on
                     which  to  sort. The column selected for sorting the jobs
                     need not itself be displayed. The  columns  that  can  be
                     specified are

                     STRING:     account,  bank,  batchid, exehost, name, sid,
                                 user

                     NUMERICAL:  aging_time, depend,  earliest_start,  highwa-
                                 ter,  jid, maxcputime, maxphyss, maxrss, mem-
                                 size, nodes, stoptime, timecharged, timeleft,
                                 used

                     PRIORITY:   priority

                     If  a  STRING  column is specified, jobs are displayed in
                     lexical order, from lowest to highest, of the  values  in
                     the specified column. If a NUMERICAL column is specified,
                     jobs are displayed in numerical  order,  from  lowest  to
                     highest,  of  the  values in the specified column. If the
                     PRIORITY column  is  specified,  jobs  are  displayed  in
                     numerical order, from highest to lowest, of the values in
                     the priority column.

                     The order of the displayed  values  can  be  reversed  by
                     prepending a '-' character to the sort key. For instance,
                     "-s priority" would cause jobs to be displayed in  prior-
                     ity order (highest priority job first, to lowest priority
                     job last) while "-s -priority" would  cause  jobs  to  be
                     displayed  in reverse priority order (lowest priority job
                     first, to highest priority job last).

       -v            In addition to default fields, aging  time  (AGING_TIME),
                     maximum  cpu  time (MAXCPUTIME), the sum of the last mea-
                     sured sizes of all processes in the job (MEMSIZE), depen-
                     dency  (DEPEND), time used per task (USED) and the earli-
                     est start time (EARLIEST_START) are  displayed.  Data  is
                     written  on  a  single line for each job. This option may
                     not be used in conjuction with the -f or -o options.

       Command line options that limit jobs selected:

       -A            List all jobs in the LCRM system.  This option is ignored
                     when used with the -b, -m, -n or -u options.

       -D            Will cause delayed jobs to be listed. In general, delayed
                     jobs have no impact on the system as  far  as  scheduling
                     and  performance.  Therefore  the  default behavior is to
                     ignore  them  unless  the  information  is   specifically
                     requested.

       -b bank       List  only  jobs  that are drawing from bank. This option
                     may not be used in conjunction with the -n option.

       -c constraints
                     List only jobs that are running, or have the potential to
                     run,  on hosts that match the given constraint list. (For
                     more information, please see A WORD ABOUT CONSTRAINTS  in
                     the psub manpage.)

       -M            Show  all statuses for the job(s) for all candidate hosts
                     (This is helpful for  obtaining  information  about  jobs
                     that show a MULTIPLE status).

       -m hostname   List only jobs that are running, or have the potential to
                     run, on hostname.

       -n jidlist    List only the jobs with LCRM jobids  that  correspond  to
                     one of the items in jidlist. jidlist must be a comma sep-
                     arated list of LCRM jobids.  This option may not be  used
                     in conjunction with either the -b or -u options.

       -R            List only running jobs

       -T            Display  the  status  of  completed and removed jobs that
                     were under control of the LCRM as well as currently  run-
                     ning or waiting jobs.

       -u uname      List  only  jobs that are owned by uname. This option may
                     not be used in conjunction with the -n option.

FIELD DESCRIPTIONS
       ACCOUNT
              The account name associated with the job.

       AGING_TIME
              If the job is not running but is eligible to be  scheduled,  the
              date-time  at  which  it became eligible to be scheduled. If the
              job is running, the date-time at which the job was scheduled  to
              run.  If  the  job  is terminated, the date-time at which it was
              terminated or removed. Otherwise, this field has no meaning.

       BANK   The bank from which resources used by the job are drawn.

       BATCHID
              The identifier assigned to the job by the  native  batch  system
              that scheduled it.

       CL     The job class. 'N' means normal, 'S' means standby and 'X' means
              expedited.

       CONSTRAINT
              The constraints placed on the residence of  job  execution  (the
              contents of the -c option to psub) as well as the geometry spec-
              ified for the job if applicable.

       CPN    The number of cpus per node requested for the job. If  none  has
              been specified for the job, a value of 1 is assumed.

       DEPEND The  jobid of the job which must complete (or be removed) before
              this job can be scheduled to run.  (If  '0',  this  job  is  not
              dependent on any other job.)

       EARLIEST_START
              The  earliest  date-time  at  which  the job is permitted to run
              (assigned via the -A option to psub or palter.)

       ECOMPTIME
              If the job is running, the estimated completion time of the job.

       EXEHOST
              If  the job is running, the name of the host at which the job is
              running.

       HIGHWATER
              The largest measured size of all processes in the job  over  the
              life of the job.

       JID    The LCRM assigned job identifier.

       MAXCPUTIME
              The maximum cpu time that the job is permitted to consume.

       MAXMEM The  largest  size permitted for any process in the job in kilo-
              bytes.

       MAXPHYSS
              The maximum across all the nodes of a job of the largest sum  of
              physical  sizes through time summed over all process of the job.

       MAXRSS The maximum across all the nodes of a job of the largest sum  of
              resident set sizes through time summed over all processes of the
              job.

       MAXRUNTIME
              The maximum elapsed time that the job is permitted to run.

       MEMINT The resident set memory integral used by the job.

       MEMSIZE
              If the job is running or has ever run, the sum of the last  mea-
              sured  sizes  of  all processes that are part of the job. Other-
              wise, the predicted size of the job when it does start  running.

       NAME   The  name assigned to the job (e.g., via the -r option to psub).

       NODES  The number of nodes that the job requested and is  permitted  to
              use.

       PRIORITY
              The  job's relative scheduling priority. Unlike UNIX "nice" val-
              ues, jobs with higher priorities  are  "more  important"  to  be
              scheduled than jobs with lower priorities. The priority of a job
              is the weighted sum of three values.  The  first  value  is  the
              job's "fair share" priority and is based upon alloted shares and
              recent resource use by the owner of the job and  the  bank  tree
              from  which  it  draws  resources. The second value is the job's
              "aging" priority which is based on how long  the  job  has  been
              eligible to run. The third value is the job's "technical" prior-
              ity and is based on a measure of how well the  job  can  utilize
              available resources.

       RUNTIME
              If  the  job has started running, the elapsed run time since the
              job began running. If the job  has  completed  or  been  removed
              after  it began running, the total elapsed run time for the job.

       SID    The kernel assigned session id of the job.

       STATUS The status of the job. See NOTES below.

       STOPTIME
              The date-time at which the job must be removed.  This  value  is
              set  only  when  a  prm is issued to remove a running job with a
              grace time.

       SUBMITTED
              The date-time at which the job was submitted.

       TASKS  The number of tasks in the job.

       TIMECHARGED
              The total amount of cpu time consumed by the job so far. If  the
              job  has terminated or been removed, the total cpu time consumed
              by the job. (See notes about charge rates.)

       TIMELEFT
              The estimated amount of wall-clock time left to the job.

       USED   The average amount of cpu time consumed by each task in the  job
              so  far.  If the job has terminated or been removed, the average
              amount of cpu time consumed by the each task in the job.

       USER   The job owner.

       VMEMINT
              The physical memory integral used by the job.

EXAMPLES
       The following command lists all jobs that are drawing from bank A

> pstat -b A

  JID  NAME   USER     ACCOUNT  BANK    STATUS  EXEHOST   CL
  874  name1  user1    590001   A       RUN     host1     N
  877  name2  user2    590001   A      *WAIT              N

The following command lists all jobs that were drawing from bank  A  but  have
completed or have been removed as well as jobs that are running or are not yet
scheduled to run.

> pstat -Tb A

  JID  NAME   USER     ACCOUNT  BANK    STATUS   EXEHOST   CL
  872  name3  user1    590001   A       COMPLETE host1     N
  873  name4  user2    590001   A       REMOVED            N
  874  name1  user1    590001   A       RUN      host1     N
  877  name2  user2    590001   A      *WAIT               N

The following command lists all jobs, running or waiting to run, on hosts that
match the constraint list.

> pstat -c 2000MB

  JID  NAME   USER     ACCOUNT  BANK    STATUS   EXEHOST   CL
  872  name3  user1    590001   A       RUN   host1     N
  873  name4  user2    590001   A      *WMEML              N
  874  name1  user1    590001   A      *QTOTLIM  host2     N
  877  name2  user2    590001   A      *WAIT               N

The  following command lists the statuses of 2 jobs at each host at which they
may run.

> pstat -M -n 900,901

  JID  NAME   USER     ACCOUNT  BANK    STATUS   EXEHOST   CL
  900  name1  user2    590001   A      *QTOTLIM  host1     N
  900  name1  user2    590001   A      *QTOTLIMU host2     N
  900  name1  user2    590001   A      *WMEML    host3     N
  901  name2  user2    590001   A       RUN      host3     N

The following command lists the statuses of 2 jobs as  above  without  the  -M
option.

> pstat -n 900,901

  JID  NAME   USER     ACCOUNT  BANK    STATUS   EXEHOST   CL
  900  name1  user2    590001   A      *MULTIPLE           N
  901  name2  user2    590001   A       RUN      host3     N


The following command lists only the jid, name, and user fields.

>pstat -o jid,name,user

  JID  NAME     USER
  874  name1    user1
  877  name2    user2

The  following command lists all of a user's jobs, displaying only the job id,
the executing host name, the status, the batchid and the session id.

>pstat -u user1 -o jid,exehost,status,batchid,sid

  JID  EXEHOST STATUS BATCHID        SID
  874  host1    RUN   176.host1      18885
  875          *WAIT

The following example is equivalent to the previous example (and assumes csh).

>setenv PSTAT_CONFIG jid,exehost,status,batchid,sid
>pstat -u user1

  JID  EXEHOST STATUS BATCHID        SID
  874  host1    RUN   176.host1      18885
  875          *WAIT

The  following  command  lists  all jobs in verbose mode. (Because of the line
length of the output, it will typically display with wrap around.)

>pstat  -v

  JID  NAME     USER     ACCOUNT  BANK      STATUS    EXEHOST   CL
AGING TIME   MAXCPUTIME   MEMSIZE DEPEND     USED  EARLIEST_START
 1587  job1     user1    123456   A          RUN      host1     N  10/02/95
17:00:13       100:00       5Mb      0     0:38
 1578  job2     user2    987654   B          RUN      host2     N  10/02/95
10:35:00        10:00     100Mb      0     6:06
 1592  job3     user3    123123   C          HELDu    host3     N  10/02/95
16:11:54        16:00   74432Kb      0     0:53
 1591  job4     user4    321321   D         *WAIT               N  10/02/95
17:40:26         0:30     230Mb      0     0:00  10/03/95 00:00:00

The following command lists jobs in full mode. Because of the amount of data,
it is multiple lines of output per entry.

> pstat  -f

---------------------------------------------------------------------------
LCRM BATCH JOB ID             16614 user:                            eckert
---------------------------------------------------------------------------
  job name:               sampleJob bank:                               sa
  batch identifier:  blue199.3265.0 account:                         000000
  session identifier: blue199.13172

  executing host:              blue job status:                         RUN
  expedited:                     no standby:                             no
  priority:                   0.568 preempted by:                       N/A

  cpn:                          N/A min/max nodes:                        2
  node distribution:              2  geometry:                          N/A
  constraint:                                                   blue,pbatch

  submitted at:   09/06/99 08:56:04 earliest start time:                N/A
  must stop at:                 N/A terminated at:                      N/A
  elapsed run time limit:      2:00 time limit per task:               2:00
  elapsed run time:            1:03 tasks:                               32
  time used:                  32:11 time used per task:                1:00
  time charged:               32:50

  resident memory integral:  583Mbh physical memory integral:        614Mbh
  largest process size:        19Mb process size limit:           unlimited
  max resident set size:      813Mb max physical size:                302Mb
  job size:                   624Mb


NOTES
       If a job is permitted to run on more than one host, it actually  has  a
       somewhat  independent status for each of the hosts until it is actually
       scheduled to run on one of them. When a job  is  not  running  and  the
       pstat  output  is  not qualified by the -m option, the status shown for
       the job may apply to only one of the hosts at which it is permitted  to
       run. The host to which the status applies is not shown.

       For example, a job may request a maximum time greater than is currently
       permitted (by an administrator) at one host and at the same time may be
       prevented  from  running  on another host because that host's memory is
       currently overloaded. The status for the job could be shown  either  as
       TOOLONG  or WMEM. To see a job's status at any particular host, use the
       -m option.

       Different charge rates for different classes may be  applied  to  jobs.
       The defined batch job classes are: expedited, normal and standby.

       Possible values for "STATUS" are:

       (If an asterisk(*) precedes the status field, it indicates that the job
       has not yet run.)

       Value     Meaning

       BAT_WAIT  On starting a job (or restarting  a  checkpointed  job),  the
                 native  batch  system has determined that necessary resources
                 are not available to the job and has  delayed  its  execution
                 until  those  resources  are available. (For instance, in the
                 case of a restarted job either the job's session id or one of
                 its  process  id's may be claimed by another session. Another
                 example would be that a job requests more nodes on an  multi-
                 node  machine  than  are currently available.)  The user must
                 either wait until the claimed resource has been  released  or
                 terminate and resubmit the job.

       COMPLETE  The  job  has  completed execution and is no longer under the
                 control of LCRM.

       CPU&TIME  The number of nodes (-ln) and time limit (-tM) evalutated  to
                 a  number  that exceeds the currently configured maximum per-
                 mitted node count * time limit per job. The job will  be  re-
                 evaluated  when  the  configured  maximum amount permitted is
                 increased by an administrator.

       CPUS>MAX  The number of requested cpus (-lc) or nodes (-ln)  evalutated
                 to  a  number  that  exceeds the currently configured maximum
                 permitted cpus per job. The job will be re-evaluated when the
                 configured maximum amount permitted is increased by an admin-
                 istrator.

       DEPEND    The job is specifically awaiting the  completion  of  another
                 job.  It will be re-evaluated when the job it depends on ter-
                 minates.

       DEFERRED  The production host returned a bad status for this  job.  The
                 job  will  be held for a specific period of time and then re-
                 evaluated. The default waiting period is 10 minutes.

       DELAYED   The job is in the user's FIFO delayed job queue.   This  hap-
                 pens  when the user has more than maxjobsperuser jobs waiting
                 to be scheduled.   The  maxjobsperuser  variable  is  a  LCRM
                 global  variable.  As the user's submitted jobs are scheduled
                 by LCRM, delayed jobs will automatically be submitted to LCRM
                 in first in, first out order.

       ELIG      The job is eligible to run.

       HELD[c][s][u]
                 The  job has an explicit user level, coordinator level and/or
                 a system level hold applied  to  it.  If  the  character  'u'
                 appears  after  the  HELD  status, then a user level hold has
                 been applied. If the character 'c' appears, then a  coordina-
                 tor  level  hold  has  been  applied.  If  the  character 's'
                 appears, then a system level  hold  has  been  applied.  User
                 level  holds can be set or released by a job owner, coordina-
                 tor or LCRM manager. Coordinator level holds can  be  set  or
                 cleared  by a coordinator or LCRM manager. System level holds
                 can be set or cleared only by a LCRM manager. The job will be
                 re-evaluated after all hold levels are removed (via prel).

       HLD_IDLE  A  user  level  hold  has been applied to the job by the LCRM
                 system because its use of CPU time has fallen below a minimum
                 threshold.  The user level hold (and thus this status) can be
                 removed by using prel.

       HOLDING   The job is in the process of being  checkpointed.  After  the
                 job  is  checkpointed,  its  status  is  re-evaluated and set
                 depending on the reason for the checkpoint.

       JRESLIM   Scheduling the job would cause a limit on the number of  jobs
                 that  can run concurrently on the machines in a resource par-
                 tition to be exceeded. The applicable limit is the least num-
                 ber  of  jobs permitted to the user/bank or any of its parent
                 banks in the resource partition.

       MULTIPLE  The job has different statuses at two or more of the hosts at
                 which  it may run, or multiple statuses on a single host. Use
                 the -M option to see the job's status at each of  its  candi-
                 date hosts.

       NOACCT    The account name to be associated with the resources this job
                 will use has been removed. The job will be re-evaluated  when
                 a valid account is assigned to the job (via palter).

       NOBANK    The  bank  from  which  the  job was to draw its resources no
                 longer exists.  The job will be  re-evaluated  when  a  valid
                 bank is assigned to the job (via palter).

       NOCONF    A  host  permitted  to  run the job does not currently have a
                 valid configuration parameter set. The job will be  re-evalu-
                 ated  when  an  administrator  assigns  a valid configuration
                 parameter set.

       NONEW     An administrator has disallowed new jobs from  running  while
                 this  job  was not running. The job will be re-evaluated when
                 new jobs are again permitted to run by an administrator.

       NOPRISRV  A host permitted to run this job is operating at  a  priority
                 service  level greater than normal, and the the job's bank is
                 not within the priority service bank tree. The  job  will  be
                 re-evaluated  with  the host is returned to normal service by
                 an administrator.

       NOTIME    The job owner has zero effective  shares  to  the  bank  from
                 which the job is drawing resources. The job will be re-evalu-
                 ated when bank shares are reassigned by a coordinator or sys-
                 tem administrator. (Use pshare with the "-m <machine>" option
                 to determine the shares you have allocated to bank(s) on  the
                 target  machine.  Use  pshare  with the "-m <machine> and "-r
                 <bank>" options to determine  the  shares  allocated  to  the
                 bank's  parent  tree.  If any bank in the tree has zero allo-
                 cated shares, then all subbanks as well as your permission to
                 the <bank> specified have zero effective shares at the speci-
                 fied machine.)

       NRESLIM   Scheduling the job would cause a limit on the number of nodes
                 that  can be committed to a user or bank in a resource parti-
                 tion to be exceeded. The applicable limit is the least number
                 of  nodes  permitted  to  the  user/bank or any of its parent
                 banks in the resource partition.

       NTRESLIM  Scheduling the job would cause a limit on the amount of node-
                 time  that  can  be committed to a user or bank in a resource
                 partition to be exceeded. The applicible limit is  the  least
                 amount  of node-time permitted to the user/bank or any of its
                 parent banks in the resource partition.

       PREEMPTD  On machines that support preemption,  this  status  indicates
                 that  the  job  has been preempted in order to allow a higher
                 priority  job  to  run  using  the  preempted  jobs  set   of
                 resources.  The  output  from  PSTAT using the -f option will
                 show the job id of the job that has  preempted  this  job.  A
                 preempted  job is stopped from running and will resume execu-
                 tion once the higher priority job has terminated.

       PTOOBIG   The maximum, or estimated maximum, process size  of  the  job
                 exceeds  the  maximum permitted size of processes at the exe-
                 cuting host. The job will be re-evaluated when the configured
                 maximum permitted size of processes is increased by an admin-
                 istrator.

       QCKPLIM   A host permitted to run this job has reached  its  checkpoint
                 file space limit.  This status is only possible for jobs that
                 may run on hosts that support checkpointing. The job will  be
                 re-evaluated  when sufficient space is made available by ter-
                 minating jobs.

       QTOTLIM   The number of running jobs plus checkpointed jobs on  a  host
                 permitted  to  run  this  job is greater than or equal to the
                 maximum number of such jobs permitted  by  an  administrator.
                 The  job  will be re-evaluated when any of the active jobs on
                 the  host  terminates  or  when  configuration   limits   are
                 increased.

       QTOTLIMU  The  number  of  running jobs plus checkpointed jobs that are
                 owned by the job's owner on a host permitted to run this  job
                 is  greater  than or equal to the maximum number of such jobs
                 owned by a single user permitted by an administrator. The job
                 will be re-evaluated when any of the active jobs owned by the
                 user on the host terminates or when configuration limits  are
                 increased.

       REMOVED   The job has been removed by the 'prm(1)' utility.

       RM_PEND   The job is in the process of being removed from the system.

       RM_STBY   The  job  is  being  removed  to start a higher priority job.
                 (Only standby jobs will ever have this status.)

       RUN       The job has been given to the underlying batch system and the
                 batch  system  has  started the job. Even if a job spends the
                 majority of its time in a sleep state, the job is still  con-
                 sidered running.

       RUN_SBY   The  same  as  run,  except the job is running in the standby
                 class and is subject to the rules that apply to standby jobs.

       STAGING   The job has been submitted by LCRM to the native batch system
                 for it to run and the native batch system has  not  confirmed
                 yet that the job is actually running.

       STOPPEND  The  job  is running, but has been removed (prm) with a grace
                 time before it is forcefully removed.

       TIMEOUT   A request has been made to a production machine that did  not
                 respond  in  a timely manor. The request is reissued until it
                 is successful.

       TOOLONG   The job requests more time than the currently configured max-
                 imum permitted time. The job will be re-evaluated if its max-
                 imum permitted time is decreased (via palter) or if the  con-
                 figured maximum permitted time is increased by an administra-
                 tor.

       TQUOTA    The job owner's allocation or bank has reached  its  resource
                 usage quota. The job will be re-evaluated when the user allo-
                 cation or bank's  quota  is  automatically  refreshed  or  is
                 refreshed by an administrator.

       USED>MAX  The  time  used  by  the  job  is  greater  than  its maximum
                 requested time. This status is only possible  for  jobs  that
                 run  on hosts that support checkpointing.  On other machines,
                 a job will be terminated if it uses all  the  time  requested
                 for it. The job will be re-evaluated if its maximum permitted
                 time is increased (via palter).

       WAIT      The job has not yet reached its do-not-run-before time.  When
                 this time is reached, the job will be re-evaluated.

       WCPU      There  are  not  enough  cpus/nodes available for this job to
                 run.

       WHOST     A host permitted to run this job is not currently being  man-
                 aged  by  LCRM.   When communications with the host have been
                 re-established the job will be re-evaluated.

       WMEML     The memory of a host permitted to run this job would be over-
                 committed  based  on the limits set by the system administra-
                 tors. The job will be re-evaluated when enough memory becomes
                 available via termination of processes and/or jobs.

       WMEMT     The  memory  of a host permitted to run this job would exceed
                 the target range that has been set by the system  administra-
                 tor.  The job will be re-evaluated when enough memory becomes
                 available via termination of processes and/or jobs.

       WPRIO     While there are enough nodes to run this job, doing so  would
                 cause the start of a higher priority job to be delayed.

       WSTBY     This  job  is  waiting  for  one  or more  standby jobs to be
                 removed so that it can start.

       WSUBH     The host at which the job  was  submitted  is  not  currently
                 being  managed  by  LCRM.   When communications with the host
                 have been re-established the job will be re-evaluated.


Possible values for "CL" (class) are:
       D      The job is a delayed job

       N      The job is a normal job.

       S      The job has been specified as a standby job.

       X      The job has been expedited.

AUTHOR
       Robert R Wood, Lawrence Livermore National Laboratory,
            bwood@llnl.gov

SEE ALSO
       palter, pexp, plim, phold, prel, prm



                                                                      PSTAT(l)