NET/MASTER RMS Management and Operations Guide

Managing the RMS UDB File
Planning for, Installing, and Managing RMS
3–8 115415 NonStop NET/MASTER RMS Management and Operations Guide
3. Change the name of the file used in the command for each system-level NCL
procedure to ZRMSMGHN (the name of the message handler NCL procedure file).
For example, you may have the following statement in your READY procedure:
CMD 'SYSPARMS EMSPROC= filename '
filename is the name of the NCL procedure that you want to start as an
EMSPROC. To use the RMS message handler instead, change the statement to the
following:
CMD 'SYSPARMS EMSPROC=ZRMSMGHN'
Managing the RMS
UDB File
RMS stores its data (for example, rulesets) in the user database (UDB) file ZRMSDB.
The file is in the NonStop NET/MASTER MS subvolume $vol.ZNNMDATA, where vol
is the name of the volume. RMS organizes its data into records. For example, each of
the following is a record:
Control options of a ruleset
A rule
Default ruleset allocation for a user
A message set
You can use the following Guardian FUP INFO command to obtain the attributes of
the ZRMSDB file, including the size of a record in the file:
FUP INFO $ vol .ZNNMDATA.ZRMSDB,DETAIL
The initial size of ZRMSDB is 32 KB, and the size extends to a maximum of 2 MB as
new records are created. When the file becomes full, you can resolve the problem by
doing one or both of the following:
Use the RMS panel interface to delete out-of-date rulesets, rules, command groups,
and message sets from ZRMSDB. See Section 6, “Updating and Maintaining
Rulesets, Rules, and Command Groups,” on how to perform deletions.
Use the Guardian FUP ALTER command to increase the value of the
MAXEXTENTS attribute of ZRMSDB; that is, increase the maximum number of
extents that can be allocated to the file. (An extent is a unit of storage allocation
for a file and is allocated as contiguous space on disk.) Each extent consists of
some specified number of 2048-byte pages. For example, issue the following
command to double the maximum possible size of ZRMSDB by increasing the
MAXEXTENTS attribute to 32 pages:
FUP ALTER $ vol .ZNNMDATA.ZRMSDB,MAXEXTENTS 32