Follow the steps below to diagnose problems while establishing connection to a PD Tools Common Server.
Specify new connection in Host Connections View |
---|
![]() |
PD Tools Common Component Preference Page |
---|
![]() |
Success Dialog | Failure Dialog |
---|---|
![]() |
![]() |
Once you have the dialog, especially the dialog with error(s), you can examine the returned messages to diagnose the problem.
Diagnostic Information | Action | ||
---|---|---|---|
'***** ERROR *****' | Marks the beginning of error(s) discovered during the problem diagnosis. Read the following message to understand the problem(s). For example, the error dialog above reports an error related to an invalid port number. You need to verify that the port number is valid for the PD Tools common server with your system administrator. | ||
The diagnostic tool Hangs | If the client is hanging after clicking on the test connection button, click on the cancel button and read the problem diagnostic information returned in the dialog. You have most likely specified a port number which is used by another product. | ||
Failure to launch an extension |
The PD Tools common server is extensible with additional configuration files. For example, it can be extended to handle Fault Analyzer for z/OS and File Manager
for z/OS plug-ins by configuring the extensions. If you are unable to use one of the PD Tools plug-ins, it is quite possible that the server extensions are not
installed/configured on your server. To check what extensions are configured to the server, look for a message
Getting the information about extensions installed on the server. Extensions: in the problem diagnostic text. You will find a list of server extensions that
are known to the server. Look for the extension configuration names below:
In the example above, FA and FM extensions are installed along with DEFAULT (a must have configuration file) and VRFY (pre-configured extension for enabling the problem diagnosis). |
You can view the local log file contents by pressing the "View Log" button. You can also clear the contents of the local log file by pressing the "Clear Log" button.
The log file contents are only useful when diagnosing problems with the IBM support team. When requested, follow the steps required to capture the debugging information: