NET/MASTER RMS Management and Operations Guide

Migrating From NonStop NET/MASTER MS System-Level NCL Procedures to RMS Message Handlers
Planning for, Installing, and Managing RMS
115415 NonStop NET/MASTER RMS Management and Operations Guide 3–7
Verifying That RMS Is
Successfully Initialized
After NonStop NET/MASTER MS startup completes, verify that RMS is initialized by
following these steps:
1. The NCL procedure ZRMSININ, which initializes RMS, starts the timer driver
NCL procedure ZRMSTDRN. From OCS, issue the SHOW NCL=ALL
PROC=ZRMSTDRN command to verify that the corresponding NCL process
exists. The message NNM1037 appears indicating the presence of the NCL
process.
2. The wake-up timer should have been started. From OCS, issue the SHOW
TIMER=ALL command to verify for the existence of the timer. Two messages
similar to the following indicate the presence of the wake-up timer:
NNM1722 9 AT 23:59:59 SDPLBMON 1 0 NO CUR NO -
NNM1725 MSG=RMSTIMER 23:59:59 930331
The time defaults to 23:59:59 if there are no active RMS timers; otherwise, the time
indicates the time of the next timed event.
Allocating Default
Rulesets
On your system, you may have rulesets developed for use by the different types of
message handlers. You may want to have these message handlers started
automatically with default rulesets, for example, by using the SYSPARMS or the
PROFILE command in an NCL procedure.
Allocate default rulesets to the following users through option 4 on the NonStop
NET/MASTER RMS primary menu panel:
Allocate the ruleset for the EMSPROC to the user didEMSP, where did is the
domain ID.
Allocate the ruleset for the LOGPROC to the user didLOGP, where did is the
domain ID.
Allocate the ruleset for a MSGPROC to the user that requires it.
See Section 7, “Managing Default Rulesets,” on how to allocate default rulesets.
Migrating From
NonStop NET/MASTER
MS System-Level NCL
Procedures to RMS
Message Handlers
On your system, you may already be using NonStop NET/MASTER MS commands to
start system-level NCL procedures to process messages (for example, you may have
customized your NonStop NET/MASTER MS NCL procedure READY to start
EMSPROC and LOGPROC).
You can convert to using RMS message handlers as follows:
1. Incorporate the existing features in your system-level NCL procedures into RMS
rulesets. See Section 5, “Creating and Developing Rulesets and Rules.”
2. Allocate an appropriate ruleset from Step 1 as the default ruleset to the user that
owns the environment in which the message handler using that ruleset executes.
See Section 7, “Managing Default Rulesets,” on how to allocate default rulesets.