Operator access to monitoring applications

Description Submit all comments and votes

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is in the field of monitoring and alarm systems, and more particularly, the invention is directed to a display system which facilitates the display of status information which reflects the current status of multiple host based programs on a single display screen. The display system is called Multiple System Alert Monitor (MSAM).

2. Background of the Invention

Monitoring and alarm systems are required for a wide variety of applications ranging from simple mechanisms to rather complex processes. An example of a simple mechanism requiring a monitoring and alarm system would be a home heating system, and an example of a complex process also requiring a monitoring and alarm system would be a nuclear reactor.

Monitoring systems acquire information from a variety of sources. The information may come from sensors attached to devices measuring temperature and pressure, or they may come from another computer connected by a communications interface. An example of a monitoring system acquiring information from sensor information can be found in U.S. Pat. No. 4,588,987, to Stephens, issued May 13, 1986 and U.S. Pat. No. 4,471,348, to London et al., issued Sept. 11, 1984. These patents discuss techniques for acquiring sensor information from a plant environment, filtering the information and formatting it for display on a graphics display screen.

Monitoring systems for computer applications include the system described in U.S. Pat. No. 4,348,739, to Deaver et al., issued Sept. 7, 1982. The Deaver et al. system provides operator information on the characteristics of a data communication system. The information is displayed on a single terminal in the form of a table of summary information. The terminal is connected to the communication system and uses a handshaking protocol to obtain information. The information displayed is very important to the data processing staff because it provides management information for the communications network.

As monitoring capabilities evolved to more complex techniques, the ability to provide multiple virtual displays on a single display screen became necessary. An example of this type of processing is disclosed in the aforementioned patent to London et al. The system disclosed in the London et al. patent assigns each virtual display information for its own use. The information for each of the virtual displays is obtained and formatted for display on the separate sections of the display screen assigned to each of the virtual displays. With the advent of color displays, monitoring packages began to use color graphics to accentuate trends and alarm situations to assist the operator in determining where the problem occurred. An example of this approach is illustrated in U.S. Pat. No. 4,375,079, to Ricketts et al., issued Feb. 22, 1983. This patent describes the IBM 3279 color display and how it can be utilized to display color graphics. The color graphics include bar charts, pie charts and line graphs.

One system operation that can be monitored with this system is the IBM Customer Information Control System (CICS). This system manages a network of terminals and other communications devices attached to a host processor. A description of the operation of this system can be found in the Customer Information Control System/Virtual Storage (CICS/VS) General Information Manual, GC33-0155-1 published by International Business Machines Corporation. Due to the complexity of CICS, there are a number of monitoring programs that support the tuning and management of the system. The IBM Network Performance Monitor (NPM) aids network support personnel in managing the performance and growth of communications networks. A description of NPM can be found in the Network Performance Monitor General Information Manual, GH20-6539 published by International Business Machines Corporation. CICS Performance Analysis Reporting System (CICS/PARS) provides online display capabilities, system alert monitoring functions, problem determination aids and extensive batch reporting and analysis capabilities. A description of CICS/PARS can be found in CICS/OS/VS Performance Analysis Reporting System/MVS General Information System, GH20-6836-0 published by International Business Machines Corporation.

Today, with the proliferation of personal computers (PCs), systems are taking advantage of the user acceptance of PCs for performing functions locally to offload host processes. PCs are often attached to a host processor to monitor and collect information and to display the information on a locally attached graphics device and printer. An example of this approach is found in Sharman, "Multi-Thread Host Server For PC Support", IBM Technical Disclosure Bulletin, Vol. 28, No. 9, Feb. 1986. Sharman discloses a technique for using PCs in a CICS environment. The PCs are used as local file, print and message servicers. Rather than print a report on a remote host printer, each user employing the disclosed technique has the capability of locally printing a report, storing a host file and interacting with a CICS application.

Another pertinent example of such a monitoring application residing on a PC is discussed by Gallant, "Outspoken Micros Keep Support Center Humming", Computerworld, Apr. 8, 1985, at page 1, col. 1. Gallant's article discusses a PC based CICS monitoring system. The PCs are tied into four major on-line CICS applications that impact most of the company's 1200 employees. The PCs use a voice synthesizer to announce alerts while simultaneously calculating response times, maintaining history information and charting the results for tracking service.

The problem with even the most advanced of these systems is the inability to display information from multiple host applications on a single display screen. A significant amount of time is spent by the operator moving from one monitoring application to another trying to identify specific problems. The issue is further compounded when there are multiple copies of CICS running on a single processor.

SUMMARY OF THE INVENTION

It is therefore an object of the present invention to provide a monitoring system that concurrently monitors multiple host applications and displays the information on a single display screen.

It is a further object of the invention to provide a monitoring system that summarizes the information from host monitoring applications and displays the information on a single display screen.

It is another object of the invention to rely upon the graphics and multi-tasking capabilities of a microprocessor system with a host communication interface, such as the IBM 3270-PC, to communicate with multiple host monitoring applications and display summary information in the form of tabular reports, graphs and other status information.

It is yet another object of the invention to employ the microprocessor system speaker to emit an audible tone of varying frequency and duration for indicating the attainment of user definable thresholds.

It is still another object of the invention to automatically translate the monitoring and alarm messages from host applications into voice messages to alert the operator to a specific problem.

According to the invention, these objects are accomplished by providing a computer program MSAM which runs on a microprocessor system with a host communications interface such as an IBM 3270-PC. MSAM is a single program which gathers information from multiple CICS host regions and displays the information on a single display screen. The information includes graphics, reports, monitoring and alarm information. The display screens that the user is presented with are in a format that correspond to the host display screens that are commonly employed in large data processing (DP) centers today.

MSAM reduces the overhead of the communications between the microprocessor and the host by employing a structured data stream that eliminates the need to pass large amounts of information. The microprocessor receives existing, summarized information and reduces the information to a complete, accurate picture of the multiple applications that enables the operator to have timely information and respond effectively in a complex DP environment.

The alarm information is organized to effectively call the operator's attention to the key problem quickly and efficiently. Key alarm messages can be designated as voice messages which are automatically translated and output as synthesized voice alerts. Threshold conditions can be called to the operator's attention by specifying tolerances, that once achieved, trigger an electronic tone of designated duration and frequency.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, aspects and advantages of the invention will be better understood from the following detailed description of a preferred embodiment with reference to the drawings, in which:

FIG. 1 is a screen print showing an example of a CICS/PARS alert monitor display;

FIG. 2 is a screen print showing an example of an NPM display alert message;

FIG. 3 is the functional organizational chart of the system according to the present invention;

FIG. 4 is a screen print showing the alert monitor invocation screen;

FIG. 5 is a screen print showing the initial system configuration screen;

FIG. 6 is a screen print showing an example of a MSAM graphics screen;

FIGS. 7 to 23 are the detailed flowcharts of the HOST & PC logic of the invention;

FIGS. 24 to 36 are screen prints showing the sample session screens; and

FIG. 37 is a screen print of the current voice parameters MSAM screen.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT OF THE INVENTION

MSAM HARDWARE/SOFTWARE ENVIRONMENT

The disclosed invention is described using an IBM 3270-PC; however, one of ordinary skill in the art will recognize that any microprocessor that has the capability of communicating with a host computer could be substituted for the IBM 3270-PC. The Multiple System Alert Monitor (MSAM) relies upon many standard IBM products to provide the advanced monitoring capabilities. These products include the Personal Computer (PC)/Disk Operating System (DOS). PC/DOS acts as the operating system for the IBM 3270-PC. The IBM 3270-PC is an IBM product that provides cooperative processing between PC and host display programs. It combines the functions of a 3270 terminal with the flexibility of a PC. With one keyboard and one display, the user has access to a PC session and up to four host sessions. The user can press the JUMP key to move between the applications. The IBM 3270-PC allows the operator to divide the display into multiple windows of user-specified size. The windows can be distributed between multiple host sessions and a single DOS session. The host sessions are active at the same time; however, the user can only interact with one session at a time. This capability is important to allow multiple host sessions to be processed in the background as a single display is presented to guide the user to the key problems.

There are various models of the IBM 3270-Personal Computer(PC) with modular features. These features include additional memory, medium to high resolution monochrome and color graphics displays and a PC/Advanced Technology (PC/AT) version. Additional information describing the IBM 3270-PC is contained in the IBM 3270-Personal Computer Control Program User's Guide and Reference, SC23-0103 and the Introduction and Preinstallation Planning Guide, GA23-0179; both are published by International Business Machines Corporation.

The IBM 3270-PC Control Program is also used as a window and task manager for the IBM 3270-PC. This program interfaces between PC/DOS and the 3270-PC hardware to perform the functions of multiple 3270 displays. The IBM 3270-PC Control Program manages the keyboard and display to allow the user to interface with up to four host sessions and one PC session, one at a time. The control program also contains the Applications Programming Interface (API) which contains the support for the structured field communications. The structured field communications is used to support communications between MSAM and the HOST. This program is discussed in detail in the IBM 3270-PC Control Program Programming Guide, GA23-0221 published by International Business Machines Corporation. These products are used in conjunction with unique displaying, reporting, monitoring and alarming code to implement the invention on an IBM 3270-PC.

HOST SOFTWARE

The hosts that the application is monitoring are required to have some other IBM products. These include the Customer Information Control System (CICS). As mentioned earlier, CICS is a general purpose data communication monitor that reduces the effort necessary to implement terminal-oriented transaction applications. CICS is used around the world to enable applications ranging from payroll to inventory control to function interactively and handle a large number of displays. In a DP environment it is very important to manage CICS to allow users to enjoy quick response times to their inquiries in an interactive environment. Because of this need, CICS/Performance Analysis Reporting System (CICS/PARS) was created. This product aids network support personnel in managing the performance and growth of their CICS environment. CICS/PARS has a complete set of monitoring tools to allow a user at a host display to monitor a CICS application and create the reports necessary to track the performance of the application. One function of CICS/PARS is the alert monitor. The alert monitor allows thresholds for CICS system resources to be set and provides display capability to monitor these resources. FIG. 1 shows an example of a CICS/PARS alert monitor display. An additional feature of CICS/PARS is the graphical display of selected system resources using the IBM Graphical Data Display Manager (GDDM). GDDM provides full-screen extended alphanumeric and graphic support for the IBM 3270 display family including the 3270-PC family of products. Application programs such as CICS/PARS call GDDM routines to create graphic displays. Details of the GDDM product are presented in the GDDM General Information Manual, GC33-0108 published by International Business Machines Incorporated. The graphical displays that CICS/PARS creates are displayable on any of the host sessions active on the IBM 3270-PC. A complete description of CICS/PARS is contained in the CICS/OS/VS Performance Analysis Reporting System User's Guide and Reference, SH20-6837.

If communications information for the host is desired, the host must have the Network Performance Monitor (NPM) installed. This product aids network support personnel in managing the performance and growth of their communications network by supplying on-line statistics to allow real-time analysis of a network. The functions that NPM supplies are similar to CICS/PARS except that they are concerned with communications networks. An operator can enter thresholds corresponding to network tolerances. Should a threshold be exceeded, a message is displayed which indicates the nature of the problem. An example of an NPM display message is shown at the top of FIG. 2. A complete description of NPM appears in the Network Performance Monitor User's Guide and Reference, SH20-6360.

MSAM APPLICATION ENVIRONMENT

The application program that enables the disclosed invention resides on the IBM 3270-PC and communicates with CICS/PARS and/or NPM to obtain status information on the host CICS applications and the host communications environment. CICS/PARS collects status information from the host applications and sends it to the 3270-PC application to be processed. The interface between CICS/PARS and the IBM 3270-PC application is a Structured Field Communication interface. Structured Field Communication allows an efficient and clean method of transmitting data between the host and the 3270-PC. The data is transferred in the structure specified depending on the one character TYPE field.

TYPE FIELD DESCRIPTION

The TYPE field is a one character indication which communicates which action has been taken by the source of the communication or should be taken by the destination of the communication. The TYPE field is limited to a single character because that character fits conveniently after the communications header byte to word align any data in the communication. Based on the type of communications, the TYPE field may be followed by a variable amount of data; although, some transactions have no data following the TYPE field.

The structures associated with TYPE fields have a letter prefix associated with the structure name that corresponds to the one byte values. The structure prefix for the TYPE values Hex 00 and Hex 7F MSAM to HOST communications is "P". The structure prefix for the TYPE values Hex 80 and Hex FF for HOST to MSAM communications is "H".

Each set of 16 TYPE codes correspond to a similar task. For example, 30-3F are the TYPE BYTES associated with the MSAM alert monitor function. In addition the TYPE codes associated with a 3270-PC MSAM function are separated by 80 hex from the host TYPE codes. Thus, BO-BF are the TYPE BYTES associated with the alert monitor function on the HOST. Similarly, 30-3F are the TYPE BYTES associated with the MSAM alert monitor function.

As much as possible, the data in the communications buffer is passed as short integers of two bytes. String data will be passed as single bytes of EBCDIC.

COMMUNICATIONS CHARACTERISTICS

The MSAM initiated communications transaction TYPE BYTES are defined below:

__________________________________________________________________________ Alert Monitor Gateway Startup (30-37) (1) Define P --A --BUSY HEX 31 (gateway session already in progress) Alert Monitor Invocation Group (38-3F) (1) Define P --A --NO --GATE HEX 38 (gateway session not yet established) (2) Define P --A --TOO --MANY HEX 39 (attempt to start more than 17 AM sessions) (3) Define P --A --GOOD --DATA HEX 3B (valid data received from HOST for starting summary line) (4) Define P --A --BAD --DATA HEX 3C (HOST has sent invalid start up data - no summary line) Alert Monitor Gateway Execution Group (40-4F) (1) Define P --A --READ HEX 40 (MSAM requests that HOST read AM Status Array to send to MSAM) (2) Define P --A --X --SESS HEX 43 (MSAM desires to delete a subset of AM invokes (see del --sess struct)) (3) Define P --A --X -- ALL HEX 44 (MSAM desires to terminate all AM invokes) Graphic Data Group (50-5F) (1) Define P --G --PFKEY HEX 52 (MSAM is sending the user selected PF Key to the HOST) (2) Define P --G --NO HEX 53 (PC does not have an APA card) (3) Define P --G --BUSY HEX 54 (MSAM graphics session is currently in progress) (4) Define P --G --ERROR HEX 55 (A Virtual Device Interface (VDI) error is cancelling an MSAM graphics session) (5) Define P --G --X --DATA HEX 56 (MSAM received unexpected data - no graphics session) (6) Define P --G --REFRESH HEX 57 (MSAM requesting graphic data refresh) Error Handling Group (70-7F) (1) Define P --STOP --REQUEST HEX 7F (Sent in two cases: (A) The Control Break Key is struck at any time when using MSAM (If control break is pressed from a graphics screen, the HOST should respond as if a quit (exit CICS/PARS) has been pressed. In a gateway session, the HOST should kill all active alert monitors and exit CICS/PARS.) (B) PF10 is pressed from the MSAM Main Menu) __________________________________________________________________________

The following HOST initiated TYPE BYTES are defined:

__________________________________________________________________________ Alert Monitor Gateway Startup (B0-B7) (1) Define H --A --ALIVE HEX B0 (HOST is starting a gateway session - sends h --am --start) Alert Monitor Invocation Group (B8-BF) (1) Define H --A --INVOC HEX B8 (HOST is starting another alert monitor for MSAM summary lines) (2) Define H --A --GOOD --ID HEX BA (HOST has access to the AM Status Array) (3) Define H --A --BAD --ID HEX BD (HOST does not have access to the AM Status Array) Alert Monitor Gateway Execution Group (C0-CF) (1) Define H --A --GOOD --READ HEX C0 (HOST has data from AM Status Buffer to send to MSAM) (2) Define H --A --NO --DATA HEX C1 (No updates to AM Status Buffer since previous MSAM request) (3) Define H --A --X --ACK HEX C3 (HOST is confirming attempt to delete a subset of AM invokes) (4) Define H --A --X --ALL HEX C4 (HOST is confirming attempt to delete all AM invokes) Graphic Data Group (D0-DF) (1) Define H --G --DATA --REPLY HEX D1 (HOST is sending data to MSAM to display graphically) (2) Define H --G --PFKEY --ACK HEX D2 (Ack of a PF key sent to the HOST by MSAM) Error Handling Group (F0-FF) (1) Define H --STOP --REPLY HEX FF (Ack that MSAM is terminating) __________________________________________________________________________

The data that follows the different TYPE fields is described below:

______________________________________ Data For TYPE H --G --DATA --REPLY (1) Define BYE --GRAPH HEX 0000 (Exit from alert monitor graph) (2) Define ALT --GRAPH HEX 0001 (Alert monitor graph) (3) Define VSL --GRAPH HEX 0002 (Low Virtual Storage graph) (4) Define VSH --GRAPH HEX 0003 (High Virtual Storage graph) (5) Define DSA --GRAPH HEX 0004 (Dynamic storage graph) (6) Define HIS --GRAPH HEX 0005 (DSA and OSCOR history graph) (7) Define BYE --GR --VSE HEX 0010 (Exit from alert monitor graph) (8) Define ALT --GR --VSE HEX 0011 (Alert monitor graph) (9) Define VSL --GR --VSE HEX 0012 (Low Virtual Storage graph) (10) Define VSH --GR --VSE HEX 0013 (High Virtual Storage graph) (11) Define DSA --GR --VSE HEX 0014 (Dynamic storage graph) (12) Define HIS --GR --VSE HEX 0015 (DSA and OSCOR history graph) Data following P --G --PFKEY (Function Key Pressed) (1) Define PF1 HEX 0100 (PF1 key pressed on MSAM) (2) Define PF2 HEX 0200 (PF2 key pressed on MSAM) (3) Define PF3 HEX 0300 (PF3 key pressed on MSAM) (4) Define PF4 HEX 0400 (PF4 key pressed on MSAM) (5) Define PF5 HEX 0500 (PF5 key pressed on MSAM) (6) Define PF6 HEX 0600 (PF6 key pressed on MSAM) (7) Define PF7 HEX 0700 (PF7 key pressed on MSAM) (8) Define PF8 HEX 0800 (PF8 key pressed on MSAM) (9) Define PF9 HEX 0900 (PF9 key pressed on MSAM) (10) Define PF10 HEX 0A00 (PF10 key pressed on MSAM) (11) Define PF11 HEX 0B00 (PF11 key pressed on MSAM) (12) Define PF12 HEX 0C00 (PF12 key pressed on MSAM) (13) Define H --PA1 HEX 0D00 (PA1 pressed on MSAM) (14) Define H --PA2 HEX 0E00 (PA2 pressed on MSAM) (15) Define H --PA3 HEX 0F00 (PA3 pressed on MSAM) (16) Define H --ENTER HEX 1000 (Enter pressed on MSAM) (17) Define H --CLEAR HEX 1100 (ESC key pressed on MSAM - interpret as CLEAR on HOST) ______________________________________

The different communications buffers and their structures are listed below to describe the traffic between MSAM and the HOST.

______________________________________ NAME SIZE(bytes) DESCRIPTION ______________________________________ g --dsa 44 DSA Graph data g --vsl 58 VSL Graph g --vsh 44 VSH Graph g --his 840 History Graph h --alt 162 Alert Monitor Graph HOST g --alt 162 Alert Monitor Graph MSAM ______________________________________

