You can use several methods to automate your system and test your automation rules. The following lessons describe the various automation methods and the corresponding lessons:
AOF Edit (OPSVIEW option 2.1) lets you create rules using the OPS/REXX programming language.
You can test and verify your automation rules before they get into a production environment.
You can establish another message suppression rule, and you can establish a test command rule.
You can use rule sets to group rules in a meaningful way. These groups are called rule sets.
Enabling and disabling rules and rule sets is how you turn them on and off.
EasyRule (OPSVIEW option 2.3) helps you create rules that respond to various system events, including system messages. EasyRule lets you modify the display of system console messages without the need for programming.
Note: To create more complex rules, you use the AOF edit facility rather than EasyRule.
The Automation Analyzer (OPSVIEW option 7.2) examines and displays a statistical analysis of the message activity of your system. You can use this information to choose the messages you want to suppress. Then, you create message suppression rules from the panels of the Automation Analyzer directly.
Most z/OS installations use the IBM product for message suppression, named the Message Processing Facility (MPF). CA OPS/MVS provides an MPF conversion facility (OPSVIEW option 7.3) that lets these installations migrate without losing the time that they have invested in MPF. The MPF conversion facility reads messages from the MPF message suppression list and generates CA OPS/MVS rules automatically.
Important! The MPF conversion facility is limited to simple suppression entries. Messages regarding console colors and exit information are not automatically processed. If you use the MPF conversion facility, you must modify parmlib to remove message suppression.
|
Copyright © 2014 CA.
All rights reserved.
|
|