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

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—544517-008
5-49
Output File Consideration
File permissions
When import creates any of the error output files, import ensures that the
permissions are set so that read and write permission is granted only for the current
user and his/her group because these files may have user data that is confidential.
Read and write permission for the current user and/or the group may be further
restricted depending on the umask setting at the time of the file creations. If any of the
error output files is created under the /G directory, the Guardian file access codes shall
be set to "CCCU", which will prevent any user other than the owner and his/her group
from reading or writing to the file.
Displaying messages
import uses the existing error message to display capability when it encounters any
error.
Output File Consideration
Non-ignorable execution errors
Inserting a row into a table may be a multi-step process. This involves inserting the row
into the base table and may also require adding a row to one or more index
tables,checking referential integrity constraints, performing trigger actions,and so on.
Some execution errors are detected after a row has been inserted into the target's
base table. These include any uniqueness constraints that are enforced by an index,
referential integrity constraints, and errors detected while performing trigger actions.
Other such errors include those returned by DP2, TMF, and other low level
components such as file full conditions, audit file full, or network errors. If any error is
encountered after the row has been inserted into the base table, the error cannot be
ignored and the IMPORT utility shall terminate just as it does in the current release.
The row contents of the error log file are the same as the input file. However, the
position of rows may differ.
Rows in the parsing error log file 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:
30 No success and no ignorable errors
40 No success and ignorable errors encountered
50 No success and a serious problem encountered
70 Serious problems that prevent the import from starting
90 Invalid option or combination of options