Installation and Configuration Supplement

Configuring APPC on the Client

This section describes how to configure a client workstation to communicate with a server using the APPC communication protocol, and assumes that APPC is functional on the client and server workstations. See Software Requirements for the communication protocol requirements for your platform. See Possible Client-to-Server Connectivity Scenarios for the supported communication protocols for your particular client and server.

You need to ensure that the server that you are attempting to establish communications with supports APPC clients. APPC client communications are supported by the following servers: AIX OS/2 Solaris Windows NT

The following steps are required to set up a client to use APPC communications:

step  1.	Identify and record parameter values.
step  2.	Configure the client: step  a. Update the APPC profiles. step  b. Catalog the APPC or APPN Node. step  c. Catalog the database.
step  3.	Test the connection between the client and server.

Step 1. Identify and Record Parameter Values

As you proceed through the configuration steps, complete the Your Value column in the following table. You can fill in some of the values before you start configuring this protocol.

Before you configure the client workstation, have your DB2 administrator and LAN administrator fill in copies of the worksheet in Table 16 for each DB2 instance to which you want to connect.

After you fill in the Your Value entries, you can use the worksheet to configure APPC communications on the client. During the configuration process, replace the sample values that appear in the configuration instructions with your values from the worksheet, using the boxed numbers (for example, (1)) to relate the configuration instructions to the worksheet values.

Note:

The worksheet and configuration instructions supply suggested or sample values for required configuration parameters. For other parameters, use the communications program's default values. If your network configuration is different from that used in the instructions, consult your Network Administrator for values that are appropriate to your network.

Table 16. Worksheet for Planning Client to Server APPC Connections

Ref.	Name at the Client Workstation	Network or Server Name	Sample Value	Your Value
Network Elements at the Server
(1)	Server name	Local Network Name	SPIFNET
(2)	Partner LU Name	Local LU Name	NYX1GWOA
(3)	PLU Alias		NYX1GW0A
(4)	Partner Node name	Local Control Point Name	NYX1GW
(5)	Database Alias		sample
(6)	Mode Name		IBMRDB
(7)	Connection name (Link name)		LINKSERV
(8)	Remote Network or LAN address	Local Adapter or Destination Address	400009451901
Network Elements at the Client Workstation
(9)	Network ID		SPIFNET
(10)	Local Control Point Name		CLI1GW
(11)	(Local) LU name		CLI1GW0A
(12)	(Local) LU alias		CLI1GW0A
(13)	Local Node or Node ID	ID BLK	071
(14)		ID NUM	27509
(15)	Mode name		IBMRDB
(16)	Symbolic Destination name		DB2CPIC
(17)	(Remote) Transaction program (TP) name		DB2DRDA (Application TP) or X'X'07'6DB' (Service TP)
DB2 Directory Entries (at the client workstation)
(18)	Node name		db2node
(19)	Security		None
(20)	Database name		sample
(21)	Database alias		TOR1

For each server that you are connecting to, fill in a copy of the worksheet as follows:

1. For network ID, determine the network name of both the server and client workstations ((1), (3), and (9)). Usually these values will be the same. (For example, SPIFNET.)

2. For the partner LU name ((2)), determine the Local LU name defined on the server for inbound connections.

3. For partner node name ((4)), determine the local control point name defined on the server.

4. For database alias ((5)), determine the name of the target database

5. For mode name ((6) and (15)), usually the default IBMRDB is sufficient.

6. For remote network address ((8)), determine the controller address or local adapter address of the target server system.

7. Determine the local control point name ((10)) of the client workstation. This is usually the same as the PU name for the system.

8. Determine the local LU name ((11)) to be used by the client workstation.

9. For local LU alias ((12)), you usually use the same value as for the local LU name ((11)).

10. For symbolic destination name ((16)), choose a suitable value.

11. For (remote) transaction program (TP) name ((17)), determine the transaction program name defined on the server for your APPC connections.

12. Leave the other items blank for now ((18) to (21)).

Step 2. Update the APPC Profiles

Use the completed worksheet in Table 16 to configure DB2 client APPC communications for access to a remote DB2 Connect or DB2 Universal Database server.

Go to the sections that describe how to configure APPC communications on the platforms that are present in your network: Configuring IBM eNetwork Communications Server for OS/2 Configuring IBM eNetwork Personal Communications for Windows 9x and Windows NT Configuring IBM eNetwork Communications Server for Windows NT Configuring IBM eNetwork Communications Server for Windows NT SNA API Client Configuring Microsoft SNA Server for Windows NT Configuring Microsoft SNA Client Configuring IBM eNetwork Communications Server for AIX Configuring Bull SNA for AIX Configuring SNAPlus2 for HP-UX Configuring SunLink SNA for Solaris

Configuring IBM eNetwork Communications Server for OS/2

This section describes how to manually configure IBM eNetwork Communications Server V5 for OS/2 (CS/2 V5) on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC.

Before you begin, ensure that your workstation has CS/2 V5 or later installed.

The steps in this section describe how to use IBM eNetwork Communications Server for OS/2 Version 5. If you have Communications Manager for OS/2 V.1.x, the steps you perform are similar, but the interface and menu names are different.

For more information on setting up your environment, refer to the online help supplied with CS/2, or to the following publications:

• Connectivity Supplement

• DRDA Connectivity Guide

The following assumptions have been made:

• The basic installation of the IBM eNetwork Communication Server V5 for OS/2 package has already been completed.

• The DB2 client for OS/2 has been installed.

These instructions describe how to create new profiles within a new configuration. If you are modifying an existing configuration, you may need to delete some profiles before you can verify the configuration.

To configure your system, perform the following steps:

