Globus Toolkit 3.9.2 Development Documentation: GRAM
Command line tool: managed-job-globusrun
This command is used to submit jobs to Globus resources. The job
startup is done using the GRAM services. Also, the GASS service
can be used to provide access to remote files and for redirecting
standard output streams.
In addition to starting jobs, it is possible to list previously
started jobs, query state of previously started jobs, parse RSL
request strings and/or files.
The existence of a valid proxy is required for essentially all
supported operations but RSL parsing (-p).
Arguments
[options] [<factory>] <RSL> -p -file <RSL filename> -list [<factory>] (-state | -kill) <job handle> -help | -usage | -version
with
<RSL> = -file <RSL filename> | <command line> <factory> = -factory <contact> [-type <type>] <contact> = [<protocol>://]<host>[:[port]][/<service>]
[options] = [-s] [-w] [-o] [-q] [-n] [-b] [-duration] [-terminate-at] [-auth <auth>] [-xmlsec <sec>] [-personal]
Options
Help options |
|||||||||
-help |
Displays help information about the command. | ||||||||
-usage |
Displays usage of the command. | ||||||||
-v, -version |
Displays version of the command. | ||||||||
| Job Factory Contact options |
|||||||||
-factory <contact> |
Specifies the URL of the Job Factory Service to contact when submitting or listing jobs. A factory contact string can be specified in the following ways:
It is also possible to specify the protocol
by prepending For those factory contacts which omit the protocol, port or service field, the following default values are used, as the following table explains:
Omitting altogether the -factory option is equivalent to specifying the local host as the contact string (with the implied default protocol, port and service). |
||||||||
-type <factory type> |
Specifies the type of factory resource to use. This is the name of the local resource manager. The default value is Fork | ||||||||
Job Specification
options |
|||||||||
<command line> |
Creates a simple job description that only consists of a command line of the form: 'executable (argument)*' Quotes must be used if there is one or more arguments. |
||||||||
-file <RSL filename> |
Reads RSL from the local file <RSL filename>. The RSL must be a single job request. |
||||||||
-p |
This option only parses the RSL, and then prints either a success message or a parser failure. No job will be submitted to any factory service. The RSL must be a single job request. |
||||||||
Internal
GASS Server options |
|||||||||
-s, -server |
Starts the GASS server with read access to local files, providing the remote job with read-only access to the local filesystem. The GASS server URL will be prepended to the source file path of each stage-in directive. |
||||||||
-w, -write |
Allows the GASS server to start with read/write access to local files. Similar to -server, except the GASS server will also allow writing to the local filesystem. The GASS server URL will also be prepended to the destination path of each stage-out directive. Implies -server. | ||||||||
-o, -output |
Starts the GASS server and displays the job's standard output and error streams on the standard output and error of the command's process. Special paths starting with the GASS server URL will be added to the stdout and stderr directives. No other read/write access will be provided by this option alone. Implies -quiet. |
||||||||
Batch Operations options |
|||||||||
-b, -batch |
Do not wait for started job to complete (and do not destroy started job service on exit.) The handle of the job service will be printed on the standard output. Incompatible with internal GASS options (-server, -write-allow, and -output.) The job must use an external GASS server if it needs to access local files. This option is incompatible with multi-request jobs. Implies -quiet. |
||||||||
-l, -list |
This option is NOT FUNCTIONAL YET (see below) |
||||||||
-state <handle> |
Print out the state of the specified job. For a list of valid states, see the GRAM documentation [need link]; the current valid states are Pending, Active, Done, Suspended, and Failed. | ||||||||
-k, -kill <handle> |
Kill the specified job. Note: The <handle> argument is printed out when executing in batch mode or when using the -list option. |
||||||||
Job Resource Lifetime
options |
|||||||||
-duration <duration> |
Specify the duration of the job resource. The job resource will destroy itself automatically after the specified duration starting from service creation.
Incompatible with -date-time. Useful with -batch. |
||||||||
-terminate-at <date> |
Specify termination date/time of job.
Same as -duration but with an absolute Format: MM/dd/yyyy HH:mm Default: see -duration. The date expression may need to be quoted, as in: -terminate-at '08/15/2005 11:30' Incompatible with -duration. Useful with -batch. |
||||||||
Security options |
|||||||||
-auth <auth> |
Set authorization type. <auth> can be:
|
||||||||
-xmlsec <sec> |
Set message protection level. <sec> can be:
|
||||||||
-personal |
Shortcut for -auth self. | ||||||||
-proxy <proxy file> |
Use <proxy file> instead of the default proxy credential file. | ||||||||
-deleg <deleg> |
Set delegation type. <deleg> can be:
|
||||||||
Miscellaneous options |
|||||||||
-q, -quiet |
Set quiet mode to ON (do not print diagnostic messages when job state changes, in non-batch mode). This option is useful when job output is redirected to the local process and parsed. |
||||||||
-n, -no-interrupt |
Disable interrupt handling. By default, interrupt signals (typically generated by Ctrl + C) cause the program to terminate the currently submitted job. This flag disables that behavior. | ||||||||
-timeout <integer> |
Set timeout for HTTP socket, in milliseconds. Applies to job submission only. The default value is 120000. |
||||||||
GT2 globusrun
options NOT functional (yet) |
|||||||||
-l, -list |
NOT IMPLEMENTED ON SERVER SIDE YET. List previously started and not destroyed job services for this user. The output of this command consists of the handles and RSL of the submitted jobs. Requires the -factory <URL> argument. |
||||||||
-dryrun |
NOT IMPLEMENTED ON SERVER SIDE YET. Augment the RSL in order to mark this job as a dry run, if the RSL does not already say so. This causes the job manager to stop short of starting the job, but still detect other RSL errors (such as bad directory, bad executable, etc). An error message will be displayed if the dry run fails. Otherwise, a message will be displayed indicating that the dryrun was successful. |
||||||||
-authenticate-only |
NOT IMPLEMENTED ON SERVER SIDE YET. | ||||||||
-interactive |
DUROC not supported yet. | ||||||||