bapp

Displays information about application profile configuration.

Synopsis

bapp [-l | -w] [application_profile_name ...]
bapp [-h | -V]

Description

Displays information about application profiles configured in lsb.applications.

Returns application name, job slot statistics, and job state statistics for all application profiles:

In MultiCluster, returns the information about all application profiles in the local cluster.

CPU time is normalized.

Options

-w

Wide format. Fields are displayed without truncation.

-l

Long format with additional information.

Displays the following additional information: application profile description, application profile characteristics and statistics, parameters, resource usage limits, associated commands, binding policy, NICE value, and job controls.

application_profile_name ...

Displays information about the specified application profile.

-h

Prints command usage to stderr and exits.

-V

Prints product release version to stderr and exits.

Default output format

Displays the following fields:

APPLICATION_NAME

The name of the application profile. Application profiles are named to correspond to the type of application that usually runs within them.

NJOBS

The total number of job slots held currently by jobs in the application profile. This includes pending, running, suspended and reserved job slots. A parallel job that is running on n processors is counted as n job slots, since it takes n job slots in the application.

PEND

The number of job slots used by pending jobs in the application profile.

RUN

The number of job slots used by running jobs in the application profile.

SUSP

The number of job slots used by suspended jobs in the application profile.

Long output format (-l)

In addition to the above fields, the -l option displays the following:

Description

A description of the typical use of the application profile.

PARAMETERS/ STATISTICS
SSUSP

The number of job slots in the application profile allocated to jobs that are suspended by LSF because of load levels or run windows.

USUSP

The number of job slots in the application profile allocated to jobs that are suspended by the job submitter or by the LSF administrator.

RSV

The number of job slots in the application profile that are reserved by LSF for pending jobs.

Per-job resource usage limits

The soft resource usage limits that are imposed on the jobs associated with the application profile. These limits are imposed on a per-job and a per-process basis.

The possible per-job limits are:
CPULIMIT

The maximum CPU time a job can use, in minutes, relative to the CPU factor of the named host. CPULIMIT is scaled by the CPU factor of the execution host so that jobs are allowed more time on slower hosts.

MEMLIMIT

The maximum running set size (RSS) of a process.

By default, the limit is shown in KB. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify a larger unit for display (MB, GB, TB, PB, or EB).

MEMLIMIT_TYPE

A memory limit is the maximum amount of memory a job is allowed to consume. Jobs that exceed the level are killed. You can specify different types of memory limits to enforce, based on PROCESS, TASK, or JOB (or any combination of the three).

PROCESSLIMIT

The maximum number of concurrent processes allocated to a job.

PROCLIMIT

The maximum number of processors allocated to a job.

SWAPLIMIT

The swap space limit that a job may use.

By default, the limit is shown in KB. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify a larger unit for display (MB, GB, TB, PB, or EB).

THREADLIMIT

The maximum number of concurrent threads allocated to a job.

Per-process resource usage limits
The possible UNIX per-process resource limits are:
CORELIMIT

The maximum size of a core file.

By default, the limit is shown in KB. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify a larger unit for display (MB, GB, TB, PB, or EB).

DATALIMIT

The maximum size of the data segment of a process, in KB. This restricts the amount of memory a process can allocate.

FILELIMIT

The maximum file size a process can create, in KB.

RUNLIMIT

The maximum wall clock time a process can use, in minutes. RUNLIMIT is scaled by the CPU factor of the execution host.

STACKLIMIT

The maximum size of the stack segment of a process. This restricts the amount of memory a process can use for local variables or recursive function calls.

By default, the limit is shown in KB. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify a larger unit for display (MB, GB, TB, PB, or EB).

BIND_JOB

The processor binding policy for sequential and parallel job processes enabled in the application profile. Displays one of: NONE, BALANCE, PACK, ANY, USER, or USER_CPU_LIST.

For example:

bapp -l app1

APPLICATION NAME: app1
 -- test processor binding options
……
PARAMETERS:
BIND_JOB: ANY

For backwards compatibility, bapp -l displays "Y" or "N" if BIND_JOB is defined with those values in the application profile.

CHKPNT_DIR

The checkpoint directory, if automatic checkpointing is enabled for the application profile.

CHKPNT_INITPERIOD

The initial checkpoint period in minutes. The periodic checkpoint does not happen until the initial period has elapsed.

CHKPNT_PERIOD

The checkpoint period in minutes. The running job is checkpointed automatically every checkpoint period.

CHKPNT_METHOD

The checkpoint method.

MIG

The migration threshold in minutes. A value of 0 (zero) specifies that a suspended job should be migrated immediately.

Where a host migration threshold is also specified, and is lower than the job value, the host value is used.

PRE_EXEC

The pre-execution command for the application profile. The PRE_EXEC command runs on the execution host before the job associated with the application profile is dispatched to the execution host (or to the first host selected for a parallel batch job).

POST_EXEC

The post-execution command for the application profile. The POST_EXEC command runs on the execution host after the job finishes.

JOB_INCLUDE_POSTPROC

If JOB_INCLUDE_POSTPROC= Y, post-execution processing of the job is included as part of the job.

JOB_POSTPROC_TIMEOUT

Timeout in minutes for job post-execution processing. If post-execution processing takes longer than the timeout, sbatchd reports that post-execution has failed (POST_ERR status). On UNIX, it kills the process group of the job’s post-execution processes. On Windows, only the parent process of the pre-execution command is killed when the timeout expires, the child processes of the pre-execution command are not killed.

REQUEUE_EXIT_VALUES

Jobs that exit with these values are automatically requeued.

RES_REQ

Resource requirements of the application profile. Only the hosts that satisfy these resource requirements can be used by the application profile.

JOB_STARTER

An executable file that runs immediately prior to the batch job, taking the batch job file as an input argument. All jobs submitted to the application profile are run via the job starter, which is generally used to create a specific execution environment before processing the jobs themselves.

CHUNK_JOB_SIZE

Chunk jobs only. Specifies the maximum number of jobs allowed to be dispatched together in a chunk job. All of the jobs in the chunk are scheduled and dispatched as a unit rather than individually.

RERUNNABLE

If the RERUNNABLE field displays yes, jobs in the application profile are automatically restarted or rerun if the execution host becomes unavailable. However, a job in the application profile is not restarted if you use bmod to remove the rerunnable option from the job.

RESUME_CONTROL

The configured actions for the resume job control.

The configured actions are displayed in the format [action_type, command] where action_type is RESUME.

SUSPEND_CONTROL

The configured actions for the suspend job control.

The configured actions are displayed in the format [action_type, command] where action_type is SUSPEND.

TERMINATE_CONTROL

The configured actions for terminate job control.

The configured actions are displayed in the format [action_type, command] where action_type is TERMINATE.

NO_PREEMPT_INTERVAL

The configured uninterrupted running time (minutes) that must pass before preemption is permitted.

MAX_TOTAL_TIME_PREEMPT

The configured maximum total preemption time (minutes) above which preemption is not permitted.

NICE

The relative scheduling priority at which jobs from the application execute.

See also

lsb.applications, lsb.queues, bsub, bjobs, badmin, mbatchd