Readme.rtf       Date 2022/11/06

BlackWood Systems, Inc.

phone: 602-569-8766
email: support@blackwood-systems.com
web:   www.blackwood-systems.com

This file contains the latest version and upgrade information. This file is the first place to look for initial installation and upgrade information.

Please thoroughly read and accept the License Agreement as displayed in the installer before using this software.

For an initial install, further in this document the section entitled FIRST INSTALLATION describes the installation process from start to finish.

Sections in this document

Compatibility between client and server
Special Notes
CURRENT VERSIONS
NEW FEATURES / BUGS FIXED
CLIENT INSTALLATION NOTES
mini-MOMI
MULTIPLE PLATFORM SERVER SUPPORT
FIRST INSTALLATION
UPDATE AN EXISTING INSTALLATION
RUNNING SSMOMI SCREEN SAVER AS A STAND ALONE PROGRAM
MANUAL INSTALLATION OF NONSTOP BASED PROGRAMS
FUTURE PLANS
Directory layout

Compatibility between client and server

The ability of our customers to upgrade as painlessly as possible to a new MOMI release is important to us.

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.

CURRENT VERSIONS
   
Release Package            6.16
Release Date (yyyy/mm/dd)  2022/11/06

Item	Version
----	-------
Latest O/S tested	G06.32.01  
		J06.23.00 – L22.09.00
	
Client Version	6.16   Build 903
Server Version (VPROC)	6.16   T0000G06___V6_16____2022_11_02
      
Buffer Version	Client 21.68   Server 21.68
History database	3.10
CONFMOMI	6.01
OBYMOMI	6.00
OBYCSQL	5.02
MomiFTP.exe	2.15
CentralServer.exe	1.7
ssMOMI.scr	6.00
MomiEMail.exe	1.10
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
•	An uninstall no longer leaves behind short-cuts or files when two or more versions were present. 

MOMI Client
New Screens: 	
•	None

New Features:
•	Files / Enscribe / Volumes
      - Added 'Mini-Report' to show space usage for Volumes. (for Jeff N.)

•	 SubSystems / Logs / EMS Log
- If a filter is active during a Lightning-mode retrieval the screen will also display how many of the records passed the filter. (For Gary B.)
- If a client filter is active the selection will display a light purple to differentiate it from a client filter that has been selected but not yet activated by the 'Filter' or 'PreFilter' button.

•	Alarms / Define / Alarm  and
Alarms / List   / Alarm  and
Alarms / List   / Export and
Alarms / List   / Import   
- Added support for new alarm type event for number of Events Over Time (FCT=Flag/Count/Time). Currently only used on EMS message alarms. (for Eric S.)

•	 Configure / Client / Actions / MOMI.INI actions
- Added section to allow user to edit the MOMI.INI file (using NOTEPAD) then restart the client using the newly changed file.

Bug Fixes:
•	If the MOMI.INI did not exist and it was created, the default value for number of EMS Messages kept in memory was 100 not the correct default value of 5000.  Fixed.

•	If the client had the "Auto check for new versions" turned on at the same time the ReadMe.RTF was open using Microsoft Word, when the auto check was performed the client would crash. Fixed.

•	Under some circumstances when text was retrieved from the Clipboard and the Clipboard was opened exclusive by either the client or another process the Client would crash. Fixed.

•	Using the MOMI_INIT.INI to create the initial INI file would not always correctly create the MOMI.INI file. Fixed.

•	Files / Enscribe / View File and
   SubSystems / Spooler / View Job
- When a 'Search' or 'Export' was being performed and a 'Request' or 'Clear' was pressed the client could crash.  Fixed.

•	SubSystems / Logs / EMS Log
- If the 'Lightning' button was pressed during a normal record retrieval the Lightning retrieval would start over at the original data/time rather than just continue from where it was.
  Bug was introduced in 6.14.  Fixed.
- The Export filters button never became active so it was impossible to export EMS Filters. Fixed.
- Lightning Filtered count was not reset when filter was cleared or changed. Fixed.

•	SubSystems / Spooler / Collector
- Under some circumstances when a Spooler Collector was deleted the client would crash. Fixed.

•	SubSystems / Spooler / Jobs and
   SubSystems / Spooler / View Job
- A jump directly from Spooler Jobs to Spooler View Job when the Spooler View Job screen had not yet been created would sometimes cause the client to crash. Fixed.

•	SubSystems / Logs / EMS Log
- If the 'Lightning' button was pressed during a normal record retrieval the Lightning retrieval would start over at the original data/time rather than just continue from where it was. Bug was introduced in 6.14.  Fixed.
- The Export filters button never became active so it was impossible to export EMS Filters. Fixed.
- Lightning Filtered count was not reset when filter was cleared or changed. Fixed.

•	SubSystems / Spooler / Jobs and
   SubSystems / Spooler / View Job and
   SubSystems / Logs / EMS EventBX and
   Files / Enscribe / View File
- A 'Search' would not work correctly if both Wildcards and case-sensitive were selected. Fixed.

•	SubSystems / Spooler / Jobs
 - If using right-click to get to Process Detail screen it sometimes would bring up the previous process name.  Fixed.

