OSI/MHS Configuration and Management Manual
Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-73
Summary
they are also known as the registration database. If you follow the default installation 
procedure, they will reside in one subvolume. 
After you install the OSI/MHS subsystem, you use ADD commands to configure it. You 
start by adding the SUBSYS object:
ADD SUBSYS $ZMHS.#SUBS1, USER-FNAME $VOL1.REGDB.APPLS, &
 MTA-ASSOC-FNAME $VOL1.REGDB.MTAS, &
 ROUTING-FNAME $VOL1.REGDB.ROUTES, OSI-MGR $OSI, &
 ISO-COUNTRY-NAME US, ADMD-NAME ATT, &
 MTA-NAME TANDEMMTA, MTA-DESIGNATOR POSTMAN
The attributes USER-FNAME, MTA-ASSOC-FNAME, and ROUTING-FNAME tell 
OSI/MHS the names of the user, association, and routing databases. The attribute 
OSI-MGR tells the name of the OSI manager process for OSI/AS. The remaining 
attributes help to locate and identify this OSI/MHS subsystem.
Later, you might need to relocate the registration database (probably to balance the 
use of different disks.) The component databases must remain on the same node as 
the MHS manager process. HP recommends that you keep them together in a single 
subvolume.
Before you can move the databases, you must stop the subsystem. After moving the 
databases, you can restart the subsystem. Then you would use the ALTER command 
to tell the subsystem where the databases are located. The following commands 
would stop the subsystem, then reconfigure it to look at a new volume, subvolume, and 
file for APPL registrations:
STOP SUBSYS $ZMHS.#SUBS1
ALTER SUBSYS $ZMHS.#SUBS1, USER-FNAME $VOL2.SUBVOL2.USERS
You can also use the ADD or ALTER command to establish or alter the way OSI/MHS 
handles the accounting of subsystem activity:
ALTER SUBSYS $ZMHS.#SUBS1, ACCT-REGISTRATION ON
START SUBSYS $ZMHS.#SUBS1
When the ACCT-REGISTRATION attribute is turned on and the subsystem restarted, 
OSI/MHS reports to the EMS alternate collector whenever an APPL object (user 
application record) in the registration database is added, deleted, or modified. This 
example sets the ACCT-REGISTRATION attribute to ON. (The default is OFF.)
Summary
The OSI/MHS management environment consists of the OSI/MHS management 
components (the MHS manager and the MHS databases) and the DSM management 
components (SCF, SCP, and EMS). You manage your subsystem by using one of 
these interfaces to manipulate OSI/MHS objects. You also use EMS to monitor system 
events and accounting events.










