zCX instance Z file system (zFS) allocation
A new Z file system (zFS) is allocated and mounted on the newly created instance directory when executing the zCX provisioning workflow. As part of provisioning, the workflow will explode the compressed binaries and build the instance image in the zFS directory before loading the image on the ROOT VSAM data set. An uncompressed image size is around 3500 MB, and the zFS must have enough space to hold the uncompressed image before it is loaded on the ROOT VSAM data set and removed from the file system.
The recommended zFS allocation size is greater of 4095 MB, or 1.5x the zCX instance memory requirement (ZCX_MEMGB). In addition to the uncompressed root image, the zFS instance directory also holds the FFDC information for the zCX instance.
IBM recommends updating the BPXPRMxx member mount statements to include the zFS mount on the instance directory to persist after IPL.
| Variable | Description | Required | Default (if applicable) |
|---|---|---|---|
| ZCX_ZFS_FILESYSTEM_HLQ | Specify a high level qualifier to use for zFS file system allocation. The high level qualifier can be up to 28 characters including periods. The zCX workflow constructs the fully qualified zFS file system name using the specified high level qualifier and the unique instance name. The zFS file system is used to hold the zCX appliance instance specific details and FFDC information for the zCX appliance instance. | Yes | |
| ZCX_ZFS_ENCRYPT | Flag to indicate whether to encrypt the zFS file system that is mounted on the zCX instance
directory. The encryption key label must be predefined using either the RACF DS profile for the zFS
file system high level qualifier or with the SMS data class construct to use the encrypt option.
Once the encryption key label is defined, the zFS file system VSAM linear data set is defined with an encryption key label. The encryption process uses the VSAM encryption support that is provided by DFSMS. When zFS encrypts a file system, it encrypts all security information, access control lists, symbolic link contents, and file contents. |
Yes | |
| ZCX_ZFS_VOLUME | This is the zFS volume name that is used for allocation. | Depends on whether it is SMS managed and site installation requirements. Check with the storage administrator for more details. | |
| ZCX_ZFS_PRIMARY_MEGABYTES | This is the primary megabytes that are used for zFS allocation. The recommended zFS
filesystem allocation size is greater of 4095MB or 1.5X of the zCX Appliance Instance memory
specification (ZCX_MEMGB). |
Yes | 4095 MB |
| ZCX_ZFS_SECONDARY_MEGABYTES | This is the secondary megabytes for the zFS allocation. | Yes | 1000 MB |
| ZCX_ZFS_DATACLAS | This is the DATACLAS that is used for zFS allocation. | Yes, if the zFS being allocated is greater than 4 GB and requires extended addressability specification. Extended addressability specification may be required for zFS file system allocation depending on site installation requirements. Check with the storage administrator to obtain the DATACLAS specification. | |
| ZCX_ZFS_STORCLAS | This is the zFS STORCLAS to use for SMS-managed file system allocation. | Yes, if the zFS file system being allocated is greater than 4 GB and requires extended addressability specification. Extended addressability specification may be required for zFS allocation depending on site installation requirements. Check with the storage administrator to obtain the STORCLAS specification. | |
| ZCX_ZFS_GROUP_NAME | This is the SAF group that controls access to the zCX appliance instance directory. The started task user must be connected to this group. | Yes | |
| ZCX_ZFS_MGMTCLAS | This is the zFS file system MGMTCLAS to use for SMS managed storage zFS file system allocation. | SMS managed storage specification may be required for zFS file system allocation in your site. Check with your storage administrator and obtain the MGMTCLAS specification. |