In order for MOMI to collect information on a timely basis, it must run at a priority high enough so that the other programs on the system do not 'walk over' or interrupt operation.
The diagram above shows the relative process priorities of $MOMI and its server programs.
MOMI, to divide its workload, starts several copies of itself. The main program $MOMI, is the master traffic cop, data collector and data reporter. MOMI also starts a copy of itself in every CPU in order to collect information about that CPU. All information collected is reported back to $MOMI. $MOMI and the CPU collectors consume a fairly consistent portion of CPU resources, with $MOMI varying the most, based on incoming requests from the PC Clients.
By default, $MOMI and the collectors in each CPU run at a rather high priority of 170. This priority is set in the OBYMOMI file.
MOMI also starts other processes based on needs of the PC Client and generally run at default priorities in the 80 to 95 range. These priorities can be adjusted in the CONFMOMI file.
If you have concerns with the priority of the MOMI environment, you could run $MOMI at a lower priority than your critical production programs. Please be aware that running $MOMI at a lower priority could prevent the timely collection and reporting of data (usually showing up as random interruptions). In the Main Overview screen you may see MOMI CPU collectors reporting as HUNG or STOP. Once you have tested and are comfortable with the operation of MOMI on your system, MOMI should run at a rather high priority to help to insure consistent data collection and reporting.