Diagnostic probe management in data processing systems

• US 7,254,745 B2
• Filed: 10/03/2002
• Issued: 08/07/2007
• Est. Priority Date: 10/03/2002
• Status: Expired due to Fees

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Potter, Bruce M., Briskey, Kenneth C., Ranganathan, Kesavaprasath
• Primary Examiner(s): Bonzo; Bryce P.
• Application Number:
  US10/263,886
• Publication Number:
  US 20040068677A1
• Time in Patent Office: 1,769 Days
• Field of Search: 714/27
• US Class Current: 714/27
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

A common interface (API) is provided which permits a single diagnostic probe manager to communicate with and to control a plurality of diagnostic probes. Through this interface the diagnostic probes are enabled to pass information concerning dependencies between software levels present in a hierarchical stack. This information is particularly useful in that it permits the probe manager to direct diagnostic efforts at the lowest desirable level so as to avoid the problems that occur when problems are indicated at a high level but which are actually caused by lower level software components.

Claims

1. A method for constructing diagnosis software for use in data processing systems, said method comprising the step of:

providing a diagnostic probe manager and a plurality of diagnostic probes which have a common interface defined for communication between said diagnostic probe manager and said diagnostic probes, said probes being directed to a specific hierarchical software level and being further capable of returning information to the diagnostic probe manager indicating dependency on other diagnostic probes controlled by said manager.

2. The method of claim 1 in which at least some of said plurality of diagnostic probes are independent.

3. The method of claim 1 in which said diagnostic probe manager determines in what order said other diagnostic probes are executed based upon said returned dependency information.

4. The method of claim 1 in which said diagnostic probe manager operates to prevent probes from being run twice.

5. The method of claim 1 in which said diagnostic probe manager causes a lowest level of diagnostic probe to be executed first.

6. The method of claim 1 in which said diagnostic probe manager determines in what order said other diagnostic probes are executed.

7. The method of claim 1 in which said diagnostic probe manager operates to prevent probes from being run twice.

8. A method for diagnosing software problems in data processing systems, said method comprising the steps of:

providing a plurality of diagnostic probes; and

providing a diagnostic probe manager for said plurality of diagnostic probes1 said probes and said diagnostic probe manager communicating through a common interface, said diagnostic probes being directed to a specific hierarchical software level and being further capable of returning information to said diagnostic probe manager indicating dependency on other diagnostic probes controlled by said manager.

9. The method of claim 8 in which at least some of said plurality of diagnostic probes are independent.

10. The method of claim 8 in which said diagnostic probe manager is capable of allowing execution of probes that depend on a failed probe.

11. The method of claim 8 in which at least one diagnostic probe returns information selected from the set consisting of error messages, probe dependency, probe purpose and detailed probe documentation.

12. The method of claim 8 in which said interface includes a flag for indicating that errors indicated by specified messages numbers are to be ignored.

13. The method of claim 8 in which said interface includes a flag indicating a severity level for determining whether or not error messages are reported.

14. The method of claim 8 in which at least one of said probes returns a status indication.

15. The method of claim 8 in which each diagnostic probe operates independently of all other diagnostic probes.

16. The method of claim 8 in which said diagnostic probe manager ceases execution of any probe depending on a failed probe.

17. A data processing system including memory and processor elements wherein said memory includes a plurality of software components and further includes a plurality of diagnostic probes for determining problems with said software components and a diagnostic probe manager for said plurality of diagnostic probes, said diagnostic probes and said diagnostic probe manager having a common interface defined for communication between said diagnostic probe manager and said diagnostic probes, said probes being directed to a specific hierarchical software level and being further capable of returning information to the diagnostic probe manager indicating dependency on other diagnostic probes controlled by said manager.

18. A machine readable medium containing thereon code for implementing a diagnostic probe manager which provides a common interface for communicating between said diagnostic probe manager and a plurality of diagnostic probes, said diagnostic probes and said diagnostic probe manager having a common interface defined for communication between said diagnostic probe manager and said diagnostic probes, said probes being directed to a specific hierarchical software level and being further capable of returning information to the diagnostic probe manager indicating dependency on other diagnostic probes controlled by said manager.