Starting Your Product › How to Complete Configuration With CA CSM › Create the Recovery File (Optional)

Create the Recovery File (Optional)

If you commented or deleted the RECFILE DD in the TSS started task procedure, skip this procedure.

The recovery feature stores forward recovery information. The recovery file records changes made to the security file. This file is a wraparound file. When the file is full, recording continues at the beginning of the file, overlaying existing data. The default size recovery file can hold approximately 2,000 changes before a wraparound occurs.

The recovery file does not support DFSMS Extended Sequential data sets (multi-volume data sets).

Do not allocate the recovery file on the same volume as the security file in case of loss due to hardware malfunction.

Follow these steps:

1. Edit the TSSMAINT utility to conform to your site's standards.

   Note: TSSMAINT resides in the CA Top Secret CAKOJCL0 data set.

   The utility is updated.

2. Edit the recovery file parameters one per line, starting in column 1:

   CREATE RECOVERY

   Requests recovery file initialization.

   BLOCKS=????

   Specifies the number of blocks to be used for the recovery file. A large recovery file delays initialization of the CA Top Secret address space every time it is started. The size of the recovery file depends on the interval between security file backups. Make the file large enough to record two to three days of changes for every day in the security file backup period. For example, if the security file is backed up at the end of each day, the recovery file should be large enough to accommodate at least two days of changes.

   Default: 250

   Minimum: 250

   Maximum: N/A

   The recovery parameters include your site-specific values.

3. Replace lowercase type in the JCL with the appropriate parameters for your site.

   Note: The file block size should provide efficient utilization of the track capacity for the device the file resides on. An exact value is not necessary as TSSMAINT rounds the block size down to a multiple of its logical record length. The actual block size may be less than specified on the JCL, but it should be approximate.

   The recovery parameters include your site-specific values.