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.

Alarm definition file system structure

MainView Alarm Management uses the MainView Infrastructure (MVI) common registry to store alarm definitions.

The MVI common registry is a UNIX System Services (USS) HFS or zFS file system.

The HFS and zFS file systems provide the ability to use directory structures to organize the alarm definitions. You provide an initial directory, and MVI common registry creates the directory structure for your alarm definitions. Your alarm definitions and libraries can be shared within a sysplex.

In previous MainView Alarm Management versions, the PDS file system storage limited the group name to two characters, but with the new alarm definition directory structure alarm, group, and the new library names are expanded to eight characters.

In the new HFS and zFS file systems, alarm definitions are stored one to a file, and they are stored in the file system as follows:

  • FILESYSTEM/Library001/Group001/alarmDefinition
  •           /Library002/Group001/alarmDefinition

Inside the file system each library is represented by a directory, each group within a library is represented by a directory, and the alarm definitions are files within the group directory. The same group name my be in several libraries.

Allocating and mounting the file system

The HFS or zFS file system must be mounted and allocated to grow as needed to accommodate additional alarm definitions.

The file system is allocated during customization by using MainView Customization or manually using the information in the Manual customization.

To identify the file system to a CAS, use the PLEXMGR view HFSPATH. See Administering for more information.

Related topic

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