NET/MASTER RMS Management and Operations Guide

New and Changed Information
115415 NonStop NET/MASTER RMS Management and Operations Guide iii
The following sections in this guide contain new or changed information:
Notation Conventions
The subsection “Boldface” now precedes the subsection “Underline _.”
Section 1 Introduction to RMS
Editorial changes only.
Section 2 Message Handlers, Timers, Rulesets, and Rules
The subsection “Continuity of Message Handler Operation” has been updated. If the
Event Management Service Process (EMSP) fails and is recreated, EMSPROC fails and
is restarted. Messages received from slightly before the failure are resent to
EMSPROC. Therefore, you must cater for the case of EMSPROC receiving some
duplicate messages.
The subsection “Queuing of Rule Actions” has been updated to include additional
information on NCL queues.
Section 3 Planning For, Installing, and Managing RMS
Information in the subsections “Installing RMS on Your System,” “Making RMS
Operational,” and “Securing RMS Files” has been reorganized. The subsection
“Making RMS Operational” has additional information that describes how to make
RMS operational during or after NonStop NET/MASTER MS startup. The new
subsection “Verifying That RMS Is Successfully Initialized” contains some of the
reorganized information.
The subsection “Limiting Concurrent Rule Actions” is new. It describes how to limit
the number of rule actions that can concurrently execute using NCL queues.
The subsection “Customizing the BASERULE Rules” has been updated. The
RMS : System Action panel (in Steps 7, 10, and 13) shows the new NCL Queue field.
Section 4 Getting Started
Figure 4-1 has been updated to show the new Display/Delete Delayed Message
Actions option on the RMS : Message Action Control panel.
The subsection “Developing the Ruleset” has been updated. The RMS : System Action
panel (in Step 27) shows the new NCL Queue field.
Section 5 Creating and Developing Rulesets and Rules
The subsection “Specifying the Message Action Rule Actions” has been updated. It
cautions that, when automating tasks, you must allow for rules performing actions
that have already been performed.
The subsections “Specifying the Message ID,” “Specifying the Subsystem ID,” and
“Specifying the Message Profile Variable” have been updated to include additional
information about using the wild-card characters question mark (?) and asterisk (*).