System Requirements › DASD Space Requirements

DASD Space Requirements

The following sections contain information on the space requirements for CA‑ACTIVATOR, CP minidisks, and CMS minidisks.

Minidisk Configuration

If you are installing CA ACF2 for z/VM for the first time, you need to define and format the following disks.

Required CAIMAINT Minidisks

Optional CAIMAINT Minidisks

Required Minidisks

Optional Minidisks

Required Service Machine Minidisks

Optional Service Machine Minidisks

Notes:

1. You can combine all 2A3 minidisks as a single 26 cylinder minidisk (4680 blocks). You can also combine all 3A3 minidisks as a single 26 cylinder minidisk (4680 blocks). We recommend you leave enough space for future maintenance.
2. This disk contains the PROFILE exec for the CA‑ACF2 service machine.
3. This disk contains the ACFFDR TEXT file, the ACF2VM MODULE file, the ACFSTART EXEC, the CALMP KEYS file, and any user‑written exits that reside in the CA ACF2 for z/VM service machine. The CA ACF2 for z/VM service machine accesses in read‑only to let another user update the ACFFDR while the service machine is running. Whenever you issue the ACFSERVE RELOAD FDR command or the ACFSERVE RELOAD LMP command and you have accessed the disk in read‑only, the CA ACF2 for z/VM service machine reaccesses this minidisk to ensure it uses the latest version of the ACFFDR TEXT or CALMP KEYS files.
4. This disk contains backups of the CA ACF2 for z/VM databases. The minidisk must be large enough for all backup files, have enough extra space for the largest backup file, and room for growth. Backup files have a filetype of BACKUPDB. The files have a record format of sequential variable length for both CMS and VSAM databases. The space allocation shown assumes the sample CMS database sizes. After you have successfully taken backups, use the actual size of the backup files to determine the disk size.
5. During installation, these minidisks will be formatted with 4k blocks and reserved with the CMS RESERVE command. We have based the space allocation shown in the chart on the following specification:

   Logonid database

   Holds 2,880 logonid records. Each additional cylinder of 3390 disk (180 4 Kb blocks) holds an additional 720 logonid records.

   Rule database

   Holds 1,440 rule records, assuming an average rule record length of 2 Kb. Each additional cylinder of 3390 disk (180 4 Kb blocks) holds 360 more rule records.

   Infostorage database

   Holds 720 infostorage records, assuming an average infostorage record length of 2K. Each additional cylinder of 3390 disk (180 4 Kb blocks) holds 360 more infostorage records.

6. During installation, these minidisks will be formatted with 4k blocks and reserved with the CMS RESERVE command. The CA ACF2 for z/VM service machine automatically accesses the SMF minimidisks. If you add SMF disks at a later time, they will need to be formatted with 4k blocks and reserved with the CMS RESERVE command with a file id of:

   SMF 00000000 fm
   

7. This disk contains the CA ACF2 for z/VM STARTUP OPTIONS file. This disk must be one cylinder on CKD DASD or a 12 or more block FBA minidisk.
8. These disks contain alternate CMS databases if you want to use them. Set them up using the criteria in number 6.
9. This disk contains the CA ACF2 for z/VM command modules. Let all users who execute the ACF, ACFCOMP, ACFDCMP, and ACFNRULE commands access it.
10. This disk contains the CA ACF2 for z/VM report generator modules and exec. Let all users who generate CA ACF2 for z/VM reports access it.
11. This disk contains the CA ACF2 for z/VM help files. Let all users who can use the CA‑ACF2 help facility access it.
12. This disk contains executable CA ACF2 for z/VM full‑screen files. Let all users who can use the CA ACF2 for z/VM full‑screen feature access it.
13. If you have already installed other CA products on this CAIMAINT disk, you need this much free space on this disk before beginning to install CA ACF2 for z/VM. This ensures you have sufficient space for both the initial CA ACF2 for z/VM installation and future genlevel maintenance. If you want to place the CA ACF2 for z/VM documentation on this disk, increase the size by 30 cylinders (5400 blocks).
14. If you have already installed other CA products on this CAIMAINT disk, you need this much free space on this disk before generating a production CA ACF2 for z/VM system.
15. If you maintain separate test and production systems with separate CAIMAINT machines for each system, this disk is not required.

VSAM Database Configuration

If you are using Shared Database Support (systems shared across different operating systems), you must allocate space for the CA ACF2 for z/VM primary databases. The following table lists the number of records that fit on one cylinder of data component space. It also lists the number of records that fit on one track of index component space. Use the data in the following chart and your projected record count to estimate the space you need for the CA ACF2 for z/VM databases:

We have based these estimates on the following assumptions. Make adjustments as needed for your site.

• The logonid record size is 1,024 bytes and 4,096 bytes for access rule sets and infostorage records.
• The control interval size for all data and index components is 4,096 bytes.

Be sure to allocate space for the backup data sets. Space allocations for the sequential backup data sets should be approximately equal to the size of the catalog component of the corresponding cluster.

Required CP Minidisks

You should access all the minidisks required to assemble CP modules and generate CP. Refer to the IBM documentation for the appropriate disks to generate your system.