Differences

This shows you the differences between two versions of the page.

--- basic_usage_of_grid_engine_commands [2009/11/05 08:12] – 172.26.0.166
+++ basic_usage_of_grid_engine_commands [2010/05/22 14:19] (current) – external edit 127.0.0.1
@@ Line 31: / Line 31: @@
 Example:
+<code>
 qsub -cwd -v SOME_VAR -o /dev/null -e /dev/null myjob.sh
+</code>
 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's terminal window. By default, if the job cannot be run immediately, qrsh will not queue the job. Using the '-now no' flag to qrsh will allow jobs to queue. Note that I/O can be redirected with the shell redirect operators. For example, to run the uname -a command:
-qrsh uname -a
+<code>qrsh uname -a</code>
 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
+<code>qrsh uname -a > /tmp/myfile</code>
 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
+<code>qrsh -now no uname -a</code>
 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.