JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

Unsupported SQL/MP Features
• SQL/MP DDL support
• Columns described with the character sets ISO8859/2 through ISO8859/9
• Utility commands
• Embedded-only SQL/MP statements
• Transaction Control statements
• Stored procedures
Refer to the NonStop SQL/MP documentation set for a complete list of supported features.
Other Unsupported Features
These features are not required for JDBC 3.0 compliance, and they are not supported by the
NonStop JDBC Type 4 Driver.
• Multiple result sets returned by batch statements.
• Database savepoint support. (Not provided in SQL/MX)
• Retrieval of auto generated keys.
• Transform group and type mapping.
• Relationship between connector architecture and JDBC 3.0 SPI.
• Secured socket communication or encryption for the interaction between the NonStop JDBC
Type 4 Driver and MXCS. However, secure socket communication or encryption for
Windows-based clients are supported. For more information, see “Providing a secure JDBC
connection using NonStop SSL” (page 108)
• Security context (user name and password) implicit propagation from AppServer to the NonStop
JDBC Type 4 Driver.
• IPV6 protocol stack. (IPV6 addressing is emulated over IPV4 on the MXCS server side)
Restrictions
• The Type 4 driver supports only database features that are supported by NonStop SQL/MX
and SPJ. Therefore, the Type 4 driver is not fully compliant with JDBC 3.0 specifications.
• The Type 4 driver depends on MXCS for all server side manageability related features.
• JDBC Type 4 Driver for SQL/MX Release 3.x cannot connect to a NonStop system running a
SQL/MX Release 2.x version of MXCS server objects.
java.sql.connection.setAutoCommit(boolean autoCommit())
Sets the auto-commit mode of this connection to the given state (true or false). If a connection is in
auto-commit mode, then the SQL statements will be executed and committed as individual
transactions. Otherwise, the SQL statements are grouped into transactions that are terminated by
a call to either the method commit or method rollback. By default, new connections are in
auto-commit mode. If the value of auto-commit is changed in the middle of a transaction, the current
transaction is committed. If setAutoCommit is called and the value for auto-commit is not changed
from its current value, it is treated as a NO-OP.
80 Type 4 Driver Compliance