If you are installing MOMI for the first time, or updating an existing installation of MOMI, this section will walk you through the installation details using a utility called MOMIFTP.EXE. This utility handles the details transferring MOMI files from the PC to the Tandem via FTP.
If the utility cannot be used, please refer to the ReadMe.txt file for manual installation instructions.
Note: The MOMI Software download EXE file may be altered to a ZIP file by renaming it and changing the extension from .EXE to .ZIP. Conventional utilities that recognize the ZIP format will see and process the file just like any other compressed format. This allows the ability to view the contents of the EXE prior to executing or treat the EXE as a ZIP.
1) If you need MOMI software, download the latest version of MOMI from our web site.
2a) If you downloaded an EXE from our web site:
2b) If you renamed the EXE to a ZIP:
2c) If you have a MOMI CD:
3) The EXE files self extract to a temporary location and launch a program which gives you the option display the ReadMe file or perform either a Normal Installation to the PC or a Server Install Only. Select Normal Installation. The setup on an expanded ZIP or CD will go directly to a Welcome screen. Click through the initial and Welcome screen. Please read and accept the license agreement.
4) Choose the location where the MOMI files on the PC are to be installed.
5) The next screen selects the Setup Type. Choose Complete Installation.
6) Choose the name of the program group for shortcut on the Start menu (typically use the default).
7) Click Next to begin the installation. The installation may take some time if all help formats are installed.
8) Check the box to Install Server Files and click finish.
9) The program MomiFTP is automatically started and will perform the FTP transfer of files from the PC to the Tandem.
10) From a TACL terminal emulator, Logon with the User ID and password to operate $MOMI. Volume to the location where the MOMI files were placed.
11) Edit the file OBYMOMI. This is a TACL obey file used to start MOMI and provide initial configuration information. Page down to the section "set values below here". This marked portion of the obey file is the place to change the initial startup values for MOMI.
Check the process names, CPU $MOMI operates in, priority and home terminal. The default values are usually valid for most systems.
12) Edit the file CONFMOMI . This edit file is used to set various MOMI parameters after startup. Set the System-description and check the TCP/IP process name and port that MOMI will 'listen' on for PC Client connections.
13) SQL/MP compile MOMI (If you don't have SQL/MP, ignore this step):
From a TACL prompt: OBEY OBYCSQL
14) Create BWSSG or the Super Group helper process (see Security Considerations to determine if you need this step):
(these steps omit logons as different users that may be required in your environment)
Purge BWSSG2
Rename BWSSG1, BWSSG2
Rename BWSSG, BWSSG1
FUP DUP BWMOMI, BWSSG,sourcedate (BWMOMIi on TNS/E)
FUP Give BWSSG, <Super.Group> (Super.Super on TNS/E)
FUP secure BWSSG,NGNG,PROGID
15) Start MOMI:
From a TACL prompt: OBEY OBYMOMI
(wait at least 2 minutes before proceeding to the next step)
16) On your PC, start the PC MOMI Client (Start / Programs / BlackWood Systems / MOMI / MOMI). The MOMI Client will detect an initial start on the PC and will prompt for the TCP/IP address of the Tandem and port. The port is defined in the CONFMOMI file and has a default of 2000.
Shortly (or awhile) after starting the MOMI server on the NonStop System, the following message, one per processor, may be logged to EMS:
07-08-19 09:47:46.200 \SYSTEM.$XMnn TANDEM.MEASURE.G09 4016 Measurement 0 $vol.subvol.DCPUS: write to datafile failed. File error 45.
These messages are not a problem and may be ignored. No action is required.
MOMI starts on the NonStop System a measurement (the DCPUS file) configured for a variety of entities (CPU, Process, TMF, etc...). This measurement does not specify an interval but is effectively used for LISTACTIVE purposes. However, MEASURE will write data to this file such as processes stopping. Once the file is full, an error 45 is logged once from each processor in the system.
Even after the DCPUS file fills, the MEASURE counter records accessed by MOMI are still available. MOMI continues to access the counters via LISTACTIVE (the DCPUS file is not really used, but it must be present for MEASURE).
Later releases of the Operating System provide a means within MEASURE to prevent this error. If available, this feature it is automatically enabled by MOMI.