Installing CA Disk Under CA ACF2

To run effectively on a system using CA ACF2, follow these steps. The steps apply even if you do not have the CA Disk Security Interface for CA ACF2 installed.

To process the data sets managed by CA Disk, setup your production CA Disk runs to have sufficient access. The simplest way to accomplish this access is to run these CA Disk tasks with a Logon ID that has the non-CNCL attribute.

Many users with CA ACF2 select instead to set up a Logon ID as a data administrator.

To install CA Disk under CA ACF2:

Create a Logon ID that has the MAINT attribute.
Create a CA ACF2 GSO options record to allow that Logon ID access using the program ADSMI002 from your CA.DISK.LOADLIB.
```
MAINT    LIBRARY(CA.DISK.LOADLIB)
         LID(logonid)
         PGM(ADSMI002)
```
If you already have a MAINT record, append a qualifier to the record name to generate a unique RECID.
```
MAINT.DMS LIBRARY(CA.DISK.LOADLIB)
             LID(logonid)
             PGM(ADSMI002)
```
Except for the TSO command processors, most of the time CA Disk runs as the program name ADSMI002. The remaining usage is either with the program name of ADSMI000 or ADSMI302.

The only time to use ADSMI302 is if Customer Support requests a PET trace for debugging a problem. The ADSMI000 program is used where CA Disk does not control the retention of the tape such as Sequential Migrate or FDS Unload. Tapes created with these functions should not be under EDM control.

Both ADSMI000 and ADSMI302 need a CA ACF2 GSO option.
Run these CA Disk production jobs with your Logon ID.
Other alternatives are possible.

You can process (archive, restore, migrate, and so on) data sets you are authorized for.

Also, to accomplish its function, CA Disk must update format-1 DSCBs in volume VTOCs. For example, backups must be able to turn off the change bit DS1IND02. Restore and Move/Copy processing must update certain fields that CA Disk maintains. See the CA Disk SVC for a list of those fields. To avoid S913-38 abends as CA Disk tries to do this function, allow CA Disk to open VTOCs for INPUT and OUTPUT.

To run any CA Disk task with a Logon ID that does not have the nonCNCL attribute, add the CA ACF2 access rule. Adding the rule lets CA Disk programs update your VTOCs.
```
$KEY(SYSVTOC)
- UID(*) LIB('CA.DISK.LOADLIB') PGM(ADSMI002)
READ	(A) WRITE(A)
```
If you plan to use the CA Disk TSO command RESTORE, add the CA ACF2 access rule:
```
$KEY(SYSVTOC)
- UID(*) LIB('CA.DISK.LOADLIB') PGM(RESTORE)
READ(A) WRITE(A)
```
Note: READ(A) also implies EXEC(A). If the CA Disk load library is in the Linklist, replace LIB('CA.DISK.LOADLIB') with LIB('SYS1.LINKLIB'). WRITE(A) can be replaced with WRITE(L).

Except for the TSO command processors, CA Disk always runs as the program name ADSMI002.

When running all of your CA Disk tasks with Logon IDs that have the non-CNCL attribute, do not worry about CA ACF2 protection for VTOCs.
Determine if a user is authorized to perform Storage Administration functions. CA Disk uses the RACROUTE parameter STATUS=ACCESS under ISPF. CA ACF2 does not allow the use of STATUS=ACCESS by an unauthorized ISPF Dialog. Instruct CA ACF2 to allow the access and not abend the request with an S047 abend in module ACF9C000, by installing the following SAFDEF statement:
```
INSERT SAFDEF.adsds1 RB(ADSMI002) PROGRAM(ADSMI002) NOAPFCHK
RACROUTE(REQUEST=AUTH,CLASS=FACILITY,STATUS=ACCESS,ENTITY=STGADMIN.DMS.-)
```

Installing the SAFDEF statement lets the CA Disk ISPF Dialog determine access to the FACILITY class profile without causing a violation or the S047 Abend. Change the operand of the STGADMIN.DMS ENTITY parameter if the default CA Disk FACILITY names controlled by sysparm SMSSTGAD are not used. The default value of SMSSTGAD is STGADMIN.DMS.STGADMIN which is the value ENTITY= in the sample SAFDEF.

This section contains the following topics:

Installing the CA ACF2 Interface