LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 373
Working with Application Profiles
Remove an
application profile
Prerequisites: Before removing an application profile, make sure there are no
pending jobs associated with the application profile.
If there are jobs in the application profile, use bmod -app to move pending jobs to
another application profile, then remove the application profile. Running jobs are
not affected by removing the application profile associated with them,
NOTE: You cannot remove a default application profile.
1 Log in as the LSF administrator on any host in the cluster.
2 Run
bmod -app to move all pending jobs into another application profile.
If you leave pending jobs associated with an application profile that has been
removed, they remain pending wit h the pending reason
Specified application profile does not exist
3 Edit lsb.applicationss and remove or comment out the definition for the
application profile you want to remove.
4 Save the changes to
lsb.applications.
5 Run badmin reconfig to reconfigure mbatchd.
Define a default application profile
Define a default application profile that is used when a job is submitted without
specifying an application profile,
1 Log in as the LSF administrator on any host in the cluster.
2 Set
DEFAULT_APPLICATION in lsb.params to the name of the default
application profile.
DEFAULT_APPLICATION=catia
3 Save the changes to lsb.params.
4 Run
badmin reconfig to reconfigure mbatchd.
Adding an application profile does not affect pending or running jobs.
Specify successful application exit values.
Use SUCCESS_EXIT_VALUES to specify a list of exit codes that will be considered
as successful execution for the application.
1 Log in as the LSF administrator on any host in the cluster.
2 Set
SUCCESS_EXIT_VALUES to specify a list of job success exit codes for the
application.
SUCCESS_EXIT_VALUES=230 222 12
3 Save the changes to lsb.applications.