ROSCOE Started Task name is not properly identified/defined to the system ACP.

Products that require a started task will require that the started task be restricted to certain resources, data sets, 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.

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

- TSSCMDS.RPT(@ACIDS).

Review ROSCOE STC/Batch ACID(s). If the following attributes are defined, this is not a finding.

FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND MASTFAC(ROSCOE)

The ROSCOE systems programmer and the ISSO will ensure that a product's Started Task(s) is properly identified/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.

A sample is provided here:

TSS CREATE(ROSCOE) TYPE(USER) - NAME('*STC* for ROSCO') DEPT(xxxx) - FAC(STC) - MASTFAC(ROSCOE) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND