Autonotification system for notifying recipients of detected events in a network environment

• US 5,748,884 A
• Filed: 06/13/1996
• Issued: 05/05/1998
• Est. Priority Date: 06/13/1996
• Status: Expired due to Term

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Incorporated (Verizon Communications Inc.)
• Inventors: Royce, Kevin M., Erdmann, Brian W., Scheetz, Jeffrey P., Landry, Hayes J. Jr., Cole, John D., Berry, Stanley D.
• Primary Examiner(s): Begusoliel, Jr., Robert W.
• Assistant Examiner(s): Palys, Joseph E.
• Application Number:
  US08/663,401
• Time in Patent Office: 691 Days
• Field of Search: 395/185.01, 395/185.1, 395/182.02, 395/182.13, 395/182.16, 395/733, 395/740, 395/741, 395/200.11, 395/184.01, 395/182.22, 395/200.44 , 395/591
• US Class Current: 714/57
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/301 where the computing system is a virtual computing platform, e.g. logically partitioned systems virtual machines G06F9/45533; logical partitioning of resources G06F9/5077
• CPC Class Codes: G06F 11/3017 where the computing system is implementing multitasking multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3068 where the reporting involves data format conversion
• CPC Class Codes: G06F 11/327 Alarm or error message display
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

An autonotification system that automatically performs pre-determined notification procedures based on specific messages detected from programs called traps. The present invention detects triggering events, such as job failures, abnormal ends (ABENDs), erroneous output, return codes, and successful completions. When a triggering event is detected, the system will reference data that specifies the notification service to perform. Such notification services may include the issuance of numeric pages, alpha-numeric pages, electronic mail, Problem Management Records (PMRs), and voice mail messages. The notification procedures include confirmations of receipt of notifications. The notification procedures also include automatic escalations, based on such confirmations, to notify additional personnel (default recipients) when no response or a negative response is received from the prior recipient of the notification.

Claims

1. An autonotification system for use in a network environment, wherein said network processes a job, the system comprising:

a pre-determined notification procedure having an instruction indicating a first recipient to notify when a triggering event occurs while the job is being processed;

an auxiliary procedure for entering a plurality of global variables into the system;

including a global variable to notify a default recipient different from said first recipient;

means for confirming receipt of a notification;

means for escalating said notification to said default recipient, if said first recipient does not accept and, said escalating means also escalating said notification when said first recipient does not confirm within a predetermined time period;

means for detecting one of a plurality of traps occurring from the processing of said job and generating a detection message corresponding to said trap;

means for analyzing said detection message to determine whether said trap is eligible for one of a plurality of notification services and generating an analysis message, wherein said means for analyzing comprises

an applications (APPS) process;

a user-invoked process;

a non-notification process;

a systems software process; and

a default process; and

autonotification means for automatically notifying said first recipient according to an autonotification message.

2. The system of claim 1, wherein said detection message comprises:

a job name for the job, wherein the jobname includes a high level qualifier (HLQ);

a job number for the job;

a resource access control facility (RACF) ID for the job;

a logical partition (LPAR) number identifying an LPAR on which the job executed;

a code identifying said triggering event; and

a trap ID.

3. The system of claim 2, wherein said detection message further comprises a job triggering event date/time/step entry.

4. The system of claim 1, wherein said plurality of notification services comprises one or more of:

an alpha-numeric paging notification service;

a numeric paging notification service;

an electronic mail notification service;

a program management record (PMR) notification service; and

a non-notification service.

5. The system of claim 1, wherein said autonotification means includes a traffic cop to determine which one of said plurality of notification services should be accessed.

6. The system of claim 1, wherein said analysis message comprises said detection message and a master record, the master record comprising:

a group ID;

an on/off processing switch; and

a plurality of autonotification switches, each autonotification switch corresponding to one of said plurality of notification services.

7. The system of claim 6, wherein said analysis message further comprises at least one subgroup ID.

8. The system of claim 1, wherein said autonotification message comprises said analysis message and a paging information table, wherein said paging information table comprises:

at least one paging number;

an escalation sequence, said escalation sequence including times for executing said escalation sequence; and

a security code for accessing a voice response unit (VRU).

9. The system of claim 1, wherein said autonotification message comprises said analysis message and an e-mail information table, wherein said e-mail information table comprises at least one e-mail address.

10. The system of claim 1, wherein said confirmation means includes a voice response unit.

11. An automated method of notifying a user of the occurrence of a triggering event during the execution of a job on a mainframe logical partition (LPAR) within a network environment, the method comprising the steps of:

detecting a trap;

generating a detection message corresponding to said trap;

analyzing said detection message to determine if the job is one that should be tracked, including;

determining whether autonotification should be conducted for the LPAR that the job executed on;

allocating a unique problem ID for tracking the job, if the job is one to be tracked;

matching a high level qualifier associated with the job to a master record;

determining which one of a plurality of decision-support processes should be performed; and

performing said decision-support process;

generating an analysis message;

feeding said analysis message to a traffic cop;

determining a notification service to execute; and

performing said notification service.

