The Application page provides an interface for manipulating the application and its requirements. It consists of three sections: the Application, the POSIX Application and Additional POSIX Application elements.
This section allows to manipulate the Application element of a JSDL document. This elememt is a generic container that holds specific application definitions, such as POSIX applications defined in the POSIX Application section.
An Application Name is optional and defines the name of the application, independantly of the location of it's executable. The Application Name is of type "String".
An Application Version is optional and defines the version of the application, that is to be executed. If left empty this means that any version of the application can be executed. The Application Version is of type "String".
An Application Description is optional is optional and provides, human readable, description about the application. The Application Version is of type "String".
This section allows to manipulate the POSIXApplication element of a JSDL document. This elememt is an extension to the JSDL Application element and it's used to describe POSIX style applications.
A POSIX Application is optional and defines the name of the POSIX Application.
An Executable is optional and specifies the executable of the application to be executed. If not specified along with the ApplicationName element above then this could suggest a null or a data staging job.
An Argument is optional and provides argument for the application to be executed. In the Arguments list one or more arguments can be specified for the application. Arguments are of type "String".
Press Add... for opening an input dialog to insert an argument. The File System Name specifies the name of a file system. This name of a file system is defined by the FileSystem element of a JSDL document. Using the JSDL editor, you can define the file system name in the File System section of Resources Page.
Press Edit... to change the details of the selected argument. Press Remove to remove the selected argument.
A Standard Input File is optional and specifies the standard input of the application to be executed. The input filename is relative to the working directory or the file system name if this is specfied. The Standard Input File is of type "String".
A Standard Output File is optional and specifies the standard output of the application to be executed. The output filename is relative to the working directory or the file system name if this is specfied. The Standard Output File is of type "String".
A Standard Error File is optional and specifies the standard error of the application to be executed. The standard error filename is relative to the working directory or the file system name if this is specfied. The Standard Error File is of type "String".
An Environmental Variable is optional and defines the name and value of an environment variable that needs to be specified for the execution of the job on the consuming system.
Press Add... for opening an input dialog to insert an environmental variable. The Environmental Variable name and value are of type "String". Press Edit... to change the details of the selected environmental variable. Press Remove to remove the selected variable.
This section allows you to provide additional information about the requirements of the POSIX style application to be executed.
A Working Directory is optional and specifies the starting directory required by the job to execute. The Working Directory if of type "String".
A Wall Time Limit is optional and specifies in seconds the limit of the application execution duration. The Wall Time Limit is of type "Non-Negative Integer".
A File Size Limit is optional and specifies in bytes the maximum size of any file related to the job. The File Size Limit is of type "Non-Negative Integer".
A Core Dump Limit is optional and specifies in bytes the maximum size of core dumps a job may create. The Core Dump Limit is of type "Non-Negative Integer".
A Data Segmentation Limit is optional and specifies in bytes the maximum limit of data segments. The Data Segmentation Limit is of type "Non-Negative Integer".
A Locked Memory Limit is optional and specifies in bytes the maximum amount of physical memory the job is allowed to lock. The Locked Memory Limit is of type "Non-Negative Integer".
A Memory Limit is optional and specifies in bytes the maximum amount of physical memory the job should use when executing. The Memory Limit is of type "Non-Negative Integer".
An Open Descriptor Limit is optional and specifies the maximum amount of open file-descriptors (files, pipes, sockets) the job can have. The Open Descriptors Limit is of type "Non-Negative Integer".
A Pipe Size Limit is optional and specifies in bytes the maximum size of pipelines created by the job processing. The Pipe Size Limit is of type "Non-Negative Integer".
A Stack Size Limit is optional and specifies in bytes the maximum size of the execution stack. The Stack Size Limit is of type "Non-Negative Integer".
A CPU Time Limit is optional and specifies in seconds the maximum number of CPU time seconds the job is allowed to consume. The Stack Size Limit is of type "Non-Negative Integer".
A Process Count Limit is optional and specifies the maximum number of processes the job can spawn. The Process Count Limit is of type "Non-Negative Integer".
A Virtual Memory Limit is optional and specifies in bytes the maximum amount of virtual memory the job can allocate. The Virtual Memory Limit is of type "Non-Negative Integer".
A Thread Count Limit is optional and specifies the maximum amount of threads the job is allowed to create. The Thread Count Limit is of type "Non-Negative Integer".
A User Name is optional and specifies the user name to be used when executing the application. The User Name is of type "String".
A Group Name is optional and specifies the group name to be used when executing the application. The Group Name is of type "String".