NonStop Server for Java (NSJ) Programmer's Guide (NSJ 2.1+)

is the name of a file to which any errors encountered during cleanup will be logged.
The Blob map file parameter is required to successfully run the Cleanup utility. The error file can optionally 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 Sun Microsystems document that describes the JDBC 2.0 Standard Extension API has not been finalized. The following
information describes the current content of that document.
The enhancements to the JDBC 2.0 Standard Extension API include the following:
JNDI for naming databases●
Connection pooling●
Distributed transaction support●
JNDI for Naming Databases
For JDBC 1.0, the only way to connect to a database was by using the JDBC driver manager. With this approach, the JDBC
driver that is used to create a database connection must first be registered with the JDBC driver manager. A drawback of this
approach is that the JDBC driver class name usually identifies a particular JDBC driver vendor that makes the code that loads
the driver specific to that vendor's product. It is therefore 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) it might also be specific to a particular computer name and
port.
Using JNDI (Java Naming and Directory Interface) solves these problems by allowing an application to specify a logical name
that JNDI associates with a particular data source.
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 the following standard names for data source properties:
DatabaseName●
DataSourceName●
Description●
Network Protocol●
Password●
RoleName●
ServerName●
UserName●
All of 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. NonStop 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.