Maintaining Resource Rules with the ACF Command › Using ACF COMPILE to Build Resource Rules

Using ACF COMPILE to Build Resource Rules

The COMPILE subcommand creates a set of resource rules. The syntax for the COMPILE subcommand is:

         { *   } [List|NOList ]
COmpile  { fn  } [Store|NOStore]
                 [Force|NOForce]

*

Indicates that the subsequent text is input to the compiler. Using the COMPILE subcommand without parameters is equivalent to specifying an asterisk.

fn

Indicates a CMS filename where the rule compiler input resides. The filetype must be RULE. The filename cannot be one of the subcommand operands (LIST|NOLIST, STORE|NOSTORE, FORCE|NOFORCE). The ACF command cannot distinguish between a file named FORCE or an operand named FORCE. But you can have a rule with a key of FORCE. You must build the FORCE rule in a file with a filename of FORCE1, for example.

List|NOList

The LIST parameter displays the input to the compiler on the terminal screen when you compile the rule set. NOLIST causes no such display. LIST is the default when compiling from a CMS file. Otherwise, NOLIST is the default.

Store|NOStore

The STORE parameter automatically stores the rule set at compilation time. NOSTORE causes no automatic storing of the rule set, you must issue the STORE subcommand to store the rule set from an interactive compile. STORE is the default when compiling from a CMS file. Otherwise, NOSTORE is the default.

Force|NOForce

The FORCE parameter stores the resource rule set, regardless of whether it currently exists. NOFORCE only stores the resource rule set if it did not already exist. FORCE is the default. When you use FORCE|NOFORCE as parameters of the COMPILE subcommand, they apply only to the COMPILE subcommand you are issuing. When you use FORCE|NOFORCE as parameters of the SET subcommand, they are in effect until you change them or END the ACF command. They are not affected by changes in the ACF command setting.

CA ACF2 for VM provides two ways of compiling a resource rule set, from a CMS file or directly at the terminal. The following pages explain these two methods.