Our standard release migration recommendation is to upgrade the server first and the client second within a release series (i.e. 4.xx, 5.xx and 6.xx). Normally, when a release series changes, both the client and server must both be upgrade at the same time. However, a 5.xx client will operate with MOMI 6.xx.

Please check below for Oldest client version tested with server.

Note that not all features may operate when running a combination of old and new MOMI software.

Special Notes

MOMI software is packaged within an MSI file created by InstallShield and provides the capabilities to install to the PC (all users or current user), copy MOMI software to the NonStop System and copy MOMI software to a shared located.

Short-cuts to MOMI software under the Windows Start menu use the format of BWS MOMI n.nn (where n.nn is the version number).

The PC must be configured with at least 24-bit color for the client to operate fully with MOMI. A warning message is displayed at client startup if a lower color depth is detected. While the client will generally function correctly with a lower color depth, certain features are not available such as the pop-up window when the mouse is placed over the connector lines between systems on the screen SubSystems / Expand / Diagram.

The CAIL Emulator was provided courtesy of CAIL and is not a component of any purchased MOMI product. The Emulator is no longer provided and was removed from the MOMI installation package.

The IP Workshop Pro TCP/IP Subnet calculator is provided courtesy of Peter Kostov and Peko Software and is not a component of any purchased MOMI product. BlackWood Systems and Peko Software reserves the right to discontinue, limit or alter the availability in future releases. Please see the IP Workshop Pro help within the calculator for additional information and to check out other tools he has available.

Release Package 6.18e

Release Date (yyyy/mm/dd) 2025/11/16

Item Version

---- -------

Latest O/S tested J06.23.01 – L25.09.00

Client Version 6.18d Build 924

Server Version (VPROC) 6.18e T0000G06___V6_18e___2025_11_13

Buffer Version Client 21.77 Server 21.77

History database 3.10

CONFMOMI 6.03

OBYMOMI 6.01

OBYCSQL 5.02

MomiFTP.exe 2.16

CentralServer.exe 1.8

ssMOMI.scr 6.00

MomiEMail.exe 1.12

SendMail.exe 1.01

IPCalc.exe 1.3.3

Oldest client version

tested with server 5.80

Clients 5.15 and earlier may fail on connect.

New Features / Bugs Fixed

(see MOMI HISTORY.RTF for previous versions)

Common new features (requires current client and server)

If you are using Client Access, newly added screens in a MOMI release update are not available to users by default. This action may be changed on the screen Configure / Client Access / Global Settings by checking the option New screens enabled by default. The user that started MOMI, known as the Default Security User, always has new screens enabled by default.

Installer

· The installer now references Readme.PDF instead of Readme.RTF. This reflects the removal of Wordpad, previously the default RTF file viewer, in recent versions of Windows 11. Shortcuts created for MOMI ReadMe and History in Windows Start also now reference PDF files. Microsoft Edge, the O/S browser, had a built-in ability to display PDF files.

Help

· None

Installation Files

· None

MOMI Client

New Screens:

· None

New Features:

· Some Grids now have a setting in the Tools popup that allows the user to set the default sort column.

· Grids that contain an ‘X' checkbox to select the row now have new checkboxes that resize with the grid. Previously on a full screen client on a 4k monitor the checkbox was too small to see.

· Grids that contain a precent progress bar now will resize with the grid. Previously on a full screen client on a 4k monitor the nn% was too small to see.

· CPUs / Detail Chart L/H

- Detail Chart now has the ability to view the detail info from the various History databases as well as the live data.

· Overview

- Overview now allows EMS messages to display if the client is in Mini-MOMI mode. The main EMS Logs screen is still not available in Mini-MOMI. (For Vikas K.)

- When the mouse is over the top/left 1/3 of the "BlackWood" or "Alarms" of the client and if allowed by Configure/Client/Single Screen/Alarms "Allow display of Logo/Alarm Popup" and User is allowed to view Active alarms and Popup screen will display of all monitored systems. This popup will remain up until the mouse leaves the "BlackWood" or "Alarms".

· Files / File View

SubSystems / Spooler / View Job

- added ability to print only selected lines when using the export 'Print to PC Printer'.

SubSystems / Expand /Lines / Detail

SubSystems / Expand /Lines / Info

- Added Query Packet Size values.

· Alarms / Define / Actions

- The Alarm Display text can now be customized similar to the EMS Message and the Email.

- When creating screenprints for email to BlackWood now screenprints include all EMS and Email set and clear screens.

· Alarms / List / Alarms

- Alarms can be temporarily turned off.

- Added 'Delete Alarm' to right-click action menu.

· Configure / Client / General / Logon & Connections

- added check to cause jump to Overview screen when a Logon is successful

- added check to cause jump to Overview screen when a system change is successful.

Bug Fixes:

· When a user logged on all alarm info was discarded and re-requested causing a delay in the display of Alarms. Fixed.

· When the client was on one of the alarm screens and the connection to the server failed, when the client reconnected, it would not reload the alarm info until the user clicked on an alarm tab. Fixed.

· Files / File Explorer / NSK

Files / Enscribe / Files

Files / File Entity

Processes / Process Detail

- When switching to get File Detail, if the File was an ANSI name it would not correctly get the Partition, Alternate Keys and Alternate Key Files data. Fixed.

· Files / Enscribe / SubVols

- If a request for a subvol that did not exist was sent to a server version that was prior to 6.18d the client would crash. Fixed.

- If a volume was an SSD drive they were mistakenly colored as Virtual disks. Fixed.

· SubSystems / Logs / EMS Log

- If invalid Distributor Filter name or Template Name was used no records were returned but the error did not display. Fixed.

· SubSystems / Logs / VHS Log

- If the first request was for 'CURRENT ACTIVE VHS LOG' and sent by moving the scroll speed and direction indicator instead of using the Request button the request would fail with the error 'File System Error(13) The Filename was not specified in the proper form [CURRENT ACTIVE VHS LOG]' Fixed.

· SubSystems / Logs / EMS EventBX

- Vertical scrollbar did not show when needed. (broken in version 6.18) Fixed.

· SubSystems / LogViewer

- Save buttons were not always enabled when they should be. Fixed.

· SubSystems / Expand / $NCP

SubSystems / Expand / $ZEXP

- Screens would only load when the screen was requested the first time, so when the system changed the data for the new system was not loaded. Fixed.

· History / Chart

- The starting point of the Initial chart was incorrect on Windows 11 PCs. Fixed.

· Alarm / Active

- When attempting to temporarily turn off an alarm the popup would disappear when and update to the screen arrived. Fixed.

· Alarm / Define / Alarm

- The ability to display and set the Interval times for a TCP/IP Ping was not visible. Fixed.

Misc. Items:

· SubSystems / Logs / EMS Log

- Config Request for "Lightning Mode" is now bigger.

· Alarms / Active

- When the alarm active screen is displayed for the first time it now loads much faster.

· Configure / Client / General / Fonts

- For ‘Character Display’ only the character sets installed on the PC will be enabled on 'Available Additional Character Set’.

Known issues:

· Systems / File Transfer / SFTP

- If file is transferred as a Key-Sequenced structured file sometimes SFTP will think the transfer is successful but the host file is left empty. A check is now done and an error shows if this happened. Note: Sometimes making the REC LEN even will succeed. Some failures are caused by unknown factors and seem to be a failure in the SFTP Server on the NonStop.

· SubSystems / Discovery

- Feature is still under development and subject to change.

Comments and suggestions are invited and welcome.

MOMI Server

New Features:

· None

Bug Fixes:

· Corrected validation issues that caused the following alarms to report as purple alarms in the client. 6.18d had introduced more in depth entity validation within alarms that triggered this problem:

TMF / Subsystem down

System / Busy percent

Expand / Line quality

Expand / Line state up/down

Expand / Path state up/down

Expand / Link-Time

