Platform LSF Version 6.0 - Platform LSF Reference

[ Platform Documentation ] [ Title ] [ Contents ] [ Previous ] [ Next ] [ Index ]

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] [-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 alternate number of hours

If neither -l nor -b is present, the default is to display the fields in OUTPUT only (see below).

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 -soption, 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.

For example, bhist -l can display configured thread limit.

bhist -l can display job exit code. A job with exit code 131 means that the job exceeded a configured resource usage limit and LSF killed the job.

-p

Only displays information about pending jobs.

-r

Only displays information about running jobs.

-s

Only displays information about suspended jobs.

-t

Displays job events chronologically.

-w

Wide format. Displays the information in a wide format.

-C start_time,end_time

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. 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.

The time interval can be specified in many ways. For more specific syntax and examples of time formats, see TIME INTERVAL FORMAT.

-D start_time,end_time

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. 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.

The time interval can be specified in many ways. For more specific syntax and examples of time formats, see TIME INTERVAL FORMAT.

-S start_time,end_time

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. 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.

The time interval can be specified in many ways. For more specific syntax and examples of time formats, see TIME INTERVAL FORMAT.

-T start_time,end_time

Used together with -t.

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. 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.

The time interval can be specified in many ways. For more specific syntax and examples of time formats, see TIME INTERVAL FORMAT.

-f logfile_name

Searches the specified event log. Specify either an absolute or a relative path.

Useful for analysis directly on the file.

-J job_name

Only displays the jobs that have the specified job_name.

-m host_name

Only displays jobs dispatched to the specified host.

-n number_logfiles | -n 0

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 will be 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 will include only lsb.events and lsb.events.1.

-N host_name | -N host_model | -N CPU_factor

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.

Use lsinfo to get host model and CPU factor information.

-P project_name

Only displays information about jobs belonging to the specified project.

-q queue_name

Only displays information about jobs submitted to the specified queue.

-u user_name | -u all

Displays information about jobs submitted by the specified user, or by all users if the keyword all is specified.

job_ID | "job_ID[index]"

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.

-h

Prints command usage to stderr and exits.

-V

Prints LSF release version to stderr and exits.

OUTPUT

Default Format

Statistics of the amount of time that a job has spent in various states:

PEND

The total waiting time excluding user suspended time before the job is dispatched.

PSUSP

The total user suspended time of a pending job.

RUN

The total run time of the job.

USUSP

The total user suspended time after the job is dispatched.

SSUSP

The total system suspended time after the job is dispatched.

UNKWN

The total unknown time of the job (job status becomes unknown if sbatchd on the execution host is temporarily unreachable).

TOTAL

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).

Long Format (-l)

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.

FILES

Reads lsb.events.

SEE ALSO

lsb.events(5), bgadd(1), bgdel(1), bjgroup(1), bsub(1), bjobs(1), lsinfo(1)

TIME INTERVAL FORMAT

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

Where:

year is a four-digit number representing the calendar year.
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.
. (period) represents the current month/day/hour:minute.
.-relative_int is a number, from 1 to 31, specifying a relative start or end time prior to now.

start_time,end_time

Specifies both the start and end times of the interval.

start_time,

Specifies a start time, and lets the end time default to now.

,end_time

Specifies to start with the first logged occurrence, and end at the time specified.

start_time

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.

ABSOLUTE TIME EXAMPLES

Assume the current time is May 9 17:06 2004:

1,8 = May 1 00:00 2004 to May 8 23:59 2004

,4 = the time of the first occurrence to May 4 23:59 2004

6 = May 6 00:00 2004 to May 6 23:59 2004

2/ = Feb 1 00:00 2004 to Feb 28 23:59 2004

/12: = May 9 12:00 2004 to May 9 12:59 2004

2/1 = Feb 1 00:00 2004 to Feb 1 23:59 2004

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 2004

2001/12/31,2004/5/1 = from Dec 31, 2001 00:00:00 to May 1st 2004 23:59:59

RELATIVE TIME EXAMPLES

.-9, = April 30 17:06 2004 to the current time

,.-2/ = the time of the first occurrence to Mar 7 17:06 2004

.-9,.-2 = nine days ago to two days ago (April 30, 2004 17:06 to May 7, 2004 17:06)

[ Top ]

[ Platform Documentation ] [ Title ] [ Contents ] [ Previous ] [ Next ] [ Index ]

Date Modified: February 24, 2004
Platform Computing: www.platform.com

Platform Support: support@platform.com
Platform Information Development: doc@platform.com

Copyright © 1994-2004 Platform Computing Corporation. All rights reserved.