______________________________________ STRUCTURE SIZES ASSOCIATED WITH THE Alert Monitor Function NAME SIZE(bytes) DESCRIPTION ______________________________________ h --sys --term --id 14 handshaking information h --am --start 32 add a new summary line p --am --start 32 h --am --start MSAM reformatted h --a --rec 22 AM status array p --a --rec 24 h --a --rec MSAM reformatted h --a --array[ ] 17*22 AM is 17 (h --a --rec's) p --a --array[ ] 17*24 AM status array MSAM p --a --ctrl 52 record of the control array p --ctrl[ ] 17*52 A p --a --ctrl for the 17 sess. del --sess 18 delete sessions array sf --fun 6 func. code to func. maps time --out 6 structure of timeouts m. #s t --o --values[ ] 6*6 array of type time --out t --out 10 timeouts and time values t --out[ ] 6*10 A t --out for each pending m. ______________________________________

The following structure is passed from the HOST to MSAM at gateway initiation with the H.sub.-- A.sub.-- ALERT transmission. It is passed back with the P.sub.-- A.sub.-- GOOD.sub.-- DATA at each alert invocation. The actual byte assignment is:

______________________________________ 0-3 sysid 4-7 termid 8-9 HOST index 10-11 MSAM slot number 12-13 Host operating system (FFFF is MVS, 0000 is VSE) ______________________________________

The TYPE field plays a critical role in defining the communication's buffer to the HOST and to MSAM. The number of bytes of data is dependent on the value of the TYPE field. For example, if the TYPE field's value is hex 003A, there is no data and the communications buffer is interpreted to mean that the 3270-PC is requesting the host to send the start values for the status information. Alternatively, if the TYPE field's value is hex 0001, the 3270-PC interprets the data following the TYPE field to be an alert monitor graph.

SYSTEM INITIALIZATION

Referring now to the drawings and more particularly to FIG. 3, there is shown the organizational chart of the system according to the invention. When MSAM is invoked at 301 on an IBM 3270-PC, an initial logo display is presented at 302 to the user. The user presses the enter key to enter the system. When the system is initially started at 303, the user presses the JUMP key to select a host session. The user logs on to the CICS/PARS session that he desires to dedicate as a gateway between CICS/PARS and the 3270-PC. The 3270-PC screen dedicated to this function remains active until the last CICS/PARS alert monitor is cancelled.

Once the gateway session is established, the user presses the JUMP key to select a second host session. The user logs on to the first CICS session that he wishes to monitor and brings up the Alert Monitor Invocation screen shown in FIG. 4. The first time the system is started, the system configuration is presented to the user on the configuration screen shown in FIG. 5. The options are listed on the left side for the user's review. Characteristics that are reflected on this display include the model of IBM 3270-PC, the IBM 3270-PC Control Program Release Level, the type of IBM 3270-PC display, the existence of All Points Addressable and Programmed Symbols, and the mode of graphics supported. The configuration information on these displays are useful for product support because they provide configuration information that makes it easier to identify the problem the user is experiencing.

PROGRAM FUNCTIONAL OVERVIEW

The functions available to the user are indicated in the four boxes under the MAIN screen 304 in FIG. 3. These are the Function Key(Fkey) functions 305, the Network Performance Monitor (NPM) data functions 306, the CICS/PARS data functions 307 and the Graphics Functions 308. The function key functions 305, include: F1 describes the functions 309 of the other Fkeys at 310. F2 311 executes a DOS command 312 such as displaying a directory listing of your disk. F4 313 changes the level of the history collection 314 to increase or decrease the amount of information that is collected. As F5 is pressed, selections are rotated through Collect All Summary Lines to Collect Exceeded Thresholds Only to Collect No Summary Lines. F6 enters the Voice definition screen; and F8 315 cancels a CICS/PARS session 316.

NPM MONITORING

MSAM monitors NPM screens for the purpose of detecting an alert message from NPM. This removes the operator from the responsibility of monitoring one or more physically detached terminals for a NPM alert condition. To invoke NPM monitoring 306, the user must use one of the host sessions on the IBM 3270-PC to access NPM and set the threshold monitoring parameters. More information on these displays and their functions can be found in the Network Performance Monitor General Information Manual, GC33-6539 published by International Business Machines Corporation. The session used to set the thresholds must remain dedicated to NPM so that the presence of an alert message may be detected by MSAM.

Information from NPM is obtained through Screen Captures. Screen Capture allows MSAM to access the host screen images. MSAM processes NPM screens by distinguishing the screen of interest from the other screens, picking out the significant information from the screen and transforming the information into usable information. Since screen capture is used, no structures are needed for communication.

CICS/PARS MONITORING

The CICS/PARS data 307 display screen allows the user to view summary line descriptions of CICS system resources which are passed via a gateway link between the IBM 3270-PC and the CICS/PARS application residing on the host. This gateway session acts as the data channel for all system resource summary line information passing between the IBM 3270-PC and the CICS/PARS application. The actual communication is by means of a structured buffer described field. The structured field communication provides an efficient method of transmitting data between a host and an IBM 3270-PC. The data stream is reduced to the minimal amount of summary in