CA VM:Secure uses configuration files to control the processing of many product–related functions. Each configuration file can include only specific records. The configuration files are:
Controls who is authorized to issue CA VM:Secure commands.
Maintains information about DASD controlled by CA VM:Secure.
Controls how CA VM:Secure operates.
Controls password processing. For CA VM:Secure, this file also controls how the Rules Facility operates.
Most configuration records in these files can be changed while CA VM:Secure is running, and their new values become effective as soon as you save the changes in the configuration file. This is referred to as dynamic reconfiguration.
Several configuration file records cannot be changed while CA VM:Secure is running.
Note: For more information about these records, see Configuration Files and Records.
You can update these configuration files directly through an XEDIT interface controlled by CA VM:Secure.
Note: For more information about each of the configuration files and their associated records, see the chapter "Configuration File Reference" in the Reference Guide.
If you use CA VM:Secure to manage SFS allocations, information about your SFS is stored in a configuration file that you do not edit directly. This file, SFS CONFIG, is created when you configure CA VM:Secure for SFS, and CA VM:Secure alone maintains it, based on the descriptions and enrollments you add to CA VM:Secure. If you edit this file directly, you will invalidate the CA VM:Secure functions for SFS management.
Note: For more information about configuration for SFS, see Configuring CA VM:Secure for SFS.
|
Copyright © 2014 CA.
All rights reserved.
|
|