Alarm definition file system structure
Alarm Management
uses the
BMC AMI Ops Infrastructure
(
BMC AMI OpsI
) common registry to store alarm definitions.
The BMC AMI OpsI 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 BMC AMI OpsI common registry creates the directory structure for your alarm definitions. Your alarm definitions and libraries can be shared within a sysplex.
In previous 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:
/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 can 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 configuration or manually using the information in Manual-customization.
To identify the file system to a CAS, use the PLEXMGR view HFSPATH. For more information, see Administering.
Related topic