12. The method of claim 11, wherein said step of performing said notification service comprises the steps of:

generating an autonotification message;

generating a write to operator respond (WTOR) message containing all pertinent information for sending said notification;

sending said WTOR message to an outboard console personal computer (OBCP);

receiving an acknowledgment back;

transmitting a notification request to a voice response unit (VRU);

creating a voice response problem text to be played to the recipient of said notification;

transmitting a notification request message to an appropriate personal computer (PC) for generating said notification service;

issuing said notification;

alerting production control of the triggering event for display on a monitor;

informing said VRU of receipt of said notification; and

selecting one of three options to listen to the problem, transfer the problem to a production control center, and exit VRU.

13. The method of claim 12, wherein said option to listen to the problem further comprises the step of selecting one of the further options of acknowledging receipt of the problem, rejecting responsibility for the problem, replaying the problem description, and requesting additional information about the problem.

14. The method of claim 13, wherein said selection of said option acknowledging receipt of the problem further comprises the steps of:

recording the recipient'"'"'s name;

acknowledging acceptance of the problem to the appropriate LPAR; and

clearing all data corresponding to the accepted problem.

15. The method of claim 13, wherein said selection of said option rejecting responsibility for the problem further comprises the steps of:

transferring the recipient back to said step of selecting one of three options;

determining next escalation; and

triggering said notification for next escalation.

16. The method of claim 11, wherein said step of performing said notification service comprises the steps of:

generating a problem management report (PMR);

storing said PMR into a global variable;

transmitting said global variable to a central repository on the same LPAR where a PMR system resides; and

loading said global variable into said PMR system using time-of-day rules.

17. The method of claim 11, wherein said step of performing said notification service comprises the steps of:

recording the triggering event;

storing one of said analysis message and said detection message into a flat file;

copying said flat file to a dataset; and

transmitting said flat file to a central site for storage and future reference.

18. A method of invoking time sensitive processes and loading global variables from data control tables into an Autonotification system, the steps comprising:

executing a single time-of-day rule every minute;

triggering a process detector that reads in a program control table specifying the cycle and frequency of each time sensitive process used by the system and loads the global variables from the data control tables into the system;

executing each time sensitive process in said program control table per table instructions;

loading the data control tables into at least two partitioned datasets; and

transmitting said partitioned datasets into global variables on a plurality of mainframe logical partitions (LPARs) using daily batch transmission.

19. A computer program product for use within a multiuser data processing system environment, comprising:

a computer usable medium having computer readable program code means embodied in the medium for enabling a computer to provide an autonotification system within a networking environment that notifies a recipient of the occurrence of a triggering event during execution of a job on a mainframe logical partition (LPAR), the computer program product having;

computer readable program code means for enabling the computer to detect one of a plurality of traps occurring from the execution of a job and generate a detection message corresponding to the trap wherein said plurality of traps comprises

a time-of-day rule trap;

a message rule trap; and

a user-invoked rule trap;

computer readable program code means for enabling the computer to analyze said detection message to determine whether said trap is eligible for one of a plurality of notification services and to generate an analysis message;

computer readable program code means for enabling the computer to generate an autonotification message and to notify a first recipient using one of the notification services;

computer readable program code means for enabling the computer to escalate a notification to a default recipient different from said first recipient;

computer readable program code means for enabling the computer to confirm receipt of said notification; and

computer readable program code means for enabling the computer to enter a plurality of global variables into the system.

20. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps within a multiuser data processing system environment for providing an autonotification system within a networking environment for notifying a recipient of the occurrence of a triggering event during execution of a job on a mainframe logical partition (LPAR), the method steps comprising at compile time:

detecting a trap;

generating a detection message corresponding to said trap;

analyzing said detection message to determine if the job is one that should be tracked, including;

determining whether autonotification should be conducted for the LPAR that the job executed on;

allocating a unique problem ID for tracking the job, if the job is one to be tracked;

matching a high level qualifier associated with the job to a master record;

determining which one of a plurality of decision-support processes should be performed; and

performing the decision-support process;

generating an analysis message;

feeding said analysis message to a traffic cop;

determining a notification service to execute; and

performing said notification service.

21. The method of claim 20, wherein said step of performing said notification service comprises the steps of:

generating an autonotification message;

generating a write to operator respond (WTOR) message containing all pertinent information for sending said notification;

sending said WTOR message to an outboard console personal computer (OBCP);

receiving an acknowledgment back;

transmitting a notification request to a voice response unit (VRU);

creating a voice response problem text to be played to the recipient of said notification;

transmitting a notification request message to an appropriate personal computer (PC) for generating said notification service;

issuing said notification;

alerting production control of the triggering event for display on a monitor;

informing said VRU of receipt of said notification; and

selecting one of three options to listen to the problem, transfer the problem to a production control center, and exit VRU.

22. The method of claim 21, wherein said option to listen to the problem further comprises the step of selecting one of the further options of acknowledging receipt of the problem, rejecting responsibility for the problem, replaying the problem description, and requesting additional information about the problem.

23. The method of claim 22, wherein said selection of said option for acknowledging receipt of the problem further comprises the steps of:

