Standards compliance
Db2® for i 7.2 conforms with IBM® and Industry SQL Standards.
Distributed relational database architecture
- Open Group Publications: DRDA V5 Vol. 1: Distributed Relational Database Architecture(DRDA), at https://www2.opengroup.org/ogsys/catalog/C112
- Open Group Publications: DRDA V5 Vol. 2: Formatted Data Object Content Architecture(FD:OCA), at https://www2.opengroup.org/ogsys/catalog/C113
- Open Group Publications: DRDA V5 Vol. 3: Distributed Data Management Architecture (DDM), at https://www2.opengroup.org/ogsys/catalog/C114
Character data representation architecture
- Character Data Representation Architecture Reference and Registry, at http://www-01.ibm.com/software/globalization/cdra/
Unicode standard
- The Unicode Standard, at http://www.unicode.org
SQL standards
Db2 for i 7.2 conforms with the following industry standards for SQL:
- ISO/IEC 9075-1:2016, Information technology - Database languages - SQL - Part 1: Framework (SQL/Framework)
- ISO/IEC 9075-2:2016, Information technology - Database languages - SQL - Part 2: Foundation (SQL/Foundation)
- ISO/IEC 9075-3:2016, Information technology - Database languages - SQL - Part 3: Call-Level Interface (SQL/CLI)
- ISO/IEC 9075-4:2016, Information technology - Database languages - SQL - Part 4: Persistent Stored Modules (SQL/PSM)
- ISO/IEC 9075-10:2016, Information technology - Database languages - SQL - Part 10: Object Language Bindings (SQL/OLB)
- ISO/IEC 9075-11:2016, Information technology - Database languages - SQL - Part 11: Information and Definition Schemas (SQL/Schemata)
- ISO/IEC 9075-14:2016, Information technology - Database languages - SQL - Part 14: XML-Related Specifications (SQL/XML)
Db2 for
i 7.2
conforms with the following industry technical report for SQL:
- ISO/IEC TR 19075-6:2016, Information technology
- Database languages - SQL Technical Reports - Part 6: SQL support
for JavaScript Object Notation (JSON)
For strict adherence to the standards, consider using
the standards options. Standards options can be specified through
the following 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 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 IBM 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 IBM 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 IBM 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 IBM i Access.) (For more information about the IBM Toolbox for Java, see IBM Toolbox for Java.) |