Space banner


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Before allocating the MainView Infrastructure common registry

Consider the following items before allocating the MainView Infrastructure (MVI) common registry:
  • Decide whether you want to use HFS or zFS for the MVI common 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 MVI common registry file systems you will need. Each CAS can have a MVI common registry, or CASs can share a single MVI common registry. For more information about the MVI common registry, see Managing the MainView 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 MVI common registry file system. Do not choose an existing directory that is used for some other purpose.


    • Mounting a file system on an existing directory will make all existing data inaccessible.

    • If the mount point is the system root, the MVI 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.

Was this page helpful? Yes No Submitting... Thank you