step  1.	Start a new configuration Double-click on the IBM eNetwork Communications Server icon. Double-click on the Communications Manager Setup icon. In the Communications Manager Setup window, click on the Setup push button. In the Open Configuration window, provide a name for a new configuration file and click on OK. The Communications Manager Configuration Definition window opens.
step  2.	Configure the protocol Select the Commonly used definitions radio button. In the Communications Definitions box, select the protocol that you want to use. These assume that you are intructions using APPC APIs over Token-Ring. Click on the Configure push button. The APPC APIs over Token-Ring window opens. Enter your Network ID ((9)) in the Network ID field. Enter your local Control Point name ((10)) in the Control point name field. Click on the End node push button that your network administrator advises you to use. You can select either the End node - to a network node server radio button or the End node - no network node server radio button. A network node server is used when many users are routed through the same connection. This example assumes no network node server is used. Click on the Advanced push button. The Communications Manager Profile List window opens. Subsequent steps begin from this window. You will return to this window when each of the following steps are completed.
step  3.	Prepare a LAN DLC profile On the Profile List window, select the DLC - Token ring or other LAN Types Adapter Parameters option and click on the Configure push button. The Token Ring or Other Lan Types Adapter Parameters window opens. Enter your Network ID ((9)) in the Network ID field. Click on OK.
step  4.	Update the SNA local node characteristics On the Profile List window, select the SNA local node characteristics option and click on the Configure push button. The Local Node Characteristic window opens. Enter your Network ID ((9)) in the Network ID field. The Local node name was probably set when CS/2 was installed. If you are not sure, consult your local network administrator. Enter your Node ID ((13), (14)) in the Local node ID (hex) field. The first part should be filled in for you already when you display the profile. You only need to complete the second part. Click on OK.
step  5.	Prepare the SNA Connection Profiles On the Profile List window, select the SNA Connections option and click on the Configure push button. The Connection List window opens. From the Partner Type window, select either the To peer node radio button (normally used for OS/400 connections), or the To host radio button (normally used for OS/390, MVS, VSE, and VM connections), and click on the Create push button. The Adapter List window opens. Select the Token-ring, or other LAN types Adapter Type, and specify the same adapter number that you specified previously in the DLC profile. Click on the Continue push button. The Connection to a Peer Node window or the Connection to a Host window opens.
step  6.	Configure the connection in the Connection to a Peer Node or Connection to Host window Enter the Link name ((7)) in the Link name field. In the Connection window, click on the Additional parameters push button. The Additional Connection Parameters window opens. Enter your local Control Point name ((10)) in the Local PU name field. Clear the Backup Link check box. Enter your Node ID ((13) and (14)) in the Node ID fields. Click on OK. Enter the remote LAN address ((8)) in the LAN destination address field. Enter the Network ID ((1)) of the remote system in the Partner network ID field. Enter the Partner Node name ((4)) in the Partner node name field. Click on the Define Partner LUs push button. The Partner LU window opens.
step  7.	Create a partner LUs profile Enter the Network ID ((3)) of the remote system in the Network ID field. Enter the Partner LU name ((2)) in the LU name and Alias fields. Click on the Add push button to add the partner LU profile to the connection profile. Click on OK. Click on the Additional Parameters push button. The Additional Connection Parameters window opens. Verify that the Multiple PU Parameters fields are filled in. This value is the Local Node ID in hex ((13) and (14)). Click on OK to return to the Connection window. Click on OK to return to the Connections List window. Click on the Close push button to return to the Profile List window.
step  8.	Set SNA features On the Profile List window, select the SNA features option and click on the Configure push button. The SNA Features List window opens. Subsequent steps begin from this window.
step  9.	Prepare a local LU profile If the DB2 client workstation is defined as an independent LU, prepare a Local LU Profile by performing the following steps: On the SNA Features List window, select Local LUs->Create from the action menu bar. Enter your Local LU name ((11)) in the LU name field. Enter your Local LU alias ((13)) in the alias field. Select the Independent LU radio button in the NAU address box. Click on OK. To use this local LU when the client workstation starts the APPC connection, select the Use this local LU as your default local LU alias check box. By default, all APPC connections that are started from this client workstation will use this local LU.
step 10.	Prepare a mode definition From the SNA Features List box, select the Modes option and click on the Create push button. The Mode Definition window opens. Enter your Mode name ((6), (15)) in the mode name field. For the other fields, you can either specify values that match the mode profile defined on your server system, or tune the parameters. Click on OK to finish the creation of the mode and to return to the SNA Features List panel.
step 11.	Create the CPIC side information From the SNA Features List box, select the CPI Communications Side Information option and click the Create push button. The CPI Communications Side Information window opens. Enter the Symbolic destination name ((16)) in the Symbolic destination name field. Select the Alias radio button. Click on the Alias drop down box and select your Partner LU alias ((12)). Enter the remote Transaction Program (TP) name ((17)) in the Partner TP field. Select the None radio button in the Security type group. This does not mean that you will have no security. You will specify the security type later when you update the DB2 directories. Enter the mode name ((6)) in the Mode name field. Click on OK to save the CPI side information profile and return to the SNA Features List panel. Click on Close to return to the Communications Server Profile List panel.
step 12.	Save the configuration Click on the Close button to return to the Comminucation Server Configuration Definition window. Click on the Close button to automatically verify and save the new configuration file, and leave the configuration windows. Stop and start the Communications Server by clicking on the Stop Communications Normally button, then on the Start Communications button.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM eNetwork Personal Communications for Windows 9x and Windows NT

This section describes how to configure IBM Personal Communications for Windows 95, Windows 98 and Windows NT on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC.

Before you begin, ensure that the IBM Personal Communications for Windows NT or Windows 9x you installed meets the following requirements:

__  1.

It is Version 4.2 or higher

__  2.

The IBM Personal Communications IEEE 802.2 LAN interface or LLC2 driver is installed. The LLC2 driver is installed from the IBM Communications Server installation directory. To verify this, perform the following steps: Click on the Start push button and select Settings->Control Panel. Double-click on the Network icon. Select the Protocols tab. The IBM LLC2 Protocol must be one of the protocols listed. If it is not, you need to install this protocol from your IBM Personal Communications for Windows 9x or Windows NT software media. Refer to the documentation supplied with IBM Personal Communications for instructions.

The following assumptions are made:

• The basic installation of the IBM Personal Communication package has already been completed, with the requirements listed above met.

• The DB2 client has been installed.

To start IBM Personal Communications, perform the following steps:

step  1.	Click on the Start push button and select Programs->IBM Communications Server->SNA Node Configuration. The IBM Personal Communications SNA Node Configuration window opens.
step  2.	Select File->New from the menu bar. The Define the Node window opens. Subsequent steps will begin from this window.

To configure APPC communications, perform the following steps:

step  1.	Configure the Node In the Configuration options box, select the Configure Node option and click on the New push button. The Define the Node window opens. In the Fully qualified CP name fields, type in the network name ((9)) and the local control point name ((10)) Optionally, in the CP alias field, type in a CP alias. If you leave this blank the local control point name will be used. In the Local Node ID fields, type in the block ID ((13)) and the physical unit ID ((14)). Click on OK.
step  2.	Configure the device In the Configuration options box, select the Configure devices option and click on the New push button. Select the appropriate DLC from DLCs field. These instructions in this section use the LAN DLC. Click on the New push button. The appropriate window opens with default values displayed. In our example, the Define a LAN device window opens. Click on OK to accept the default values.
step  3.	Configure Connections In the Configuration options box, the select Configure connections option. Ensure that the LAN option is selected in the DLCs field. Click on the New push button. The Define a LAN connection window opens. On the Basic tab: In the Link station name field, type in the link name ((7)). In the Destination address field, type in the remote LAN address ((8)). On the Adjacent Node tab: In the Adjacent CP name fields, type in the network ID ((3)) and the Partner node name ((4)). In the Adjacent CP type field, select Back-level LEN. Ensure that TG number is set to 0 (the default). Click on OK.
step  4.	Configure Partner LU 6.2 In the Configuration options box, select the Configure partner LU option and click on the New push button. The Define a partner LU 6.2 window opens. In the Partner LU name fields, type in the network ID ((3)) and the partner LU name ((2)). In the Partner LU alias field, type in the partner LU name ((2)). In the Fully-qualified CP name fields, type in the network ID ((3)) and the control point name ((4)). Accept the defaults in the Advanced tab. Click on OK.
step  5.	Configure Modes In the Configuration options box, select the Configure modes option and click on the New push button. The Define a mode window opens. Enter your Mode name ((15)) in the Mode name field of the Basic tab. Select the Advanced tab. Select the #CONNECT option from the Class of Service Name field. Click on OK.
step  6.	Configure Local LU 6.2 In the Configuration options box, select the Configure local LU 6.2 option and click on the New push button. The Define a local LU 6.2 window opens. Enter your Local LU name ((11)) in the Local LU name field. Type in a value for the LU session limit field. The default, 0, specifies the maximum allowed value. Accept the defaults for the other fields. Click on OK.
step  7.	Configure CPI-C Side Information In the Configuration options box, select the Configure CPI-C side information option and click on the New push button. The Define CPI-C side information window opens. In the Symbolic destination name field, type in the symbolic destination name ((16)). In the Mode name field, type in the mode name ((15)). In the Partner LU Name fields, type the Network ID ((3)) in the first field, and the Partner LU Name ((2)) in the second field. Specify the TP name. In the TP name field: To specify a application TP, in the TP name field, type in the name of the application TP ((17)), and ensure that the Service TP check box is not selected. To specify a service TP, in the TP name field, type in the name of the service TP ((17)), and ensure that the Service TP check box is selected. Accept the defaults for the other fields. Click on OK.
step  8.	Save the Configuration Select File->Save As from the menu bar. The Save As window opens. Type in a file name, for example ny3.acg. Click on OK. In the dialog box that opens, you are asked if you want this configuration to be the default. Click on the Yes push button.
step  9.	Update the environment IBM Personal Communications uses an environment variable called appcllu to set the default Local LU used for APPC communications. You may set this variable on a per-session basis by opening a command window and enter the set appcllu=local_lu_name command, where local_lu_name is the name of the local LU you want to use. However, you will probably find it more convenient to permanently set the variable. To permanently set the variable in Windows NT, perform the following steps: Click on the Start button and select Settings->Control Panel. Double-click on the System icon. The System Properties window opens. Select the Environment tab. Type appcllu in the Variable field. Type your local LU name ((11)) in the Value field. Click on the Set push button to accept the changes. Click on OK to exit the System Properties window. The environment variable will now remain set for future sessions.
step 10.	Start SNA Node Operations Click on the Start button and select Programs->IBM Personal Communications->Administrative and PD Aids->SNA Node Operations. The Personal Communications SNA Node Operations window opens. From the menu bar, select Operations->Start Node. In the window that opens, select the configuration file you saved in the previous step (for example, ny3.acg) and click on OK.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM eNetwork Communications Server for Windows NT

