WMSX examples

Simple job

Job submission with edg-job-submit is not very straightforward, as the generated job identifier has to be stored, and then the job output retrieval directory has to be resolved by this identifier. To save you from this typing exercise, the WMSX is capable of managing the output retrieval directory for simple jobs.

You can find a prepared example for this task here: . To submit the example job, type the following commands.

Get the tarball:

> tar  -xzf  simplejob.tar.gz
> rm  -f  simplejob.tar.gz
> cd  simplejob

Log onto the Grid:

> voms-proxy-init  -voms your_vo
# If your job is expected to be long, also get long term authentication:
> myproxy-init  -n

Submit the job:

> wmsx-provider.sh  workdir
> wmsx-requestor.sh  -vo your_vo
# If your job is expected to be long, also make the WMSX remember your grid password:
> wmsx-requestor.sh  -remembergrid
# If your job is expected to be long and you are working on AFS, also make the WMSX remember your AFS password:
> wmsx-requestor.sh  -rememberafs
> wmsx-requestor.sh  -j simplejob.jdl  -r workdir/out/resultdir
# Or, if JobType = "Interactive" was set in the JDL file, say instead:
> wmsx-requestor.sh  -j simplejob.jdl  -r workdir/out/resultdir  -o workdir/out/StdOutFile

Your results shall be retrieved into the directory workdir/out/resultdir. If your job was interactive (JobType = "Interactive" was set in the JDL file), the file containting StdOut / StdErr shall be workdir/out/StdOutFile, which shall be updated on the fly. Remark: if the JobType = "Interactive" was set, the fields StdInput, StdOutput and StdError cannot be set in the JDL file.

If you are finished, you can stop WMSX, and destroy your Grid authentications:

> wmsx-requestor.sh  -k
# If myproxy-init was used, i.e. for long term jobs:
> myproxy-destroy
> voms-proxy-destroy

Mass submission of independent jobs: simple parameter scan

Mass submission of chained jobs: parameter scan with chained jobs

-- AndrasLaszlo - 28 Nov 2007