CL/SuperSession Started task(s) must be properly defined to the STARTED resource class for RACF.

Access to product resources must be restricted to only individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could 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(ZCLS0032).

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

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

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

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

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

setr racl(started) ref