SQL return codes

The GET DIAGNOSTICS statement can be used in all languages to return return codes and other information about the previous SQL statement. For more information, see GET DIAGNOSTICS.

Additionally, each host language provides a mechanism for handling SQL return codes:

• In C, COBOL, FORTRAN, and PL/I, an application program containing executable SQL statements must provide at least one of the following:
  • A structure named SQLCA.
  • A stand-alone CHAR(5) (CHAR(6) in C) variable named SQLSTATE (SQLSTA or SQLSTATE in FORTRAN).
  • A stand-alone integer variable named SQLCODE (SQLCOD in FORTRAN).
  A stand-alone SQLSTATE or SQLCODE must not be declared in a host structure. Both a stand-alone SQLSTATE and SQLCODE may be provided.

  An SQLCA can be obtained by using the INCLUDE SQLCA statement. If an SQLCA is provided, neither a stand-alone SQLSTATE or SQLCODE can be provided. The SQLCA includes a character-string variable named SQLSTATE (SQLSTT in FORTRAN) and an integer variable named SQLCODE (SQLCOD in FORTRAN) .

  A stand-alone SQLSTATE should be used to conform with the SQL 1999 Core standard.

• In Java™, for error conditions, the getSQLState method can be used to get the SQLSTATE and the getErrorCode method can be used to get the SQLCODE.
• In REXX and RPG, an SQLCA is provided automatically.

SQLSTATE

Regardless of whether the application program provides an SQLCA or a stand-alone variable, SQLSTATE is also set by the database manager after execution of each SQL statement. Thus, application programs can check the execution of SQL statements by testing SQLSTATE instead of SQLCODE.

SQLSTATE provides application programs with common codes for common error conditions. Furthermore, SQLSTATE is designed so that application programs can test for specific errors or classes of errors. The scheme is the same for all database managers and is based on the ISO/ANSI SQL 2003 Core standard. A complete list of SQLSTATE classes and SQLSTATEs associated with each SQLCODE is supplied in the SQL Messages and Codes book in the iSeries Information Center.

SQLCODE

The SQLCODE is also set by the database manager after each SQL statement is executed as follows:

• If SQLCODE = 0 and SQLWARN0 is blank, execution was successful.
• If SQLCODE = 100, no data was found. For example, a FETCH statement returned no data, because the cursor was positioned after the last row of the result table.
• If SQLCODE > 0 and not = 100, execution was successful with a warning.
• If SQLCODE = 0 and SQLWARN0 = 'W', execution was successful with a warning.
• If SQLCODE < 0, execution was not successful.

A complete listing of DB2 UDB for iSeries SQLCODEs and their corresponding SQLSTATEs is provided in the SQL Messages and Codes book in the iSeries Information Center.