Site module
Use of the Site module is optional. The product is fully operational without it. Job CKRZSITE in the SCKRSAMP library is supplied to assist you in creating the Site module.
Table 1 list the zSecure™ options that can be customized in the Site module CKRSITE:
| Parameter | Allowed values | Description | Default |
|---|---|---|---|
| AUTH | SINGLE DOUBLE TRIPLE | Default multi-authority setting. | SINGLE |
| CUSTSPEC | Up to 100 characters of text | Site or customer-specific identifier. This parameter
is included in the SYSPRINT output for various zSecure components.
Because the value is also used as the default CHECKPWD in zSecure Collect, choose a value that can be expected to be stable over a long period (10 years or more). |
<none> |
| CLASS | SAF class name | Resource class for the zSecure security checks. | XFACILIT |
| KEEPCOMMAND | Numeric | Expiration period for CKGRACF queued commands. | 7 |
| KEEPAUDIT | Numeric | Period during which completed and expired queued commands and past scheduled actions are retained by CKGRACF. The value of this setting must be larger than the expiration period. | 30 |
| RESTRICT | Y N | Restricted mode. Alternatively, you can use the general resource CKR.READALL provided by the CLASS parameter instead of this setting. | N |
If you perform a distribution-oriented installation, you might want to use different CKRSITE parameters for different z/OS® images. This configuration can be set up by storing the CKRSITE modules in separate libraries for each image, and concatenating these libraries to the SCKRLOAD library, using either JCL or the WPREFIX/UPREFIX parameter. In line mode, the WPREFIX/UPREFIX parameters only support the SCKRCARL library. Also, note that storing CKRSITE directly in the SCKRLOAD library would be an SMP/E violation because the SCKRLOAD library is SMP/E-managed.