The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D installation data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, BMC users, security personnel (domain level and decentralized), and BMC STCs and/or batch users. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Data sets to be protected will be: SYS2.IOA.*.CTDI. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(<syspaudt>) DSN(SYS2.IOA.*.CTDI.) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS2.IOA.*.CTDI.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<audtaudt>) DSN(SYS2.IOA.*.CTDI.) ACCESS(R) TSS PERMIT(<bmcuser>) DSN(SYS2.IOA.*.CTDI.) ACCESS(R) TSS PERMIT(<secaaudt>) DSN(SYS2.IOA.*.CTDI.) ACCESS(R) TSS PERMIT(<secdaudt>) DSN(SYS2.IOA.*.CTDI.) ACCESS(R) TSS PERMIT(<CONTROLD>) DSN(SYS2.IOA.*.CTDI.) ACCESS(R)