The ISSO will ensure that WRITE and/or greater access to BMC IOA installation datasets is limited to systems programmers only. READ access can be given to auditors, BMC users, operations, production control and scheduling personnel, 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 datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)
Datasets to be protected will be:
SYS2.IOA.*.IOAI
The following commands are provided as a sample for implementing dataset controls:
$KEY(SYS2)
IOA.-.IOAI.- UID(<syspaudt>) R(A) W(L) A(L) E(A)
IOA.-.IOAI.- UID(<tstcaudt>) R(A) W(L) A(L) E(A)
IOA.-.IOAI.- UID(<audtaudt>) R(A) E(A)
IOA.-.IOAI.- UID(<bmcuser>) R(A) E(A)
IOA.-.IOAI.- UID(<operaudt>) R(A) E(A)
IOA.-.IOAI.- UID(<pcspaudt>) R(A) E(A)
IOA.-.IOAI.- UID(BMC STCs) R(A) E(A)