Allocate a New Security File with a New ACID Size

Creating and Setting Up Users › How to Increase ACID Size › Allocate a New Security File with a New ACID Size

Allocate a New Security File with a New ACID Size

Allocate a new security file with a new ACID size by increasing the maximum size of ACIDs.

Note: This change can be implemented one security file at a time, does not affect the size of the security file, and does not affect system performance.

Follow these steps:

Determine the required number of blocks for creating the security file:
1. Edit TSSMAIND and the SECPARMS portion of TSSMAINS to conform to your site's standards, including the following edits.
  The TSSMAIND and TSSMAINS members are in the CAKOJCL0 data set. CAKOJCL0 is available in the yourHLQ.SAMPJCL data set that was installed during product installation (where yourHLQ specifies the data set prefix for the site).
  - Specify the name of the dummy run in the SECDUMMY member referenced in TSSMAIND.
    A dummy run lets you calculate required blocks without allocating the real security file.
  - Set the ID=DUMMY parameter to consist of a maximum of eight characters.
2. Execute a dummy run with the JCL in TSSMAIND.
The number of blocks required is returned.

Note: Running TSSMAIND causes an SD37 ABEND or U1520. This result is normal.
Create the security file:
1. Edit the CAKOJCL0 member TSSMAINS.
  The CAKOJCL0 data set is available in the yourHLQ.SAMPJCL data set that was installed during product installation (where yourHLQ specifies the data set prefix for the site).
  - Set the SPACE parameter on the SECFILE DD statement as recommended in the TSSMAIND output.
    The default in the JCL is to use block allocation (rather than cylinders). To use blocks, set the BLKSIZE and BLOCKS parameters properly on the PROC statement. To use cylinders, follow the instructions in the TSSMAINS comments.
  - Set VOLSER JCL to the DASD volume serial identifier for your security file.
  - Set SECPRIM ID=PRIMARY to identify the name of your security file.
    ID supports a maximum of eight characters. The specified characters are placed in the primary security file and distinguish the primary security file from the backup file. We recommend ID=PRIMARY for the primary file and ID=BACKUP for the backup file.
  - Set the VSAMFILE DD statement to refer to the VSAM data set that you created when you defined a VSAM cluster in the catalog.
  - Set the VSAMAIX DD statement in STEP 2 to refer to the alternate index VSAM data set (if the security file is shared), or remove STEP 2 (if the security file is not shared).
    After the VSAM file is created, to copy information from an existing security file, run the TSSXTEND utility. You can copy information from a BDAM-only security file or a security file that uses BDAM and VSAM files.
2. Specify a MAXACIDSIZE entry (for increasing all ACID size), ORGACIDSIZE entry (for increasing organization ACID size), or both in the TSSMAINS utility job as follows:
```
MAXACIDSIZE=nnnn
```
  nnn
  
  Specifies a value between 256 and 512 that lets all ACIDs reach a size of more than 256 KB. ACIDs that reach the original limit will adopt the new maximum size.
```
ORGACIDSIZE=nnnn
```
  nnnn
  
  Specifies a value between 513 and 1024 that lets organizational ACIDs (DEPT, DIV, and ZONE) reach a size of more than 512 KB. ACIDs that reach the original limit will adopt the new maximum size.
  
  Important! Use this parameter only if you must support an department organizational ACID size that is greater than the MAXACIDSIZE value. CA Top Secret ignores any ORGACIDSIZE value that is less than the MAXACIDSIZE value.
3. Run the TSSMAINS job.
  The product allocates the file.
  
  Note: If you are using more than one CPU, you can place the security file on a shared DASD volume that is accessible to all systems. In this situation, you specify the control option SHRFILE(YES) on each CPU.
Edit the CAKOJCL0 member TSSMAINB:
Important! The SECPARMS contents must remain unchanged from the values used in TSSMAINS. If the backup file has different attributes than the primary file, the product might not be able to copy the primary file into the backup file during a backup process.
- Set parameters BLOCKS and CYLS to be identical to the CYLS and BLOCKS parameters that TSSMAINS uses to create the security file.
- Assign a BLKSIZE value that is identical to the BLKSIZE value of the primary security file.
- (Optional) Edit the ID parameter in the SECBACK member reference (default of ID=BACKUP).
  ID can contain up to eight characters. The value should clearly indicate that this file is the backup security file.
Execute the JCL in CAKOJCL0 member VSAMDEF6 to invoke IDCAMS to create a separate backup VSAM file.
Note: Specify the backup VSAM file on the VSAMFILE DD statement.

The product creates a separate backup VSAM file.
Run TSSMAINB to allocate the backup security file.

You now have a new security file with a new ACID size.