BMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP. (Cat II impact)
BMC Mainview for z/OS requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC) Insure that the logonids(s) for the BMC Mainview for z/OS started task(s) includes the following: STC MUSASS NO-SMC
The BMC Mainview for z/OS system programmer and the IAO will ensure that a product's 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. Example: SET LID INSERT MV$CAS STC MUSASS NO-SMC INSERT MV$PAS STC MUSASS NO-SMC INSERT MV$MVS STC NO-SMC
The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users).
Identification And Authentication (Organizational Users)