JDBC Driver for SQL/MP 3.0

The
Blob map file
parameter is required to successfully run the Cleanup utility. As an option, an error file can be
provided to log any errors encountered during cleanup.
Note: The Guardian name of the BLOB map file (in the $volume.subvolume.filename format) must be
provided to the Cleanup utility. The Blob map file name must be enclosed in single quotes so that it is
not interpreted by the OSS shell. For example:
java com.tandem.sqlmp.SQLMPBlobCleanup '$myvol.blobs.mapfile' err
JDBC 2.0 Standard Extensions
The enhancements to the JDBC 2.0 Standard Extension API include these:
JNDI for naming databases
Distributed transaction support
JNDI for Naming Databases
JNDI (Java Naming and Directory Interface) enables an application to specify a logical name that JNDI associates with
a particular data source. Using JNDI solves these problems.
For JDBC 1.0, using the JDBC driver manager was the only way to connect to a database. With the JDBC 1.0
approach, the JDBC driver that creates a database connection must first be registered with the JDBC driver manager.
However, the JDBC driver class name often identifies a driver vendor whose code loads a driver specific to that
vendor's product. The code, therefore, is not portable. In addition, an application needs to specify a JDBC URL when
connecting to a database by means of the driver manager. This URL might not only be specific to a particular vendor's
JDBC product, but for databases other than SQL/MP, the URL might also be specific to a particular computer name
and port.
A JDBC data source object is a Java programming language object that implements the DataSource interface. A data
source object is a factory for JDBC connections. Like other interfaces in the JDBC API, implementations of
DataSource must be supplied by JDBC driver vendors.
JDBC Data Source Properties
The JDBC 2.0 API specifies these standard names for data source properties:
DatabaseName
DataSourceName
Description
Network Protocol
Password
RoleName
ServerName
UserName
All these data source properties are of type String, and all are optional except the Description property, which is
required to provide a description of the data source. The NonStop Server for Java includes the property
TransactionMode, also of type String. Acceptable values for that property are INTERNAL or EXTERNAL. If you specify
INTERNAL, JDBC manages (begins, ends, rolls back) transactions within the connection. If you specify EXTERNAL, you
are responsible for beginning and ending transactions.