Scenario II: Exception-initiated monitoring

Figure 1. RMFCS Scenario II: Exception-Initiated Monitoring
RMFCS Scenario II: Exception-Initiated Monitoring. This figure is explained in the surrounding text.

The concept of scenario I can easily be adapted to support exception-initiated monitoring.

This requires a Monitor III reporter address space to be running in batch mode. The sample job RMFM3B is provided to achieve this.

Whenever a new Monitor III report is produced, the ERB3RPH3 procedure can now check whether the actual performance data values exceed the thresholds.

If they do, ERB3RPH3 can activate the PWS connection by producing a predefined message, and further processing continues as in Scenario I.