Follow the steps below to diagnose problems while establishing a connection to the ADFz Common Components Server.
Specify new connection in Host Connections View |
---|
![]() |
ADFz Preference Page |
---|
![]() |
Success Dialog | Failure Dialog |
---|---|
![]() |
![]() |
Once you have the dialog, especially the dialog with errors, you can examine the returned messages to diagnose the problem.
Diagnostic Information | Action | ||
---|---|---|---|
'***** ERROR *****' | Marks the beginning of errors discovered during the problem diagnosis. Read the error message to understand the problem. 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 ADFz 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 ADFz 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 ADFz plug-ins, it is possible that the server extensions are not installed and configured on your server. To check which extensions are configured on the server, look for the following section in the diagnostics text: Getting the information about extensions installed on the server. You will find a list of server extensions that are known to the ADFz Server. Look for the extension configuration names shown below:
In the example above, FA and FM extensions are installed along with DEFAULT (a required configuration file) and VRFY (a 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 files are intended for use by the IBM support team when diagnosing problems. If requested, follow these steps to capture the debugging information: