Difference: BasicUsage (8 vs. 9)
Revision 92008-11-21 - AndrasLaszlo
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
How to submit simple jobs onto the Grid | ||||||||
| Line: 32 to 30 | ||||||||
setenv GLITE_WMSUI_CONFIG_VAR /some_directory/glite_wms.conf (for tcsh). | ||||||||
| Changed: | ||||||||
| < < | The default version of the file glite_wms.conf may be obtained from /opt/glite/etc/ on any UI machine. (However, the prefix /opt may be different on various platforms, if non-standard installation directory is used for GLite.) | |||||||
| > > | The default version of the file glite_wms.conf may be obtained from /opt/glite/etc//glite_wms.conf on any UI machine. (However, the prefix /opt may be different on various platforms, if non-standard installation directory is used for GLite.) | |||||||
Log onto the Grid (get authenticated on the Grid) | ||||||||
| Line: 42 to 40 | ||||||||
> grid-proxy-init -valid 04:00 This is the same, but the authentication will expire in 4 hours. The default (and maximum) lifetime is 12 hours. | ||||||||
| Changed: | ||||||||
| < < | If you are member of more then one VO, you can choose between them by using the voms-proxy-init for logging in, instead of grid-proxy-init command. E.g.: | |||||||
| > > | If you are member of more then one VO, you can choose between them by using the glite-voms-proxy-init for logging in, instead of grid-proxy-init command. E.g.: | |||||||
| Changed: | ||||||||
| < < | > voms-proxy-init -voms hungrid Or: | |||||||
| > > | > glite-voms-proxy-init -voms hungrid Or: | |||||||
| Changed: | ||||||||
| < < | > voms-proxy-init -voms hungrid -valid 04:00
To get information on your user proxy, you can use the commands grid-proxy-info or voms-proxy-info -all. You can destroy your user proxy by grid-proxy-destroy or voms-proxy-destroy. | |||||||
| > > | > glite-voms-proxy-init -voms hungrid -valid 04:00 | |||||||
| Added: | ||||||||
| > > | To get information on your user proxy, you can use the commands grid-proxy-info or glite-voms-proxy-info -all. You can destroy your user proxy by grid-proxy-destroy or glite-voms-proxy-destroy. | |||||||
Get your jobs authenticated on the Grid | ||||||||
| Line: 105 to 101 | ||||||||
Once you prepared the JDL file, you can look for the available queues, which are capable of running your job, by the command:
> glite-wms-job-list-match --vo your_vo testjob.jdl | ||||||||
| Changed: | ||||||||
| < < | This will return a list of Grid queues (computing elements), which are capable of executing your job. | |||||||
| > > | This will return a list of Grid queues (computing elements), which are capable of executing your job. | |||||||
The job can be submitted by the command:
> glite-wms-job-submit --vo your_vo -a testjob.jdl | ||||||||
| Changed: | ||||||||
| < < |
This will return a sURL address, which is a unique identifier of your job, which shall be denoted by jobID in the followings. | |||||||
| > > | This will return a sURL address, which is a unique identifier of your job, which shall be denoted by jobID in the followings. | |||||||
The status of the job can be viewed by:
> glite-wms-job-status jobID | ||||||||
| Changed: | ||||||||
| < < | This will return the current status of your job. | |||||||
| > > | This will return the current status of your job. | |||||||
If your job has failed to be ran by the Grid system, the logging may be retrieved by:
> glite-wms-job-logging-info jobID | ||||||||
| Changed: | ||||||||
| < < | This will return the logging info on your job. A convenient way to find out failure reasons is: | |||||||
| > > | This will return the logging info on your job. A convenient way to find out failure reasons is: | |||||||
| > glite-wms-job-logging-info -v 3 jobID | grep "reason" | uniq | ||||||||
| Changed: | ||||||||
| < < |
This will return all the available most detailed logging info on your job, and shall print lines containing the string "reason", furthermore shall suppress multiple printing of consecutive identical lines. | |||||||
| > > | This will return all the available most detailed logging info on your job, and shall print lines containing the string "reason", furthermore shall suppress multiple printing of consecutive identical lines. | |||||||
If your job has properly finished, you can retrieve the outputs by the command:
> glite-wms-job-output jobID | ||||||||
| Changed: | ||||||||
| < < |
This will retrieve the content of the OutputSandbox into the directory /tmp/jobOutput/yourusername_jobID. It is also possible to specify some other directory name by the --dir switch. | |||||||
| > > | This will retrieve the content of the OutputSandbox into the directory /tmp/jobOutput/yourusername_jobID. It is also possible to specify some other directory name by the --dir switch. | |||||||
For further information, look at the man pages of the above commands, and maybe also to the man pages of other glite-wms- commands. For further references on simple job submission, see https://edms.cern.ch/file/722398//gLite-3-UserGuide.pdf . Also a complete description of the JDL language is available there. | ||||||||
View topic | History: r15 < r14 < r13 < r12 | 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