OSI/MHS Configuration and Management Manual
Installing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
4-5
Keyword Defaults
You must specify at least one pair of MR_ keywords for every OSI/MHS subsystem. 
You do not need to specify any MS_ keywords unless you plan to configure message 
stores. You do not need to specify any RS_ keywords unless you plan to configure 
remote operations service groups. You do not need to specify any GI_ keywords 
unless you plan to configure gateway interfaces. You do not need to specify any LO_ 
keywords unless you plan to configure local user agents.
Keyword Defaults
The installation procedure always supplies a default value for all keywords with 
prefixes of MR_, MS_, and RS_ that have a suffix of 1. These keywords are: 
MR_PDU_STORE_DATA1
MR_PDU_STORE_LOG1
MS_SQL_DATABASE1
MS_PDU_STORE_DATA1
MS_PDU_STORE_LOG1
RS_PDU_STORE_DATA1
RS_PDU_STORE_LOG1
The exact file-name value supplied for these keywords depends upon your current 
volume when you run the installation procedure.
A keyword and its value are used only if its corresponding step is set to yes in the 
installation file. If you set the corresponding step to no, the keywords for that step are 
not used. For example, if you set
CREATE_RS_DATABASES 
to no, the keywords prefixed with RS_ are not used during that run of the installation 
procedure.
Installation File Examples
This subsection contains three examples of installation files. All examples assume that 
your current volume and subvolume are $MYVOL.OSIMHS. The three examples are 
as follows:
•
A basic skeleton file named Install1. This file is for a first-time installation.
•
A customized file named Install2. This file is for a first-time installation, but 
multiple MS, MR, RS, GI, and LO groups have been added to suit the needs of a 
particular department or company.
•
A customized file named Install3. This file is for an upgrade from an earlier version 
(D20 or D21) to D22. Multiple MR, MS, RS, GI, and LO groups have been added 
to the basic file. 
Note. The examples, although shown for upgrading to D22, is also valid for upgrading to D41.










