Difference: WmsxExample (2 vs. 3)

Revision 32007-11-29 - AndrasLaszlo

Line: 1 to 1

META TOPICPARENT	name="WmsxSoftware"

WMSX examples

Line: 30 to 30

> 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

Changed:

<
< > wmsx-requestor.sh -j simplejob.jdl -o workdir/out/StdOut -r workdir/out/resultdir

>
> > 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

Changed:

<
< Your results shall be retrieved into the directory workdir/out/resultdir, and the file containting StdOut / StdErr shall be workdir/out/StdOut, which is retrieved on the fly, if JobType = "Interactive" was set in your JDL file.

>
> 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

Changed:

<
< # If myproxy-init was used:

>
> # If myproxy-init was used, i.e. for long term jobs:

> myproxy-destroy
> voms-proxy-destroy

Line: 47 to 49

Mass submission of chained jobs: parameter scan with chained jobs

Deleted:

<
<

A real-life example

View topic | History: r18 < r17 < r16 < r15 | More topic actions...

Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback