MOMI obtains its information on the Nonstop server platform by running a number of processes that use a combination of data gathered 1) continually, and 2) on demand.
MOMI is started by obeying the file OBYMOMI from a TACL prompt. This obey file starts the initial $MOMI process which serves as the main overseer for the MOMI subsystem. This main MOMI will:
start a master process that configures the main measurement in the MEASURE subsystem
start an Expand collector process
start a collector in each processor of the system
start a process that writes history to the HST01db file
start a process that performs the history consolidation and deletion
start an NSKCOM process for obtaining virtual memory statistics
post a 'listen' on the assigned TCP/IP process(es) and port(s)
The MOMI PC Client issues a TCP/IP connect to the address and port configured to establish communication with $MOMI. $MOMI either provides answers directly to Client queries or passes the request to a server started by $MOMI. The response is returned to $MOMI which is in turn returned to the PC Client.
Sensitive commands that require security are executed in the context of the User ID provided. $MOMI starts a server; the server will Logon under the credentials provided; the server will execute the sensitive commands.
The BWMOMI server uses dynamic SQL/MP statements to obtain information from the system and user catalogs. The dynamic SQL/MP is used in support of the PC MOMI Client screens Files / SQL/MP / *. The TACL obey file OBYCSQL performs an SQL/MP compile of the BWMOMI object with the attribute of NOREGISTER ON (this means that the SQL/MP catalog does not reflect BWMOMI).