ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Why is there CACHE|NOCACHE and CACHE(5) in GSO MUSASS definitions when the ACF2/CICS and ACF2/IMS interfaces also have Cache?

book

Article ID: 199387

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC LDAP SERVER FOR Z/OS PAM CLIENT FOR LINUX ON MAINFRAME WEB ADMINISTRATOR FOR TOP SECRET

Issue/Introduction

Is  the CACHE parameter required in the GSO MUSASS definition ACF2/CICS or ACF2/IMS are also being used?

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

The musass CACHE should only be used if you are not using a MUSASS interface like ACF2/CICS or ACF2/IMS.
Both interfaces provide cache processing internally to the interface.
Running a MUSASS that doesn't have a formal interface may provide faster resource validations if Musass cache is active.
It will provide previously accessed permissions without going through the full validation.

Powered by Wolken Software