This section describes how to configure IBM eNetwork Communications Server for Windows NT (CS/NT) on a DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server.

Before you begin, ensure that the IBM eNetwork Communications Server for Windows NT (CS/NT) you installed meets the following requirements:

__  1.	It is Version 5.0 or higher if you are planning to update multiple databases within the same transaction. If you are planning to use 2-phase commit, then Version 5.01 of CS/NT is required
__  2.	The IBM Communications Server IEEE 802.2 LAN interface or LLC2 driver was installed. The LLC2 driver was installed from the CS/NT installation directory. During installation CS/NT asks if you want to install LLC2. If you are not sure whether LLC2 was installed with your copy of CS/NT, you can find out as follows: Click on the Start push button and select Settings->Control Panel. Double-click on the Network icon. On the Network window, select the Protocols tab. The IBM LLC2 Protocol must be one of the protocols listed. If it is not, you need to install this protocol from your IBM Communications Server for Windows NT software media. Refer to documentation supplied with CS/NT for instructions.
__  3.	The APAR fixes JR11529 and JR11170 were applied. These fixes are required to enable cancelling of queries in progress by using Ctrl-BREAK or issuing the SQLCancel ODBC/CLI call.

To start IBM eNetwork Communications Server, perform the following steps:

step  1.	Click Start and select Programs->IBM Communications Server-> SNA Node Configuration. The IBM Communications Server SNA Node Configuration window opens.
step  2.	Select File->New->Advanced from the menu bar. The Configuration options window opens. Subsequent steps will begin from this window.

To configure IBM eNetwork Personal Server for APPC communications, perform the following steps:

step  1.	Configure Node In the Configuration options field, select the Configure Node option and click on the New push button. The Define the Node window opens. In the Fully qualified CP name fields, type in the network name ((9)) and the local control point name ((10)). Optionally, in the CP alias field, type in a CP alias. If you leave this blank the local control point name will be used. In the Local Node ID fields, type in the block ID ((13)) and the physical unit ID ((14)). Select the appropriate node type. The default is to select the End Node radio button. Click on OK.
step  2.	Configure the device In the Configuration options box, select the Configure devices option and click on the New push button. The appropriate window opens with default values displayed. Select the appropriate DLC from DLCs field. These instructions in this section asssume that you are using the LAN DLC. Click on OK to accept the default values.
step  3.	Configure Connections In the Configuration options box, select the Configure connections option and click on the New push button. Ensure that in the DLCs field, the LAN option is selected. Click on the New button. The Define a LAN connection window opens. On the Basic tab: In the Link station name field, type in the link name ((7)). In the Destination address field, type in the remote LAN address ((8)). On the Security tab: In the Adjacent CP name fields, type in the network ID ((3)) and the Control Point name ((4)). In the Adjacent CP type field, select the appropriate CP type (eg. Back-level LEN). Ensure that TG number is set to 0 (the default). Click on OK.
step  4.	Configure Partner LU 6.2 In the Configuration options box, select the Configure partner LU option and click on the New push button. The Define a partner LU 6.2 window opens. In the Partner LU name fields, type in the network ID ((3)) and the partner LU name ((2)). In the Partner LU alias field, type in the partner LU name ((2)). If you are configuring Communications Server for SNA Clients, in the Fully-qualified CP name fields, type in the network ID ((3)) and the adjacent control point name ((4)). Leave the other fields blank. Click on OK.
step  5.	Configure Modes In the Configuration options box, select the Configure modes option and click on the New push button. The Define a mode window opens. In the Mode name field, type in the mode name ((6)). Select the Advanced tab and ensure that the Class of Service Name is set to #CONNECT. Accept the defaults for the other fields. Click on OK.
step  6.	Configure Local LU 6.2 In the Configuration options box, select the Configure local LU 6.2 option and click on the New push button. The Define a local LU 6.2 window opens. In the Local LU name field, type in the local LU name ((11)). Type in a value for the LU session limit field. The default, 0, specifies the maximum allowed value. Accept the defaults for the other fields. Click on OK.
step  7.	Configure CPI-C Side Information In the Configuration options box, select the Configure CPI-C side information option and click on the New push button. The Define CPI-C side information window opens. In the Symbolic destination name field, type in the symbolic destination name ((16)). In the Mode name field, type in the mode name ((15)). Select the Use Partner LU alias radio button and select a Partner LU alias. Specify the TP name. In the TP name field: To specify a application TP, in the TP name field, type in the name of the application TP ((17)), and ensure that the Service TP check box is not selected. To specify a service TP, in the TP name field, type in the name of the service TP ((17)), and ensure that the Service TP check box is selected Accept the defaults for the other fields. Click on OK.
step  8.	Save the Configuration Select File->Save as from the menu bar. The Save As window opens. Type in a file name, for example ny3.acg Click on OK. In the window that opens you are asked if you want this configuration to be the default. Click on the Yes push button.
step  9.	Update the Environment CS/NT uses an environment variable called appcllu to set the default APPC Local LU. You may set this variable on a per-session basis by opening a command window and typing set appcllu=local_lu_name command, where local_lu_name is the Local LU name; however, you will probably find it more convenient to permanently set the variable. In order to permanently set the variable in Windows NT, perform the following steps: step  a. Click the Start push button and select Settings->Control Panel. step  b. Double-click on the System icon. The System Properties window opens. step  c. Select the Environment tab. step  d. Type appcllu in the Variable field, and type your local LU name ((11)) in the Value field. step  e. Click on Set push button to accept the changes step  f. Click on OK. The environment variable will now remain set for future sessions.
step 10.	Start SNA Node Operations To start SNA node operations on your machine, perform the following steps: step  a. Click on the Start push button and select Programs->IBM Communications Server->SNA Node Operations. The SNA Node Operations window opens. step  b. Select Operations->Start Node from the menu bar. In the dialog box that opens, select the configuration file you saved at the end of Step 2 (in our example, ny3.acg). step  c. Click OK. SNA node operations will now begin running.
step 11.	Registering Communications Server as a Windows NT Service To automatically start Communications Server when the machine is started, you can register it as a Windows NT Service. To register Communications Server as an NT service execute one of the following commands: csstart -a (to register Communications Server with default configuration) or: csstart -a c:\ibmcs\private\your.acg where c:\ibmcs\private\your.acg represents the fully qualified name of the non-default Communications Server configuration file you wish to use. Whenever your machine is booted in the future, Communications Server will be started automatically with the required configuration file.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM eNetwork Communications Server for Windows NT SNA API Client

