StarSQL for Java v2.58 Release Notes
May 2011
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.
The following topics are addressed in these Release Notes. Refer to the StarSQL for Java Quick Start Guide for detailed information about installing StarSQL for Java for the first time, and refer to the StarSQL for Java User's Guide for detailed information about using the StarSQL JDBC driver..
- What's New in this Release
- Upgrade Considerations
- System Requirements
- Installing and Using the StarSQL for Java Driver
- Known Issues
- Release History
- Contacting StarQuest
What's New in this Release
StarSQL for Java v2.5 introduces the following new features and improvements:
- Support for Apache Derby (JavaDB) databases
- Improved support for CLOB and mixed byte (especially UNICODE) data
- Improved buffer management and parsing
- Improved exception handling
- Incorporation of all previous fixes
- Support for DB2 for VM databases
Upgrade Considerations
This section describes issues of interest for users who are upgrading from a prior version of StarSQL for Java.
StarSQL/iSeries for Java Product Name Changed
If you are upgrading from StarSQL/iSeries for Java, note that the product name has changed. All versions of StarSQL for Java now use the same installer. In addition, you will need to edit StarLicense.properties and set DEFAULT_PRODUCTID=CA. Refer to the Licensing chapter in the StarSQL for Java User's Guide and to the commented sample lines in the supplied StarLicense.properties for details.
System Requirements
You can install and run the StarSQL for Java driver on any computer that has a Java Virtual Machine (JVM) equivalent to the Sun JDK 1.4.1 or later.
To use workstation licensing on UNIX, you must install the StarLicense package for your UNIX operating system.
StarSQL for Java can connect to any of the following host databases:
- DB2 for OS/390 and z/OS v5.1 and later
- DB2 for i (formerly known as DB2/400, DB2 UDB for iSeries, and DB2 for i5/OS) running OS/400 V3R2 and later (V4R2 and later required for native DRDA over TCP/IP support)
- DB2 Universal Database (UDB) for Linux, UNIX, and Windows v6.1
and later - Apache Derby (JavaDB) 10.3 or later
- DB2 Server for VSE & VM 7.1 and later
The following host provide support for LOBs (large objects):
- DB2 for OS/390 and z/OS v6.1 and later
- DB2 for i, running OS/400 V5R2 and later
- DB2 UDB for Linux, UNIX, and Windows v8.1 and later
- Apache Derby (JavaDB) 10.3 or later
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 and z/OS v6.1 and later
- DB2 for i, running OS/400 V4R5 and later
To support password encryption on a DB2 UDB for iSeries V5R1 or V5R2 host, you must install the Cryptographic Access Provider 56-bit for iSeries (#5722-AC2) or Cryptographic Access Provider 128-bit for iSeries (#5727-AC3). - DB2 UDB for Linux, UNIX, and Windows v8.1 and later
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.
Installing and Using the StarSQL for Java Software
- The StarSQL for Java Quick Start Guide provides step-by-step instructions for installing and using the StarSQL JDBC driver in the shortest time.
- After you've installed the software, refer to the contents, index, or search the StarSQL for Java User's Guide for the topic or issue you want to learn more about.
- Browse the StarSQL for Java technical documents at http://www.starquest.com/Supportdocs/browse.shtml for specialized information, such as using the StarSQL for Java driver in a particular environment or to accomplish a special task.
All StarQuest products require a license to use the software. StarSQL for Java uses a file named StarLicense.properties for the license configuration. 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).
Known Issues
Administrator privileges may be needed to modify configuration
On a computer running Windows Vista or Server 2008 you may need administrator privileges to modify the StarLicense.properties file. Right-click on the Program group shortcut Edit StarLicense.Properties and enable the Run as Administrator option.
Using DatabaseMetadata API methods with synonym
Some DatabaseMetadata API methods may not work correctly when the table name is a synonym.
Error adding a table to a query using 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.
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
Release History
This section provides information about problems or enhancements that are made available as "point releases" and major releases of the [StarQuest product] software.
| Version Number | Release Date | Significant Changes |
|---|---|---|
| v2.58.0509 | 05/09/11 | 11677 StarPipes Proxy Licensing |
| v2.57.0228 | 02/28/11 | 11049 CLOB/BLOB implementation hides errors
11300 Reporting Precision of BIGINT 11582 Return meaningful value for Vendor Code (SQLCode) in getErrorCode method 11596 Calling getMoreResults on a prepared "query" can cause cursor to be inadvertently closed |
| v2.56.1116 | 11/16/09 | 10982 Some SBCS conversions missing for "common" MBCS hosts 10983 Change order of SECMEC in ACCSEC (workaround UDB 7.2 bug) 10984 Misinterprets ACCRDB replies - RDBAFLRM is error, regardless of SQLSTATE 11016 Failure to connect to some multi-byte UDB hosts |
| v2.55.0910 | 09/10/09 | 10856 Support JDBC 3.0 method getGeneratedKeys() 10892 problem with SQLDTA larger than 32K (affects stored procedures) 10903 handle CLOB output parameters from zOS |
| v2.54.0826 | 08/26/09 | 10881 JVM does not terminate due to persistent StarSQL/Java Threads |
| v2.53.0724 | 07/24/09 | 10712 NullPointerException occurs when changing the password using the newPassword property 10638 Support StarPipes RDBAliasing 10785 "driver not capable" error using the DB2 v9 row_number() over() function 10791 Support StarAdmin 10663 Documentation update 10806 Documentation update 10822 Bind problem (DBCLOB) to DB2 for zOS v8 10823 Bind problem (DBCLOB) to DB2 for zOS v9 10828 Cannot get table metadata for table using SQuirrel SQL Client |
| v2.52.0316 | 03/16/09 | 10624 Support INTEGER and SMALLINT data type conversion to BigDecimal |
| v2.51.1216 | 12/16/08 | 10457 Nullpointer exception when fetching data with Squirrel SQL client 10542 Support for DB2 Server for VSE & VM 10543 StarLicense.properties: change default settings |
Contacting StarQuest
If you need to contact technical support, please provide the following information to help the support engineers address your issue. You can contact StarQuest via phone, email, or facsimile as indicated at the bottom of this page.
| Company Information | Address Phone Fax |
| Contact Information | First and Last Name of individual contact Email Address |
| Host Type | Hardware and Operating System (i.e., AS/400 V5R4) |
| Network Protocol/Gateways | Protocol and/or Gateways used (i.e., TCP/IP, HIS 2000) |
| Client Type | Client Type and Operating System (i.e., Windows 2008 SP2) |
| StarQuest Product, Version, and Source |
Which StarQuest product and what version is installed (i.e., StarSQL for Windows v5.50.02.18) Where you obtained the software (i.e., direct from StarQuest, name of specific reseller) |
| Problem Information | Provide as much detail as possible, including information about any application that is using the StarQuest product when the problem occurs and the exact error message that appears. |
© 2009 StarQuest Ventures, Inc. All rights reserved.
StarQuest Ventures, Inc.
PO Box 1076
Point Reyes Station, CA 94956
Telephone: 415-669-9619
FAX: 415-669-9639
Sales & Support: contact@starquest.com
URL: http://www.starquest.com