Previous Topic: Allocate a New Security File with a New ACID SizeNext Topic: Delete an ACID


Copy the Backup Security File to the New Security File

After allocating a security file that provides a new ACID size limit, copy the old backup security file to the new security file.

To perform this task, you must be a Master Security Control ACID (MSCA) or a user with one of the following authorizations:

Follow these steps:

  1. Use the following JCL to copy the contents of the old backup security file into the new security file:
    //jobname JOB USER=msca only
    //EXTEND EXEC PGM=TSSXTEND
    //MAINTOUT DD SYSOUT=A
    //SECFOLD DD DSN=name.of.backup.security.file,DISP=SHR
    //SECFNEW DD DSN=name.of.new.security.file,DISP=SHR
    //SECNVSM DD DSN=name.of.vsamfile,DISP=SHR for the output (new) VSAM dataset
    //SECOVSM DD DSN=name.of.vsamfile,DISP=SHR for the incoming (old) VSAM dataset
    //MAINTIN DD *
    COPY SECURITY
    OLDKEY=encryption_key_of_old_file
    NEWKEY=encryption_key_of_new_file
    /*
    

    The OLDKEY and NEWKEY fields must be a 16-character hexadecimal number. You cannot add comments to these fields.

    Important! Safeguard your key.

  2. Change the PROC statements in your JCL procedures (TSS STC, TSSB STC, and backup and recovery procedures) to point to the new security and backup files.
  3. IPL the system by modifying the TSS procedure in SYS1.PROCLIB to include the new primary and backup security files and VSAM files.
  4. Start CA Top Secret with the new security file.

Increased ACID size is now available. ACIDs that reach the original limit will adopt the new maximum size. Having an increased size avoids the need to redesign the security implementation and prevents situations in which administrators cannot add attributes and properties to records that have run out of space.