MOMI Readme.txt      Date 2007/03/29
   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 TANDEM 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.

The general rule we follow is that the servers within a release class, i.e.
 2.xx, 3.xx, 4.xx, etc...), support the last few releases of the client in the
 same class.  So, for example, if upgrading from 3.50 to 3.65, which is in the
 same release class, generally you upgrade the server first and the client
 second.

When a new release class is issued, i.e. 3.xx to 4.xx, this type of upgrade
 requires a change to both the server and client.  In this situation, you may
 wish to start a second instance of the MOMI server listening on a different
 TCP/IP port and run two instances of MOMI during the change-over period.

The PC MOMI clients require a minimum server version in order to operate.  The
 "Minimum Server Version" is documented below.  The client will display a
 warning message if connected to a server below the minimum required.

When installing a new release package, the section "Current Versions" (below)
 lists the "Minimum Server Version" required by the client along with the
 oldest client tested with the server.

Special Notes
-------------
The PC must be configured with at least 24 bit color for the client to operate
 fully.  A warning message is displayed at client start up if a lower color
 depth is detected.  While the client will generally function correctly,
 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 SubSystems / Expand
 / Diagram page.

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             4.22
   Release Date          2007/03/29

      Item                  Version
      ----                  -------
      Latest O/S tested        G06.30.01 & H06.09.00
      Client Version           4.22
      Server Version           4.19  vproc:  T0000G06___V4_19____03_28_2007
      Minimum Server Version   4.06
      Buffer Version           Client 21.15  Server 21.15
      History database         3.00
      CONFMOMI                 3.06
      OBYMOMI                  3.03
      OBYCSQL                  3.02
      MomiFTP.exe              1.62
      ssMOMI.scr               4.11
      MomiEMail.exe            1.03
      IPCalc.exe               1.3.3

      Oldest client version
       tested with server      4.06

NEW FEATURES / BUGS FIXED (for previous versions see MOMI HISTORY.TXT)
-------------------------
MOMI Client
   New Screens:
     - on 'Systems:Detail' added 2 new ways to display other systems in
        addition to the old 'All Systems'.
       '1-4 Systems' allows you to select the 1-4 systems you want to view.
       'Systems Line' puts all systems being probed on a single chart.

   New Features:
     - 'Files:Enscribe:Files' now displays the Trusted flag in the column
        labeled 'T'.
     - 'Configure:Server:Server Info 2' now displays 'CPU Limit EMS',
        'TCP/IP Timeout' settings and the 'H06.04 or later' and
        'H06.09 or later' flags.

   Bug Fixes:
     - Rewrote the User Hint loading method to speed processing when a large
        number (hundreds) of user hints are present.

   Misc. Items:
     - None

   Known issues:
     - None

MOMI Server
   New Features:
     - The server now provides the information to allow the client to jump
        from the alarm TMF / Transaction rate (per sec) to the screen
        Processes / Process Entity.

     - The Alarm TMF / Transaction rate (per sec) now has the option to
        Delay Alarm.  Any existing alarm will initially display as Purple and
        indicate it must be re-saved (which updates an internal version number)
        in order to enable the alarm.

     - The IP address of the Network Source is added to the following message:
            "SNTP:System time n.nnnnnn seconds ahead|behind Network Source
             (n.n.n.n)"

     - Added the CONFMOMI keyword CPU-LIMIT-EMS to allow throttling of the MOMI
        server used to process requests on the screen SubSystems / Logs /
        EMS Msgs.  See MOMI help for additional information.

     - Additional checking has been added to processing messages from a client
        to help prevent looping (or other errors) should a foreign message (a
        message not from a MOMI client) be received.

     - Added the CONFMOMI keyword TCPIP-TIMEOUT to determine the maximum
        amount of time a MOMI PC Client may be globally paused or not send in
        any data before the TCP/IP socket is closed.  The value defaults to 10
        minutes.

     - The CPU types S7800B and S86100 are now recognized.

     - Now provide the state of the TRUST flag for object files (this field is
        only available on TNS/E systems) on the screen Files / Enscribe / File.

   Bug Fixes:
     - The computation for the Overall System Busy percent is slightly revised
        to improve accuracy.

     - The following Alarms now enumerate correctly (i.e. expand to the correct
        underlying types of processes) when a wild card is used or handle the
        wild card correctly:

               Process / State running/stopped
               Expand  / Line state up/down
               Expand  / Path state up/down
               TCP/IP  / Ping host

     - The local time offset on the screen CPUs / CPU Info now displays
        correctly during Daylight Savings Time.  Previously, it would be off
        by 1 hour.  The value is for informational purposes and did not cause
        any other processing error.

   Misc.Items:
     - CPU usage during MOMI startup and network traffic during operation is
        reduced when handling lots (i.e. hundreds) of UserHints.

   Known issues:
     - SQL Statements measurements do not seem to function via the MEASURE
        callable procedures used by MOMI on later releases of the operating
        system.  Case 10-070115-8974 is open with HP.

     - On the TNS/E system, some minor features such as ProcessH for System
        code is not yet changed to support the new platform, but all other
        major features are in place.

     - On the TNS/E system, prior to H06.09.00, in CPU where the OSS Name
        Server operates, the MOMI CPU collector in that processor consumes
        progressively more CPU cycles than the other collectors. This has been
        traced down to obtaining OSS Name Server information via MEASURE.  On
        TNS/E systems, the CONFMOMI keyword DISABLE-MEAS-OSSNS TRUE should be
        added to prevent collection of this MEASURE entity.

MOMIFTP
     - None

ssMOMI
     - None

MOMIEMail
     - None

IPCalc
     - None

CLIENT INSTALLATION NOTES
-------------------------
Installation of the PC client via the SETUP does not normally require
 administrative access.  However, this is dependant on the security settings of
 the PC environment.

Windows XP, by default, has more restrictive settings than most.  In this
 environment, the following is recommended if installation is not by an
 administrator or power user (in some cases):

      A) install to a subdirectory other than "\Program Files" which by default
         is fairly well locked down.  Simply choose another subdirectory such
         as "C:\BlackWood Systems" .

      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 for users to operate MOMI in a reduced function 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 Tandem 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 of the program.

While it is BlackWood's 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 systems and some K-Series by default.
 Support for the Nonstop Integrity (i.e. Itanium) and older platforms require
 a simple change to point to the needed object file.

On the Nonstop system, in the subvolume where MOMI is installed, the following
 three object files are present:

   BWMOMIa - 16-bit (accelerated for TNS/R)
   BWMOMI  - 32-bit TNS/R native (K-Series, S-Series)
   BWMOMIi - 32-bit TNS/E native (Integrity)

BWMOMIa is 16-bit code accelerated for the TNS/R systems.  It is primarily used
 for older systems and might support operating system releases prior to D45.

BWMOMI is 32-bit TNS/R native code for the S-Series and K-Series system.  This
 is the default object file selected by MOMI configuration files.

BWMOMIi is 32-bit TNS/E native code for the Integrity systems.

On systems other than the S-Series, change the following:

   1) in the file OBYMOMI, change the variable pointing to the MOMI object
        (BWMOMI is the default) as needed.

   2) in the file OBYCSQL, change the object reference to match the object
       selected in step 1.

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

Note: The EXE files may be altered to ZIP files by renaming them 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 file:

         a. double click on the downloaded file

   2b) If you renamed the EXE to a ZIP:

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

         b. double click on the file Setup.EXE

   2c) If you have a MOMI CD:

         a. double click on the file Setup.EXE

   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.

         On the 1st Connect to Tandem page, fill in the Host Address (your
         Tandem 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 Tandem 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
         Tandem.  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 start up values for MOMI.

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

       For the Nonstop Integrity (i.e. Itanium), change the object file
       reference to BWMOMIi.

   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

       For the Nonstop Integrity, change the object file reference to BWMOMIi.

   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 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 1 minute 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 the value defined in the CONFMOMI file
       (a default of 2000).

Note that other sections of this document will repeat some of these details,
 installation alternatives and/or provide other details.

RUNNING SSMOMI SCREEN SAVER AS A STAND ALONE PROGRAM
----------------------------------------------------
Some users have requested the ability to run the ssMOMI screen saver as a stand-
 alone program that does not stop when the screen is clicked or the keyboard is
 pressed.

To run ssMOMI as a stand alone program the steps are:

 1) make copy of ssMOMI.scr in some location other than C:\Windows and name it
     ssMOMI.exe.

 2) Use run time param of '/c AsEXE' to start program first, setting INI file
     location. i.e. 'D:\Program Files\ssMOMI.exe /c AsEXE' will run the program
     and allow the user to set the location of the MOMI.INI file to be used.

 3) Use run time param of 'AsEXE' to start program using predefined INI.
     i.e. 'D:\Program Files\ssMOMI.exe AsEXE' will run the program so it will
     only stop when the X-button is pressed.

