TSSFAR, dismatch between index entries and available acid

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

Why in TSSFAR we get a dismatch between index entries (324,464) and available acid (386,751)?

*** Security File Statistics Begins ***
Acid index entries allocated: 400,895 Acid index entries defined: 324,464
Next available acid number: 386,751 Last available acid number: 400,895

Environment

Release:
Component: TSSMVS

Resolution

Acid index entries allocated: 400,895 is the maximum number of slots available to index an acid.
Acid index entries defined: 324,464 is the current number of slots used to index acids
Next available acid number: 386,751 is the slot number which is the first available to index an acid.
Last available acid number: 400,895 is the last slot number available to index an acid.

Also, when the "Next available acid number" is closed or egal to "Last available acid number:" we are not at risk. See the technical document #000091824.

See link below:

https://comm.support.ca.com/kb/is-it-necessary-to-create-new-secfile-if-next-available-is-close-to-last-available-acid-number/kb000091824