Readme.rtf       Date 2016/10/21

BlackWood Systems, Inc.
15982 N 78th Street - Suite B
Scottsdale, AZ  85260

phone: 602-569-8766
fax:   480-905-8778
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 agree to the License.txt file 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. 3.xx, 4.xx and 5.xx). When a release series changes, both the client and server must both be upgrade at the same time.

Please note: due to enhancements and bug fixes the oldest MOMI Client that will operate correctly with this server is 5.30. While clients prior to 5.30 should connect and generally work, they may encounter disconnects or error messages.

Special Notes

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 a pop up window when the mouse is placed over the connector lines between systems on the screen SubSystems / Expand / Diagram.

The CAIL Emulator is provided courtesy of CAIL and is not a component of any purchased MOMI product. The Emulator is a limited-function version of the CAIL CTT/Suite product. BlackWood Systems and CAIL reserves the right to discontinue, limit or alter the availability in future releases. Please see the CAIL Emulator help within the Emulator for additional information. To obtain a full featured emulator, please contact CAIL. If a full PC based version of the CAIL emulator is already installed, the full version is used instead of the limited version.

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								5.81
   Release Date (yyyy/mm/dd) 	2016/10/21

				Item												Version
				----												-------
				Latest O/S tested				G06.32.01 - H06.29.00
J06.20.00 - L06.05.00 (L16.05.00)
	
				Client Version						5.81
				Server Version (VPROC)	5.50   T0000G06___V5_50____2016_09_13
      
				Buffer Version						Client 21.48   Server 21.48
				History database					3.00
				CONFMOMI										3.09
				OBYMOMI										5.02
				OBYCSQL										5.02
				MomiFTP.exe								2.06
				ssMOMI.scr								4.14
				MomiEMail.exe							1.10
				SendMail.exe							1.01
				IPCalc.exe								1.3.3

				Minimum server version
				to provide main line
				client functions					5.33

				Oldest client version
				tested with server				5.33

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.  

Impacts in this version
None

MOMI Client
	New Screens: 	
·	None

	New Features:
