This task indicates if you are sharing your security database with another CA Top Secret security system. If the security database is shared, this task specifies the system that performs Security File backups. Record‑locking features help ensure database integrity.
If your Security, Audit/Tracking, Recovery, and Backup files currently exist (on minidisks or on real OS volumes), you must provide appropriate CP directory control statements for the CA Top Secret server to gain access to these files. For information, see Task KVC0I030.
If you are planning to use the Single System Image feature of Z/VM 6.2 and later, we recommend all Top Secret servers within the cluster share the security database. This sharing complements the intent of this feature of a logical single image.
CA Top Secret for z/VM cannot share security files with:
Note: If you are sharing the security file between MVS and VM and the security file under MVS has been created with the AESENCRYPT option, this security file can no longer be shared between MVS and VM.
SHRFILE other than NO causes the server to ensure minidisk caching is turned off for the server files at start up.
To share your security database with another CA Top Secret security system
|
Copyright © 2013 CA.
All rights reserved.
|
|