The Rules Facility stores rules in a group of files in its rules database. The rules database contains files to represent all five levels of rules: system, security group, user, group default, and system default. Authorized users can use the RULES command to edit rules files.
The contents of the rules files determine the rules set up for your site. Each authorized user on your system is represented by a user rules file in the rules database, each security group is represented by a group rules file, and so on.
Each rules file contains a set of records. Each record establishes a single rule. A rules file record can be 71 characters long. If you need to continue a record to the next line, use a comma as the continuation character.
The maximum length of a logical line in a rules file is 255 characters. Using a standard 71 character XEDIT line, you can use about three and a half lines of text for one record. A message warns you if you exceed this limit.
A comma at the end of a comment line (a line beginning with an asterisk) does not serve as a continuation character. It is simply a comma. For example:
* THIS IS A COMMENT LINE,
When an expired rule is found in a rules file (when a user issues the RULES command), it issues message 219I. This message tells you that the rule has expired and can be removed.
When all rules are removed from a rules file, CA VM:Secure erases that rules file; any comments that were included in that file are lost.
If your site has implemented an interface between CA VM:Secure and CA VM:Schedule, you can create rules to control canceling, querying, and scheduling of these jobs. These rules are discussed later in this chapter.
If your site has implemented an interface between CA VM:Secure and CA VM:Tape, you can create rules to control catalog updates, listings, and tape mounts. These rules are discussed later in this chapter.
|
Copyright © 2014 CA.
All rights reserved.
|
|