Database Data File Record Format; Field Position And Field Length Example 1; Field Position And Field Length Example 2 - HP StorageWorks P9000 User Manual

• The position of the fields to be converted, the type of conversion to be performed on those
fields, how the result should be edited and output to the output record, and the length of the
output field will be specified.
• A Field Definition file will be created for each record format (field configuration) found in the
database data file to be converted. For each field in the input record, position, length, type
of code conversion to be performed, and output length are specified in the prescribed format.
3. Use the Parameter Definition file to associate the Field Definition file with the database data file.
• Parameter Definition files are used to associate Field Definition files with the database data
file to be converted. The Parameter Definition file is used by the File Conversion Utility to
specify the database data files for mto conversion or otm conversion (a pair of files: Mainframe
SAM file and an open systems UNIX/PC file).
• Describe the Parameter Definition file in text file form.
4. Execute/run the File Conversion Utility.

Database Data File Record Format

When using Code Converter to perform conversions such as double-byte conversions, the database
data file must be a sequential access method file (SAM) with fixed-length or variable-length records.
In addition, the field positions within the records must be fixed and consistent. You must confirm the
record formats of the Mainframe file and the open systems file.
Code Converter retrieves input data from a fixed position within each record. The field position within
the record and the field length must be the same for all records, as shown in
17 (for example, SAM file output by the DB2 REORG utility).
Figure 16 Field Position and Field Length Example 1
.
Figure 17 Field Position and Field Length Example 2
.
The following figure illustrates the record formats supported and conversion modes provided by the
Data Exchange Code Converter.
38 Using Data Exchange Code Converter
Figure 16 and Figure