SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—544517-008
5-50
Output File Consideration
1. The format of numbers may be changed.
For example: 123456.7 in the original input file may appear as 1.234567E+05 in
the error log file.
2. The value of some floating point numbers may not be exactly the same (though
extremely close). This is due to an internal conversion to binary format and then
back to floating point ASCII format for logging to the error log file.
3. Any string which includes the field delimiter, the row delimiter, or the field-qualifier
character may appear different.
For example, if the field qualifier is a double-quote character (")
Use a double-quote("") <in the original input file>
will reflect as
"Use a double-quote(")" <in the error log file>
4. If the format file is said to skip column 1 of each row in the original input file, the
data in column 1 will not be displayed in the execution error log file.
For example:
"Data for a manager", 378456, Comm. Dept, 125 <in the original input file>
will reflect as
, 378456, Comm. Dept, 125 <in the error log file>
If the format file is said to skip a column in the middle of each row, the same would
be indicated by consecutive Field Delimiter characters in execution error log rows.
If the input file has fixed-width columns instead of field delimiters, the rows in the
execution error log file would contain all NullValue characters (as specified in the
format file or space by default) for any skipped columns.
Although the appearance of such rows will be different in the execution error log
than in the input file, these rows in the error log can still be used to import to the
destination table without requiring you to fix these appearance differences. The
real problem that caused the row to get an execution error would need to be fixed
by you. However, these appearance differences do not require fixing before the
row can be imported. Such appearance differences do not affect the column values
in the destination table. The only possible exception to this would be if the
miniscule change in the value of a floating point number is considered to be
significant.
Note. The leading comma (Field Delimiter character) indicates that the first field is
missing.