Figure 23 Overview of Code Conversion in Variable Length Records (with “end” specified for field
length)
.
• You can specify “end” in the Field Definition file only when the field is the last field of the record.
When “end” is specified, code conversion for the last field starts at the beginning of the field
and ends at the end of the record. In Figure 23, “end” is specified for Field 2, indicated by
the grey areas.
Converting Variable Length UNIX/PC Records to Fixed Length Mainframe Records (otm)
After removing the delimiters in the variable length UNIX/PC records, code conversion is performed
on each field, and the result is output to the Mainframe in fixed length record format.
Padding and delimiter must be specified in the end statement of the Field Definition file.
After code conversion, the extra space in the Mainframe record is padded with the padding code
specified. The extra space in each field is filled with the field padding code specified in the Edit
Option file. The total length of the output fields defined in the field definition must be less than the
fixed length of the Mainframe record.
NOTE:
Mainframe records with padding cannot be reconverted to UNIX/PC records using mto conversion.
• Fixed field length: The following figure shows how otm code conversion is performed when the
fields specified in the field definition statement have a fixed length (when “end” is not specified
for the input field length). Delimiters are not output to the Mainframe records.
Using Data Exchange Code Converter42
To Next Page
Loading...
Need help?
General