The TACL obey file OBYMOMI provides the means to start MOMI.
1) Insure the MEASURE subsystem is running on your NonStop System.
Failure to start MEASURE will cause a MEASURE NOT RUNNING error in the MOMI PC Client.
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.
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 (or use the process name specified in the OBYMOMI file)
3) Other MOMI processes will perform cleanup and stop themselves automatically after 10 to 15 seconds.
The System administrator should add the necessary references to MOMI in the system start up 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 start up 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 start up 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 start up
...
In the system start up files, MOMI should be started after TCP/IP, MEASURE, and the home terminal specified in OBYMOMI are all started, perhaps near the end of the system start up sequence.
In the system shutdown files, MOMI should be stopped early in the shutdown sequence and before the MEASURE subsystem is stopped.