Example 1
In the sample Rule list below, several rules may exist that relate to (and operate on) the same data set.
Table 179 Sample Rule List – Example 1
  | 
Selection Criteria  | 
||||||||
|---|---|---|---|---|---|---|---|---|---|
Rule  | 
Priority  | 
Data Set  | 
Job  | 
Account  | 
Program  | 
Owner  | 
Media  | 
Volume  | 
Continue  | 
1  | 
  | 
ABCD  | 
PAY786  | 
  | 
  | 
  | 
  | 
  | 
NO  | 
2  | 
  | 
ABCD  | 
*  | 
  | 
  | 
  | 
  | 
  | 
YES  | 
3  | 
  | 
ABC*  | 
*  | 
  | 
  | 
  | 
  | 
  | 
YES  | 
4  | 
  | 
A*  | 
*  | 
  | 
  | 
  | 
  | 
  | 
NO  | 
5  | 
  | 
*  | 
PAY*  | 
  | 
  | 
  | 
  | 
  | 
NO  | 
6  | 
  | 
*  | 
*  | 
  | 
  | 
  | 
  | 
  | 
  | 
Note:
Assume that JCL specifies data set ABCD within job XYZ. Control-M/Tape searches the sample Rule list above and finds that Rule 1 matches the JCL data set name. Control-M/Tape then attempts to match the job name, that (in this case) does not match. Control-M/Tape then searches the next rule in the Rule list and finds a match. Some or all of the Action categories are satisfied by the parameters specified in Rule 2.
If additional Action categories need to be satisfied, Control-M/Tape continues the rule search by checking Rules 3 and 4, that both meet the search criteria for data set name. However, Control-M/Tape stops searching after Rule 4, because the CONTINUE SEARCH parameter is set to NO.
If certain Action categories remain unfilled after the search is completed, Control-M/Tape uses the default values from the installation parameters (CTTPARM member definitions) For example, the retention is taken from the DEFEXPDT parameter.
Example 2
Assume that the following Rule list is loaded into common storage. The only difference between this list and the previous list is that a new Rule 1 has been added. Rule 1 has the highest priority in the list and applies to any data set accessed by a job named XYZ.
Table 180 Sample Rule List – Example 2
  | 
Selection Criteria  | 
||||||||
|---|---|---|---|---|---|---|---|---|---|
Rule  | 
Priority  | 
Data Set  | 
Job  | 
Account  | 
Program  | 
Owner  | 
Media  | 
Volume  | 
Continue  | 
1  | 
Highest  | 
*  | 
XYZ  | 
  | 
  | 
  | 
  | 
  | 
YES  | 
2  | 
  | 
ABCD  | 
PAY786  | 
  | 
  | 
  | 
  | 
  | 
NO  | 
3  | 
  | 
ABCD  | 
*  | 
  | 
  | 
  | 
  | 
  | 
YES  | 
4  | 
  | 
ABC*  | 
*  | 
  | 
  | 
  | 
  | 
  | 
YES  | 
5  | 
  | 
A*  | 
*  | 
  | 
  | 
  | 
  | 
  | 
NO  | 
6  | 
  | 
*  | 
PAY*  | 
  | 
  | 
  | 
  | 
  | 
NO  | 
7  | 
Lowest  | 
*  | 
*  | 
  | 
  | 
  | 
  | 
  | 
  | 
Using the same search criteria as in the previous example, Control-M/Tape encounters a JCL that specifies data set ABCD within job XYZ. Control-M/Tape searches the Rule list above and finds that Rule 1 applies because it matches the data set mask specification and the job name. Control-M/Tape fills in all the Action categories that are specified in Rule 1. If there are still remaining attributes to be filled in, Control-M/Tape continues searching the Rule list. In the list above, these Action categories may come from any of Rules 3, 4, or 5 – in that sequence. Rule 2 does not apply because it contains a different job name.
If a rule is not located for a specific data set or volume, actions can still be taken based on generic rules. Generic rule actions are specified using mask character * in any of the selection criteria fields.
Parent Topic |