CONNECTING TO DB2 COMMON SERVER (DB2/2, DB2/6000, AND DB2/NT)
StarSQL 1.05
December 15, 1995
Copyright 1995, StarWare Connectivity Software, Inc.

StarSQL can connect to the DB2 Common Server (DB2/2, DB2/6000, and DB2/NT) 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/6000
WINDOWS NT:  Microsoft SNA Server
 
CONFIGURING DB2 COMMON SERVER:

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.

DB2/NT with Microsoft SNA Server:

If you are using DB2/NT with Microsoft SNA Server, enter the following command
at the prompt in the Command Line Processor within the DB2 for Windows NT 
(Common) Group:

	update database manager configuration authentication client

You can also issue database manager commands outside the Command Line Processor 
interactive mode if you prefix the command with "db2".

ENABLING DRDA SUPPORT FOR DB2/NT:

Set the following environment variable in the System Control Panel:

DB2COMM=APPC

SPECIFYING A TPNAME FOR DB2 COMMON SERVER:

During configuration of DB2 Common Server, specify the tpname that the 
server will accept incoming allocates on over the SNA network.

DB2/2 or DB2/6000:

You should specify the optional service TPName of X'07'6DB, which is the 
default tpname TPName that StarSQL uses.

DB2/NT:

Enter the following command at the prompt in the Command Line Processor within the 
DB2 for Windows NT (Common) Group:

	update database manager configuration tpname DB2

where "DB2" is the name of the DB2 instance that you want to use. You can also 
issue database manager commands outside the Command Line Processor interactive mode 
if you prefix the command with "db2".

SPECIFYING AN ALTERNATE TPNAME FOR DB2 COMMON SERVER:

DB2/2 and DB2/6000:

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.

DB2/NT:

To override the TPName you have specified from a command line prompt, set the 
following environment variable in the System Control Panel:

	DB2SERVICETPINSTANCE=DB2

where "DB2" is the StarSQL default TPName.

NOTE: Whether you use the TPName specified in the database manager command or 
override it with the DB2SERVICETPINSTANCE environment variable, you must enter a 
name in the TPName field of the update database manager command in order to connect 
with DB2/NT. 

CONFIGURING STARSQL FOR DB2 COMMON SERVER: 

When you configure StarSQL for DB2/2, DB2/6000, or DB2/NT, 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.

DB2/NT:

Your UserID must be 8 characters or less in length. Use a UserID with the same
authorities. For example, use "ADMIN" rather than "ADMINISTRATOR".

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  DB2 Common Server 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.