Using The Generic Submit Script

To try out the generic submit script, you should first make a copy of the script to a network drive accessible by all machines on your network. (Since this script calls itself as a render script, it must be accessible by all machines via the same path)

• Copy the generic submit script from the rush directory to a network drive.

  In place of the following example, use an absolute path that can be accessed by your entire network:

  	    cp /usr/local/rush/examples/submit-generic.pl /net/rush
  	    

• Invoke the script from the network drive.

  The interface should pop up. If it doesn't, verify the first line in the script's path points to the correct location of your perl binary.
  When the GUI pops up, note there are various 'Advanced Options' available if you scroll the window down.

• Select the 'Shell' you want to use.

  In this example, choose 'perl'.

• Enter the shell commands to execute.

  These are the commands you want to have executed for each frame on all the machines, and will be run in the 'Shell' you selected above.
  Since we've selected 'perl', enter some perl commands you know will work on both unix and Windows platforms:

  	    print "Working on frame $ENV{RUSH_FRAME}\n";
  	    system("netstat -an");
  	    exit(0);
  	    

  Note: If your commands assume you to be in a particular directory, you better include a chdir command to the full absolute path.
  As with all render scripts, you should return a proper exit code; 0=Done, 1=Fail, 2=Retry.

• Enter the cpus to use.

  In our case, lets use any 5 available cpus at the lowest priority:

    
  	    +any=5@1
  	    

• Set the directory where logs should be written.

  Scroll down to 'Log Directory', and set the absolute path to a network directory which all machines can access.
  In place of the following example, use an absolute path that is relevant to your network.

  	    //net/tmp/logs
  	    

• Submit the job by clicking the 'Submit' button.

  The job should submit, and an irush interface should pop up with the jobid already set.
  For more info on the irush interface, see the irush tutorial.

• Monitor the job.

  Hit 'Frames' in irush to watch the progress of your job.
  If some frames are running, or got done already, click on some, and hit 'Logs' to see the output of the perl commands you entered.

• Dump the job when you're done.

  When you're finished with the job, hit 'Dump' in irush.