In this part, you will learn to set up these three connectivity scenarios:
From DB2 for iSeries client to DB2 for Linux, UNIX, and Windows server
From DB2 for iSeries client to DB2 for z/OS server
From DB2 for iSeries client to DB2 for iSeries server
The DB2 Connect software is not required in these scenarios.
Figure E.5 shows the overview for the scenario described in this section.
Table E.7 presents the list of commands required to set up this connection.
Table E.8 provides troubleshooting hints for connectivity problems.
Client Machine torisc6 | Database Server aries |
---|---|
ping aries.xyz.com This command can be performed from the OS/400 Main menu (assuming the hostname was used instead of the IP address itself in the Add RDB Directory Entry panel). | aries.xyz.com = the host name of the database server If you cannot ping, there may be problems with the DNS. Try pinging the IP address. |
ping 9.23.190.24 This command can be performed from the OS/400 Main menu. | 9.23.190.24 = the IP address of the database server This will confirm whether or not there are problems with the network. |
No corresponding information required on this machine. |
|
If you used a service name instead of the port number in your Add RDB Directory Entry panel, make sure the entry is correct in the services file at the client machine. | No corresponding information required on this machine. |
netstat
This command shows all connections and port numbers and their statuses. It can be performed from the OS/400 Main menu, options 6 -> 5 -> 10 -> 7 -> 3. |
netstat -a -n
This command shows all connections and port numbers and their statuses. Issue it from your command prompt. |
Figure E.6 shows the overview for the scenario described in this section.
Table E.9 presents the list of commands required to set up this connection.
Table E.10 provides troubleshooting hints for connectivity problems.
Client Machine torisc6 | Database Server tlba22me |
---|---|
ping tlba22me.myacme.com This command can be performed from the OS/400 Main menu (assuming the hostname was used instead of the IP address itself in the Add RDB Directory Entry panel). | tlba22me.myacme.com = the host name of the database server If you cannot ping, there may be problems with the DNS. Try pinging the IP address. |
ping 10.228.50.34 This command can be performed from the OS/400 Main menu. | 10.228.50.34 = the IP address of the database server This will confirm whether or not there are problems with the network. |
No corresponding information required on this machine. | Since the Database server is DB2 UDB for OS/390 and z/OS, check:
|
If you used a service name instead of the port number in your Add RDB Directory Entry panel, make sure the entry is correct in the services file at the client machine. | No corresponding information required on this machine. |
netstat
This command shows all connections and port numbers and their statuses. It can be performed from the OS/400 Main menu, options 6 -> 5 -> 10 -> 7 -> 3. |
netstat
This command shows all connections and port numbers and their statuses. Issue this command from option 6 Command in the main ISPF menu. |
Figure E.7 shows the overview for the scenario described in this section.
Table E.11 presents the list of commands required to set up this connection.
Table E.12 provides troubleshooting hints for connectivity problems.
Client Machine torisc6 | Database Server mytorisc |
---|---|
ping mytorisc.acme.com This command can be performed from the OS/400 Main menu (assuming the hostname was used instead of the IP address itself in the Add RDB Directory Entry panel). | mytorisc.acme.com = the host name of the database server If you cannot ping, there may be problems with the DNS. Try pinging the IP address. |
ping 90.29.168.62 This command can be performed from the OS/400 Main menu. | 90.29.168.62 = the IP address of the database server This will confirm whether or not there are problems with the network. |
No corresponding information required on this machine. | Since the Database server is DB2 UDB for iSeries, check:
Is DDM started? If not, execute the following command:
STRTTCPSVR SERVER(*DDM)
|
If you used a service name instead of the port number in your Add RDB Directory Entry panel, make sure the entry is correct in the services file at the client machine. | No corresponding information required on this machine. |
netstat
This command shows all connections and port numbers and their statuses. It can be performed from the OS/400 Main menu, options 6 -> 5 -> 10 -> 7 -> 3. |
netstat
This command shows all connections and port numbers and their statuses. It can be performed from the OS/400 Main menu, options 6 -> 5 -> 10 -> 7 -> 3. |