DB2 Connect Quick Beginnings for Linux**

Preparing OS/390 for DB2 Connect

Your VTAM administrator and your host system administrator must configure VTAM and OS/390 to receive inbound connection requests from your DB2 Connect workstation. Usually your host system has already been configured for communications. For more information, contact your VTAM administrator and your host system administrator or refer to the Connectivity Supplement.

This section assumes that your DB2 for OS/390 server has already been configured for remote client access, if this is not the case, refer to the Connectivity Supplement for the required VTAM configuration steps.

Verify that the Correct PTFs Have Been Applied to your OS/390 SystemDB2 Universal Database for OS/390

Before you configure you OS/390 system to accept inbound requests for data from your DB2 Connect Personal edition workstation, you muse verify that the following PTFs have been applied:

• PTF UQ06843 for APAR PQ05771
• PTF UQ09146 for APAR PQ07537.

Configure DB2 Universal Database for OS/390

Before you can use DB2 Connect, your DB2 Universal Database for OS/390 Administrator must configure DB2 Universal Database for OS/390 to permit connections from DB2 Connect workstations. This section indicates the minimum updates required in order to permit a DB2 Connect client to make a connection to the DB2 Universal Database for OS/390 database server. For more detailed examples, refer to the Connectivity Supplement, and the DB2 for OS/390 Installation Reference.

Configure TCP/IP for DB2 Universal Database for OS/390

This section describes how to configure TCP/IP communications between your DB2 Connect workstation and DB2 Universal Database for OS/390 Version 5.1 or later. It assumes that:

• You are connecting to a single host database via TCP/IP. Multiple host connections will be handled in exactly the same way, although the port number and service number required in each case may be different.
• The target database resides on DB2 Universal Database for OS/390 Version 5.1 or later.
• All the necessary software prerequisites are installed.

Prerequisite OS/390 Software for TCP/IP Support

OS/390 R3+ is the minimum operating system level required for TCP/IP support. OS/390 V2R5+ is the recommended operating system level, and the best performer.

The following informational APARS for DB2 for OS/390 are regularly updated with information about PTFs to install for various OS/390 components, particularly TCP/IP for OS/390. If you use TCP/IP connectivity with DB2 for OS/390, it is extremely important that you review and apply the following PTFs and APAR fixes:

• II11164
• II11263
• II10962
• DB2 for OS/390 Version 5.1: PTF UQ13908, PTF UQ17755

Collecting Information

Before you can use DB2 Connect over a TCP/IP connection, you must collect information about both the host database server and the DB2 Connect workstation. For each host server that you are connecting to via TCP/IP, you must have the following information:

• The locations of the equivalent files at the target DB2 Universal Database for OS/390 host.
• The TCP/IP port number defined to DB2 Universal Database for OS/390. (Note that the associated service name information is not exchanged between the DB2 Connect workstation and DB2 Universal Database for OS/390). Port number 446 has been registered as the default for communication from a DB2 Connect workstation.
• The TCP/IP addresses and hostnames for both the host and the DB2 Connect workstation.
• The LOCATION NAME of the DB2 for OS/390 database server
• The user ID and password to be used when issuing CONNECT requests for the database at the host.

Refer to your local network administrator and your DB2 for OS/390 administrator for help getting this information. Use one copy of the example work sheet, Table 5, to plan each TCP/IP connection between DB2 Connect and a host database server.

Example Worksheet

Table 5. Example Worksheet for Planning TCP/IP Connections to DB2 Universal Database for OS/390

Ref.	Description	Sample Value	Your Value
User Information
(TCP-1)	User Name	A.D.B.User
(TCP-2)	Contact Info	(123)-456-7890
(TCP-5)	User ID	ADBUSER
(TCP-6)	Database Type	db2390
(TCP-7)	Connection type (must be TCPIP).	TCPIP	TCPIP
Network Elements at the Host
(TCP-8)	Host name	nyx
(TCP-9)	Host IP address	9.21.15.235
(TCP-10)	Service name	db2inst1c
(TCP-11)	Port number	446
(TCP-12)	LOCATION NAME	newyork
(TCP-13)	User ID
(TCP-14)	Password
Network Elements at the DB2 Connect Workstation
(TCP-18)	Host name	mcook02
(TCP-19)	IP address	9.21.27.179
(TCP-20)	Service name	db2inst1c
(TCP-21)	Port number	446

Notes:

1. To obtain the host's IP address (TCP-9), enter at the host:

      TSO NETSTAT HOME
   

2. To obtain the port number (TCP-11), look for DSNL004I in the DB2 master address space or system log.

Configuring the TCP/IP Connection

Use the manual steps in this section to complete the configuration and make the connection.

1. Complete the Worksheet

Complete a copy of the example worksheet for each TCP/IP host:

1. Fill in the values to be used for the TCP/IP address and hostname of the DB2 Universal Database for OS/390 host (items 8 and 9).
2. Fill in the values to be used for the TCP/IP address and hostname of the DB2 Connect workstation (items 18 and 19).
3. Determine the port number or service name to be used for the connection (items 10 and 11, or 20 and 21).
4. Determine the LOCATION NAME of the DB2 for OS/390 database server to which you wish to connect.
5. Determine the values to be used for user ID and PASSWORD when connecting to the host database.

Note that some additional planning considerations may apply, refer to the DB2 Connect User's Guide for more information.

2. Update the DB2 Universal Database for OS/390 Host

At your OS/390 host:

1. Verify the host address or the host name.
2. Verify the port number or the service name.
3. Update the services file with the correct port number and service name if necessary.
4. Update the hosts file (or the Domain Name Server used by the DB2 Universal Database for OS/390 system) with the hostname and IP address of the DB2 Connect workstation.
5. Ensure the new definitions are active before attempting to test the connection. Refer to your host network administrator or change control staff if necessary.
6. Check with the DB2 Universal Database for OS/390 administrator that you have a valid user ID, password, and database LOCATION NAME.
7. PING the DB2 Connect workstation, using the correct port number if that option is supported by TCP/IP on the host system. For example:

      ping remote_host_name -p port_number