MOMI Readme.txt Date 2005/11/11 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. If you install the sample CALENDAR.NEW File it will not overwrite your CALENDAR.MOM file. It is only used when a CALENDAR.MOM does not already exist. This prevents changes made to your calendar from being lost with an upgrade. The same is true of the ERRORCODES.MOM, if a new copy is installed it will not effect the User-added entries that are saved in the CUSTERRORS.MOM file. Sections in this document ------------------------- Compatibility between client and server Special Notes CURRENT VERSIONS NEW FEATURES / BUGS FIXED CLIENT INSTALLATION NOTES PASSWORDS mini-MOMI 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 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 startup 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. CURRENT VERSIONS ---------------- Release Package 4.05 Release Date 2005/11/11 Item Version ---- ------- Latest O/S tested G06.27 Client Version 4.05 Server Version 4.04 vproc: T0000G06___V4_04____11_11_2005 Minimum Server Version 4.00 Buffer Version Client 21.04 Server 21.04 History database 3.00 CONFMOMI 3.03 OBYMOMI 3.02 OBYCSQL 3.00 MomiFTP.exe 1.55 ssMOMI.scr 1.09 Oldest client version tested with server 4.00 NEW FEATURES / BUGS FIXED (for previous versions see MOMI HISTORY.TXT) ------------------------- MOMI Client Known issues: - Predefined alarm sounds are not all available yet. New Screens: - none New Features: - on 'Configure:Settings:Actions' added ability to import MOMI INI file. Note: after importing the user must exit the client and restart it to get the new settings. - on 'Configure:Client Access:Define' added button to clear and check all items. (for Vikas K.) - on 'Configure:Client Access:Define' added ability to define UserId profile with wildcards (* and/or ?). For Expample: This allows a UserID profile of APPL.* which allows any user loggong on under the APPL group to use this profile if there is not an exact match. (for Vikas K.) Bug Fixes: - Under some rare circumstances, if the Client lost its connection to the Tandem the Client would enter a deadly embrace hard loop and would not be accessible. The only way to recover the client was to stop the MOMI Client. Fixed. - versions 4.03 and 4.04 had bug not allowing new users to be added to Alarm Email Group. Fixed. - If a TCP/IP Connection timer expired (Tandem hasn't answered client in 30 seconds or more) and Restart AutoUpdate on ReConnection is set the Client would not restart the AutoUpdate. Fixed. - 'Configure:Reference:Unit Conversion' would only use the first 4 characters entered in the conversion. Fixed. Misc. Items: - none MOMI Server New Features: - The generation of Email in alarm processing is now performed in an Asynchronous manner. - The Alarms for Process / Debug/Inspect and Process / Looping now display the object file name. - The Session Time for Processes / ProcessH Entity can now display days. - The LOG file now displays the second line of an Alarm. - The MOMI CPU collectors and the screen Processes / All Processes no longer send a device query to subtype 30 processes that are suspended. Bug Fixes: - The Alarm Spooler / Device - State down/not ready now accepts an Entity Name with an optional first and second qualifier (i.e. $dev.#aa.bb). - A small memory leak (160 bytes) was corrected in MOMI servers that open and close a file. - The screens Files / File Entity and Processes / Process Detail File Entity now correctly display a TCP/IP v4 address when available. Note that this information is not always available from MEASURE (only OSS sockets and it appears to be OSS server sockets). Misc. Items: - The LOG file is now available even if history is not enabled. Known issues: - none MOMIFTP - none ssMOMI - none KNOWN BUGS - 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 suggested 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. PASSWORDS --------- Existing customers, or customers using an active trial password, can use the password previously supplied for version 2.xx of MOMI. Password versions are as follows: Password version description ---------------- ----------- Version 1 early MOMI releases Version 2 MOMI release 1.xx Version B MOMI release 2.xx Version B MOMI release 3.xx Version B MOMI release 4.xx Please send an email to BlackWood if you are unsure or have any question about a password. 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. 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 code 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 will have an initial screen referring to the self extracting files. Press Setup. 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 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 startup. 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) Start MOMI: From a TACL prompt: OBEY OBYMOMI (wait at least 1 minute before proceeding to the next step) 15) 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 runtime 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 runtime 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 -------------------------------------------- Two versions of MOMI server based objects are available, native or accelerated. Native objects, the default, should be used on all G series and D4x versions of Guardian. Accelerated objects provide some support for older versions of Guardian. While both objects provide the same functionality, we recommend the Native versions to provide the highest level of performance. Note that the accelerated versions have an A on the end of their name and would have a file code of 100 instead of 700. Rename the object file to remove the "A" once it has transferred to the Tandem. There are 2 methods to Transfer the Tandem Files: 1) Using the MOMIFTP.EXE program in the '\Tandem Install' directory. This program will transfer all the files from the PC to the Tandem via FTP. Also, it will set the necessary file codes. To use this program, simply run the program (double click on it) and follow the steps on the screen. 2) The Manual method: A) FTP (or IXF) files from the \Tandem subdirectory. This subdirectory is either from the expanded ZIP or the subdirectory where the MOMI client is installed if you chose the FULL or Custom option. Note the binary/ASCII requirements. a) binary BWMOMI (or BWMOMIa) b) binary BWMTCP (or BWMTCPa) c) binary EMSEXPO d) ASCII OBYMOMI e) ASCII CONFMOMI f) ASCII OBYCSQL g) ASCII OBYALTER B) After transferring files to Tandem alter the file code for the two binary files to file code 700 (use 100 if accelerated) via FUP. a) fup alter BWMOMI ,code 700 (or 100 if BWMOMIa) b) fup alter BWMTCP ,code 700 (or 100 if BWMTCPa) c) fup alter EMSEXPO,code 845 Alternately, the TACL obey file OBYALTER can be used to perform the file code alterations. 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 chartable 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_MOMI.exe = MOMI client setup 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 = various CAIL support directories HELP = Directory containing new HTML Help = various format Help File Directories 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 (native code 700) BWMOMIA = MOMI Server (16-bit code 100) EMSEXPO = Compiled EMS filter (code 845) 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