•	If 'Disable all Action Confirmations' is not checked, before any file is saved on the PC it is now checked to see if that filename already exists.  If it does the user is allowed to       overwrite, change name or not save the file. (for Gary B.)
•	CPUs / CPU Info
•	- Added right-click menu on columns for 'Elapsed Time since Load' and 'Time CPU last loaded' to jump to EMS logs with time set at Load Time.  User can then watch what happened at coldload           or back up as long as needed to check what happened before Cold load.
•	Alarms / Define / Alarm 
•	- For type 'EMS', subtype 'User defined' added to 'Limit by Type' the ability to make a line a comment so it will not be used in setting the alarm.  Also added display of selected line and            if selecting a limit already set the limit will be removed. (for Vikas K.)
•	
•		Bug Fixes:
•	Systems / File Transfer
•	- Under some rare circumstances the Drag and drop would pick the wrong file to transfer.  Fixed.
•	- If a non-ascii file was PC->NSK transfered as a ascii file and the non-ascii file contained tab characters the client would crash.  Fixed.
•	Systems / Probe
•	- Current system was not being checked for alarms unless it was checked in the 'Select Systems'. Now if current system is being displayed it will also be checked for alarms.  Fixed.
•	SubSystems / Logs / EMS Log
•	- Process locator ('$'-button) 'Add Name' was mistakenly enabled.  Fixed.
•	Alarms / Active
•	- The right-click actions to temporarily turn on/off and alarm and to delete an EMS alarm were not working and returned an 'Item not found' error.  This bug was introduced in the 5.80 version of the client.  Fixed.
•	Configure / Client Access / Global Settings' and         
•	Configure / Client Access / User Define / Systems
•	- Enabling/disabling the FTP/SFTP/MFTP checkboxes when the overall File Transfer was checked/unchecked was inconsistant and confusing.  Fixed.
•	
•	Misc. Items:
•	Diagnostic and Config info file now contains file versions of MOMI installed programs.
•	Made some changes to Autoupdate for the screens that allow setting and clearing autoupdate.
•	- if the screen normally is in autoupdate mode the checkbox was moved to its config popup.
•	- if the screen is not normally in autoupdate mode it is displaying on the screen.
•	- if autoupdate is unchecked during a collection no more records will display so the screen will not update with new records and replace any on screen
•	- Checking the autoupdate will no longer cause the request to be sent, you must then press the request button.
•	·      Files / DiskFile
•	- Prevented Physical Reads and Writes from displaying a negative number if the Measure returned values are incorrect.
•	·      Configure / Diagnostics / Client
•	- Now displays when connection to a system occurs and when a communication error occurs.
•	·      Configure / Reference / BlackWood Systems
•	- Removed button to jump to BlackWood Forum.
•	
•		Known issues:
•	·	The Systems / File Transfer MFTP cannot transfer PC->NSK to a structured files format.
•	·	The SubSystems / Discovery screen is still under development and subject to change.  Comments are welcome!
•	
•	
•	MOMI Server
•		New Features:
•	·	Data retrieval from MEASURE is now more efficient by using MEAS_READACTIVE_MANY_ where possible.
•	
•	The default volume/subvolume and initial OSS directory are now made available to the client.
•	
•	·	Expand line “not ready” error code is now displayed on an active alarm. 
•	
•	New alarms:
•	Expand / Line quality
•	DiskFile / Broken or Corrupt
•	
•	·	Server now provides a ‘bulk access’ capability for the MEASURE entity File and is accessible on the screen Subsystems / Discovery.  This capability prevents the internal need to start and stop measurements for MEASURE data.  Note that at this time MEASURE does not report an entity accessed in this manner as residing on a remote node (in other words the node name is not returned).
•	
•	·	Support added binary reading/writing of Guardian files. Used in MOMI file transfers. 
•	
•	·	$RECEIVE queue length now reported as a decimal value, instead of a whole number, on newer platforms where available in MOMI.
•	
•	·	Support for the new screen Expand / System Entity (newer platforms only).
•	
•	·	MOMI history Process now reports the fields (some fields not reported except on latest O/S releases):
•	
•	Ready-time
•	Launches
•	Recv-Qtime
•	TLEs
•	Begin-Trans
•	Abort-Trans
•	
•	·	The MEASURE entity Disk Open now reports a 32-bit OCB number on the latest O/S releases.
•	
•		
•	Bug Fixes:
•	The server no longer returns the message "Expected initial message from client" when the CONFMOMI keyword CLIENT-INITIAL-MSG was set to true.	
•	
•	The alarm DiskFile / File existence (and others) with an OSS path name would not function correctly with a length greater than 47 characters. The internal limit was raised to 200 characters.
•	
•	The default file extents for CNF01DB and LOG01DB were increased.
•	
•	A small memory leak was corrected in the reading of MOMI history.
•	
•	·	Expand alarms are now removed when a line is removed.
•	
•	The computation and display of $RECEIVE Queue Time is now correct on the Overview screen and changed to 2 decimal positions from 3.
•	
•	The listing of locks now displays the logical filename instead of the internal “funny” name if the file is on a virtual disk.
•	
•	Corrected the computation of Ready Time Only as seen on the screen Processes / Process Detail.
•	
•	·	Server no longer reports "MEASURE is DOWN" under J06.20.  Same issue would    also be corrected under L16.05 (system with this release is not yet available).
•	
•	·	Changes were made to PING processing to support prevent premature terminations of Trace Route in the client (client also needed changes as well).
•	
•	·	TCP/IP screens no longer cause a high CPU utilization if another status request is in progress. Internally, SPI was returning an error ZCOM^ERR^CMD^IN^PRGRSS (-40) which was considered retry-able by MOMI. Effectively, the NonStop TCP/IP subsystem will only handle one command at a time so now the ‘duplicate’ command will terminate.
•	
•	Certain server generated error messages displayed by the client will now properly display a # sign in the file name instead of a number.
•	
•	The screen SQL/MP / Catalog no longer returns an error -8421 on TNS/X Systems.
•	
•		Misc. Items:
•	The initial memory allocation of certain MOMI processes was increased to help prevent additional memory allocations and fragmentation.
•	
•	·	The MEASURE entity FILE is now added to the initial and persistent measurement started by MOMI. The MOMI screen Overview / CPU Info / Free CIDs should be checked to insure sufficient MEASURE resources are available.
•	
•	·	All MEASURE counter access now uses the ZMS format.
•	
•	The internal format for the date in an SMTP message (i.e. email) was altered to prevent it from displaying as 12/31/1969 on devices running Android 6.
•	
•	·	Processes with DDL’s of a zero length no longer cause an error 13 with ProcessH measurements.
•	
•	·	Legacy code from K series was removed. MOMI executable will now only operate on S-Series or later systems.
•	
•	·	Changes in computations in the MOMI CPU collectors should result in more values displaying as whole numbers, such as 2.00 instead of 1.99.
•	
•	·	The TCP/IP address is now displayed, if available, with the error message "Error on listen socket".  The idea is to display the address that caused the error.
•	
•	The screens Subsystems / TCP/IP now display additional error information if the open to $ZNET fails.
•	
•	·	Additional messages are logged with MEASURE error codes in the event measurements cannot be started.
•	
•	·	System types in Expand now report NS-X for type 11 CPUs.
•	
•	·	TNS/X systems could temporarily report very high CPU utilization in MOMI.  This was due to code executing so quickly that a MOMI ‘time period’ could complete before the start of the next period. Logic was revised to help prevent this except in the case of a change of the system time.
•	
•	
•	Known issues:
•	·	History files HST02DB, HST03DB and HST04DB have a limit of approximately 600,000 processes per time period. If this limit reached the history consolidator server will log a message and discontinue the consolidation for the affected file (others preceding are not affected). Typically this limit would only affect the HST04DB which has a default time period of 1 day and only on a large system with a great deal of transient processes throughout the day.  
•	
•	MOMIFTP 
•	None

