For example, the following bjobs command shows that job 2 is running longer than the configured JOB_OVERRUN threshold, and is consuming no CPU time. bjobs displays the job idle factor, and both job overrun and job idle exceptions. Job 1 finished before the configured JOB_UNDERRUN threshold, so bjobs shows exception status of underrun:
bjobs -x -l -aJob <2>, User <user1>, Project <default>, Status <RUN>, Queue <normal>, Command<sleep 600>Wed Aug 13 14:23:35 2009: Submitted from host <hostA>, CWD <$HOME>, Output File</dev/null>, Specified Hosts <hostB>;Wed Aug 13 14:23:43 2009: Started on <hostB>, Execution Home </home/user1>, ExecutionCWD </home/user1>;Resource usage collected.IDLE_FACTOR(cputime/runtime): 0.00MEM: 3 Mbytes; SWAP: 4 Mbytes; NTHREAD: 3PGID: 5027; PIDs: 5027 5028 5029SCHEDULING PARAMETERS:r15s r1m r15m ut pg io ls it tmp swp memloadSched - - - - - - - - - - -loadStop - - - - - - - - - - -cpuspeed bandwidthloadSched - -loadStop - -EXCEPTION STATUS: overrun idle------------------------------------------------------------------------------Job <1>, User <user1>, Project <default>, Status <DONE>, Queue <normal>, Command<sleep 20>Wed Aug 13 14:18:00 2009: Submitted from host <hostA>, CWD <$HOME>,Output File </dev/null>, Specified Hosts <hostB>;Wed Aug 13 14:18:10 2009: Started on <hostB>, Execution Home </home/user1>, ExecutionCWD </home/user1>;Wed Aug 13 14:18:50 2009: Done successfully. The CPU time used is 0.2 seconds.SCHEDULING PARAMETERS:r15s r1m r15m ut pg io ls it tmp swp memloadSched - - - - - - - - - - -loadStop - - - - - - - - - - -cpuspeed bandwidthloadSched - -loadStop - -EXCEPTION STATUS: underrun