Method, system and program for handling errors occurring in function calls

• US 6,973,643 B2
• Filed: 08/17/2001
• Issued: 12/06/2005
• Est. Priority Date: 08/17/2001
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Goldsmith, Kevin Scott, Vining, Robert Guy
• Primary Examiner(s): DAS, CHAMELI
• Application Number:
  US09/932,332
• Publication Number:
  US 20030037291A1
• Time in Patent Office: 1,572 Days
• Field of Search: 717/124, 717/126, 717/141, 717/130, 714/38, 714/47, 714/48, 714/49, 714 1- 2, 714/15, 714/25, 709/201, 709/204, 709/209, 707/2, 707/203
• US Class Current: 717/124
• CPC Class Codes: G06F 11/006 Identification G06F11/2289 takes precedence
• CPC Class Codes: G06F 11/0775 Content or structure details of the error report, e.g. specific table structure, specific error fields
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36

Abstract

Provided is a method, system, and program for handling errors in a service program including service functions capable of being called from application programs. A call is received for one service function from a service function call within one application program. A series of test operations are performed when executing the service function call. Each test operation returns an identifier if the test operation failed where each identifier is associated with one error state. If one test operation failed, then the identifier for the failed test operation is transferred to an error handling agent, wherein the error handling agent accesses error information associated with the identifier and generates error information describing a specific cause of the error that caused the test operation to fail and then returns to the application program with a generic return code.

Claims

1. A method for handling errors in a service program including service functions capable of being called from application programs, comprising:

receiving a call for one service function from a service function call within one application program;

performing a series of test operations when executing the service function call, wherein each test operation returns an identifier if the test operation failed, wherein each identifier is associated with one error state;

if one test operation failed, transmitting the identifier associated with the error state of the failed test operation to an error handling agent, wherein the error handling agent accesses error information associated with the identifier and generates error information describing a specific cause of the error that caused the test operation to fail;

generating error information providing a description of a service function error associated with a received identifier;

providing a directory including entries corresponding to identifiers capable of being received from the service function, wherein the directory maintains error information for identifiers that describes a specific cause of the test operation failure associated with the identifier;

accessing one entry in the directory corresponding to the received identifier, wherein the generated error information comprises the description of a specific cause of the error in the directory entry for the received identifier;

detecting a change in a version number of the service program;

accessing an updated directory reflecting changes resulting from an update to service functions in the service program; and

replacing the directory with the updated directory, wherein the updated directory is capable of including modifications to the identifiers and error information.

2. The method of claim 1, wherein the identifier indicates an occurrence of an error at a unique location in the service program.

3. The method of claim 1, further comprising:

if no test operation for the called service function failed, then transmitting one identifier indicating that no error occurred to the error handling agent.

4. The method of claim 1, wherein the error handling agent is separate from the service program receiving the call.

5. A method for handling errors resulting from execution of a service function in a service program, wherein one application program calls the service function in the service program, comprising:

receiving an identifier from the service program executing the service function, wherein the service program performs a series of test operations when executing the service function, wherein each test operation returns one identifier if the test operation failed that is associated with one error state;

if the received identifier indicates that one error occurred during execution of the service function, then generating and transmitting a return code to the application program indicating that an error occurred;

generating error information providing a description of a service function error associated with the received identifier;

providing a directory including entries corresponding to identifiers capable of being received from the service function, wherein the directory maintains error information for identifiers that describes a specific cause of the test operation failure associated with the identifier;

accessing one entry in the directory corresponding to the received identifier, wherein the generated error information comprises the description of a specific cause of the error in the directory entry for the received identifier;

detecting a change in a version number of the service program;

accessing an updated directory reflecting changes resulting from an update to service functions in the service program; and

replacing the directory with the updated directory, wherein the updated directory is capable of including modifications to the identifiers and error information.

6. The method of claim 5, wherein the identifier indicates an occurrence of an error at a unique location in the service program.

7. The method of claim 5, further comprising:

