The Platform Console allows you to submit and monitor jobs, and provides access to job reports. You can choose to submit jobs directly from the Platform Console, or through a separate workload management application (for example, Platform Lava or Platform LSF). After logging on to the Platform Console, you can monitor the jobs you submitted through either the Console or a workload management application.
There are a number of standard interfaces in the Platform Console through which you can submit jobs. A generic interface is provided, along with several pre-configured and customizable interfaces (such as Fluent, LS-DYNA, ABAQUS, ANSYS, Nastran, and EnginFrame).
The Generic interface allows you to submit LSF jobs via a web browser. The Generic interface cannot be customized.
Submit jobs by running a binary or script as a job command (for example, /bin/sleep 10). Use this interface to specify most bsub options including input, output, and error files, notification and queue details, processor and resource requirements, and host and job limits.
By default, the Platform Console provides some templates for several popular job submission interfaces. You can add new ones, and customize existing interfaces to suit your workload submission requirements. Included interfaces are briefly described here.
This is an application-specific interface for job submission. Fluent must be installed to use this interface. The out-of-box interface can be customized.
Submit CAT, DAT, and journal files that reside locally or on a server, and provide parameters and job options that are specific to the Fluent application, such as time stamp and iteration number.
To integrate with the actual Fluent application, you must change the FLUENT_CMD to point to the application For example:
This is an application-specific interface for job submission. LS-DYNA must be installed to use this interface. The out-of-box interface can be customized.
Submit d3dump files that reside locally or on a server, point to the input deck, and provide parameters and job options that are specific to the LS-DYNA application.
To integrate with the actual LS-DYNA application, you must change the DYNA_CMD to point to the application For example:
DYNA_CMD="$DYNA_TOP/binaries/ls_dyna/linux/$VERSION"
This is an application-specific interface for job submission. ABAQUS must be installed to use this interface. The out-of-box interface can be customized.
Submit INP, restart, and user files that reside locally or on a server, and provide parameters and job options that are specific to the ABAQUS application.
To integrate with the actual ABAQUS application, you must change the ABAQUS_CMD to point to the application For example:
ABAQUS_CMD="/pcc/app/abaqus/6.5.3/x86-64/Commands/abaqus"
This is an application-specific interface for job submission. ANSYS must be installed to use this interface. The out-of-box interface can be customized.
Submit computing (.db), load case, and TXT files that reside locally or on a server, and provide parameters that are specific to the ANSYS application, such as the parallel type and MPP solver.
To integrate with the actual ANSYS application, you must change the ANSYS_CMD to point to the application For example:
ANSYS_CMD="/pcc/app/ansys_inc/v110/ansys/bin/ansys110"
This is an application-specific interface for job submission. Nastran must be installed to use this interface. The out-of-box interface can be customized.
Point to an input deck and provide parameters that are specific to the Nastran application.
To integrate with the actual Nastran application, you must change the NASTRAN_CMD to point to the application For example:
NASTRAN_CMD="/pcc/app/msc/nastran/2005/bin/msc2005 nastran"