1GLOBUS-JOB-RUN(1) GRAM5 Commands GLOBUS-JOB-RUN(1)
2
6 globus-job-run - Execute a job using GRAM
7
9 globus-job-run [-dumprsl] [-dryrun] [-verify]
10 [-file ARGUMENT_FILE]
11 SERVICE_CONTACT
12 [-np PROCESSES | -count PROCESSES]
13 [-m MAX_TIME | -maxtime MAX_TIME]
14 [-p PROJECT | -project PROJECT]
15 [-q QUEUE | -queue QUEUE]
16 [-d DIRECTORY | -directory DIRECTORY]
17 [-env NAME=VALUE]...
18 [-stdin [-l | -s] STDIN_FILE]
19 [-stdout [-l | -s] STDOUT_FILE]
20 [-stderr [-l | -s] STDERR_FILE]
21 [-x RSL_CLAUSE]
22 [-l | -s] EXECUTABLE [ARGUMENT...]
23 globus-job-run [-help] [-usage] [-version] [-versions]
25
27 The globus-job-run program constructs a job description from its
28 command-line options and then submits the job to the GRAM service
29 running at SERVICE_CONTACT. The executable and arguments to the
30 executable are provided on the command-line after all other options.
31 Note that the -dumprsl, -dryrun, -verify, and -file command-line
32 options must occur before the first non-option argument, the
33 SERVICE_CONTACT.
34 The globus-job-run provides similar functionality to globusrun in that
36 it allows interactive start-up of GRAM jobs. However, unlike globusrun,
37 it uses command-line parameters to define the job instead of RSL
38 expressions.
39
41 The full set of options to globus-job-run are:
42 -help, -usage
44 Display a help message to standard error and exit.
45 -version
47 Display the software version of the globus-job-run program to
48 standard output.
49 -version
51 Display the software version of the globus-job-run program
52 including DiRT information to standard output.
53 -dumprsl
55 Translate the command-line options to globus-job-run into an RSL
56 expression that can be used with tools such as globusrun.
57 -dryrun
59 Submit the job request to the GRAM service with the dryrun option
60 enabled. When this option is used, the GRAM service prepares to
61 execute the job but stops before submitting the job to the LRM.
62 This can be used to diagnose some problems such as missing files.
63 -verify
65 Submit the job request to the GRAM service with the dryrun option
66 enabled and then without it enabled if the dryrun is successful.
67 -file ARGUMENT_FILE
69 Read additional command-line options from ARGUMENT_FILE.
70 -np PROCESSES, -count PROCESSES
72 Start PROCESSES instances of the executable as a single job.
73 -m MAX_TIME, -maxtime MAX_TIME
75 Schedule the job to run for a maximum of MAX_TIME minutes.
76 -p PROJECT, -project PROJECT
78 Request that the job use the allocation PROJECT when submitting the
79 job to the LRM.
80 -q QUEUE, -queue QUEUE
82 Request that the job be submitted to the LRM using the named QUEUE.
83 -d DIRECTORY, -directory DIRECTORY
85 Run the job in the directory named by DIRECTORY. Input and output
86 files will be interpreted relative to this directory. This
87 directory must exist on the file system on the LRM-managed
88 resource. If not specified, the job will run in the home directory
89 of the user the job is running as.
90 -env NAME=VALUE
92 Define an environment variable named by NAME with the value VALUE
93 in the job environment. This option may be specified multiple times
94 to define multiple environment variables.
95 -stdin [-l | -s] STDIN_FILE
97 Use the file named by STDIN_FILE as the standard input of the job.
98 If the -l option is specified, then this file is interpreted to be
99 on a file system local to the LRM. If the -s option is specified,
100 then this file is interpreted to be on the file system where
101 globus-job-run is being executed, and the file will be staged via
102 GASS. If neither is specified, the local behavior is assumed.
103 -stdout [-l | -s] STDOUT_FILE
105 Use the file named by STDOUT_FILE as the destination for the
106 standard output of the job. If the -l option is specified, then
107 this file is interpreted to be on a file system local to the LRM.
108 If the -s option is specified, then this file is interpreted to be
109 on the file system where globus-job-run is being executed, and the
110 file will be staged via GASS. If neither is specified, the local
111 behavior is assumed.
112 -stderr [-l | -s] STDERR_FILE
114 Use the file named by STDERR_FILE as the destination for the
115 standard error of the job. If the -l option is specified, then this
116 file is interpreted to be on a file system local to the LRM. If the
117 -s option is specified, then this file is interpreted to be on the
118 file system where globus-job-run is being executed, and the file
119 will be staged via GASS. If neither is specified, the local
120 behavior is assumed.
121 -x RSL_CLAUSE
123 Add a set of custom RSL attributes described by RSL_CLAUSE to the
124 job description. The clause must be an RSL conjunction and may
125 contain one or more attributes. This can be used to include
126 attributes which can not be defined by other command-line options
127 of globus-job-run.
128 -l
130 When included outside the context of -stdin, -stdout, or -stderr
131 command-line options, -l option alters the interpretation of the
132 executable path. If the -l option is specified, then the executable
133 is interpreted to be on a file system local to the LRM.
134 -s
136 When included outside the context of -stdin, -stdout, or -stderr
137 command-line options, -l option alters the interpretation of the
138 executable path. If the -s option is specified, then the executable
139 is interpreted to be on the file system where globus-job-run is
140 being executed, and the file will be staged via GASS. If neither is
141 specified, the local behavior is assumed.
142
144 If the following variables affect the execution of globus-job-run.
145 X509_USER_PROXY
147 Path to proxy credential.
148 X509_CERT_DIR
150 Path to trusted certificate directory.
151
153 globusrun(1), globus-job-submit(1), globus-job-clean(1), globus-job-
154 get-output(1), globus-job-cancel(1)
155University of Chicago 03/18/2010 GLOBUS-JOB-RUN(1)