How to Submit Test Jobs

Before you start submitting batch scripts to the grid engine system, check to see whether your site's standard shell resource files (.cshrc, .profile, or .kshrc) as well as your personal resource files contain commands such as stty. Batch jobs do not have a terminal connection by default, and therefore calls to stty result in an error.

1. Log in to the master host.

2. Type the following command.

   % rsh exec-host-name date

   exec-host-name refers to one of the already installed execution hosts. You should try this test on all execution hosts if your login or home directories differ from host to host. The rsh command should give you output similar to the date command run locally on the master host. If any additional lines contain error messages, you must fix the cause of the errors before you can run a batch job successfully.

   For all command interpreters you can check on an actual terminal connection before you run a command such as stty.

   The following is an example of a Bourne shell script to test the terminal connection.

   tty -s if [ $? = 0 ]; then stty erase ^H fi

   The following example shows C Shell syntax.

   tty -s if ( $status = 0 ) then stty erase ^H endif

3. Submit one of the sample scripts contained in the sge-root/examples/jobs directory.

   % qsub sge-root/examples/jobs/simple.sh

4. Use the qstat command to monitor the job's behavior.

   For more information about submitting and monitoring batch jobs, see Submitting Batch Jobs in Sun N1 Grid Engine 6.1 User’s Guide.

5. After the job finishes executing, check your home directory for the redirected stdout/stderr files script-name.ejob-id and script-name.ojob-id.

   job-id is a consecutive unique integer number assigned to each job.

   In case of problems, see Chapter 9, Fine Tuning, Error Messages, and Troubleshooting, in Sun N1 Grid Engine 6.1 Administration Guide.