This document provides late-breaking information about the StarSQL for Windows ODBC software driver.
StarSQL for Windows provides fast reliable access to IBM DB2 relational databases from any ODBC-enabled application. The powerful StarSQL driver enables Windows applications on a desktop computer to transparently access, send SQL queries to, and retrieve results from databases on remote IBM mainframe, midrange, or UNIX systems, including double-byte hosts. This allows you to open a database on the host as if the database were stored on your local computer.
The following topics are addressed in these Release Notes. Refer to the StarSQL for Windows Quick Start Guide for detailed information about installing StarSQL for the first time, and refer to the StarSQL for Windows Help (sqwizard.chm) and User's Guide (ssqlwin.pdf) for detailed information about using the StarSQL for Windows driver.
You can install and run the StarSQL for Windows driver on computers with the following Windows operating systems. You can install the 32-bit version of StarSQL on 64-bit operating systems for use with 32-bit ODBC applications.
StarSQL requires Visual C++ 2017/2019 runtimes. The StarSQL installer will install the Microsoft-supplied Microsoft Visual C++ 2017/2019 Redistributable package if it is not already present on the system. The Microsoft Redistributable package will remain on the system if StarSQL is upgraded or uninstalled.
We recommend installing the latest Windows updates. For Windows Server 2012R2 and windows 8.1, the April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) is required.
StarSQL requires the Universal C Runtime (KB2999226), which is a Windows operating system component typically installed by Windows Update on systems earlier than Windows 10; it can also be downloaded from Update for Universal C Runtime in Windows. If not already present, this component is installed by the StarSQL installer as part of the Visual Studio 2017 redistributables. The error api-ms-win-crt-convert-I1-1-0.dll is missing will result if KB2999226 has not been installed.
The following command will display whether KB2999226 has been installed:
C> wmic qfe list brief /format:texttablewsys | findstr KB2999226
Note that these system requirements supercedes any listed in the online documentation.
The StarSQL ODBC driver works within a TCP/IP network to connect a Windows client directly to a DB2 host. You can also use a SSL (Secure Socket Layer) connection when supported by the host database, or in conjunction with a StarPipes Gateway.
If you need SNA connectivity to your host, the StarQuest StarPipes software can serve as a gateway between clients on a TCP/IP network and DB2 hosts on an SNA network. StarPipes can also be used to provide a SSL (Secure Sockets Layer) connection over a public network.
You can use the StarSQL driver to connect to any of the following host databases:
If you will be accessing Unicode or ASCII LOB data on DB2 for z/OS v8.1, it is recommended that you have applied the PTFs described in the IBM APAR PQ85495. For details, refer to the expert setting UseSYSDUMMYAEU in the StarSQL Configuration Wizard help (sqwizard.chm).
This release of StarSQL for Windows includes the following enhancements. .
This section describes issues of interest for users who are upgrading from a prior version of StarSQL.
StarSQL 6.34 & later supports (and properly describes) TIMESTAMP columns with a scale between 0 and 12. We have chosen to expose DB2's default timestamp precision of 6 as a separate data type name in SQLGetTypeInfo(), named "TIMESTAMP(6)", the type name "TIMESTAMP" is now described as having variable scale from 0 to 12. Setting the data source option HideTsScale=YES will instruct StarSQL to revert to pre-6.34 behavior and hide the variable scale version of TIMESTAMP in SQLGetTypeInfo().
This version of StarSQL requires Windows 7sp1 or 2008R2sp1 or later; older operating systems such as Windows XP, Windows Vista, Windows Server 2003 and Windows Srrver 2008 are no longer supported.
Detailed Upgrade Considerations
See the technical document Upgrade Considerations for StarSQL 6.1 & Later for detailed information including data source changes, installation hints and information about deprecated features.
Rebinding Packages
After installing StarSQL, you should rebind StarSQL packages on the host system if you upgrading from a version of StarSQL prior to V6.27. We suggest that you use StarAdmin to do this; see the StarSQL technical document Binding StarSQL Packages Using StarAdmin for details. If you are using any version of StarSQL prior to v6.19, upgrade those clients to StarSQL v6.19 or later or use a different package collection. See the StarSQL User's Guide (SSQLWin.pdf) for details about package compatibility.
There is no need to bind SQL packages for Derby databases.
StarSQL (64-bit) and StarSQL (32-bit) can be installed on the same system and are independent of each other.
StarSQL (64-bit) can use the same StarSQL packages as StarSQL (32-bit).
ODBC data sources for 32-bit and 64-bit environments are configured independently using the appropriate version of the Windows ODBC Administrator. The 32-bit version of ODBC Administrator is located in the Windows\SysWOW64 directory, and the 64-bit version is located in the Windows\System32 directory. Selecting the ODBC Administrator shortcut from the StarSQL (32-bit) program group invokes the 32-bit version of ODBC Administrator, and selecting the ODBC Administrator shortcut from the StarSQL (64-bit) program group invokes the 64-bit version.
The 64-bit ODBC driver appears with the name StarSQL (64-bit). The 32-bit version of the StarSQL ODBC driver is named StarSQL 32. Note that it is important to specify the correct driver name in File data sources or in DSN-less connection strings.
On a Windows x64 system, both 32-bit and 64-bit User Data Sources ("User DSNs") are visible to both 32-bit and 64-bit ODBC applications and both versions of ODBC Administrator, but are only usable by the matching type of application (i.e. 64-bit applications only can use 64-bit User DSNs, 32-bit applications can only use 32-bit User DSNs). If your ODBC application attempts to use the incorrect type of data source, a "Data source name not found and no default driver specified" error is returned. Attempting to open a User DSN with the incorrect version of ODBC Administrator will display the error "The setup routines for the StarSQL ODBC driver could not be found. Please reinstall the driver".
To help identify the type of a User DSN, you may want to add "_32" or "_64" to the data source name.
For additional information, see the Microsoft Knowledge Base article http://support.microsoft.com/kb/942976: "The 32-bit version of the ODBC Administrator tool and the 64-bit version of the ODBC Administrator tool display both the 32-bit user DSNs and the 64-bit user DSNs in a 64-bit version of the Windows operating system."
When using two-phase commit on a 64-bit computer, install only the 64-bit version of the Resource Manager Administration Tool. Only one version of the Resource Manager and MMC Plug-in can be installed at one time, and the 64-bit version of the Resource Manager can be used by both 32-bit and 64-bit ODBC applications. If you must use a version of the 32-bit StarSQL that is earlier than v5.5 for two-phase commit, do not install the Resource Manager component of StarSQL (64-bit).
To import and export data with the SQL Server 2005 and later using SQL Server Integration Services (SSIS), you will be using Business Intelligence Development Studio, which is a 32-bit application and displays only 32-bit providers. Consequently you will need to install both the 32-bit and 64-bit versions of StarSQL, and configure both 32-bit and 64-bit data sources with identical names. The SSIS runtime will select the appropriate version of the provider to use.
You also can use the older Data Transformation Services (DTS) for import/export. Be sure to use the 64-bit version of the DTS wizard DTSWizard.exe.
For OLEDB applications such SQL Server linked server function, use the 64-bit OLEDB Provider for ODBC (MSDASQL).
Refer to the following technical documents for additional information:
This section describes specific IBM issues and the FixPak and PTFs that may be necessary for StarSQL to function properly.
In general, it is a good idea to stay current with the PTF CUM and HIPER packages and the DB2 Group PTF, and to use the latest version of StarSQL. The following sections describe more specific issues for different versions of IBM i (OS/400); check to see that the PTFs listed below are either installed or superceded.
Install the following PTF's:
5770SS1-SI60775 for APAR SE64851
Install the following PTF's:
5770SS1-SI47677
5770SS1-SI47695
5770SS1-SI47401
5770SS1-SI47379
If you are using Java stored procedures, install PTF 5770SS1-SI39711.
If you are using LOB, install PTF 5770SS1-SI39331.
If you are at cum level ptf level C10229710 and experience unusual behavior, such as "SQLSTATE 22001, native error -404, [StarSQL][StarSQL ODBC Driver][DB2/400]Value for column COL1 too long.", install PTF 5770SS1-SI46072 for APAR SE51079.
If you are uploading XML data to the iSeries, install PTF 5770SS1-SI52427.
If you are using 2PC, install PTF 5770SS1-SI51103.
cum C8064610 or later
PTF 5761SS1-SI30581
If you are using LOB, install PTF 5761SS1-SI39331
If you are using stored procedures, install PTF's 5761SS1-SI36405 and 5761SS1-SI36136.
If you are uploading XML data to the iSeries, install PTF 5761SS1-SI52430.
f you are using 2PC, install PTF 5761SS1-SI51095.
PTF 5722SS1-SI23461
PTF 5722SS1-SI24317
If you are using stored procedures, install PTF's 5722SS1-SI22551, 5722SS1-SI36406, and 5722SS1-SI36059.
If you are working with BLOB data, install PTFs 5722SS1-SI22324 and 5722SS1-SI22335.
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.
Binding Packages on the host system
For hosts running Derby, there is no need to bind SQL packages on the host system.
Suppress Warnings from stored procedures
After upgrading from an older version of StarSQL or an older version of DB2, you may encounter new warning messages when invoking stored procedures; for example:
[DB2]PROCEDURE JPPNODOP RETURNED 1 QUERY RESULTS SETS
If you have an existing application that expects the older behavior, you can suppress warnings from stored procedures by adding the following to the [Default] section of swoodbc.ini (or swodbc64.ini) in the StarSQL Programs directory:
SuppressSpWarnings=Y
Using StarSQL with MSDASQL OLEDB provider or OpenOffice
To take advantage of StarSQL's Unicode support when using Open Office, or when using SQL Server linked server or other applications that use the MSDASQL OLEDB provider, set the AlwaysWide setting (available as either a connect string or a data source expert setting) to YES to instruct StarSQL to report SQL_CHAR and SQL_VARCHAR as SQL_WVARCHAR etc. This will cause the MSDASQL OLEDB provider to expose these columns as WString instead instead of String.
File DSNs and Microsoft Access
File DSNs that contain more than 255 characters may cause Microsoft Access to produce an error that the maximum length of the connection string has been reached. To avoid this, review the File DSN and remove any parameters that are not required for the connection. The only required parameters are Driver, HostName, Netlib, and Server. Any parameter that is set to the driver's default value may be safely removed. The default values can be found in the StarSQL online help (sqwizard.chm).
This section provides information about problems or enhancements that are made available as "point releases" between major releases of the StarSQL for Windows software.
| Version Number | Release Date | Significant Changes |
|---|---|---|
| v6.41.0331 | Mar 2020 | 14228 - SSL: handle case where SSL not loaded on z/OS host 14820 - Change default for QRYBUFSIZ from 256K to 2M |
| v6.40.0309 | Mar 2020 | 14364 - Build StarSQL & libiconv with VS2019 & IS2019 14750 - Add XA support 14801 - Invalid Timestamp Conversion (LUW->LUW) |
| v6.37.0719 | Jul 2018 | 14329 - parser issue in SQDR snapshot scenario |
| v6.36.0608 | Jun 2018 | 14308 - use dynamic SQL rather than packages for all catalog calls (DB2 z/OS) |
| v6.35.0430 | Apr 2018 | 14260 - connection to DRDA A/S servers that don't send SRVNAM and EXTNAM in the EXCSATRD 14288 - improve handling of DLL unload |
| v6.34.0116 | Jan 2018 | 14119 - improvements in reporting TIMESTAMP scale 14175 - improved support for TIMESTAMP(s) s>6 14183 - Config option HideTsScale to hide Variable scale TIMESTAMP |
| v6.33.1002 | Oct 2017 | 13988 - Cursor Identified is not open (WITH clause) 14007 - Expose Hidden Columns in SQLColumns 14068 - Improvements in SSL support |
| v6.32.0208 | Feb 2017 | 13778 - StarSQL installer: update to InstallShield 2016 13870 - Implement conditional passing of RSTREF for DB2 Z/OS XML processing |
| v6.31.1025 | Oct 2016 | 13788 - rename libiconv-2.dll |
| v6.30.0830 | Aug 2016 | 13718 - Build StarSQL & libiconv with VS2015 |
| v6.28.0817 | Aug 2016 | 13698 - Communications link failure retrieving XML column data 13715 - SQL Server 2016 Linked Server problems 13724 - insert of binary BLOB data |
| v6.27.0603 | Jun 2016 | 13663 - UDB BigInt overflow condition in catalog calls 13678 - Column name containing em-dash incorrectly translated by SQLDescribeCol |
| v6.26.0513 | May 2016 | 13653 - SQLStatistics Fails w/error -413 SQLCODE when CARDF column in SYSTABLES is > max(integer) |
| v6.25.0115 | Jan 2016 | 13579 - custom 1252 to Unicode conversion |
| v6.24.1223 | Dec 2015 | 13562 - Error in caching logic may cause conversion error for SQL_C_CHAR |
| v6.23.1110 | Nov 2015 | 13475 - Installer: update to IS2015 and use new SHA-256 code-signing certificate 13520 - Support additional cp1252 conversions |
| v6.22.1029 | Oct 2015 | 13392 - support IBM IDAA accelerator |
| v6.21.0507 | May 2015 | 13317 - DB2 LUW SQL Column maximum column name length should be reported as 128 |
| v6.20.1007 | Aug 2014 | 12620 - Expose alternate "character" data types (DB2 for z/OS) 12651 - DB2 for z/OS 11: add new error messages 12675 - Update host error messages for DB2 LUW 10.5 12714 - Return SQLSTATE=42S02 rather than 42704 for table not found error 12765 - Support Apache Derby 12768 - z/OS Identity Propagation 12789 - MSI Installer: add Derby; update to IS2013 12790 - Derby: add host messages 12803 - Update host messages for IBM i 7.2 12817 - Improve handling of certain dynamic values (DBMS version etc) 12884 - handle LOB output parameters from a stored procedure that returns result sets |
| v6.19.1307 | Jan 2014 | 12604 - Support SQL_C_BIT Conversions to integer and decimal data types. 12619 - Expose alternate "character" data types explicitly to provide Apps with better data type granularity at create table time. 12630 - Return "wide" SQL types for GRAPHIC etc |
| v6.18.1016 | Oct 2013 | 10302 Trace Viewer when SQLAM>6 and SQLDARD present in trace 12521 Abandon 2PC connection after AGNPRMRM SYNCCTL failure 12522 password key generation |
| v6.17.0912 | Sept 2013 | 12504 Hang when passing short string to stored procedure fixed length CHAR parameter |
| v6.16.0814 | Aug 2013 | 12487 Problems passing string parameter larger than 8k using ADO |
| v6.15.0620 | May 2013 | 12408 - Disable roundtrip conversion check 12428 - libiconv updates |
| v6.14.0508 | May 2013 | 12387 DescribeColumnAll only returns first 30 characters of column name in result set |
| v6.13.0201 | Feb 2013 | 12272 StarSQL returning incorrect data for some decimal datatypes |
| v6.12.1226 | Jan 2013 | 12089 SSL connection from Win7 or Server2008 to UDB fails 12212 CLOB data type not returned properly on SP by SQLDescribeColumn 12226 Unable to create datasource on Windows Server 2012 |
| v6.11.0720 | Jul 2012 | 12050 Fixes for columns-wise binding for result sets and parameters (64-bit) 12052 SQL_DESC_OCTET_LENGTH does not correctly reflect column byte count when alwaysWide is turned on. |
| v6.10.0319 | Mar 2012 | Initial release of v6.10 |
If you need to contact technical support, please provide the following information to help the support engineers address your issue. You can contact Stelo via phone, email, or facsimile as indicated at the bottom of this page.
| Company Information | Address Phone |
| Contact Information | First and Last Name of individual contact Email Address |
| Host Type | Hardware and Operating System (i.e., IBM i 7.3) |
| Network Protocol/Gateways | Protocol and/or Gateways used (i.e., TCP/IP, SSL/TLS) |
| Client Type | Client Type and Operating System (i.e., Windows Server 2019, Oracle Linux 8.6) |
| Stelo Product, Version, and Source |
Which Stelo product and what version is installed (i.e., StarSQL for Windows v6.41.0719) Where you obtained the software (i.e., direct from Stelo, name of specific reseller) |
| Problem Information | Provide as much detail as possible, including information about any application that is using the Stelo product when the problem occurs and the exact error message that appears. |
Stelo, a StarQuest company
548 Market St, #22938
San Francisco, CA 94104-5401
Telephone: +1 415.669.9619
Sales information: https://www.stelodata.com/contact-stelo
URL: https://www.stelodata.com
Support: https://support.stelodata.com
Info Center: https://docs.stelodata.com