recording the recipient'"'"'s name;

acknowledging acceptance of the problem to the appropriate LPAR; and

clearing all data corresponding to the accepted problem.

24. The method of claim 22, wherein said selection of said option for rejecting responsibility for the problem further comprises the steps of:

transferring the recipient back to the step of selecting one of three options;

determining next escalation; and

triggering another notification.

25. The method of claim 20, wherein said step of performing said notification service comprises the steps of:

generating a problem management report (PMR);

storing said PMR into a global variable;

transmitting said global variable to a central repository on the same LPAR where a PMR system resides; and

storing said global variable into said PMR system using time-of-day rules.

26. The method of claim 20, wherein said step of performing said notification service comprises the steps of:

recording said triggering event;

storing said analysis message into a flat file;

copying said flat file to a dataset; and

transmitting said flat file to a central site for storage and future reference.

27. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps within a multiuser data processing system environment for invoking time sensitive processes and loading global variables from data control tables into an autonotification system, the method steps comprising at compile time:

executing a single time-of-day rule every minute;

triggering a process detector that reads in a program control table specifying the cycle and frequency of each time sensitive process used by the system and loads the global variables from the data control tables into the system;

executing each time sensitive process entry in said program control table per table instructions;

loading data control tables into at least two partitioned datasets; and

transmitting said partitioned datasets into global variables on a plurality of mainframe logical partitions (LPARs) using daily batch transmission.

28. An autonotification system for use in a network environment, wherein said network processes a job, the system comprising:

a pre-determined notification procedure having an instruction indicating a first recipient to notify when a triggering event occurs while the job is being processed;

an auxiliary procedure for entering a plurality of global variables into the system, including a global variable to notify a default recipient different from said first recipient;

means for confirming receipt of a notification;

means for escalating said notification to said default recipient, if said first recipient does not accept and, said escalating means also escalating said notification when said first recipient does not confirm within a predetermined time period;

means for detecting one of a plurality of traps occurring from the processing of said job and generating a detection message corresponding to said trap, wherein said plurality of traps comprises;

a time-of-day rule trap that executes according to a pre-defined schedule;

a message rule trap that executes according to an operating system message; and

a user-invoked rule trap that executes according to a user-defined instruction;

means for analyzing said detection message to determine whether said trap is eligible for one of a plurality of notification services; and

autonotification means for automatically notifying said first recipient.

29. The system of claim 28, wherein said plurality of traps further comprises a system software rule trap that executes according to an external program.

30. An autonotification system for use in a network environment, wherein said network processes a job, the system comprising:

a pre-determined notification procedure having an instruction indicating a first recipient to notify when a triggering event occurs while the job is being processed;

an auxiliary procedure for entering a plurality of global variables into the system, including a global variable to notify a default recipient different from said first recipient, wherein said auxiliary procedure includes transferring a plurality of data control tables into global variables, said data control tables comprising at least two partitioned data sets, said partitioned data sets comprising;

an application-related data set; and

a system control data set;

means for confirming receipt of a notification; and

means for escalating said notification to said default recipient, if said first recipient does not accept and, said escalating means also escalating said notification when said first recipient does not confirm within a predetermined time period.

31. The system of claim 30, wherein said application-related data set comprises:

a master record table;

a paging information table;

an e-mail information table; and

a late job table.

32. The system of claim 30, wherein said system control data set comprises:

an LPAR table;

a transmission control table; and

a program control table.

33. An autonotification system for use in a network environment, wherein said network processes a job, the system comprising:

a pre-determined notification procedure having an instruction indicating a first recipient to notify when a triggering event occurs while the job is being processed;

an auxiliary procedure for triggering a time-of-day rule to invoke a plurality of time sensitive processes and for entering a plurality of global variables into the system, including a global variable to notify a default recipient different from said first recipient;

means for confirming receipt of a notification; and

means for escalating said notification to said default recipient, if said first recipient does not accept and, said escalating means also escalating said notification when said first recipient does not confirm within a predetermined time period.

34. The system of claim 33, further comprising:

means for detecting one of a plurality of traps occurring from the processing of said job and generating a detection message corresponding to said trap;

means for analyzing said detection message to determine whether said trap is eligible for one of a plurality of notification services and generating an analysis message; and

autonotification means for automatically notifying said first recipient according to an autonotification message.

35. The system of claim 34, wherein said detection message comprises:

a job name for the job, wherein the jobname includes a high level qualifier (HLQ);

a job number for the job;

an resource access control facility (RACF) ID for the job;

a logical partition (LPAR) number identifying an LPAR on which the job executed;

a code identifying said triggering event; and

a trap ID.

36. The system of claim 34, wherein said plurality of notification services comprises one or more of:

an alpha-numeric paging notification service;

a numeric paging notification service;

an electronic mail notification service;

a program management record (PMR) notification service; and

a non-notification service.

37. The system of claim 34, wherein said plurality of traps comprises:

a time-of-day rule trap that executes according to a pre-defined schedule;

a message rule trap that executes according to an operating system message; and

a user-invoked rule trap that executes according to a user-defined instruction.