Exception Monitor samplers

The Exception Monitor helps you detect potential problems by monitoring thresholds that you establish and sending a warning message when a threshold is exceeded.

You can use the Exception Monitor in the following ways:

  • When MainView SYSPROG Services is operating as a batch job or started task

    When the Exception Monitor is operating as a batch job or a started task, warning messages are sent to the console.

  • From the MainView for z/OS product

    When you use the Exception Monitor from the MainView for z/OS product, you can access warning messages from the WARN view and you can send warning messages (optionally) to the console.

    For more information, see the description for the LCLAEW parameter in INSYS0.

  • From the MainView AutoOPERATOR for z/OS product option

In all environments, you can also specify that warning messages are directed to the AOAnywhere API in MainView AutoOPERATOR. For more information, see the description for the AEWALERT parameter in INSYS0.

There are two ways to control the Exception Monitor samplers:

  • Using the WARNING Service, which is described in this publication

  • Through the EMSTAT view. For more information, see Using the Exception Monitor.

In all environments, you must add to PARMLIB member PWSCPMxx the Exception Monitor samplers and their parameters that you want to use, where xx is a user-defined two-character suffix. For more information, see the description for the AEWSTART parameter in INSYS0.

You can use the WARNING service to dynamically change individual parameters on active samplers. For more information, see WARNING.


The following topics provide detailed information about the Exception Monitor samplers, including proper syntax, required and optional parameters, and usage examples:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*