JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

on an exception. By this, re-execution of entire jobs is avoided. However, for any TMF errors, that
results in transaction failure, cannot be addressed by this enhancement.
DatabaseMetaData Calls
For the DatabaseMetaData calls, specify the catalog and schema values. If you do not specify
these values, the JDBC/MX driver uses the following default values:
catalog = NONSTOP_SQLMX_NSK;
schema = PUBLIC_ACCESS_SCHEMA;
HP Extensions
The following HP extensions to the JDBC standard are implemented in the JDBC/MX driver.
Interval Data Type
The interval data type is not a generic SQL type defined in the Java 2 JDBC 3.0 Specification,
but SQL/MX supports the interval data type. To allow JDBC applications for SQL/MX to access
the interval data type, the JDBC/MX driver maps it to the Types.OTHER data type. The
JDBC/MX driver enables the getObject() and getString() methods of the ResultSet
interface, and the setObject() and setString() methods of the PreparedStatement
interface, to access this data type. The interval data type is always accessed as a String
object. The JDBC/MX driver also allows escape syntax for interval literals.
Internationalization
The JDBC/MX driver is designed so that Java messages can be adopted for various languages.
The error messages in JDBC/MX components are stored outside the source code in a separate
property file and retrieved dynamically based on the locale setting. The error messages in different
languages are stored in separate property files based on the language and country. This extension
does not apply to all messages that can occur when running JDBC applications.
SQL Conformance
JDBC/MX conforms to the SQL language entry level of SQL:1999. This subsection describes the
JDBC/MX support for:
• “SQL Scalar Functions” (page 68)
• “CONVERT Function” (page 71)
• “JDBC Data Types” (page 71)
• “Floating-Point Support” (page 72)
• “SQL Escape Clauses” (page 73)
SQL Scalar Functions
JDBC/MX maps JDBC scalar functions to their equivalent SQL/MX functions, as shown in the
following tables:
Table 9 Numeric Functions
SQL/MX Equivalent FunctionJDBC Function
ABSABS
ACOSACOS
ASINASIN
ATANATAN
68 JDBC/MX Compliance