StarSQL Technical Documents

Quick Start Guides | FAQs | StarSQL for Java | StarSQL General

Quick Start Guides

StarSQL Quick Start Guide (PDF): Article # SQV00SQ008
This document is a guide for installing and configuring the StarSQL for Windows ODBC driver.
StarSQL for UNIX Quick Start Guide (PDF): Article # SQV00SQ007
This document is a guide for installing and configuring StarSQL for UNIX.

Frequently Asked Questions (FAQs)

How to troubleshoot and report a StarSQL ODBC Driver for Windows problem: Article # SQV00SQ0016
This document describes how to collect the information needed to help StarQuest Customer Support troubleshoot a problem that you are encountering with the use of the StarSQL ODBC Driver for Windows.

How to troubleshoot and report a StarSQL for UNIX problem: Article # SQV00SQ0017
This document describes how to collect the information needed to help StarQuest Customer Support troubleshoot a problem that you are encountering with the use of the StarSQL for UNIX driver.
StarSQL FAQs: Article # SQ000I0112
The following FAQs are designed to answer common questions regarding StarSQL.
StarSQL Login FAQs: Article # SQ00ID0101
This article answers frequently asked questions (FAQs) about using StarSQL logins.
StarAdmin FAQ: Article # SQ00IS0063
StarAdmin is a stand-alone application bundled with StarSQL.
Frequently asked questions regarding DDF (Distributed Data Facility): Article # SQ000S0028
Do I need to run DB2 on the mainframe with the distributed options switched on in order to use StarSQL Pro? Our DBA says we run without this option at the moment
Common Installation Error Messages: Article # SQ000E0069
This technical document lists the most common error messages for StarSQL installations.
Common PC Error Messages for StarPipes for the AS/400: Article # SP000E0060
This document lists the most common error messages received by StarSQL users connecting with StarPipes for the AS/400.

StarSQL for Java Technical Documents

Logging StarSQL for Java Activity: Article # SQV00SJ001
If you only wish to log DRDA activity review this document for information about setting the connection parameter of the connection URL or datasource.
Sending Client Information to DB2 using StarSQL for Java: Article # SQV00SJ002
This document details how to use the native API in StarSQL for Java to pass client information with every DB2 connection request from an application server. This information can include the application name, user ID, workstation name, or an accounting string.
Using StarSQL for Java to Access DB2 from an Oracle Stored Procedure: Article # SQV00SJ003
This document describes how to use StarSQL for Java to access a DB2 database from an Oracle database.
How to troubleshoot and report a StarSQL for Java problem: Article # SQV00SJ004
This document describes how to collect the information needed to help StarQuest Customer Support troubleshoot a problem that you are encountering with the use of the StarSQL for Java driver.

General StarSQL Technical Documents

Creating a Custom StarSQL 5.x Installable Image: Article # SQV00SQ006
This document describes how to create and execute a silent installation that can help rapidly deploy the StarSQL driver on a large number of Windows-based client computers. A normal (non-silent) installation receives the necessary input from the user in the form of responses to dialog boxes. A silent installation uses the settings specified in a response file instead of prompting for user input. This reduces the installation time and ensures that StarSQL is installed the same way on every computer.
Deploying a Silent Installation of StarSQL using Microsoft Systems Management Server (SMS): Article # SQV00I0054
This document describes how to deploy StarSQL to a large number of desktops using Microsoft Systems Management Server (SMS) and a StarSQL silent installation package. It provides a sample of the SMS package definition file (PDF) to use as a base for customization.
How to Resolve InstallShield Error 1607: Unable to Install InstallShield Scripting Run Time: Article # SQV00SQ0012
This document attempts to detail all of the possible solutions that are known to resolve this error. Depending on your system, you may need to try some or all of the listed suggestions.
StarSQL Character Conversion and National Language Support: Article # SQV00SQ0015
The document describes the format of the file that StarSQL uses to look up CCSID values and determine which character conversion routine to use for converting character data between disparate systems, and lists the CCSIDs that are currently supported by StarSQL.

How To Use a StarSQL Data Source in a SQL Server 2005 SSIS Package: Article # SQV00SQ0011
This document describes how to create a SQL Server 2005 Integration Services (SSIS) package to import or export DB2 data using a StarSQL data source.

