Version and Copyright Information Document Title HP NonStop JDBC Type 4 Driver Programmer's Reference Abstract This document describes how to use the HP NonStop™ JDBC Type 4 Driver. This driver provides Java applications running on a foreign platform with JDBC access to an HP NonStop SQL/MX database running on the HP NonStop platform. Where applicable, the Type 4 driver conforms to the standard JDBC 3.0 API from Sun Microsystems, Inc. Product Version HP NonStop JDBC Type 4 Driver 1.
Legal Notices © Copyright 2005 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation. This 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.
HP NonStop JDBC Type 4 Driver Programmer's Reference Next Version and Copyright Information Published September 2005 Table of Contents What's New in This Guide About This Guide Is This Document for You? Document Structure Printing This Document Related Reading Type 4 Driver APIs NonStop System Computing Documents Notation Conventions Abbreviations 1.
JDBC Data Source (client-side) MXCS Data Source (server-side) Security How to Make a Connection to SQL/MX Connection by Using the DataSource Interface Overview of Tasks to Deploy DataSource Objects DataSource Object Properties Programmatically Creating an Instance of the DataSource Class Programmatically Registering the DataSource Object Retrieving a DataSource Instance by using JNDI and to the Data Source Specifying the Properties File that Configures the Data Source Connection by Using the DriverManager C
Creating and Using a Properties File Setting Properties in the Command Line Precedence of Property Specifications Type 4 Driver Property Descriptions blobTableName Property catalog Property clobTableName Property connectionTimeout Property dataSourceName Property description Property initialPoolSize Property ISO88591 Property KANJI Property KSC5601 Property language Property LOB Table Name Properties loginTimeout Property maxIdleTime Property maxPoolSize Property maxStatements Property minPoolSize Property
5.
Using MXCI To Create Base Tables that Have LOB Columns Using JDBC Programs To Create Base Tables that Have LOB Columns Managing LOB Data by Using the Lob Admin Utility Running the Lob Admin Utility Help Listing from the Type 4 Lob Admin Utility Creating LOB Tables Using SQL/MX Triggers to Delete LOB Data Backing Up and Restoring LOB Columns Limitations of LOB Data (CLOB and BLOB Data Types) 7.
JDBC Drivers Third-Party Databases Operating Systems 10. Messages About the Message Format Type 4 Driver Error Messages A. Sample Programs Accessing CLOB and BLOB Data Sample Program Accessing CLOB Data Sample Program Accessing BLOB Data Glossary Index List of Tables 1. Document Chapters 3.1. Corresponding SQL/MX Character Sets and Java Encoding Sets 4.1. Connection Control Properties 4.2. Pooling Management Properties 4.3. Operations on CLOB and BLOB Data 4.4. Internationalization Properties 4.5.
What's New in This Guide Prev Next What's New in This Guide This edition (part number 529651-002) of the HP NonStop JDBC Type 4 Driver Programmer's Reference describes using the Type 4 driver version 1.1. This edition is an minor update to the previous edition, 529651-001. The new features listed in this edition are cumulative for this update and the previous edition. This edition, therefore, includes changes in the manual since the 528781-003 edition, which described the Type 4 driver version 1.0.
❍ ISO88591 Property ❍ KANJI Property ❍ language Property ❍ networkTimeout Property ❍ properties Property ❍ reserveDataLocators Property ❍ translationVerification Property ● Migration considerations for migrating from version 1.0 of the NonStop JDBC Type 4 Driver product in Migration. ● Added the following terms to the glossary: base table BLOB CLOB data source LOB LOB table ● Removed the javax.sql.DataSource.
About This Guide Prev Next About This Guide Is This Document for You? Document Structure Printing This Document Related Reading Type 4 Driver APIs NonStop System Computing Documents 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 access NonStop SQL/MX with the Type 4 driver. This document assumes you are already familiar with: ● J2EE or Java applications running on JDK 1.4.
Describes working with BLOB and CLOB data in JDBC applications using the standard interface described in the JDBC 3.0 API specification. Describes the database management (administrative) tasks for Chapter 6, Managing the SQL/MX Tables for BLOB adding and managing the tables for BLOB and CLOB data. The and CLOB Data Type 4 driver uses SQL/MX tables in implementing support for BLOB and CLOB data access.
● JDBC 3.0 Specification, available for downloading from Sun Microsystems (http://java.sun.com/products/jdbc/download.html). ● 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.
MXCI commands and utilities. Notation Conventions Bold Type Bold type within text indicates terms defined in the Glossary. For example: abstract class Computer Type Computer type letters within text indicate keywords, reserved words, command names, class names, and method names; enter these items exactly as shown. For example: myfile.c Italic Computer Type Italic computer type letters in syntax descriptions or text indicate variable items that you supply.
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.filename Line Spacing If the syntax of a command is too long to fit on a single line, each line that is to be continued on the next line ends with a backslash (\) and each continuation line begins with a greater-than symbol (>).
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. virtual machine WWW.
Chapter 1. Introduction to HP NonStop JDBC Type 4 Driver Prev Next Chapter 1. Introduction to HP NonStop JDBC Type 4 Driver Type 4 Driver API Package Type 4 Driver Architecture Client Platforms Supported Accessing a Database with the Type 4 Driver Samples 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 NonStop JDBC Type 4 Driver API Reference manual in the NonStop Technical Library.
Client Platforms Supported Java enabled platforms that support JDK 1.4.1 or higher. For a detailed list, please refer to the softdoc file delivered with the product, either the product CD or on the website for Scout for NonStop Servers at HP NonStop eServices portal (https://onepoint.nonstop.compaq.com/). Registration is required at the website. Accessing a Database with the Type 4 Driver 1. A Java client application establishes a connection. 2.
Type 4 driver, through the MXCS Service, Accesses an SQL/MX Database Samples The following samples are provided with the Type 4 driver. Sample CallableStatementSample DBMetaSample PreparedStatementSample ResultSetSample SQLMPSample StatementSample WLS_MedRecSample Description Demonstrates the invocation of a stored procedure in Java (SPJ).(1) Gets metadata from a table by using the Connection interface and ResultSetMetaData interface.
Notes: 1. Creates, populates and drops sample SQL/MX tables. 2. The sample’s documentation explains how to create the SQL/MX tables. For information on these samples, see the README file provided with the Type 4 driver software under the samples directory. Prev About This Guide Part Number 529651 Up Home Next Chapter 2.
Chapter 2. Installing and Verifying the Type 4 Driver Prev Next Chapter 2. Installing and Verifying the Type 4 Driver 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 delivered with the product, either on the product CD or on the website for Scout for NonStop Servers at HP NonStop eServices portal (https://onepoint.nonstop.compaq.com/).
● a tar file (T1249.tar) that contains these product files: ❍ lib ● ❍ ❍ samples ● CallableStatementSample ● common ● DBMetaSample ● PreparedStatementSample ● README for samples ● ResultSetSample ● t4sqlmx.properties ● SQLMPSample ● WLSMedRecSample ● WLSTwoPhaseAndPoolingSample docs ● ❍ white papers install ● ● t4sqlmx.jar product.contents (test input file for install, uninstall, and platform fixing) README.
This command displays output similar to: Version procedure: T1249_V11_15MAY05_HP_NONSTOP(TM)_JDBCT4_2005_04_28 To run the installation check program, use the command: java t4sqlmxSanityCheck Prev Chapter 1. Introduction to HP NonStop JDBC Type 4 Driver Part Number 529651 Up Home Next Chapter 3.
Chapter 3. Accessing SQL Databases with SQL/MX Prev Next Chapter 3.
Illustrates the three layers of the Type 4 driver—the API layer, IDL layer, and the Transport layer— to the MXCS association server Data Sources JDBC Data Source (client-side) MXCS Data Source (server-side) The term data source logically refers to a database or other data storage entity.
Note: There is no secure wire communication such as SSL provided for the communication between Type 4 driver and the MXCS server.
DataSource Object Properties A DataSource object has properties that identify and describe the actual data source that the object represents. These properties include such information as the URL for the MXCS association server, the database schema and catalog names, the location of the database server, the name of the database, and so forth. Note: When a JDBC application uses any server data source, the data source must be started before using it.
below together with the application code to perform the operation. 1. Import the packages. import javax.naming.*; import java.sql.*; import javax.sql.DataSource; 2. Create the initial context. Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.fscontext.RefFSContextFactory"); try { Context ctx = new InitialContext(env); } catch( ... ) { ... } 3.
-Djdbc.drivers=com.tandem.t4jdbc.SQLMXDriver ● Uses the Class.forName method programmatically within the application: Class.forName("com.tandem.t4jdbc.SQLMXDriver") ● Adds the Type 4 driver class to the java.lang.System property jdbc.drivers property within the application: jdbc.drivers=com.tandem.t4jdbc.SQLMXDriver Establishing the Connection The DriverManager.getConnection method accepts a string containing a Type 4 driver URL.
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. The following SPJ features are not supported: ● An SPJ returning java.sql.
Guidelines for Statement Pooling ● To enable statement pooling, set the maxStatements property to an integer value greater than 0 and enable connection pooling. See Connection Pooling for more information. ● Enabling statement pooling for your JDBC applications might dramatically improve the performance. ● Explicitly close a prepared statement by using the Statement.close method because PreparedStatement objects that are not in scope are also not reused unless the application explicitly closes them.
corruption. "Update ... Where Current of" Operations The fetch size on a ResultSet must be 1 when performing an update ... where current of cursor SQL statement. If the value of the fetch size is greater than 1, the result of the update ... where current of operation might be one of the following: ● An incorrect row might be updated based on the actual cursor position. ● An SQLException might occur because the cursor being updated might have already been closed. Note: By default, the fetch size is 1.
ISO88591 ISO88591_1 KANJI SJIS KSC5601 EUC_KR A description of these character sets appears in the following table, which summarizes the character sets supported by SQL/MX. Table 3.1. Corresponding SQL/MX Character Sets and Java Encoding Sets SQL/MX Character Set Corresponding Java Encoding Set—Canonical Name for java.io and java.lang API ISO88591 ISO88591_1 KANJI SJIS KSC5601 EUC_KR Description Single-character, 8-bit, character set for character-data type.
> java –DISO88591=SJIS test1.java The following method invocation sets column one of stmt to the String “abcd” where “abcd” is encoded as SJIS. The charset parameter to the String getBytes method is SJIS stmt.setString(1, “abcd”); Controlling What Happens on an Exception You can use the translationVerification property to explicitly define the behavior of the driver if the driver cannot translate all or part of an SQL parameter. The value portion of the property can be TRUE or FALSE.
b1[3] = 0x42; / String k1 = new String(b1, “SJIS”); Internally, the JVM stores k1 as UCS2 in 4 octets (bytes). The UCS2 encoding would be: 0x30 0xA2 0x30 0xA3 An SQL insert statement is prepared: pStmt = conn.PrearedStatement(“insert into t1 values (?)”); The statements parameter is set to the string: pStmt.setString(1, k1); Internally, the Type 4 driver creates an array of bytes by using the following pseudo code: byte inB = k1.getBytes(“SJIS”); int colLen = 12; // i.e.
message=message_text For example: driver_err_error_from_server_msg=An error was returned from the server. Error: {0} Error detail: {1} where the message is driver_err_error_from_server_msg. The message_text is: An error was returned from the server. Error: {0} Error detail: {1} The pattern {n} inmessage_text, where n equals 1, 2, 3, and so forth, is a placeholder that is filled in at run time by the Type 4 driver. Any translation must include these placeholders.
Chapter 4. Type 4 Driver Properties Prev Next Chapter 4.
password Property properties Property reserveDataLocators Property roundingMode Property schema Property serverDataSource Property T4LogFile Property T4LogLevel Property translationVerification Property url Property user Property Summary of the Type 4 Driver Properties Client-Side Properties Server-Side Properties Type 4 driver properties that effect client-side operations and server-side are summarized in the following tables. For the detailed description, click the link provided in the property name.
Sets the initial connection pool size when initialPoolSize connection pooling is used with the Type 4 driver. (Ignored for connections made through the ConnectionPoolDataSource object.) Set the number of seconds that a physical maxIdleTime connection can remain unused in the pool before the connection is closed. Sets the maximum number of physical connections maxPoolSize that the pool can contain. maxStatements Sets the total number of PreparedStatement objects that the connection pool should cache.
T4LogFile T4LogLevel Sets the name of the logging file for the Type 4 driver. Sets the logging levels that control logging output for the Type 4 driver. The name is defined by the following pattern: %h/t4sqlmx%u.log OFF Table 4.6. Miscellaneous Client-Side Properties Property Name Description description Specifies the registered source name. Specifies the location of the properties file that contains properties keyword-value pairs that specify property values for configuring the Type 4 driver.
Sets the URL value for the MXCS association server. Can be set only on None the DriverManager object. Sets the URL value for the MXCS None association server. url user How to Specify JDBC Type 4 Properties Where To Set Properties Creating and Using a Properties File Setting Properties in the Command Line Precedence of Property Specifications The Type 4 JDBC driver properties configure the driver.
format: property_name=property_value For example, maxStatements=1024 To configure a DataSource connection, the properties file might contain property names and values as indicated in the following list: url=jdbc:t4sqlmx://mynode.mycompanynetwork.
4. Set the –Dt4sqlmx.property_name=property_value in the java command line For more information, see order of precedence for properties specified in various ways for use with the Driver Manager.
translationVerification Property url Property user Property The properties are listed in alphabetic order (with the exception of LOB Table Name Properties) together with their descriptions. blobTableName Property See LOB Table Name Properties. catalog Property The catalog property sets the default catalog used to access SQL objects referenced in SQL statements if the SQL objects are not fully qualified. Set this property on a DataSource object, ConnectionPoolDataSource object, or DriverManager object.
Range: -1, 0 to 2147483647 ● Zero (0) specifies infinity as the timeout value. ● A non-zero positive value overrides the value set on the MXCS server data source, if allowed by the MXCS settings. For more information, see the SQL/MX Connectivity Server Manual. ● A negative value is treated as -1. For an example, consider this scenario. Even if a connection is not being used, it takes up resources.
initialPoolSize Property The initialPoolSize property sets the initial connection pool size when connection pooling is used with the Type 4 driver. Set this property on a DataSource object or DriverManager object. This property is ignored for connections made through the ConnectionPoolDataSource object, For information about how to set the property value, see How to Specify JDBC Type 4 Properties.
KANJI Property The KANJI character-set mapping property corresponds to the SQL/MX KANJI character set, which is a double-byte character set widely used on Japanese mainframes. This property is a subset of Shift JIS -- the double character portion. The encoding for this property is bigendian. Set this property on a DataSource object, ConnectionPoolDataSource object, or DriverManager object. For information about how to set properties, see How to Specify JDBC Type 4 Properties.
JDBC Type 4 Properties. Data type: String Default: none The value can be any valid Java Canonical Name as listed in the "Canonical Name for java.io and java.lang API" column of the Sun documentation, Supported Encodings (http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html). For example, to set the language to shift-JIS, Japanese: language=SJIS LOB Table Name Properties LOB tables store data for BLOB columns and CLOB columns.
Data type: int Units: seconds Default: 60 Range: 0 to 2147483647 If set to 0 (zero), no login timeout is specified. maxIdleTime Property Note: The maxIdleTime property is available in the V11^AAC and subsequent Software Product Releases (SPRs). The maxIdleTime property determines the number of seconds that a physical connection should remain unused in the pool before the connection is closed. 0 (zero) indicates no limit.
Default: -1 (Disables connection pooling.) Range: -1, 0 through 2147483647, but greater than minPoolSize The value determines connection-pool use as follows: Any negative value is treated like -1. 0 means no maximum pool size. A value of -1 disables connection pooling. Any positive value less than minPoolSize is changed to the minPoolSize value. maxStatements Property The maxStatements property sets the total number of PreparedStatement objects that the connection pool should cache.
Range: -1, 0 through n, but less than maxPoolSize Any negative value is treated like -1. Any value greater than maxPoolSize is changed to the maxPoolSize value. The value of minPoolSize is set to -1 when maxPoolSize is -1. The value determines connection pool use as follows: ● When the number of physical connections in the free pool reaches the minPoolSize value, the Type 4 driver closes subsequent connections by physically closing them—and not adding them to the free pool.
password Property The password property sets the Guardian password value for to MXCS. The password is encrypted when it is passed to MXCS. Set this property on a DataSource object, ConnectionPoolDataSource object, or DriverManager object. For information about how to set properties, see How to Specify JDBC Type 4 Properties.
Also, the administrator should avoid setting high values for the reserveDataLocators (for example in the range of trillions or so). Setting high values prevents other Type 4 applications that use LOB table from reserving data locators. For additional information about data locator use, see Reserving Data Locators. To change this value for a JDBC application, specify this property from the command line. For example, the following command reserves 150 data locators for program class myProgramClass.
driver. schema Property The schema property sets the database schema that accesses SQL objects referenced in SQL statements if the SQL objects are not fully qualified. Set this property on a DataSource object, ConnectionPoolDataSource object, or DriverManager object. For information about how to set properties, see How to Specify JDBC Type 4 Properties.
T4LogFile Property The T4LogFile property sets the name of the logging file for the Type 4 driver. Set this property on a DataSource object, ConnectionPoolDataSource object, or DriverManager object. For information about how to set properties, see How to Specify JDBC Type 4 Properties. Data type: String Default file name is defined by the following pattern: %h/t4sqlmx%u.log where / represents the local pathname separator. %h represents the value of the user.home system property.
DriverManager object. For information about how to set properties, see How to Specify JDBC Type 4 Properties. Data type: String Default: OFF Logging Levels OFF is a special level that turns off logging; the default setting. SEVERE indicates a serious failure; usually applies to SQL exceptions generated by the Type 4 driver. WARNING indicates a potential problem, which usually applies to SQL warnings generated by the Type 4 driver.
command line: -Dt4sqlmx.T4LogLevel=FINE T4LogLevel Considerations ● If a security manager is defined by your application using an AppServer, LoggingPermission must be must be granted in the java.policy file as follows: permission java.util.logging.LoggingPermission "control",""; ● The Type 4 driver is not designed to inherit the java.util.logging.FileHandler.level settings at program startup. ● Server-side tracing and logging through MXCS is managed by NSM/web.
For more information, see Internationalization (I18N) Support . url Property The url property sets the URL value for the MXCS association server. This property is used in the DriverManager object. The format to specify the URL is: jdbc:t4sqlmx//ip_address|machine_name:port_number/[:] [property=value[;property2=value]...] where ip_address|machine_name:port_number specifies the location where the MXCS association server is running. Data type: String Default: none For example: url=jdbc:t4sqlmx://mynode.
Chapter 3. Accessing SQL Databases with SQL/MX Part Number 529651 Home Chapter 5.
Chapter 5. Working with BLOB and CLOB Data Prev Next Chapter 5.
NULL and Empty BLOB or Empty CLOB Value Transactions Involving Blob and Clob Access Access Considerations for Clob and Blob Objects This chapter describes working with BLOB and CLOB data in JDBC applications. You can use the standard interface described in the JDBC 3.0 API specification to access BLOB and CLOB data in NonStop SQL/MX tables with support provided by the Type 4 driver. BLOB and CLOB are not native data types in an SQL/MX database.
LOB Architecture: Tables for LOB Data Support Setting Properties for the LOB Table Specifying the LOB Table Reserving Data Locators Before running the JDBC application that uses BLOB and CLOB data through the JDBC API, the database administrator must create the LOB tables. For information on creating LOB tables, see Managing LOB Data with the Lob Admin Utility.
Reserving Data Locators A data locator is the reference pointer value (SQL LARGEINT data type) that is substituted for the BLOB or CLOB column in the base table definition. Each object stored into the LOB table is assigned a unique data locator value. Because the LOB table is a shared resource among all accessors that use the particular LOB table, reserving data locators reduces contention for getting the next value.
from myTable where ….for update"); if (rs.next()) myCLOB = rs.getClob(1); You can now write data to the CLOB column. See Writing ASCII or Unicode Data to a CLOB Column. Note: Limitation: Do not rename the CLOB column in the select query. Writing ASCII or MBCS Data to a CLOB Column You can write ASCII or MBCS data to a CLOB column. Note: Multibyte Character Set (MBCS) data and ASCII data are handled the same way. ASCII Data To write ASCII or MBCS data to the CLOB column, use the Clob interface.
ps.setAsciiStream(1, inputAsciiStream, length_of_data); ps.executeUpdate(); The Type 4 driver reads the data from InputStream and writes the data to the LOB table. The Type 4 driver substitutes the next-available data locator for the parameter of the CLOB column in the table. Inserting a Clob Object by Using the setClob Method Your JDBC application cannot directly instantiate a Clob object. To perform an equivalent operation: 1. Obtain a Clob object by using the getClob method of the ResultSet interface.
byte[] myClobData; myClobData = new byte[length]; is.read(myClobData, offset, length); Updating CLOB Data Updating Clob Objects with the updateClob Method Replacing Clob Objects To update CLOB data, use the methods in the Clob interface or use the updateClob method of the ResultSet interface. The Type 4 driver makes changes directly to the CLOB data. Therefore, the Type 4 driver returns false to the locatorsUpdateCopy method of the DatabaseMetaData interface.
Objects with the updateClob Method. Deleting CLOB Data To delete CLOB data, the JDBC application uses the SQL DELETE statement to delete the row in the base table. When the row containing the CLOB column is deleted by the JDBC application, the corresponding CLOB data is automatically deleted by the delete trigger associated with the base table. For information about triggers, see Using SQL/MX Triggers to Delete LOB Data. See also NULL and Empty BLOB or CLOB Value.
Note: ● The EMPTY_BLOB() function is an HP NonStop specific function and might not work on other databases. ● Do not use the EMPTY_BLOB() function when using the PreparedStatement interface. Then, obtain the handle to the empty BLOB column by selecting the BLOB column for update. The following code illustrates how to obtain the handle to an empty BLOB column: Blob myBlob = null; Statement s = conn.createStatement(); ResultSet rs = s.
PreparedStatement ps = conn.prepareStatement("insert into myTable (myBlobColumn) values (?)"); ps.setBinaryStream(1, inputBinary, length_of_data); ps.executeUpdate(); The Type 4 driver reads the data from InputStream and writes the data to the LOB table. The Type 4 driver substitutes the next-available data locator for the parameter of the BLOB column in the table. Inserting a Blob Object by Using the setBlob Method Your JDBC application cannot directly instantiate a Blob object.
Updating BLOB Data Updating Blob Objects by Using the updateBlob Method Replacing Blob Objects To update BLOB data, use the methods in the Blob interface or use the updateBlob method of the ResultSet interface. The Type 4 driver makes changes to the BLOB data directly. Therefore, the Type 4 driver returns false to the locatorsUpdateCopy method of the DatabaseMetaData interface. Applications do not need to issue a separate update statement to update the BLOB data. Update BLOB data in the following ways.
Deleting BLOB Data To delete BLOB data, the JDBC application uses the SQL DELETE statement to delete the row in the base table. When the row containing the BLOB column is deleted by the application, the corresponding BLOB data is automatically deleted by the delete trigger associated with the base table. For information about triggers, see Using SQL/MX Triggers to Delete LOB Data. See also NULL and Empty BLOB or CLOB Value.
with the current LOB object. ● When the application obtains the InputStream or Reader from the LOB object, the Type 4 driver closes the InputStream or Reader that is already associated with the LOB object. ● Similarly, when the application obtains the OutputStream or Writer from the LOB object, the Type 4 driver closes the OutputStream or Writer that is already associated with the LOB object. Prev Chapter 4. Type 4 Driver Properties Part Number 529651 Up Home Next Chapter 6.
Chapter 6. Managing the SQL/MX Tables for BLOB and CLOB Data Prev Next Chapter 6.
Character large object data BLOB Binary large object data Note: The CLOB and BLOB data type specification is special syntax that is allowed for use in base tables accessed by the Type 4 driver described in this manual.
Managing LOB Data by Using the Lob Admin Utility Running the Lob Admin Utility Help Listing from the Type 4 Lob Admin Utility Creating LOB Tables Use the Lob Admin Utility (T4LobAdmin) for the following tasks: ● Creating the LOB table (a table that holds LOB data). ● Creating the SQL/MX triggers for the LOB columns in the base tables to ensure that orphan LOB data does not occur in a LOB table.
prog_option Description -help Displays help information -exec Runs the SQL statements that are generated. Generates SQL statements to create LOB tables. These statements describe the architecture of the tables -create and, therefore, provide a description of the LOB tables. -trigger Generates SQL statements to create triggers for the designated table. The base table must exist. -drop Generate SQL statements to drop triggers for the designated table. The table must exist.
Creating LOB Tables Except as noted below, use the -create and -execute options of the Lob Admin Utility to create LOB tables. Note: Partitioned LOB tables must be manually created. You cannot use the Lob Admin Utility if your site needs partitioned LOB tables. Do not use the -execute option of the Lob Admin Utility. Follow these steps to manually create partitioned LOB tables: 1. Use the -create and -out options of the Lob Admin Utility to have SQL statements written to a file. 2.
Limitations of LOB Data (CLOB and BLOB Data Types) Limitations of the CLOB and BLOB data types, collectively referred to as LOB data, are: ● LOB columns can only be in the target column list of these SQL statements: ❍ INSERT statement ❍ Select list of a SELECT statement ❍ Column name in the SET clause of an UPDATE statement ● LOB columns cannot be referenced in the SQL/MX functions and expressions.
Chapter 7. Type 4 Driver Compliance Prev Next Chapter 7.
CallableStatement.getArray(int parameterIndex) CallableStatement.getArray(String parameterName) CallableStatement.getBlob(int parameterIndex) CallableStatement.getBlob(String parameterName) CallableStatement.getClob(int parameterIndex) CallableStatement.getClob(String parameterName) CallableStatement.getObject(int parameterIndex, Map map) CallableStatement.getObject(String parameterName, Map map) The particular CallableStatement method is not supported. CallableStatement.
When used for access to SQL/MP user tables, the following additional methods in the java.sql package throw an SQLException with the message "Unsupported feature method-name": Method Comments PreparedStatement.setBlob(int parameterIndex, Blob x) The particular PreparedStatement methods are not supported for access of SQL/MP user PreparedStatement.setClob(int parameterIndex, Clob x) tables only. ResultSet.getBlob(int columnIndex) ResultSet.getBlob(String columnName) ResultSet.
java.sql.Array java.sql.Ref java.sql.Savepoint java.sql.SQLData The underlying data types are not supported by SQL/MX. java.sql.SQLInput java.sql.SQLOutput java.sql.Struct The following interfaces in the javax.sql package are not implemented in the Type 4 driver: Method javax.sql.XAConnection Comments Distributed Transactions, as described in the JDBC 3.0 API specification, are not yet implemented. javax.sql.XADataSource javax.sql.RowSet javax.sql.
The column is added to the column data, but its value is set to NULL because SQL/MX does not support the column type for types as follows: TYPE_CAT, java.sql.DatabaseMetaData.getTables(String catalog, String schemaPattern, String[] types) TYPE_SCHEMA, TYPE_NAME, SELF_REFERENCING_COL_NAME, and REF_GENERATION. BASE_TYPE is added to the column data, but its value is java.sql.DatabaseMetaData.
Conformance of DatabaseMetaData Methods' Handling of Null Parameters This topic describes how the Type 4 driver determines the value of null parameters passed as a parameter value on DatabaseMetaData methods. Since other vendors might implement the JDBC specification differently, this information explains the Type 4 driver results on the affected queries. This implementation applies to methods that take parameters that can represent a pattern.
Types.DATE Types.DECIMAL Types.DISTINCT Types.DOUBLE Types.FLOAT Types.INTEGER Types.JAVA_OBJECT Types.LONGVARBINARY Yes Yes No Yes Yes Yes No Data type is mapped by SQL/MX . Data type varies from that used for table creation. Yes DATE DECIMAL(p,s) N.A. DOUBLE PRECISION FLOAT(p) INTEGER N.A. VARCHAR(n)¹ VARCHAR[(n)] Maximum length is 4018 No N.A. Types.NULL Yes NUMERIC(p,s) Types.NUMERIC Yes FLOAT(p) Types.REAL No N.A. Types.REF Yes SMALLINT Types.SMALLINT No N.A. Types.STRUCT Yes TIME Types.
DATETIME HOUR TO MINUTE DATETIME MINUTE DATETIME MINUTE TO SECOND 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, might 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.
● Embedded-only SQL/MP statements ● Transaction Control statements ● Stored procedures Refer to the NonStop SQL/MP documentation set for a complete list of supported features. Other Unsupported Features These features are not required for JDBC 3.0 compliance, and they are not supported by the NonStop JDBC Type 4 Driver. ● Multiple result sets returned by batch statements. ● Database savepoint support. (Not provided in SQL/MX ) ● Retrieval of auto generated keys.
Chapter 8. Tracing and Logging Facilities Prev Next Chapter 8.
4 Driver Logging).
is the port to which the server is connected. For example: TCP:\banshee-tcp.$Z0133/46003:NonStopODBC dialogue-id If applicable, the dialogue-id used for the MXCS connection. class If applicable, the name of the class that issued the logging request. method If applicable, the name of the method that issued the logging request. parameters An optional set of parameters associated with the method. text Optional textual information for the message. Note: The tilde (~) character separates message parts.
Chapter 9. Migration Prev Next Chapter 9. Migration JDBC Drivers Third-Party Databases Operating Systems JDBC Drivers Driver You Are Migrating From Code Changes JDBC Type 3 Driver No JDBC Driver for SQL/MX No (JDBC/MX), a Type 2 driver Configuration Changes Considerations url, catalog, schema, logging facilities url, catalog, schema, logging facilities; potential property value changes (verify using Summary of the Type 4 Driver Properties) N.A.
Third-Party Databases Applications must be compatible with features and data types supported by SQL/MX. Any application using specific features and data types customized for third-party databases must be modified to work with the Type 4 driver. For features and data types supported by SQL/MX, see the SQL/MX Reference Manual.
Chapter 10. Messages Prev Next Chapter 10. Messages About the Message Format Type 4 Driver Error Messages About the Message Format Messages are listed in numerical SQLCODE order. Descriptions include the following: SQLCODE SQLSTATE message-text Cause [ What occurred to trigger the message.] Effect [ What is the result when this occurs. ] Recovery [ How to diagnose and fix the problem. ] Type 4 Driver Error Messages 29001 HYC00 Unsupported feature - {0} Cause.
Cause. An attempt was made to set the transaction isolation level to an invalid value. Effect. SQLMXConnection.setTransactionIsolation does not set the transaction isolation value. Recovery. Valid isolation values are: SQL_TXN_READ_COMMITTED, SQL_TXN_READ_UNCOMMITTED, SQL_TXN_REPEATABLE_READ, and SQL_TXN_SERIALIZABLE. If no isolation value is specified, the default is SQL_TXN_READ_COMMITTED. 29005 HY024 Invalid ResultSet type Cause. An attempt was made to set an invalid ResultSet Type value. Effect.
Recovery. To insert a row, move the cursor to the insert row. To delete, cancel, or update a row, move the cursor from the insert row. 29010 07009 Invalid column name Cause. A column search does not contain columnName string. Effect. The column comparison or searches do not succeed. Recovery. Supply a valid columnName string to the findColumn(), validateGetInvocation(), and validateUpdInvocation() methods. 29011 07009 Invalid column index or descriptor index Cause.
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. 29019 07002 Parameter {0, number, integer} for {1, number, integer} set of parameters is not set Cause.
disabled. 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. Effect. The current AutoCommit mode is not modified. Recovery. Complete the transaction, then attempt to set the AutoCommit mode. 29029 HY011 SetTransactionIsolation not possible, since a transaction is active Cause. An attempt was made to set transaction isolation level while a transaction was active. Effect.
Cause. The character encoding is not supported. Effect. An exception is thrown when the requested character encoding is not supported. Recovery. ASCII (ISO88591), KANJI, KSC5601, and UCS2 are the only supported character encodings. SQL/MP tables do not support UCS2 character encoding. 29037 HY106 ResultSet type is TYPE_FORWARD_ONLY Cause. An attempt was made to point a ResultSet cursor to a previous row when the object type is set as TYPE_FORWARD_ONLY. Effect.
Recovery. Change the table to include a primary-key column. 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. 29043 HY000 Max rows value is not valid Cause.
29048 HY009 Invalid use of null Cause. A parameter that has an expected table name is set to null. Effect. The DatabaseMetadata method does not report any results. Recovery. For the DatabaseMetaData method, supply a valid table name that is not null. 29049 25000 Invalid transaction state Cause. The begintransaction() method was called when a transaction was in progress. Effect. A new transaction is not started. Recovery.
Recovery. Use the validateSetInvocation() or validateExecuteInvocation method prior to the statement close. 29057 HY000 Auto generated keys not supported Cause. An attempt was made to use the Auto-generated keys feature. Effect. The attempt does not succeed. Recovery. The Auto-generated keys feature is not supported. 29058 HY000 Connection is not associated with a PooledConnection object Cause. The getPooledConnection() method was invoked before the PooledConnection object was established. Effect.
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. 29067 07009 Invalid input value in the method {0} Cause. One or more input values in the given method is invalid. Effect. The given input method failed. Recovery.
Recovery. Refer to url Property for the valid address format. 29103 HY000 Address is null Cause. The address was empty. Effect. Operation fails. Recovery. Refer to url Property for the valid address format. 29104 HY000 Expected suffix: suffix Cause. The address suffix was incorrect or missing. Effect. Operation fails. Recovery. Refer to url Property for the valid address format. 29105 HY000 Unknown prefix for address Cause. The address prefix was incorrect or missing. Effect. Operation fails. Recovery.
Recovery. N.A. 29110 HY000 Address is missing an IP address or machine name. Cause. An IP address or machine name is required, but missing. Effect. The operation fails. Recovery. Include a valid IP address or machine name. Refer to url Property for the valid address format. 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.
Recovery. Use the getCause method on the Exception to determine the appropriate recovery action. 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. 29117 HY000 Error while closing session. Cause: cause Cause. An error was encountered while closing a session. Effect. The operation fails. Recovery.
Cause. Unable to perform the operation. Effect. Operation fails. Recovery. Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. 29123 HY000 An execute call 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. 29124 HY000 An execute direct message error occurred.
Effect. Operation fails. Recovery. Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. 29129 HY000 A fetch rowset 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. 29130 HY000 A get sql catalogs message error occurred. Cause: cause Cause.
Recovery. Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. 29135 HY000 A terminate dialogue 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. 29136 HY000 An association server connect reply occurred.
Recovery. Evaluate the returned value from the getCause method on the Exception to determine the appropriate recovery action. 29141 HY000 An execute direct 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. 29142 HY000 An execute N reply error occurred. Cause. Unable to perform this operation. Effect. Operation fails. Recovery.
29147 HY000 An initialize dialogue 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. 29148 HY000 A prepare 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.
Cause. Incorrect user name and/or password. Effect. Operation fails. Recovery. Retry with correct user name and/or password. 29154 HY000 Timeout expired Cause. Unable to perform this operation. Effect. Operation fails. Recovery. Retry and/or change the timeout value for the operation. 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.
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. 29160 HY000 The message header was not long enough. Cause. The message returned by the server was too short to be a valid message. Effect. Operation fails. Recovery. None. Report the entire message to your service provider.
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. 29166 HY000 This method is not implemented. Cause. Internal error. Effect. Operation fails. Recovery. None. Report the entire message to your service provider. 29167 HY000 Internal error. An internal index failed consistency check. Cause. Internal error. Effect.
FALSE. 29173 HY000 Translation of SQL statement {0} failed. Cause. Translation errors occurred when translating the SQL statement into the target character set reported in the {0} replacement variable. Effect. The method fails. Recovery. Edit the SQL statement to use characters within the appropriate character set. You can also turn off translation validation by setting the translationVerification property to FALSE. 29174 HY000 Autocommit is on and updateRow was called on the ResultSet object. Cause.
Cause. Transaction state is incorrect. Effect. Operation fails. Recovery. Retry. 01118 S1008 Operation cancelled. Cause. The operation was cancelled. Effect. Operation fails. Recovery. Retry operation. 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.
Appendix A. Sample Programs Accessing CLOB and BLOB Data Prev Next Appendix A. Sample Programs Accessing CLOB and BLOB Data Sample Program Accessing CLOB Data Sample Program Accessing BLOB Data This appendix shows two working programs. Sample Program Accessing CLOB Data This sample program shows operations that can be performed through the Clob interface or through the PreparedStatement interface.
// - need an Inputstream object that already has data // - need a PreparedStatement object that contains the // 'insert...' DML of the base table // - ps.setAsciiStream() for the lob data // - ps.executeupdate(); for the DML // // To run this example, issue the following: // # java TestCLOB 1 TestCLOB.java 1000 // import java.sql.*; import java.io.*; public class TestCLOB { public static void main (String[] args) throws java.io.FileNotFoundException, java.io.
System.out.println("Key: " + recKey +"; Using " + length + " of file " + args[1]); try { Class.forName("com.tandem.t4jdbc.SQLMXDriver"); start = System.currentTimeMillis(); //url should be of the form: // jdbc:t4sqlmx://ip_address|machine_name:port_number/:” String url = “jdbc:t4sqlmx://mymachine:6000/:”; conn1 = DriverManager.getConnection(url); System.out.println("Cleaning up test tables..."); Statement stmt0 = conn1.createStatement(); stmt0.execute("delete from clobdatatbl"); stmt0.
// Clob interface example - This technique is suitable when // the LOB data is already in the app, such as having been // transferred in a msgbuf. try { // insert a second base table row with an empty LOB column System.out.println("CLOB interface EMPTY LOB insert..."); String stmtSource2 = "insert into clobbase values (?,EMPTY_CLOB())"; PreparedStatement stmt2 = conn1.prepareStatement(stmtSource2); stmt2.setInt(1,recKey+1); stmt2.executeUpdate(); Clob clob = null; // System.out.
Sample Program Accessing BLOB Data This sample program shows the use of both the Blob interface and the PreparedStatement interface to take a byte variable and put the variable's value into a base table that has a BLOB column. // LOB operations may be performed through the Blob, or // PreparedStatement interface. This program shows examples of // using both interfaces taking a byte[] variable and putting // it into the cat.sch.blobtiff table.
throws java.io.FileNotFoundException, java.io.IOException { int int long long Connection numBytes; recKey; start; end; conn1 = null; // Set t4slqmx.blobTableName System Property. This property // can also be added to the command line through // "-Dt4slqmx.blobTableName=...", or a // java.util.Properties object can be used and passed to // getConnection. System.setProperty( "t4slqmx.blobTableName","cat.sch.blobdatatbl" ); if (args.length < 2) { System.out.
Statement stmt0 = conn1.createStatement(); stmt0.execute("delete from blobdatatbl"); stmt0.execute("delete from blobtiff"); conn1.setAutoCommit(false); } catch (Exception e1) { e1.printStackTrace(); } // PreparedStatement interface example - This technique is // suitable if the LOB data is already on the // NonStop system disk. try { System.out.println("PreparedStatement interface LOB insert..."); String stmtSource1 = "insert into blobtiff values (?,?)"; PreparedStatement stmt1 = conn1.
update (EMPTY in this case)..."); PreparedStatement stmt3 = conn1.prepareStatement("select tiff from blobtiff where col1 = ? for update"); stmt3.setInt(1,recKey+1); ResultSet rs = stmt3.executeQuery(); if (rs.next()) tiff = rs.getBlob(1); // has to be there else the base table insert failed System.out.println("Writing data to previously empty BLOB..."); OutputStream os = tiff.setBinaryStream(1); byte[] bData = k.getBytes(); os.write(bData); os.close(); conn1.commit(); } catch (SQLException e) { e.
Glossary Prev Next Glossary A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z A 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.
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(). B base table A table that has physical existence: that is, a table stored in a file. BLOB Short for Binary Large OBject, a collection of binary data stored as a single entity in a database management system.
your class path. The t4sqlmx.jar file is in the location where you installed this product. You can set the class path explicitly or with the CLASSPATH environment variable. client A software process, hardware device, or combination of the two that requests services from a server. Often, the client is a process residing on a programmable workstation and is the part of a program that provides the user interface. The workstation client might also perform other portions of the program logic.
Data Manipulation Language (DML) The set of data-manipulation statements within the SQL language. These statements include INSERT, DELETE, and UPDATE, which cause database modifications that Remote Duplicate Database Facility (RDF) can replicate. data source A logical name that defines the information required to access data. ● On the client side, it defines the driver name, network address, and specific attributes such as catalog and schema names.
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 get() method A method used to read a data item. For example, the Connection.getAutoCommit() method returns the transaction mode of the JDBC driver's connection to an SQL/MX database. Compare to set() method. Guardian An environment available for interactive and programmatic use with the NonStop Kernel.
The formal name of the NonStop Server for Java product whose Java virtual machine conforms to the Java 2 Standard Edition, SDK 1.4.1. See also NonStop Server for Java 4. HP NonStop SQL/MP (SQL/MP) HP NonStop Structured Query Language/MP, the HP relational database management system for NonStop servers. HP NonStop SQL/MX (SQL/MX) HP NonStop Structured Query Language/MX, the HP next-generation relational database management system for business-critical applications on NonStop servers.
interactive Question-and-answer exchange between a user and a computer system. interface In general, the point of communication or interconnection between one person, program, or device and another, or a set of rules for that interaction. See also API. International Electrotechnical Commission (IEC) A standardization body at the same level as ISO.
See International Organization for Standardization (ISO). J jar The Java Archive tool, which combines multiple files into a single Java Archive (JAR) file. Also, the command to run the Java Archive Tool. JAR file A Java Archive file, produced by the Java Archive Tool, jar. java The Java interpreter, which executes Java bytecode. Also, the command to run the Java interpreter. The Java command invokes the Java Run-Time.
Java Run-time The Java VM and the Core API. This is the standard Java environment that the java command invokes. Java virtual machine The process that loads, links, verifies, and interprets Java bytecode. The NonStop Server for Java 4 implements the Java HotSpot virtual machine. JDBC See Java Database Connectivity (JDBC). JDBC API The programmatic API in Java to access relational databases.
L LAN See local area network (LAN). LOB Short for Large OBject. Represents either CLOB or BLOB data. LOB table The table that stores the actual data associated with CLOB columns and BLOB columns in base tables. Contrast with base table. 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.
One of the following: ● An addressable device attached to a computer network. ● A hypertext document. NonStop Server for Java 4 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).
The ability to transfer programs from one platform to another without reprogramming. A characteristic of open systems. Portability implies use of standard programming languages, such as C. Portable Operating System Interface X (POSIX) A family of interrelated interface standards defined by ANSI and Institute for Electrical and Electronic Engineers (IEEE). Each POSIX interface is separately defined in a numbered ANSI/IEEE standard or draft standard.
expandability. server One of the following: ● An implementation of a system used as a stand-alone system or as a node in an Expand network. ● The hardware component of a computer system designed to provide services in response to requests received from clients across a network. For example, NonStop system servers provide transaction processing, database access, and other services. A process or program that provides services to a client.
A stored procedure whose body is a static Java method. stub One of the following: ● A dummy procedure used when linking a program with a run-time library. The 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.
U Unicode A character-coding scheme designed to be an extension of ASCII. By using 16 bits for each character (rather than ASCII's 7), Unicode can represent almost every character of every language and many symbols (such as "&") in an internationally standard way, eliminating the complexity of incompatible extended character sets and code pages. Unicode's first 128 codes correspond to those of standard ASCII.
X There are no entries for this section. Y There are no entries for this section. Z There are no entries for this section. Prev Appendix A.
Index Prev Index A Abbreviations in this manual, Abbreviations Access considerations Blob and Clob objects, Access Considerations for Clob and Blob Objects API, Communication Overview (see also Java API) layer, Communication Overview Appendix A, Sample Programs Accessing CLOB and BLOB Data Architecture LOB support, Architecture for LOB Support Type 4 driver, Type 4 Driver Architecture ASCII data PreparedStatement interface, ASCII Data reading, Reading ASCII Data from a CLOB Column Audience, Is This Documen
sample applications, Samples Binary data reading, Reading Binary Data from a BLOB Column writing, Writing Binary Data to a BLOB Column BLOB columns associated LOB table, Specifying the LOB Table creating, Using MXCI To Create Base Tables that Have LOB Columns inserting, Inserting a BLOB Column by Using the Blob Interface reading from, Reading Binary Data from a BLOB Column transactions, Transactions Involving Blob and Clob Access writing binary data to, Writing Binary Data to a BLOB Column BLOB data accessi
Character padding, How the Padding Character Causes the Discrepancy in Length Character-set properties use, Controlling String Literal Conversion by Using the Character-Set Properties using, Using the Character-Set Properties Character sets ISO8859/2 through ISO8859/9, Unsupported SQL/MP Features SQL/MX, Controlling String Literal Conversion by Using the Character-Set Properties CLASSPATH environment variable, Setting CLASSPATH Client components, Accessing a Database with the Type 4 Driver connection securi
inserting CLOB columns, Inserting CLOB Columns by Using the Clob Interface writing ASCII or MBCS data, ASCII Data Clob object inserting, Inserting a Clob Object by Using the setClob Method Replacing, Replacing Clob Objects clobTableName property description, LOB Table Name Properties setting, Specifying the LOB Table Columns character, fixed-length, Trimming Padding for Fixed-Length Character Columns Communication overview, Communication Overview Compliance description, Type 4 Driver Compliance overview, Co
components, Accessing a Database with the Type 4 Driver connectionTimeout property, connectionTimeout Property loginTimeout property, loginTimeout Property maxIdleTime property, maxIdleTime Property connectionTimeout property, connectionTimeout Property create option, program_options CREATE TABLE statement base tables, Using MXCI To Create Base Tables that Have LOB Columns Creating base tables, Creating Base Tables that Have LOB Columns data source, Programmatically Creating an Instance of the DataSource Cl
creating, JDBC Data Source (client-side) dataSourceName property, dataSourceName Property log writer, Standard JDBC Tracing and Logging Facility MXCS (server-side), MXCS Data Source (server-side) object properties, DataSource Object Properties overview of, Data Sources programmatically creating an instance, Programmatically Creating an Instance of the DataSource Class registering, Programmatically Registering the DataSource Object retrieving, Retrieving a DataSource Instance by using JNDI and to the Data So
DriverManager class connection-pool participants, Connection Pooling getting a connection, Connection by Using the DriverManager Class guidelines , Guidelines for Connections Using the Driver Manager log writer, Standard JDBC Tracing and Logging Facility setting properties, Where To Set Properties Drivers migration, JDBC Drivers drop option, program_options E EMPTY_BLOB() function description, NULL and Empty BLOB or Empty CLOB Value limitation, Inserting a BLOB Column by Using the Blob Interface storing BL
G getConnection() method DataSource object, Retrieving a DataSource Instance by using JNDI and to the Data Source DriverManager class, Establishing the Connection Glossary, Glossary Guardian ID, Security user name, Security user name, specifying, user Property H help option, program_options HP extensions, HP Extensions I I18N (see Internationalization support) IDL layer, Communication Overview initialPoolSize property description, initialPoolSize Property InputStream current object, Access Considerations
ISO8859/2 through ISO8859/9 character sets, Unsupported SQL/MP Features ISO88591_1 Java encoding set, Controlling String Literal Conversion by Using the Character-Set Properties ISO88591 property description, ISO88591 Property using, Controlling String Literal Conversion by Using the Character-Set Properties J Java encoding sets, Controlling String Literal Conversion by Using the Character-Set Properties JDK version, Installation Requirements java command-line, Setting Properties in the Command Line Java A
JNDI, Connection by Using the DataSource Interface retrieving a data source , Retrieving a DataSource Instance by using JNDI and to the Data Source K KANJI columns inserts, How the Padding Character Causes the Discrepancy in Length KANJI property description, KANJI Property using, Controlling String Literal Conversion by Using the Character-Set Properties KSC5601 property description, KSC5601 Property using, Controlling String Literal Conversion by Using the Character-Set Properties L language property, l
LOB tables creating, Creating LOB Tables illustrated, Architecture for LOB Support limitation on partitioning, Creating LOB Tables partitioning, Creating LOB Tables setting properties for, Setting Properties for the LOB Table specifying, Specifying the LOB Table Localizing messages, Localizing Error Messages and Status Messages locatorsUpdateCopy method, Updating BLOB Data Logging facilities, Tracing and Logging Facilities levels, Logging Levels message format, Message Format output examples, Examples of Lo
reading, Reading ASCII Data from a CLOB Column Message format, logging output, Message Format Messages creating localized file, Procedure To Create a Localized-Message File internationalization of, Internationalization of Messages language property, language Property localized file, File-Name Format for the Localized-Messages File localizing, Localizing Error Messages and Status Messages Type 4 driver, Messages Migration, Migration minPoolSize property, minPoolSize Property MXCS association server, Communic
P password authentication, Security property, password Property Platforms, Client Platforms Supported Pooling, Client-Side Properties (see also Connection pooling) enabling, maxPoolSize Property management properties, Client-Side Properties Precedence property specifications, Precedence of Property Specifications PreparedStatement interface inserting a Blob, Inserting a BLOB Column by Using the PreparedStatement Interface inserting CLOB data, Inserting CLOB Data by Using the PreparedStatement Interface stat
Registering driver , Loading and Registering the Driver Replacing Clob objects, Replacing Clob Objects Requirements for client platform, Client Platforms Supported for NonStop server, Type 4 Driver Architecture hardware, Installation Requirements JDK version, Installation Requirements NonStop system, Installation Requirements reserveDataLocators Property description, reserveDataLocators Property Reserving data locators, Reserving Data Locators Restoring LOB columns, Backing Up and Restoring LOB Columns Rest
components, Accessing a Database with the Type 4 Driver id, Message Format name, traced, Message Format properties, Server-Side Properties serverDataSource property, serverDataSource Property setClob Method inserting, Inserting a Clob Object by Using the setClob Method setLogWriter method, Standard JDBC Tracing and Logging Facility SJIS Java encoding set, Controlling String Literal Conversion by Using the Character-Set Properties Socket connection, networkTimeout Property SPJs (see Stored procedures in Java
generating, program_options Statement pooling description, Statement Pooling guidelines, Guidelines for Statement Pooling maxStatements property, maxStatements Property troubleshooting, Troubleshooting Statement Pooling Stored procedures description, Stored Procedures SQL/MP, Unsupported SQL/MP Features Storing BLOB data, Storing BLOB Data CLOB data, Storing CLOB Data String literals controlling conversion, Controlling String Literal Conversion by Using the Character-Set Properties use, When String Literals
maxIdleTime property, maxIdleTime Property networkTimeout property, networkTimeout Property Tracing facilities, Tracing and Logging Facilities properties for, Client-Side Properties standard facilities, Standard JDBC Tracing and Logging Facility Transaction control statements SQL/MP, Unsupported SQL/MP Features SQL/MX, Unsupported NonStop SQL Features Transactions Blob and Clob access, Transactions Involving Blob and Clob Access translationVerification property description, translationVerification Property
JDBC 3.0 API deviations, Deviations JDBC 3.0 API unsupported features, Unsupported Features layered program, Communication Overview messages, Messages other unsupported features, Other Unsupported Features product files, Product Files restrictions, Restrictions using character-set properties, Controlling String Literal Conversion by Using the Character-Set Properties version 1.
U UCS2 character set, How the Padding Character Causes the Discrepancy in Length Unsupported features other, Other Unsupported Features SQL/MP, Unsupported SQL/MP Features SQL/MX, Unsupported NonStop SQL Features Update where current of, "Update ...
current object, Access Considerations for Clob and Blob Objects Writing ASCII data, Writing ASCII or MBCS Data to a CLOB Column Binary data, Writing Binary Data to a BLOB Column MBCS data, Writing ASCII or MBCS Data to a CLOB Column Prev Glossary Part Number 529651 Up Home Legal Notices
