StarSQL Release 5.39 Release Notes July 2008 Copyright 1994-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: Fast, reliable DB2 access middleware ============================================= StarSQL is a powerful ODBC driver that enables Windows applications on your PC workstation to transparently access, send SQL queries to, and retrieve results from databases on remote IBM mainframe, midrange, or UNIX systems, including double-byte hosts. Using your favorite Open Database Connectivity (ODBC)-enabled PC applications, your PC establishes a connection to access databases stored on the remote host. This allows you to open a database on the host as if the database were stored on your PC. This file contains important & last minute information about StarSQL. Be sure to read Late Breaking Notes for important information. Read the StarSQL Help (HTML) and StarSQL Users Guide (PDF) for more information. ======== CONTENTS ======== System Requirements Host Connectivity Host Databases LOB Support Late Breaking Notes Limitations Change History If You Need Help ==================== SYSTEM REQUIREMENTS: ==================== * Windows 2000 * Windows XP * Windows Server 2003 * Windows Vista * Windows Server 2008 * IBM AIX 4.3.3 and later * Sun Solaris 8 and later (SPARC) * Red Hat Linux 9.0 and later (x86) * SUSE Linux 9 or later (x86) * HP-UX 11i or later (PA-RISC) * FreeBSD 6.1 or later ================= HOST CONNECTIVITY ================= StarSQL can use any of the following networks to connect to the host: * TCP/IP * Microsoft Host Integration Server 2000 or higher * NetManage AS/400 Router * A SNA communications product that provides a CPI-C interface ============== HOST DATABASES ============== StarSQL can connect to any of the following host databases: * DB2 for OS/390 and z/OS v5.1 and later * SQL/DS (DB2 for VM & VSE) v3.3 and later * DB2/400 (DB2 UDB for iSeries) - OS/400 v3r2 and later * DB2 Universal Database (UDB) v6.x and later for UNIX and Windows. For native DRDA over TCP/IP support: * DB2 for OS/390 and z/OS v5.1 and later * DB2 for VM v6.1 and later * DB2 for VSE v7.1 and later * DB2/400 (DB2 UDB for iSeries, DB2 for i5/OS) - 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 v5r1 (with appropriate PTF's) and later * DB2 Universal Database v8.1 and later for UNIX and Windows. If you will be accessing Unicode or ASCII LOB data on DB2 for OS/390 or z/OS, it is recommended that you have applied the PTF's described in the IBM APAR PQ85495. For details, refer to the StarSQL documentation on the expert Settings UseSYSDUMMYAEU. ========== WHAT'S NEW ========== * Support for DB2 9 for z/OS and DB2 9 for Linux, UNIX and Windows * Support for Windows Vista and Server 2008 * Support for i5/OS v6r1 * enhanced international language support, including enhanced support for Group 2 multi-byte and double-byte character sets * enhanced Unicode host support ======================= Upgrade Considerations: ======================= After installing StarSQL 5.30, you should rebind StarSQL packages on the host system. We suggest that you use StarAdmin to do this. These packages are backwards compatible with StarSQL 5.1x and 5.2x clients. If you are using StarSQL 5.0x or earlier, we recommend that you upgrade those clients or use a different package collection. In addition, if you are upgrading from a previous version of StarSQL 5.3x (prior to 5.38), you should rebind packages if you are connecting to DB2 for z/OS and are changing the value of the new UseDynamicCatalogSQL expert setting from its default of "YES" to "NO". See the StarSQL User's Guide (PDF) for details about package compatibility. =============================== ODBC Data Source default changes =============================== The default values for the expert settings IncludeSynonyms and SpecialColumns have been changed to Yes. Using these settings can enhance the use of StarSQL with some ODBC-enabled applications such as Microsoft Query, as they can help the application identify join columns, etc. If you create a new data source, it will contain Yes for these values; however, if have an existing data source created with a version of StarSQL prior to 5.10, then you will need to use the Expert Page of the data source configuration wizard to modify these values if desired. The Expert Page can also be used to override the default values for new created data sources if you prefer to use a value of No. New expert setting UseDynamicCatalogSQL --------------------------------------- StarSQL 5.36.0605 introduces a new expert setting UseDynamicCatalogSQL. Selecting "Yes" will cause StarSQL to favor dynamic over static SQL for catalog functions when connected to DB2/zOS servers. The default for UseDynamicCatalogSQL is Yes. In addition, the default for UseDSCRDBTBL is now Yes if it is not found in the datasource. New SWODBC.INI keyword EXPLAIN ------------------------------ Adding the keyword Explain=All in the [Defaults] section of SWODBC.INI will cause all packages bound by StarSQL to be able to be explained using Visual Explain tools. This includes both dynamic SQL packages bound with StarAdmin (or created when needed by the StarSQL driver) and static SQL packages created with the StarScribe Package Editor. Change in underscore wildcard behavior -------------------------------------- The behavior of the expert setting useDSCRDBTBL = YES (the default) will cause StarSQL to NOT consider an underscore (“low line”) a wildcard for purposes of using the DSCRDBTBL DRDA command. This behavior enhances compatibility with certain third party applications. Users who require the underscore to function as a wildcard may set the expert setting useDSCRDBTBL to NO for purposes of SQLColumns, etc. The interpretation of ‘%” remains unaffected by this change; a “%” is never considered a component of a basic name. =================== LATE BREAKING NOTES =================== Binding catalog package to DB2 UDB v8 FP8 or FP9 fails ------------------------------------------------------ If you have installed fixpak 8 or fixpak 9 on DB2 UDB v8 (Windows and UNIX), you will not be able to bind catalog packages. This is an IBM problem (APAR JR21670). The fix is included in FixPak 10. OS/400 PTF's: ------------- In general, it is a good idea to stay current on PTF packages and the DB2 Group PTF, and use the latest version of StarSQL. The following sections describe more specific issues for different versions of AS/400; check to see that the PTF's listed below are either installed or superceded. v6r1: cum C8064610 or later PTF 5761SS1-SI30581 v5r4: PTF 5722SS1-SI23461 PTF 5722SS1-SI24317 If you are using stored procedures, install PTF 5722SS1-SI22551 If you are working with BLOB data, install PTF's 5722SS1-SI22324 and 5722SS1-SI22335 v5r3: After installing CUM PTF C5298530 or DB2 Group PTF SF99503-8 (November 2005), you may encounter a problem with incorrect precision information being returned for decimal and numeric fields. To resolve this problem, install PTF SI121373 for APAR SE23286. If you are using StarSQL to invoke Java stored procedures on an AS/400, install PTF 5722SS1-SI18139 for APAR SE20127. v5r2: After installing the cum PTF or DB2 Group PTF from December 2005, you may experience extremely high temporary storage usage when an ODBC application (such as SQDR) using StarSQL connects to the iSeries machine. If you encounter this problem, install PTF 5722SS1-SI23370 for APAR SE25005. If you are using StarSQL to invoke Java stored procedures on an AS/400: install PTF 5722SS1-SI18984 for APAR SE21110. v5r1: install PTF 5722SS1-SI09453, which corrects APAR SE10974: Calling a stored procedure over DRDA results in parameters being tagged as char data when the parameters are binary data. v4r4: The following are known issues with StarSQL and OS/400 v4r4 that are resolved by OS/400 PTF's: • function check on certain catalog SQL (also a problem with v4r3): install PTF SF59100 (v4r3) or PTF SF59120 (v4r4) for APAR SA84253. • function check after repeated iterations of certain catalog SQL and SELECT statements: install PTF SF59294 for APAR SA85033. • invoking a stored procedure returns a “DDM code point 2114 not supported” error message: install PTF SF58942 for APAR SA84890. • DRDA problem: SF62126 for APAR SA88584 • DRDA problem: SF62392 for APAR SA88896 =========== LIMITATIONS =========== When a Unicode application uses the StarSQL ANSI driver, it cannot send late-bound character data, i.e. character data bound using the SQL_LEN_DATA_AT_EXEC macro, for the C types SQL_C_CHAR, SQL_C_WCHAR, or SQL_C_TCHAR. ============== CHANGE HISTORY ============== 5.39.0715 10435 review use of locale sensitive functions used by StarSQL - in particular strtod 10436 escaped wildcard doesn't use DSCRDBTBL 10439 TrcViewer: display percent, underscore and back slash 5.38.0702 10416 Use list of catalog catalog qualifiers and IN Predicate, in favor of LOCATE/RTRIM (DB2 for z/OS V6 and later) 10417 add "FOR FETCH ONLY" to Catalog Queries 10420 provide mechanism for StarSQL packages to be bound with "EXPLAIN" enabled 10349 Cannot get table/view/procedure list in VS.NET 2005/2008 Server Explorer or Data Source Config Wizard 10425 Amend use of RTRIM(CREATOR) LIKE() to use alternative predicate form for MVS 10426 remove surprfluous CREATOR LIKE(%) in Catalog Static SQL for MVS 5.37.0617 10415 SQL_NO_DATA when fetching the first row for the re-executed resultset the 2nd-Nth time 5.36.0606 10413 add new expert setting "UseDynamicCatalogSQL" to "UseDynamic" for Catalog DB2/zOS V6 and later 5.35.0415 10374 Character substitution on assembled late parameter data confuses FSMs 10381 Multithread race condition in sqiconv.dll 5.34.0304 10343 FDOCA parsing error in SQLDTARD 5.33.0215 10331 Interaction between StarSQL and ODBC driver manager's Unicode conversion for long strings 5.32.0111 10314 sqimport 10310 Installer: move to InstallShield 2008 and add certificate & code-signing 10312 Installer: behavior of dsimport and other utilities in Vista 10319 SQL_MAX_COLUMN_NAME_LEN for UDB V8 10321 Add support for SQL_C_SBIGINT and SQL_C_UBIGINT input parameters 5.31.1212 10270 dsimport: fails if there is a long manifest list 10288 Char conversion fails for column name if segmented in SQLDARD 10295 Fix return value for SQLGetInfo SQL_MAX_CATALOG_NAME_LEN (BusinessObjects compatibility) 10296 Local result set repeats after SQL_NO_DATA_FOUND (BusinessObjects compatibility) 10279 Cannot record static sql statements containing 'IN' keyword 10284 StarScribe: validation fails with long (and complex) parameterized queries 10289 SQLDescribeParam makes too many internal calls to SQLDescribeCol 10301 thread synchronization issue with the dmobject code. 10302 Trace Viewer crashes if SQLAM>6 and SQLDARD present in trace (partial fix) 10304 BusinessObjects Designer crashes while fetching data from SQLColumns call 10305 No table list returned for schema that matches current UserID 10243 update All personalities to specify SQL_OUTER_JOINS=38, 1, "Y" 10251 Incomplete Catalog SQL for UDB 10257 ccsid.csv not found when ODBC application is run from other than C: drive 10308 Error calling SQLTables from BO Designer against DB2/400 10309 Parser and four part names 10293 2PC: StarSQL not fully setup for 2PC after installation (w/Resource Manager) (add registry entry for 2pc) ================ IF YOU NEED HELP ================ * Read the StarSQL Help (HTML) or the StarSQL Users Guide (PDF). * Browse the StarSQL technical documents in the support area at http://www.starquest.com, including the StarSQL Quick Start Guide. Before you contact technical support, be prepared to provide the following information: Company Information - Address - Phone - Fax Contact Information - Last and First Name - Email Address Product for IBM Host - IBM Host/Version (e.g. AS/400, v4r3) - Gateway/Version (e.g. HIS 2000, TCP/IP) - Operating System on PC/Version (e.g. Windows 2000 Server SP4) - StarSQL Version - Where You Got the Product From Problem Information - Application/Version (if applicable) - Exact Error Message (if applicable) - Nature of Your Request -------------------------------------------- -------------------------------------------- --------------------------------------------