bapp

Displays information about application profile configuration.

Synopsis

bapp [-alloc] [-l | -w] [application_profile ...]

bapp [-h | -V]

Description

Displays information about application profiles that are configured in the lsb.applications file.

Returns application name, task statistics, and job state statistics for all application profiles.

In the LSF multicluster capability, returns the information about all application profiles in the local cluster.

Returns job slot statistics if the -alloc option is used.

CPU time is normalized.

Options

-alloc

Shows counters for slots in RUN, SSUSP, USUSP, and RSV state. The slot allocation is different depending on whether the job is an exclusive job or not.

-w

Wide format. Fields are displayed without truncation.

-l

Long format with additional information.

Displays the following additional information about the application profile:

Description
Profile characteristics and statistics
Parameters
Resource usage limits
Associated commands
Binding policy
NICE value
Job controls
Pending time limits
Eligible pending time limits
(As of Fix Pack 4) APS priority factors

application_profile ...

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 tasks for all jobs that are currently held in the application profile. The total includes tasks in pending, running, and suspended jobs.
If the -alloc option is used, total is the sum of the counters for RUN, SSUSP, USUSP, and RSV states.
PEND: The number of tasks for all pending jobs in the application profile. If used with the -alloc option, output is 0, because pending jobs do not have slot allocation.
RUN: The number of tasks for all running jobs in the application profile. If the -alloc option is used, the total is allocated slots for the jobs in the application profile.
SUSP: The number of tasks for all suspended jobs in the application profile. If the -alloc option is used, the total is allocated slots for the jobs in the application profile.

Long output format with the -l option

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

Description

A description of the typical use of the application profile.

PARAMETERS/STATISTICS

SSUSP: The number of tasks for all jobs in the application profile that are suspended by LSF because of load levels or run windows.
USUSP: The number of tasks for all jobs in the application profile that are suspended by the job submitter or by the LSF administrator.
RSV: The number of tasks that reserve slots for pending jobs in the application profile.
ENV_VARS: The name-value pairs that are defined by the application-specific environment variables.

Per-job resource usage limits

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

The following per-job limits are supported:

CPULIMIT: The maximum CPU time a job can use, in minutes, relative to the CPU factor of the named host. The 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 the LSF_UNIT_FOR_LIMITS parameter in the lsf.conf file 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 that are allocated to a job.
SWAPLIMIT: The swap space limit that a job can use.
By default, the limit is shown in KB. Use the LSF_UNIT_FOR_LIMITS parameter in the lsf.conf file to specify a larger unit for display (MB, GB, TB, PB, or EB).
TASKLIMIT: The maximum number of tasks that are allocated to a job.
THREADLIMIT: THREADLIMITThe maximum number of concurrent threads that are allocated to a job.

Per-process resource usage limits

The following UNIX per-process resource limits are supported:

CORELIMIT: The maximum size of a core file.
By default, the limit is shown in KB. Use the LSF_UNIT_FOR_LIMITS parameter in the lsf.conf file 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 limit 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 limit 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 the LSF_UNIT_FOR_LIMITS parameter in the lsf.conf file 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 the following values: NONE, BALANCE, PACK, ANY, USER, or USER_CPU_LIST.

bapp -l app1
APPLICATION NAME: app1
 -- test processor binding options
...
PARAMETERS:
BIND_JOB: ANY

For compatibility with an earlier versions, the bapp -l command displays Y or N if the BIND_JOB parameter 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 elapses.

CHKPNT_PERIOD

The checkpoint period in minutes. The running job is check-pointed 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 is to 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 job-based pre-execution command for the application profile. The PRE_EXEC command runs on the execution host before the job that is 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 job-based post-execution command for the application profile. The POST_EXEC command runs on the execution host after the job finishes.

HOST_PRE_EXEC

The host-based pre-execution command for the application profile. The HOST_PRE_EXEC command runs on all execution hosts before the job that is associated with the application profile is dispatched to the execution hosts. If a job-based pre-execution PRE_EXEC command was defined at the queue-level/application-level/job-level, the HOST_PRE_EXEC command runs before the PRE_EXEC command of any level. The host-based pre-execution command cannot be run on Windows systems.

HOST_POST_EXEC

The host-based post-execution command for the application profile. The HOST_POST_EXEC command runs on the execution hosts after the job finishes. If a job-based post-execution POST_EXEC command was defined at the queue-level/application-level/job-level, the HOST_POST_EXEC command runs after the POST_EXEC command of any level. The host-based post-execution command cannot be run on Windows systems.

LOCAL_MAX_PREEXEC_RETRY_ACTION

The action to take on a job when the number of times to attempt its pre-execution command on the local cluster (the value of the LOCAL_MAX_PREEXEC_RETRY parameter) is reached.

JOB_INCLUDE_POSTPROC

If the JOB_INCLUDE_POSTPROC=Y parameter is defined, 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, the sbatchd daemon reports that post-execution 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 re-queued.

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 before the batch job, taking the batch job file as an input argument. All jobs that are submitted to the application profile are run through the job starter, which is used to create a specific execution environment before LSF processes the jobs themselves.

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 a pre-emptable job can be preempted.

MAX_TOTAL_TIME_PREEMPT

The configured maximum total preemption time (minutes) after which preemption cannot take place.

NICE

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

Current working directory (CWD) information

JOB_CWD: The current working directory for the job in the application profile. The path can be absolute or relative to the submission directory, and includes dynamic patterns.
JOB_CWD_TTL: The time to live for the current working directory for a job. LSF cleans the created CWD after a job finishes based on the TTL value.

JOB_SIZE_LIST

A list of job sizes (number of tasks) allowed on this application, including the default job size that is assigned if the job submission does not request a job size. Configured in the lsb.applications file.

PEND_TIME_LIMIT

The pending time limit for a job in the application profile. If a job remains pending for longer than this specified time limit, IBM® Spectrum LSF RTM (LSF RTM) triggers the alarm and other actions. Configured in the lsb.applications file.

ELIGIBLE_PEND_TIME_LIMIT

The eligible pending time limit for a job in the application profile. If a job remains in an eligible pending state for longer than this specified time limit, IBM Spectrum LSF RTM (LSF RTM) triggers the alarm and other actions. Configured in the lsb.applications file.

PRIORITY

The APS priority factor for the application profile. PRIORITY is defined by the PRIORITY parameter in the configuration file lsb.applications.