CACHE versus SECCACHE.

book

Article ID: 50318

calendar_today

Updated On:

Products

CA Cleanup CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Top Secret CA Top Secret - LDAP CA Top Secret - VSE

Issue/Introduction

Description:

When SECCACHE has been activated, do we still need to have CACHE activated?

Solution:

It is recommended that SECCACHE and CACHE be both turned on.

The SECCACHE control option is used to improve sign-on performance by caching sign-on activity.

Activating this functionality will greatly decrease the I/O being made to the CA Top Secret Security File.

The CACHE control option is used to improve performance and reduce overhead by caching security checks for resources.

This saves CA Top Secret from going through a full security check and saves the I/O overhead.

For more details about the SECCACHE and CACHE control option, please see the CA Top Secret Control Option Guide.

Environment

Release:
Component: AWAGNT