Allocating the BMC AMI Ops Infrastructure common registry

Before you begin

Consider the following items before allocating the BMC AMI OpsI common registry:

• Decide whether you want to use HFS or zFS for the BMC AMI OpsIcommon registry file system.

  If you are not sure which type of file system to use, check with the system programmer who is responsible for UNIX System Services at your site. BMC recommends using zFS.

• Determine how many BMC AMI OpsIcommon registry file systems you will need. Each CAS can have a BMC AMI OpsIcommon registry, or CASs can share a single BMC AMI OpsIcommon registry. For more information about the BMC AMI OpsIcommon registry, see Managing-the-BMC-AMI-Ops-Infrastructure-common-registry.

• BMC recommends that the file system be mounted off a user mount point or the IBM /var mount point. You must create a directory to use as a mount point for the BMC AMI OpsI common registry file system. Do not choose an existing directory that is used for some other purpose.

  Warning

  • Mounting a file system on an existing directory will make all existing data inaccessible.
  • If the mount point is the system root, the BMC AMI OpsI common registry will not initialize.

  BMC has no dependency on the location of this directory. The best location will depend on your site’s configuration and use of the HFS or zFS file system.

• It is very important that the file system that you allocate (either HFS or zFS) is sized properly and configured to grow dynamically. Be sure to allocate an appropriate number of primary and secondary extents on a volume that has available free space.

  When you allocate the initial file system, specify at least 75 MB of initial storage. Since the majority of the storage is used for alarm definitions, you can use the following formula to estimate the amount of space that is required for your alarm definitions:

  Size (in bytes) = Number of Alarms x 1.5 x 100,000

• If you decide to use zFS, keep the following considerations in mind:
  • zFS must be defined on your z/OS system by using the IOEFSPRM PARMLIB member.
  • You should allocate the aggregate in compatibility mode.
  • To ensure that the file system can grow dynamically if it requires more space, use the AGGRGROW IOEFSPRM option or the AGGRGROW MOUNT parameter.
• The CAS and PAS started task procedures must have read and write access to the file system that you allocate.

To allocate the common registry file system

1. Copy the appropriate BBSAMP member to your UBBSAMP data set.
   You can use one of the following members as a model for allocating and mounting the BMC AMI OpsI common registry file system:
   • HFSALLOC to allocate and mount an HFS file system
   • ZFSALLOC to allocate and mount a zFS file system
2. Modify HFSALLOC or ZFSALLOC as described in the member.
3. Save the modified member and submit the job.
4. Repeat these steps for each file system that you want to allocate.

Where to go from here

Before you can use the allocated file system, you must perform the following tasks:

• Mount the file system (HFS or zFS) on the operating system.

  You must add a MOUNT statement to the BPXPRMxx member in SYS1.PARMLIB. The MOUNT statement will mount the file system on subsequent IPLs.

• Identify a mount point for the file system to each CAS.

  You must use the Plex Manager HFSPATH view to identify the mount point. For more information, see the Managing-the-BMC-AMI-Ops-Infrastructure-common-registry.