Workload (Job) Management
Job submission
Jobs should always be submitted with a VOMS proxy.
- Basic information on how to submit your job with gLite WMS tools.
- How to submit your jobs with gLite WMS tools, with proxy delegation information.
(With the WMS through WMProxy, a proxy is delegated to the WMProxy and the proxy can be reused for all submitted jobs. This speeds up the job submission process.)
- Basic information on how to submit your job with EDG tools.
Data Management
*how to use storage element.
Other information
- Some potentially useful scripts/tricks/... in Jobscripts
- Advanced data access with gridftp (for processing files > 40MB)
- Information on grid APIs
- How to configure a User Interface on an existing machine, like a desktop, laptop or server
Workload Management Systems
Many Job Management systems (Workload Management System, WMS)coexist; each of them using different commands tools with similarities in the syntax and the functionalities.
- LCG-2 WMS, the LCG RB: giving access to LCG nodes.
- gLite RB via NS: (Using the gLite Resource Broker through the Network Server) obsolete.
It introduces new functionalities like VOMS proxy renewal and provides slightly better performances. It's replaced by the gLite WMS via WMProxy.
- gLite WMS via WMProxy: allows job submission in bulk and offers better job mangement performance.
It provides faster submission speed and is recommended for the submission of larger number of jobs.
| Function | LCG RB | gLite WMS via NS | gLite WMS via WMProxy |
| Submitting a job | edg-job-submit [-o joblist] jdlfile | glite-job-submit [-o joblist] jdlfile | glite-wms-job-submit [-o joblist] jdlfile |
| Job status | edg-job-status [-i joblist] jobIDs | glite-job-status [-i joblist] jobIDs | glite-wms-job-status [-i joblist] jobIDs |
| Logging Information | edg-job-get-logging-info [-i joblist] jobIDs | glite-job-logging-info [-i joblist] jobIDs | glite-wms-job-logging-info [-i joblist] jobIDs |
| Job output retrieval | edg-job-get-output [-dir outdir] [-i joblist] jobIDs | glite-job-output [-dir outdir] [-i joblist] jobIDs | glite-wms-job-output [-dir outdir] [-i joblist] jobIDs |
| Cancelling a job | edg-job-cancel [-i joblist] jobID | edg-job-cancel [-i joblist] jobID | glite-wms-job-cancel [-i joblist] jobID |
| List available resources | edg-job-list-match jdlfile | glite-job-list-match jdlfile | glite-wms-job-list-match jdlfile |
| Proxy delegation | glite-wms-job-delegate-proxy -d delegID |
All WMS describe job with a JDL (Job Description Langage) file
Job Status
The gLite WMS allow to have more information on the job status than the LCG RB. This is decribed in the table below where at higher verbosity level we can see more information.
| LCG RB | LCG RB | gLite RB and WMProxy | gLite RB and WMProxy |
| Verbosity level | Added information | Verbosity level | Added information |
| 0 (default) | Current status, status reason, destination, submission time | 0 | Current status |
| 1 | condorId, CPUtime, done_code, Network Server, owner | 1(default) | Status reason, destination, submission time |
| 2 | JDL, matched JDL, Condor JDL, state enter times | 2 | condorId, CPUtime, done_code, Network Server, owner |
| 3 | JDL, matched JDL, Condor JDL, state enter times |
When querying the status of a collection (a DAGID), the output of glite-wms-job-status will print also the jobIDs of all the jobs in the collection. The status of the single jobs can then be queried from their jobIDs.
