| The ISSO will ensure that update, and alter access to program product user data sets is limited to systems programmers and all update and allocate 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 user data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.
Data sets to be protected will be:
The production IODF data sets. (i.e., hhhhhhhh.IODFnn)
The working IODF data sets. (i.e., hhhhhhhh.IODFnn.)
The activity log for the IODF data sets. (i.e., hhhhhhhh.IODFnn.ACTLOG)
Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**.
The following commands are provided as a sample for implementing dataset controls:
ad 'sys3.iodf*.**' uacc(none) owner(sys3) -
audit(success(update) failures(read)) -
data('Vendor DS Profile: IODF for HCD')
pe 'sys3.iodf*.**' id(syspaudt tstcaudt) acc(a)
pe 'sys3.iodf*.**' id(audtaudt autoaudt operaudt) acc(r)