HP Neoview Release 2.5 Software - Manual (Page 27)

5 Control File Organization and Syntax
The control file is a text file that tells Transporter how you want your data moved from source
to target for either loading or extracting purposes. This chapter discusses the following topics:
• “Creating a Control File” (page 27)
• “Control File Limits” (page 27)
• “Control File Organization and Syntax” (page 27)
• “Supported Data Types” (page 51)
Creating a Control File
You can use any text editor to create the control file and you can create the file on any system
and move it to your loader platform. You can also use the Control File Editor (CFE) or Control
File Generator to create a control file.
Control File Limits
These limits apply to the control file:
• One control file invokes a single instance of the Transporter client. If you have tasks that
must run concurrently, specify those tasks in one of these ways:
— as separate job entries under the same job
— in separate control files, which requires that you invoke multiple instances of the
Transporter client
• The name you create for a control file element (for example, “Typeformats” (page 31) or
“Maps” (page 41) ) is limited to 64 bytes, must begin with a letter or an underscore, and can
contain only letters, underscores, and digits.
• For a load operation, the maximum length of an input record is 32768 characters, including
the record separator.
• The maximum number of job entries allowed for a single job is 1024.
• The maximum number of jobs allowed in a single control file is 1024.
Control File Organization and Syntax
The control file describes source, target, and settings for data movement.
A control file begins with a version attribute, followed by any number of options,
dataformats
, typeformats, maps, sources, and jobs sections, in any order.
The following control file elements are required:
• a version attribute
• dataformats
• a sources section
• a maps section
• a jobs section
If you specify a control file section or option list, you must have at least one entry. If a given
control file option is defined multiple times as a global option or defined multiple times in the
same option list, only the final occurrence is recognized by Transporter.
All control file keywords and option names are case-insensitive.
The options section sets global options for all jobs controlled by a control file. However, certain
options in other sections of the control file can override the global setting or are unique to that
section. For more information, refer to
“Global Options Table” (page 125) .
The control file consists of these sections:
Creating a Control File 27