ACFCOMP - TSO Rule Set Compile Command

Describes the ACFCOMP TSO rule set compile command.
The ACFCOMP TSO command provides an alternative to compiling access rule sets. This command is issued from TSO READY mode.
The TSO ACFCOMP command follows one of these syntax formats:
Methods of Compilation
CA ACF2 can compile access rule sets directly at the terminal or from a partitioned data set (PDS).
Compiling Directly at the Terminal
Enter an access rule set directly from the terminal by first entering the ACFCOMP command without an asterisk or data set name:
Enter an access rule set directly from the terminal by first entering the ACFCOMP command without an asterisk or data set name:
READY acfcomp
CA ACF2 responds with:
Enter your rule set text just as you would under the ACF COMPILE subcommand. The access rule set is automatically stored after you compile it.
Compiling from a Partitioned Data Set (PDS)
Create access rule sets by first entering the control statements and rule entries in a PDS member. Each control statement or rule entry must be on a separate line. The last line does not have to be a blank line. For example:
After entering the control statements and rule entries in the PDS member, issue the ACFCOMP command with the name of the PDS and member. For example:
acf set rule acfcomp work.text(rule)
  • [*] (asterisk)
    Indicates that the text that follows is input to the compiler. The system prompts you to enter the access rule text directly from the terminal.
  • (no parameters)
    Equivalent to specifying an asterisk. However, the valid parameters that you can specify differ slightly. See the previous syntax.
  • [ALL]
    Causes compilation and storing of access rule sets from all members of a specified partitioned data set (PDS). For example:
    READY acfcomp work.text all
    If any member of the PDS in use does not contain access rule set text, do not specify this parameter.
  • dsname
    Specifies several different options for dsname command:
    • Enter the partitioned data set (PDS) and the member name that specifies the dsname to be compiled sequentially.
    • Enter just the PDS. CA ACF2 prompts you for a member name. If you sent the job to ACFBATCH, CA ACF2 does not prompt you for a member name, but will however, give you an error message.
    • Enter the PDS and then the ALL parameter to compile the input from all the PDS members.
    • Enter the PDS without the member name or the ALL parameter. The PDS name follows TSO conventions. Your high-level index is assumed unless you specify The entire PDS name and enclose it in single quotes. For example:
  • [
    This is valid only for data set access rules. The FORCE parameter enables the access rule set to store, regardless of whether it currently exists. NOFORCE enables the access rule set to store only if it does not already exist. FORCE is the default.
  • [
    Causes the input to the compiler to appear on your screen or to print on your listing during compilation of a rule set. NOLIST causes no such display or printed list. LIST is the default. This parameter does not apply for compilations directly from the terminal.
    Specifies a number from 0 to 999 that limits the size of the rule set that you can input to the compiler. This number is used as a space scaling factor and has no direct correlation to the number of rules in a rule set. (Different rules require different amounts of space.) The default is 250. If a rule set compiles correctly but encounters space problems when you try to store it, specify MAXRULE with a value less than 250. Alternatively, if a rule set contains a lot of duplication (that is, input source names and so forth), specify a higher value for MAXRULE to enable the compiler to accept a larger rule set. However, using the NEXTKEY parameter in your access rules is the preferable way to handle large rule sets.
  • [
    Causes the rule set to automatically store at compilation time. NOSTORE causes no automatic storing of the rule set. You must issue the STORE subcommand to store the rule set. STORE is the default.