Read this section if you have a Windows NT workstation that has IBM eNetwork Communications Server for Windows NT SNA API Client Version 5.0 or higher installed and you want to connect to an IBM eNetwork Communications Server for Windows NT server.

The Communications Server for Windows NT server and its SNA API client act as a split client. This configuration requires that you have an APPC-enabled application (such as DB2 client) running on the SNA API client workstation.

The instructions in this section use a Windows NT client. The instructions for other supported operating systems are similar; refer to your Communications Server for Windows NT documentation for more information.

To configure the Windows NT SNA API client for APPC communications, perform the following steps:

step  1.	Create a user account for the SNA API client on the Communications Server for Windows NT server Click on the Start button and select Programs->Administrative Tools (Common)->User Manager. The User Manager window opens. Select Users->New User from the menu bar. The New User window opens. Fill in the fields for the new SNA client user accout. For more information, refer to the Windows NT online help. Ensure that this user account is a member of the Administrators, IBMCSADMIN, and IBMCSAPI groups. To add this user account to these groups, perform the following steps: Click on the Groups push button Select a group from the Not member of box and click on the <- Add push button. Repeat this step for each group that your user account must belong to. Click on OK. Click on the Add push button.
step  2.	Start the configuration GUI for the IBM eNetwork CS/NT SNA API Client. Click on the Start button and select Programs->IBM Communications Server SNA Client->Configuration. The CS/NT SNA Client Configuration window opens.
step  3.	Configure Global Data In the Configuration options box, select the Configure Global Data option and click on the New push button. The Define Global Data window opens. Enter the user name for the SNA API client in the User name field. Enter the password for the user account in the Password and Confirm Password fields. Click on OK.
step  4.	Configure APPC Server List In the Configuration options box, select the Configure APPC Server List option and click on the New push button. The Define APPC Server list window opens. Type in the IP address of the server (for example, 123.123.123.123). Click on OK.
step  5.	Configure CPI-C Side Information In the Configuration options box, select the Configure CPI-C side information option and click on the New push button. The Define CPI-C side information window opens. Enter the symbolic destination name ((16)) in the Symbolic destination name field. Enter your Local LU alias ((12)) in the Local LU alias field. Enter the mode name ((15)) in the Mode name field. Enter the transaction program name ((17)) in the TP name field. Select the For SNA API Client use check box for this transaction program. Enter the network ID ((3)) and partner LU name ((2)) in the Partner LU name field. Click on OK.
step  6.	Save the Configuration Select File->Save As from the menu bar. The Save As window opens. Type in a file name and click on Save push button.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring Microsoft SNA Server for Windows NT

This section describes how to configure Microsoft SNA Server Version 4.0 for Windows NT on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC. Although Microsoft SNA Server will run on Windows NT 4.0 Workstation, Windows NT 4.0 Server is recommended.

For instructions on how to configure Microsoft SNA Client for Windows NT, go to Configuring Microsoft SNA Client.

You can define the properties of your SNA connections in the Microsoft SNA Server Manager (Server Manager). The Server Manager uses an interface similar to that of the Windows NT Explorer. There are two panes in the main window of the Server Manager. All the configuration options we will be using can be accessed by right-clicking on objects in the left-hand pane of the window. Every object has a context menu that you can access by right-clicking on the object.

To configure APPC communications for use by the DB2 client using Microsoft SNA Server Manager, perform the following steps:

step  1.	Start the Server Manager by clicking on the Start button and selecting Programs->Microsoft SNA Server->Manager. The Microsoft SNA Server Manager window opens.
step  2.	Define the control point name Open the Servers folder in the left pane of the Server Manager by clicking on the [+] sign beside the Servers folder. Right-click on the SNA Service folder and select the Properties option. The Properties window opens. Enter the correct NETID ((9)) and Control Point Name ((10)) in the corresponding fields. Click on OK.
step  3.	Define the link service (802.2) Right-click on the SNA Server icon and Select Insert->Link Service from the menu bar. The Insert Link Service window opens. Select DLC 802.2 Link Service. Click on the Add push button. Click on the Finish push button.
step  4.	Define the connection properties Right-click on the SNA Service icon and select Insert->Connection->802.2 from the menu bar. The Connection Properties window opens. Enter a connection name ((7)) in the Name field under the General tab. Click on the Link Service drop-down box and select the SnaDlc1 option. Select the Remote End radio button from the Host System group. Select the Both Directions radio button from the Allowed Directions group. Select the On Server Startup radio button from the Activation group. Select the Address tab. Fill in the Remote Network Address field ((8)). Accept the default numbers in the other fields. Select the System Identification tab. Enter the following information: For the Local Node Name, add the Network ID ((9)), the Local PU Name ((10)), and the Local Node ID (( 13) plus (14)). Accept the XID Type default. For the Remote Node Name, add the NETID ((1)) and the Control Point Name ((4)). Accept the other defaults Click on OK.
step  5.	Define a local LU Right-click on the SNA Service icon and select the Insert->APPC->Local Lu option. The Local APPC LU Properties window opens. Enter the following information: The LU Alias ((12)). The NETID ((9)). The LU Name ((11)). Select the Advanced tab. Select the Member of Default Outgoing Local APPC LU Pool option. Accept the other defaults. Click on OK.
step  6.	Define a remote LU Right-click on the SNA Services icon and select the Insert->APPC->Remote LUoption. The Remote APPC Lu Properties window opens. Click on the Connection drop down box and select the appropriate connection name ((7)). Enter the partner LU name ((2)) in the LU Alias field. Enter the Network ID ((1)) in the Network Name field. The other fields will be filled in by the program. If your LU alias is not the same as your LU Name, make sure you specify the LU Name in the appropriate field. The program will fill it in automatically, but it will be incorrect if the alias and the name are not the same.
step  7.	Click on OK.

Define a mode

1. Right-click on the APPC Modes folder and select the Insert->APPC->Mode Definition option. The APPC Mode Properties window opens.

2. Enter the Mode name in the Mode Name field ((6)).

3. Select the Limits tab.

4. Enter appropriate numbers for the Parallel Session Limit and Minimum Contention Winner Limitfields. Your Server-Side or LAN administrator should be able to supply you with the numbers if you do not know which limits to use.

5. Accept the other defaults, and click on OK.

Define the CPIC name properties

1. Right-click on CPIC Symbolic Name folder icon and select the Insert->APPC->CPIC Symbolic Name option. The CPIC Name Properties window opens.

2. Enter the Symbolic Destination Name ((16)) in the Name field.

