The RULES command creates or deletes a file in the rules database or invokes XEDIT for updating existing rules.
The following table explains the kinds of rule to use to control various functions.
|
To control: |
Create this kind of rule: |
|---|---|
|
Other users’ access to your virtual machine and minidisks |
AUTOLOG, COUPLE, DIAL, LINK, LOGON, LOGONBY, SPOOL, TRANSFER, or XAUTOLOG |
|
CP commands at the system level |
STORE or TAG |
|
CA VM:Secure GROUP command |
MEMBER |
|
CA VM:Tape commands |
CATALOG, LIST, or MOUNT |
|
CA VM:Schedule commands |
CANCEL, QUERY, or SCHEDULE |
You can add the edit special comment (*ED=) to any rules file. This statement contains the following information about the last update performed on a rules file: date, time, user ID performing the update, and the name of the CA VM:Secure macro invoked for the last update.
If all rules are removed from a rules file, CA VM:Secure erases the rules file. Any comments that you put in the file will be lost.
CA VM:Secure treats XAUTOLOG rules as AUTOLOG rules. All AUTOLOG rules apply to the CP XAUTOLOG command.
Examples
vmsecure rules
This command puts you in XEDIT in your user rules file. You can then enter a rule such as:
accept kelso link
This rule allows user ID KELSO to link to all of your minidisks. If one of your minidisks has a link password other than ALL, the requesting user ID must enter the password.
vmsecure rules (erase)
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |