CA VTAPE Started task(s) must be properly defined to the STARTED resource class for RACF.

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

Refer to the following report produced by the RACF Data Collection:

- DSMON.RPT(RACSPT).

Automated Analysis Refer to the following report produced by the RACF Data Collection:

- PDI(ZVTA0032).

Verify that the CA VTAPE started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

The CA VTAPE system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP.

A unique userid must be assigned for the CA VTAPE started task(s) thru a corresponding STARTED class entry.

The following sample set of commands is shown here as a guideline:

rdef started SVTS.** uacc(none) owner(admin) audit(all(read)) stdata(user(SVTS) group(stc)) rdef started SVTSAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(SVTSAS) group(stc))

setr racl(started) ref