Advanced Commands › Using ACFCOMP to Compile Rules

Using ACFCOMP to Compile Rules

The ACFCOMP command lets you compile and store access rule sets quickly and easily. You can enter rule text from the terminal or from a CMS file. You can also use ACFCOMP to process resource rule sets. The syntax for the ACFCOMP command is:

ACFCOMP {*           }   [(List|(NOList   ]
        {fn {ft fm}  }   [(Store|(NOStore ]
                         [(Force|(NOForce ]

The operands for ACFCOMP are defined below.

*

Specifies that you are entering rule text from a terminal. CA ACF2 for VM prompts you for the rule text. After you enter all the rule text, press Enter to indicate you are done.

fn ft fm

The filename, filetype, and filemode of the CMS file that contains the rule text. If this file contains multiple rule sets, CA ACF2 for VM compiles all the rule sets. You only need to specify the filename (fn). By default, CA ACF2 for VM assumes the filetype is RULE and the filemode is A.

(List|(NOList)

LIST Specifies that CA ACF2 for VM display the compiled rule sets at the terminal. NOLIST suppresses the display. The default is LIST.

Store|(NOStore

STORE specifies that CA ACF2 for VM automatically store the compiled rule sets on the Rule database if the compile is successful. NOSTORE compiles the rule sets, but does not store them. This makes NOSTORE a useful option for testing. STORE is the default.

Force|(NOForce

FORCE specifies that CA ACF2 for VM store the compiled rule sets if a rule with the same $KEY already exists. In effect, CA ACF2 for VM replaces the existing rule with the newer rule. NOFORCE suppresses the store if a rule with the same $KEY exists. When you compile multiple rule sets and specify NOFORCE, CA ACF2 for VM only stores rules that do not exist on the Rule database.

The following sections illustrate how you can use ACFCOMP to compile access rule sets.