
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 50)
• “encoding” (page 51)
• “endseq” (page 53)
• “forcestaging” (page 54)
• “multipart” (page 55)
• “noaudit” (page 56)
• “parallelstreams” (page 57)
• “password” (page 57)
• “retries” (page 58)
• “sorted” (page 58)
• “startseq” (page 58)
• “system” (page 59)
• “teamsize” (page 59)
• “tenacity” (page 59)
• “timeout” (page 59)
• “url” (page 60)
• “user” (page 60)
“Sources” (page 43)
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:
• “autotran” (page 49)
• “baddatafile” (page 49)
• “commitsize” (page 49)
• “deleteonerror” (page 50)
• “discards” (page 50)
• “enabletriggers” (page 51)
• “errors” (page 53)
• “faileddatafile” (page 54)
• “operation” (page 57)
• “parallel” (page 57)
• “rowsetsize” (page 58)
• “taskrowsetsize” (page 59)
• “truncate” (page 60)
“Jobs” (page 46)
Comments you want to include in the file.
This control file section has no unique options.
“Comments” (page 47)
Includes a control file segment in this file.
This control file section has no unique options.
“Include” (page 48)
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.
Control File Organization and Syntax 27
Comentarios a estos manuales