SQL/MX 2.x Installation and Management Guide (H06.10+, J06.03+)
Reorganizing SQL/MX Tables and Maintaining Data
HP NonStop SQL/MX Installation and Management Guide—544536-007
10-25
Summary of import Options
For more information about these and other import command options, see the
SQL/MX Reference Manual.
Format File Considerations for import
For more information about format file structures and field options for import, see the
SQL/MX Reference Manual.
Format File for a DELIM Input File
If the input file type is DELIM and you want to use a format file, you must include the
[COLUMN FORMAT] section. The other sections are optional.
Format File for a FIXED Input File
If the input file type is FIXED, you must specify a format file that includes the
[COLUMN FORMAT] and [FIXED WIDTH FORMAT] sections. The columns listed in
the [COLUMN FORMAT] section must match the columns listed in the [FIXED WIDTH
FORMAT] section. The other sections are optional.
Input File Considerations for import
Fixed Input File
In a fixed input file, specified by using the -W FIXED option, different columns can
have different lengths. But for each column, all rows must be the same length. You
should pad column values that are shorter than the column width with spaces or
NullValue characters to ensure that every row has exactly the same number of bytes
for a given column.
Delimited Input File
A delimited input file, specified by using the -W DELIM option or by default, uses field
and row delimiters and field qualifiers if needed. If you specify a format file, import
uses the delimiters in the file unless you also specify delimeters on the import
command line, in which case the command line specifications are used.
If you do not specify a format file, import uses the default delimiters described in the
SQL/MX Reference Manual.
For information about other input file considerations, including using a field qualifier,
field delimeter, row delimeter, or record delimeter, see the SQL/MX Reference Manual.
Output File Considerations for import
IEH-F-LIM-20 [IMP-EH-LIM-80] Contents of logged execution error rows only
approximate.
Rows in the parsing error log file must look exactly like the corresponding row in the
input file. However, rows in the execution error log file may not look like the
corresponding row in the input file. Four notable cases are:










