Previous Topic: SECCACHE—Security Record CacheNext Topic: SECFILE—Security File Name


SECCACHE in a Shared Security File Environment

In a shared security file environment, it is important that policy changes made on one system are reflected within any in-core processing tables on all remote systems as soon as possible. This is accomplished internally when a security file I/O is performed on the remote system, for example when a user logs on.

The SECCACHE control option eliminates much of the security file I/O associated with a user log on event. To improve the synchronization an internal processing event performs any in-core table refresh, if required, at the end of two TIMER cycles. This keeps the tables up to date even though the security file has not been accessed. You can manually synchronize the in-core tables with the MODIFY SYNCH control option. This allows you to immediately see the effects of remote changes to selected SDT records with the TSS LIST command.