There are three types of rulesets: test stream, application, and system. A test stream can be run with more than one type of ruleset. CA Verify for CICS will try to apply all of the rules from all of the rulesets and will inform you if any conflicts occur.
Note: There is a hierarchy in applying rulesets. During logging, system rulesets are applied first, application next, and test stream rulesets last. During a run, test stream rulesets are applied first, application next, and system rulesets last.
A test stream ruleset is the most specific. Use it to identify very specific changes for a test stream, such as fields that have moved their position on a screen.
An application ruleset is the next most specific. It is most often used for screens that are common within an application, such as the application main menu. By creating an appplication-level ruleset, changes to the main menu can be identified in one ruleset, but applied to more than one test stream (for example, all test streams whose application node name matches the node name of the application ruleset).
A system ruleset is the least specific. Use it to apply a change to all screens across all applications.
The type of ruleset you create is determined by how it is named; see the section Name the Ruleset for details.
The procedure for creating any type of ruleset is explained in the following table.
|
Task |
Description |
Panel Used |
|
1 |
Name the ruleset |
Maintain Rules menu |
|
2 |
Add a ruleset description |
Add Rules—Ruleset Description panel |
|
3 |
Add rules to the ruleset |
Begins with the Add Rules—Rule Actions menu |
|
Copyright © 2012 CA.
All rights reserved.
|
|