Compaq NonStop Java Programmer's Reference Abstract This document describes the Compaq NonStopTM Server for Java...based on Java 2 Platform, Standard Edition, SDK 1.2.2 (short form: NonStop Java), a Java environment that supports compact, concurrent, dynamic, and portable programs for the enterprise server. NonStop Java uses the Compaq Kernel operating system to add scalability and program persistence to the Java environment. Product Version NonStop Java 2.
Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Check with your authorized Compaq representative to make sure you have the most recent information. Export Statement Export of the information contained in this manual may require authorization from the U.S. Department of Commerce.
U.S. Government Users Restricted Rights--Use, duplication or disclosure restricted by GSA ADP Schedule Contract. Unpublished--All rights reserved under the Copyright Laws of the United States. Abbreviations OSS is a mnemonic for Open System Services. DCE is a mnemonic for Distributed Computing Environment. Copyrights, Trademarks, and Registered Trademarks Copyright 2002 Compaq Computer Corporation.
DynaComm is a trademark of FutureSoft Engineering, Inc. IMAGEN is a registered trademark of IMAGEN Corporation. IBM, IBM PC, IBM Personal Computer, and AT are registered trademarks; and AIX, CICS, and RISC System/6000 are trademarks of IBM Corporation. X Window System is a trademark of the Massachusetts Institute of Technology. CICS Option is a trademark of Micro Focus Ltd. CICS is a trademark of IBM Corporation.
Corporation. © 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation. OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C.
TPC Benchmark, TPC-A, TPC-B, TPC-C, tpsA, tpsB, and tpmC are trademarks of the Transaction Processing Performance Council. AFS and Transarc are registered trademarks and Episode is a trademark of the Transarc Corporation. BSD is a trademark of the University of California, Berkeley. Xerox and Ethernet are registered trademarks of Xerox Corporation. All other product names mentioned herein may be trademarks or registered trademarks of their respective companies.
NonStop Java Programmer's Reference ● ● ● About This Document ❍ New and Changed Information ❍ Is This Document for You? ❍ Document Structure ❍ Printing This Document ❍ Related Reading ■ Compaq Documents ■ Sun Microsystems Documents ❍ Notation Conventions ❍ Abbreviations ❍ Your Comments Invited Introduction to NonStop Java ❍ Java Development Kit (JDK) Highlights ❍ Java Naming and Directory Interface (JNDI) Highlights ❍ Execution Scenarios ■ Stand-Alone Execution ■ Web-Based Exec
❍ ❍ ● Setting Environment Variables ■ Symbolic Link ■ Binding Libraries into the JVM ■ Native Libraries ■ Configuring TCP/IP and DNS for RMI NonStop Java Directory Structure ■ Directory Contents ■ Demonstration Programs ■ Symbolic Links ■ Wrappers Running Java Tools Compaq Implementation Specifics ❍ Additional Files ❍ Java Abstract Window Toolkit (AWT) ❍ Java Native Interface (JNI) ❍ ● ■ ■ Calling C or C++ Methods From Java ■ Calling Java Methods From C or C++ ■ Using the
❍ ■ SQLMPDatabaseMetaData ■ SQLMPDataSource ■ SQLMPDriver ■ SQLMPPreparedStatement ■ SQLMPResultSet ■ SQLMPResultSetMetaData ■ SQLMPStatement Transactions and the JDBC Driver for SQL/MP ■ Autocommit Mode and the Standard Driver ■ Nonautocommit Mode and the Standard Driver ■ Autocommit Mode and the Transaction-Aware Driver ■ Nonautocommit Mode and the Transaction-Aware Driver ❍ SQL/MP Driver Requirements ❍ JDBC Driver Types ❍ JDBC DriverManager ❍ Loading a Driver ❍ ■ Specifyi
■ ● ❍ Sample SQL/MP Program ❍ Compliance Information ❍ JDBC Driver for SQL/MP Support for JDBC 2.0 Result Set Support ■ Batch Update Support ■ BLOBs and CLOBs ■ JDBC 2.
❍ Current Class Methods ❍ Java Transaction API (JTA) ■ javax.transaction Interfaces ■ javax.transaction Exceptions ■ Examples ● Just-in-Time (JIT) Compiler ● Glossary ● Index ● List of Examples ● List of Figures ● List of Tables NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
Java 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 ● Your Comments Invited New and Changed Information This edition of the NonStop Java Programmer's Reference differs from the previous edition (part number 426947-001) in the following ways: ● Information about expl
about the JDK. For experienced Java programmers, this document explains how to access NonStop SQL/MP and NonStop SQL/MX databases. For developers new to Compaq systems, this document: ● Explains Compaq fundamentals as they apply to the NonStop Java product ● Explains differences between NonStop Java and the JDK ● Refers to other appropriate Compaq documentation Document Structure This document consists of a set of linked HTML files (web pages).
Glossary Defines many terms that this document uses. List of Examples Lists the examples in this document. Each example name is a link to that example. List of Figures Lists the figures in this document. Each figure name is a link to that figure. List of Tables Lists the tables in this document. Each table name is a link to that table. Index Lists this document's subjects alphabetically. Each index entry is a link to the appropriate text.
● System Services (OSS) environment (c89) must be installed and configured correctly. Also, you might need this document if you use the Java Native Interface (JNI) to communicate between Java and C. Inspect Manual Documents the Compaq Inspect interactive symbolic debugger for Compaq NonStop Series systems and Compaq NonStop/RISC systems. You can use Inspect to debug programs running in a Java Virtual Machine (JVM).
❍ SQL/MP Reference Manual ❍ ❍ Explains the SQL/MP language elements, expressions, functions, and statements. SQL/MP Installation and Management Guide ❍ Explains how to plan, install, create, and manage an SQL/MP database; describes the syntax of installation and management commands; and describes SQL/MP catalogs and file structures. SQL/MP Query Guide ❍ Explains how to retrieve and modify data from a NonStop SQL/MP database and how to analyze and improve query performance.
● ❍ Describes the SQL/MX programmatic interface for ANSI C and COBOL. Also describes embedded SQL statements used in C and COBOL applications. SQL/MX Data Mining Guide ❍ Describes the SQL/MX data structures and operations needed for the knowledge-discovery process.
❍ ❍ Java Remote Method Invocation (RMI) document (http://java.sun.com/products/jdk/rmi/index.html) Reference pages for the following packages: ■ java.rmi (http://www.javasoft.com/products/jdk/1.2/docs/api/java/rmi/package-summary.html) ■ java.rmi.dgc (http://java.sun.com/products/jdk/1.2/docs/api/java/rmi/dgc/package-summary.html) ■ java.rmi.registry (http://java.sun.com/products/jdk/1.2/docs/api/java/rmi/registry/package-summary.html) ■ java.rmi.server (http://java.sun.com/products/jdk/1.
print {objectID|objectName} ... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: dump objectID ... Punctuation 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.
CPU. central processing unit DBMS. database management system DCL. Data Control Language DDL. Data Definition Language DML. Data Manipulation Language DNR. Domain Name Resolver DNS. Domain Name Server DSA. digital signature algorithm DSM. Distributed Systems Management GUI. graphical user interface HTML. Hypertext Markup Language HTTP. Hypertext Transfer Protocol IDL. Interface Definition Language IEC. International Electrotechnical Committee IEEE. Institute for Electrical and Electronic Engineers IETF.
MIF. FrameMakerTM Interface Format MP. massively parallel NonStop TM/MP. NonStop Transaction Manager/MP NonStop TS/MP. NonStop Transaction Services/MP ODBC. Open Database Connectivity OLTP. Online Transaction Processing OMG. Object Management Group OSS. Open System Services OTS. Object Transaction Services POSIX. portable operating system interface x Pthread. POSIX thread RAM. random-access memory RDF. Remote Duplicate Database Facility RISC. reduced instruction set computing RMI.
WWW. World Wide Web Your Comments Invited Mail, Email, or Fax Your Comments To ATTN: Product Manager -- Software Publications LOC CAC-03 Compaq Computer Corporation Cupertino, CA 95014-2599 From Name_________________________________________________ Company Name_______________________________________ Company Address_____________________________________ Telephone Number____________________________________ Fax Number___________________________________________ Email pubs.comments@compaq.
| Contents | Index | Glossary | Prev | Next Introduction to NonStop Java The Compaq NonStop Server for Java...based on Java 2 Platform, Standard Edition, SDK 1.2.2 (short form: NonStop Java) is a Java environment that supports compact, concurrent, dynamic, portable programs for the enterprise server. NonStop Java requires the Compaq NonStop Kernel Open System Services (OSS) environment for its operation.
The following table lists the JDK 1.2.2 API packages supported by NonStop Java 2.1: Package Description java.applet Provides the classes necessary to create an applet and the classes an applet uses to communicate with its applet context. java.beans Contains classes related to Java Beans development. java.beans.beancontext Provides classes and interfaces relating to bean context. java.io Provides for system input and output through data streams, serializatio, and the file system. java.
java.security.acl The classes and interfaces in this package have been superseded by classes in the java.security package. java.security.cert Provides classes and interfaces for parsing and managing certificates. java.security.interfaces Provides interfaces for generating asymmetric cipher algorithm keys and digital signature algorithm keys. java.security.spec Provides classes and interfaces for key specifications and algorithm parameter specifications. java.sql Provides the JDBC package. java.
If accessed from NonStop Java 2.1, an unsupported feature throws an UnsupportedClassException. For more information on JDK 1.2.2, see the Sun Microsystems documentation. Java Naming and Directory Interface (JNDI) Highlights The Java Naming and Directory Interface (JNDI) provides naming and directory functionality to Java programs. It is independent of any specific directory service implementation, so it allows a variety of directories to be accessed in a common way.
The main() method executes when you use the java command to invoke the Java Virtual Machine (JVM). No major modifications were made to the JVM standard architecture to enable command-line execution. The JVM runs as a single executable program named java and performs the standard functions of class loading, linking, verification, and execution. Web-Based Execution A significant Compaq extension of JDK 1.2.
itself and waits for a request. A CLASSPATH environment variable is configured with the locations of directories, zip files, or JAR files from which servlet classes are to be loaded. HyperText Markup Language (HTML) invokes an instance of an HttpServlet class in much the same way as it invokes a CGI program. Instead of referring to a program in a cgi-bin directory, HTML refers to SSC-name/Servlet-name.
NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
Contents | Index | Glossary | Prev | Next Installation and Configuration This section explains these subjects: ● Installation Requirements ● Configuration Requirements ● NonStop Java Directory Structure ● Running Java Tools Installation Requirements Hardware and software requirements for the Compaq NonStop Server for Java...based on Java 2 Platform, Standard Edition, SDK 1.2.2 (short form: NonStop Java) are described in the README file on the product CD.
Since the G06 software release, the operating system creates one swap file per processor, but the default swap file size is 256 MB. Your system administrator can use the NSKCOM tool to create additional swap files. Even if the default swap file size is already 256 MB (or more), you might need to create additional swap files if you plan to run multiple large processes in the same processor, because processes running in the same processor share the same swap file.
JREHOME If you install Nonstop Java in a location other than the /usr/tandem directory, and you plan to run the java executable or one of its tools directly out of the java/bin/oss/bin/posix_threads directory instead of through the shell wrappers in java/bin, you must do the following: 1. Create a shell variable called JREHOME and set it to the location of the jre directory.
Binding Libraries Into the JVM To establish an environment that permits the use of servlets and similar clients, you must bind the appropriate libraries into the JVM. To bind the libraries, use /usr/tandem/java/install/Makefile. This Makefile relinks java with any libraries in the directories /usr/tandem/java/lib, /usr/tandem/java/lib/oss/posix_threads, /usr/tandem/java/jre/lib, and /usr/tandem/java/jre/lib/oss/posix_threads. For information about this Makefile, see /usr/tandem/java/install/README.
NonStop Java Directory Structure This subsection describes: ● Directory Contents ● Symbolic Links ● Wrappers Directory Contents The /usr/tandem/java directory contains release documents and subdirectories. The following table lists the subdirectories and describes their contents.
Demonstration Programs The /demo directory contains subdirectories, each of which contains a demo program and a README file that documents how the demo should be used. Demos provided include the following: Demonstration Program Illustrates awt The exception a program receives if it attempts to use an AWT method to visually display something (Because of the nonvisual nature of Compaq servers, NonStop Java does not support AWT.
The wrappers also set the JREHOME environment variable. Running Java Tools After installing the NonStop Java software and setting the environment variables, you start a tool by typing its name at the shell prompt using a file name as an argument. You can also specify the path to a tool by typing the path in front of the tool each time or by adding the path to the startup file.
Contents | Index | Glossary | Prev | Next Compaq Implementation Specifics This section explains these subjects: ● Additional Files ● Java Abstract Window Toolkit (AWT) ● Java Native Interface (JNI) ● IEEE Floating-Point Implementation ● JavaBeans ● jdb: Java Debugger Additional Files In addition to the standard Java packages, NonStop Java 2.1 provides these files: tandemvm.jar File containing classes that supplement rt.jar jtatmf.
Java Native Interface (JNI) The Sun Microsystems Java Native Interface (JNI) standard defines both the C-language APIs that enable Java methods to call C and C++ methods and the way that C and C++ methods can start and interact with a Java Virtual Machine (JVM). NonStop Java supports JNI and the Invocation API with the following modifications: ● ● ● ● You must relink the JVM whenever you use new C or C++ routines in your Java programs.
● (/usr/tandem/java/include/oss/dce). Use Pthread wrappers for any functions that mandate thread-aware activity, such as socket I/O, file I/O, and pipes. Because Pthreads are user-level threads, the operating system does not schedule each thread independently, and therefore, operating system calls from a user thread can block the entire JVM rather than only the active thread. Pthread wrappers prevent this problem.
IEEE Floating-Point Implementation Java uses IEEE floating-point arithmetic. NonStop Java 2.1 uses the public-domain software-emulation package SoftFloat to achieve IEEE floating-point compliance. The SoftFloat library is packaged with the Java Virtual Machine (JVM). Incompatibilities between the IEEE and Compaq floating-point representations might cause loss of precision or accuracy when you convert a Java String that represents a Compaq float or double value to a Java Float or Double value.
# The format of a line is one of: # key : element # key = element # key element # where is a fully qualified class name and is one of TANDEM_FP # or IEEE_FP. # # # # # # # For example the lines: com/pkg/myclass = IEEE_FP classB = TANDEM_FP tell the JVM that native methods of com/pkg/myclass want to get floats and doubles in IEEE floating point format, whereas native methods of classB want to get floats and doubles in Tandem floating point format.
yield Yields the current thread (the debugger), giving up control of the processor so other threads (programs) can run. For more information about jdb and how to start java so that jdb can attach to it, see the NonStop Java Tools Reference Pages. Contents | Index | Glossary | Prev | Next NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
| Contents | Index | Glossary | Prev | Next Accessing NonStop SQL/MP Databases Java programs interact with NonStop SQL/MP databases using the Java Database Connectivity (JDBC) API. The NonStop Server for Java...based on Java 2 Platform, Standard Edition, SDK 1.2.2 (short form: NonStop Java) and the JDBC Driver for SQL/MP include the following items: ● The JDBC 2.0 API ● The JDBC DriverManager in the Java Development Kit (JDK) 1.2.
getSQLState setNextException Interfaces ❍ ❍ ● ❍ Blob (See SQLMPBlob.) ❍ Clob (See SQLMPClob.) ❍ Connection (See SQLMPConnection.) ❍ DatabaseMetaData (See SQLMPDatabaseMetaData.) ❍ Driver (See SQLMPDriver.) ❍ PreparedStatement (See SQLMPPreparedStatement.) ❍ ResultSet (See SQLMPResultSet.) ❍ ResultSetMetaData (See SQLMPResultSetMetaData.) ❍ Statement (See SQLMPStatement.) SQLMPBlob An SQLMPBlob is a transaction duration reference to a BLOB (Binary Large OBject).
getMaxFieldSize() setFloat(int parameterIndex, float x) getMaxRows() setInt(int parameterIndex, int x) getPassword() setLong(int parameterIndex, long x) getQueryTimeout() setMaxFieldSize(int max) getTransactionIsolation() setMaxRows(int max) getTypeMap() setNull(int parameterIndex, int sqlType) getUrl() setObject(int parameterIndex, java.lang.Object x) setObject(int parameterIndex, java.lang.Object x,, int targetSqlType) setObject(int parameterIndex, java.lang.
SQLMPClob An SQLMPClob is a transaction duration reference to a CLOB (Character Large OBject). This means that an SQLMPClob object is valid for the duration of the transaction in which it was created. The SQLMPClob class provides methods for getting the length of an SQLMPClob value, for materializing a CLOB value on the client, and for searching for a substring or CLOB object within a CLOB value.
● ● setAutoCommit(true) setTransactionIsolation() The transaction-aware driver always returns TRANSACTION_NONE in response to a call to getTransactionIsolation(). SQLMPDatabaseMetaData SQLMPDatabaseMetaData provides information about an SQL/MP database.
SQLMPPreparedStatement SQLMPPreparedStatement allows an SQL/MP statement to be compiled, stored in an SQLMPPreparedStatement object, and then executed multiple times.
§ If you want to set a column in a SQL/MP table to null, you must supply a null indicator when you create the update statement for the table.
getBoolean(int) getBoolean(String) rowUpdated() getByte(int) getByte(String) setFetchDirection(int direction) getBytes(int) getBytes(String) setFetchSize(int rows) getCharacterStream(int colIndex) getCharacterStream(String colname) updateAsciiStream(String colname, InputStream x,, int length) updateAsciiStream(int columnIndex, InputStream x,, int length) getClob(int i) getClob(String colName) updateBigDecimal(String colname, BigDecimal x) updateBigDecimal(int columnIndex, BigDecimal) getConcurrenc
getMetaData() updateLong(int columnIndex, long x) updateLong(String colname, long x) getObject(int) getObject(int columnIndex) getObject(String) getObject(String colname) updateNull(int columnIndex) updateNull(String colname) getRow() updateObject(int columnIndex, Object x) updateObject(int columnIndex, Object x,, int scale) updateObject(String colname, Object x) updateObject(String colname, Object x,, int scale) getShort(int) getShort(String) updateRow() getStatement() updateShort(int columnIndex,
SQLMPResultSetMetaData SQLMPResultSetMetaData provides information about a result set returned by an SQL/MP database.
● ● ● ● ● ● ● getResultSetType() getUpdateCount() getWarnings() setCursorName() setFetchDirection(int direction) setFetchSize(int rows) setMaxFieldSize() The SQL/MP drivers do not support the following SQLMPStatement methods: ● cancel() ● getMaxRows() ● setEscapeProcessing() ● setMaxRows() ● setQueryTimeout() Transactions and the JDBC Driver for SQL/MP The Transaction Management Facility (TMF) is the system entity that manages transactions.
SQL/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. See the Softdoc or the README file that accompanies the NonStop Java product for information about these tasks. JDBC Driver Types The following table describes the types of JDBC drivers: Type Written in Java Description No.
Loading a Driver To load a JDBC driver, load its JDBC driver class (not the JDBC driver file, whose name has the suffix .class) into the Java Virtual Machine (JVM) in one of the following 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. The first two of the preceding ways allow you to change drivers without modifying your program code; the third way does not.
java -Djdbc.drivers=com.tandem.sqlmp.SQLMPDriver;com.javaco.purejavajdbc.Driver Adding the JDBC Driver Class to the jdbc.drivers Property To add the JDBC driver class to the jdbc.drivers property: 1. Create a new Properties object using this command: Properties prop=new Properties(); 2. Add the JDBC driver class to the jdbc.drivers property using this command: prop.put("jdbc.drivers","driver_class_name[;driver_class_name]"); 3. Set the system properties using this command: System.
import java.sql.*; ... Connection myConnection = DriverManager.getConnection("jdbc:sqlmptx:"); Pure Java Driver Example In a Java program, the following code uses a pure Java driver, javaco, to create a connection (myConnection) between the program and the database MyDatabase, which resides on the server MyServer: import java.sql.*; ... Connection myConnection = \ > DriverManager.
Compatible Java and SQL/MP Data Types The following 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.
Not supported for current release n Referring to Database Objects By default, the SQL/MP driver uses Guardian filenames for SQL/MP database objects, as the following table shows. Default SQL/MP Database Object Names Database Object Catalog Default Name * [\node.][$volume.]subvol Index [\node.][[$volume.]subvol.]fileID Table Examples $sqldata.sales \tokyo.$disk02.sqlcat emptab $sqldisk.fy02.xsalary \newyork.$sqldisk.fy02.
Note: Previous versions of NonStop Java used an equal sign (=) instead of a plus sign. For compatibility, the JDBC Driver for SQL/MP supports the equal sign, but Compaq recommends the plus sign for new programs. 3. If the put() calls for the previous step are in a separate file, use the properties.load method to load that file into the java.util.Properties object. 4. Connect your program to the database, passing the java.util.Properties object to DriverManager.getConnection(). 5.
// 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.executeQuery("select * from longname2 where col1='pickme'"); Loading a Properties File Using a System Property The JDBC driver (optionally) looks for a System property called jdbcPropfile.
❍ ❍ ❍ ❍ ❍ 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 the following example, no alias substitution is possible: select jobcode, deptnum, first_name, last_name from persnl.
Dangling Statements SQL/MP drivers track all statements within a connection, but when an exception occurs, Java's garbage collection feature might prevent a driver from immediately closing an open statement. A statement that is left dangling inside a connection could cause unexpected results. To avoid dangling statements: ● Create statements outside try-catch blocks. ● Close statements when they are no longer needed.
String sqlmpURL = "jdbc:sqlmp:"; // Use a valid table name from an existing database in the select statement. String sqlmpQuery = "select * from $VOL1.MYVOL.MYTAB"; Statement stmt = null; Connection sqlmpConn = null; ResultSet res = null; try { // Try to connect to the SQL/MP database. sqlmpConn = DriverManager.getConnection(sqlmpURL); // Create an SQL statement object to submit SQL statements. stmt = sqlmpConn.createStatement(); // Submit a query and create a ResultSet object. res = stmt.
● ● ● Column aliasing is not supported because SQL/MP does not support column aliasing. The ODBC minimum SQL grammar is not supported. Therefore, the JDBC Driver for SQL/MP does not support the following: ❍ Numeric functions, string functions, system functions, or the convert function. ❍ Escape syntax for time or date literals, LIKE escape characters, or escape characters for outer joins. Because SQL/MP does not support stored procedures, escape syntax is not supported for stored procedures.
Concurrency An application can choose from two different concurrency types for a result set: read-only and updatable. A read-only result set does not allow updates of its contents. An updatable result set allows rows to be updated, deleted, and inserted. As 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.
The Properties object should contain one 'BlobInfo' property for every table column that contains BLOBs. A BlobInfo property is identified by a key of type 'BlobInfoN', where N represents a unique number used to identify that property. Format of a BlobInfo property The format of a BlobInfo property is as follows: BlobInfoN, sqlmp_table_name, column_name, sqlmp_catalog_of_Blob_table, $vol.subvol [, ... ] where N is a unique number used to identify the BlobInfo property.
// add BlobInfo Properties prop.put("BlobInfo1", ","$VOL1.MYVOL.PRODUCT, PICTURE, $VOL.CTLG, $VOL1.SUBVOL1, \ > $VOL2.SUBVOL2"); prop.put("BlobInfo2", ","$VOL2.MYVOL.EMPLOYEE, EMPPIC, $VOL.CTLG, $VOL2.SUBVOL2"); ");//add BlobMapFile Property prop.put("BlobMapFile", ","$VOL2.MYVOL.BLOBMAP"); ");// add other properties to java.util.Properties object..... The BLOB table name, column name, and catalog name are required by JDBC.
Errors encountered during the writing of a BLOB to a BLOB file generate an SQLException in the following format: SQLMP: error message. See File System error ## for further details. where: error message is the error encountered while performing this operation. error ## 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.
error ## is the file system error returned while reading the BLOB from a BLOB file. Note: Retrieving a BLOB from a database runs as a waited operation, so reading a BLOB within a thread blocks that thread. 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.
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.
Connection Pooling A connection pool is a cache of database connections that is maintained in memory so that the connections can be reused. NonStop Java does not support connection pooling because it is normally implemented by the middle-tier server vendor. Distributed Transactions For an application, the NonStop Java JDBC driver supports distributed transactions in a standard way, as described in the JDBC 2.0 Standard Extensions document.
| Contents | Index | Glossary | Prev | Next Accessing NonStop SQL/MX Databases The JDBC Driver for NonStop SQL/MX (JDBC/MX) implements the JDBC technology that supports JDBC 2.1 Data Access API. The JDBC/MX driver enables Java applications to use Compaq NonStop SQL/MX to access Compaq NonStop SQL databases. This section contains information specific to the JDBC/MX driver only.
Connection to SQL/MX A Java application can obtain a JDBC connection to SQL/MX in two ways: ● Using the DriverManager class ● Using the DataSource implementation Connection Using the DriverManager Class This is the traditional way to establish a connection to the database. The DriverManager class works with the Driver interface to manage the set of drivers loaded. When an application issues a request for a connection using the DriverManager.
Using a DataSource object increases the application portability by allowing the application to use a logical name for a data source instead of providing driver-specific information in the application. A logical name is mapped to a DataSource object by means of a naming service that uses the Java Naming and Directory Interface (JNDI).
without regard to whether the application commits or rolls back the transaction. SQL Object Naming and Mapping JDBC/MX supports two object name types for NonStop SQL objects: ANSI (the default type) and SHORTANSI. JDBC/MX also supports Guardian names in SQL commands. SQL reserved words that are part of Guardian names must appear in UPPER CASE and be enclosed in double quotation marks ("). For more information, see the Compaq NonStop SQL/MX Reference Manual.
The schema is used for both DDL and DML statements. The catalog represents the subvolume where the SQL object is registered, while the schema represents the subvolume where the SQL object is located. The catalog and schema are of the format system_volume_subvol with "\" and "$" removed. Java applications can specify the default catalog and schema at run time using the system properties catalog and schema, respectively, using -D option in the command line, as follows.
DatabaseMetaData.getProcedures(...) DatabaseMetaData.getProcedureColumns(...) Stored procedures are not available in SQL/MX. DatabaseMetaData.GetColumnPrivileges(...) DatabaseMetaData.getTablePrivileges(...) GRANT/REVOKE is not supported in SQL/MX. DatabaseMetaData.getImportedKeys(...) DatabaseMetaData.getExportedKeys(...) DatabaseMetaData.getCrossReference(...) Foreign keys are not supported in SQL/MX The following optional interfaces in the javax.
java.sql.Connection.createStatement(...) java.sql.Connection.prepareStatement(...) The JDBC Driver for SQL/MX does not support the scroll-sensitive result set type, so an SQLWarning is issued if an application requests that type. The result set is changed to a scroll-insensitive type. java.sql.Connection.setCatalog(...) The catalog argument is ignored. The default catalog can be specified in the command line only. java.sql.Connection.setReadOnly(...) The read-only attribute is ignored. java.sql.
Updatable Result Set The JDBC Driver for SQL/MX supports both read-only and updatable concurrency modes. The JDBC Driver for SQL/MX expects the following criteria for a result set to be updatable: ● The table name of the first column in the result set is assumed to be the table to be updated. This assumption allows queries from multiple tables also to be updatable. ● The query selects the primary key columns of the table to be updated.
SQL Conformance JDBC/MX conforms to the SQL language entry level of SQL-92.
SQRT SQRT TAN TAN TRUNCATE Not supported in this release String Functions JDBC Function SQL/MX Equivalent Function ASCII ASCII CHAR CHAR CONCAT Supported, but no equivalent SQL/MX function DIFFERENCE Not supported INSERT INSERT LCASE LOWER LEFT SUBSTRING LENGTH LENGTH LOCATE LOCATE (JDBC LOCATE start parameter is not supported) LTRIM TRIM...LEADING REPEAT REPEAT REPLACE REPLACE RIGHT RIGHT RTRIM TRIM...
CURDATE, CURRENT_DATE CURRENT_DATE CURTIME, CURRENT_TIME CURRENT_TIME DAY DAY EXTRACT EXTRACT DAYNAME Not supported DAYOFMONTH Not supported DAYOFWEEK DAYOFWEEK DAYOFYEAR DAYOFYEAR HOUR HOUR MINUTE MINUTE MONTH MONTH MONTHNAME MONTHNAME NOW NOW QUARTER QUARTER SECOND SECOND TIMESTAMPADD Not supported TIMESTAMPDIFF Not supported WEEK WEEK System Functions JDBC Function SQL/MX Equivalent Function DATABASE Not supported in this release IFNULL Not supported in this relea
the equivalent SQL/MX data type is a string literal with a value of CHARACTER. JDBC Data Types The following table shows the JDBC data types that are supported by JDBC/MX and their corresponding SQL/MX data types: JDBC Data Type Supported by JDBC/MX SQL/MX Data Type Types.Array No Types.BIGINT Yes Types.BINARY No Types.BIT No Types.BLOB No Types.CHAR Yes Types.CLOB No Types.DATE Yes DATE Types.DECIMAL Yes DECIMAL(p,s) Types.DISTINCT No Types.DOUBLE Yes DOUBLE PRECISION Types.
Types.TINYINT No Types.VARBINARY No Types.VARCHAR Yes VARCHAR(n) The JDBC/MX driver maps the following SQL/MP data types to the JDBC data type Types.
{ oj join-expression } join-expression { INTERVAL sign interval-string interval-qualifier } INTERVAL sign interval-string interval-qualifier { fn scalar-function } scalar-function { escape 'escape-character' } escape 'escape-character' { [?=]call procedure-name... } Not supported in the current release * JDBC syntax does not include nested joins, while SQL/MX does. JDBC/MX extends the SQL escape syntax for an outer join.
| 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. To make this facility generic, it is implemented as wrapper JDBC driver; it can therefore be used with the JDBC Driver for SQL/MP (JDBC/MP), the JDBC Driver for NonStop SQL/MX (JDBC/MX), or the Compaq NonStop JDBC Server (a Type 3 JDBC driver).
t3jdbc:sqlrmi: Type 3 JDBC Driver Java applications should turn on tracing using the DriverManager.setLogWriter method. Tracing Using the DataSource Implementation This is preferred way to establish a JDBC connection and to enable the JDBC trace facility. In this way, a logical name is mapped to a trace data source object by means of a naming service that uses the Java Naming and Directory Interface (JNDI).
is the hashcode of the JDBC object className is the JDBC implementation class name Trace output is sent to the PrintWriter specified in the setLogWriter method. Contents | Index | Glossary | Prev | Next NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
| Contents | Index | Glossary | Prev | Next Transactions The Compaq NonStop Server for Java...based on Java 2 Platform, Standard Edition, SDK 1.2.2 (short form: NonStop Java) lets you work with transactions in several ways. You can: ● Use the Current class methods to define transactions across transaction services, such as transactions that include JDBC calls. ● Use the Java Transaction API (JTA). Note: Compaq processes can start a maximum of 100 concurrent transactions in each process.
resume Sets or resumes association of a transaction with the calling thread. rollback Rolls back the transaction associated with the calling thread. rollback_only Marks the transaction associated with the calling thread so that the only possible outcome is to roll back the transaction. set_timeout Modifies the time-out value associated with transactions started by subsequent invocations of the begin method. suspend Suspends the association of the calling thread with a transaction context.
API-TMF; the version of NonStop Java Transaction API that uses JTS is called NonStop Java Transaction API-JTS. NonStop Java Transaction API-TMF and NonStop Java Transaction API-JTS have identical interfaces. You can specify TMF or JTS when you use JTAFactory.getUserTransaction to get a reference to javax.transaction.UserTransaction. (See examples.) The default is TMF. NonStop Java Transaction API-TMF is intended for applications other than CORBA applications.
● ● ● ● ● ● ● ● HeuristicCommitException HeuristicMixedException HeuristicRollbackException InvalidTransactionException NotSupportedException TransactionRequiredException TransactionRolledbackException SystemException Examples The following examples are identical except that: ● The first example uses NonStop Java Transaction API-TMF by default ● The second example requests NonStop Java Transaction API-TMF ● The third example requests NonStop Java Transaction API-JTS NonStop Java Transaction API-TMF by
import com.tandem.jta.JTAFactory; // Get a reference to UserTransaction based on TMF (by request). UserTransaction utx = JTAFactory.getUserTransaction(JTAFactory.TMF); // Start transaction utx.begin(); // Do work ... // Commit transaction utx.commit(); NonStop Java Transaction API-JTS The following code gets a reference to UserTransaction based on JTS. It then starts and ends a transaction. import javax.transaction.UserTransaction; import com.tandem.jta.
Contents | Index | Glossary | Prev | Next Just-in-Time (JIT) Compiler Java supports the use of native RISC instructions instead of Java bytecode to improve Java run-time performance. To generate RISC instructions, run the Java interpreter with the -jit option. The -jit option is a Compaq extension to standard Java. -jit performs just-in-time (JIT) compilation on each class, translating the class to native RISC code when it is loaded.
Legend 1. 2. 3. 4. Java bytecode Run-time JIT compilation Native RISC instructions Java Virtual Machine (JVM) For more information about java, see the NonStop Java Tools Reference Pages. Contents | Index | Glossary | Prev | Next NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
Contents | Index | Prev | Next Glossary ABCDEFGHIJKLMNOPQRSTUVWXYZ A abstract class In Java, a class designed only as a parent from which subclasses can be derived, which is not itself suitable 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. Abstract Window Toolkit (AWT) The package that implements graphical user interfaces for Java.
communicate with other software components. ASCII See American Standard Code for Information Interchange (ASCII). autocommit mode A mode in which a JDBC driver automatically commits a transaction without the programmer's calling commit(). AWT See Abstract Window Toolkit (AWT). B BDK See JavaBeans Development Kit (BDK). BLOB A data type used to represent Binary Large OBjects. These are typically used to store, in Enscribe files, images or serialized objects in the database.
catalog In Compaq NonStop SQL/MP and Compaq NonStop SQL/MX, a set of tables containing the descriptions of SQL objects such as tables, views, columns, indexes, files, and partitions. CGI See Common Gateway Interface (CGI). CISC See complex instruction set computing (CISC). class path The location where the JVM and other Java programs that are located in the /usr/tandem/java/bin directory search for class libraries (such as classes.zip).
Transaction API uses JTS and another uses TMF. Compaq NonStop Kernel operating system The operating system for Compaq systems. Compaq NonStop ODBC Server The Compaq implementation of ODBC. Compaq NonStop Series/RISC Compaq computers that support the Compaq NonStop Kernel operating system and are based on RISC technology. NonStop Series/RISC processors implement the RISC instruction set and are upwardly compatible with the Compaq NonStop Series (TNS) system-level architecture.
complex instruction set computing (CISC) A processor architecture based on a large instruction set, characterized by numerous addressing modes, multicycle machine instructions, and many special-purpose instructions. The goal of CISC design is to minimize the size of a program's machine code, minimize the number of program instructions fetched, use relatively few registers, and tolerate relatively dumb compilers.
D Data Control Language (DCL) The set of data control statements within the SQL/MP language. Data Definition Language (DDL) A Compaq language that describes the record and file structures of a database. When a database is created with DDL, the DDL compiler can create a library that other languages can use. Data Definition Language (DDL) dictionary A database that contains object definitions and record types created by the DDL compiler. It serves as a map of a user's business database.
See Domain Name Server (DNS). Domain Name Server (DNS) A Compaq product, part of TCP/IP, that provides the facilities for the maintenance and automated distribution of network resource name information. DNS permits decentralized administration of resource names and specifies redundancy of servers to provide a reliable query service for users. driver A class in JDBC that implements a connection to a particular database management system such as NonStop SQL/MP.
F fault tolerance The ability of a computer system to continue processing during and after a single fault (the failure of a system component) without the loss of data or function. G garbage collection The process that reclaims dynamically allocated storage during program execution. The term usually refers to automatic periodic storage reclamation by the garbage collector (part of the run-time system), as opposed to explicit code to free specific blocks of memory.
different color, font, or style. When the user activates the link (usually by clicking on it with the mouse), the browser displays the target of the link. hypertext A collection of documents (nodes) containing cross-references or links that, with the aid of an interactive browser, allow a reader to move easily from one document to another. Hypertext Mark-up Language (HTML) A hypertext document format used on the World Wide Web.
❍ Stub networks such as individual LANs interoperability One of the following: ❍ The ability to communicate, execute programs, or transfer data between dissimilar environments, including among systems from multiple vendors or with multiple versions of operating systems from the same vendor. Compaq documents often use the term connectivity in this context, while other vendors use connectivity to mean hardware compatibility.
The collection of conformance tests that any vendor's JDK must pass in order to be conformant with the Sun Microsystems specification. Java Core Classes See Core API. Java Database Connectivity (JDBC) The Java standard for access to relational databases such as SQL/MP or SQL/MX. Java Development Kit (JDK) The JVM, core libraries, and tools for Java. NonStop Java 2.1 consists of the full JDK 1.2.2 but does not fully support AWT. For more information on JDK 1.2.2, see the Sun Microsystems JDK 1.
The process that loads, links, verifies, and interprets Java bytecode. The NonStop Java JVM has been extended with a JIT Compiler. Java Web Server Sun Microsystems World Wide Web server and related classes, written in pure Java. Formerly called jeeves. Compaq does not have a license for Java Web Server, but Compaq supports servlets by using iTP Secure WebServer. For more information, see the Sun Microsystems Java Web Server document (http://jserv.java.sun.com/products/webserver/).
The Java class verifier, which verifies the validity of Java classes. Also, the command to run the Java class verifier. JCK See Java Conformance Kit (JCK). jdb The Java Debugger, which helps you find and fix errors in Java programs. Also, the command to run the Java Debugger. jdb uses the Java Debugger API. JDBC The Java standard for access to relational databases such as SQL/MP or SQL/MX. JDBC is a product name, not an abbreviation, but is generally considered to represent Java Database Connectivity.
See Java Virtual Machine (JVM). K key One of the following: ❍ A value used to identify a record in a database, derived by applying a fixed function to the record. The key is often simply one of the fields (a column if the database is considered as a table with records being rows). Alternatively, the key can be obtained by applying a function to one or more of the fields. ❍ A value that must be fed into the algorithm used to decode an encrypted message in order to reproduce the original plain text.
N native In the context of Java programming, something written in a language other than Java (such as C or C++) for a specific platform. native method A non-Java routine (written in a language such as C or C++) that is called by a Java class. native mode The operational environment in which native RISC instructions run. native2ascii The Native-to-ASCII converter, which converts a file with native-encoded characters into one with Unicode-encoded characters.
encoding and is then solely responsible for the external format. Object Transaction Service (OTS) The transaction service standard adopted by the OMG and used as the model for JTS. ODBC See Open Database Connectivity (ODBC). OLTP See online transaction processing (OLTP). OMG See Object Management Group (OMG). online transaction processing (OLTP) A method of processing transactions in which entered transactions are immediately applied to the database.
Pathsend interface The interface to a Pathway system that enables a Pathsend process to communicate with a server process. Pathsend process A client (requester) process that uses the Pathsend interface to communicate with a server process. A Pathsend process can be either a standard requester, which initiates application requests, or a nested server, which is configured as a server class but acts as a requester by making requests to other servers. Also called a Pathsend requester.
interface is separately defined in a numbered ANSI/IEEE standard or draft standard. The standards deal with issues of portability, interoperability, and uniformity of user interfaces. POSIX See Portable Operating System Interface X (POSIX). private key An encryption key that is not known to all parties. protocol A set of formal rules for transmitting data, especially across a network.
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 Remote Method Invocation (RMI) The Java package used for homogeneous distributed objects in an all-Java environment. ❍ requester See client. RISC See reduced instruction set computing (RISC). RMI See Remote Method Invocation (RMI). rmic The Java RMI stub compiler, which generates stubs and skeletons for remote objects.
serialization See Object Serialization. serialized object An object that has undergone object serialization. serialver The Serial Version Command, which returns the serialVersionUID of one or more classes. Also, the command to run the Serial Version Command. server One of the following: ❍ An implementation of a system used as a stand-alone system or as a node in an Expand network.
site update tape (SUT) The tape that Compaq sends to a customer, containing all of the software that the customer has purchased. To install the software, the customer uses the SUT as input to the INSTALL program or to the DSM/SCM program. skeleton In RMI, the complement of the stub. Together, skeletons and stubs form the interface between the RMI services and the code that calls and implements remote objects. socket A logical connection between two application programs across a TCP/IP network.
stub need not contain any code. Its only purpose is to prevent "undefined label" errors at link time. ❍ A local procedure in a remote procedure call (RPC). A client calls the stub to perform a task, not necessarily aware that the RPC is involved. The stub transmits parameters over the network to the server and returns results to the caller. Subsystem Control Facility (SCF) The interactive interface for configuring, controlling, and collecting information from Compaq data-communications subsystems.
Adobe (Acrobat Exchange PDF viewer). Formerly called Tandem Information Manager. transaction A user-defined action that a client program (usually running on a workstation) requests from a server. Transaction Management Facility (TMF) A set of Compaq software products that assures database integrity by preventing incomplete updates to a database. It can continuously save the changes that are made to a database (in real time) and back out these changes when necessary.
W World Wide Web (WWW) An Internet client-server hypertext distributed information retrieval system that originated from the CERN High-Energy 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.
Java Docs Home Page | Contents | Glossary | Prev Index ABCDEFGHIJKLMNOPQRSTUVWXYZ A Abbreviations used in this document Abstract Window Toolkit (AWT) Accessing NonStop SQL/MP databases Accessing NonStop SQL/MX databases Additional files in NonStop Java 2.
C C/C++ methods calling from Java debugging invoking the JVM from Cached row sets in JDBC 2.
aliases for creating and using when you can use which SQL statements support referring to Databases Directory, NonStop Java contents of structure of Default catalog and schema with JDBC/MX Debugging Deviations from JDBC in JDBC/MX batch updates updatable result set Distributed transactions in JDBC 2.
description of types of E Environment variables Execution of Java tools of NonStop Java as a stand-alone process as a web-based servlet from C or C++ code from RMI Extensions to JDBC in JDBC/MX internationalization interval data type F Failing Guardian socket calls Features of JDK 1.2.2 Features in JDBC Driver for NonStop SQL/MX deviations from JDBC extensions to JDBC unsupported features Feedback on this document, providing Files additional in NonStop Java 2.
IEEE implementation of G getConnection method I IEEE floating-point implementation Implementation specifics, Compaq Indexes See Database objects Installing NonStop Java J Java Abstract Window Toolkit (AWT) Java Checker (javachk) Java data types, converting NonStop SQL/MP data types to Java Database Connectivity See JDBC Java Debugger (jdb) Java Development Kit (JDK) Java Naming and Directory Interface (JNDI) Java Native Interface (JNI) Java tools, executing Java Transaction API (JTA) Java Transaction Ser
jdb (Java Debugger) JDBC DriverManager drivers See Drivers JDBC Driver for SQL/MP support for JDBC 2.
JDK (Java Development Kit) JIT (Just-in-Time) compiler JNDI (Java Naming and Directory Interface) JNDI for naming databases in JDBC 2.
See JDBC Driver for SQL/MP NonStop SQL/MX See JDBC Driver for NonStop SQL/MX Notation conventions O Object naming and mapping, SQL/MX P Passing NonStop SQL/MP statements to databases PATH environment variable Properties file Pthreads Pure Java drivers connecting to a database description of put() calls for alias creation R Reader comment card Related reading Compaq documents NonStop Java documents Sun Microsystems documents Remote Method Invocation (RMI) configuring DNS and TCP/IP for invoking the JVM fr
S Schema,default, with JDBC/MX Servlet, executing NonStop Java as SHORTANSI name type Sockets C or C++ methods and Java Checker (javachk) and RMI and TCP/IP configuration and SQL Conformance by JDBC/MX sqlmp driver See Drivers, standard SQL/MP See JDBC Driver for SQL/MP SQLMPBlob SQLMPCachedRowSet SQLMPClob SQLMPConnection SQLMPDatabaseMetaData SQLMPDataSource SQLMPDriver SQLMPPreparedStatement SQLMPResultSet SQLMPResultSetMetaData SQLMPStatement sqlmptx driver See Drivers, transaction-aware SQL/MX See JDBC
See Drivers, standard Standard extensions to JDBC 2.
nonautocommit mode and the standard driver nonautocommit mode and the transaction-aware driver Troubleshooting in JDBC/MP Truncation of data V Variables, environment Virtual Machine See Java Virtual Machine (JVM) W Web-based execution of NonStop Java Wrappers in general for Pthreads Y Your comments invited ABCDEFGHIJKLMNOPQRSTUVWXYZ Contents | Glossary | Prev NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
| Contents | Index | Glossary | Prev | Next List of Examples Section Title Example Title(s) Compaq Implementation Specifics ● Invocation API Demo Accessing NonStop SQL/MP Databases ● BlobInfo and BlobMapFile Properties Example ● Standard Driver Example ● Transaction-Aware Driver Example ● Pure Java Driver Example ● Passing SQL/MP Statements to a Database ● Specifying Properties Using the put() Method ● Specifying Properties in a Properties File ● How a Dangling Statement Can Be Created
| Contents | Index | Glossary | Prev | Next List of Figures Section Title Figure Title(s) Introduction to NonStop Java ● Relationship of JDK, NonStop Java, Servlets, and iTP Secure WebServer Accessing NonStop SQL/MP Databases ● Loading a JDBC Driver Class Into the JVM Accessing NonStop SQL/MX Databases ● Architecture of the JDBC Driver for SQL/MX Just-in-Time (JIT) Compiler ● Interpreter Mode ● Just-in-Time (JIT) Compiler Mode NonStop Java Programmer's Reference (426947-002) Copyright © 200
| Contents | Index | Glossary | Prev | Next List of Tables Section Title Table Title(s) About This Manual ● Document Sections Introduction to NonStop Java ● Supported JDK 1.2.2 Features ● Unsupported JDK 1.2.
NonStop Java Programmer's Reference (426947-002) Copyright © 2002, Compaq Computer Corporation. All rights reserved.
