Syntax: globusrun [options] [RSL String]
        globusrun -version[s]
        globusrun -help

    Options
    -help | -usage
           Display help
    -version
           Display version
    -versions
           Display versions of all activated modules
    -i | -interactive 
           Run globusrun in interactive mode (multirequests only)
    -f <rsl filename> | -file <rsl filename> 
           Read RSL from the local file <rsl filename>. The RSL can
           be either a single job request, or a multirequest
    -q | -quiet
           Quiet mode (do not print diagnostic messages)
    -o | -output-enable
           Use the GASS Server library to redirect standout output
           and standard error to globusrun. Implies -quiet
    -s | -server
           $(GLOBUSRUN_GASS_URL) can be used to access files local
           to the submission machine via GASS. Implies -output-enable
           and -quiet
    -w | -write-allow
           Enable the GASS Server library and allow writing to
           GASS URLs. Implies -server and -quiet.
    -mpirun <integer>
           Currently a no-op.
    -r <resource manager> | -resource  <resource manager> 
           Submit the RSL job request to the specified resource manager.
           A resource manager can be specified in the following ways: 

           host
           host:port
           host:port/service
           host/service
           host:/service
           host::subject
           host:port:subject
           host/service:subject
           host:/service:subject
           host:port/service:subject

           For those resource manager contacts which omit the port, 
           service or subject field the following defaults are used:

           port = 2119 
           service = jobmanager 
           subject = subject based on hostname

           This is a required argument when submitting a single RSL
           request
    -n | -no-interrupt
           Cause SIGINT to terminate globusrun, while leaving the
           submitted job to run to completion. By default the SIGINT
           signal will be trapped and the job will be terminated
    -k | -kill <job ID>
           Kill a disconnected globusrun job
    -status <job ID>
           Print the current status of the specified job.
    -b | -batch
           Cause globusrun to terminate after the job is successfully
           submitted to the scheduler. Useful for batch jobs. This option
           cannot be used together with -interactive, and is also
           incompatible with multi-request jobs.
           If used with -s, files may be staged in to the job, but stdout
           and stderr will not be redirected.
           The "handle" or job ID of the submitted job will be written on
           stdout.
    -refresh-proxy | -y <job ID>
           Cause globusrun to delegate a new proxy to the job named by the
           <job ID>
    -stop-manager <job  ID>
           Cause globusrun to stop the job manager, without killing the
           job. If the save_state RSL attribute is present, then a
           job manager can be restarted by using the restart RSL attribute.

    Diagnostic Options
    -p | -parse
           Parse and validate the RSL only. Do not submit the job to
           a GRAM gatekeeper
    -a | -authenticate-only
           Submit a gatekeeper "ping" request only. Do not parse the
           RSL or submit the job request. Requires the -resource-manger 
           argument
    -d | -dryrun
           Submit the RSL to the job manager as a "dryrun" test
           The request will be parsed and authenticated. The job manager
           will execute all of the preliminary operations, and stop
           just before the job request would be executed