Standards compliance

Start of changeDB2® for i 7.1 conforms with IBM® and Industry SQL Standards.End of change

Start of changeEnd of change
For strict adherence to the standards, consider using the standards options. Standards options can be specified through the following interfaces:
Table 1. Standards Option Interfaces
SQL Interface Specification
Embedded SQL SQLCURRULE(*STD) parameter on the Create SQL Program (CRTSQLxxx) commands. The SET OPTION statement can also be used to set the SQLCURRULE values.

(For more information about CRTSQLxxx commands, see Embedded SQL Programming.)
Run SQL Statements SQLCURRULE(*STD) parameter on the Run SQL Statements (RUNSQLSTM) command.

(For more information about the RUNSQLSTM command, see SQL Programming.)
Call Level Interface (CLI) on the server SQL_ATTR_HEX_LITERALS connection attribute

(For more information about CLI, see SQL Call Level Interfaces (ODBC).)
JDBC or SQLJ on the server using IBM Developer Kit for Java™ Translate Hex connection property object

(For more information about JDBC and SQLJ, see IBM Developer Kit for Java.)
ODBC on a client using the IBM i Access Family ODBC Driver Hex Parser Option in ODBC Setup

(For more information about ODBC, see System i® Access.)
OLE DB on a client using the IBM i Access Family OLE DB Provider Hex Parser Option Connection Object Properties

(For more information about OLE DB, see System i Access.)
ADO .NET on a client using the IBM i Access Family ADO .NET Provider HexParserOption in Connection Object Properties

(For more information about ADO .NET, see System i Access.)
JDBC on a client using the IBM Toolbox for Java Interpret SQL hexadecimal constants as binary data in JDBC Setup

(For more information about JDBC, see System i Access.)

(For more information about the IBM Toolbox for Java, see IBM Toolbox for Java.)