LSF Version 7.3 - Running Jobs With Platform LSF

Viewing Job History (bhist)
Sometimes you want to know what has happened to your job since it was submitted. The
bhist command displays a summary of the pending, suspended and running time of
jobs for the user who invoked the command. Use
bhist -u all to display a summary
for all users in the cluster.
For more details on
bhist options, see the bhist command in the Platform LSF
Command Reference.
◆ “Viewing detailed job history” on page 49
◆ “Viewing history of jobs not listed in active event log” on page 49
◆ “Viewing chronological history of jobs” on page 50
Viewing detailed job history
The -l option of bhist displays the time information and a complete history of
scheduling events for each job.
bhist -l 1531
JobId <1531>, User <user1>, Project <default>, Command< example200>
Fri Dec 27 13:04:14: Submitted from host <hostA> to Queue <priority>,
CWD <$HOME>, Specified Hosts <hostD>;
Fri Dec 27 13:04:19: Dispatched to <hostD>;
Fri Dec 27 13:04:19: Starting (Pid 8920);
Fri Dec 27 13:04:20: Running with execution home </home/user1>, Execution CWD
</home/user1>, Execution Pid <8920>;
Fri Dec 27 13:05:49: Suspended by the user or administrator;
Fri Dec 27 13:05:56: Suspended: Waiting for re-scheduling after being resumed
by user;
Fri Dec 27 13:05:57: Running;
Fri Dec 27 13:07:52: Done successfully. The CPU time used is 28.3 seconds.
Summary of time in seconds spent in various states by Sat Dec 27 13:07:52 1997
PEND PSUSP RUN USUSP SSUSP UNKWN TOTAL
5 0 205 7 1 0 218
Viewing history of jobs not listed in active event log
LSF periodically backs up and prunes the job history log. By default, bhist only
displays job history from the current event log file. You can use
bhist -n
num_logfiles to display the history for jobs that completed some time ago and are
no longer listed in the active event log.
num_logfiles
The -n num_logfiles option tells the bhist command to search through the
specified number of log files instead of only searching the current log file.
Log files are searched in reverse time order. For example, the command
bhist -n 3
searches the current event log file and then the two most recent backup files.