MANUAL INSTALLATION OF TANDEM 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 \Tandem subdirectory to the Nonstop server.
       The source \Tandem 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 BWMOMIa
         b) binary BWMOMI
         c) binary BWMOMIi
         d) binary EMSEXPO
         e) ASCII  FUPEVTCX
         f) ASCII  OBYMOMI
         g) ASCII  CONFMOMI
         h) ASCII  OBYCSQL
         i) ASCII  OBYALTER

   2) After transferring files to Tandem, 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 BWMOMIa,code 100
	      b) fup alter BWMOMI ,code 700
	      c) fup alter BWMOMIi,code 800
	      d) fup alter EMSEXPO,code 845

After the Files are installed on the Tandem:

   1) Volume to the location where the MOMI files were placed

   2) Edit the file OBYMOMI.  Check the process name for MOMI, CPU $MOMI
       operates in, priority and home terminal.

   3) Edit the file CONFMOMI.  Check the TCP/IP process 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 full MOMI users, add your MOMI password.  Also, define any history
       files desired.  Note that MOMI will automatically create the history
       files in the location specified.

   4) SQL compile MOMI.  From the TACL prompt: OBEY OBYCSQL

FUTURE PLANS (may or may not be in future releases)
---------------------------------------------------
   1) Add screen of Pathway information.
   2) Add more history chart-able entities.
   3) Add new functionality as requested by our users
   4) More Tools and References as we think of them

Any suggestions are welcome.  If you run across a bug, please drop us a line!

Email suggestions/bug reports to: support@blackwood-systems.com

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

The MOMI CD or EXE files follow the same general layout.  The smaller EXE file
 only contains 1 format of help and omits the help in Word format.

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

   Setup.EXE                  = MOMI client setup program

   Installer.EXE              = MOMI client/server setup selector program

   Readme.txt                 = Readme instructions    (<<<---START HERE)

   Documents Directory:       = Directory of documentation
      Readme.txt              =     This file
      MOMI History.txt        =     Change history
      License.txt             =     MOMI disclaimer/license
      MOMI_User.doc           =     Word document of user help

   PC Manual Setup Directory: = Directory for Manual Install
      MOMI.EXE                =     MOMI client
      Calendar.mom            =     MOMI calendar database
      TimeZone.mom            =     MOMI time zone database
      ErrorCodes.mom          =     MOMI system supplied error database
      CAIL                    =     Directory containing CAIL Emulator
         <dirs>               =        various CAIL support directories
      HELP                    =     Directory containing new HTML Help
         <dirs>               =        various format Help File Directories
      EXTRAS                  =     Directory containing MOMI Extra programs
         <MomiEMail>          =        SubDir for MOMI EMail
            MomiEMail.EXE     =           MOMI EMail Sending program
         <IPCalc>             =        SubDir for IP Workshop Pro
            IPCalc.EXE        =           IP Workshop program
            IPCalc.hlp        =           IP Workshop help file
            IPCalc.cnt        =           IP Workshop help file
            ip_networks.cmf   =           IP Workshop mask sample
            borlndmm.dll      =           IP Workshop Support DLL
            cc3250mt.dll      =           IP Workshop Support DLL
      SOUNDS                  =     Directory containing MOMI Alarm Sound Files
      MISC_SOUNDS             =     Directory containing MOMI Misc. Sound Files

   Tandem Install Directory:  = Directory of Tandem Installation Programs
      MomiFTP.EXE             =     Program to FTP MOMI files to Tandem
      TanFiles                =     MomiFTP.EXE config database
      PcFiles                 =     MomiFTP.EXE config database
      Tandem                  =     Directory of Tandem software
         BWMOMI               =        MOMI Server   (TNS/R native code 700)
         BWMOMIa              =        MOMI Server   (CISC  16-bit code 100)
         BWMOMIi              =        MOMI Server   (TNS/E native code 800)
         EMSEXPO              =        Compiled EMS filter        (code 845)
         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
         CONFMOMI             =        Initial configuration file

   Extras Directory:          = Directory of Optional Programs
      ssMOMI.SCR              =     MOMI Screen saver