System Installation Choices › Parameter Library › SYSn.IPLPARM

SYSn.IPLPARM

If HCD (hardware configuration definition) defines the I/O configuration, you should also consider the following to be another high level on the inverted tree structure of parmlib:

• The SYSn.IPLPARM data sets on the IODF volume
• The SYS1.PARMLIB data set on the IODF volume and then on the SYSRES volume

You should also investigate update access to these data sets and the data sets they point to, especially the IODF data set.

If HCD is not used, you should still investigate update access to any data set the LOADxx member in SYS1.PARMLIB points to, especially the MVSCP data set.

These data sets are significant from an auditing perspective because they determine where the LOADxx member is loaded from, and the LOADxx member can determine the data sets which together comprise the logical Parmlib concatenation.

Also important is the eight-byte LOADPARM value specified by the operator at IPL time. This specifies the four-byte address of the IODF volume, and also specifies the two-character suffix of the LOADxx member to be used.

An audit of operational IPL procedures might be considered to verify that the IODF address to be used, along with the LOADPARM value which identifies both the IODF volume address and the LOADxx member suffix is valid.