StarQuest Technical Documents

Quick Start Guide for StarPipes for Windows

Last Update: 19 June 2008
Product: StarPipes for Windows
Version: 2.x or later
Article ID: SQV00SW002

Abstract

This document is a guide for installing and configuring StarPipes for Windows. Please read through it completely before starting your installation. Please follow the instructions specific to your purpose. If you are using StarPipes with IBM Communications Server for Windows, please refer to the StarPipes for Windows Help.

Solution

Step 1: Complete pre-installation tasks
Step 2: Install StarPipes
Step 3: Configure a route
Step 4: Configure a StarSQL data source

Step 1: Complete pre-Installation tasks for SNA to TCP/IP. (There are no pre-Installation tasks for using as a TCP/IP gateway.)

This document assumes that you already have a Microsoft Host Integration Server configured to connect to your DB2 host. Gather the following information from your Host Integration Server:

  • Local LU
  • Remote LU
  • Mode

Return to the top

Step 2: Install StarPipes.

When installing StarPipes, you will be given the following choices:

  • Install StarPipes for Windows:
    Choose this option to install StarPipes on any Windows server or workstation for users to connect through to the DB2 host.
  • Install StarPipes Management Utilities:
    Administrators can choose this option if they would like to remotely monitor StarPipes connections.

Next, you will be asked to specify the connectivity method you will be using:

  • If you are using SNA, choose Microsoft SNA Server.
  • If you are connecting directly via TCP/IP to your DB2 host, choose None.

At the end of the installation, you will be given the option of configuring StarPipes for Windows. Use this application to configure StarPipes routes to your DB2 host. You can run the StarPipes Configuration application now or later.

Return to the top

Step 3: Configure a route.

You must configure a StarPipes route to your host before you can use StarSQL. Open the StarPipes Configuration from the StarPipes program group.

For SNA to TCP/IP connectivity:

  • Click on the Communications Tab.
  • The TCP/IP port is the port StarPipes monitors for incoming and outgoing DRDA messages. The default is 446.
  • Click on Add.
  • Choose SNA LU6.2.
  • RDB Name: This corresponds to the Database Server Name in your StarSQL data source.
  • Enter the Local LU, Remote LU, and Mode from Step 1.
  • Click OK to save the route.
  • Click on the Service Control tab and verify that StarPipes is running.

For TCP/IP gateway:

  • Click on the Communications Tab.
  • The TCP/IP port is the port StarPipes monitors for incoming and outgoing DRDA messages. The default is 446.
  • Click on Add.
  • Choose TCP/IP.
  • RDB Name: This corresponds to the Database Server Name in your StarSQL data source.
  • Host Name: This is your DB2 TCP/IP host name or IP address.
  • Port: The port on your host on which you have configured DRDA to listen for requests (usually 446).
  • Click OK to save the route.
  • Click on the Service Control tab and verify that StarPipes is running.

Note: You may wish to change the StarPipes service from "manual" to "automatic" so that it will start automatically every time this computer is started. This change can be made in Windows Services.

Return to the top

Step 4: Configure a StarSQL data source

Please refer to the Quick Start Guide for StarSQL for directions on how to configure a data source to your host.

Note: These are the exceptions to the data source configuration.

  • Host Name: This is the name of the Windows computer on which StarPipes is installed.
  • Port: This is the port StarPipes is listening on (default is 446).

Return to the top

Other references:
StarPipes for Windows Help (.chm)

DISCLAIMER

The information in technical documents comes without any warranty. 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 information in technical documents may be gathered from various sources, including IBM, Microsoft, and other organizations.