Misc. Items:

· None

Known Issues:

· None

MOMIFTP

· 2.16 - Fixed bug that a very large file would fail on transfer.

ssMOMI

· None

MomiEmail

· None

SendMail

· None

CentralServer

· None

IPCalc

· None

Client Installation Notes

Installation of the PC client may be perform as the current user (i.e. non-administrator level) or as an Administrator for all users of the PC. Security of some corporate environments may prevent a current user installation. Administrator level setup usually requires that you right-click on the installer file and select Run as administrator to gain Admin rights, which could be considered a level above Administrator.

Setup also provides the option to copy MOMI files to a shared network location and copy files to the NonStop System (via FTP or sFTP).

mini-MOMI

MOMI operates in a reduced functionality or mini-MOMI mode when the MOMI server is started without a password (a time limited trial password or a purchased password are placed in the CONFMOMI file on the NonStop System).

Mini-MOMI is available a period of 2-years from the version date of the NonStop server portion of the program. The expiration date is displayed on the PC Client screen Configure / Diagnostics.

Shops running mini-MOMI are encouraged to check our web site from time-to-time for new versions or updates.

While it is our intention to provide mini-MOMI in future versions, BlackWood reserves the right to alter, limit or discontinue mini-MOMI in subsequent releases.

Multiple Platform Server Support

MOMI configuration files support S-Series, NonStop Integrity, NonStop Blades and Integrity NonStop X.

On the NonStop system, in the subvolume where MOMI is installed, the following object files are present by default:

BWMOMI - 32-bit TNS/R native (S-Series)

BWMOMIi - 32-bit TNS/E native (Integrity & Blades)

BWMOMIx - 32-bit TNS/X native (Intel X64 & Virtual NonStop)

The TACL obey files OBYCSQL, used to SQL/MP compile MOMI objects, and OBYMOMI, used to start the MOMI subsystem, automatically select the correct object file.

If automatic platform selection logic does not function, the error Illegal program file format is encountered, simply change the obey files to reference to the correct BWMOMI? object.

First Installation

Update an Existing Installation

The procedures for installing MOMI the first time or updating an existing installation are virtually the same.

In prior releases, MOMI installation software was packaged as an EXE or ZIP. The MSI format performs all of the same features, plus allows the client to be installed under the current user which normally does not require administrator access.

The MOMI PC Client installs by default into its own version specific subdirectory and is accessed from the Windows Start menu under BWS MOMI n.nn (where n.nn is the version number).

It is recommended that a new version of the MOMI server software or an update to an existing version is installed into the same subvolume on the NonStop System. By default, existing startup and configuration information is not changed. Existing files are renamed as necessary to allow for installation while the MOMI server is running and to provide for fallback.

The installation process starts by obtaining MOMI software from either our website or perhaps a flash drive handed out a conference (we can also send you the software on a flash drive on request). MOMI installation software is a standard Windows MSI file and can either perform a new install or update an existing installation. The installation program also contains utilities for transferring MOMI server software to the NonStop System (MomiFTP) and for placing MOMI software on a shared drive location (CentralServer).

The following steps describe installing MOMI software on the local PC and on the NonStop System:

1) Obtain MOMI software and double click on the MSI file. The initial screen provides allows display of the ReadMe and detailed installer Help.

2) Click though the Welcome screen. Please read and accept the License Agreement. Click through to continue.

3) The Utilities screen allows the option to run MOMIFTP and CentralServer (can be run now or later). Click Install Client > to continue.

4) The next screen selects the Setup Type. The default is Complete. Click through to continue.

5) The Ready to Install the Program screen allows MOMI software on this PC to be installed Only for me (<user>) or Anyone who uses this computer (all users). Choose the desired option. Note the Anyone... selection prompts for an administrator logon if needed. After the installation completes, click Finish.

6) Press the Windows Start button and under BWS MOMI n.nn (where n.nn is the version just installed) select MomiFTP.

