displays historical information about jobs
Displays information about your own pending, running and suspended jobs. Groups information by job
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
Displays information about both finished and unfinished jobs.
If the job was submitted bsub -K, the -l option displays Synchronous execution.
If you submitted a job using the OR (||) expression to specify alternative resources, this option displays the successful Execution rusage string with which the job ran.
If you submitted a job with multiple resource requirement strings using the bsub -R option for the order, same, rusage, and select sections, bhist -l displays a single, merged resource requirement string for those sections, as if they were submitted using a single -R.
bhist -l displays job exit codes.
bhist -l displays jobs exceptions. For example, if a job's runtime exceeds the runtime estimate, a job exception of runtime_est_exceeded displays.
Only displays jobs that completed or exited during the specified time interval. Specify the span of time for which you want to display the history. If you do not specify a start time, the start time is assumed to be the time of the first occurrence. If you do not specify an end time, the end time is assumed to be now.
Specify the times in the format "yyyy/mm/dd/HH:MM". Do not specify spaces in the time interval string.
Only displays jobs dispatched during the specified time interval. Specify the span of time for which you want to display the history. If you do not specify a start time, the start time is assumed to be the time of the first occurrence. If you do not specify an end time, the end time is assumed to be now.
Specify the times in the format "yyyy/mm/dd/HH:MM". Do not specify spaces in the time interval string.
Only displays jobs associated with a user group submitted with bsub -G for the specified user group. The –G option does not display jobs from subgroups within the specified user group.
The -G option cannot be used together with the -u option. You can only specify a user group name. The keyword all is not supported for -G.
Only displays information about jobs submitted during the specified time interval. Specify the span of time for which you want to display the history. If you do not specify a start time, the start time is assumed to be the time of the first occurrence. If you do not specify an end time, the end time is assumed to be now.
Specify the times in the format "yyyy/mm/dd/HH:MM". Do not specify spaces in the time interval string.
Only displays information about job events within the specified time interval. Specify the span of time for which you want to display the history. If you do not specify a start time, the start time is assumed to be the time of the first occurrence. If you do not specify an end time, the end time is assumed to be now.
Specify the times in the format yyyy/mm/dd/HH:MM. Do not specify spaces in the time interval string.
Searches the specified event log. Specify either an absolute or a relative path.
Useful for analysis directly on the file.
The specified file path can contain up to 4094 characters for UNIX, or up to 255 characters for Windows.
Only displays the jobs that have the specified job name.
The job name can be up to 4094 characters long for UNIX and Linux or up to 255 characters for Windows. Job names are not unique.
The wildcard character (*) can be used anywhere within a job name, but cannot appear within array indices. For example job* returns jobA and jobarray[1], *AAA*[1] returns the first element in all job arrays with names containing AAA, however job1[*] will not return anything since the wildcard is within the array index.
Only displays information about jobs belonging to the specified License Scheduler project.
Searches the specified number of event logs, starting with the current event log and working through the most recent consecutively numbered logs. The maximum number of logs you can search is 100. Specify 0 to specify all the event log files in $(LSB_SHAREDIR)/cluster_name/logdir (up to a maximum of 100 files).
If you delete a file, you break the consecutive numbering, and older files are inaccessible to bhist.
For example, if you specify 3, LSF searches lsb.events, lsb.events.1, and lsb.events.2. If you specify 4, LSF searches lsb.events, lsb.events.1, lsb.events.2, and lsb.events.3. However, if lsb.events.2 is missing, both searches include only lsb.events and lsb.events.1.
Normalizes CPU time by the specified CPU factor, or by the CPU factor of the specified host or host model.
If you use bhist directly on an event log, you must specify a CPU factor.
Only displays information about jobs belonging to the specified project.
Only displays information about jobs submitted to the specified queue.
Displays information about jobs submitted by the specified user, or by all users if the keyword all is specified. To specify a Windows user account, include the domain name in uppercase letters and use a single back slash (DOMAIN_NAME\user_name) in a Windows command line or a double back slash (DOMAIN_NAME\\user_name) in a UNIX command line.
Searches all event log files and only displays information about the specified jobs. If you specify a job array, displays all elements chronologically.
This option overrides all other options except -J, -N, -h, and -V. When it is used with -J, only those jobs listed here that have the specified job name are displayed.
Statistics of the amount of time that a job has spent in various states:
The total waiting time excluding user suspended time before the job is dispatched.
The total system suspended time after the job is dispatched.
The total unknown time of the job (job status becomes unknown if sbatchd on the execution host is temporarily unreachable).
The total time that the job has spent in all states; for a finished job, it is the turnaround time (that is, the time interval from job submission to job completion).
The -l option displays a long format listing with the following additional fields:
Detailed history includes job group modification, the date and time the job was forwarded and the name of the cluster to which the job was forwarded.
The displayed job command can contain up to 4094 characters for UNIX, or up to 255 characters for Windows.
The initial checkpoint period specified at the job level, by bsub -k, or in an application profile with CHKPNT_INITPERIOD.
The checkpoint period specified at the job level, by bsub -k, in the queue with CHKPNT, or in an application profile with CHKPNT_PERIOD.
The checkpoint directory specified at the job level, by bsub -k, in the queue with CHKPNT, or in an application profile with CHKPNT_DIR.
The migration threshold specified at the job level, by bsub -mig.
Job was submitted with the -K option. LSF submits the job and waits for the job to complete.
You use the time interval to define a start and end time for collecting the data to be retrieved and displayed. While you can specify both a start and an end time, you can also let one of the values default. You can specify either of the times as an absolute time, by specifying the date or time, or you can specify them relative to the current time.
Specify the time interval is follows:
start_time,end_time|start_time,|,end_time|start_time
Specify start_time or end_time in the following format:
[year/][month/][day][/hour:minute|/hour:]|.|.-relative_int
month is a number from 1 to 12, where 1 is January and 12 is December.
day is a number from 1 to 31, representing the day of the month.
hour is an integer from 0 to 23, representing the hour of the day on a 24-hour clock.
minute is an integer from 0 to 59, representing the minute of the hour.
.-relative_int is a number, from 1 to 31, specifying a relative start or end time prior to now.
Specifies a start time, and lets the end time default to now.
Specifies to start with the first logged occurrence, and end at the time specified.
Starts at the beginning of the most specific time period specified, and ends at the maximum value of the time period specified. For example, 2/ specifies the month of February—start February 1 at 00:00 a.m. and end at the last possible minute in February: February 28th at midnight.
Assume the current time is May 9 17:06 2008:
1,8 = May 1 00:00 2008 to May 8 23:59 2008
,4 = the time of the first occurrence to May 4 23:59 2008
6 = May 6 00:00 2008 to May 6 23:59 2008
2/ = Feb 1 00:00 2008 to Feb 28 23:59 2008
/12: = May 9 12:00 2008 to May 9 12:59 2008
2/1 = Feb 1 00:00 2008 to Feb 1 23:59 2008
2/1, = Feb 1 00:00 to the current time
,. = the time of the first occurrence to the current time
,2/10: = the time of the first occurrence to May 2 10:59 2008
2001/12/31,2008/5/1 = from Dec 31, 2001 00:00:00 to May 1st 2008 23:59:59