The DCS Client has some configurable parameters that control the retry of job submission and how long the DCS Client will wait for several phases of the job's processing to complete. These parameters may be tuned, if desired. Note that it is possible for the system administrator for the system upon which the DCS Client runs to have modified the defaults shown below.
These options are set via the --config
command line argument. The value for stringstring is of the form:
name1=value1[,name2=value2][,...]
where namen specifies
the option name and the corresponding value is provided by
valuen.
The following table describes the option names and values.
Time limits are given in seconds, and may be optionally suffixed with
m to specify minutes or
h to specify hours:
number[m|h]
Table 4.1. Advanced DCS Options Description
| Name | Description |
|---|---|
| job.run.timelimit |
Maximum time to allow for job completion after the
DCS server has notified the DCS Client that processing has started.
DEFAULT: 24h |
| job.start.timelimit |
Maximum time to allow for the DCS server to notify the
DCS Client that processing has started.
DEFAULT: 12h |
| submit.retry |
Permit the DCS Client to retry the submission to the
DCS Queue Manager. The values are 1 (one) for true,
0 (zero) for false.
DEFAULT: 1 |
| submit.retry.timelimit |
Maximum time to allow for submission retries
before giving up.
DEFAULT: 2h |
For example, to set the job start time limit to 2 hours, use:
dcscmd --config job.start.timelimit=2h [args ...]