basic_usage_of_grid_engine_commands
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| basic_usage_of_grid_engine_commands [2009/11/05 08:11] – 172.26.0.166 | basic_usage_of_grid_engine_commands [2010/05/22 14:19] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | == **Basic Usage of Grid Engine** == | + | ==== Basic Usage of Grid Engine |
| - | **qstat - Show job/queue status** | + | **qstat - //Show job/queue status//** |
| no arguments Show currently running/ | no arguments Show currently running/ | ||
| Line 10: | Line 10: | ||
| -U Shows current jobs by user | -U Shows current jobs by user | ||
| - | qhost - Show job/host status | + | **qhost - //Show job/host status//** |
| no arguments Show a table of all execution hosts and information about their configuration | no arguments Show a table of all execution hosts and information about their configuration | ||
| Line 17: | Line 17: | ||
| -q Shows detailed information on queues at each host | -q Shows detailed information on queues at each host | ||
| - | Using Grid Engine | + | ====Using Grid Engine==== |
| The main submit commands are qsub, qrsh and qtcsh. See the man pages for submit(1) and qtcsh(1) for more details. | The main submit commands are qsub, qrsh and qtcsh. See the man pages for submit(1) and qtcsh(1) for more details. | ||
| - | qsub - submit scripts | + | **qsub - submit scripts** |
| Started with no arguments it accepts input from STDIN (^D to send submit input) | Started with no arguments it accepts input from STDIN (^D to send submit input) | ||
| Line 31: | Line 31: | ||
| Example: | Example: | ||
| + | < | ||
| qsub -cwd -v SOME_VAR -o /dev/null -e /dev/null myjob.sh | qsub -cwd -v SOME_VAR -o /dev/null -e /dev/null myjob.sh | ||
| + | </ | ||
| In general, qsub is used for traditional batch submit, that is where I/O is directed to a file. Note that qsub only accepts shell scripts, not executable files. | In general, qsub is used for traditional batch submit, that is where I/O is directed to a file. Note that qsub only accepts shell scripts, not executable files. | ||
| Line 43: | Line 43: | ||
| Qrsh acts similar to the rsh command, except that a host name is not given. Instead, a shell script or an executable file is run, potentially on any node in the cluster. I/O is directed back to the submitter' | Qrsh acts similar to the rsh command, except that a host name is not given. Instead, a shell script or an executable file is run, potentially on any node in the cluster. I/O is directed back to the submitter' | ||
| - | qrsh uname -a | + | < |
| The uname of some machine the scheduler selects in the cluster will then be displayed on the submitting terminal. To redirect the output, | The uname of some machine the scheduler selects in the cluster will then be displayed on the submitting terminal. To redirect the output, | ||
| - | qrsh uname -a > /tmp/myfile | + | < |
| The output from uname will be written to /tmp/myfile on the submitting host. To allow the command to queue: | The output from uname will be written to /tmp/myfile on the submitting host. To allow the command to queue: | ||
| - | qrsh -now no uname -a | + | < |
| If a suitable host is not immediately available the command will block until a suitable host is available. At that time, the command output will be displayed on the submitting terminal. | If a suitable host is not immediately available the command will block until a suitable host is available. At that time, the command output will be displayed on the submitting terminal. | ||
basic_usage_of_grid_engine_commands.1257408662.txt.gz · Last modified: (external edit)