Changes between Version 39 and Version 40 of JobSubmission

Timestamp:

Mar 17, 2015, 9:41:53 AM (9 years ago)

Author:

davea

Comment:

--

JobSubmission

@@ -11 +11 @@
 Create a job with the given input files (which must already be [JobStage staged]).
 
-Mandatory arguments are:
+Mandatory arguments:
  --appname name:: application name
 
-Optional arguments are:
+Optional arguments:
  --wu_name name:: workunit name (default: appname_PID_TIME)
- --wu_template filename:: [JobTemplates#Inputtemplates Input template] filename relative to project root; usually in templates/.
+ --wu_template filename:: [JobTemplates#Inputtemplates Input template] filename relative to project root;
+   usually in templates/.
    Default: templates/appname_in.
- --result_template filename:: [JobTemplates#Outputtemplates Output template] filename, relative to project root; usually in templates/.
+ --result_template filename:: [JobTemplates#Outputtemplates Output template] filename,
+   relative to project root; usually in templates/.
    Default: templates/appname_out.
- --batch n::
+ --batch n:: associate the job with the given batch.
  --priority n:: high values are assigned before low values;
   see --priority_order and --priority_order_create_time options on the [BackendPrograms#feeder feeder]
  --stdin:: Read stdin, and create one job per line (see below).
+ --continue_on_error:: keep going if an error occurs (used with --stdin)
  --broadcast, --target_host, etc.:: [AssignedWork Assign or broadcast] this job.
   
@@ -104 +107 @@
 }}}
 The ''name'' and ''appid'' fields of the DB_WORKUNIT structure must always be initialized.
-Other job parameters may be passed either in the DB_WORKUNIT structure or in the [JobTemplates#Inputtemplates input template file]
+Other job parameters may be passed either in the DB_WORKUNIT structure
+or in the [JobTemplates#Inputtemplates input template file]
 (the latter has priority).
 On a successful return, wu.id contains the database ID of the workunit.