VSAM fileshave an AIX cluster (Alternate Index) and PATH associated with them.
This is the recommendation for a shared security file.
Is there any performance considerations to having standalone file systems with a VSAM file that
has an AIX and Path?
Release : 16.0
Component : CA Top Secret for z/OS
If the primary VSAM file is increased in size of primary VSAM file you need to increase the
size of the backup to match.
If not sharing the file having an AIX define, will increase I/O during adds and updated to the file.
On a system that is not sharing the security file, there is no I/O to the AIX for read request. Only for adds and updates.
If the AIX and PATH are allocated they are used, during adds and updates.
This allows the sharing system to know what records need to be added or refreshed on other system.