z/VM HCD/HCM support for z13 (2965 and 2964) processor: Additional space needed to install HCM APARs (for z/VM 540, 620 and 630)

Updated: February 2016

The size of the z/VM HCM installer (file name EEQINSTM) has increased. This increase means that some of the disks required to service component VMHCD or VMHCDSFS are no longer large enough.

Before installing the z/VM HCD/HCM PTFs required to support the z/13 (2964) processor, you will need to increase the size of several disks (if your products are installed on minidisk) or add space to your Shared File System (SFS) file pool (if your products are installed in SFS). Verify how much space is currently allocated to the VMHCD/HCM service userid and, if necessary, allocate additional space prior to installing the VMHCD/HCM service.

  • For VMHCD/HCM on z/VM 620 or 630:
         If VMHCD/HCM is installed on minidisks, the 6VMHCD20 2D2 disk
         should be at least 750 cylinders (3390) or 135000 4K blocks
         (FBA/SCSI)  The 6VMHCD20 300 disk should be at least 360
         cylinders (3390) or 54000 4K blocks (FBA/SCSI).  If either of
         these disks is smaller than those sizes follow your normal
         procedures to increase the disk sizes.
    

    If VMHCD/HCM is installed in SFS, use the QUERY LIMITS command to determine how many blocks user 6VMHCD20 is authorized to use. To install this and future service, 6VMHCD20 needs to be authorized for at least 330000 blocks. Use the command: MODIFY USER +180000 FOR 6VMHCD20 (the default file pool id for service is VMPSFS) to authorize 6VMHCD20 for 180000 blocks of additional space. Verify that your SFS file pool has at least 180000 blocks of free space using the command: QUERY FILEPOOL MINIDISK (the default SFS file pool for service is VMPSFS). If your SFS file pool does not have at least 180000 blocks of free space, in the same storage group that 6VMHCD20 is in (default is storage group 2), add space to the file pool. Add minidisks for user VMSERVP to total at least 1000 cylinders (or 180000 4K blocks, if using FBA/SCSI volumes) and then use the SFS commands QUERY FILEPOOL MINIDISK and FILEPOOL MINIDISK to add the new minidisks to the file pool. If you are running a multi-member SSI cluster be sure to define these new minidisk on a DASD volume that is shared (Common) by all members of your cluster. See "CMS File Pool Planning, Administration, and Operation" for more information on adding space to a file pool.

  • For VMHCD/HCM on z/VM 540:
         If VMHCD/HCM is installed on minidisks, the 5VMHCD40 2D2 disk
         should be at least 750 cylinders (3390) or 135000 4K blocks
         (FBA/SCSI)  The 5VMHCD40 300 disk and the 5VMHCD40 400 disk
         should each be at least 360 cylinders (3390) or 54000 4K blocks
         (FBA/SCSI).  If any of these disks is smaller than those sizes
         follow your normal procedures to increase the disk sizes.
     
    

    If VMHCD/HCM is installed in SFS, use the QUERY LIMITS command to determine how many blocks user 5VMHCD40 is authorized to use. To install this and future service, 5VMHCD40 needs to be authorized for at least 384000 blocks. Use the command: MODIFY USER +234000 FOR 5VMHCD40 (the default file pool for service is VMSYS) to authorize 5VMHCD40 for 180000 blocks of additional space. Verify that your SFS file server has at least 234000 blocks of free space using the command: QUERY FILEPOOL MINIDISK (the default SFS file pool for service is VMSYS). If your SFS file pool does not have at least 234000 blocks of free space, add space to the file pool. Add minidisks for user VMSERVS to total at least 1300 cylinders (or 234000 4K blocks, if using FBA/SCSI volumes) and then use the SFS commands QUERY FILEPOOL MINIDISK and FILEPOOL MINIDISK to add the new minidisks to the file pool. See "CMS File Pool Planning, Administration, and Operation" for more information on adding space to a file pool.