Executing DB2 SQL Parameterized Stored Procedures from a Visual Basic .NET Application Using StarSQL: Article # SQV00SQ009
This document describes how to execute DB2 SQL parameterized stored procedures from a Visual Basic .NET application using the StarSQL software and the Microsoft ODBC.NET Data Provider.
Executing a DB2 Query from a Visual Basic .NET Application Using StarSQL: Article # SQV00SQ0010
This document describes how to execute a DB2 query from a Visual Basic .NET application using the StarSQL software and the Microsoft ODBC.NET Data Provider.
Using StarSQL with the Perl DBI Module: Article # SQV00SQ0013
This document explains how to set up and use StarSQL and unixODBC with Perl on UNIX platforms. The same concepts should apply to using Perl on Windows. This document also provides instructions on how to create and run a CGI application written in Perl on an Apache HTTP Server.
Using StarSQL with PHP and php-odbc: Article # SQV00SQ0014
This document explains how to set up and use StarSQL and unixODBC with Apache and PHP on UNIX. The same concepts should also apply to using PHP on Windows. This document provides instructions on how to create and run a stand-alone PHP application and a PHP Web server application.
How to Bind StarSQL Packages Using StarAdmin: Article # SQ000I0125
StarSQL for Windows includes an application called StarAdmin that you can use to bind SQL packages on the host. You must create and bind all required packages when setting up StarSQL, after upgrading DB2, or after a major upgrade of StarSQL versions.
Calling an AS/400 Program with QCMDEXC: Article # SQ00IS0127
You can execute a program on the AS/400 using the program QCMDEXC.
Improving Performance in Microsoft Access 95 (Access 7.0): Article # SQ00AD0007
This article presents some registry entries to adjust when investigating Microsoft Access performance issues with StarSQL.
How to Create a Local Index in Microsoft Access (Text Only): Article # SQ00AD0001
This technical note explains how to create a local index for attached tables in Access 2.0, Access 95 and Access 97.
How to Create a Local Index in Microsoft Access: Article # SQ00AD0002
This technical note explains how to create a local index for attached tables in Access 2.0, Access 95 and Access 97.
Using StarSQL with Microsoft Access FAQs: Article # SQ0ADE0003
This technical document presents solutions for common problems encountered with StarSQL and Microsoft Access 2.0, 7.0 and 8.0.
Inserting Times into attached DB2 tables in Microsoft Access: Article # SQ0ADE0079
This document shows you the correct format for inserting a time into an attached DB2 table in Microsoft Access.
How to Create a SQL Pass Through Query in Microsoft Access (Text Only): Article # SQ00AD0004
This technical note explains how to create a SQL pass through query in Access 95 or Access 97.
How to Create a SQL Pass Through Query in Microsoft Access (Text Only): Article # SQ00AD0004
This technical note explains how to create a SQL pass through query in Access 95 or Access 97.
How to Join a DB2 table and a Local Microsoft Access Table: Article # SQ00AD0006
This article describes how to join a DB2 table and a local Microsoft Access table for optimal performance.
Sample ADO Code using RecordCount property: Article # SQ00AD0097
Below is sample code written in Visual Basic 6.0 which demonstrates how to successfully use the RecordCount property for an ADO Resultset. With a ForwardOnly cursor, you must set the CursorLocation property of the ADO Connection to client.
Sample ADO code to query DB2 Table and return data: Article # SQ00AD0096
Below is sample code written in Visual Basic 6.0 which demonstrates how to connect to your DB2 host via StarSQL using ADO, issue a SELECT against a table passing a parameter to the WHERE clause. Results are displayed in a listbox.
Sample ADO code to access static SQL: Article # SQ00AD0093
Below is sample code written in Visual Basic 6.0 which demonstrates how to access a static SQL statement embedded in a static package bound on the host. This method accesses the statement directly by statement name, rather than the more typical technique, which relies on the StarSQL driver to match SQL statements in the code to those in the package.
Sample ADO code using Update and UpdateBatch: Article # SQ00AD0095
Below is sample code written in Visual Basic 6.0 which demonstrates how to insert records into a table using .AddNew with both .Update and .UpdateBatch methods. A common error, “Insufficient base table information for updating or refreshing”, is resolved by upgrading to StarSQL 4.0 or later.
SQL Catalog Functions Default to the Userid for the Catalog (Schema) Name: Article # SQ000E0113
The default behavior for StarSQL in an ODBC catalog call is to use your userid as the catalog or schema name if you do not specify one (i.e. you leave it empty string or null).
APPC Network Error - Verbid 0B00, Primary_rc 0003, Secondary_rc 084B6031 When Using StarSQL and Microsoft SNA Server: Article # SQ000E0010
When using StarSQL and Microsoft SNA Server to connect DB2/MVS you may receive an error APPC Network Error - Verbid 0B00, Primary_rc 0003, Secondary_rc 084B6031. This error can occur when the MAXDBAT ZPARM was set to zero in DB2.
Error: Unexpected APPC Network Error - Verbid 1400, Primary_rc F004, Secondary_rc 010000F0: Article # SQ00EI0091
When using StarSQL Pro and SNA Server to connect DB2, you may receive the following error Unexpected APPC Network Error - Verbid 1400, Primary_rc F004, Secondary_rc 010000F0.
Sample Code: ASP Script for use with Microsoft IIS: Article # SQ000D0080
ASP script that shows you how to connect to your DB2 with StarSQL.
How to Automate StarSQL Logins: Article # SQ00DI0011
If you would like to embed your password so that you do not have to enter it every time you use StarSQL, you may automate the process. This document shows you how to automate StarSQL logins by including the DB2 userid and password for the data source in your registry or your file DSN.
Preventing Users from Creating Packages in DB2/400: Article # SQ000S0012
AS/400 database administrators can control a user's ability to create packages by changing the authority on the CRTSQLPKG (Create SQL Package) object.
Using Business Objects with StarSQL: Article # SQ00AE0131
With Business Objects 4.1.5, you have the option of installing special StarSQL modules to fully take advantage of all of the features of StarSQL. With these modules installed, the universe wizard in the Business Objects Designer may report the following error when selecting a table to use in the universe.
Error: CCSID 500 is invalid or not supported: Article # SQ000E0016
StarSQL users connecting to DB2 for OS/390 (DB2/MVS) may get error messages indicating that CCSID 500 is not valid. These error messages are usually resolved by setting the appropriate ZPARM on DB2.
CISC AS/400 problems and PTFs: Article # SQ00SI0114
This document describes the scenarios and solutions to problems you may have when connecting to an AS/400 v3r1 or v3r2.
Error: Connection refused by remote host or Connect Host <hostname> not found: Article # SQ00EI0090
The host name specified in the StarSQL data source setup does not match the hostname of the system you are trying to connect to or TCP/IP is not started on the host. This is an error message returned from the host when you try to connect via direct TCP/IP.
Creating Restricted Views in SQL/DS: Article # SQ00DS0019
This document explains the requirements and steps necessary to create restricted views in SQL/DS. Example SQL statements used to create restricted views are provided.
SQL Syntax Error with Seagate Crystal Reports 6.0: Article # SQ00AD0020
When using Crystal Reports 6.0, you recieve an error message about the SQL syntax or an invalid token.
CRW 7 Maintenance Release Tech Note: Article # SQ00AE0139
There is a problem with Maintenance Release 1 of Crystal Reports where you will get a security error when running a report. You may get the error message: SECMEC value '4' is not supported.
Sample Code: DAO (VB 4.0) Updating an AS/400 Table Using a Microsoft Access Database: Article # SQ00AD0023
This is sample Visual Basic code that shows how to use DAO to update an AS/400 table as an attached Microsoft Access table.
How to Distribute StarSQL Data Source(s) to Your Users: Article # SQ000I0025
StarSQL ships with an administrative tool (DSIMPORT) that allows you to distribute your datasources to your users. This technical document explains how to use DSIMPORT.
Error ‘Couldn’t find file c:\starsql.mdb’ when using the Data Control in Visual Basic: Article # SQ00DE0024
When using Visual Basic and DAO to access tables remotely, you may receive the error: Couldn’t find the file ‘C:\starsql.mdb’. This occurs because DAO by default expects an Access database to be the source.
Enabling TCP/IP Access for DB2 for OS/390: Article # SQ00IS0027
This document discusses the system requirements for direct TCP/IP access to DB2 for OS/390.
How to: Drop and Rebind StarSQL Static Packages (AS/400): Article # SQ000I0031
This document explains how to drop and rebind old StarSQL static packages and bind (create) new packages.
Using a DSN-less Connection with StarSQL: Article # SQ000D0032
This technical document describes how to create a connection to DB2 using StarSQL that does not use a data source name (DSN). This type of connection is known as a DSN-less connection. The use of DSN-less connections eliminates the need to create ODBC DSNs in order to access the database server.
SQL Server 7 DTS Wizard Error: Article # SQ00AE0107
StarSQL clients using the Query Builder function in the DTS Data Import/Export Wizard to retrieve data from DB2 may receive the following error message when selecting a table:
How To Use The ODBC API SQLExtendedFetch With StarSQL: Article # SQ000D0118
This document details how the ODBC API SQLExtendedFetch can be used with StarSQL.
Access Violation (gpf) when closing an ODBC-enabled application in Windows 95: Article # SQ000E0034
Applications running on a Windows 95 platform produce an access violation (GPF) when the user closes the application.
How to Generate a DRDA Trace with the StarSQL DRDA Trace Recorder: Article # SQ00DE0099
This document explains how to generate a DRDA Trace with the StarSQL DRDA Trace Recorder.
How to Enable Connection Pooling: Article # SQ0ADI0035
This document explains how to enable and configure connection pooling for use with Microsoft Transaction Server and Internet Information Server.
How to Enable DRDA over TCP/IP for OS/400 V4R2 and later: Article # SQ00IS0036
This technical document explains how to configure your AS/400 to accept DRDA requesters, such as StarSQL Pro, over TCP/IP.
How to Generate an ODBC Trace With the ODBC Administrator: Article # SQ00DE0037
This document explains how to generate an ODBC API Trace from the ODBC Administrator. It provides instructions for ODBC Administrator version 2.x and 3.x. ODBC API traces are useful to Customer Support for isolating problems.
IIS Fails Through Microsoft SNA Server 4.0 with SP1 with Primary Return Code F004: Article # SQ00ADE088
When using an ASP script with StarSQL AND Microsoft SNA Server with Service Pack 1 installed, you are unable to connect. You get an error message, “APPC Network Error: AP COMM SUBSYSTEM NOT LOADED. Verbid 1400. Primary return code F004, Secondary Return code 0100000F0”. You can connect successfully using StarSQL with other ODBC-enabled applications.
Performance Tuning of Microsoft SNA Server for use with StarSQL: Article # SQ000I0094
This article discusses how to optimize SNA Server performance. It is intended for use by systems programmers and the Microsoft SNA Server administrator.
How To Use JDBC With StarSQL: Article # SQ000D0116
This document explains how to use JDBC with StarSQL. For best results, we encourage that you use StarSQL for Java with your Java applications.
How to Use a Microsoft SQL Server Linked Server to Access DB2 with StarSQL: Article # SQ00AI108
SQL Server linked servers can be used to access DB2 through a StarSQL ODBC data source. This document demonstrates how to add and use a linked server.
Using StarSQL to Access Multi-Member Files: Article # SQ000S0043
This document explains how to use StarSQL to access members in multi-member files on the AS/400 system.
Error: Database server DB2 [DB2/400, SQL/DS] . . . not supported by this version (#0): Article # SQ00ES0045
Older versions of the StarSQL may return this error, or a similar error, with newer versions of the host database. In every case, upgrading StarSQL resolves the error and is the preferred solution.
Accessing Non Externally Described Files on the AS/400: Article # SQ000S0046
This document outlines the conversion for a System/36 Program-described file to an externally described file.
Sample Code: Connection in Visual Basic DAO Using ODBC Direct: Article # SQ000D0047
This is sample Visual Basic 5 code that shows how to establish a DAO connection using ODBC Direct. Visual Basic 4 does not support ODBC Direct Workspaces.
Using StarSQL with Microsoft Office 97 FAQs: Article # SQ000A0048
This technical document presents solutions for common problems encountered with StarSQL and Microsoft Office.
Error “Catalog tables could not created...” with PowerBuilder: Article # SQ0ADE0049
When using PowerBuilder 5.0 against an AS/400, you receive an error Catalog tables could not be created and are not available for use.
PowerBuilder Performance Tips: Article # SQ00AD0050
When you are developing PowerBuilder applications, you may experience poor performance querying table catalog information. This document suggests ways to improve performance.
Sample Code: Connection in Visual Basic Using RDO: Article # SQ000D0051
This is sample Visual Basic code that shows how to establish an RDO connection.
Sample SQL for Registering a Stored Procedure on the AS/400: Article # SQ00ID0109
This document provides sample SQL used to register a stored procedure on an AS/400. It assumes you have already written the stored procedure that you want to register and a have program on the AS/400 that the stored procedure will reference.
Creating Restricted Views in DB2/MVS: Article # SQ000S0052
The simplest way to create a restricted view is to use StarAdmin. This document explains the requirements and steps necessary to create restricted views manually on DB2/MVS. Example SQL statements used to create restricted views are provided.
How to configure DB2 For Windows NT to Allow Two-Phase Commit Processing: Article # SQ00ID0119
StarSQL, version 3.0, introduces support for Two-Phase Commit (2PC) processing over APPC. DB2 for Windows NT (UDB) requires some configuration to allow this using DRDA. This document will explain the setup required on the DB2 server.
Sample ADO Code to Call a Stored Procedure and Return Output Data: Article # SQ00AD0123
This document provides sample Active Server Page (ASP) code that uses ADO with StarSQL to call a stored procedure and return output parameter data. This sample assumes there is already a stored procedure registered on the host that calls an existing program.
GPF When Viewing SQL Server Tables with StarSQL Pro: Article # SQ000E0062
It appears that I am viewing SQL Server tables when I am trying to connect to DB2 with StarSQL or my application GPFs when I try to open a table for the first time with StarSQL.
Cognos Imprompt returns error when connecting to AS/400: Article # SQV00SQ001
The following error may occur when Cognos Imprompu attempts to connect to an AS/400 using StarSQL: [Microsoft][ODBC Driver Manager] Invalid argument value.
How to Return Result Set Column Names from a DB2 Stored Procedure: Article # SQV00SQ002
When calling a DB2 for OS/390 stored procedure the result set column names may not be returned to the application.
Creating a Custom StarSQL 4.x Installable Image: Article # SQV00SQ003
The StarSQL setup program provides a choice for creating an installable image. With this option, the choices you make during the installation are recorded as you run the installation program. You can then use the installable image to install StarSQL for Windows on multiple desktops without having to repeat the setup dialog responses on each PC.
How to make a connection in Visual Basic .NET with StarSQL and the ODBC.NET: Article # SQV00SQ004
This technical article provides sample code to make a connection using the ODBC .NET Managed Provider in Visual Basic .NET and StarSQL.
AS/400 iSeries tuning tips to improve performance when using StarSQL: Article # SQV00SQ005
This technical article offers AS/400 iSeries tuning tips to improve performance when using StarSQL.
Using the DYNAMICRULES Bind Option With StarSQL: Article # SP00IS0065
StarSQL version 2.52 and later supports the use of the DYNAMICRULES Bind option for use with DB2, version 4.1 and above, on MVS systems. The DYNAMICRULES Bind option can be used in situations where dynamic SQL is being used from the client application but enhanced security is required on the DB2 host.
StarSQL and IIS FAQ: Article # SQ0ADE0066
This document describes solutions to the most common problems using StarSQL with Microsoft's Internet Information Server versions 3.0 and 4.0.
Choosing A StarSQL Network Option: Article # SQ000I0070
To connect your PC client to a DB2 host with StarSQL, you need to choose a network transport in the data source configuration. This technical document explains the use of the Select Network option in the data source.
How to Change the Read-Only Attribute of StarSQL: Article # SQ000E0115
StarSQL data sources can be configured to be “read-only” which prevents the user from updating the database.
How To: Dynamically Changing Static Package Files: Article # SQ000D0072
Typical project development occurs in teams, not by a single programmer. Those who wish to utilize the static sql capabilities of StarSQL find a problem with administering the package files created by multiple programmers. This is especially the case with web site development.
Performance Tips for StarSQL and Universal Database (UDB): Article # SQ00ID0121
This document provides tips to improve performance when connecting to Universal Database (UDB) with StarSQL.
StarSQL Workaround For Updating DB2 Tables with Timestamps in Microsoft Access and Visual Basic: Article # SQ00AD0074
This document discusses an update problem using StarSQL and the Microsoft’s JET database engine for DB2 timestamp data. Applications that use JET include Microsoft Access and Visual Basic (DAO).
Upgrading a StarSQL Data Source from Version 2.x to 3.x: Article # SQ000I0111
The StarSQL 4.x/5.x Data Source Setup is now the StarSQL Setup Wizard. This document is a guide to ease your transition from StarSQL 2.x to StarSQL 4.x/5.x. It explains how to correlate the StarSQL 2.x data source parameters with the new Setup Wizard.
Using Lotus Approach with StarSQL: Article # SQ000A0075
Updates of DB2 data using Lotus Approach must meet minimum StarSQL requirements.
Using the VB5 Data Form Wizard with StarSQL: Article # SQ000D0077
When using the Visual Basic 5 Data Form Wizard to create a form, the programmer has two choices of controls, remote data control and data control.
Using the VB6 Data Form Wizard with StarSQL: Article # SQ000D0128
When using the Data Form Wizard in Visual Basic 6 (VB6), you may get the following error message: ’The operation requested by the application is not supported by the provider.’
Formatting Date/Time strings for DB2 in Visual Basic: Article # SQ00DS0076
Visual Basic formatted date and time strings do not match syntax acceptable to DB2, resulting in an error such as: “SQL Syntax error”, or “Syntax of date, time, or timestamp value not valid.”

Technical Documents | Customer Support | Home