Download GLITE 3.2 USER GUIDE

The commands to obtain a job’s current status or its state history obtain the requested information from the
Logging and Bookkeeping (LB) service further described below.
The following table summarizes the main commands commands with their most commonly used options, and
the use of these commands will be described in the following sections.
Function
gLite WMS
Submit a job
glite-wms-job-submit [-d
delegID] [-a] [-o joblist]
jdlfile
glite-wms-job-status [-v
verbosity] [-i joblist]
jobIDs
glite-wms-job-logging-info
[-v verbosity] [-i joblist]
jobIDs
glite-wms-job-output [-dir
outdir] [-i joblist] jobIDs
glite-wms-job-cancel [-i
joblist] jobID
glite-wms-job-list-match
[-d delegID] [-a] jdlfile
glite-wms-job-delegate-proxy
-d delegID
See job status
See job logging
information
Retrieve job output
Cancel a job
List available resources
Delegate proxy
6.3.1. Single Job Submission
To submit a job to the WLCG/EGI Grid, the user must have a valid proxy certificate in the User Interface machine
(as described in Chapter 4) and use a command like this, here shown in its simplest form:
glite-wms-job-submit -a jdlfile
where jdlfile is a file containing the job description, usually with extension .jdl. The -a option for the gLite
command is necessary to automatically delegate a user proxy to the WMProxy server (see later).
Example 6.3.1.1
(Submitting a simple job)
Create a file test.jdl with this content:
Executable = "/bin/hostname";
StdOutput = "std.out";
StdError = "std.err";
OutputSandbox = {"std.out","std.err"};
It describes a simple job that will execute /bin/hostname. Standard output and standard error are redirected
to the files std.out and std.err respectively; the OutputSandbox attribute ensures that they are transferred back
to the User Interface when the user asks for the output after the job has finished.
Now, submit the job via gLite WMS by doing:
CERN-LCG-GDEIS-722398
Manuals Series
Page 62