Sent-With-Job Executable Example with Globus RSL

To send your executable along with your job submission using Globus RSL, you will need to use what is called a GASS server. However, one of these is start implicitly when you run globusrun with “-s”. So, you can submit a job with a non-local executable as follows:

& (jobtype=single)
  (environment=(GLOBUS_DUROC_SUBJOB_INDEX 0))
  (executable=$(GLOBUSRUN_GASS_URL)/./my_executable)

Note that the path above “./my_executable” simply says that the executable is in the directory you are submitting the job from. You may specify any valid path here.

Then, submit this RSL file to the Purdue Altix (caesar) or Notre Dame cluster as normal:

globusrun -s -f my_job.rsl -r gatekeeper.purdue.nwicgrid.org/jobmanager-pbs
globusrun -s -f my_job.rsl -r gatekeeper.nd.nwicgrid.org/jobmanager-sge

If you would like to redirect your output and error, you may add the following parameters to the RSL file:

  (stdout=my_job.out)
  (stderr=my_job.err)