Previous Topic: Calculate Required BlocksNext Topic: Create the Security File

Starting Your Product › How to Complete Configuration With CA CSM › Creating the Security File › Create the VSAM File

Create the VSAM File

To maintain digital certificates, keyrings, and Kerberos KERBSEGM and KERBLINK records in a VSAM data set, use IDCAMS to allocate the data set. Using the VSAM data set allows heavy use of digital certificates. To assign a name to your users, use the Kerberos KERBNAME for your web users. The VSAM data set increases the amount of records that can be stored by converting the records to VSAM.

The r9 VSAM file structure is no longer supported. CA Top Secret only supports the r12 and later VSAM file structure. If you are using the r9 VSAM file structure, allocate an r12 and later VSAM file structure and run TSSXTEND to copy the security file and r9 VSAM file to the new security file.

Note: References to the VSAM file in this guide indicate the r12 and later file structure unless noted otherwise.

Follow these steps:

  1. Edit the sample JCL provided in VSAMDEF3 to specify the data set name and volume to be allocated.

    Note: Do not run STEP 2 if the security file is not shared.

    The sample includes your site-specific values.

  2. Run VSAMDEF3.

    The VSAM base cluster file is defined. If the security file is shared, the alternate index file and path file are defined.

  3. Specify this data set on the VSAMFILE DD statement in the jobs that execute TSSMAINT.

    The VSAM file is created.

After the VSAM file is created, if you wish to copy in information from an existing security file you must run the TSSXTEND utility. You can copy information from a BDAM only security file or a security file that uses both BDAM and VSAM files.