Previous Topic: Destinations of Trace MessagesNext Topic: Examples: SHRFILE control option


SHRFILE—Share Files

Valid on z/OS and z/VM.

Use the SHRFILE control option to specify whether files used by CA Top Secret are shared among other operating systems and/or CPUs.

Important! Do not use this option to share files with an CA Top Secret for z/OS version lower than 5.1 or an CA Top Secret for z/VM 1.4 version lower than 9906.

All entry methods are accepted.

This control option has the following format:

SHRFILE(YES[,AINDXPER])|(SECURITY[,AINDXPER])|(NO)
YES

(Default) Specifies that both the security file and the AUDIT files are shared among other operating systems and/or CPUs. This is the default. If you are not actually sharing the security file and audit files, this option will generate significant unnecessary I/O to the security file and the AUDIT files.

SECURITY

Specifies that the security file but not the AUDIT files are shared among other operating systems and/or CPUs. CA Top Secret will perform lock processing on the Security File (and subsequently on the Recovery File), but will not perform lock processing on the Audit File. Audit File processing is handled as if SHRFILE(NO) had been specified.

NO

Specifies that neither the security file nor the AUDIT files are shared among other operating systems and/or CPUs. The LOCK records on the Security and Audit Files are obtained at startup and never released, totally eliminating all I/O required for lock record processing in a single CPU environment.

AINDXPER

(Obsolete) This is no longer an option, it is now the default method of processing I/O when the security file is shared between multiple systems. The control option syntax checking still supports specification of the option so that existing parameter files do not experience problems.