next up previous contents
Next: Overview of JDL Basic Up: Job Examples Previous: Job Examples   Contents


JOB hnam: JDL file only

It is a good practice, even for experienced users, to have a small set of simple jobs to test the Grid. The first example is made only of the hnam.jdl JDL file:


JDL File hnam.jdl
Executable = "/bin/hostname";
StdOutput = "hnam.out";
StdError = "hnam.err";
OutputSandbox = {"hnam.out","hnam.err"};


The user should be able to submit the job without options:
$ edg-job-submit -o JID hnam.jdl

The only option I suggest is the output file JID to store the URL that allows job status inquiry and output retrieval. In case of success edg-job-submit prints the DNS name and port of the LB and the NS (i.e. RB in EDG1.4 terminology), the job URL and the output file name and location. Job status in inquired by:
$ edg-job-status -i JID
that prints job status (ex. Ready, Running, Done) and the CE that supports the WN where the job is run. The CE is printed in the destination field:
Destination: hotdog46.fnal.gov:2119/jobmanager-pbs-long

When the job is completed (status = Done), the output is collected with:
$ edg-job-get-output -i JID
that prints the destination directory:
/tmp/jobOutput/mZbah04bTXed9Su89W6z1A
the directory holds the OutputSandbox files defined in the JDL. In this example the output files are hnam.err and hnam.out. File hnam.err should be empty while hnam.out lists the WN DNS name as shown in the following examples:


Examples of hnam.jdl OutputSandbox
$ cd /tmp/jobOutput/5ObaQux3VuLBvMsL1QDo3g
$ cat hnam.out
grid004.ct.infn.it
$ cat /tmp/jobOutput/mZbah04bTXed9Su89W6z1A/hnam.out
hotdog49.fnal.gov


The examples report output produced by jobs directed to different resource brokers (NS).


next up previous contents
Next: Overview of JDL Basic Up: Job Examples Previous: Job Examples   Contents
luvisetto 2003-12-17