VSAM FILE Empty after Running TSSXTEND in Top Secret

Products

• Top Secret
• Top Secret - LDAP
• WEB ADMINISTRATOR FOR TOP SECRET

Issue/Introduction

Last weekend we upgraded from Top Secret 15.0 to 16.0.  As part of that upgrade we created a new set of security files including the VSAM files related to key rings and certificates.

We ran PGM=TSSXTEND to copy the 15.0 security backup to 16.0.  Apparently this does not copy the associated key ring and certificate data which is held in the VSAM files.

Fortunately there are not too many of these data so they could be recreated if necessary, but I wondered if it would be possible to do any of the following:

1.  REPRO the data from the old VSAM files to the new.

2.  Update the TSS proc to point to the old 15.0 VSAM files and restart, preferably without an IPL.

3.  Another option I'm not aware of?

 

 

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

The first time you create a VSAM file and run TSSXTEND the OLD VSAM DD has to be commented out.
This ensures that the TSSXTEND program looks in the BDAM file to pull the certificates and related data that is going to be stored in the NEW VSAM.
The next time you run TSSXTEND you need to put the file name of the existing VSAM FILE in the OLD VSAM DD and remove the comment asterisk so that the file is found and the contents copied into the NEW VSAM file. If you do not remove the comment asterisk then the NEW VSAM FILE will be empty.