
Table 5-1 Control File Organization (continued)
OptionsControl File Section
Location of sources and targets for data.
These global options can be overridden in this section of the control file.
• “datasource” (page 47)
• “endseq” (page 48)
• “multipart” (page 50)
• “parallelstreams” (page 52)
• “password” (page 52)
• “retries” (page 53)
• “sorted” (page 53)
• “startseq” (page 53)
• “system” (page 54)
• “tenacity” (page 54)
• “rowsetsize” (page 53)
• “url” (page 54)
• “user” (page 55)
“Sources” (page 40)
A list of Transporter jobs and assigned options.
These job level options can override those global options defined in the
options section for the corresponding job:
• “baddatafile” (page 47)
• “commitsize” (page 47)
• “deleteonerror” (page 48)
• “discards” (page 48)
• “errors” (page 49)
• “faileddatafile” (page 49)
• “operation” (page 52)
• “parallel” (page 52)
• “rowsetsize” (page 53)
• “truncate” (page 54)
“Jobs” (page 42)
Comments you want to include in the file.
This control file section has no unique options.
“Comments” (page 44)
Includes a control file segment in this file.
This control file section has no unique options.
“Include” (page 45)
Version
version versionnumber;
A control file always begins with the version attribute. No other sections can precede the
version attribute.
If a control file begins with the %include statement, the first included file that does not begin
with another %include statement must begin with the version attribute. In other words, the
first non-%include statement that Transporter sees must be the version attribute.
versionnumber
is the major version, followed by optional minor and patch versions. All version number
components are separated by a period (.). Only the major version is required. The components
of the version number correspond to the major, minor, and patch versions of the Transporter
product, respectively. If Transporter sees an incompatible version number in the control file,
Control File Organization and Syntax 27
Commentaires sur ces manuels