Starting exception processing when the OMEGAMON Collector is started
When the OMEGAMON® Collector is started, its startup parameters determine whether exception events are to be processed. Dependent on which exception events are specified, the appropriate traces are started. If an Exception Threshold data set with exception criteria is already available, it can be specified in the OMEGAMON Collector startup parameters. By this means, exception processing automatically starts with predefined exception thresholds whenever the OMEGAMON Collector is started.
For more information about the Exception Threshold data set, a sample data set provided with the product, its data set attributes, and how its content can be modified, see the Reporting User's Guide.
For more information about OMEGAMON Collector startup parameters, see the topic about configuring OMEGAMON Collector for exception processing in Monitoring Performance from the OMEGAMON Classic Interface. The EXCEPTIONEVENT startup parameter determines the events, and the AUTOEXCPTHNAME startup parameter specifies the name of the Exception Threshold data set that is to be used at startup.
If this means of starting exception processing is used, and if the content of the Exception Threshold data set is modified while the OMEGAMON Collector is running, remember to refresh the environment if you want the new exception criteria to be recognized.
Refer to How to restart exception processing (REINIT command) for more details.