Changes between Version 25 and Version 26 of JobSubmission

Timestamp:

Feb 17, 2013, 3:37:36 AM (11 years ago)

Author:

Christian Beer

Comment:

added links to template description

JobSubmission

@@ -14 +14 @@
  --wu_name name:: workunit name (default: appname_PID_TIME)
  --wu_template filename:: WU template filename relative to project root; usually in templates/.  Default: templates/appname_in.
- --result_template filename:: result template filename, relative to project root; usually in templates/.  Default: templates/appname_out.
+ --result_template filename:: [JobTemplates result template] filename, relative to project root; usually in templates/.  Default: templates/appname_out.
  --batch n::
  --priority n:: high values are assigned before low values;
   see --priority_order and --priority_order_create_time options on the [BackendPrograms#feeder feeder]
 
-The following [JobIn job parameters] may be passed in the input template,
+The following [JobIn job parameters] may be passed in the [JobTemplates input template],
 or as command-line arguments to create_work;
 the input template has precedence.
@@ -56 +56 @@
 }}}
 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 input template file (the latter has priority).
+Other job parameters may be passed either in the DB_WORKUNIT structure or in the [JobTemplates input template file] (the latter has priority).
 On a successful return, wu.id contains the database ID of the workunit.