1just-man-pages/condor_submit_Gdeange(r1a)l CommandsjuMsatn-umaaln-pages/condor_submit_dag(1)
2
6 condor_submit_dag Manage and queue jobs within a specified DAG for exe‐
7 cution on remote machines
8
10 condor_submit_dag [ -help | -version ]
11 condor_submit_dag [ -no_submit ] [ -verbose ] [ -force ] [ -maxidle
13 NumberOfJobs ] [ -maxjobs NumberOfJobs ] [ -dagman DagmanExecutable ] [
14 -maxpre NumberOfPREscripts ] [ -maxpost NumberOfPOSTscripts ] [ -noti‐
15 fication value ] [ -noeventchecks ] [ -allowlogerror ] [ -r schedd_name
16 ] [ -debug level ] [ -usedagdir ] [ -outfile_dir directory ] [ -config
17 ConfigFileName ] [ -insert_sub_file FileName ] [ -append Command ] [
18 -oldrescue 0|1 ] [ -autorescue 0|1 ] [ -dorescuefrom number ] [
19 -allowversionmismatch ] [ -no_recurse ] [ -update_submit ] [
20 -import_env ] [ -DumpRescue ] [ -valgrind ] DAGInputFile1 [ DAGInput‐
21 File2 ... DAGInputFileN ]
22
24 condor_submit_dag is the program for submitting a DAG (directed acyclic
25 graph) of jobs for execution under Condor. The program enforces the job
26 dependencies defined in one or more DAGInputFile s. Each DAGInputFile
27 contains commands to direct the submission of jobs implied by the nodes
28 of a DAG to Condor. See the Condor User Manual, section for a complete
29 description.
30
32 -help
33 Display usage information.
35 -version
39 Display version information.
41 -no_submit
45 Produce the Condor submit description file for DAGMan, but do not
47 submit DAGMan as a Condor job.
48 -verbose
52 Cause condor_submit_dag to give verbose error messages.
54 -force
58 Require condor_submit_dag to overwrite the files that it produces,
60 if the files already exist. Note that dagman.outwill be appended to,
61 not overwritten. If new-style rescue DAG mode is in effect, and any
62 new-style rescue DAGs exist, the -force flag will cause them to be
63 renamed, and the original DAG will be run. If old-style rescue DAG
64 mode is in effect, any existing old-style rescue DAGs will be
65 deleted, and the original DAG will be run. Section details rescue
66 DAGs.
67 -maxidle NumberOfJobs
71 Sets the maximum number of idle jobs allowed before condor_dagman
73 stops submitting more jobs. Once idle jobs start to run, condor_dag‐
74 man will resume submitting jobs. NumberOfJobs is a positive inte‐
75 ger. If the option is omitted, the number of idle jobs is unlimited.
76 Note that for this argument, each individual process within a clus‐
77 ter counts as a job, which is inconsistent with -maxjobs .
78 -maxjobs NumberOfJobs
82 Sets the maximum number of jobs within the DAG that will be submit‐
84 ted to Condor at one time. NumberOfJobs is a positive integer. If
85 the option is omitted, the default number of jobs is unlimited. Note
86 that for this argument, each cluster counts as one job, no matter
87 how many individual processes are in the cluster.
88 -dagman DagmanExecutable
92 Allows the specification of an alternate condor_dagman executable to
94 be used instead of the one found in the user's path. This must be a
95 fully qualified path.
96 -maxpre NumberOfPREscripts
100 Sets the maximum number of PRE scripts within the DAG that may be
102 running at one time. NumberOfPREScripts is a positive integer. If
103 this option is omitted, the default number of PRE scripts is unlim‐
104 ited.
105 -maxpost NumberOfPOSTscripts
109 Sets the maximum number of POST scripts within the DAG that may be
111 running at one time. NumberOfPOSTScripts is a positive integer. If
112 this option is omitted, the default number of POST scripts is unlim‐
113 ited.
114 -notification value
118 Sets the e-mail notification for DAGMan itself. This information
120 will be used within the Condor submit description file for DAGMan.
121 This file is produced by condor_submit_dag . See notification within
122 the section of submit description file commands in the condor_submit
123 manual page on page for specification of value .
124 -noeventchecks
128 This argument is no longer used; it is now ignored. Its functional‐
130 ity is now implemented by the DAGMAN_ALLOW_EVENTSconfiguration macro
131 (see section ).
132 -allowlogerror
136 This optional argument has condor_dagman try to run the specified
138 DAG, even in the case of detected errors in the user log specifica‐
139 tion. As of version 7.3.2, this argument has an effect only on DAGs
140 containing Stork job nodes.
141 -r schedd_name
145 Submit condor_dagman to a remote machine, specifically the con‐
147 dor_schedd daemon on that machine. The condor_dagman job will not
148 run on the local condor_schedd (the submit machine), but on the
149 specified one. This is implemented using the -remote option to con‐
150 dor_submit . Note that this option does not currently specify input
151 files for condor_dagman , nor the individual nodes to be taken
152 along! It is assumed that any necessary files will be present on the
153 remote computer, possibly via a shared file system between the local
154 computer and the remote computer. It is also necessary that the user
155 has appropriate permissions to submit a job to the remote machine;
156 the permissions are the same as those required to use condor_submit
157 -remote option. If other options are desired, including transfer of
158 other input files, consider using the -no_submit option, modifying
159 the resulting submit file for specific needs, and then using con‐
160 dor_submit on that.
161 -debug level
165 Passes the the level of debugging output desired to condor_dagman .
167 level is an integer, with values of 0-7 inclusive, where 7 is the
168 most verbose output. A default value of 3 is passed to condor_dagman
169 when not specified with this option. See the condor_dagman manual
170 page on page for detailed descriptions of these values.
171 -usedagdir
175 This optional argument causes condor_dagman to run each specified
177 DAG as if condor_submit_dag had been run in the directory containing
178 that DAG file. This option is most useful when running multiple DAGs
179 in a single condor_dagman . Note that the -usedagdir flag must not
180 be used when running an old-style rescue DAG (see section ).
181 -outfile_dir directory
185 Specifies the directory in which the .dagman.outfile will be writ‐
187 ten. The directory may be specified relative to the current working
188 directory as condor_submit_dag is executed, or specified with an
189 absolute path. Without this option, the .dagman.outfile is placed in
190 the same directory as the first DAG input file listed on the command
191 line.
192 -config ConfigFileName
196 Specifies a configuration file to be used for this DAGMan run. Note
198 that the options specified in the configuration file apply to all
199 DAGs if multiple DAGs are specified. Further note that it is a fatal
200 error if the configuration file specified by this option conflicts
201 with a configuration file specified in any of the DAG files, if they
202 specify one. For more information about how condor_dagman configura‐
203 tion files work, see section .
204 -insert_sub_file FileName
208 Specifies a file to insert into the .condor.subfile created by con‐
210 dor_submit_dag . The specified file must contain only legal submit
211 file commands. Only one file can be inserted. (If both the DAG‐
212 MAN_INSERT_SUB_FILE configuration variable and -insert_sub_file are
213 specified, -insert_sub_file overrides DAGMAN_INSERT_SUB_FILE.) The
214 specified file is inserted into the .condor.subfile before the Queue
215 command and before any commands specified with the -append option.
216 -append Command
220 Specifies a command to append to the .condor.subfile created by con‐
222 dor_submit_dag . The specified command is appended to the .con‐
223 dor.subfile immediately before the Queue command. Multiple commands
224 are specified by using the -append option multiple times. Each new
225 command is given in a separate -append option. Commands with spaces
226 in them must be enclosed in double quotes. Commands specified with
227 the -append option are appended to the .condor.subfile after com‐
228 mands inserted from a file specified by the -insert_sub_file option
229 or the DAGMAN_INSERT_SUB_FILE configuration variable, so the -append
230 command(s) will override commands from the inserted file if the com‐
231 mands conflict.
232 -oldrescue 0|1
236 Whether to use "old-style" rescue DAG naming (see section ) when
238 creating a rescue DAG (0 = false, 1 = true).
239 -autorescue 0|1
243 Whether to automatically run the newest rescue DAG for the given DAG
245 file, if one exists (0 = false, 1 = true).
246 -dorescuefrom number
250 Forces condor_dagman to run the specified rescue DAG number for the
252 given DAG. A value of 0 is the same as not specifying this option.
253 Specifying a non-existent rescue DAG is a fatal error.
254 -allowversionmismatch
258 This optional argument causes condor_dagman to allow a version mis‐
260 match between condor_dagman itself and the .condor.subfile produced
261 by condor_submit_dag (or, in other words, between condor_submit_dag
262 and condor_dagman ). WARNING! This option should be used only if
263 absolutely necessary. Allowing version mismatches can cause subtle
264 problems when running DAGs. (Note that, starting with version 7.4.0,
265 condor_dagman no longer requires an exact version match between
266 itself and the .condor.subfile. Instead, a "minimum compatible ver‐
267 sion" is defined, and any .condor.subfile of that version or newer
268 is accepted.)
269 -no_recurse
273 This optional argument causes condor_submit_dag to not run itself
275 recursively on nested DAGs (the default is that recursion is
276 enabled). (DAG nodes specified with the SUBDAG EXTERNALkeyword or
277 with submit file names ending in .condor.subare considered nested
278 DAGs, and, by default, condor_submit_dag -no_submit -update_submit
279 is run on the corresponding DAG files.)
280 -update_submit
284 This optional argument causes an existing .condor.subfile to not be
286 treated as an error; rather, the .condor.subfile will be overwrit‐
287 ten, but the existing values of -maxjobs , -maxidle , -maxpre , and
288 -maxpost will be preserved.
289 -import_env
293 This optional argument causes condor_submit_dag to import the cur‐
295 rent environment into the environment command of the .condor.subfile
296 it generates.
297 -DumpRescue
301 This optional argument tells condor_dagman to immediately dump a
303 rescue DAG and then exit, as opposed to actually running the DAG.
304 (This feature is mainly intended for testing.)
305 -valgrind
309 This optional argument causes the submit description file generated
311 for the submission of condor_dagman to be modified. The executable
312 becomes valgrind run on condor_dagman , with a specific set of argu‐
313 ments intended for testing condor_dagman . Note that this argument
314 is intended for testing purposes only. Using the -valgrind option
315 without the necessary valgrind software installed will cause the DAG
316 to fail. If the DAG does run, it will run much more slowly than
317 usual.
318
322 Condor User Manual
323
325 condor_submit_dag will exit with a status value of 0 (zero) upon suc‐
326 cess, and it will exit with the value 1 (one) upon failure.
327
329 To run a single DAG:
330 % condor_submit_dag diamond.dag
332 To run a DAG when it has already been run and the output files exist:
334 % condor_submit_dag -force diamond.dag
336 To run a DAG, limiting the number of idle node jobs in the DAG to a
338 maximum of five:
339 % condor_submit_dag -maxidle 5 diamond.dag
341 To run a DAG, limiting the number of concurrent PRE scripts to 10 and
343 the number of concurrent POST scripts to five:
344 % condor_submit_dag -maxpre 10 -maxpost 5 diamond.dag
346 To run two DAGs, each of which is set up to run in its own directory:
348 % condor_submit_dag -usedagdir dag1/diamond1.dag dag2/diamond2.dag
350
352 Condor Team, University of Wisconsin-Madison
353
355 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
356 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
357 Licensed under the Apache License, Version 2.0.
358 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
360 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
361 date just-man-pages/condor_submit_dag(1)