LSB_ESUB_METHOD

Syntax

LSB_ESUB_METHOD="application_name [application_name] ..."

Description

Specifies a mandatory esub or epsub that applies to all job submissions. LSB_ESUB_METHOD lists the names of the application-specific esub or epsub executables used in addition to any executables specified by the bsub -a option.

For example, LSB_ESUB_METHOD="dce fluent" runs LSF_SERVERDIR/esub.dce and LSF_SERVERDIR/esub.fluent for all jobs submitted to the cluster, then runs LSF_SERVERDIR/epsub.dce and LSF_SERVERDIR/epsub.fluent after the jobs are submitted. These esubs and epsubs define, respectively, DCE as the mandatory security system and FLUENT as the mandatory application for all jobs. However, the purpose of an esub program might be different than its corresponding epsub program because esub is run before the job is submitted, while epsub is run after the job is submitted.

LSB_ESUB_METHOD can also be defined as an environment variable.

The value of LSB_ESUB_METHOD must correspond to an actual esub or epsub file. For example, to use LSB_ESUB_METHOD=fluent, at least one of the esub.fluent file or the epsub.fluent file must exist in LSF_SERVERDIR.

The name of the esub or epsub program must be a valid file name. Valid file names contain only alphanumeric characters, underscore (_) and hyphen (-).

Restriction: The name esub.user is reserved. Do not use the name esub.user for an application-specific esub. This also applies to the epsub.user file.

The parent esub (mesub) uses the name you specify to invoke the appropriate esub or epsub program. The esub and esub.application_name programs (or epsub and epsub.application_name programs) must be located in LSF_SERVERDIR.

LSF does not detect conflicts based on esub or epsub names. For example, if LSB_ESUB_METHOD="openmpi" and bsub -a pvm is specified at job submission, the job could fail because these esubs define two different types of parallel job handling.

Default

Not defined. LSF does not apply a mandatory esub to jobs submitted to the cluster.