View available application profiles

Procedure

Run bapp. You can view a particular application profile or all profiles.
bapp
APPLICATION_NAME  NJOBS  PEND   RUN  SUSP
fluent               0     0     0     0
catia                0     0     0     0

A dash (-) in any entry means that the column does not apply to the row.

View detailed application profile information

Procedure

To see the complete configuration for each application profile, run bapp -l.

bapp -l also gives current statistics about the jobs in a particular application profile, such as the total number of jobs in the profile, the number of jobs running, suspended, and so on.

Specify application profile names to see the properties of specific application profiles.

bapp -l fluent
APPLICATION NAME: fluent
 -- Application definition for Fluent v2.0
STATISTICS:
   NJOBS     PEND      RUN    SSUSP    USUSP      RSV
       0        0        0        0        0        0
 
PARAMETERS:
 CPULIMIT
 600.0 min of hostA
 RUNLIMIT
 200.0 min of hostA
Start of change  TASKLIMIT End of change
 9
 FILELIMIT DATALIMIT STACKLIMIT CORELIMIT MEMLIMIT SWAPLIMIT PROCESSLIMIT THREADLIMIT
    800 K     100 K     900 K      700 K     300 K   1000 K     400          500
RERUNNABLE: Y
CHUNK_JOB_SIZE: 5

View jobs associated with application profiles

Procedure

Run bjobs -l -app application_profile_name.
bjobs -l -app fluent
Job <1865>, User <user1>, Project <default>, Application <fluent>, 
                     Status <PSUSP>, Queue <normal>, Command <ls>
Tue Jun  6 11:52:05 2009: Submitted from host <hostA> with hold, CWD
                     </clusters/lsf9.1/work/cluster1/logdir>;
 PENDING REASONS:
 Job was suspended by LSF admin or root while pending;
 SCHEDULING PARAMETERS:
           r15s   r1m  r15m   ut      pg    io   ls    it    tmp    swp    mem   tlu
 loadSched   -     -     -     -       -     -    -     -     -      -      -     -
 loadStop    -     -     -     -       -     -    -     -     -      -      -     -
                 cpuspeed    bandwidth
 loadSched          -            -
 loadStop           -            -
...

A dash (-) in any entry means that the column does not apply to the row.

Accounting information for all jobs associated with an application profile

Procedure

Run bacct -l -app application_profile_name.
bacct -l -app fluent
Accounting information about jobs that are:
  - submitted by users jchan,
  - accounted on all projects.
  - completed normally or exited
  - executed on all hosts.
  - submitted to all queues.
  - accounted on all service classes.
  - associated with application profiles: fluent
------------------------------------------------------------------------------
 
Job <207>, User <user1>, Project <default>, Application <fluent>, Status <DONE>
                     , Queue <normal>, Command <dir>
Wed May 31 16:52:42 2009: Submitted from host <hostA>, CWD <$HOME/src/mainline/lsbatch/cmd>;
Wed May 31 16:52:48 2009: Dispatched to 10 Hosts/Processors <10*hostA>
Wed May 31 16:52:48 2009: Completed <done>.
Accounting information about this job:
     CPU_T     WAIT     TURNAROUND   STATUS     HOG_FACTOR    MEM    SWAP
      0.02        6              6     done         0.0035     2M      5M
------------------------------------------------------------------------------
...
SUMMARY:      ( time unit: second )
 Total number of done jobs:      15      Total number of exited jobs:     4
 Total CPU time consumed:       0.4      Average CPU time consumed:     0.0
 Maximum CPU time of a job:     0.0      Minimum CPU time of a job:     0.0
 Total wait time in queues:  5305.0
 Average wait time in queue:  279.2
 Maximum wait time in queue: 3577.0      Minimum wait time in queue:    2.0
 Average turnaround time:       306 (seconds/job)
 Maximum turnaround time:      3577      Minimum turnaround time:         5
 Average hog factor of a job:  0.00 ( cpu time / turnaround time )
 Maximum hog factor of a job:  0.01      Minimum hog factor of a job:  0.00
 Total throughput:             0.14 (jobs/hour)  during  139.98 hours
 Beginning time:       May 31 16:52      Ending time:          Jun  6 12:51
...

View job success exit values and requeue exit code information

Procedure

  1. Run bjobs -l to see command-line requeue exit values if defined.
    bjobs -l
    
    Job <405>, User <user1>, Project <default>, Status <PSUSP>, 
    Queue <normal>, Command <myjob 1234>
    Tue Dec 11 23:32:00 2009: Submitted from host <hostA> with hold, CWD </scratch/d
                         ev/lsfjobs/user1/work>, Requeue Exit Values <2>;
    ...
  2. Run bapp -l to see SUCCESS_EXIT_VALUES when the parameter is defined in an application profile.
    bapp -l
    APPLICATION NAME: fluent
     -- Run FLUENT applications
    
    STATISTICS:
       NJOBS     PEND      RUN    SSUSP    USUSP      RSV 
           0        0        0        0        0        0
    
    PARAMETERS:
    
    SUCCESS_EXIT_VALUES: 230 222 12
    ...
  3. Run bhist -l to show command-line specified requeue exit values with bsub and modified requeue exit values with bmod.
    bhist -l
    Job <405>, User <user1>, Project <default>, Command <myjob 1234>
    Tue Dec 11 23:32:00 2009: Submitted from host <hostA> with hold, to Queue 
    <norma
                         l>, CWD </scratch/dev/lsfjobs/user1/work>, R
                         e-queue Exit Values <1>;
    Tue Dec 11 23:33:14 2009: Parameters of Job are changed:
                             Requeue exit values changes to: 2;
    ...
  4. Run bhist -l and bacct -l to see success exit values when a job is done successfully. If the job exited with default success exit value 0, bhist and bacct do not display the 0 exit value
    bhist -l 405
    Job <405>, User <user1>, Project <default>, Interactive pseudo-terminal mode, Co
                         mmand <myjob 1234>
    ...
    Sun Oct  7 22:30:19 2009: Done successfully. Success Exit Code: 230 222 12.
    ...
    bacct -l 405
    ...
    Job <405>, User <user1>, Project <default>, Status <DONE>, Queue <normal>, Comma
                         nd <myjob 1234>
    Wed Sep 26 18:37:47 2009: Submitted from host <hostA>, CWD </scratch/dev/lsfjobs/user1/wo
                         rk>;
    Wed Sep 26 18:37:50 2009: Dispatched to <hostA>;
    Wed Sep 26 18:37:51 2009: Completed <done>. Success Exit Code: 230 222 12.
    ...