StarPipes for Windows v3.03
December 2007
Copyright 1994-2007 StarQuest Ventures, Inc.
All Rights Reserved.
StarQuest Ventures, Inc.
PO Box 1076
Point Reyes Station, CA 94956
Telephone: 415-669-9619
FAX: 415-669-9629
Sales & Support: contact@starquest.com
URL: http://www.starquest.com
This directory contains StarPipes, TCP/IP-to-SNA conversion software
for use with StarSQL and other DRDA requesters. This should be
installed on a Windows computer if you wish to take advantage of
the TCP/IP support in StarSQL to connect to DB2 systems that do not
support DRDA over TCP/IP.
StarPipes can also be configured to allow TCP/IP messages to flow directly
to the DB2 host unchanged; in this case, the DB2 system must support
DRDA over TCP/IP.
Advanced features include access to multiple DB2 hosts through a single
Windows server and support for the PEM (Password Management) feature.
System Requirements:
* Windows 2000
* Windows XP
* Windows Server 2003
* Windows Vista
* TCP/IP support configured and running on the Windows system.
Use of a static IP address (rather than DHCP) is highly recommended.
* StarSQL or other DRDA client software using native TCP/IP
connections.
* For SNA-APPC connections, one of the following:
Microsoft Host Integration Server 2000 or later
IBM Communications Server for Windows NT, version 5.01 or later
During installation, you will be prompted for your choice of SNA
server (Microsoft Host Integration Server, IBM Communications Server, or none).
If you wish to switch later, you will need to reinstall StarPipes for
Windows.
StarPipes for Windows will work with either the client or server
software of the SNA server; however, for best performance we recommend
that StarPipes for Windows be installed on the same machine as the
SNA server.
Updating from previous versions:
================================
If you are upgrading from StarPipes for Windows NT v2.20 and earlier,
you must first remove the old version by selecting "Uninstall
StarPipes for Windows NT" from the StarPipes for Windows NT
Program Group.
This will also remove your StarPipes configuration; you should make a
note of the configuration before removing the old version.
Known Limitations:
==================
When configuring StarSQL v5.0 & later, the Network pane contains a
Test Connection button that verifies host connectivity.
Using this test may result in a "Communications link failure" message,
but the test can still be used to verify connectivity to the StarPipes
gateway and whether a valid license was found. This is a known
limitation of StarSQL.
Revision History:
=================
3.03.1203 12/03/07
10291 Debug trace information is obscured when using default Local/Remote LUs
10292 VTAM/DB2 V8 want SECMGR(1) if ASSEC(<=5) and APPC
3.02.1129 11/29/07
10278 Invalid trace files being produced by StarPipes
10281 log SECMEC value to StarPipes trace file
10283 Support Test Connection button from StarSQL clients
3.01.1125 11/25/07
10276 Application Trace request crashes Service
10277 Support ACCSEC SECMEC values for Encryption with APPC hosts
December 2007
Copyright 1994-2007 StarQuest Ventures, Inc.
All Rights Reserved.
StarQuest Ventures, Inc.
PO Box 1076
Point Reyes Station, CA 94956
Telephone: 415-669-9619
FAX: 415-669-9629
Sales & Support: contact@starquest.com
URL: http://www.starquest.com
This directory contains StarPipes, TCP/IP-to-SNA conversion software
for use with StarSQL and other DRDA requesters. This should be
installed on a Windows computer if you wish to take advantage of
the TCP/IP support in StarSQL to connect to DB2 systems that do not
support DRDA over TCP/IP.
StarPipes can also be configured to allow TCP/IP messages to flow directly
to the DB2 host unchanged; in this case, the DB2 system must support
DRDA over TCP/IP.
Advanced features include access to multiple DB2 hosts through a single
Windows server and support for the PEM (Password Management) feature.
System Requirements:
* Windows 2000
* Windows XP
* Windows Server 2003
* Windows Vista
* TCP/IP support configured and running on the Windows system.
Use of a static IP address (rather than DHCP) is highly recommended.
* StarSQL or other DRDA client software using native TCP/IP
connections.
* For SNA-APPC connections, one of the following:
Microsoft Host Integration Server 2000 or later
IBM Communications Server for Windows NT, version 5.01 or later
During installation, you will be prompted for your choice of SNA
server (Microsoft Host Integration Server, IBM Communications Server, or none).
If you wish to switch later, you will need to reinstall StarPipes for
Windows.
StarPipes for Windows will work with either the client or server
software of the SNA server; however, for best performance we recommend
that StarPipes for Windows be installed on the same machine as the
SNA server.
Updating from previous versions:
================================
If you are upgrading from StarPipes for Windows NT v2.20 and earlier,
you must first remove the old version by selecting "Uninstall
StarPipes for Windows NT" from the StarPipes for Windows NT
Program Group.
This will also remove your StarPipes configuration; you should make a
note of the configuration before removing the old version.
Known Limitations:
==================
When configuring StarSQL v5.0 & later, the Network pane contains a
Test Connection button that verifies host connectivity.
Using this test may result in a "Communications link failure" message,
but the test can still be used to verify connectivity to the StarPipes
gateway and whether a valid license was found. This is a known
limitation of StarSQL.
Revision History:
=================
3.03.1203 12/03/07
10291 Debug trace information is obscured when using default Local/Remote LUs
10292 VTAM/DB2 V8 want SECMGR(1) if ASSEC(<=5) and APPC
3.02.1129 11/29/07
10278 Invalid trace files being produced by StarPipes
10281 log SECMEC value to StarPipes trace file
10283 Support Test Connection button from StarSQL clients
3.01.1125 11/25/07
10276 Application Trace request crashes Service
10277 Support ACCSEC SECMEC values for Encryption with APPC hosts