To access a remote server through APPC, you must first have installed and configured communication software for both the client and DB2 server workstations. See "Software Requirements" for the communication protocol requirements for your platform. See "Possible Client-to-DB2 Server 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:
Before you proceed through the configuration steps, enter your value
for the Transaction program name in the following table.
Table 20. APPC Values Required at the Server
|Parameter||Description||Sample Value||Your Value|
|Transaction program name (tpname)||The Transaction program that the server listens on for client requests.||nyserver||
The following steps describe how to configure this protocol on the server. Replace the sample value with your value as recorded on your worksheet.
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:
If you have trouble logging on to the system, see "Logging on to the System".
. INSTHOME/sqllib/db2profile (for Bourne or Korn shell) source INSTHOME/sqllib/db2cshrc (for C shell)where INSTHOME is the home directory of the instance.
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 the following command:
update admin configuration using tpname nyserver db2admin stop db2admin start
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.
Refer to the DB2 Connect Enterprise Edition Quick
Beginnings manual for detailed instructions on how to configure your APPC communications
subsystem to support communications from the Transaction program that you
specified for the server.
[ DB2 List of Books | Search the DB2 Books ]