Increase Maximum Acid Size On The Top Secret Security File While Implementing AES256 Password Encryption
Article ID: 188077
Top SecretTop Secret - LDAPWEB ADMINISTRATOR FOR TOP SECRET
While moving to AES256 password encryption, which requires formatting a new security file and copying the old security file into the new security file with TSSXTEND, would there be any issue to also increasing the max acid size?
These also require formatting a new security file and copying the old security file into the new security file.
Release : 16.0
Component : CA Top Secret for z/OS
There shouldn't be any issues implementing AES256 password encryption and increasing the maximum acid size.
This is also a good time to:
1) Run a TSSFAR report to check the health and size of the security file.
2) Increase the size of the areas such as ACCESSORS, RESBLOCKs, etc if these are close to reaching the limits on the current security file.
3) Fix invalid pointers with the WHOHAS TSSXTEND keyword.
These can all be fixed by formatting a new security file and running TSSXTEND to copy the old security file into the new security file.