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

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—544517-008
5-30
import Utility
If the -LES option is specified and any -L, -XL, -E, -XE, -PM, -XM, or -SF options
are also specified, the value(s) specified for the individual options overrides the
default value, which the -LES option establishes. The default values established
by the -LES option is applicable for any of the seven individual options, which are
not specified on the command line.
All error output filenames, including any that are automatically chosen by import,
is reported in the results summary file output.
-PM parsing-errormsg-filename
is an option that specifies the pathname parsing-errormsg-filename of an
OSS output file to which import logs the error messages that correspond with the
logged data rows that have parsing errors. The name of the error message file
must be specified in OSS format, for example /usr/jdoe/errfile, may be the
same as the one specified with the -E option, but must not be the same as any
other output file.
This output file is created by the import utility as a non-audited, OSS
unstructured file (or a Guardian file of type 180 if the error log file is specified to be
under /G). If the file already exists, import terminates with an error message. If
the -PM option is not specified, the error messages corresponding to rows with
parsing errors are not logged. If the -PM option is specified, but the -E option is
not, import terminates with an error message.
If parsing-errormsg-filename and error-filename are specified to be the same file,
import logs each error message to the error log file, prefixed by the string
^@ERR_ST]^ and suffixed by the string ^\[ERR_ND^, and by a row delimiter if the
input file is a delimited file. The corresponding row in error immediately follows.
If the -Z option is used to specify that the input file contains characters other than
ISO88591, and parsing-errormsg-filename and error-filename are
specified to be the same file, import will terminate with an error message.
If parsing-errormsg-filename and error-filename are not the same file,
the error messages in the error message file will be in the same order as the
corresponding logged rows in error in the error file. This is sufficient to allow the
user to determine the corresponding error message for any particular row in error-
filename.
The error messages written to parsing-errormsg-filename do not have any
row numbers to indicate the row in error-filename associated with the error
message. However, some parsing error messages do have a row number
indicating the associated row in the input file.
Regardless of whether parsing-errormsg-filename and error-filename
are the same file, if you invoke import again, with error-filename as the input
file, the same format file can be used. Any interspersed error messages are
automatically ignored by import. You must specify the same file type (DELIM or
FIXED) when using error-filename, as was used for the original input file.