3. Click on the Mode Name drop down box and select a mode name, for example, IBMRDB ((15)).

4. Select the Partner Information tab.

5. Select the SNA Service TP (in hex) radio button, in the Partner TP Name box, and enter the Service TP name ((17)), or select the Application TP radio button and enter the Application TP name ((17)).

6. In the Partner Lu Name box, select the Fully Qualified radio button.

7. Enter the fully-qualified Partner LU Name ((1) and (2)).

8. Click on OK.

Save the configuration

1. Select File->Save from the menu bar of the Server Manager window. The Save File window opens.

2. Type a unique name for your configuration into the File Name field.

3. Click on the Save push button.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring Microsoft SNA Client

This section provides step-by-step instructions for setting up communications between your Microsoft SNA Client workstation and a Windows NT workstation that has Microsoft SNA Server V4.0 (or later) installed.

For instructions on how to configure Microsoft SNA Server Version 4.0 for Windows NT on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC, go to Configuring Microsoft SNA Server for Windows NT.

The rest of this section assumes:

1. The Microsoft SNA Server has already been configured for APPC communications to connect to a DB2 Connect or DB2 Universal Database server using APPC. Refer to the Microsoft SNA Server documentation for more information.

2. Microsoft SNA Client Version 2.11 is not already installed on your client workstation.

To configure the Microsoft SNA client, perform the following steps:

Step 1. Obtain Required Information

For your Microsoft SNA client software to function properly you must have access to a properly-configured Microsoft SNA Server. Request that your SNA Server administrator:

step  1.	Obtain the proper license for you to use Microsoft SNA Client on your workstation.
step  2.	Define a user ID and password for you on the SNA Server domain.
step  3.	Define connections to server databases that you need to access, as described in Configuring Microsoft SNA Server for Windows NT.
step  4.	Provide you with the symbolic destination name ((16)), database name ((5)), and user account to use for each database connection defined in the previous step. If you plan to change server passwords, the SNA administrator will also need to provide you with symbolic destination names for password management tasks on each server.
step  5.	Provide you with the Microsoft SNA Server domain name and the protocol used for communicating with the SNA server (TCP/IP, NetBEUI, IPX/SPX).

Step 2. Install the Microsoft SNA Client on the DB2 Client Workstation

Obtain the Microsoft SNA Client software, and follow the instructions provided with it to start the installation program. When you reach the Optional Components window, deselect the Install ODBC/DRDA driver check box.

Step 3. Install the DB2 client

step  1.	Install the DB2 client.
step  2.	Click on the Start button and select Programs->DB2 for Windows NT->Client Configuration Assistant.
step  3.	You need to provide the following information: __  a. The Symbolic destination name ((16)) defined at the Microsoft SNA Server for the Partner LU ((2)) of the target database server. __  b. The real database name ((5)).

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM eNetwork Communications Server for AIX

This section describes how to configure IBM eNetwork Communication Server V5.0.2.5 for AIX on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC. IBM eNetwork Communication Server for AIX is the only SNA product supported for DB2 Connect running on RS/6000 machines.

Before you begin, ensure that your workstation has IBM eNetwork Communication Server V5.0.2.5 for AIX (CS/AIX) installed. If you need further information in order to configure your SNA environment, refer to the online help provided with CS/AIX.

The following assumptions are made:

• The basic installation of the IBM eNetwork Communication Server V5 for AIX package has already been completed.

• The DB2 client has been installed.

• The user is logged on to the system as a user with root authority.

To configure CS/AIX for use by a DB2 client, log on to the system as a user with root authority and use either the /usr/bin/snaadmin tool or the /usr/bin/X11/xsnaadmin tool. Information about these programs can be found in the system documentation. To use the xsnaadmin program to configure CS/AIX, perform the following steps:

step  1.	Enter the xsnaadmin command. The Node window for the server opens.
step  2.	Define a Node Select Services->Configure Node Parameters from the menu bar. The Node Parameters window opens. Click on the APPN support drop down box and select the End node option. Enter your Network ID and the Local PU Name ((9) and (10)) in the Control point name fields. Enter Local PU Name ((10)) in the Control point alias field. Enter your Node ID ((13) and (14)) in the Node ID fields. Click on OK.
step  3.	Define a port Select the Connectivity and Dependent LUs window. Click on the Add push button. The Add to Node window opens. Select the Port using radio button. Click on the Port using drop down box and select the appropriate port type. For our example, we will select the Token ring card option. Click on OK. The Port window for the chosen port type opens. Enter a name for the port in the SNA port name field. Select the Initially active check box. Select the Define on connection network check box. Enter your SNA Network Name ((9)) in the first part of the CN name field. Enter the Control Point Name ((10)) associated with your AIX computer in the second part of the CN name field. Click on OK. The Port window closes and a new port appears in the Connectivity and Dependent LUs window.
step  4.	Define a link station In the Connectivity and Dependent LUs window, select the port you defined in the previous step. Click on the Add push button. The Add to Node window opens. Select the Add a link station to port radio push button. Click on OK. The Token ring link station window opens. Enter a name for the link in the Name field. Click on the Activation drop down box and select the On demand option Select the Independent only radio button in the LU traffic box. In the Independent LU traffic group box: Enter the Network ID ((3)) and the Partner LU Name ((2)) in the Remote Node fields. Click on the Remote node type drop down box and select the type of node that applies to your network. In the Contact information box, enter the SNA Destination Address ((8)) assigned to the DB2 server in the Mac address field. Click on OK. The Link Station window is closed and a new link station appears as a child of the port in the Connectivity and Dependent LUs window.
step  5.	Define a local LU Select the Independent local LUs window. Click on the Add push button. The Local LU window opens. Enter your independent local LU Name ((11)) in the LU name field. Enter the local LU alias in the LU alias field ((12)). Click on OK. The new LU appears in the Independent local LUs window.
step  6.	Define a partner LU over the link station Select Services->APPC->New Partner LUs->Partner LU on link station from the menu bar. The Partner LU on link station window opens. Enter the name for the Local LU ((11)) you defined previously in the LU name field. Enter the name for the Link station you defined previously in the LS name field. Enter the name of the Partner LU ((1)+(2)) you want to connect to in the Partner LU name fields. Click on OK. The Partner LU opens in the Independent Local LUs window of the Local LU that was created in the previous step.
step  7.	Define an alias for the partner LU Select the Remote Sytems window. Click on the Add push button. The Add to node window opens. Select the Define partner LU alias radio push button. Click on OK. The Partner LU window opens. Enter an alias for the partner LU in the Alias field. Enter the same value in the Uninterpreted name field. Click on OK.
step  8.	Define a mode Select Services->APPC->Modes from the menu bar. The Modes window opens. Click on the New push button. The Mode window opens. Enter a mode name ((15)) in the Name field. The configuration values below are suggested for the following fields: Initial Session limits: 20 Maximum Session limits: 32767 Min con. winner sessions: 10 Min con. loser sessions: 10 Auto-activated session: 4 Initial Receive pacing window: 8 These values are suggested because they are known to work. You may need to tailor these values so that they are optimized for your particular environment. Click on OK. The new mode appears in the Modes window. Click on Done.
step  9.	Define the CPI-C destination name Select Services->APPC->CPI-C from the menu bar. The CPI-C destination names window opens. Click on the New push button. The CPI-C destination window opens. Enter the Symbolic Destination Name ((16)) you want to associate with the server's database in the Name field. In the Partner TP box: Select the Service TP (hex) option, and enter the hexadecimal TP number ((17)) or: Select the Application TP field and enter the application TP name. ((17)) In the Partner LU and mode box: Select the Use PLU Alias field and enter the Partner LU Alias ((2)) you created in a previous step. Enter the Mode name ((15)) for the mode you created in a previous step in the Mode field. Select the type of conversation level security you want to use in the Security group box. This is usually None. Click on OK. The new destination name appears in the Destination names window. Click on the Done push button.
step 10.	Test the APPC connection Start the SNA subsystem by entering the /usr/bin/sna start command. You can enter the /usr/bin/sna stop command to stop the SNA subsystem first, if required. Start the SNA administration program. You can enter either the /usr/bin/snaadmin command or the /usr/bin/X11/xsnaadmin command. Start the subsystem node. Select the appropriate node icon in the push button bar, and click on the Start push button. Start the link station. Select the link station you defined previously in the Connectivity and Dependent LUs window, and click on the Start push button. Start the session. Select the LU you defined previously in the Independent Local LUs window, and click on the Start push button. A session activation window opens. Select or enter the Partner LU and Mode desired Click on OK.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring Bull SNA for AIX

