JDBC Type 4 Driver 1.1 Programmer's Reference

Type 4 driver, through the MXCS Service, Accesses an SQL/MX Database
Samples
The following samples are provided with the Type 4 driver.
Sample Description
CallableStatementSample Demonstrates the invocation of a stored procedure in Java (SPJ).(1)
DBMetaSample
Gets metadata from a table by using the Connection interface and
ResultSetMetaData interface. The information retrieved includes
Type, (of what getTypeInfo()), catalogs, tables, procedures,
columns, columns, column count on tables, and so forth.(1)
PreparedStatementSample
Using the PreparedStatement interface, performs a select all and
parameterized select for data type of CHAR, INT, TIMESTAMP,
DECIMAL, NUMERIC, and DATE.(1)
ResultSetSample
Executes a simple select statement, metadata information about the
result set returned by the simple select statement, and finally, uses
the result-set metadata to print out each row returned by the simple
select statement.(1)
SQLMPSample
Executes a simple select statement on an SQL/MP table, retrieves
metadata information about the result set returned by the simple
select statement, and, uses the result-set metadata to print out each
row returned by the simple select statement. (Access an existing
SQL/MP table through the SQL/MX engine.)
StatementSample
Executes a simple select statement, retrieves metadata information
about the result set returned by the simple select statement, and
uses the result-set metadata to print out each row returned by the
simple select statement.(1)
WLS_MedRecSample
Demonstrates that a J2EE application built to work with a database
like Oracle can work with NonStop SQL/MX by just reconfiguring
the application in BEA WebLogic Server. No coding changes or
recompilation are required to switch to NonStop SQL/MX from a
different relational database management system (RDBMS).(2)
WLS_TwoPhaseAndPoolingSample
Demonstrates:
That configured as a non-XA driver emulating two-phase
commit in BEA WebLogic Server 8.1, the Type 4 driver can
participate in a two-phase commit.(2)
●
Connected pooling, particularly that the number physical
connections created does not exceed the maximum number
of physical connections configured in BEA WebLogic Server
8.1.(2)
●