Scenario I: Message-initiated monitoring

Figure 1. RMFCS Scenario I: Message-Initiated Monitoring

In this scenario, the MPF parmlib member is used for event handling and further processing of system alerts. It is assumed that the special emergency events that will trigger the monitoring task are also producing specific console messages.

Sample MPFLSTxx Entries

/*-------------------------------------------------------------*/
/* MESSAGES THAT RESULT IN AN ACTIVATION OF AN RMFCS SESSION   */
/*-------------------------------------------------------------*/
-------,
IEA995I,SUP(NO),USEREXIT(ERBCSACT),AUTO(ERBCSGUI) AUTOSTART RMFCS
IRA100E,SUP(NO),USEREXIT(ERBCSACT),AUTO(ERBCSGUI) AUTOSTART RMFCS
-------,

On the basis of this example, the following happens:

User exit ERBCSACT gets control if the supervisor produces symptom dump output (message IEA995I), or if the system resource manager has recognized an SQA storage shortage (message IRA100E).
Module ERBCSACT now issues a MODIFY command for the started task RMFCSC (Client Server Control) which may have been started automatically during system IPL.
RMFCSC then receives the name of a REXX EXEC, passed as token to the user exit through the AUTO parameter.
The REXX EXEC (here ERBCSGUI) is then executed unconditionally in the RMFCSC address space.
Immediately, ERBCSGUI requests a connection to the listening workstation.
This actual bind can be performed in batch mode by exploiting the ISPF GUI feature with the following command:
```
ISPSTART PANEL(ISR@PRIM) NEWAPPL(ISP) GUI(LU:NET_id.LU_id) +
         TITLE(RMFCS_cvtsname) GUISCRW(121) GUISCRD(32)
```
The GUI session pops up immediately, and the affected system identifies itself on panel ISR@PRIM and is also displayed as part of the window title bar.
From there, the user has unlimited access to all RMF™ Monitor III and Monitor II reports needed to analyze the critical situation.
In case of message IRA100E, the Monitor III STORC/STORCR reports would immediately provide detailed SQA storage information.
Afterwards, the session can be stopped by simply closing the GUI window.

Simultaneous client sessions with simultaneous connections to different z/OS hosts are supported.