HP NonStop JDBC Type 4 Driver Programmer's Reference ● Documentation on both the NonStop Technical Library and the product CD: ❍ HP NonStop JDBC Type 4 Driver Programmer's Reference ● Documentation on the NonStop Technical Library: ● HP NonStop JDBC Type 4 Driver API Reference Pages Documentation on the product CD only: ❍ Software Release Documents ❍ README Files Product Version HP NonStop JDBC Type 4 Driver V1.0 Supported Hardware Java enabled platforms that support JDK 1.4.1 or higher.
JDBC/MX Doc Home Page HP NonStop JDBC Type 4 Driver Programmer's Reference Abstract This document describes how to use the HP NonStop JDBC Type 4 Driver. The Type 4 driver provides Java applications with JDBC access to HP NonStop SQL/MX databases. The Type 4 driver for NonStop SQL/MX conforms where applicable to the standard JDBC 3.0 API from Sun Microsystems, Inc. Product Version HP NonStop JDBC Type 4 Driver V1.0 Client Platforms The Type 4 Driver supports Java enabled platforms that support JDK 1.4.
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 2004 Hewlett-Packard Development Company L.P.
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. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.
JDBC/MX Doc Home Page HP NonStop JDBC Type 4 Driver Programmer's Reference Contents ● ● ● About This Document ❍ 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 Type 4 Driver for NonStop SQL/MX ❍ JDBC/MX Architecture ❍ Sample Programs Installing and Verifying the Type 4 Driver ❍ Installation Requirements ❍ Product Fil
● ● ● Accessing SQL/MX Databases ❍ Communication Overview ❍ Security ❍ Connection to SQL/MX ■ Connection Using the DriverManager class ■ Connection Using the DataSource Interface ❍ Type 4 Driver Properties ❍ Stored Procedures ❍ Connection Pooling ❍ Statement Pooling ❍ Nonblocking SQL/MX Access Using the Type 4 Driver with WebLogic Server (WLS) 8.
● Index ● List of Examples ● List of Figures ● List of Tables JDBC/MX Doc Home Page HP NonStop JDBC Type 4 Driver Programmer's Reference (528781-003 ) © 2004 Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary About This Document This section explains these subjects: ● Is This Document for You? ● Document Structure ● Printing This Document ● Related Reading ❍ Type 4 Driver APIs ● Notation Conventions ● Abbreviations Is This Document for You? This HP NonStop™ JDBC Type 4 Driver Programmer's Reference is for experienced Java programmers who want to use the JDBC API, 3.0 to access SQL databases with NonStop SQL/MX.
Accessing SQL/MX Databases Explains how to access SQL/MX databases using the HP NonStop JDBC Type 4 driver. Using JDBC Type 4 Driver With BEA WebLogicServer 8.1 Explains how to use the JDBC Type 4 driver with Web Logic Server 8.1. HP NonStop JDBC Type 4 Driver Compliance Explains how the HP NonStop JDBC Type 4 driver differs from the Sun Microsystems JDBC standard. Lists unsupported features for NonStop SQL/MX and SQL/MP. Type 4 Driver Tracing and Logging Explains the tracing and logging facility.
Type 4 Driver APIs For information about APIs for the Type 4 Driver, see the following document in the NonStop Technical Library: HP NonStop JDBC Type 4 Driver API Reference Pages NonStop System Computing Documents The following NonStop system computing documents are available in the NonStop Technical Library. ● ● Additional Java-Oriented Products. These documenents are available in the Java category under Independent Products in the NonStop Technical Library (http://techlibrary.cac.cpqcorp.
❍ SQL/MX Installation and Management Guide Describes how to install and manage SQL/MX on a NonStop server. ● ❍ HP NonStop SQL/MX Connectivity Service Manual ❍ Describes the SQL/MX connectivity service (MXCS) on the NonStop server. SQL/MX Glossary ❍ Explains the terminology used in SQL/MX documentation. SQL/MX Query Guide ❍ Explains query execution plans and how to write optimal queries for SQL/MX.
● ● ● ● JDBC API Documentation, includes links to APIs and Tutorials (http://java.sun.com/j2se/1.4.1/docs/guide/jdbc/index.html) JDBC Data Access API, general information (http://java.sun.com/products/jdbc/index.html) JDBC Data Access API, FAQs for JDBC 3.0 (http://java.sun.com/products/jdbc/faq.html) JDBC API Javadoc Comments ❍ Core JDBC 3.0 API in the java.sql package (http://java.sun.com/j2se/1.4.1/docs/api/java/sql/package-summary.html) ❍ Optional JDBC 3.0 API in the javax.sql package (http://java.
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 the following example, spaces are not permitted before or after the period: subvolume-name.
LAN. local area network MBCS. Multibyte Character Set NonStop TS/MP. NonStop Transaction Services/MP OSS. Open System Services POSIX. portable operating system interface x RISC. reduced instruction set computing RVU. Release Version Update SPJ. stored procedure in Java SQLJ. embedded SQL in Java programs SQL/MP. Structured Query Language/MP SQL/MX. Structured Query Language/MX TCP/IP. Transmission Control Protocol/Internet Protocol TMF. Transaction Management Facility URL. uniform resource locator VM.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary | Prev | Next Introduction to the HP NonStop JDBC Type 4 Driver Type 4 Driver API Package The Type 4 driver package, com.tandem.t4jdbc, is shipped with the driver software. For class and method descriptions, see the JDBC Type 4 Driver API Reference Pages manual in the NonStop Technical Library. The HP NonStop JDBC Type 4 Driver (hereafter, Type 4 driver) implements JDBC technology that conforms to the standard JDBC 3.0 Data Access API.
5. MXCS receives JDBC Type 4 requests from the client and processes them using the SQL/MX 2.0 database engine. The following figure illustrates database access using the Type 4 driver: Samples The following samples are provided with the Type 4 Driver.
SQLMPSample StatementSample WLS_MedRecSample WLS_TwoPhaseAndPoolingSample For information on these samples, see the README file provided with the Type 4 driver software under the samples directory. Back to top JDBC/MX Docs Home Page | Contents | Index | Glossary | Prev | Next HP NonStop JDBC Type 4 Driver Programmer's Reference (528781-003 ) © 2004 Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MX Docs Home Page | Contents Prev | Next | Index | Glossary | Installing and Verifying the Type 4 Driver This section explains these subjects: ● Installation Requirements ● Product Files ● Setting CLASSPATH ● Verifying the Type 4 driver Installation Requirements Hardware and software requirements for the Type 4 Driver are described in the Softdoc file on the product CD on which the Type 4 driver is delivered. Read that document before installing the product.
Product Files The JDBC Type 4 client component is delivered as an independent product on CD, containing these files and directories (Note: this is a partial list.): ● a tar file (T1249.tar) that contains these product files: ❍ lib ■ t4sqlmx.jar ❍ samples ■ CallableStatementSample ■ common ■ DBMetaSample ■ PreparedStatementSample ■ README for samples ■ ResultSetSample ■ t4sqlmx.properties ■ SQLMPSample ■ WLSMedRecSample ■ WLSTwoPhaseAndPoolingSample ❍ install ■ product.
To run the installation check program, use the command: java t4sqlmxSanityCheck Back to top JDBC/MX Docs Home Page | Contents | Index | Glossary | Prev | Next HP NonStop JDBC Type 4 Driver Programmer's Reference (528781-003 ) © 2004 Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary Accessing SQL/MX Databases This section describes the following subjects: ● Communication Overview ● Data Sources ● Security ● Connection to SQL/MX ❍ Connection Using the DriverManager class ❍ Connection Using the DataSource Interface ■ Example Settings for Configuring Data Source Properties ● Type 4 Driver Properties ● Stored Procedures ● Connection Pooling ● Statement Pooling ● Thread-safe SQL/MX Access Communication O
Security Clients connect to the MXCS server with a valid Guardian user name and ID, using standard JDBC 3.0 APIs. An application can make multiple connections to MXCS using different user IDs, and creating different connection objects. The Type 4 driver provides for user name and password authentication before connecting to MXCS. The password is encrypted with a proprietary algorithm provided by the MXCS product.
catalog String See catalog. SQL/MX 2.0 database catalog value. schema String See schema. SQL/MX 2.0 database schema value. int See maxStatements Property. The total number of PreparedStatement objects that the connection pool should cache. See maxStatements Property. int See minPoolSize Property. Limits the number of physical connections that can be in the free connection pool. See minPoolSize Property. maxStatements minPoolSize maxPoolSize int See maxPoolSize Property.
❍ ❍ ● ● ● java.util.properties parameter have a higher precedence over the command-line properties. command-line properties have a higher precedence over file properties set through the -Dt4sqlmx.properties option. The connection pooling feature is available when the Java application uses the DriverManager class to obtain a JDBC connection. The connection pool size is determined by the maxPoolSize property value and minPoolSize property value.
T4LogLevel String See T4LogLevel. Logging level for the NonStop JDBC Type 4 Driver. T4LogFile String See T4LogFile. Logging file for the NonStop JDBC Type 4 Driver. connectionTimeOut int See connectionTimeOut. Number of seconds before the connection to MXCS times out. serverDataSource String See serverDataSource. Name of the MXCS server datasource to connect to. Example Settings For Configuring Data Source Properties To set data source properties in a t4sqlmx.properties file: ClassName=com.
Other NonStop JDBC Type 4 Driver properties: ● loginTimeOut ● ● datasourceName description catalog Sets the database catalog for the MXCS connection. For more information, see the SQL/MX Connectivity Services Manual. schema Sets the database schema for the MXCS connection. For more information, see the SQL/MX Connectivity Services Manual. url Sets the URL value for the MXCS association server.
● connections by physically closing them—not by adding them to the free pool. 0 means the connections are not physically closed; the connections are always added to the free pool when the connection is closed. maxPoolSize Property Sets the maximum number of physical connections that the pool can contain. These connections include both free connections and connections in use.
where t4log_file_name is a legal filename. If the property value is not set, the default for T4LogFile is system_temporary_directory/t4sqlmx_date.log. For example: ● On Solaris: /var/tmp/t4sqlmx_date.log ● On Windows XP: C:\TEMP\t4sqlmx_date.log or C:\Documents and Settings\mydir\Local Settings\Temp\t4sqlmx_date.log, depending on the location of the temp directory If the specified log file already exists, the logger appends messages to the existing file.
loginTimeOut When a connection is attempted for a period longer than the set value, in seconds, for loginTimeOut, the connection disconnects. ● Default = 60 seconds ● If set to 0 (zero), there is no login timeout specified. Stored Procedures Java applications can use the JDBC standard CallableStatement interface to run stored procedures (SPJs) by using the CALL statement. For further information, see the SQL/MX Guide to Stored Procedures in Java. Unsupported features ● An SPJ returning java.sql.
propertyCycle int The interval, in seconds, that the pool should wait before enforcing the current policy defined by the values of the above connection pool properties. Connection Pooling With the DriverManager Class Connection pooling is available by default when your JDBC application uses the DriverManager class for connections.
● Troubleshooting Statement Pooling Note the following JDBC Type 4 driver for NonStop SQL/MX implementation details if you are troubleshooting statement pooling: ● JDBC Type 4 driver for NonStop SQL/MX looks for a matching PreparedStatement object in the statement pool and reuses the PreparedStatement. The matching criteria include the SQL string, current catalog, current schema, current transaction isolation, and resultSetHoldability.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary Using the Type 4 Driver With WebLogic Server(WLS) 8.
For detailed information about WebLogic Server, see the BEA WebLogic Server documentation, which is located at the following URL: http://edocs.bea.com/wls/docs81/index.html. This section discusses features of BEA WLS 8.1 that apply to use with the Type 4 driver. Compatibility The Type 4 driver is compatible with BEA WLS version 8.1 or later. Note: BEA WLS 7.0 Last Agent Optimization feature is not supported. Therefore, the Type 4 driver can be used with BEA WLS 7.0 for local transactions only.
BEA WLS 8.1 Supported Transaction Scenario BEA WLS 8.
Connection and Statement Pooling The Type 4 driver supports all interfaces required for WLS 8.1 connection pooling and statement pooling. A WLS 8.1 JDBC sample is provided with the Type 4 driver product for demonstrating connection pooling and integration. WLS8.1 implements the connection pooling component. The WLS8.1 application server maintains the cache of pooled objects, and retrieves an object when the client requests a connection.
and made available for future requests. If the connection cannot be initialized, the pooling component discards the pooled connection object. To enable WLS 8.1 application servers to manage the connection pool, the Type 4 driver provides methods that get and set connection pool configuration properties as per the JDBC 3.0 specification.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary Type 4 Driver Compliance The Type 4 driver conforms where applicable to the Sun Microsystems JDBC 3.0 API specification. However, this driver differs from the JDBC standard in some ways. This subsection describes the JDBC methods that are not supported, the methods and features that deviate from the specification, and features that are HP extensions to the JDBC standard.
parameterName) CallableStatement.executeBatch() Connection.releaseSavepoint(Savepoint savepoint) Connection.rollback(Savepoint savepoint) Connection.setSavepoint() Connection.setSavepoint(String name) The particular Connection methods are not supported. PreparedStatement.setArray(int parameterIndex, Array x) PreparedStatement.setBlob(int parameterIndex, Blob x) PreparedStatement.setClob(int parameterIndex, Clob x) PreparedStatement.setRef(int parameterIndex, Ref x) PreparedStatement.
ResultSet.getBlob(int columnIndex) ResultSet.getBlob(String columnName) ResultSet.getClob(int columnIndex) ResultSet.getClob(String columnName) ResultSet.updateBlob(int columnIndex) ResultSet.updateBlob(String columnName) ResultSet.updateClob(int columnIndex) ResultSet.updateClob(String columnName) The particular ResultSet methods are not supported for access of SQL/MP user tables only. The following methods in the java.
javax.sql.RowSet javax.sql.RowSetInternal javax.sql.RowSetListener javax.sql.RowSetMetaData javax.sql.RowSetReader javax.sql.RowSetWriter RowSet is not implemented in the JDBC Driver for SQL/MX. You can, however, download reference implementation of RowSet from Sun Microsystems (http://developer.java.sun.com/developer/earlyAccess/crs/). For additional information about deviations for some methods, see Deviations.
javax.sql.DataSource.setLogWriter This method has no effect unless the JDBC trace facility is enabled; for information on the JDBC trace facility, see the NonStop Server for Java Programmer's Reference. java.sql.Connection.createStatement(...) java.sql.Connection.prepareStatement(...) The Type 4 driver 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.
Types.CHAR Types.CLOB Types.DATE Types.DECIMAL Types.DISTINCT Yes No Yes Yes No Types.DOUBLE Yes Types.FLOAT Types.INTEGER Types.JAVA_OBJECT Yes Yes No Data type is mapped by SQL/MX 2.0. Data type varies from that used for table creation. Yes Maximum length is 4018 No Yes Yes No Yes No Yes Yes Data type is mapped by SQL/MX 2.0. Data type varies from that used for table creation. Data type is mapped by SQL/MX 2.0. Data type varies from that used for table creation. Yes Data type is mapped by SQL/MX 2.0.
DATETIME SECOND DATETIME FRACTION Floating-Point Support The Type 4 driver supports only IEEE floating-point data to be passed between the application client and the Type 4 driver. Note: Any data access to or from a column with Tandem floating-point format in SQL/MP, may result in loss of precision of the data. SQLJ Support The Type 4 driver supports non-customized SQLJ applications, but does not support customized SQLJ applications.
● ● ● Security context (user name and password) implicit propagation from AppServer to the NonStop JDBC Tpe 4 Driver. IPV6 protocol stack. (IPV6 addressing is emulated over IPV4 on the MXCS server side) Distributed transactions. Restrictions ● ● The Type 4 driver supports only database features that are supported by NonStop SQL/MX 2.0 and SPJ. Therefore, the Type 4 driver is not fully compliant with JDBC 3.0 specifications.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary Type 4 Driver Tracing and Logging The Type 4 driver provides a function for logging error and trace messages using the java.util.logging.logger feature of the JDK1.4.1. The driver generates event messages in the trace file as necessary. Tracing for the client is turned on by setting the T4LogLevel property. Set the log file location and level of logged messages through the logging properties T4 LogFile and T4LogLevel.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary Migration Driver You Are Migrating From JDBC Type 3 Driver Code Configuration Changes Changes No url, catalog, schema, logging properties NonStop JDBC/MX Driver No url, catalog, schema, logging properties SequeLink JDBC Driver No url, catalog, schema, logging properties Considerations N.A. Application not portable if using: ● HP extension cpqPrepare ● BLOB/CLOB Application not portable if using SequeLink specific features.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index Type 4 Driver Error Messages Messages 29000 through 29249 29001-29009 29010-29019 29020-29027 29030-29039 29040-29049 29050-29059 29060-29068 Messages 29100 through 29170 01000 through 08000 08001 through 08010 S1000 29100-29109 01000-07999 29110-29119 08001-08010 29120-29129 S1000 29130-29139 29140- 29149 29150-29159 29160-29170 Messages are listed in numerical SQLCODE order.
[back to the top] 29003 HY000 Statement does not exist Cause: A validation attempt was made on the getter or exec invocation on a closed statement. Effect: The getter or exec invocation validation fails. Recovery: Issue validateGetInvocation() or validateExecDirectInvocation when the statement is open. [back to the top] 29004 HY024 Invalid transaction isolation value Cause: An attempt was made to set the transaction isolation level to an invalid value. Effect: SQLMXConnection.
29007 07009 Invalid descriptor index Cause: A ResultSetMetadata column parameter or a ParameterMetaData param parameter is outside of the descriptor range. Effect: The ResultSetMetadata or ParameterMetaData method data is not returned as expected. Recovery: Validate the column or parameter that is supplied to the method. [back to the top] 29008 24000 Invalid cursor state Cause: The ResultSet method was called when the connection was closed. Effect: The method call does not succeed.
Recovery: Make sure to validate the column that is supplied to the method. [back to the top] 29012 07006 Restricted data type attribute violation Cause: An attempt was made to execute a method either while an invalid data type was set or the data type did not match the SQL column type. Effect: The interface method is not executed. Recovery: Make sure the correct method and Java data type is used for the column type. [back to the top] 29013 HY024 Fetch size is less than 0 Cause: The size set for ResultSet.
29018 22018 Invalid character value in cast specification Cause: An attempt was made to convert a string to a numeric type but the string does not have the appropriate format. Effect: Strings that are obtained through a getter method cannot be cast to the method type. Recovery: Validate the string in the database to make sure it is a compatible type.
[back to the top] 29026 HY000 Transaction can't be committed or rolled back when AutoCommit mode is on Cause: An attempt was made to commit a transaction while AutoCommit mode is enabled. Effect: The transaction is not committed. Recovery: Disable AutoCommit. Use the method only when the AutoCommit mode is disabled. [back to the top] 29027 HY011 SetAutoCommit not possible, since a transaction is active Cause: An attempt was made to call the setAutoCommit() mode while a transaction was active.
29032 23000 Row has been modified since it is last read Cause: An attempt was made to update or delete a ResultSet object row while the cursor was on the insert row. Effect: The ResultSet row modification does not succeed. Recovery: Move the ResultSet object cursor away from the row before updating or deleting the row. [back to the top] 29033 23000 Primary key column value can't be updated Cause: An attempt was made to update the primary-key column in a table. Effect: The column is not updated.
TYPE_SCROLL_SENSITIVE and TYPE_SCROLL_INSENSITIVE types are scrollable. [back to the top] 29038 HY107 Row number is not valid Cause: A ResultSet absolute() method was called when the row number was set to 0. Effect: The cursor is not moved to the specified row number. Recovery: Supply a positive row number (specifying the row number counting from the beginning of the result set), or supply a negative row number (specifying the row number counting from the end of the result set).
[back to the top] 29042 HY000 Fetch size value is not valid Cause: An attempt was made to set the fetch-row size to a value that is less than 0. Effect: The number of rows that are fetched from the database when more rows are needed is not set. Recovery: For the setFetchSize() method, supply a valid row value that is greater than or equal to 0.
Recovery: Make sure the data to be retrieved is within a valid data-type range. [back to the top] 29047 HY000 Batch update failed. See next exception for details Cause: One of the commands in a batch update failed to execute properly. Effect: Not all the batch-update commands succeed. See the subsequent exception for more information. Recovery: View the subsequent exception for possible recovery actions.
29051 01S02 ResultSet type changed to TYPE_SCROLL_INSENSITIVE Cause: The Result Set Type was changed. Effect: None. Recovery: This message is reported as an SQL Warning. It is an informational message only; no recovery is needed. [back to the top] 29053 HY000 SQL SELECT statement is invalid in executeUpdate() method Cause: A select SQL statement was used in the executeUpdate() method. Effect: The SQL query not performed exception is reported.
[back to the top] 29058 HY000 Connection is not associated with a PooledConnection object Cause: The getPooledConnection() method was invoked before the PooledConnection object was established. Effect: A connection from the pool cannot be retrieved. Recovery: Make sure a PooledConnection object is established before using the getPooledConnection() method. [back to the top] 29059 HY000 jdbcmx.
[back to the top] 29063 HY00 Transaction error {0} - {1} while obtaining start data locator Cause: A transaction error occurred when the JDBC/MX driver attempted to reserve the data locators for the given process while inserting or updating a LOB column. Effect: The application cannot insert or update the LOB columns. Recovery: Check the file-system error in the message and take recovery action accordingly.
29101 HY000 Contact your HP service provider. Cause: Internal error. Effect: Operation fails. Recovery: None. Report entire message to your service provider. [back to the top] 29102 HY000 Error while parsing address address Cause: The address format was not recognized. Effect: Operation fails. Recovery: Refer to url for proper address format. [back to the top] 29103 HY000 Address is null Cause: The address was empty. Effect: Operation fails. Recovery: Refer to url for proper address format.
29106 HY000 Expected address format: jdbc:subprotocol::subname Cause: N.A. Effect: N.A. Recovery: This is an informational message. Refer to url for proper address format. [back to the top] 29107 HY000 Address not long enough to be a valid address. Cause: The address length was too short to be a valid address. Effect: Operation fails. Recovery: Refer to url for proper address format. [back to the top] 29108 HY000 Expecting \\/.
[back to the top] 29111 HY000 Unable to evaluate address address Cause: cause Cause: The driver could not determine the IP address for a host. Effect: The operation fails. Recovery: The address or machine name may not be properly qualified or there my exist a security restriction. See the documentation for the getAllByName method in the java.net.InetAddress class. Include a valid IP address or machine name. Refer to url for proper address format. [back to the top] 29112 HY000 Missing ']'.
29115 HY000 Error while reading from socket. Cause: cause Cause: Socket read error. Effect: The operation fails. Recovery: Use the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29116 HY000 Socket is closed. Cause: Socket close error. Effect: The operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29117 HY000 Error while closing session.
[back to the top] 29120 HY000 An association server connect message error occurred. Cause: Unable to connect to the MXCS association server. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29121 HY000 A close message error occurred. Cause: cause Cause: Unable to perform this operation. Effect: Operation fails.
19124 HY000 An execute direct message error occurred. Cause: cause Cause: Unable to perform this operation. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29125 HY000 An execute direct rowset message error occurred. Cause: Unable to perform this operation. Effect: Operation fails.
29128 HY000 A fetch perf message error occurred. Cause: cause Cause: Unable to perform this operation.. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29129 HY000 A fetch rowset message error occurred. Cause: cause Cause: Unable to perform this operation.. Effect: Operation fails.
29132 HY000 A prepare message error occurred. Cause: cause Cause: Unable to perform this operation.. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29133 HY000 A prepare rowset message error occurred. Cause: cause Cause: Unable to perform this operation.. Effect: Operation fails.
29136 HY000 An association server connect reply occurred. Exception: exception Exception detail: exception_detail Error text/code: error text_or_code Cause: Unable to perform this operation. Effect: Operation fails. Recovery: Evaluate any error or error detail information accompanying this message. Check the EMS event log for server errors. See the Operator Messages Manual for server errors. See the SQL/MX Connectivity Service Manual for corrective action.
29140 HY000 An execute direct reply error occurred. Cause: Unable to perform this operation.. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29141 HY000 An execute direct rowset reply error occurred. Cause: Unable to perform this operation.. Effect: Operation fails.
[back to the top] 29145 HY000 A fetch rowset reply error occurred. Cause: Unable to perform this operation.. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29146 HY000 A get sql catalogs reply error occurred. Cause: Unable to perform this operation.. Effect: Operation fails.
[back to the top] 29150 HY000 A set connection option reply error occurred. Cause: Unable to perform this operation.. Effect: Operation fails. Recovery: Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. [back to the top] 29151 HY000 A terminate dialogue reply error occurred. Cause: Unable to perform this operation. Effect: Operation fails.
[back to the top] 29155 HY000 Unknown message type Cause: Internal error. Effect: Operation fails. Recovery: Check the EMS event log for server errors. See the Operator Messages Manual for server errors. See the SQL/MX Connectivity Service Manual for corrective action. [back to the top] 29156 HY000 An error was returned from the server.
[back to the top] 29159 HY000 The message header contained the wrong signature. Expected: expected_signature Actual: actual_signature Cause: The server's signature differs from the expected version. Effect: Operation fails. Recovery: Evaluate any error or error detail information accompanying the message. Install compatible versions of the driver and MXCS server. [back to the top] 29160 HY000 The message header was not long enough.
[back to the top] 29163 08001 ODBC Services not yet available: server Cause: A message returned by the server. Effect: Operation fails. Recovery: Retry and/or wait for a server to become available. Configure MXCS server data source with more servers. [back to the top] 29164 08001 DataSource not yet available or not found: error Cause: A message returned by the server. Effect: Operation fails. Recovery: Create server data source and/or configure server data source with more servers.
[back to the top] 29168 HY000 Unknown reply message error: error error detail: error_detail Cause: Server returned an error. Effect: Operation fails. Recovery: Evaluate any error or error detail information accompanying the message. Check the EMS event log for server errors. See the Operator Messages Manual for server errors. See the SQL/MX Connectivity Service Manual for corrective action.
[back to the top] 01118 S1008 Operation cancelled. Cause: The operation was cancelled. Effect: Operation fails. Recovery: Retry operation. [back to the top] 08001 HY000 Retry attempts to connect to the datasource failed, May be ODBC server not able to register to the ODBC service process. Cause: A server error. Effect: Operation fails. Recovery: Evaluate any error or error detail information accompanying the message. Check the EMS event log for server errors.
[back to the top] JDBC/MX Docs Home Page | Contents | Index | Prev | Next HP NonStop JDBC Type 4 Driver Programmer's Reference (528781-003 ) © 2004 Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index Glossary ABCDEFGHIJLMNOPQRSTUVWXYZ 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.
autocommit mode A mode in which a JDBC driver automatically commits a transaction without the programmer's calling commit(). B base table A table that has physical existence: that is, a table stored in a file. branded A Java virtual machine 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.
The operation demanded by an operator or program; a demand for action by, or information from, a subsystem. A command is typically conveyed as an interprocess message from a program to a subsystem. concurrency A condition in which two or more transactions act on the same record in a database at the same time. To process a transaction, a program must assume that its input from the database is consistent, regardless of any concurrent changes being made to the database.
The JDBC class that manages drivers. E exception An event during program execution that prevents the program from continuing normally; generally, an error. Java methods raise exceptions using the throw keyword and handle exceptions using try, catch, and finally blocks. Expand The NonStop Kernel operating system network that extends the concept of fault tolerance to networks of geographically distributed NonStop systems.
H Hotspot virtual machine See Java Hotspot virtual machine. 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 JDBC Type 4 Driver for NonStop SQL/MX The product that provides access to SQL/MX 2.0 and conforms to the JDBC API. HP NonStop Kernel operating system The operating system for NonStop systems.
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 Markup Language (HTML) A hypertext document format used on the World Wide Web. Hypertext Transfer Protocol (HTTP) The client-server Transmission Control Protocol/Internet Protocol (TCP/IP) used on the World Wide Web for the exchange of HTML documents. I IEC See International Electrotechnical Commission (IEC).
❍ environments, including among systems from multiple vendors or with multiple versions of operating systems from the same vendor. HP documents often use the term connectivity in this context, while other vendors use connectivity to mean hardware compatibility. Within a NonStop system node, the ability to use the features or facilities of one environment from another.
Java 4 implements the Java HotSpot virtual machine. Java Naming and Directory Interface (JNDI) A standard extension to the Java platform, which provides Java technology-enabled application programs with a unified interface to multiple naming and directory services. Java Native Interface (JNI) The C-language interface used by C functions called by Java classes. Includes an Invocation API that invokes a Java VM from a C program. Java Run-time The Java VM and the Core API.
L LAN See local area network (LAN). local area network (LAN) A data communications network that is geographically limited (typically to a radius of 1 kilometer), allowing easy interconnection of terminals, microprocessors, and computers within adjacent buildings. Ethernet is an example of a LAN. M MXCI SQL/MX Conversational Interface. MXCS The HP NonStop SQL/MX Connectivity Service.
The informal name of the NonStop Server for Java, based on the Java 2 Standard Edition, SDK 1.4.1. This product is a Java environment that supports compact, concurrent, dynamic, and portable programs for the enterprise server. NonStop Technical Library (NTL) The browser-based interface to NonStop computing technical information. NTL replaces HP Total Information Manager (TIM). NSK See HP NonStop Kernel operating system. O ODBC See Open Database Connectivity (ODBC).
POSIX See Portable Operating System Interface X (POSIX). protocol A set of formal rules for transmitting data, especially across a network. Low-level protocols define electrical and physical standards, bit-ordering, byte-ordering, and the transmission, error detection, and error correction of the bit stream. High-level protocols define data formatting, including the syntax of messages, the terminal-to-computer dialogue, character sets, sequencing of messages, and so on.
A method used to modify a data item. For example, the Connection.setAutoCommit() method changes the transaction mode of the JDBC driver's connection to an SQL/MX database. Compare to get() method. SQL context An instantiation of the SQL executor with its own environment. SQLJ Also referred to as SQLJ Part 0, the "Database Language SQL—Part 10: Object Language Bindings (SQL/OLB)" part of the ANSI SQL-2002 standard that allows static SQL statements to be embedded directly in a Java program.
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. TMF See HP NonStop Transaction Management Facility (TMF) transaction A user-defined action that a client program (usually running on a workstation) requests from a server.
V virtual machine (VM) A self-contained operating environment that behaves as if it is a separate computer. See also Java virtual machine and Java Hotspot virtual machine. 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.
JDBC/MX Docs Home Page | Contents | Prev | Next | Glossary Index ABCDEFGHIJKLMNOPQRSTUVWXYZ A Abbreviations used in this document Accessing SQL/MX Databases ANSI Architecture Type 4 driver Audience for this document APIs B Blocking Java VM process See Nonblocking access C Catalog, default Character set encodings CLASSPATH environment variable Compliance Connecting to SQL/MX using the DataSource interface using the DriverManager class Connection pooling using the basic DataSource API with the DriverManag
D DataSource interface connection pooling dataSourceName property Data types support of Demonstration programs summary Document structure DriverManager class connection pooling E encodings support Error messages Extensions to JDBC internationalization F Features in the Type 4 driver deviations from JDBC unsupported features File encoding File locations installation Floating point support G getConnection method See Connecting to SQL/MX
H HP extensions, JDBC 3.0 API I IEEE floating point Installation, verifying ISO88591 character set J java command-line options enabling tracing setting Type 4 driver properties Java Database Connectivity accessing SQL/MX databases See also JDBC API, 3.0 JDBC API, 3.
M maxPoolSize property maxStatements property Messages Migrating applications minPoolSize property Multibyte character set (MBCS) data character set encodings supported character sets Multithreaded Java application N Nonblocking SQL/MX access NonStop SQL/MX documents Notation conventions O P Programs, sample Properties DataSource object DriverManager class Type 4 driver properties R Related reading Type 4 Driver documents
NonStop system computing documents Sun Microsystems documents S Sample programs Schema, default SPJs See Stored procedures SQL conformance SQLException SQLJ Statement pooling feature description with WebLogicServer Stored procedures T Tandem floating point Threads, blocking T4LogFile property T4LogLevel property Tracing See logging Troubleshooting connection pooling statement pooling Type 4 driver U UCS2 character set Unicode character set
V Verifying installation W WebLogic Server WLS ABCDEFGHIJKLMNOPQRSTUVWXYZ JDBC/MX Docs Home Page | Contents | Glossary | Prev | Next HP NonStop JDBC Type 4 Driver Programmer's Reference (528781-003 ) © 2004 Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MX Docs Home Page | Contents | Prev | Next | Index | Glossary List of Examples Section Title Example Title(s) Installing and Verifying JDBC/MX ● Verifying the JDBC Type 4 Driver for NonStop SQL/MX Accessing SQL/MX Databases ● Example Settings for Configuring Data Source Properties JDBC/MX Docs Home Page | Contents | Index | Glossary | Prev | Next HP NonStop JDBC Type 4 Driver Programmer's Reference (528781-003 ) © 2004 Hewlett-Packard Development Company L.P. All rights reserved.
JDBC/MX Docs Home Page | Contents Prev | Next | Index | Glossary | List of Figures Section Title Figure Title(s) Introduction to the HP NonStop JDBC Type 4 Driver ● Architecture of the JDBC Type 4 Driver for NonStop SQL/MX Accessing SQL/MX Databases ● Communication Overview Using the Type 4 Driver with WebLogic Server (WLS) 8.1 ● BEA WLS 8.1 Supported Transaction Scenario Using the Type 4 Driver with WebLogic Server (WLS) 8.1 ● BEA WLS 8.
JDBC/MX Docs Home Page | Contents | Index | Glossary | Prev List of Tables Section Title Table Title(s) About This Manual ● Document Sections Introduction to JDBC Type 4 Driver for NonStop SQL/MX ● Sample Programs Summary Accessing SQL Databases With SQL/MX ● JDBC Type 4 Driver for NonStop SQL/MX Properties Used With the DriverManager Class ● DataSource Object Properties ● Patterns in the Logging File Name ● Standard ConnectionPoolDataSource Object Properties ● Corresponding SQL/MX Charac