ssMOMI 
·	None	

MomiEmail 
·	None	

SendMail 
·	None	

IPCalc 
·	None

CLIENT INSTALLATION NOTES

Installation of the PC client via setup normally requires logon as an administrator. 

If Administrator is not available, some other options that might work:

A.	install to a subdirectory other than C:\Program Files or perhaps to a shared directory.

B.	Choose Custom install and uncheck installation of the screen saver. This will prevent access to the \Windows subdirectory.

mini-MOMI

MOMI provides the ability to operate in a reduced functionality or "lite" mode.  This mode is automatic whenever MOMI is started without a password.  To install mini-MOMI, follow the installation instructions but omit a password in the CONFMOMI file.

Mini-MOMI will operate for 1-year from the version date of the NonStop server portion of the program.  The time remaining is displayed on the PC Client configuration screen.

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

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:

   BWMOMI  - 32-bit TNS/R native (S-Series)
   BWMOMIi - 32-bit TNS/E native (Integrity & Blades)
   BWMOMIx - 32-bit TNS/X native (Intel X64)

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

In the event that the automatic platform selection logic does not function, simply change in the obey files the reference to the object BWMOMI? as needed.

FIRST INSTALLATION
UPDATE AN EXISTING INSTALLATION

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 NonStop via FTP.

Installing MOMI software to the local PC usually requires Administrator access under Windows. Other functions such as copying software to the NonStop or to a shared server location may require other levels of security access.

1)	If you need MOMI software, download the latest version of MOMI from our web site.

2a) If you downloaded an EXE file:

a. double click on the downloaded file

2b) If you downloaded a ZIP file:

a. expand the ZIP file to an empty subdirectory on your PC

     b. double click on the file Launcher.exe

2c) If you have a MOMI CD:

a. double click on the file Launcher.exe

3)	Once the installation process starts your given the options to a) Install the MOMI Client, b) Install the MOMI Server files on NonStop Server, c) Copy MOMI client files to common server location, or d) View ReadMe file for MOMI. Select Install MOMI Client. Click though 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 NonStop.

On the 1st Connect to NonStop page, fill in the Host Address (your NonStop IP address), User ID, password and initial Volume/Subvolume where the MOMI files are placed.  The User ID specified owns the files once the transfer takes place.  Press Connect. If the connection was successful, you will see a big green "Connected..." .

Press Next to advance the screen.

On the 2nd Select Vol/SubVol on NonStop screen shows a list of the files present in the selected location. Change the location if desired and press Change.

Press Next to advance the screen.

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

Press the Exit button to disconnect and stop the program.

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 initial startup values for MOMI.

Check the process names, CPU $MOMI operates in, priority and home terminal.   The default values are good for most systems.

