Quick Beginnings

Configuring APPC on the DB2 Connect Server to Accept Clients

To access a remote server through APPC, you must first have installed and configured communication software for both the client and DB2 Connect server workstations. See "Software Requirements" for the communication protocol requirements for your platform. See "Possible Client-to-DB2 Connect Gateway Connectivity Scenarios" for the supported communication protocols for your particular client and server.

Before completing the steps in this section, be sure that you have completed the instructions in "Setting the DB2COMM Registry Value".

The following steps are required to set up APPC communications:

Identify and record parameter values.
Configure the server:
1. Update the database manager configuration file.
2. Configure the APPC communications subsystem.

Step 1. Identify and Record Parameter Values

Before you proceed through the configuration steps, enter your value for the Transaction program name in the following table.

Table 25. APPC Values Required at the DB2 Connect Server

Parameter Description Sample Value Your Value
Transaction program name (tpname) The Transaction program that the server listens on for client requests. nyserver

Parameter	Description	Sample Value	Your Value
Transaction program name (`tpname`)	The Transaction program that the server listens on for client requests.	`nyserver`

Step 2. Configure the DB2 Connect Server

The following steps describe how to configure this protocol on the server. Replace the sample value with your value as recorded on your worksheet.

A. Update the Database Manager Configuration File

You must update the database manager configuration file with the Transaction program name (tpname).

To update the database manager configuration file, perform the following steps:

Log on to the system as a user with System Administrative (SYSADM) authority.

If you have trouble logging on to the system, see "Logging on to the System".
If you are using UNIX, set up the instance environment and invoke the DB2 command line processor as follows:
1. Run db2profile or db2cshrc as follows:
```
   . INSTHOME/sqllib/db2profile    (for Bourne or Korn shell)
   source INSTHOME/sqllib/db2cshrc (for C shell)
```
  where INSTHOME is the home directory of the instance
2. Start the DB2 command line processor by issuing the db2 command.
Update the database manager configuration file with the server's Transaction program name (tpname) using the following commands in the command line processor:
```
   update dbm cfg using tpname tpname
   db2stop
   db2start
```
For example, if the server's Transaction program name (tpname) is nyserver, use:
```
   update dbm cfg using tpname nyserver
   db2stop
   db2start
```
If you are configuring the Administration Server to use APPC, you must update the admin server configuration file, use:
```
   update admin configuration using tpname nyserver
   db2admin stop
   db2admin start
```

B. Configure the APPC Communications Subsystem

To configure your DB2 server to accept remote clients using APPC, you need to update the APPC communications subsystem to support the Transaction program name (tpname) that the server will use.

If you have not already configured your APPC communication subsystem to support the Transaction program name that you have specified for the DB2 Connect server, use the instructions in Chapter 11. "Configuring Communications to Host and AS/400 Databases Manually" to complete the configuration.
If you have already configured your DB2 Connect server to support inbound APPC client communications, go to Chapter 33. "Configuring Client-to-Server Communications Using the Command Line Processor".

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]