Choosing a Command Set
edg-job-* — deprecated
glite-job-* — doesn't work anymore at DESY
glite-wms-job-* — preferred
Checking the JDL File
glite-wms-job-list-match -a foo.jdl
Checks the syntax of your JDL file and prints out a list of Computing Elements to which this job could be sent (depending on Requirements and possibly InputData job attributes). Strictly speaking, the syntax check is only a side effect, but it's nevertheless very useful!
Don't forget the option “-a” for automatic proxy delegation — whatever that means.
Submitting a Job
glite-wms-job-submit -a -o foo.jid foo.jdl
The option “-o” will save the ID of the submitted job to a text file instead of just printing it out on the terminal. You don't have to use that option, but it comes very handy together with the option “-i” of the following commands. If the file already exists, the ID of the new job will be appended at the end, i. e. you can manage more than one job with a single job ID file.
Again, you need “-a” for automatic proxy delegation to submit a job.
Checking the Job Status
glite-wms-job-status -i foo.jid
The option “-i” takes the name of a file which was produced by the option “-o” of glite-wms-job-submit. You can also provide the job ID on the command line directly.
Retrieving the Job Output
glite-wms-job-output --dir . -i foo.jid
Fetches the files which were specified in the OutputSandbox job attribute and stores them on your local disk. Depending on your configuration, you may have to provide the option “--dir” to specifiy a destination path for the files (the default is currently /tmp). Again, you can also specify the job ID directly on the command line if you don't have a job ID file.
Cancelling a Job
glite-wms-job-cancel -i foo.jid
Cancels the specified job. Be aware that you won't be able to retrieve any output files — if the job has already started running, the executable on the worker node will simply be killed and all data on the worker node will be discarded.
Getting Detailed Logging Information
glite-wms-job-logging-info -v 2 -i foo.jid
Displays a detailed list of actions which took place on the different servers which are involved in job management. The option “--v” controls the verbosity level. Level 1 is not often too useful, level 2 may contain error messages which your administrator will understand, and level 3 will usually swamp you with enormous amounts of information.