Troubleshooting AS/400 TCP/IP Connectivity
See Also

If you are unable to connect to the AS/400 database from ASNA’s Acceler8DB Database Manager, the following information may help identify possible incorrect setups on the AS/400.

It is assumed that TCP/IP configuration has been completed correctly on the PC side. If you are unsure whether TCP/IP is installed or correctly configured on your PC, contact your network administrator for assistance.

TCP/IP names are a combination of host names (machine names) and domain names. A machine name for TCP/IP does not have to match the AS/400 machine name; however, it will be a unique name - and it can be the same as the AS/400 machine name.

Throughout this example, the machine name used is ‘machine’, and the AS/400 name is actually ‘S1037242’. The domain name used throughout this example is ‘domain.com’. Together the machine name and the domain name make a ‘complete’ TCP/IP name - ‘machine.domain.com’. At your site, you should use your own domain name and own machine name.

1. First check to see if you are able to ping the AS/400 by name from your PC. For example, if the TCP/IP name of the AS/400 is ‘machine.domain.com,’ then the following command should be issued from your machine from a DOS Box:

ping machine.domain.com

·      If you do not get a ‘reply’ from the machine that was pinged, then TCP/IP may not be configured correctly, either on your machine or on the AS/400. If you receive a “Bad command or filename” error message when typing the ping command, your machine may not have TCP/IP installed. Please check with your network administrator to make sure your machine has TCP/IP capability.

·      If you do get a response from the AS/400 when the ping command is issued, then it is still possible some settings on the AS/400 may be incorrect. From a command line on the AS/400, issue the following command: cfgtcp.

2. From the Configure TCP/IP menu screen that appears, select the Work with TCP/IP Interfaces (option 1).

3. The following menu screen will appear.

shg00025_shg.gif

You should see something similar to this screen. If you do not, then TCP/IP is probably not configured on the AS/400 properly, or it may not be completely installed. Check with your AS/400 administrator to make sure the AS/400 has TCP/IP installed.

4. If there is an internet address other than 127.0.0.1 listed, select that address and enter an option 5 command to display the setting for that IP address.

·      The Interface status should indicate Active. If it does not, then the TCP/IP services, although installed, may not be started, or it may have terminated. The TCP/IP services should be started.

·      Try re-connecting to the AS/400 database after restarting the TCP/IP services. (To start the TCP/IP services you must have sufficient authority rights and issue the following command from a menu prompt: STRTCP). After you have done this, then issue another ping command to see if you get a reply.

5. If you reach this point and are still having problems accessing the AS/400 via TCP/IP, then F12 back to the main configuration screen for TCP/IP (Configure TCP/IP) and enter option 21 (Configure Related Tables) from the main TCP/IP configuration menu.

·      On the Configure Related Tables menu screen that appears next, select option 1, Work with Service Table Entries. You will then see the Work with Service Table Entries menu screen. Scroll through the list of services to find the Acceler8DBServer entry.

·      If there is no entry here, then that is the problem. Make sure you perform the installation section for the AS/400 as stated earlier in this chapter.

·      If the Acceler8DBServer entry is found, then the default port will be 5042 (unless it was installed with a different port). It is strongly suggested to use Port 5042.

checked_shg.gif  The protocol listed in the service table entry for the ‘Acceler8DBServer’ service should be ‘tcp’. It is case sensitive, so if the letters are uppercase, you will need to remove the service and re-add the service with lower case letters.