The ISSO will ensure that WRITE and/or greater access to program product user datasets is limited to systems programmers, and all WRITE and/or greater access is logged. Ensure that READ access is limited to auditors, operations personnel, and automated operations users. 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 UPDATE 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. Datasets to be protected will be: The production IODF datasets (i.e., hhhhhhhh.IODFnn) The working IODF datasets (i.e., hhhhhhhh.IODFnn) The activity log for the IODF datasets (i.e., hhhhhhhh.IODFnn.ACTLOG) Note: Currently on most CSD systems the prefix for these datasets is SYS3.IODF*.**. The following commands are provided as a sample for implementing dataset controls: SET RULE $KEY(S3I) $PREFIX(SYS3) IODF-.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) IODF-.- UID(tstcaudt) R(A) W(L) A(L) E(A) IODF-.- UID(audtaudt) R(A) E(A) DATA(DEFAULT Auditor) IODF-.- UID(autoaudt) R(A) E(A) IODF-.- UID(operaudt) R(A) E(A)