| |
| META TOPICPARENT |
name="WmsxSoftware" |
WMSX |
| |
-
-f - Check if the provider is running.
-
-k - Kill provider.
|
|
>
> |
-
-backend yourbackend - With this, you may specify the job submission backend. Here,
yourbackend may be any of edg, glite, glitewms, worker. Default backend is glitewms.
|
| |
-
-rememberafs - Will ask for your AFS password and renew AFS tokens until provider is running. It only works if you do not quit the interactive terminal (when you quit interactive session, AFS automatically deletes your tokens).
-
-forgetafs - Forget the AFS password.
-
-vo yourvo - Set the VO for all future job submissions to
yourvo.
-
-remembergrid - Will ask for your Grid password and renew the Grid tokens until there are no more managed jobs. If your grid key files (
userkey.pem and usercert.pem, typically located under ~/.globus) are located on AFS space, you should use -rememberafs, and should not quit the interactive terminal. If this is not feasible, copy the .globus directory to some local disk space, and point the environmental variables X509_USER_CER and X509_USER_KEY to the absolute path of usercert.pem and userkey.pem, respectively.
|
|
<
< | The possible job submission procedures ars described in the next sections. |
>
> | The possible job submission procedures are described in the next sections. |
| |
Submission of single jobs with traditional JDL files |
| |
-
-name runname - Give the name
runname to this execution run (optional). It is used as a subdirectory under the working directory of the provider to distinguish between different ArgList submissions.
-
-n nmaxjobs - Set the maximal number of concurrently running jobs to
nmaxjobs (optional).
|
|
<
< | The word COMMAND refers to a WMSX JDL file (not a traditional JDL file), named COMMAND.jdl, which describes your job. If the COMMAND.jdl is not present, default job specifications are assumed, which shall be discussed in the followings. |
>
> | The word COMMAND refers to a WMSX JDL file (not a traditional JDL file), named COMMAND.wjdl, which describes your job. If the COMMAND.wjdl is not present, default job specifications are assumed, which shall be discussed in the followings. |
| |
The outputs of the jobs are written into generated directories under the out directory of the specified working directory of the provider.
WMSX JDL files |
|
<
< | For each COMMAND in the ArgList file, there may be a JDL file COMMAND.jdl, to customize the properties of your job. |
>
> | For each COMMAND in the ArgList file, there may be a WMSX JDL file COMMAND.wjdl, to customize the properties of your job. |
| | The structure of a WMSX JDL file is similar to traditional JDL files, however the supported variables are only:
-
JobType - If this variable is set to
"Interactive", the jobs will be run as interactively in the sense that the StdOut / StdError is retrieved on-the-fly, so you are able to see what your job is currently doing. If not set, the job is not interactive by default.
|
| |
-
Software - List of software that must be present (executable) on the target machine. The special key
"AFS" requires and checks AFS presence. E.g.: Software = {"AFS", "g++"};. If not set, defaults to empty.
-
Requirements - Extra queue requirements, like in a traditional JDL file. If not set, defaults to empty.
|
|
<
< | If the JDL file is not present, the above default values are assumed (i.e. the tarball has to have the name COMMAND.tar.gz etc.). |
>
> | If the WMSX JDL file is not present, the above default values are assumed (i.e. the tarball has to have the name COMMAND.tar.gz etc.). |
| |
In the followings, things are more easily explained if the notion of AbsCOMMAND is introduced: this is simply the full path to the file COMMAND.jdl file (or if not present, to the the COMMAND.tar.gz file), without the ".jdl" extension (or without the ".tar.gz" extension). |
