The TACL obey file OBYMOMI provides the means to start MOMI.
1) Insure the MEASURE subsystem is running on your Tandem system.
2) Start MOMI from a TACL prompt:
volume MOMI (subvolume where files were placed)
obey OBYMOMI
3) Once MOMI is started, you are ready to run the PC based MOMI Client. When cold loading your Tandem system, in the system startup files perform the OBYMOMI after MEASURE, TCP/IP and the home terminal referenced in the OBYMOMI file have been started.
MOMI only requires a Guardian stop from a TACL prompt for an orderly shutdown.
1) From a TACL prompt, LOGON with the User ID MOMI was started under.
2) STOP $MOMI (use the process name selected in the OBYMOMI file)
3) Other MOMI processes will stop themselves automatically after 10 to 15 seconds.
The Tandem system administrator should add the necessary references to MOMI in the system startup and shutdown procedures.
Generally, the system administrator will use a TACL running under the super.super ID to reference a stream of other TACL files that perform the startup of various software components. The original TACL obey file will use a TACL / in ... / of an intermediary obey file. The intermediary obey file created by the system administrator performs a log-down (from super.super) to the selected MOMI User ID and then obeys the OBYMOMI file. Below is an obey file fragment (details are omitted):
...
... main startup obey file executing as super.super
TACL /in STRTMOMI, out strtlog, name/
... in the STRTMOMI file ...
Logon user.momi
volume $vol.momi
obey OBYMOMI
... continue system startup
...
In the system startup files, MOMI should be started after the MEASURE subsystem is started and near the end of the system startup sequence.
In the system shutdown files, MOMI should be stopped early in the shutdown sequence and before the MEASURE subsystem is stopped.