Resource security in BTS

BTS resources (processes, activities, and containers) are protected in the same way as resources accessed by CICS® file control commands. That is, resource-level security for a process, its activities, and their containers is based on the CICS file definition that specifies the repository data set to which records for processes of this type are written.

Users who run programs that define or acquire processes or activities of a particular process-type need UPDATE access to the corresponding CICS file.

Note:
When a task issues an ACQUIRE command, CICS allows the appropriate record to be read from the BTS repository, even if the userid associated with the request has only READ access. However, when the task issues a syncpoint the record is written back to the data set and, if the userid does not have UPDATE access, the task abends.

Users who inquire on or browse processes or activities of a particular process-type need at least READ access to the corresponding CICS file.

Related concepts
Process and activity userids
Attach-time security for processes and activities
Command security in BTS
The CICS RACF® Security Guide
Related reference
ACQUIRE
[[ Contents Previous Page | Next Page Index ]]