if the received identifier indicates that one error did not occur during execution of the service function, then the generated return code indicates that no error occurred.

8. The method of claim 5, further comprising:

returning additional data describing the error to the application program if the return code indicates that one error occurred.

9. The method of claim 5, wherein the return code comprises generic error information, wherein one return code is used to provide generic error information for multiple identifiers.

10. The method of claim 5, further comprising:

receiving data related to the failed test operation from the service program; and

including the received data related to the failed test operation within the generated error information.

11. The method of claim 5, further comprising:

writing the generated error information to a log file.

12. The method of claim 5, wherein the directory further maintains a generic error code in each entry, wherein the same generic error code is used for multiple identifiers providing a general description of the error state resulting from the failure of the test operation, and wherein the return code transmitted to the application program comprises the generic error code for the received identifier in the directory.

13. The method of claim 5, wherein the application program and service program execute on different computer systems.

14. The method of claim 5, wherein the application program and service program run on different operating system platforms.

15. The method of claim 5, wherein the service program comprises an operating system program.

16. The method of claim 5, wherein the steps of receiving the identifier, generating the error information, and transmitting the return code are performed by a program that is external to the application program and service program.

17. A system for handling errors resulting from execution of a service function in a service program, comprising:

(a) at least one computer readable medium, including;

(i) an application program;

(ii) a service program;

(iii) at least one service function included in the service program;

(iv) an error handling agent;

(b) means, performed by the application program, for calling one service function in the service program;

(c) means, performed by the service program in response to the call to the service function, for;

(i) performing a series of test operations when executing the service function, wherein each test operation returns one identifier if the test operation failed that is associated with one error state;

(ii) transmitting the identifier associated with the error state of the failed test operation to the error handling agent if one test operation failed; and

(d) means, performed by the error handling agent, for;

(i) receiving the identifier from the service program executing the service function;

(ii) generating and transmitting a return code to the application program indicating that an error occurred if the received identifier indicates that one error occurred during execution of the service function;

(iii) generating error information providing a description of a service function error associated with the received identifier;

(iv) providing a directory including entries corresponding to identifiers capable of being received from the service function, wherein the directory maintains error information for identifiers that describes a specific cause of the test operation failure associated with the identifier; and

(v) accessing one entry in the directory corresponding to the received identifier, wherein the generated error information comprises the description of a specific cause of the error in the directory entry for the received identifier;

(vi) detecting a change in a version number of the service program;

(vii) accessing an updated directory reflecting changes resulting from an update to service functions in the service program; and

(viii) replacing the directory with the updated directory, wherein the updated directory is capable of including modifications to the identifiers and error information.

18. The system of claim 17, wherein the identifier indicates an occurrence of an error at a unique location in the service program.

19. The system of claim 17, wherein the generated return code indicates that no error occurred if the received identifier indicates that one error did not occur during execution of the service function.

20. The system of claim 17, wherein the means performed by the error handling agent further performs:

returning additional data describing the error to the application program if the return code indicates that one error occurred.

21. The system of claim 17, wherein the return code comprises generic error information, wherein one return code is used to provide generic error information for multiple identifiers.

22. The system of claim 17, wherein the means performed by the error handling agent further performs:

receiving data related to the failed test operation from the service program; and

including the received data related to the failed test operation within the generated error information.

23. The system of claim 17, wherein the means performed by the error handling agent further performs:

writing the generated error information to a log file.

24. The system of claim 17, wherein the directory further maintains a generic error code in each entry, wherein the same generic error code is used for multiple identifiers providing a general description of the error state resulting from the failure of the test operation, and wherein the return code transmitted to the application program comprises the generic error code for the received identifier in the directory.

25. The system of claim 17, wherein the application program and service program execute on different computer systems.

26. The system of claim 17, wherein the application program and service program run on different operating system platforms.

27. The system of claim 17, wherein the service program comprises an operating system program.

28. The system of claim 17, wherein the error handling agent executes externally from the application program and service program.

29. The system of claim 17, wherein each error state is associated with one location in source code for the service function call.

30. An article of manufacture including code for handling errors in a service program including service functions capable of being called from application programs by:

receiving a call for one service function from a service function call within one application program;

performing a series of test operations when executing the service function call, wherein each test operation returns an identifier if the test operation failed, wherein each identifier is associated with one error state;

if one test operation failed, transmitting the identifier associated with the error state of the failed test operation to an error handling agent, wherein the error handling agent accesses error information associated with the identifier and generates error information describing a specific cause of the error that caused the test operation to fail;

generating error information providing a description of a service function error associated with a received identifier;

providing a directory including entries corresponding to identifiers capable of being received from the service function, wherein the directory maintains error information for identifiers that describes a specific cause of the test operation failure associated with the identifier;

accessing one entry in the directory corresponding to the received identifier, wherein the generated error information comprises the description of a specific cause of the error in the directory entry for the received identifier;

detecting a change in a version number of the service program;

accessing an updated directory reflecting changes resulting from an update to service functions in the service program; and

replacing the directory with the updated directory, wherein the updated directory is capable of including modifications to the identifiers and error information.

31. The article of manufacture of claim 30, wherein the identifier indicates an occurrence of an error at a unique location in the service program.

32. The article of manufacture of claim 30, further comprising:

if no test operation for the called service function failed, then transmitting one identifier indicating that no error occurred to the error handling agent.

33. The article of manufacture of claim 30, wherein the error handling agent is separate from the service program receiving the call.

34. An article of manufacture for handling errors resulting from execution of a service function in a service program, wherein one application program calls the service function in the service program, by:

receiving an identifier from the service program executing the service function, wherein the service program performs a series of test operations when executing the service function, wherein each test operation returns one identifier if the test operation failed that is associated with one error state;

if the received identifier indicates that one error occurred during execution of the service function, then generating and transmitting a return code to the application program indicating that an error occurred;

generating error information providing a description of a service function error associated with the received identifier;

providing a directory including entries corresponding to identifiers capable of being received from the service function, wherein the directory maintains error information for identifiers that describes a specific cause of the test operation failure associated with the identifier;

accessing one entry in the directory corresponding to the received identifier, wherein the generated error information comprises the description of a specific cause of the error in the directory entry for the received identifier;

detecting a change in a version number of the service program;

accessing an updated directory reflecting changes resulting from an update to service functions in the service program; and

replacing the directory with the updated directory, wherein the updated directory is capable of including modifications to the identifiers and error information.

35. The article of manufacture of claim 34, wherein the identifier indicates an occurrence of an error at a unique location in the service program.

36. The article of manufacture of claim 34, further comprising:

if the received identifier indicates that one error did not occur during execution of the service function, then the generated return code indicates that no error occurred.

37. The article of manufacture of claim 34, further comprising:

returning additional data describing the error to the application program if the return code indicates that one error occurred.

38. The article of manufacture of claim 34, wherein the return code comprises generic error information, wherein one return code is used to provide generic error information for multiple identifiers.

39. The article of manufacture of claim 34, further comprising:

receiving data related to the failed test operation from the service program; and

including the received data related to the failed test operation within the generated error information.

40. The article of manufacture of claim 34, further comprising:

writing the generated error information to a log file.

41. The article of manufacture of claim 34, wherein the directory further maintains a generic error code in each entry, wherein the same generic error code is used for multiple identifiers providing a general description of the error state resulting from the failure of the test operation, and wherein the return code transmitted to the application program comprises the generic error code for the received identifier in the directory.

42. The article of manufacture of claim 34, wherein the application program and service program execute on different computer systems.

43. The article of manufacture of claim 34, wherein the application program and service program run on different operating system platforms.

44. The article of manufacture of claim 34, wherein the service program comprises an operating system program.

45. The article of manufacture of claim 34, wherein the steps of receiving the identifier, generating the error information, and transmitting the data are performed by a program that is external to the application program and service program.