•	SubSystems / Expand / Diagram
- Sometimes when multiple systems were being probed the display would not display all paths and lines. Fixed.

•	 History / Export
- The runtime string created using "Create Runtime Export" would not work if ran from a command line, it only worked with the Test button.  Fixed.

•	 Alarms / Define / Alarm
- It was possible to display, save, change and/or delete an Alarm with the name <NONE>.  Fixed.

•	Alarms / List / Alarm and
Alarms / List / EMail and
Alarms / List / EMail Group and
Alarms / List / Group List
- When using an alternate Windows character set(Chinese-Taiwan-0404) the expanded '[+]' fields would display unwanted '?'. Fixed.

•	Configure / Client / Single Screen / Alarms
- When attempting to change the Alarm text color the client might crash.  Fixed.

Misc. Items:
•	Made improvements to make sure when the client is updating the MOMI.INI file it did not interfere with other clients accessing the file.

•	 Security Logon and
    File Transfer Logon
- When the Enter key is pressed while entering UserID or Password the Send Response button is now clicked instead of tabbing to the button. (for Adam W.)

•	CPUs / CPU Info
- Added column of CIDs used (derived from Configured - Free). (for Gary B.)

•	SubSystems / Logs / EMS Log
- When exiting Lightning-mode the message scroll speed will revert to the speed last set by the user not the default value. (for Gary B.)

•	SubSystems / Spooler / Jobs
- Copy Jobs now displays all available collectors sorted by how full they are.

•	SubSystems / TCP/IP / Process Status
- Added column for Opener process file name(NSK or OSS). (for Gary B.)
- Added 'View Process Detail' and 'Copy name to clipboeard' to right-click menu item for 'Process' and 'OpenerPName'

•	SubSystems / Expand / Diagram
- Reworked the diagram to speed up the loading of the diagram objects and make it flash less when it updates.

•	SubSystems / Expand / Paths / Detail and
SubSystems / Expand / Lines / Detail
- Added ability to scroll using mouse wheel.

•	Alarms / Define
- Disabled alarm entities now display the screen in Orange to improve read-ability when user has display set to High-Contrast theme.

•	Alarms / Define / Alarm / EMS Set and EMS Clear
        - If user tries to copy more data into the definition than allowed it will prevent it and beep to notify the user.
- Any blank lines are now removed before being saved.

•	Alarms / List / Import
- Import now has more complete counts for number of each item type deleted or imported.

•	Configure / Client / General
- Added new section 'Character Display'  this allows the user to globally set if Multibyte character sets (i.e. Chinese) are allowed for displays and set how the display of non-printable characters is handled if Multibyte are not allowed.
- Removed individual setting for Allowing Multibyte character sets for following screens EMS Logs, View File, View Spooler Job, Overview EMS display and User-defined screens.

•	Configure / Client / File Locations
- Removed HTML4 help.  Anyone that had selected HTML4 will auto-change to HTML5.

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:

•	Communication between the client and server no longer loops (showing high CPU utilization on NonStop System) when reading more than one than 1 shorthand history record. This situation arose when the client was exporting Disk Entity History data for the current day. The looping would stop if the requesting client was stopped.

•	Live history data no longer (possibly) delays by one period.

Misc. Items:

•	Server can now provide a letter after the version (for example 6.15g).

•	Minor coding cleanup and performance enhancements.

Known Issues:

•	None 

MOMIFTP 
•	version 2.15 Changed to work with new Installer and Added Stats(?) popup.

ssMOMI 
•	None

MomiEmail 
•	None

SendMail 
•	None

CentralServer
•	version 1.7 Added Help and Stats(?) popup.

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 install. 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 new MSI format performs all of the same features, plus allows the client to be installed under the current user which does not normally 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  BWMOMI, BWSSG, sourcedate (BWMOMIi TNS/E - BWMOMIx TNS/X)

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. 

RUNNING SSMOMI SCREEN SAVER AS A STAND ALONE PROGRAM

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

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

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: 

CAIL	               = No longer used

Documents							= Directory of documentation
 License.rtf /txt 		=		MOMI disclaimer/license
 MOMI History.rtf			=		Change history
 Readme.rtf       		=		This file	(<<<---START HERE)

Extras            		= Directory of Optional Programs
		IPCalc									=  Directory of IP Calculator	 
	MomiEMail							=  Directory of MOMI Email support (diagnostic) 
ssMOMI.SCR						=		MOMI Screen saver
   
	Help               		=	Directory of Help files
	 HTML5									=  Directory of HTLM5 style help
	 Microsoft_HTML_Help	=  Directory of CHM style help			
	 MS Word								=  Directory of Microsoft Word style help             
 PDF											=  Directory of Adobe PDF style help
 WebHelp								=  Directory of Web style help

	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
					G06.29-and-later	= 			optional use if G06.29 or later
						BWMOMI						= 				MOMI Server (TNS/R native code 700)
					Pre-H06.05				=				optional use on pre-H06.05
						BWMOMIi				 	=					MOMI Server (TNS/E native code 800)
					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 that copies Client files to central PC           
ErrorCodes.mom					= MOMI system supplied error database
MOMI.EXE									= MOMI client
TimeZone.mom						= MOMI time zone database