This section describes how to configure Bull DPX/20 SNA/20 Server on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC. If Bull DPX/20 SNA/20 Server is installed prior to installing the DB2 client, the client use Bull SNA. Otherwise, you need to configure DB2 Connect to work with IBM eNetwork Communications Server V5.0.2.5 for AIX. See Configuring IBM eNetwork Communications Server for AIX for more information.

To determine if Bull SNA is installed on your AIX 4.2 (or later) system, enter the following command:

  lslpp -l express.exsrv+dsk

If Bull SNA is installed, you will see output similar to the following:

    Fileset                      Level  State      Description
    ----------------------------------------------------------------------
  Path: /usr/lib/objrepos
    express.exsrv+dsk          2.1.3.0  COMMITTED  EXPRESS SNA Server and
                                                   Integrated Desktop

If you install Bull SNA after installing the DB2 client and you want the client to use Bull SNA instead of IBM eNetwork Communications Server for AIX, log on to the system as a user with root authority and enter the following command:

   /usr/lpp/db2_06_01/cfg/db2cfgos

If you want to install the Bull DPX/20 SNA/20 Server, then you must have the following software:

__  1.	AIX V4.2
__  2.	Express SNA Server V2.1.3

For more information on setting up your SNA environment, refer to the Bull DPX/20 SNA/20 Server Configuration Guide.

DB2 Connect, when used with the Bull SNA server, cannot have inbound APPC connections from remote clients. The only APPC connections it can have are outbound APPC connections to the host.

To configure Bull SNA for use by DB2 Connect, enter the express command to configure the following SNA parameters:

     Config         Express           Default configuration for EXPRESS
      Node          CLI1              SPIFNET.CLI1 (HOSTNAME=CLI1)
       Indep. LUs   6.2 LUs Using All Stations
         LU         CLI1GW            Control Point LU
       Link         tok0.00001        Link (tok0)
        Station     SERV              To SERV from CLI1
         LU         CLI1GW0A          To SERV from CLI1
          LU Pair   NYX1GW0A          To SERV from CLI1
           Mode     IBMRDB            IBMRDB

Use default values for fields not listed.

The following example illustrates the sample configuration:

   Defining hardware:
 
   System (hostname) = CLI1
   Adapter and Port  = CLI1.tok0
     MAC Address     = 400011529778
 
   Defining SNA node:
 
   Name          = CLI1
   Description   = SPIFNET.CLI1 (HOSTNAME=CLI1)
   Network ID    = SPIFNET
   Control Point = CLI1GW
   XID Block     = 071
   XID ID        = 27509
 
   Defining token ring link:
 
   Name            = tok0.00001
   Description     = Link (tok0)
   Connection Network name
     Network ID    = SPIFNET
     Control Point = NYX1GW
 
   Defining token ring station:
 
   Name               = SERV
   Description        = To SERV from CLI1
   Remote MAC address = 400009451901
   Remote Node name
     Network ID       = SPIFNET
     Control Point    = NYX1GW
 
   Defining Local LU 6.2:
 
   Name        = CLI1GW0A
   Description = To SERV from CLI1
   Network ID  = SPIFNET
   LU name     = CLI1GW0A
 
   Defining Remote LU 6.2:
 
   Name                 = NYX1GW0A
   Description          = To SERV from NYX1
   Network ID           = SPIFNET
   LU name              = NYX1GW0A
   Remote Network ID    = SPIFNET
   Remote Control Point = NYX1GW
   Uninterpreted Name   = NYX1GW
 
   Defining Mode:
 
   Name             = IBMRDB
   Description      = IBMRDB
   Class of service = #CONNECT
 
   Defining Symbolic Destination Info:
 
   Name        = DB2CPIC
   Description = To SERV from NYX1
   Partner LU  = SPIFNET.NYX1GWOA
   Mode        = IBMRDB
   Local LU    = CLI1GW0A
   Partner TP  = DB2DRDA

After you have configured these SNA parameters, you must stop and start the SNA server. To do this, perform the following steps:

step  1.	Log on to the system as a user with root authority.
step  2.	Make sure your PATH contains the $express/bin (/usr/lpp/express/bin) entry.
step  3.	Check for active users before stopping by entering the following command: express_adm shutdown
step  4.	Stop all EXPRESS activity by entering the following command: express_adm stop
step  5.	Start EXPRESS by entering the following command: express_adm start

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring SNAPlus2 for HP-UX

This section describes how to configure SNAPlus2 for HP-UX on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC.

Before you begin, ensure that your workstation has HP-UX SNAPlus2 installed. If you need more information in order to configure your SNA environment, refer to the online help provided with SNAPlus2.

The following assumptions are made:

• The basic installation of the SNAPlus2 for HP-UX package has already been completed.

• The DB2 client has been installed.

• The user is logged on as root.

To configure SNAPlus2 for DB2 Connect, log on to the system as a user with root authority and use either the /opt/sna/bin/snapadmin program or the /opt/sna/bin/X11/xsnapadmin program. Information about these programs can be found in the system documentation. The following steps describe how to use the xsnapadmin program to configure SNAplus2.

step  1.	Enter the command xsnapadmin. The Servers window opens. Double-click on your node.
step  2.	Define a Node Select Services->Configure Node Parameters from the menu bar. The Node Parameters window opens. Click on the APPN support drop down box and select the End node option. Enter your Network ID and the Local PU Name ((9) and (10)) in the Control point name fields. Enter Local PU Name ((10)) in the Control point alias field. Enter your Node ID ((13) and (14)) in the Node ID fields. Click on OK.
step  3.	Define a port Select the Connectivity and Dependent LUs window. Click on the Add push button. The Add to Node window opens. Select the Port using radio button. Click on the Port using drop down box and select the appropriate port type. For our example, we will select the Token ring card option. Click on OK. The Port window for the chosen port type opens. Enter a name for the port in the SNA port name field. Select the Initially active checkbox. From the Connection network box, select the Define on a connection network checkbox. Enter your Network ID ((9)) in the first part of the CN name field. Enter your local Control Point name ((10)) in the second part of the CN name field. Click on OK. The Port window closes and a new port appears in the Connectivity and Dependent LUs window.
step  4.	Define a link station In the Connectivity and Dependent LUs window, select the port that you defined in the previous step. Click on the Add push button. The Add to Node window opens. Select the Add a link station to port radio button. Click on OK. The Token ring link station window opens. Enter a name for the link in the Name field. Click on the Activation drop down box and select the On demand option. Select the Independent only option in the LU traffic box. In the Independent LU traffic box: Enter the Network ID ((3)) and the Partner LU Name ((2)) in the Remote Node fields. Click on the Remote node type drop down box and select the type of node that applies to your network. In the Contact information box, enter the SNA Destination Address ((8)) assigned to the DB2 server in the Mac address field. Click on OK. The Link Station window is closed and a new link station appears as a child of the port in the Connectivity and Dependent LUs window.
step  5.	Define a local LU Select the Independent local LUs window. Click on the Add push button. The Local LU window opens. Enter your independent local LU Name ((11)) in the LU name field. Enter the same name in the LU alias field ((12)). Click on OK. The new LU appears in the Independent local LUs window.
step  6.	Define a remote node Select the Remote Systems window. Click on the Add button. The Add to Node window opens. Select Define remote node. Click on OK. The Remote Node configuration window appears. Enter the Network ID ((3)) and the Partner LU Name ((2)) in the Node's SNA network name field. Click on OK. The remote node appears in the Remote Systems window, and a default partner LU is defined for the node and also appears as a child of the remote node.
step  7.	Define a partner LU In the Remote Sytems window, double-click the default partner LU that was created when you defined a remote node in the previous step. The Partner LU window opens. Enter the same Partner LU name ((2)) in the Alias and Uninterpreted name fields. Select Supports parallel sessions. Click on OK.
step  8.	Define a mode Select Services->APPC->Modes from the menu bar. The Modes window opens. Click on the Add push button. The Mode window opens. Enter a mode name ((15)) in the Name field. The configuration values below are suggested for the following fields: Initial Session limits: 20 Maximum Session limits: 32767 Min con. winner sessions: 10 Min con. loser sessions: 10 Auto-activated session: 4 Receive pacing window: 8 These values are suggested because they are known to work. You will need to tailor these values so that they are optimized for your particular application environment. Click on OK. The new mode appears in the Modes window. Click on Done.
step  9.	Define the CPI-C destination name Select Services->APPC->CPI-C from the menu bar. The CPI-C destination names window opens. Click on the Add push button. The CPI-C destination window opens. Enter the Symbolic Destination Name ((16)) you want to associate with the DB2 server database in the Name field. In the Partner TP box: Select Service TP (hex), and enter the hexadecimal TP number ((17)), or Select Application TP, and enter the application TP name. ((17)). In the Partner LU and mode box: Select the Use PLU Alias radio button, and enter the Partner LU Alias ((2)) that you created in a previous step. Enter the Mode name ((15)) for the mode that you created in a previous step in the Mode field. In the Security box, select the radio button that corresponds to the type of security level that you want to run on your network. Click on OK. The new destination name appears in the Destination names window. Click on Done.
step 10.	Test the APPC connection Start the SNA subsystem by entering the /opt/sna/bin/sna start command. You can enter the /opt/sna/bin/sna stop command to stop the SNA subsystem first, if required. Start the SNA administration program. You can enter either the /opt/sna/bin/sna admin command, the /opt/sna/bin/X11/xsna admin command. Start the subsystem node. Select the appropriate node icon in the button bar, and click the Start button. Start the link station. Select the link station you defined previously in the Connectivity and Dependant LUs window, and click on the Start push button. Start the session. Select the LU you defined previously in the Independant Local LUs window, and click on the Start push button. A session activation window opens. Select or enter the Partner LU and Mode desired. Click on OK.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, using the Client Configuration Assistant (CCA) is recommended. For more information, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring SunLink SNA for Solaris

This section describes how to configure SunLink SNA PU 2.1 (SunLink SNA) for Solaris on your DB2 client workstation to connect to a DB2 Connect or DB2 Universal Database server using APPC.

Before you begin, ensure that your workstation has SunLink SNA installed. If you need further information in order to configure your SNA environment, refer to the SunLink PU 2.1 Server Configuration and Administrator's Manual.

The following assumptions are made:

• The basic installation of the SunLink SNA PU 2.1 for Solaris package has already been completed.

• The DB2 client has been installed.

• The user is logged on as root.

To configure the SunLink SNA Server for use by a DB2 Client, log on as root and perform the following steps:

step  1.	Create the CPIC Side File
step  2.	Create the SNA Server Configuration File
step  3.	Define the Environment Variables Required by SunLink SNA
step  4.	Start the SunLink SNA Subsystem

Create the CPIC Side File

You can use any plain text editor to create the CPIC side file. The file must be placed in the application's path for a standalone DB2 Connect for Solaris system.

Note:

The name of the CPIC side file must be the same as the symbolic destination name specified in the DB2 node directory on the DB2 client.

The following example shows the CPIC side file sections required for configuring the SunLink SNA to connect to a DB2 server:

   # CPIC Side File information
   #
   PTNR_LU_NAME=NYX1GW0A
   MODE_NAME=IBMRDB
   TP_NAME=DB2DRDA
   SECURITY=NONE

Create the SNA Server Configuration File

You can use any plain text editor to create the SNA server configuration file. This file is called sunpu2.config, and it must be placed in /opt/SUNWpu21, or the directory where SunLink SNA PU 2.1 Server is installed.

The following example shows the configuration file sections required for configuring the SunLink SNA to connect to a DB2 server:

// SunLink SunLU6.2/SunPU2.1 SNA Server Sample Configuration
// Token Ring Peer-to-Peer System A @(#)sunlu62.a.tr
//
// The physical connection is a Token Ring interface adapter.
 
CP      NAME=CLI1GW                     // Local name (8 char max)
        NQ_CP_NAME=SPIFNET.CLI1GW       // Network Qualified Name
        ;
 
TRLINE  NAME=MAC1                       // SunLink specific name
        SOURCE_ADDRESS=x'400011527509'  // sysA_mac_addr for Sun machine
        ;
 
DLC     NAME=SERVLINK                   // User defined name (8 char max)
        LINK_NAME=MAC1                  // Line name this station is on
        LCLLSAP=x'04'                   // Local Link Service Access Point
        RMTLSAP=x'04'                   // Remove Link Service Access Point
        RMTMACADDR=x'400009451901       // sysB_mac_addr
        TERMID=x'07127509'              // XID negotiation
        ;
 
LU      NAME=CLI1GW0A                   // Local name (8 char max)
        NQ_LU_NAME=SPIFNET.CLI1GW0A     // Network Qualified Name
        SESS_LMT=50                     // Max LU sessions
        LUTYPE=6.2
        ;
 
PTNR_LU NAME=NYX1GW0A                   // Partner LU name(8 char max)
        LOC_LU_NAME=CLI1GWOA            // Associated Local LU
        NQ_LU_NAME=SPIFNET.NYX1GW0A     // Network Qualified Name
        ;
 
MODE    NAME=IBMRDB                     // Mode Name (8 char max)
        DLC_NAME=SERVLINK               // Associated DLC
        PTNR_LU_NAME=NYX1GW0A           // Associated Partner LU
        LCL_MAX_SESS_LMT=30             // Max Session Limit
        MIN_CW_SESS=15                  // Min Conwinners
        MIN_CL_SESS=15                  // Min Conlosers
        ;

Define the Environment Variables Required by SunLink SNA

In order to run any application, you must set the following environment variables:

APPC_GATEWAY

Name of the DB2 for Solaris server (usually the TCP/IP hostname).

APPC_LOCAL_LU

Name of the local LU name provided in the SNA configuration file.

Export these on the DB2 client machine before proceeding with the next step.

Start the SunLink SNA Subsystem

To start the SunLink SNA subsystem, perform the following steps:

step  1.	Change to the SunLink installation directory, usually: cd /opt/SUNWpu21
step  2.	Set up environment variables for FlexLM licensing. For example: export LD_LIBRARY_PATH=/usr/openwin/lib:/usr/lib export LM_LICENSE_FILE=/etc/opt/licenses/licenses_combined Refer to the SunLink documentation for more information.
step  3.	Ensure you have created the CPIC side file as described in Create the CPIC Side File
step  4.	Ensure you have created the SNA server configuration file as described in Create the SNA Server Configuration File.
step  5.	Use the sunop utility to check the status of SunLink SNA if it is already started. Check to see if the PU and/or DLC status is connected. You can also use sunop to check the status of links. Refer to the SunLink documentation for details of the sunop utility.
step  6.	Stop SunLink if it is active. For example, enter: kill -9 sunpu2.pid kill -9 sunlu2.pid
step  7.	Start SunLink using the following command: sunpu2.1

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see Step 3. Catalog the APPC or APPN Node and the sections that follow.

Step 3. Catalog the APPC or APPN Node

You must add an entry to the DB2 client workstations's node directory to describe the remote node. In most cases, you will add an APPC node entry to the node directory. For OS/2, Windows 9x, and Windows NT, you can alternatively add an APPN node entry if your local SNA node has been set up as an APPN node.

To catalog the node, perform the following steps:

step  1.	Log on to the system with a valid DB2 user ID. For more information, see Appendix G. Naming Rules. If you are adding a database to a system that has a DB2 or DB2 Connect server product installed, log on to this system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority on the instance. For more information, see Working with the System Administrative Group. This restriction is controlled by the catalog_noauth database manager configuration parameter. For more information, refer to the Administration Guide.
step  2.	If you are using DB2 Connect on a UNIX platform, set up the instance environment and invoke the DB2 command line processor. Run the start-up script 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.
step  3.	To catalog an APPC node, specify the chosen alias (node_name), Symbolic destination name (sym_dest_name), and the APPC security type (security_type) that the client will use for the APPC connection. Enter the following commands in the command line processor: catalog "appc node node_name remote sym_dest_name \ security security_type"; terminate The sym_dest_name parameter is case-sensitive and must match exactly the case of the Symbolic destination name you defined previously. For example, to catalog a remote database server with the Symbolic destination name DB2CPIC on the node called db2node, using APPC Security type NONE, enter the following commands: catalog appc node db2node remote DB2CPIC security NONE terminate
step  4.	To catalog an APPN node, specify the chosen alias (node_name), the network ID ((1)), the remote partner LU ((4)), the transaction program name ((17)), the mode ((15)), and the security type. Enter the following commands, substituting your values from the worksheet in Table 26: catalog "appn node db2node network SPIFNET remote NYX1GW0A tpname DB2DRDA mode IBMRDB security NONE" terminate

If you need to change values that were set with the catalog node command, perform the following steps: step  1. Run the uncatalog node command in the command line processor as follows: uncatalog node node_name step  2. Recatalog the node with the values that you want to use.

Step 4. Catalog the Database

Before a client application can access a remote database, the database must be cataloged on the server node and on any client nodes that will connect to it. When you create a database, it is automatically cataloged on the server with the database alias (database_alias) the same as the database name (database_name). The information in the database directory, along with the information in the node directory, is used on the client to establish a connection to the remote database.

To catalog a database on the client, perform the following steps:

step  1.	Log on to the system with a valid DB2 user ID. For more information, see Appendix G. Naming Rules. If you are adding a database to a system that has a DB2 or DB2 Connect server product installed, log on to this system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority on the instance. For more information, see Working with the System Administrative Group. This restriction is controlled by the catalog_noauth database manager configuration parameter. For more information, refer to the Administration Guide.
step  2.	Fill in the Your Value column in the following worksheet. Table 17. Worksheet: Parameter Values for Cataloging Databases Parameter Description Sample Value Your Value Database name (database_name) The database alias (database_alias) of the remote database. When you create a database, it is automatically cataloged on the server with the database alias (database_alias) the same as the database name (database_name). sample   Database alias (database_alias) An arbitrary local nickname for the remote database, on the client. If you do not provide one, the default is the same as the database name (database_name). This is the name that you use when connecting to a database from a client. tor1   Node name (node_name) The name of the node directory entry that describes where the database resides. Use the same value for node name (node_name) that you used to catalog the node in the previous step. db2node
step  3.	If you are using a UNIX client, set up the instance environment and invoke the DB2 command line processor. Run the start-up script 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.
step  4.	Catalog the database by entering the following commands: catalog database database_name as database_alias at node node_name terminate For example, to catalog a remote database called sample so that it has the alias tor1, on the node db2node, enter the following commands: catalog database sample as tor1 at node db2node terminate If you need to change values that were set with the catalog database command, perform the following steps: step  a. Run the uncatalog database command as follows: uncatalog database database_alias step  b. Recatalog the database with the value that you want to use.

Step 5. Test the Client-to-Server Connection

When you have finished configuring the client for communications, perform the following steps to test the connection:

You will need to connect to a remote database to test the connection.

step  1.	Start the database manager by entering the db2start command on the server (if it was not automatically started at boot time).
step  2.	Enter the following command to connect the client to the remote database: connect to database_alias user userid using password

The values for userid and password must be valid for the system on which they are authenticated. By default, authentication takes place on the server for a DB2 server and on the host or AS/400 machine for a DB2 Connect server.

If the connection is successful, you will get a message showing the name of the database to which you have connected. You are now able to retrieve data from that database. For example, to retrieve a list of all the table names listed in the system catalog table, enter the following SQL command in the Command Center or command line processor:

   "select tabname from syscat.tables"

When you are finished using the database connection, enter the connect reset command to end the database connection.

You are now ready to start using DB2. For more advanced topics, refer to the Administration Guide and the Installation and Configuration Supplement.

Troubleshooting the Client-to-Server Connection

If the connection fails, check the following items:

At the server:

1. The db2comm registry value includes the value appc.
   

   Check the settings for the db2comm registry value by entering the db2set DB2COMM command. For more information, refer to the Administration Guide.

2. The transaction program name (tpname) parameter was updated correctly in the database manager configuration file (or the admin server configuration file, if you are setting up the Administration Server).

3. The security service was started. Enter the net start db2ntsecserver command (for Windows NT servers only).

4. The database was created and cataloged properly.

5. The database manager was stopped and started again (enter the db2stop and db2start commands on the server).

If there are problems starting a protocol's connection managers, a warning message appears and the error messages are logged in the db2diag.log file. For more information on the db2diag.log file, refer to the Troubleshooting Guide.

At the client:

1. The node was cataloged with the correct Symbolic Destination Name (sym_dest_name).

2. The node name (node_name) that was specified in the database directory points to the correct entry in the node directory.

3. The database was cataloged properly, using the server's database alias (database_alias) that was cataloged when the database was created on the server, as the database name (database_name) on the client.

If the connection still fails after you verify these items, refer to the Troubleshooting Guide.

[ DB2 List of Books | Search the DB2 Books ]