CONNECTING TO DB2 COMMON SERVER (DB2/2 AND DB2/6000)
StarSQL 1.04
September 19, 1995
Copyright 1995, StarWare Inc.

StarSQL can connect to the DB2 Common Server (DB2/2 and DB2/6000) V2.1 and later.

What You Will Need:

You must have installed the appropriate SNA communications software on the host:
 
OS/2:	Communications Manager/2
AIX:	SNA Server/6000Database Manager Authentication
 
Database Manager Authentication (DB2/2 with CM/2 v1.11):

If you are using DB2/2 with Communications Manager/2 v1.11, set the 
authentication parameter in the database manager configuration to 
"authentication=client" instead of "authentication=server". DB2 for OS/2 
is unable to retrieve the password from the APPC FMH-5 header due to a 
Commmunications Manager/2 problem and is therefore unable to 
authenticate the user as required when authentication=server.

Configuring StarSQL for DB2/2 or DB2/6000:

When you configure StarSQL for DB2 or DB2/6000, set the Database Server 
Name to the database name that you want to connect to, rather than to 
the machine name of the server. For example, if you have installed a 
database named 'sample', specify 'sample' for the Database Server Name.

Configuring the TPName for DB2/2 and DB2/6000:

During configuration of DB2/2 and DB2/6000, specify the tpname that the 
server will accept incoming allocates on over the SNA network. You 
should specify the optional service TPName of X'07'6DB, which is the 
default tpname TPName that StarSQL uses.

Specifying an Alternate TPName:

You can override StarSQL's default TPName and specify an alternate 
TPName. Make the following entry:

	RmtTPName=yourtpname

where yourtpname is the name of the program you want to use.
 
For Windows 16-bit applications make this entry in the ODBC.INI file, 
under the the appropriate Database Server Name section.

For Windows NT and Windows 95 32-bit applications, use the Registry Editor 
to modify ODBC.INI.

Connecting StarSQL to DB2 Common Server:

IMPORTANT NOTE: When StarSQL first connects to a host, two SQL packages are 
created in the Package Collection specified in the data source. These 
packages are used for all subsequent uses of the data source. However, when 
StarSQL first connects to DB2 Common Server, only one of the two packages
is created. The second package is created on the second connection.
This is due to a host problem which will be corrected in the future.

Until this problem is fixed, perform a workaround by connecting StarSQL
to DB2 Common Server two times before using StarSQL.