NET/MASTER RMS Management and Operations Guide

Transferring Rulesets Between RMS Databases
Updating and Maintaining Rulesets, Rules, and Command Groups
115415 NonStop NET/MASTER RMS Management and Operations Guide 6–39
You must enter either a UDB file ID or the name of the file in which you want to
receive the source ruleset. The UDB File ID field and the Filename field are
mutually exclusive, and must represent an RMS database. The fields are described
below:
The UDB File ID field indicates the logical file ID of an open user database in
the current NonStop NET/MASTER MS system. The UDB file ID is one
through eight characters long, beginning with a character other than a digit.
Record locking occurs automatically during the transfer of the ruleset if the
specified UDB file ID is the current RMS database ZRMSDB. This ensures that
the transferred data is consistent.
The Filename field indicates a Guardian-format file name suitable for access
with the UDBCTL OPEN command. The Filename field has the format:
[ \sys .] [ $volume. ] [ subvolume. ] filename.
You can enter the name of the ruleset in the Ruleset Name field. If the Ruleset
Name field is left blank, the ruleset name defaults to the source ruleset name.
If the source ruleset does not exist on the destination database, a new ruleset is
created with the specified ruleset name. Records belonging to the source ruleset
are also transferred to the new ruleset in the destination database.
If the ruleset name specified in the Ruleset Name field exists on the destination
database, you must determine whether you want to replace or merge the source
ruleset with the target ruleset.
The Merge/Replace field is used to determine whether the ruleset from the source
database entirely replaces the target ruleset in the destination database, or whether
the source ruleset merges with the target ruleset in the destination database.
The Merge/Replace field can consist of the following values:
Value Description
M Records in the target ruleset with the same names as records in the source
ruleset remain unchanged. Records that are contained in the source ruleset that
are not yet in the target ruleset—for example, a rule or the environment profile—
are transferred to the target ruleset. The control options record of the target
ruleset (if it exists) is not updated.
R The target ruleset is removed and replaced by the source ruleset. The target
ruleset adopts all records of the source ruleset.
The Activation field determines whether the transferred ruleset is immediately
available to the message handler, or whether activation of the ruleset is deferred
until the next time the message handler is started.