Updated: 27 July 2009
Product: StarSQL for Windows
Version: 5.4x or later
Article ID: SQV00SQ008
This Quick Start Guide describes how to install, configure, and use the StarSQL ODBC driver (32-bit or 64-bit ) on a Windows computer, and is intended for first-time users of StarSQL. Users who are upgrading an existing installation should refer to the Release Notes and the StarSQL for Windows User's Guide for upgrade instructions. Read the complete document before starting your installation.
The estimated time to complete all tasks is approximately 30 minutes.
Before you begin, review the following list to ensure that you have the information and files you need, and that your computer environment provides the minimum requirements.
In order to connect to a DB2 host, a StarSQL data source must be configured with basic connectivity information. This DB2 connectivity information will also be used after the installation to bind host packages using the StarAdmin application.
The following sections guide you through the steps that are summarized below.
Step 1: Install StarSQL (estimated time: 5 minutes)
Step 2: License the Software (estimated time: 5 minutes)
Step 3: Install StarAdmin and Bind StarSQL Host Packages (estimated time: 10 minutes)
Step 4: Configure a Data Source Name (DSN) and Test Connectivity (estimated time: 5 minutes)
Estimated Time: 5 minutes
To successfully complete this section, you will need a user ID that has administrative authority on the Windows computer where the software will be installed.
At the end of the installation, a License Configuration dialog prompts you to enter your license key for using StarSQL. Leave this dialog open and proceed to Step 2 .
Estimated Time: 5 minutes
StarSQL requires a license for evaluation purposes. To complete this section, you will need the Registration Key in the Download Instructions that were sent to the email address specified in the StarQuest Product Download Request form.
If the computer running StarSQL has access to the Internet, follow the Online Licensing Instructions below. Otherwise, follow the Alternate Licensing Instructions.
When the request successfully completes, the license(s) for the software you are registered to use appear in the License Keys list of the Licenses tab. The Registration Key may produce several License Keys, depending on the products you are registered to use. Subsequent attempts to use the same Registration Key will result in the identical License Key(s) being retrieved.
http://starcust.starquest.com/Registration/index.html#license
Estimated Time: 10 minutes
To successfully complete this section you will need the following:
This step might be best performed by the database administrator.
If the packages are created and bound successfully, the summary output will look similar to the following:
Package binding starting: Wed Jul 29 14:44:03 PDT 2009
UID=SUPERUSER
HostName=DB2HOST.DOMAIN.COM
Port=446
Server=DB2PROD
PkgColID=STARSQL
AutoTypDefOvr=
BindRules=RUN
CustomizePrdid=No
UseJumboPackages=No
UseEncryption=Anyjdbc:StarSQL_JDBC://DB2HOST.DOMAIN.COM:446/DB2PROD;collection=STARSQL
SQL package SWNC0000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWNC0000 to PUBLIC
SQL package SWRU0000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWRU0000 to PUBLIC
SQL package SWRC0000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWRC0000 to PUBLIC
SQL package SWRR0000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWRR0000 to PUBLIC
SQL package SWTS0000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWTS0000 to PUBLIC
SQL package SWNC1000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWNC1000 to PUBLIC
SQL package SWRU1000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWRU1000 to PUBLIC
SQL package SWRC1000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWRC1000 to PUBLIC
SQL package SWRR1000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWRR1000 to PUBLIC
SQL package SWTS1000 in collection STARSQL has been created.
Granted execute privileges on STARSQL.SWTS1000 to PUBLIC
SQL package QSYS2 in collection STARSQL has been created.
Granted execute privileges on STARSQL.QSYS2 to PUBLICPackage binding completed: Wed Jul 29 14:44:55 PDT 2009
If any errors are reported, review the suggested resolutions in the Binding StarSQL Packages Using StarAdmin technical document, correct the problem and execute the bind operation again. If you are unable to resolve the error condition, copy the entire Summary text and send it to StarQuest Customer Support at contact@starquest.com.
Estimated Time: 5 minutes
To complete this section successfully, you will need a valid DB2 user ID that provides adequate authority to connect to the database.
You must configure a data source name (DSN) to your host before you can use StarSQL. To configure a data source after StarSQL is installed, start the ODBC Data Source Administrator. The ODBC Administrator is typically available from the Administrative Tools item of the Windows Control Panel. If you are running Windows x64, there is a 32-bit ODBC Administrator (located in Windows\SysWOW64) and a 64-bit ODBC Administrator (located in Windows\System32). If you have both versions of StarSQL installed, the ODBC Administrator shortcut in the StarSQL (32-bit) program group starts the 32-bit ODBC Administrator and the shortcut in the StarSQL (64-bit) program group starts the 64-bit version of the ODBC Administrator.
Add a new System or User DSN, configuring it with the values collected in the Before You Begin section and explained below. You may also refer to the Summary output from StarAdmin for these configuration values.
| OS/390 | OS/400* | UDB | |
| Database Server Name | DDF location | Database Server Name | Database Name |
| Package Collection Name | STARSQL | QGPL | STARSQL |
| Host Name | Name or IP Address | Name or IP Address | Name or IP Address |
| Port Number | 446 | 446 | 446 |
| Catalog Schema | SYSIBM | QSYS2 | SYSCAT |
*OS/400 users can alternatively create a library, such as STARSQL, to use as the Package Collection instead of using QGPL.
Note: If you are using StarPipes, enter the IP Address or network name of the StarPipes server in the Host Name field. By default, StarPipes for Windows listens on port 446.
Test your connection to the host while in the data source configuration wizard by entering in a valid userid and password. Check the option "Connect to host database..." and click either the Summary or Advanced button.
This Quick Start Guide is intended to help you install the StarQuest software and access DB2 data as quickly as possible.
As you use the StarSQL software, refer to the product documentation for more information. StarSQL provides an online help system that provides more information about defining ODBC data sources. Press F1 or click a Help button from the StarSQL Data Source Configuration Wizard to display the online help system.
If you encounter any problems while using the evaluation software, please send an email to StarQuest Customer Support at contact@starquest.com or call (+1) 415-669-9619 for assistance.
StarSQL User’s Guide
StarSQL Wizard Help system
StarSQL Technical Documents
The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization. The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.