JDBC/MP Doc Home Page HP JDBC Driver for SQL/MP Programmer's Reference Abstract This document describes how to use the JDBC Driver for SQL/MP (JDBC/MP) on HP NonStop™ servers. JDBC/MP provides HP NonStop Server for Java applications with JDBC access to HP NonStop SQL/MP. JDBC/MP driver conforms where applicable to the standard JDBC 3.0 API from Sun Microsystems, Inc.
As the original purchaser of this documentation set, you are hereby expressly granted a nontransferable license to make and use copies of the information contained herein for confidential, internal use by yourself and your employees. Legal Notices Copyright 2013 Hewlett-Packard Development Company L.P.
otherwise licensed by Hewlett-Packard Company. RESTRICTED RIGHTS LEGEND Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013. Hewlett-Packard Development Company L.P. 10600 Ridgeview Court Cupertino, CA 95014 USA Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2).
HP JDBC Driver for SQL/MP API and Reference Documentation on both NTL and the product CD: HP JDBC Driver for SQL/MP Programmer's Reference HP JDBC Driver for SQL/MP API Reference Pages Documentation on the product CD only: Software Release Documents README File Product Version HP JDBC Driver for SQL/MP(JDBC/MP)V30 and H10 Supported Hardware All HP NonStop™ all NonStop S-series servers except S700B and S70000 and all HP NonstopNS-series servers Supported Release Version Updates (RVUs) This manual supports G0
JDBC/MP Doc Home Page JDBC Driver for SQL/MP Programmer's Reference Contents About This Document New and Changed Information Is This Document for You? Document Structure Printing This Document Related Reading NonStop System Computing Documents Sun Microsystems Documents Notation Conventions Abbreviations Introduction to JDBC/MP Driver JDBC Driver Types JDBC/MP Architecture JDBC/MP API Packages Limitation Installing and Verifying JDBC/MP JDBC/MP Driver Requirements Verifying the JDBC/MP Driver Accessing SQ
Compatible Java and SQL/MP Data Types Referring to Database Objects When You Can Use Aliases Creating and Using Aliases Which SQL Statements Support Aliases Connection Pooling and the Application Server Guidelines for Implementing an Application Server to Use Connection Pooling Standard ConnectionPoolDataSource Object Properties Registering the ConnectionPoolDataSource and DataSource with a JNDI-Based Name Service Connection Pooling in a Basic DataSource Implementation Basic DataSource Object Properties Req
List of Tables JDBC/MP Doc Home Page HP JDBC Driver for SQL/MP Programmer's Reference (527401-004) Copyright © 2013, Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MP Docs Home Page | Contents | Index | Glossary | Prev | Next About This Document This section explains these subjects: New and Changed Information Is This Document for You? Document Structure Printing This Document Related Reading Notation Conventions Abbreviations New and Changed Information This edition, 527401-004 includes the following changes: Added installation details to Installing and Verifying JDBC/MP.
Document Structure This document is a set of linked HTML files (Web pages). Each file corresponds to one of the sections listed and described in this table: Document Sections Section Description Table of Contents shows the structure of this document in outline form. Each section and subsection name is a link to that section or subsection.
Note: Some browsers require that you reduce the print size to print all the text displayed on the screen. Related Reading For background information about the features described in this guide, see these documents: HP NonStop JDBC/MP Driver API and Reference (javadoc comments on the JDBC/MP APIs) NonStop System Computing Documents Sun Microsystems Documents NonStop System Computing Documents These NonStop system computing documents are available on the NonStop Technical Library (NTL).
This document describes how to use the JDBC Driver for SQL/MX (JDBC/MX) on NonStop servers. JDBC/MX provides NonStop Server for Java applications with JDBC access to NonStop SQL/MX. Inspect Manual Documents the Inspect interactive symbolic debugger for HP NonStop systems. You can use Inspect to debug Java Native Interface (JNI) code running in a Java virtual machine (JVM).
SQL/MP Version Management Guide Explains the rules that govern version management for the NonStop SQL software, catalogs, objects, messages, programs, and data structures. SQL/MP Messages Manual Explains NonStop SQL/MP messages for the conversational interface, the application programming interface (API), and the utilities. SQL/MP Programming Manual for C Describes the SQL/MP programmatic interface for ANSI C. Also describes embedded SQL statements used in C applications.
Note: Sun Microsystems Java 2 SDK, Standard Edition, Version 1.4.1 documentation is provided on the NonStop Server for Java product distribution CD for your convenience if you cannot get Java documentation from the Sun Microsystems Web sites. For more information, see the NonStop Server for Java Programmer's Reference. Notation Conventions Bold Type Bold type within text indicates terms defined in the Glossary.
Parentheses, commas, equal signs, and other symbols not previously described must be entered as shown. For example: -D propertyName=newValue Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or comma. If there is no space between two items, spaces are not permitted. In this example, spaces are not permitted before or after the period: subvolume-name.
JFC. Java Foundation Classes JDBC. Java Database Connectivity JDBC/MP. JDBC Driver for SQL/MP JDBC/MX. JDBC Driver for SQL/MX JDK. Java Development Kit JNDI. Java Naming and Directory Interface JNI. Java Native Interface JRE. Java Run-time Environment LAN. local area network NonStop TS/MP. NonStop Transaction Services/MP NTL. NonStop Technical Library OSS. Open System Services POSIX. portable operating system interface x RISC. reduced instruction set computing RVU. Release Version Update SQL/MP.
JDBC/MP Docs Home Page | Contents | Index | Glossary | Prev | Next Introduction to JDBC/MP Driver The HP JDBC Driver for SQL/MP (JDBC/MP) implements the JDBC technology that conforms to the standard JDBC 3.0 Data Access API. This JDBC/MP driver enables Java applications to use HP NonStop SQL/MP to access NonStop SQL databases. For more information on the JDBC APIs associated with the JDBC/MP implementation, see Sun Microsystems Documents.
Note: HP does not support third-party JDBC drivers for NonStop systems, but any JDBC driver that is written entirely in Java (that is, a Type 3 or a Type 4 driver) can run on top of the NonStop Server for Java. To use such a driver to connect your Java program to a third-party database, see the third-party instructions for that driver. JDBC/MP Architecture The JDBC/MP driver is a Type 2 driver; it employs proprietary, native APIs to use SQL/MP to access NonStop SQL databases.
are available with the core APIs delivered with the NonStop Server for Java product. Limitation In TNS/E, applications cannot have their own embedded SQL code. An application using the JDBC/MP driver cannot have any other object with embedded SQL code linked to it. JDBC/MP Docs Home Page | Contents | Index | Glossary | Prev | Next HP JDBC Driver for SQL/MP Programmer's Reference (527401-004) Copyright © 2013, Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MP Docs Home Page | Contents | Index | Glossary | Prev | Next Installing and Verifying JDBC/MP This section explains these subjects: JDBC/MP Driver Requirements Installing the driver Verifying the JDBC/MP Driver JDBC/MP Driver Requirements Before using the JDBC Driver for SQL/MP, the product components must be installed and the Java virtual machine (JVM) must be compiled by the SQL compiler. In TNS/E, JVM must not be recompiled by the SQL compiler.
The PINSTALL command extracts the JDBC/MP jar(sqlmp.jar) and native library (libsqlmp.so) to the /jdbcMp/T1277H32/lib directory. Installing the Driver from Scout Download the product files from Scout to your Windows system. Perform the following steps to install the driver: 1. Perform the following steps to transfer the pax files from your Windows system to the NonStop system: 1. Launch the FTP client application. 2.
To verify the SQL/MP driver after installation, run the Sample SQL/MP Program. Note for TNS/E: The libsqlmp.lib file no longer exists in JDBC/MP 3.0. The libsqlmp.lib file is replaced by the libsqlmp.so file that is copied in the $JDBCHOME/T1277H10/current/lib directory. JDBC installation dependency on the java_public_lib directory is now removed. The SQL compile operation is now executed on the libsqlmp.so file when installing JDBC/MP.
Java Docs Home Page | Contents | Index | Glossary | Prev | Next Accessing SQL Databases with SQL/MP Java programs interact with NonStop SQL databases using NonStop SQL/MP and the Java Database Connectivity (JDBC) API. The NonStop Server for Java and the JDBC Driver for SQL/MP include these items: The JDBC 3.0 API The JDBC DriverManager in the Java Development Kit (JDK) 1.4.
PreparedStatement stmt; stmt = conn.prepareStatement("insert into foo values(?,?,??); Note that the last two question marks are not separated by commas; the first question mark of the pair indicates that a value can be set for this column (the deptnum column, as these question marks appear in the third position) and the second is the null indicator, showing that the column can be set to null. If the second question mark is not present, the column could not be set to null.
The JDBC DriverManager maintains a list of available JDBC drivers. When a program calls the getConnection method, the JDBC DriverManager searches this list and connects the calling program to the appropriate JDBC driver. Loading a Driver To load a JDBC driver, load its JDBC driver class into the Java Virtual Machine (JVM) in one of these ways: Specify the JDBC driver class on the java command line. Add the JDBC driver class to the jdbc.drivers property. Load the JDBC driver class directly into the JVM.
Specifying the JDBC Driver Class on the java Command Line To specify the JDBC driver class on the java command line, use the -Djdbc.drivers option. For example, this java command loads the SQL/MP driver, whose class name is com.tandem.sqlmp.SQLMPDriver : java -Djdbc.drivers=com.tandem.sqlmp.SQLMPDriver To specify multiple JDBC driver classes on the java command line, separate them with semicolons. For example, this java command loads the SQL/MP driver and a driver whose class name is com.javaco.
Standard Driver Example In a Java program, this code uses the standard driver, sqlmp , to create a connection ( myConnection) between the program and the local SQL/MP database: import java.sql.*; ... Connection myConnection = DriverManager.getConnection("jdbc:sqlmp:"); Note: You must specify the URL for the driver exactly as it is shown in this and these examples.
Compatible Java and SQL/MP Data Types This table shows which Java data types can hold which SQL/MP data types. Use this table to determine which get() method to call to read a particular type of data from a result set or which set() method to call to define the data type of a prepared statement's input parameter. For example, if you select CHAR data from a database, use getString() to retrieve the CHAR data from the result set.
Legend R Recommended s Supported n Not supported for current release Referring to Database Objects By default, the SQL/MP driver uses Guardian file names for SQL/MP database objects, as this table shows. Default SQL/MP Database Object Names Database Object Catalog Default Name * [\node.][$volume.]subvol Index [\node.][[$volume.]subvol.]fileID Examples $sqldata.sales \tokyo.$disk02.sqlcat emptab $sqldisk.fy02.xsalary \newyork.$sqldisk.fy02.
Creating and Using Aliases To create and use aliases: 1. Create a java.util.Properties object. 2. Put each alias-Guardian file-name pair (called a substitution property) in the java.util.Properties object. Prefix each alias with a plus sign (+). The individual put() calls for this step can be either in your program. Note: Previous versions of the NonStop Server for Java used an equal sign ( =) instead of a plus sign.
// Create a java.util.Properties object named prop java.util.Properties prop=new java.util.Properties(); // Load the file that creates the aliases prop.load("jdbc-properties"); // Connect the program to the database, passing prop conn = DriverManager.getConnection("jdbc:sqlmp:", prop); // Create an SQL statement stmt = conn.createStatement(); // Use the aliases instead of their Guardian filenames rslt = stmt.executeQuery("select * from longname1 where col1='pickme'"); rslt = stmt.
In the Data Manipulation Language (DML): DECLARE CURSOR DELETE INSERT SELECT UPDATE Substitution also works on subqueries. The alias substitution mechanism does not substitute Guardian file names and Guardian DEFINEs. If your SQL query uses a DEFINE, you cannot use this alias substitution mechanism. In this example, no alias substitution is possible: select =jobcode, =deptnum, =first_name, =last_name from persnl.
the proper PooledConnection object. The lookup criteria and other methods are specific to the application server. The application server implements the ConnectionEventListener interface and registers the listener object with the PooledConnection object. The JDBC/MP driver notifies the listener object with a connectionClosed event when the application is finished using the PooledConnection object. Then, the application server can reuse this PooledConnection object for future requests.
In an environment that uses an application server, deployment of an SQLMPConnectionPoolDataSource object requires that both an application-visible DataSource object and the underlying SQLMPConnectionPoolDataSource object be registered with a JNDI-based naming service. The first step is to deploy the SQLMPConnectionPoolDataSource implementation, as is done in this code example: com.tandem.sqlmp.SQLMPConnectionPoolDataSource cpds = new com.tandem.sqlmp.SQLMPConnectionPoolDataSource(); cpds.
Determining of the Pool is Large Enough Using an SQLMPDataSource with an SQLMPConnectionPoolDataSource Basic DataSource Object Properties The basic DataSource class includes a set of properties that control connection pooling. To set the property values for your application, you use the SQLMPDataSource class, which provides getter and setter methods. The properties, listed below, are described under JDBC/MP Connection-Pooling and Statement-Pooling Properties.
sds.setPoolLogging(true); //In application code DataSource ds; //After obtaining the data source PrintWriter writer = new PrintWriter(System.out,true); ds.setLogWriter(writer); ds.setPoolLogging(true); When poolLogging is set to true, the pool writes information about the number of connections or statements currently in the pool. The pool also writes a message whenever the statement pool is full and a PreparedStatement is requested that is not in the free pool.
application. If the pool does not find a proper object, the JDBC/MP driver creates a new PreparedStatement object. An application can assure that a PreparedStatement object is returned to the free pool by calling either of these: PreparedStatement.close Connection.
Limits the number of physical connections that can be in the free connection pool. Specify the minPoolSize property as: int The integer can be 0 through n, where n is the maximum integer value and less than maxPoolSize. The default is 0. The value determines connection-pool use: When the number of physical connections in the free pool reaches the minPoolSize value, the JDBC/MP driver closes subsequent connections by physically closing the connections—not by adding them to the free pool.
jdbcPropfile Property Sets the name of the Properties file that is used to pass alias names for SQL/MP tables. Specify the jdbcPropfile property as: string The value can be any valid identifier. The default is null.
ResultSet rs = stmt.executeQuery("drop table usertable"); } catch (SQLException sqlex) { // error handling } This example is like the preceding example except that it declares the statement outside the try - catch block. If executeQuery() throws an exception, the statement is not left dangling. Statement stmt; ResultSet rs; try { stmt = conn.createStatement(); ResultSet rs = stmt.executeQuery("drop table usertable"); } catch (SQLException sqlex) { // error handling } finally { stmt.
res.close(); stmt.close(); sqlmpConn.close(); } catch (SQLException sqlex) { System.out.println(sqlex); // other error handling res.close(); stmt.close(); sqlmpConn.close(); } } } Java Docs Home Page | Contents | Index | Glossary | Prev | Next HP JDBC Driver for SQL/MP Programmer's Reference (527401-004) Copyright © 2013, Hewlett-Packard Development Company L.P. All rights reserved. .
JDBC/MP Docs Home Page | Contents | Index | Glossary | Prev | Next JDBC/MP Compliance The JDBC Driver for SQL/MP (JDBC/MP driver) conforms where applicable to the JDBC 3.0 API. JDBC API Call Exception Summary These methods in the java.sql package throw an SQLException with the message SQL/MP: method-name is an unsupported method: Method CallableStatement.getArray(int parameterIndex) CallableStatement.BigDecimal(int parameterIndex) CallableStatement.getBlob(int parameterIndex) CallableStatement.
ResultSet.updateArray(int columnIndex, java.sql.Array array) ResultSet.updateRef(int columnIndex, java.sql.Ref ref) ResultSet.updateRef(String columnName, java.sql.Ref ref) These methods in the java.sql package throw an SQLException with the message "Auto generated keys not supported": Method Comments Connection.prepareStatement(String sql, int autoGeneratedKeys) Connection.prepareStatement(String sql, int[] columnIndexes) Connection.prepareStatement(String sql, String[] columnNames) Connection.
The JDBC specification identifies several areas that are optional and need not be supported if the database management system does not provide support. The JDBC Driver for SQL/MP does not support these optional interfaces: SQL3 data types, which include Array , Ref , and Struct. SQL/MP does not support those data types. Custom type-maps used to map between SQL user-defined data types and Java classes.
With scrollable result sets, the JDBC Driver for SQL/MP might sometimes need to choose an alternative concurrency type for a result set when the result set is created. Generally, queries that meet these criteria produce an updatable result set: The query references only a single table in the database. The query does not contain any join operations. The query selects the primary key of the table it references. The query selects all the nonnullable columns in the underlying table.
A BLOB represents a Binary Large OBject. A CLOB represents a Character Large OBject. BLOBs are typically used to store images (such as GIFs) or serialized objects in the database. CLOBs are typically used to store large character data (such as an XML file) in the database.
is the name of the column to be associated with the BLOB. This column should be defined to SQL/MP as CHAR or VARCHAR 36. sqlmp_catalog is the name of the catalog associated with the BLOB table. $vol.subvol [, ... ] is a list of one or more locations in the Guardian file system where BLOB files can be stored. You must have write access to these volume and subvolume locations. BlobMapFile Property A BlobMapFile property is used to specify a unique file name in the $volume.subvolume.filename format.
The Properties object can also contain other connection-related properties and their values, such as logon ID, password, alias, and so on. The Properties object can also be created by loading the properties from a file. In either case, the format for all BLOB properties must be the same. Note: After a Properties object has been specified while creating a database connection, the connection is aware of only those BLOB properties specified during connection creation.
is the file system error returned while writing the BLOB to a BLOB file. Note: Writing a BLOB to a database runs as a waited operation, so writing a BLOB within a thread blocks that thread. Example of Writing a BLOB to the Database This example assumes that a java.util.Properties object with BLOB properties has been created as described in the previous example and a connection granted using this Properties object. The sample table $VOL2.MYVOL.
Example of Retrieving a BLOB From the Database This example assumes that a java.util.Properties object with BLOB properties has been created as described in the previous example and a connection granted using this Properties object. The sample table $VOL2.MYVOL.EMPLOYEE contains two columns: EMPNAME stores an employee's name. EMPPIC stores an employee's picture. java.lang.String selectString = new String("SELECT * FROM $VOL2.MYVOL.EMPLOYEE"); // create a Statement object for the connection stmt = conn.
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.
Distributed Transactions For an application, the NonStop Server for Java JDBC driver supports distributed transactions in a standard way, as described in the JDBC 3.0 Specification. The JDBC API assumes that distributed transaction boundaries are controlled either by a middle-tier server or another API, such as the user transaction portion of the Java Transaction API. The NonStop Server for Java does not support the middleware (those implementing resource managers) pieces of distributed transactions.
HP JDBC Driver for SQL/MP Programmer's Reference (527401-004) Copyright © 2013, Hewlett-Packard Development Company L.P. All rights reserved.
Java Docs Home Page | Contents | Index | Glossary | Prev | Next JDBC Trace Facility The JDBC trace facility is designed to trace the entry point of all the JDBC methods called from the Java applications.
This table describes the set of properties that are required for a trace data source object: Property Name Type Description dataSourceName String The data source name description String Description of this data source traceDataSource String The name of the DataSource object to be traced The traceDataSource object is used to obtain the JDBC connection to the database. Java applications should turn on tracing using the setLogWriter method of the DataSource interface.
JDBC Trace Facility Demonstration Programs The JDBC Driver for SQL/MP a provide demonstration program in its their installation directory. This program is described in a readme file in the directory. By default, the location is: JDBC/MP driver install-dir/jdbcMp/T1227V30/demo/jdbcTrace Where install-dir NSJ4 installation location. These programs demonstrate tracing by creating a wrapper around the driver-specific data source to be traced.
JDBC/MP Docs Home Page | Contents | Index | Prev | Next Glossary ABCDEFGHIJLNOPRSTUVW A abstract class In Java, a class designed only as a parent from which subclasses can be derived, which is not itself appropriate for instantiation. An abstract class is often used to "abstract out" incomplete sets of features, which can then be shared by a group of sibling subclasses that add different variations of the missing pieces.
Java VM that Sun Microsystems, Inc. has certified as conformant. browser A program that allows you to read hypertext. The browser gives some means of viewing the contents of nodes and of navigating from one node to another. Internet Explorer, Netscape Navigator, NCSA Mosaic, Lynx, and W3 are examples for browsers for the WWW. They act as clients to remote servers. bytecode The code that javac , the Java compiler, produces.
can replicate. DCL See Data Control Language (DCL). DML See Data Manipulation Language (DML). driver A class in JDBC that implements a connection to a particular database management system such as SQL/MP. The NonStop Server for Java has these driver implementations: JDBC Driver for SQL/MP (JDBC/MP) and JDBC Driver for SQL/MX (JDBC/MX). DriverManager The JDBC class that manages drivers. E exception An event during program execution that prevents the program from continuing normally; generally, an error.
HP JDBC Driver for SQL/MP (JDBC/MP) The product that provides access to SQL/MP and conforms to the JDBC API. HP JDBC Driver for SQL/MX (JDBC/MX) The product that provides access to SQL/MX and conforms to the JDBC API. HP NonStop operating system The operating system for NonStop systems. HP NonStop ODBC Server The HP implementation of ODBC for NonStop systems. HP NonStop SQL/MP (SQL/MP) HP NonStop Structured Query Language/MP, the HP relational database management system for NonStop servers.
protocol. It provides e-mail, file transfer, news, remote login, and access to thousands of databases.
The C-language interface used by C functions called by Java classes. Includes an Invocation API that invokes Java VM from a C program. Java Run-time The Java VM and the Core API. This is the standard Java environment that the Java command invokes. Java virtual machine The process that loads, links, verifies, and interprets Java bytecode. The NonStop Server for Java implements the Java HotSpot virtual machine. JDBC See Java Database Connectivity (JDBC).
An addressable device attached to a computer network. A hypertext document. NSK See HP NonStop operating system. O ODBC See Open Database Connectivity (ODBC). Open Database Connectivity (ODBC) The standard Microsoft product for accessing databases. Open System Services (OSS) An environment available for interactive and programmatic use with the NonStop operating system. Processes that run in the OSS environment use the OSS API.
Assists in disaster recovery for online transaction processing (OLTP) production databases Monitors database updates audited by the TMF subsystem on a primary system and applies those updates to a copy of the database on a remote system S scalability The ability to increase the size and processing power of an online transaction processing system by adding processors and devices to a system, systems to a network, and so on, and to do so easily and transparently without bringing systems down.
thread A task that is separately dispatched and that represents a sequential flow of control within a process. threads The nonnative thread package that is shipped with Sun Microsystems JDK. throw Java keyword used to raise an exception. throws Java keyword used to define the exceptions that a method can raise.
An Internet client-server hypertext distributed information retrieval system that originated from the CERN HighEnergy Physics laboratories in Geneva, Switzerland. On the WWW everything (documents, menus, indexes) is represented to the user as a hypertext object in HTML format. Hypertext links refer to other documents by their URLs.
JDBC/MP Docs Home Page | Contents | Glossary | Prev | Next Index A B C D E F G H I J K L M N O P Q R S T U V W X Y Z A abbreviations used in this document accessing NonStop SQL databases aliases for database objects creating and using when you can use which SQL statements support API packages architecture audience for this document autocommit mode standard driver standard driver, nonautocommit mode transaction-aware driver
JDBC driver noncompliance JDBC driver support for JDBC 3.
drivers architecture loading See also loading drivers requirements for standard, sqlmp transaction-aware, sqlmptx types of verifying installation E extensions, standard API for JDBC 2.
tracing using the DriverManager class JDBC driver types JDBC driverManager JDBC 3.
P passing SQL/MP statements to databases pooling See connection pooling entries and statement pooling poolLogging property, JDBC/MP printing this document properties basic DataSource object connection pooling with the DriverManager class HP extensions for specifying using put() method specifying in a properties file standard ConnectionPoolDataSource statement pooling properties file loading programmatically loading using a system property PropertyCycle prope
transaction-aware driver, sqlmptx Tracing See JDBC trace facility tracing TransactionMode property, JDBC/MP transactions autocommit mode, standard driver autocommit mode, transaction-aware driver distributed, support for managing with TMF nonautocommit mode, standard driver nonautocommit mode, transaction-aware driver troubleshooting dangling statements data truncation No suitable driver error statement pooling tracing truncation of data U updates,
Java Docs Home Page | Contents | Index | Glossary | Prev | Next List of Examples Section Title Example Title(s) Accessing SQL Databases with SQL/MP Standard Driver Example Transaction-Aware Driver Example Passing SQL/MP Statements to a Database Specifying Properties Using the put() Method Specifying Properties in a Properties File Registering the ConnectionPoolDataSource and DataSource Objects with a JNDI-Based Naming Service Determining if the Pool is Large Enough How a Dangling Statement Can Be Create
Java Docs Home Page | Contents | Index | Glossary | Prev | Next List of Figures Section Title Figure Title(s) Introduction to JDBC/MP Architecture of the JDBC Driver for SQL/MP Accessing SQL Databases with SQL/MP Loading a JDBC Driver Class Into the JVM Java Docs Home Page | Contents | Index | Glossary | Prev | Next HP JDBC Driver for SQL/MP Programmer's Reference (527401-004) Copyright © 2013, Hewlett-Packard Development Company L.P. All rights reserved.
Java Docs Home Page | Contents | Index | Glossary | Prev List of Tables Section Title Table Title(s) About This Manual Document Sections Introduction to JDBC/MP Driver JDBC Driver Types Accessing SQL Databases with SQL/MP Compatible Java and SQL/MP Data Types Default SQL/MP Database Object Names Standard ConnectionPoolDataSource Object Properties JDBC/MP Compliance JDBC API Call Exception Summary Metadata Support JDBC Trace Facility Tracing Using the DriverManager Class Tracing Using the DataSou
