Last Update: 19 June 2008
Product: StarPipes for Windows
Version: All
Article ID: SQV00SW001
The following FAQs are designed to answer some of the common questions regarding StarPipes for Windows.
General
Installation
Usage
StarPipes is a software product that operates on a Windows system as a service. StarPipes listens on a given port for incoming requests from DB2 users of software such as StarSQL via TCP/IP connections. It transfers messages using SNA-APPC conversation via Microsoft Host Integration Server or IBM Communication Servers to DB2 servers.
One of the advantages of StarPipes is that it eliminates the need for Microsoft Host Integration Client or IBM Communications Server Client on individual workstations.
Can I use StarPipes to connect to more than one DB2?
Yes, you can configure StarPipes to access multiple DB2 systems. StarPipes routes requests based on the RDB (Database Server) name. For each DB2 system you wish to connect to, you must establish APPC connectivity through Microsoft Host Integration Server or IBM Communications Server.
You need to be an administrator on the machine where you wish to install the StarPipes service. Run the setup.exe installation program to install StarPipes. You can choose to install both the StarPipes service and the Management Console, or just the Management Console if you only want to use StarPipes to remotely manage another computer.
StarPipes may be installed on the Host Integration Server (or Communications Server) or a client of Host Integration Server (or Communications Server).
Note: Reboot your Windows server or workstation after installing Microsoft Host Integration Server, including service packs.
Do I need a validation code (license)?
StarPipes does not require a license code to work, the license is managed by StarSQL or StarLicense.
How do I remotely manage StarPipes?
To use the Management Console, you need administrator level privileges on the machine where the StarPipes service is installed. On the remote machine, install only the StarPipes management tools. In the StarPipes Management Console, define a service on the remote machine where the StarPipes service is installed.
How do I configure StarSQL to use StarPipes?
Configure your StarSQL data source as usual for your DB2. Make sure that the Database Server Name of your StarSQL data source matches an entry in the StarPipes SNA or TCP/IP Routing entries.
In the StarSQL data source, on the "Network" page , select "TCP/IP" and for Host Name, specify the name or IP address of the Windows computer where the StarPipes service is installed. For the port, specify the port on which StarPipes listens for requests (the default is 446).
How do I view the usage statistics that StarPipes records?
In the StarPipes Configuration Logging properties, enable "Accounting Statistics". StarPipes will log usage information in two comma delimited text files which can be imported into a spreadsheet for sorting and analysis. Information recorded includes the IP address of the client requester, the DB2 user name, the length of time the connection was open and the average turnaround time of StarPipes. For more information on logging, refer to the StarPipes help.