Readme.rtf Date 2011/10/20 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. However, for MOMI 5 you may use a MOMI 4.xx Client with a MOMI 5.xx server. Please note that some features once activated with 5.xx clients may no longer be visible or operate correctly in a 'mixed' client environment. Once your MOMI server is upgraded to 5.xx, we recommend that clients used for update purposes, such as defining Alarms, are all either 5.xx or all 4.xx. For example, once the alarm EMS / User defined is updated with a 5.xx client it will no longer display properly with a 4.xx client. 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.23 Release Date (yyyy/mm/dd) 2011/10/20 Item Version ---- ------- Latest O/S tested G06.32.01 & H06.23.00 & J06.12.00 Client Version 5.23 Server Version (VPROC) 5.23 T0000G06___V5_23____10_14_2011 Minimum Server Version 5.00 Buffer Version Client 21.34 Server 21.34 History database 3.00 CONFMOMI 3.08 OBYMOMI 5.00 OBYCSQL 5.00 MomiFTP.exe 1.68 ssMOMI.scr 4.12 MomiEMail.exe 1.04 SendMail.exe 1.00 IPCalc.exe 1.3.3 Oldest client version tested with server 4.22 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: * 'Alarms : Active' if alarm detail '[+]' is being displayed the detail may now be split into multiple lines of a fixed length. This is set in the 'Configure : Settings : Single Screen : Alarms' section labeled as ' Split Alarm detail into shorted lines [####]'. (for Tom S.) * Created ability to use previously exported ini file to create new ini when client is first started. This will allow administrator to setup default startup ini for new installs. See 'MOMI_INIT.INI' help for how to setup and use. * On 'SubSystems : Logs : EMS Logs' added ability to add/select multiple collectors at same time by using a comma between collectors in the 'Collector or LogFile' location. If the user then presses the Add arrow they are all added and if the user presses the 'Request with new options' button they are all added and the collection starts. (for Hal D.) * On 'SubSystems : Logs : EMS Logs' the Config display shows the state of each collector. (this may also be displayed by right-clicking the 'Config' button. - 'Requesting - no recs yet' = messages requested but not yet received. - date and time = date time of last messages received. - 'Stop Time reached' = Collector has reached stop time. - error text = any error receiving messages from collector. Bug Fixes: * On 'Processes : All Processes', 'Files : Enscribe : Files' and 'SubSystems : Spooler : Jobs' if the AutoUpdate checkbox was checked a very small memory leak was occuring with each update. Fixed. * On most grid-type screens, If user stopped the update before all records were loaded the screen would remain 'locked' and not repaint once the user left the screen and then returned to it. Fixed. * Previously if a user created a shortcut to start MOMI and set that shortcut to 'Start Minimized' the MOMI Icon would not minimize to the Task bar but instead put a small window above the Task bar that would need to be right-clicked then restored to get the Client to start. Then it would not be minimized. Fixed. * If the user selected the Overview screen EMS Messages and the EMS system was very backed up with messages, the client would hang until it caught up. Fixed. * If 'Configure : Client Access : Overview' setting 'Allow Display of EMS Msgs' was not checked the EMS button was still available on Overview' and 'Configure : Settings : Single Screen : Overview' setting 'CPU/Process/EMS' was still available. Fixed. * If user was viewing more than 2 EMS collectors and then changed systems the client would crash. Fixed. * On 'Systems : FTP' when a file was transferred from a remote Windows Host to the local PC the confirm dialog would not display names and was locked and a transfer was impossible. Fixed. * When the Overview screen was setup to display EMS messages and the CPU History chart was clicked the History detail was displayed behind the EMS messages. Fixed. * 'Processes : Last Start/Stop' was duplicating records with every update. Fixed. * Grid Exports did not always show the correct system name when the client had changed systems. Fixed. * On 'SubSystems : Logs : EMS Logs' when displaying records in reverse order(last at bottom) the last few records would not display. Fixed. * On 'SubSystems : Logs : EMS Logs' when records were received while the Config settings display was visible and the EMS display was paused the records would not update on the screen once the config was closed. Fixed. * On 'SubSystems : Logs : EMS Logs' after a screen resize the define filter popup was being displayed in an incorrect location. Fixed. Misc. Items: * Dramatically decreased the time taken to clear (delete all records) a Grid with a large number of rows. * Client Security Logon maximum length values changed to fit buffer sizes. - UserId max length changed from 39 to 32 - Password max length changed from 39 to 25 - New and confirm new password max length each changed from 64 to 25 * On 'Processes : All Processes' changed column for 'Qualifier Info Available' from a '?' label to 'Q' and added new synthetic object file type. * On 'Processes : Process Detail' and Processes : ProcessH' added new synthetic object file type. * Removed code for old 'History Chart 1'. Chart 1 has been hidden since 5.20. * Changed logic used when changing to a system that client access requires the screen to be hidden. Previously the screens would display then be hidden causing a 'flash'. Now they are just hidden. * Grid data exports can now be stopped during collection and creation. * When using File selector to get ems log file for EMS LogFile the EMS start date and time are now set equal to that file. * Moved the 'Auto-start MOMI' items from 'Configure : Settings : File Locations' to the 'Actions' page. * Added 'Cail File path' to 'Configure : Settings : File Locations'. * In 'Client Access' if someone attempts to update or delete the record for the 'Default Security User'(the user that started MOMI) a popup will display informing them that users record may not be changed. * Dramatically sped up the Grid Tools 'Export to Clipboard' and 'Export to HTML'. * On 'SubSystems : Logs : EMS Logs' when records are being received and the 'Config' button is pressed the Display will not Pause but will keep retrieving records unless the user presses the 'Pause' button. * Added Socket info to 'Config Info' report. Known issues: * None MOMI Server New Features: * A new field of Code Type is now returned, obtain from Guardian rather than Measure as seen on the screen Processes / All Processes, which more accurately displays the type of process or the type of load file. These are the current values: TNS TNS Accelerated Native (Non-PIC) Native (PIC) Bug Fixes: * Load files, displayed on Processes / Process Detail, sometimes were not sorted. * Corrected the processing of EMS messages so that if a users templates have an override of the token ZEMS^TKN^EMPHASIS it is now picked up. Misc. Items: * Load files, displayed on the Processes / Processed Detail, now show as a space instead of ??? for a TNS Library in column Library Type. The column only applies to native object files. Known issues: * None MOMIFTP * added success popup message when done. ssMOMI * None MomiEmail * None SendMail * None IPCalc * None CLIENT INSTALLATION NOTES Installation of the PC client via the SETUP does not normally require administrative access. However, this is dependent 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 C:\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 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 or updates. 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, NonStop Integrity and NonStop Blades. 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) The TACL obey files OBYCSQL, used to SQL/MP compile MOMI objects, and OBYMOMI, used to start the MOMI subsystem, automatically select the proper object file to invoke. 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. 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 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 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. 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 on TNS/E) FUP GIVE BWSSG, (super.super on TNS/E) FUP SECURE BWSSG, NGNG, PROGID 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 2000. Note that these instructions may be repeated 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\\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 EMSEXPO d) ASCII FUPEVTCX e) ASCII OBYMOMI f) ASCII CONFMOMI g) ASCII OBYCSQL h) 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 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 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 selector program Readme.rtf = Readme instructions (<<<---START HERE) Documents Directory: = Directory of documentation Readme.rtf = This file MOMI History.rtf = 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 EXTRAS = Directory of supplemental programs = SubDir for MOMI EMail MomiEMail.EXE = MOMI EMail Sending program SendMail.EXE = MOMI EMail helper program = 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 NonStop Install Directory: = Directory of NonStop Installation Programs MomiFTP.EXE = FTP MOMI files to NonStop System TanFiles = MomiFTP.EXE config database PcFiles = MomiFTP.EXE config database NonStop = Directory of NonStop software BWMOMI = MOMI Server(TNS/R native code 700) 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