Advanced Commands › Compiling a Rule for Display at the Terminal

Compiling a Rule for Display at the Terminal

Specify the command with the filename of the input file. In this form, ACFCOMP assumes the filetype is RULE and the filemode is A. For example:

ACFCOMP DOCTST
 
ACFCOM526I Processing input file 'DOCTST RULE A'
 
ACFCMP510I ACF compiler entered
 
$KEY(DOCTST)
 V0191.JD‑ UID(*)
 V0191.VOLUME UID(*) READ(A) WRITE(A) EXEC(A)
 V0191.‑ READ(A) WRITE(A) EXEC(A)
 V0192.‑ UID(*) READ(A) EXEC(A)
 ‑ UID(****DOC) READ(A) EXEC(A)
ACFCMP551I Total record length=205 bytes ‑ 5 percent utilized
ACFCOM726I Rule DOCTST replaced
 
Ready; T=0.03/0.17 11:23:13

In the above example, the defaults of LIST, STORE, and FORCE list the rule set during the compile and store it after the compile completed successfully. The last line displayed in the example (RULE DOCTST REPLACED) indicates that the compiled rule set replaced the previous rule for DOCTST.

Specifying the Complete CMS File Parameters

You can provide the complete filename, filetype, and filemode of the CMS file. For example:

ACFCOMP DOCTST FILE D (NOLIST
 
ACFCOM526I Processing input file 'DOCTST FILE D'
 
ACFCMP510I ACF compiler entered
 
ACFCMP551I Total record length=205 bytes ‑ 5 percent utilized
ACFCOM726I Rule DOCTST replaced
 
Ready; T=0.04/0.16 11:26:19

In the above example, the defaults of STORE and FORCE store the rule set after the compile completed successfully. The last line displayed in the example (RULE DOCTST REPLACED) indicates that the rule set replaced the previous rule for DOCTST. The NOLIST operand suppressed the display of the rule being compiled.

Using NOSTORE to Test Rules

You can use the NOSTORE operand to test whether the rule sets in the CMS file compile successfully. With NOSTORE, CA ACF2 for VM compiles all rules in the input file, but does not store them. For example:

ACFCOMP DOCTST FILE D (NOSTORE
 
ACFCOM526I Processing input file 'DOCTST FILE D'
 
ACFCMP510I ACF compiler entered
 
$KEY(DOCTST)
 V0191.JD‑ UID(*)
 V0191.VOLUME UID(*) READ(A) WRITE(A) EXEC(A)
 V0191.‑ READ(A) WRITE(A) EXEC(A)
 V0192.‑ UID(*) READ(A) EXEC(A)
 ‑ UID(****DOC) READ(A) EXEC(A)
ACFCMP551I Total record length=205 bytes ‑ 5 percent utilized
 
Ready; T=0.04/0.16 11:27:22

In the above example, CA ACF2 for VM did not store or replace any rule
sets-only compile them. If an error occurs during the compile, CA ACF2 for VM issues an error message.

Using NOFORCE to Store Only New Rules

There can be times when you want to store a rule set only if it does not already exist. You can use the NOFORCE operand to do this. For example:

ACFCOMP DOCTST RULE D (NOLIST NOFORCE
 
ACFCOM526I Processing input file 'DOCTST RULE D'
 
ACFCMP510I ACF compiler entered
 
ACFCMP551I Total record length=205 bytes ‑ 5 percent utilized
ACFRUM097E Record already exists ‑ store rejected
 
Ready(00003); T=0.03/0.15 11:28:53

In the above example, CA ACF2 for VM did not store or replace a rule set because a rule set already existed for DOCTST. The NOLIST suppressed display of the rule being compiled.

Entering Rule Input Directly from the Terminal

You can use the ACFCOMP command to enter rule input directly from the terminal. For example:

ACFCOMP (STORE
 
ACFCOM527I ACF2/VM interactive compiler
$KEY(DOCTST)
 (press enter)
 V0191.JD‑ UID(*)
 (press enter)
 V0191.VOLUME UID(*) READ(A) WRITE(A) EXEC(A)
 (press enter)
 (press enter again to signal end of terminal input)
 
ACFCMP510I ACF compiler entered
 
ACFCMP551I Total record length=130 bytes ‑ 3 percent utilized
ACFCOM726I Rule DOCTST replaced
 
Ready; T=0.03/0.18 11:31:22

In the above example, the rule input is entered in interactive mode directly from the terminal.