NET/MASTER RMS Management and Operations Guide

Making RMS Operational
Planning for, Installing, and Managing RMS
3–4 115415 NonStop NET/MASTER RMS Management and Operations Guide
Refer to the NonStop NET/MASTER MS System Management Guide for more information
about customizing the INIT NCL procedure.
Initializing RMS and Activating the EMSPROC Message Handler With the BASERULE Ruleset
To initialize RMS and activate the EMSPROC message handler with the BASERULE
ruleset, follow these steps:
1. Leave the distributed INIT NCL procedure provided by Tandem in the
distribution procedure library. Do not rename or edit this NCL procedure.
2. Create a customized INIT NCL procedure in the customized procedure library.
Choose a name other than INIT for this NCL procedure: for example, CUSTINIT.
3. Add the PARAM INIT command to the CONFIG file with the name of the
customized INIT NCL procedure. For example, if you want to use a file named
CUSTINIT, include this command in the CONFIG file:
PARAM INIT=CUSTINIT
Refer to the NonStop NET/MASTER MS Command Reference Manual for more
information about the PARAM command.
4. Edit the customized INIT NCL procedure, CUSTINIT. Ensure that the first
executable statement in the NCL procedure is a CALL core statement that calls
and passes the RMSBASE initialization option to the distributed INIT NCL
procedure. The complete syntax of the CALL core statement is the following:
CALL INIT( [ PRELOAD | NOPRELOAD ], [ RMSBASE | NORMSBASE ] )
PRELOAD
Refer to the NonStop NET/MASTER MS System Management Guide for more
information.
NOPRELOAD
Refer to the NonStop NET/MASTER MS System Management Guide for more
information.
RMSBASE
specifies that RMS is to be initialized and an EMSPROC message handler
activated with the BASERULE ruleset.
NORMSBASE
specifies that RMS is not to be initialized, nor is an EMSPROC message
handler to be activated with the BASERULE ruleset.