Security File Migration to CA Top Secret r16.0 From A r14.0 Formatted Security File.

Document ID : KB000013703
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

 

 

- Upgrading CA Top Secret from release 15.0 to CA Top Secret release 16.0. All our security files were formatted when we were running Ca Top Secret r14.0 .

 

- We have got 64 security files and we would like to avoid to reallocate them all.

Question:

 

 

- Must we allocate new security file? 

 

- The CA Top Secret documentation states that we can run Ca Top Secret r16.0 with the files from r15.0.

 

 

Environment:
z/OS
Answer:

 

 

-If you have already migrated from CA Top Secret r14 to CA Top Secret r15 then the security files (both BDAM and VSAM) are now considered r15 compatible.

 

- These files can then be used for an r15 to r16 migration without any need to create new ones, unless you want to take advantage of a feature that requires an    EXTEND of the security file.

Additional Information:

 

- If you want to have more information about the CA Top Secret TSSXTEND utility go to link:

 

https://docops.ca.com/ca-top-secret-for-z-os/16-0/en/search?q=tssxtend&max=10&key=CTSFZ16

 

- If you want to have more information about the CA Top Secret TSSMAINS utility go to link:

 

 https://docops.ca.com/ca-top-secret-for-z-os/16-0/en/search?q=TSSMAINT&max=10&key=CTSFZ16