Required data sets

zSecure Alert requires the following data sets:
  • A dedicated CKFREEZE data set. This data set must pertain to the z/OS® image where zSecure Alert is running, and so it cannot be shared with zSecure Alert on other z/OS images. Because of serialization issues, the data set cannot be shared with zSecure Admin or zSecure Audit. The C2PCOLL address space periodically refreshes the contents of this CKFREEZE data set.
  • Data sets with intermediate data for the C2POLICE address space. In the JCL, these data sets are identified as SYSPRST1, SYSPRRPT, SYSPRCKF, C2P1OUT, and C2PEMFRB. The C2POLICE address space allocates them as shared so that you can view them for diagnostic purposes, but they must not be otherwise shared. By default, these data sets contain the system id in their names.
  • The Alert configuration data set. This is the data set that you previously specified in the zSecure configuration. It is written into from the ISPF interface when option SE.A "Configure zSecure Alert" is used to customize zSecure Alert. The data set must be a PDS/E to prevent space abend. A PDS/E can be shared between system images. If the data set is shared between system images, then a different configuration can be used for different images, but they can also be the same.

    Make sure that the Alert configuration data set is well protected against any attempt of intrusion into its configuration. For instance, intruders could find out the cell-phone numbers that are used for your alert messages and saturate them with messages that do not look intrusion-related before starting the actual intrusion.

    When upgrading from a previous release of zSecure, do not create new configuration data sets. Instead, continue to use the data sets that contain the results of your earlier configuration effort.

Job C2PZAIN1 in the SCKRSAMP library is supplied to assist you in creating these data sets. Before submitting, customize as follows:
  • Unless you updated the default zSecure configuration, change the JCLLIB and INCLUDE statements to specify the zSecure Alert-enabled zSecure configuration you prepared.
  • If you install zSecure Alert on multiple z/OS images, you must run the job multiple times: once with each zSecure configuration. Preferably, run each of these jobs under the z/OS image where the corresponding zSecure Alert is to run. If this is not possible (for example, because you are installing into a z/OS image that has not yet been IPL'd), make sure that all data sets are allocated on volumes that are accessible from the intended z/OS image.
  • If you want to share the zSecure Alert configuration data set among z/OS images, remove the C2PCUST allocation from all C2PZAIN1 runs except one.