After SQL messages occur (SQLSTATEs), diagnostic information is stored in error files (exception files) after the following UTILITY statements:
ALTER TABLEThe error file is defined in the SQL statement ALTER TABLE via the USING FILE parameter. Amongst other things, this file contains column values for which conversion errors resulted in data loss due to a change in data type (see the “ SQL Reference Manual Part 1: SQL Statements”).
CHECK FORMAL {SPACE | TABLE}The error file is created by SESAM/SQL when required. Amongst other things, it contains the respective SQLSTATE which is set on detection of the first inconsistency of the object to be checked (see the “ SQL Reference Manual Part 2: Utilities”).
LOAD The error file is defined in the utility statement LOAD via the USING FILE parameter. It contains information on the erroneous records of the input file used, and indicates the cause of the error (see the “ SQL Reference Manual Part 2: Utilities”).
UNLOADThe is created by SESAM/SQL as required (see the “ SQL Reference Manual Part 2: Utilities”).
The error files are SAM files whose data block length is four PAM pages. You can view the error files using the BS2000 command SHOW-FILE or load them using the EDT.
If an SQLSTATE occurs after the CHECK FORMAL utility statement (see the “ SQL Reference Manual Part 2: Utilities”), the copy of the checked space can help in the error analysis in addition to the error file.