Access to IPL Information

The automation function that collects, displays, compares, and deletes IPL information uses two started tasks. It is recommended that you run the first started task immediately after an IPL as part of COMMNDxx list processing to collect the IPL information in the SA z/OS VSAM data set "IPLDATA".

The remaining functions are handled by a NetView command. Because the started task and the command can delete IPL information, both need RACF® CONTROL access to the VSAM data set. The started task that collects the information needs RACF READ access to all parmlib members.

When a comparison of IPL information is requested, the NetView command schedules the second started task to call ISRSUPC (the compare utility provided by ISPF) because this utility requires a fixed ddname. The input and output data sets that are used by the second started tasks are dynamically allocated and deleted by the NetView address space. This requires RACF ALTER access to these data sets for NetView. In case the security option OPERSEC is set to SAFDEF or SAFCHECK, the invoking NetView user ID must be granted with the RACF ALTER access. For any other OPERSEC values, the NetView started task user ID must be granted with this access.

When the address space of the started task is created, the operating system assigns a user ID to the started task (the IBM® default is STCUSER). This user ID must have RACF UPDATE access to the data sets. The data set names are created as follows:

  hlq.domain.opid.INGPIPLx

Where:

hlq: is the high-level qualifier for temporary data set defined during the customization
domain: is the domain ID of the current NetView
opid: is the NetView operator ID
x: L, N, or O