The COMPILE subcommand compiles the diagnose limiting rule set. CA ACF2 for z/ VM provides two ways of compiling diagnose limiting rule sets: directly at the terminal or using text in a CMS file as input to the compiler.
To enter a diagnose limiting rule set directly from the terminal, enter the COMPILE subcommand without parameters:
COMPILE ACFpgm510I CA-ACF2 compiler entered
To begin, enter the $KEY control statement on the first line. Enter the other control statements and then the rule entries, each on a separate line. After entering each line of information, press Enter or the return key.
DIAGLIM COMPILE ACFpgm510I CA-ACF2 compiler entered $KEY(DIAG0004) UID(*****OPR) LOG UID(*****TEC) ALLOW ACFpgm551I Total record length=194 bytes - 4 percent utilized DIAGLIM
When you are finished adding entries to the rule set, press Enter or the return key without adding any text. The COMPILE subcommand automatically ends. After you compile the diagnose limiting rule set, you can use the TEST subcommand to see if the rule set performs as you intended.
To create a diagnose limiting rule set, enter the control statements and rule entries in a CMS file. The file must have a filetype of RULE. Enter each control statement or rule entry on a separate line.
Assume that the following text was input into a file named DIAGFILE with a filetype of RULE.
$KEY(DIAG0004) UID(OPR) LOG UID(TEC) ALLOW
After you enter the control statements and rule entries in the file, invoke CA ACF2 for z/ VM and compile the diagnose limiting rule set using the COMPILE subcommand under the DIAGLIM setting. Specify the filename following the COMPILE subcommand:
DIAGLIM compile diagfile
Indicate only the filename; the filetype is assumed to be RULE. The rule set is compiled and, by default, stored.
After you compile the diagnose limiting rule set, you can use the TEST subcommand to see if the rule set performs the intended validation of attempts to issue a diagnose instruction.
Under the DIAGLIM setting, the COMPILE subcommand has the following syntax.
COmpile { * } [ List|NOList ]
{ filename } [ Store|NOStore]
[ Force|NOForce]
Indicates that the text is input to the compiler. In an online environment, the system prompts you to enter the diagnose limiting rule text directly from the terminal.
Using the COMPILE subcommand without parameters is the same as specifying an asterisk (*).
Specifies the CMS filename that contains the diagnose limiting rule text to compile. The filetype is always RULE.
LIST displays the input to the compiler on your screen or printed on your listing when you compile the rule set. NOLIST does not display on your screen or listing. LIST is the default when compiling from a CMS file. Otherwise, NOLIST is the default.
STORE stores the rule set after it is compiled. NOSTORE does not automatically store the rule set. STORE is the default if you are compiling the rule set from a CMS file. Otherwise, NOSTORE is the default.
FORCE (the default) stores the diagnose limiting rule set even if it currently exists. NOFORCE only stores the rule set if it does not already exist. When you use FORCE|NOFORCE as a parameter of the COMPILE subcommand, it only applies to the COMPILE subcommand you are currently issuing. FORCE|NOFORCE is in effect until you change it or until you end the ACF command. Changes in the ACF command setting do not affect this setting.
CA ACF2 for z/ VM provides two ways of compiling a diagnose limiting rule set: From a CMS file or directly at the terminal.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|