12)	Edit the file CONFMOMI.  This edit file is used to set various MOMI parameters after start up.  Set the System-description and check the TCP/IP process name and port that MOMI will 'listen' on for PC client connections.

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

For licensed MOMI users, add your MOMI password.  Also, define any history files desired.  MOMI will automatically create the history files in the location specified.

13)	SQL/MP compile MOMI (If you don't have SQL/MP, ignore this step):

From a TACL prompt: OBEY OBYCSQL

14) Create a Super Group helper program (the steps below omit logon to the super.* ID):

Purge BWSSG2

Rename BWSSG1, BWSSG2

Rename BWSSG, BWSSG1

FUP DUP BWMOMI, BWSSG, sourcedate			(BWMOMIi or BWMOMIx)

FUP GIVE BWSSG, <super.group>					 

FUP SECURE BWSSG, NGNG, PROGID

(The FUP DUP option of SOURCEDATE or SAVEALL must be used)

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/ALL Programs/BlackWood Systems/MOMI_n.nn/MOMI).  The MOMI client will detect an initial start on the PC and will prompt for the TCP/IP address of the NonStop and port.  The port is defined in the CONFMOMI file and has a default of 2010.

Note that these instructions may reoccur in other portions of this document or provide optional installation methods.

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 provide a manual alternative.

1)	FTP (or IXF) files from the \NonStop subdirectory to the NonStop server. The \NonStop subdirectory is either from the expanded ZIP or the subdirectory where the MOMI client is installed on your PC if you chose the FULL or Custom option.

Note the binary/ASCII requirements.

a)	binary BWMOMI
b)	binary BWMOMIi
c)	binary BWMOMIx
d)	binary EMSEXPO
e)	ASCII  FUPEVTCX
f)	ASCII  OBYMOMI
g)	ASCII  CONFMOMI
h)	ASCII  OBYCSQL
i)	ASCII  OBYALTER

2)	Logon to the NonStop server and volume to the location where the files were placed.  Use 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

3)	Edit the file OBYMOMI. Check the process name, CPU, priority and home terminal.

4)	Edit the file CONFMOMI.  Check the TCP/IP process and port that MOMI will listen on for PC client connections.

Mini-MOMI users do not need to change other items.

Licensed MOMI users need to add their MOMI password.  Additionally, define any history files and check other settings in the file.  Note that MOMI will automatically create the history files in the location specified.

5)	SQL compile MOMI:

OBEY OBYCSQL

6)	Start MOMI:

OBEY OBYMOMI

FUTURE PLANS (may or may not be in future releases)

		1) Disk History (on Integrity and later systems)
		2) CMON   
		3) Pathway information
		4) More history chart-able entities
		5) New functionality as requested by our users
		6) Additional Tools and References as we think of them

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

support@blackwood-systems.com

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

The MOMI CD or EXE files follow the same general layout.  

The following is the general file layout and purpose for each file:

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

Extras             		= Directory of Optional Programs
ssMOMI.SCR          =  MOMI Screen saver
   
Help               		=	Directory of Help files
		Microsoft_HTML_Help =		Directory of CHM style help			
		WebHelp	         		=		Directory of Web style help
		HTML5									=		Directory of HTLM5 style help
		MOMI help.txt					=		Description of help types
		MOMI_User.doc					=		Help in Word format
		MOMI_user.pdf					=		Help in Adobe PDF format

	NonStop 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 MOMI files to NonStop System
			TanFiles							=			MomiFTP.EXE config database

   PC Manual Install 		=	Directory for Manual Install
			CAIL									=		Directory containing CAIL Emulator
			Documents						=		Directory of documents
			Extras								=		Directory of optional programs
			Help									=		Directory of Help formats
			Misc_Sounds					=		Directory of misc. sound files
			Sounds								=		Directory of MOMI sound files
			Tandem Install			=		Directory for Setting up NonStop
			Calendar.new				=		MOMI calendar database
			ErrorCodes.mom			=		MOMI system supplied error database
     MOMI.EXE							=		MOMI client
   		Readme.rtf					=		Readme instructions (<<<---START HERE)
     TimeZone.mom				=		MOMI time zone database

		Launcher.exe					= Program allowing user to select install options
		CentralServer.exe		= Program that copies Client files to central PC Server
		Readme.rtf						=	This file
		MOMI_Client.exe			= MOMI Client Installation program