Previous Topic: Control Option OverridesNext Topic: PIEBLOCKS, RESBLOCKS, SDTBLOCKS

Starting Your Product › How to Complete Configuration With CA CSM › Operational File Considerations (Optional)

Operational File Considerations (Optional)

Skip this section if you are installing CA Top Secret for the first time.

Note: If you are currently running with a BDAM file or an r9 VSAM file, you must upgrade to an r15 VSAM file because r15 does not support BDAM or the r9 VSAM file structure.

Follow these steps:

  1. From your previous release of CA Top Secret, run the TSSFAR utility with the SFSTATS option against your existing backup security file.

    A file analysis report is generated.

  2. Use the file analysis report to determine the minimum parameter values for the current release of the security file.

    You have determined the minimum parameter values.

  3. Use TSSMAIND and TSSMAINS to allocate all of special blocks directly.

    If you use the traditional BLOCKS allocation for the security file, perform the following steps:

    1. Comment the CYLS parameter.
    2. Uncomment the BLOCKS parameter.
    3. Update the BLOCKS parameter with the number reported by TSSMAIND.

    With this choice, security data is read with only one block per SIO.

  4. Copy your existing security file into the newly allocated security file using the procedures described in the appendix TSSXTEND and TSSRECVR.

    Important! If the parameters of the new security file were changed, you must also create a backup security file on DASD.

    Your existing security file is copied to the newly allocated security file.

  5. Change the SECFILE and BACKUP DD statements in your TSS startup proc to point to the newly allocated security files.

    The statements point to the newly allocated security file.