STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS Compuware Abend-AID for ACF2 Security Technical Implementation Guide

V-224294

CAT II (Medium)

Compuware Abend-AID Started Task name will be properly identified and/or defined to the system ACP.

Rule ID

SV-224294r1144191_rule

STIG

z/OS Compuware Abend-AID for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Compuware Abend-AID requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

Check Content

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

- ACF2CMDS.RPT(ATTSTC).

Verify that the logonid(s) for the Compuware Abend-AID started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

STC

Fix Text

The ISSO working with the systems programmer will ensure the Compuware Abend-AID Started Task(s) is properly identified and/or defined to the System ACP. 

If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.

Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.

The following commands are provided as a sample for defining Started Task(s):

SET LID
insert AAVIEWER stc name('STC, Compuware Abend-AID Viewer')
insert BDCAS stc name('STC, Compuware Abend-AID')
insert TDCAS stc name('STC, Compuware Abend-AID for CICS')