StarSQL for Java
Version 2.50
August 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.
Apache Derby (JavaDB) 10.3 or later
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.
Apache Derby (JavaDB) 10.3 or later
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.
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 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.4.1 or later is recommended.
===================
Other Requirements:
===================
To use workstation licensing on UNIX, you must install the StarLicense
package for your UNIX operating system.
===========
What's New:
===========
StarSQL for Java v2.5 adds the following new features:
* Support for Apache Derby (JavaDB) databases
* Improved support for CLOB and mixed byte (especially UNICODE) data
* Improved buffer managment and parsing
* Improved exception handling
* roll-up of all previous fixes
=================================
Upgrading from previous releases:
=================================
* Important Note for users upgrading from early (prior to v2.x) versions
of StarSQL for Java:
The licensing configuration file has been renamed
from STARLICENSE.CFG to StarLicense.properties.
* 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.
==================================
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.
=============================================
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.
==============
CHANGE HISTORY
==============
Version 2.50
August 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.
Apache Derby (JavaDB) 10.3 or later
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.
Apache Derby (JavaDB) 10.3 or later
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.
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 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.4.1 or later is recommended.
===================
Other Requirements:
===================
To use workstation licensing on UNIX, you must install the StarLicense
package for your UNIX operating system.
===========
What's New:
===========
StarSQL for Java v2.5 adds the following new features:
* Support for Apache Derby (JavaDB) databases
* Improved support for CLOB and mixed byte (especially UNICODE) data
* Improved buffer managment and parsing
* Improved exception handling
* roll-up of all previous fixes
=================================
Upgrading from previous releases:
=================================
* Important Note for users upgrading from early (prior to v2.x) versions
of StarSQL for Java:
The licensing configuration file has been renamed
from STARLICENSE.CFG to StarLicense.properties.
* 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.
==================================
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.
=============================================
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.
==============
CHANGE HISTORY
==============