a. On the screen 1st Connect to HPE NonStop, select the Transport type (FTP or SFTP), fill in the Host Address (NonStop System IP address or DNS), User ID, Password and Initial $Vol.SubVol where the MOMI files are placed. The User ID specified owns the files after the transfer takes place. Press Connect to HPE NonStop. If the connection was successful, you will see a big green Connected...

b. Press Next >> to advance the screen.

c. On the screen 2nd Select Vol.SubVol on HPE NonStop a list of the files present (if any) in the selected location is displayed. For a new installation, you should choose an empty subvolume. Change the location as needed Change to update the display.

d. Press Next >> to advance the screen.

e. On the screen 3rd Select New Install or Update press Put Files on HPE NonStop to start the transfer. The status boxes indicate the outcome of the transfer.

f. Press the Exit button to disconnect and stop the program.

7) From a TACL prompt, logon with the User ID and password that $MOMI will operate under. Volume to the location where the MOMI files were placed.

8) Edit the file OBYMOMI. This is a TACL obey file used to start MOMI and provide initial configuration information. Page down to the section "vvv set values below here vvv". This marked portion of the obey file is used to change the initial startup values for the $MOMI server portion.

Check the process name, CPU $MOMI operates in, priority and home terminal. Default values are usually valid for most systems.

9) Edit the file CONFMOMI. This edit file is used to set various MOMI attributes using keywords. Set the System-Description and check TCPIP-LISTEN which defines the TCP/IP process name, optionally the address and port that MOMI will listen on for PC Client connections.

· mini-MOMI users, the above should be about the only item of concern.

· MOMI users, add your MOMI password. Also, define any history files desired. MOMI automatically creates the history files.

10) SQL/MP compile MOMI (if you don't use SQL, ignore this step):

from a TACL prompt: OBEY OBYCSQL

11) Create / update BWSSG (the Super Group helper process) (see Security / General considerations to determine if you need this step):

(BWSSG is a PROGID'ed copy of the MOMI server. The following steps show you how to rename out any existing BWSSG, keeping a backup copy, create a new file - details such as required logon security to perform these operations is not covered).

Purge BWSSG2

Rename BWSSG1, BWSSG2

Rename BWSSG, BWSSG1

FUP DUP BWMOMIx, BWSSG, sourcedate (BWMOMIi TNS/E)

FUP Give BWSSG, <Super.Group>

FUP secure BWSSG, NGNG, PROGID

If used, BWSSG must be updated with BWMOMI. The FUP DUP option of SOURCEDATE or SAVEALL must be used.

12) Start MOMI:

From a TACL prompt: OBEY OBYMOMI

(wait at least 1 minute before proceeding to the next step)

13) On your PC, press the Windows Start button and under BWS MOMI n.nn (where n.nn is the version just installed) select MOMI. The first time a Client is started on a PC, it will prompt for the TCP/IP address and port of the NonStop System (the port is defined in the CONFMOMI file and has a default of 2010).

MOMI starts on the NonStop System a measurement (DCPUS file) configured with a variety of entities (CPU, Process, TMF, etc...). This measurement does not specify an interval but is effectively used for LISTACTIVE purposes.

Screen Saver

Some users have requested the ability to run the ssMOMI screen saver as a standalone program that does not stop when the screen is clicked, or the keyboard is pressed.

To run ssMOMI as a standalone program:

1) Copy the MOMI screen saver ssMOMI.scr giving it the name ssMOMI.exe.

2) Start the program as follows:

ssMOMI.EXE /c AsEXE

3) A pop-up window displays. Select the location of your MOMI.INI file. By default this is located at:

C:\Documents and Settings\<user>\Application Data\BlackWood Systems\MOMI

4) After pressing OK, the screen saver appears. Press X to close.

5) Create a Shortcut with the Target as follows:

ssMOMI.EXE AsEXE

(path details to the EXE omitted)

The run-time param /c directs the program to display a pop-up window to configure the location of the MOMI.INI. AsEXE directs the program to continue executing after keys are pressed (i.e. don’t function as a screen-saver).

