Micro Focus enterprise products include a varied set of facilities for problem analysis. These diagnostic facilities are the result of numerous implementations, and the realization that different sorts of problems can occur, each requiring its own type of approach. We will try to suggest here which diagnostic facility to use for which problem.
As a minimum, we recommend that anyone involved in Enterprise Server implementations should know, for each diagnostic tool or technique:
After identifying the appropriate facility, we aim to help any users of the enterprise products to set up and run the diagnostics, and then either analyze the output themselves or send them to Micro Focus for help from our Support teams.
Depending on the type of problem, you might need to use several of these diagnostic facilities simultaneously. For instance, a regular start point is the console log. However, this rarely shows the full problem, so very often you need a trace output and dump to complete the analysis. The console log might identify the failing process, and the trace and dump output will show the detail of what the process was doing and how it was interacting with the other processes if that is critical. Alone, these might be of little use, but together they can pinpoint what led to the failure.
Although it is well understood that during project implementation and production running, speed can be of the essence to complete the project or bring the business system back up, if Micro Focus is to help, it is vital that the diagnostic output be gathered in its entirety and treated as data of very high value in its detail and its completeness.
Please treat this documentation as a reference, and bear in mind that each problem is different and will require its own approach to diagnosis, so choose from the facilities detailed here based on what you believe to be the type of problem.