Quick Beginnings

Step 3. Install DB2 Connect for Windows

1. Install DB2 Connect Personal Edition, without selecting DB2 Connect Integrated SNA Support.

2. When the installation is completed, reboot.

3. Open the DB2 Folder, and click on the Client Configuration Assistant to start the configuration dialog.

4. You need to provide the following information:

   1. The Symbolic Destination Name defined at the Microsoft SNA Server for the Partner LU of the target DRDA host. This is (7) on the example worksheet for this configuration (Table 16), and (24) on the worksheet provided for use with SNA Server (Table 15).

   2. The real database name, for example the DB2 for OS/390 or DB2 for MVS/ESA "LOCATION NAME". This is (12) on both worksheets.

Table 16. Example Worksheet for Microsoft SNA Client Users

No.	Description	Sample Value	Your Value
User Information
(1)	User Name	A.D.B.User
(2)	Contact Info	(123)-456-7890
	Location
MS SNA Server Information (provided by SNA Server administrator)
(3)	MS SNA Server domain name	ACCOUNTS
(4)	Protocol used for communicating with SNA Server (TCP/IP, NetBEUI, IPX/SPX)	NetBEUI
(5)	User ID used to login to the MS SNA Server domain	ADBUSER
(6)	Password used to login to the MS SNA Server domain	XXXXXXX
(7)	Database CPI-C symbolic destination name (defined to MS SNA Server).	DB2CPIC
(8)	Password management CPI-C symbolic destination name	DB2PEM
Database Information (provided by host or AS/400 administrator)
(9)	Alias	NYC3
(10)	Description	New York DB #3
(11)	Database Type	DB2 for MVS/ESA or DB2 for OS/390
(12)	Host database name	NEW_YORK3
(13)	User ID assigned to you on your host or AS/400 system	ADBUSER
(14)	Password to be used to connect to your host or AS/400 system	XXXXXXXX

Update the DB2 Directories

To configure the DB2 directories, enter the following commands in the command line processor:

1. Catalog the DRDA server as an APPC node. The syntax of the command is:

      catalog appc node node_name remote sym_dest_name security program
   

   For example:

      catalog appc node DB2NODE remote DB2CPIC security program
   

   Note:

   The case of the sym_dest_name (DB2CPIC in this example) must match the case of the Symbolic Destination Name that you defined when you installed MS Client.

2. Catalog the remote database as a Data Connection Services (DCS) database. The syntax of the command is:

      catalog dcs db local_dbname as real_host_dbname
   

   For example:

      catalog dcs db NYC3 as NEW_YORK3
   

3. Catalog a Database alias for the remote database. The syntax of the command is:

      catalog db local_dbname as Db_alias at node node_name authentication dcs
   

   For example:

      catalog db DB2DB as NYC3 at node DB2NODE authentication dcs
   

In the DB2 commands above:

• node_name can be any valid eight-character name

• sym_dest_name is the name of your Side Information Profile.

• local_dbname can be any valid eight-character name

• Db_alias can be any valid eight-character name

• real_host_dbname is the name of the database you want to connect to at the DRDA server.

Test the Connection

Issue the following command from the command line processor window, remembering to substitute your Db_alias value from the previous step:

   connect to Db_alias user userid using password

For example:

   connect to nyc3 user userid using password

The user ID and password values required are those defined at the host or AS/400, and must be provided to you by your DB2 Administrator.

[ DB2 List of Books | Search the DB2 Books ]