Manual Installation of Nonstop Based Programs

If the MOMIFTP utility cannot be used to transfer files from the PC to the NonStop server, these instructions describe how an alternate file transfer program would be used. The MOMIFTP utility does not perform any special actions, but simply renames files (if existing are present) and transfers MOMI files from the PC to the NonStop System using FTP or SFTP.

The first step is to locate the source files -

PC install all users:

C:\Program Files (x86)\BlackWood Systems\BWS MOMI_n.nn\Tandem Install\NonStop\

PC install user only:

C:\Users\<User ID>\AppData\Local\Programs\BlackWood Systems\BWS MOMI n.nn

Via shared server (varies based on how shared server is organized):

\Tandem Install\NonStop\

(where n.nn is the release package number)

If MOMI is not installed, download and execute the MSI file. Select Launch CentralServer and place the files in an empty subdirectory. In the destination subdirectory under \Tandem Install\NonStop are the subdirectories \ascii and \Binary. The grouping indicates the needed file transfer mode (i.e. ASCII or Binary).

Using a file transfer utility, copy files from the PC to the NonStop (all to the same destination subvolume) -

Binary

BWMOMI

BWMOMIi

BWMOMIx

EMSEXPO

ASCII

FUPEVTCX

OBYMOMI

CONFMOMI

OBYCSQL

OBYALTER

Logon to the NonStop System, volume to the location where the files were placed and OBEY the TACL obey file OBYALTER to alter the file codes (or manually perform the steps below):

a) FUP alter BWMOMI , code 700

b) FUP alter BWMOMIi, code 800

c) FUP alter BWMOMIx, code 500

d) FUP alter EMSEXPO, code 845

At this point the files are transferred. Continue the instructions in the section First Installation / Update an existing installation after the step using MOMIFTP.

Future Plans (may or may not be in future releases)

1) CMON

2) More history chart-able entities

3) New functionality as requested by our users

4) Additional Tools and References as we think of them

5) Pathway information

We welcome comments, suggestions, and bug reports. Please send them to:

support@blackwood-systems.com

*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*

Directory Layouts

Below is the general layout for MOMI Software as seen after user Central Server or on a Flash Drive plus the general purpose for each file:

Documents	Directory or file
License rtf/txt	MOMI disclaimer/license
MOMI History rtf/pdf/html	Change history
Readme rtf/pdf/html	This file (<<<---START HERE)

Extras	Directory of Optional Programs
IPCalc	directory of IP Calculator
MomiEMail	directory of MOMI Email support
ssMOMI.SCR	MOMI Screen saver

Help	Directory of Help files
HTML5	directory in HTLM5
Microsoft_HTML_Help	directory in CHM
MS Word	directory in Microsoft Word
PDF	directory in Adobe PDF

Misc_Sounds	Directory of Miscellaneous Sounds

ShortCuts	Directory of MOMI shortcuts (after Central Server)

Sounds	Directory of MOMI sound files

Tandem Install	Directory for Setting up NonStop
NonStop	directory of NonStop software
ASCII	directory of Ascii files
CONFMOMI	Initial configuration file
FUPEVTCX	FUP obey file to create EVENTCX file
OBYALTER	TACL obey file to alter file codes
OBYCSQL	TACL obey file to SQL compile MOMI
OBYMOMI	Startup obey file
Binary	directory of Binary files
BWMOMI	MOMI Server (TNS/R native code 700)
BWMOMIi	MOMI Server (TNS/E native code 800)
BWMOMIx	MOMI Server (TNS/X native code 500)
EMSEXPO	Compiled EMS filter (code 845)

MomiFTP.EXE	FTP transfer MOMI files to NonStop System
TanFiles	MomiFTP.EXE config database

Calendar.new	MOMI calendar database (initial and updates)
CentralServer.exe	Program copies Client files to central PC
ErrorCodes.mom	MOMI system supplied error database
MOMI.EXE	MOMI client
TimeZone.mom	MOMI time zone database