Creating a rules dataset using the CA OPS/MVS RULEPREFIX2 and viewing the rules using the CA OPS/MVS OPSVIEW 4.5.1 panel.
search cancel

Creating a rules dataset using the CA OPS/MVS RULEPREFIX2 and viewing the rules using the CA OPS/MVS OPSVIEW 4.5.1 panel.


Article ID: 5987


Updated On:


OPS/MVS Event Management & Automation


I was following the R13 manual to establish an Archive for the OPS log. One of the steps was to copy the security rule ARCHSECA to a Security ruleset  and enable that rule. Now, my OPSPARMS for Prefixing and Suffixing rulesets is as follows:


So, I copied ARCHSECA into the dataset COMPANY.CAOPS.R130.SYST.SEC.RULES; which I thought corresponds to my RULEPREFIX2 and RULESUFFIX parms. When I go into OPSVIEW, I enter 4.5.1., I can see my RULEPREFIX Rules..

AOF CTRL - Entry panel --- SYST --- O P S V I E W ------------- Subsystem OPSS
Command ===>                                                                
Rule data sets of the form COMPANY.CAOPS.R0000.SYST.*.RULES:                
   Rule Set ===> *           ( * or blank for all rule sets )               
       Either specify a specific rule set or request a list of all rule sets.

How do I switch over to see my RULEPREFIX2 rules - especially for the SEC rules?    




Although the OPSVIEW 4.5.1 option panel will show all of the RULEPREFIX and RULEPREFIX2 rule dataset rulesets members and rules when selected, only one rule dataset can be specified for the panel due to the panel design and program code.


Seeing the rule members of the RULPREFIX2 rulesets can be done by selecting a ruleset, belonging to the RULEPREFIX2 dataset, from the list of rulesets in the CA OPS/MVS OPSVIEW 4.5.1 option panel. They can also be seen by the dataset name, outside of CA OPSVIEW, using ISPF 3.4.

For processing the desired rule members during OPS initialization, make sure there are no duplicate named rules in the combined RULEPREFIX and RULEPREFIX2 ruleset member display. If a rule with the same name is found using the RULEPREFIX and RULEPREFIX2 rulesets, the second duplicate named rule is ignored when the rules are processed.

In this case, a second member named ARCHSECA will be ignored. To avoid this process event problem, rename one of the rules so there is only one ARCHSECA ruleset member or disable one of the two ARCHSECA rules.


Additional Information