Platform LSF Reference Version 6.2
bhist
Platform LSF Reference
43
bhist
displays historical information about jobs
SYNOPSIS
bhist [-a | -d | -p | -r | -s] [-b | -w] [-l] [-t] [-C start_time,end_time]
[
-D start_time,end_time] [-S start_time,end_time] [-T start_time,end_time]
[
-f logfile_name | -n number_logfiles | -n 0] [-J job_name]
[
-Lp ls_project_name] [-m host_name] [-N host_name | -N host_model |
-N CPU_factor] [-P project_name] [-q queue_name] [-u user_name | -u all]
bhist [-J job_name] [-N host_name | -N host_model | -N CPU_factor]
[job_ID ... |
"job_ID[index]" ...]
bhist [-h | -V]
DESCRIPTION
By default:
◆
Displays information about your own pending, running and suspended jobs.
Groups information by job
◆
CPU time is not normalized
◆
Searches the event log file currently used by the LSF system:
$LSB_SHAREDIR/cluster_name/logdir/lsb.events (see
lsb.events(5))
◆
Displays events occurring in the past week, but this can be changed by setting the
environment variable LSB_BHIST_HOURS to an alternative number of hours
If neither
-l nor -b is present, the default is to display the fields in “OUTPUT” only.
OPTIONS
-a
Displays information about both finished and unfinished jobs.
This option overrides
-d, -p, -s, and -r.
-b
Brief format. Displays the information in a brief format. If used with the -s option,
shows the reason why each job was suspended.
-d
Only displays information about finished jobs.
-l
Long format. Displays additional information. If used with -s, shows the reason why
each job was suspended.
If you submitted a job using the
OR (||) expression to specify alternative resources, this
option displays the successful
rusage string that caused the job to run.
bhist -l can display job exit codes. A job with exit code 131 means that the job
exceeded a configured resource usage limit and LSF killed the job with signal 3
(131-128=3).