StarSQL for Java Version 2.40 June 2008 Copyright 2000-2008 StarQuest Ventures, Inc. All Rights Reserved. StarQuest Ventures, Inc. PO Box 1076 Point Reyes Station, CA 94956 Telephone: 415-669-9619 FAX: 415-669-9629 Sales & Support: contact@starquest.com URL: http://www.starquest.com StarSQL for Java is a type 4 (Direct-to-Database Pure Java) JDBC driver for DRDA access to IBM DB2 databases. It uses the TCP/IP protocol to communicate either directly to DB2 host systems that implement DRDA over TCP/IP (e.g. DB2 for OS/390 v5.1 & later, OS/400 v4r2 & later, DB2 UDB for Windows, OS/2 & UNIX v5.1 & later) or to any DB2 system through a StarPipes gateway. This version of StarSQL for Java supports the JDBC 3.0 API. See the StarSQL for Java Users Guide "ssqljava.pdf" for setup and usage information. ============== HOST DATABASES ============== StarSQL for Java can connect to any of the following host databases: DB2 for OS/390 v5.1 and later DB2/400 (DB2 UDB for iSeries) - OS/400 v3r2 and later DB2 Universal Database (UDB) v6.1 and later for UNIX and Windows. For native DRDA over TCP/IP support: DB2 for OS/390 v5.1 and later DB2/400 (OS/400 v4r2 and later) DB2 Universal Database v6.1 and later for UNIX and Windows. For LOB (large object) support: DB2 for OS/390 v6.1 and later DB2 UDB for iSeries - OS/400 v5r2 and later DB2 Universal Database v8.1 and later for UNIX and Windows. Be sure to install all LOB-related fixes to your host system. StarSQL for Java supports encrypted passwords. The following host databases support password encryption or successfully negotiate the use of password encryption: DB2 for OS/390 v6.1 and later DB2 UDB for iSeries - OS/400 v4r5 and later DB2 Universal Database v8.1 & later for UNIX and Windows (successfully negotiates the use of clear text passwords) ================== Java Requirements: ================== The use of a Java Virtual Machine (JVM) equivalent to the Sun JDK 1.3.1 or later is recommended. If you plan to use DataSource, Transaction, or SSL support, you will need either JDK 1.4.x Standard Edition or Enterprise Edition JDK 1.3.x Enterprise Edition or JDK 1.3.x Standard Edition plus - the JDBC 2.0 Optional Package (jdbc2_0-stdext.jar) for DataSource support - the JTA interfaces (jta.jar) for Transaction support - the Java Secure Socket Extension (jsee.jar) for SSL support These are installed by StarSQL for Java in the "ext" subfolder and are available for download from: http://java.sun.com/products/jdbc/download.html http://java.sun.com/products/jta http://java.sun.com/products/jsse =================== Other Requirements: =================== To use workstation licensing on UNIX, you must install the StarLicense package for your UNIX operating system. ================================= Upgrading from previous releases: ================================= Important Note for users upgrading from previous versions of StarSQL for Java: The licensing configuration file has been renamed from STARLICENSE.CFG to StarLicense.properties. ================================== Location of StarLicense.properties ================================== The StarSQL for Java driver will first try to find the StarLicense.properties file in the CLASSPATH (java.class.path). If that fails, then it will look in java.home/lib (the lib directory of the JRE directory). If it fails to find the file, it will use default values for licensing (a starlicense server named "starlic", listening on port 4999). =========================================================== Connecting to older databases or through StarPipes Gateway: =========================================================== Although StarPipes is no longer supported for licensing StarQuest products, it may still be used as gateways to SNA-only host systems. The use of password encryption when connecting to a host through a StarPipes gateway is supported only when using StarPipes for Windows v2.30 and later. ================= Windows 95/98/ME: ================= Not Enough Environment Space Error Message (Windows 95/98/ME): The batch files used by StarSQL for Java make extensive use of environment variables. If you see an error message about insufficient environment space On Windows 95/98/ME, increase the environment space by adding a variable to SYSTEM.INI in the [NonWindowsApp] section: [NonWindowsApp] CommandEnvSize=1024 Alternatively, you can put the following line in your config.sys file: shell=c:\command.com c:\ /e:1024 /p ----------- The "Edit StarLicense.properties" item in the Start Menu may display a "Browsing for notepad.exe" dialog when it is selected from a Windows 95/98/ME desktop. Solutions: Choose the Properties of the shortcut (by right-clicking on the item in the Start Menu) and change it from C:\Windows\System\notepad.exe to C:\Windows\notepad.exe or notepad.exe) Edit the StarLicense.properties file by opening it with Notepad or another editor. One way to do this is enter the following at a DOS prompt or after selecting "Run" from the Start Menu: notepad %STARSQL_JAVA%\starlicense.properties ============================================= Using StarSQL for Java with WebSphere on z/OS ============================================= When StarSQL for Java is installed on z/OS, all text files are converted to EBCDIC. This enables the use of StarSQL for Java with Java applications running from the UNIX shell of z/OS Unix System Services (USS). However, to use StarSQL for Java with WebSphere v5.x for z/OS, StarLicense.properties must be in ASCII rather than EBCDIC. To convert your existing StarLicense.properties file to ASCII with iconv: $ mv StarLicense.properties StarLicense.properties.ebcdic $ iconv -f -t "IBM-1047" "ISO8859-1" StarLicense.properties.ebcdic > StarLicense.properties =========== LIMITATIONS =========== * Some DatabaseMetadata API methods may not work correctly when the table name is a synonym. ================= APPLICATION NOTES ================= OpenOffice/StarOffice and OS/400: When creating a new query in Design View using the Data Source Administrator in OpenOffice Spreadsheet, you may encounter the following error when adding a table to the query: [StarSQL JDBC Driver][DB2]Function check. To resolve this problem, install the OS/400 PTF for APAR SE15307 (PTF SI14552 for v5r1 & SI13908 for v5r2). No PTF is needed for v5r3. Alternatively, create a new query in SQL View. ============== NEW PROPERTIES ============== StarSQL for Java 2.33 adds a new Boolean property commitProcedureCall (values true or false) which controls whether the driver sends a commit on the execute chain when invoking a stored procedure in autoCommitMode. This connection property can be set either in a URL or a datasource. The default is true. When set to false, this property provides compatibility for Java applications that were developed with older versions of StarSQL for Java (prior to 2004) and expect the older behavior of not sending a commit when invoking a stored procedure in autoCommitMode. ============== CHANGE HISTORY ============== 2.40.0612 10412 SQLCIND sub-parser not handling split comm buffer correctly 2.39.0222 10337 XA Transaction Recovery not working with WebSphere 2.38.0129 2PC support 2.37.1129 Enhancements for WebSphere 10285 ArrayOutOfBoundsException on boundary condition (hostbound) 2.36.0918 10197 - prepareCall fails when some cursor options are specified 10198 - Re-execution of prepared SELECT causes incorrect results 2.35.0614 10105 Expand support for large number of sections in StarSQL Packages 2.34.0605 10076 - Cannot handle (non-LOB) output parameters totalling more than 32K 10077 - End of chain detection incomplete in comm interface 2.33.0417 10047 Connection Property to control auto-commit of SP 10049 Incorrectly sorted MetaData from getProcedureColumns 2.32.0404 10048 NullPointerException processing stored procedure resultsets 2.31.0310 9975 Change default qualifier implementation to use CURRENT SCHEMA (DB2 for z/OS v8) 9978 Look for StarLicense.properties in java.home/lib 9979 Do not open logfiles if logging is off 9997 Dead connections remain in connection pool (Websphere) 8909 Allow setString of integer/double/decimal values to DB2/zOS and UDB 9999 JDBC Calls can hang because of security exceptions 2.30.0117 9969 Memory leak in resource pooling 9970 Isolation Level not applied correctly 2.27.1302 9945 Support ability to fetch LOB data as a stored procedure OUTPUT parameter 9934 Support native API to pass client information to host 9935 Problem reusing CallableStatement objects with stored procedure calls 2.26.0425 9520 getTimestamp() not supported for conversion of DATE fields 2.25.0314 9470 add RDBNAME parameter to ACCSEC 2.24.0914 9337 Fixes for getTables and getColumns (DB2 for OS/390 v5) 2.23.0328 8904 Package binding issues 8905 TimeStamp conversion issues 8906 Support for european date formats (dd.mm.yyyy and/or dd/mm/yy) in sql and set/getString for date fields. 8907 Support for decimal comma instead of period in jdbc interface methods handling decimal numbers. (Ability to set/getString decimal values in string representation using decimal comma) 2.22.0210 8883 Bug in stored procedure INOUT parameter handling 8888 NPE when connecting with application running in WSAD 5.1 2.21.0106 8829 Duplicate records returned when column in a row spans query block 8830 Improve handling of UTF-8 8852 Improve LOB Support for UDB and AS/400 databases 8853 LobTestApp: Connect button state