1GLOBUSRUN(1) Grid Community Toolkit Manual GLOBUSRUN(1)
2
6 globusrun - Execute and manage jobs via GRAM
7
9 globusrun [-help | -usage | -version -versions ]
10 globusrun [-p | -parse] { -f FILENAME | -file FILENAME | RSL }
12 globusrun [OPTIONS] {-r RESOURCE| -resource RESOURCE} { -a |
14 -authenticate-only }
15 globusrun [OPTIONS] {-r RESOURCE| -resource RESOURCE} { -j |
17 -jobmanager-version }
18 globusrun [OPTIONS] {-k | -kill } JOBID
20 globusrun [OPTIONS] [ -full-proxy | -D ] { -y | -refresh-proxy } JOBID
22 globusrun [OPTIONS] -status JOBID
24 globusrun [OPTIONS] { -r RESOURCE | -resource RESOURCE } { -f FILENAME
26 | -file FILENAME | RSL}
27
29 The globusrun program for submits and manages jobs run on a local or
30 remote job host. The jobs are controlled by the globus-job-manager
31 program which interfaces with a local resource manager that schedules
32 and executes the job.
33 The globusrun program can be run in a number of different modes chosen
35 by command-line options.
36 When -help, -usage, -version, or -versions command-line options are
38 used, globusrun will print out diagnostic information and then exit.
39 When the -p or -parse command-line option is present, globusrun will
41 verify the syntax of the RSL specification and then terminate. If the
42 syntax is valid, globusrun will print out the string RSL Parsed
43 Successfully... and exit with a zero exit code; otherwise, it will
44 print an error message and terminate with a non-zero exit code.
45 When the -a or -authenticate-only command-line option is present,
47 globusrun will verify that the service named by RESOURCE exists and the
48 client’s credentials are granted permission to access that service. If
49 authentication is successful, globusrun will display the string GRAM
50 Authentication test successful and exit with a zero exit code;
51 otherwise it will print an explanation of the problem and will with a
52 non-zero exit code.
53 When the -j or -jobmanager-version command-line option is present,
55 globusrun will attempt to determine the software version that the
56 service named by RESOURCE is running. If successful, it will display
57 both the Toolkit version and the Job Manager package version and exit
58 with a zero exit code; otherwise, it will print an explanation of the
59 problem and exit with a non-zero exit code.
60 When the -k or -kill command-line option is present, globusrun will
62 attempt to terminate the job named by JOB_ID. If successful, globusrun
63 will exit with zero; otherwise it will display an explanation of the
64 problem and exit with a non-zero exit code.
65 When the -y or -refresh-proxy command-line option is present, globusrun
67 will attempt to delegate a new X.509 proxy to the job manager which is
68 managing the job named by JOBID. If successful, globusrun will exit
69 with zero; otherwise it will display an explanation of the problem and
70 exit with a non-zero exit code. This behavior can be modified by the
71 -full-proxy or -D command-line options to enable full proxy delegation.
72 The default is limited proxy delegation.
73 When the -status command-line option is present, globusrun will attempt
75 to determine the current state of the job. If successful, the state
76 will be printed to standard output and globusrun will exit with a zero
77 exit code; otherwise, a description of the error will be displayed and
78 it will exit with a non-zero exit code.
79 Otherwise, globusrun will submit the job to a GRAM service. By default,
81 globusrun waits until the job has terminated or failed before exiting,
82 displaying information about job state changes and at exit time, the
83 job exit code if it is provided by the GRAM service.
84 The globusrun program can also function as a GASS file server to allow
86 the globus-job-manager program to stage files to and from the machine
87 on which globusrun is executed to the GRAM service node. This behavior
88 is controlled by the -s, -o, and -w command-line options.
89 Jobs submitted by globusrun can be monitored interactively or detached.
91 To have globusrun detach from the GRAM service after submitting the
92 job, use the -b or -F command-line options.
93
95 -help
96 Display a help message to standard error and exit.
97 -usage
99 Display a one-line usage summary to standard error and exit.
100 -version
102 Display the software version of globusrun to standard error and
103 exit.
104 -versions
106 Display the software version of all modules used by globusrun
107 (including DiRT information) to standard error and then exit.
108 -p, -parse
110 Do a parse check on the job specification and print diagnostics. If
111 a parse error occurs, globusrun exits with a non-zero exit code.
112 -f FILENAME, -file FILENAME
114 Read job specification from the file named by FILENAME
115 -n, -no-interrupt
117 Disable handling of the SIGINT signal, so that the interrupt
118 character (typically Control-C causes globusrun to terminate
119 without canceling the job.
120 -r RESOURCE
122 Submit the request to the resource specified by RESOURCE. A
123 resource may be specified in the following ways:
124 · HOST
126 · HOST:PORT
128 · HOST:PORT/SERVICE
130 · HOST/SERVICE
132 · HOST:/SERVICE
134 · HOST::SUBJECT
136 · HOST:PORT:SUBJECT
138 · HOST/SERVICE:SUBJECT
140 · HOST:/SERVICE:SUBJECT
142 · HOST:PORT/SERVICE:SUBJECT If any of PORT, SERVICE, or SUBJECT
144 is omitted, the defaults of 2811, jobmanager, and host@HOST are
145 used respectively.
146 -j, -jobmanager-version
148 Print the software version being run by the service running at
149 RESOURCE.
150 -k JOBID, -kill JOBID
152 Kill the job named by JOBID.
153 -D, -full-proxy
155 Delegate a full impersonation proxy to the service. By default, a
156 limited proxy is delegated when needed.
157 -y, -refresh-proxy: Delegate a new proxy to the service processing
159 JOBID.
160 -status
162 Display the current status of the job named by JOBID.
163 -q, -quiet
165 Do not display job state change or exit code information.
166 -o, -output-enable
168 Start a GASS server within the globusrun application that allows
169 access to its standard output and standard error streams only.
170 Also, augment the RSL with a definition of the GLOBUSRUN_GASS_URL
171 RSL substitution and add stdout and stderr clauses which redirect
172 the output and error streams of the job to the output and error
173 streams of the interactive globusrun command. If this is specified,
174 then globusrun acts as though the -q were also specified.
175 -s, -server
177 Start a GASS server within the globusrun application that allows
178 access to its standard output and standard error streams for
179 writing and any file local the the globusrun invocation for
180 reading. Also, augment the RSL with a definition of the
181 GLOBUSRUN_GASS_URL RSL substitution and add stdout and stderr
182 clauses which redirect the output and error streams of the job to
183 the output and error streams of the interactive globusrun command.
184 If this is specified, then globusrun acts as though the -q were
185 also specified.
186 -w, -write-allow
188 Start a GASS server within the globusrun application that allows
189 access to its standard output and standard error streams for
190 writing and any file local the the globusrun invocation for reading
191 or writing. Also, augment the RSL with a definition of the
192 GLOBUSRUN_GASS_URL RSL substitution and add stdout and stderr
193 clauses which redirect the output and error streams of the job to
194 the output and error streams of the interactive globusrun command.
195 If this is specified, then globusrun acts as though the -q were
196 also specified.
197 -b, -batch
199 Terminate after submitting the job to the GRAM service. The
200 GASS-related options can be used to stage input files, but standard
201 output, standard error, and file staging after the job completes
202 will not be processed. The globusrun program will exit after the
203 job hits any of the following states:
204 · PENDING
206 · ACTIVE
208 · FAILED
210 · DONE
212 -F, -fast-batch
214 Terminate after submitting the job to the GRAM service. The
215 globusrun program will exit after it receives a reply from the
216 service. The JOBID will be displayed to standard output before
217 terminating so that the job can be checked with the -status
218 command-line option or modified by the -refresh-proxy or -kill
219 command-line options.
220 -d, -dryrun
222 Submit the job with the dryrun attribute set to true. When this is
223 done, the job manager will prepare to start the job but start short
224 of submitting it to the service. This can be used to detect
225 problems with the RSL.
226
228 The following variables affect the execution of globusrun
229 X509_USER_PROXY
231 Path to proxy credential.
232 X509_CERT_DIR
234 Path to trusted certificate directory.
235
237 The globusrun program assumes any failure to contact the job means the
238 job has terminated. In fact, this may be due to the globus-job-manager
239 program exiting after all jobs it is managing have reached the DONE or
240 FAILED states. In order to reliably detect job termination, the
241 two_phase RSL attribute should be used.
242
244 globus-job-submit(1), globus-job-run(1), globus-job-clean(1),
245 globus-job-get-output(1), globus-job-cancel(1)
246
248 Copyright © 1999-2014 University of Chicago
249Grid Community Toolkit 6 03/31/2018 GLOBUSRUN(1)