Readme.rtf Date 2010/04/16 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. An example is EMS / User define alarms once updated with a 5.xx client 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. 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 5.17 Release Date (yyyy/mm/dd) 2010/04/16 Item Version ---- ------- Latest O/S tested G06.32.00 & H06.20.00 & J06.09.00 Client Version 5.17 Server Version (VPROC) 5.16 T0000G06___V5_16____04_14_2010 Minimum Server Version 5.00 Buffer Version Client 21.27 Server 21.27 History database 3.00 CONFMOMI 3.08 OBYMOMI 5.00 OBYCSQL 5.00 MomiFTP.exe 1.67 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. MOMI Client New Screens: * None New Features: * ANSI names added to 'Files' grids 'File Entity','DiskFile Entity', and 'DiskOpen Entity'. * ANSI names added to 'Process:Process Detail' grids 'File Entity has Open', 'File Entity Opened by','DiskOpen Entity'. * Grids with ANSI names now first column (File Name) is a synthetic name i.e. if ANSI use ansi name else if OSS use OSS pathname else use NSK Name. * Left Click on Synthetic name and display all 3 (ANSI,OSS,NSK). Bug Fixes: * 'Alarms:Define:Import' did not notify user when export failed because the export file was from different version of client than the import. Fixed. * 'Configure:Settings:Single Screen:SubSystems'. If user checked/Unchecked the 'Logs:VHS' or 'Logs:MOMI' 'Reverse Scrolling' checkbox before that screen had been viewed(created) the client would crash. Fixed. * 'History:Export Data:Scripts' the export dates 'this week,last week,this month and last month' did not work for any data type except CPU. Fixed. Misc. Items: * Converted PFS value display on 'Processes:Process Detail' to show used percentage. Known issues: * None MOMI Server New Features: * The MEASURE entities DiskFile, DiskOpen and File now provide an ANSI file name for SQL/MX objects. Bug Fixes: * Tool-tip information now displays on the screen Alarms/Define/Alarm field area Delay Alarm. * BWSSG is now used if MOMI is operated under a Group.Manager (i.e. *.255) User ID. Previously, MOMI did not utilize BWSSG causing Ping and Tracert to fail due to lack of needed security - "Failure to open socket - Error 4013 - (Permission denied)" Misc. Items: * Additional error information is now logged in the event that the value specified for ALARM-SMTP-SERVER-ADDR was invalid or a connect failed. * The internal processing for a demand type of measurement is revised to work around issues discovered with ZMS style of MEASURE entities and the different NonStop platforms. * Various OSS counters are now loaded for Guardian processes to allow reports where these processes are using OSS calls. * The MEASURE entities DiskFile, DiskOpen and File now provide 'cleaner' OSS path information by not reporting /G/ in the OSS Path Names. * The MEASURE entities Disk, DiskFile, DiskOpen and File now internally use ZMS style of counters on G06.26 and later releases. ZMS counters generally drop support for ^MAX type of counters and information such as channel/address from older K series systems. * As of H06.20.00 & J06.09.00 it is no longer necessary to operate BWSSG as Super.Super. It may now be operated under Super.Group. HP corrected (somewhere) the underlying issue. Known issues: * None. MOMIFTP * Prevent timeout on inactivity. Fixed bug not displaying NSK filenames. 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) BWMOMI is 32-bit TNS/R native code for the S-Series. BWMOMIi is 32-bit TNS/E native code for the Integrity and Blade systems. 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 / 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 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 source \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