Step 7. Implement Converted Rules in a Test Environment

Use the following steps to test the Control-O rules that you created in Steps 4 and 5:

1. Install INCONTROL and Control-O in a test environment, where you can perform operations without adversely affecting production at your site.
2. Specify the rule libraries created during conversion in the Rule Table list (member RULELIST) referenced by DD statement DARULLST in the Control-O monitor procedure.
3. Activate Control-O.
4. Generate events (for example, messages or commands) that should trigger Control-O rules. For example:
   • Generate messages and commands using utility IOATEST or CTOTEST.
   • Trigger time-driven rules by modifying the time of day in the system (this may require an IPL).
   • Submit jobs to trigger rules with selection criteria specifying job-related events (for example, job arrival, job ending, or job step completion).
5. Verify that the Control-O rules handled simulated events in the desired way.
   • Watch the console for messages that should be issued or suppressed by the rules.
   • Watch TSO user IDs that should receive notification of events (that is, Shout messages).
   • Review the JES console log and the Control-O Automation log for additional messages that describe how events in the test environment were handled.