Displays information about application profile configuration.
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.
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, and job controls.
Displays information about the specified application profile.
Displays the following fields:
The name of the application profile. Application profiles are named to correspond to the type of application that usually runs within them.
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.
The number of job slots used by pending jobs in the application profile.
The number of job slots used by running jobs in the application profile.
The number of job slots used by suspended jobs in the application profile.
In addition to the above fields, the -l option displays the following:
A description of the typical use of the application profile.
The number of job slots in the application profile allocated to jobs that are suspended by LSF because of load levels or run windows.
The number of job slots in the application profile allocated to jobs that are suspended by the job submitter or by the LSF administrator.
The number of job slots in the application profile that are reserved by LSF for pending jobs.
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 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.
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).
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).
The maximum number of concurrent processes allocated to a job.
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).
The maximum number of concurrent threads allocated to a job.
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).
The maximum size of the data segment of a process, in KB. This restricts the amount of memory a process can allocate.
The maximum wall clock time a process can use, in minutes. RUNLIMIT is scaled by the CPU factor of the execution host.
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).
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 backwards compatibility, bapp -l displays "Y" or "N" if BIND_JOB is defined with those values in the application profile.
The checkpoint directory, if automatic checkpointing is enabled for the application profile.
The initial checkpoint period in minutes. The periodic checkpoint does not happen until the initial period has elapsed.
The checkpoint period in minutes. The running job is checkpointed automatically every checkpoint period.
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.
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).
The post-execution command for the application profile. The POST_EXEC command runs on the execution host after the job finishes.
If JOB_INCLUDE_POSTPROC= Y, post-execution processing of the job is included as part of the job.
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), and kills the process group of the job’s post-execution processes.
Jobs that exit with these values are automatically requeued.
Resource requirements of the application profile. Only the hosts that satisfy these resource requirements can be used by the application profile.
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 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.
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.
The configured actions for the resume job control.
The configured actions are displayed in the format [action_type, command] where action_type is RESUME.
The configured actions for the suspend job control.
The configured actions are displayed in the format [action_type, command] where action_type is SUSPEND.
The configured actions for terminate job control.
The configured actions are displayed in the format [action_type, command] where action_type is TERMINATE.