NET/MASTER RMS Management and Operations Guide

ZRMSAPIN ( XFER )
RMS Procedure Calls
C–20 115415 NonStop NET/MASTER RMS Management and Operations Guide
If the target 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.
Record locking occurs automatically during the transfer of the ruleset if the
specified UDB file ID to which the ruleset is to be transferred is the current RMS
database ZRMSDB; this is to ensure that the transferred data is consistent.
If the Merge option is specified, records contained in the source ruleset that are not
yet in the target ruleset are transferred to the target ruleset. All records with the
same names remain unchanged. The control options record of the target ruleset (if
it exists) is not updated.
If the Replace option is specified, the target ruleset is removed and replaced by the
source ruleset. The target ruleset adopts all records of the source ruleset.
Immediate activation, if specified, occurs only when the destination database is the
current RMS database ZRMSDB. Immediate activation of the ruleset occurs when
the current message has completed processing.
Example
The following example shows a user NCL procedure SAMPLE which calls the NCL
procedure ZRMSAPIN ( XFER ) to transfer the ruleset SAMPLE1 from the Guardian-
format file $DATA.RODA.ZRMSDB to the current database ZRMSDB:
SAMPLE: PROCEDURE
&FILENAME=“$DATA.RODA.ZRMSDB”
&RULESET=“SAMPLE1”
&DB=“ZRMSDB”
CALL ZRMSAPIN (XFER,FNAME,&FILENAME,&RULESET,FID,&DB,R,I),
SHARE=&SYSMSG
END SAMPLE
The source ruleset SAMPLE1 replaces the ruleset in the current database, and the
transferred ruleset becomes immediately available to the message handler.