1GLOBUS-JOB-SUBMIT(1) GRAM5 Commands GLOBUS-JOB-SUBMIT(1)
2
6 globus-job-submit - Submit a batch job using GRAM
7
9 globus-job-submit [-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-submit [-help] [-usage] [-version] [-versions]
25
27 The globus-job-submit 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-submit provides similar functionality to globusrun in
36 that it allows batch submission of GRAM jobs. However, unlike
37 globusrun, it uses command-line parameters to define the job instead of
38 RSL expressions.
39 To retrieve the output and error streams of the job, use the program
41 globus-job-get-output. To reclaim resources used by the job by deleting
42 cached files and job state, use the program globus-job-clean. To cancel
43 a batch job submitted by globus-job-submit, use the program
44 globus-job-cancel.
45
47 The full set of options to globus-job-submit are:
48 -help, -usage
50 Display a help message to standard error and exit.
51 -version
53 Display the software version of the globus-job-submit program to
54 standard output.
55 -versions
57 Display the software version of the globus-job-submit program
58 including DiRT information to standard output.
59 -dumprsl
61 Translate the command-line options to globus-job-submit into an RSL
62 expression that can be used with tools such as globusrun.
63 -dryrun
65 Submit the job request to the GRAM service with the dryrun option
66 enabled. When this option is used, the GRAM service prepares to
67 execute the job but stops before submitting the job to the LRM.
68 This can be used to diagnose some problems such as missing files.
69 -verify
71 Submit the job request to the GRAM service with the dryrun option
72 enabled and then without it enabled if the dryrun is successful.
73 -file ARGUMENT_FILE
75 Read additional command-line options from ARGUMENT_FILE.
76 -np PROCESSES, -count PROCESSES
78 Start PROCESSES instances of the executable as a single job.
79 -m MAX_TIME, -maxtime MAX_TIME
81 Schedule the job to run for a maximum of MAX_TIME minutes.
82 -p PROJECT, -project PROJECT
84 Request that the job use the allocation PROJECT when submitting the
85 job to the LRM.
86 -q QUEUE, -queue QUEUE
88 Request that the job be submitted to the LRM using the named QUEUE.
89 -d DIRECTORY, -directory DIRECTORY
91 Run the job in the directory named by DIRECTORY. Input and output
92 files will be interpreted relative to this directory. This
93 directory must exist on the file system on the LRM-managed
94 resource. If not specified, the job will run in the home directory
95 of the user the job is running as.
96 -env NAME=VALUE
98 Define an environment variable named by NAME with the value VALUE
99 in the job environment. This option may be specified multiple times
100 to define multiple environment variables.
101 -stdin [-l | -s] STDIN_FILE
103 Use the file named by STDIN_FILE as the standard input of the job.
104 If the -l option is specified, then this file is interpreted to be
105 on a file system local to the LRM. If the -s option is specified,
106 then this file is interpreted to be on the file system where
107 globus-job-submit is being executed, and the file will be staged
108 via GASS. If neither is specified, the local behavior is assumed.
109 -stdout [-l | -s] STDOUT_FILE
111 Use the file named by STDOUT_FILE as the destination for the
112 standard output of the job. If the -l option is specified, then
113 this file is interpreted to be on a file system local to the LRM.
114 If the -s option is specified, then this file is interpreted to be
115 on the file system where globus-job-submit is being executed, and
116 the file will be staged via GASS. If neither is specified, the
117 local behavior is assumed.
118 -stderr [-l | -s] STDERR_FILE
120 Use the file named by STDERR_FILE as the destination for the
121 standard error of the job. If the -l option is specified, then this
122 file is interpreted to be on a file system local to the LRM. If the
123 -s option is specified, then this file is interpreted to be on the
124 file system where globus-job-submit is being executed, and the file
125 will be staged via GASS. If neither is specified, the local
126 behavior is assumed.
127 -x RSL_CLAUSE
129 Add a set of custom RSL attributes described by RSL_CLAUSE to the
130 job description. The clause must be an RSL conjunction and may
131 contain one or more attributes. This can be used to include
132 attributes which can not be defined by other command-line options
133 of globus-job-submit.
134 -l
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 -l option is specified, then the executable
139 is interpreted to be on a file system local to the LRM.
140 -s
142 When included outside the context of -stdin, -stdout, or -stderr
143 command-line options, -l option alters the interpretation of the
144 executable path. If the -s option is specified, then the executable
145 is interpreted to be on the file system where globus-job-run is
146 being executed, and the file will be staged via GASS. If neither is
147 specified, the local behavior is assumed.
148
150 If the following variables affect the execution of globus-job-submit.
151 X509_USER_PROXY
153 Path to proxy credential.
154 X509_CERT_DIR
156 Path to trusted certificate directory.
157
159 globusrun(1), globus-job-run(1), globus-job-clean(1), globus-job-get-
160 output(1), globus-job-cancel(1)
161University of Chicago 03/18/2010 GLOBUS-JOB-SUBMIT(1)