This ZIP file contains an update to the MOMI server - Version 6.17i This server is: - based on version 6.17h - compatible with MOMI PC Clients: 5.80 to 6.17j - server vproc: T0000G06___V6_17I___2024_04_25 Sections --------- Changes in this update How to update VPROC detailed information Changes in this update ---------------------- - A problem was corrected that after a client disconnects it could result in a MOMI server process with excessive CPU usage and priority drop to 1. This was observed in the main $MOMI process and suspected in other MOMI server processes. Typically, the the client would need to be connected for a long period of time (perhaps days) and visited the Files / DiskEntity L/H screen. - A crash was corrected in MOMI CPU collectors, one per processor, which could occur at MOMI subsystem startup if the NonStop System was configured for 32,099 PCBs. An EMS message logged "LB_XMEM_GET_PAGE : INTERNAL ERROR" would be logged. The underlying issue could manifest itself under other conditions. How to update ------------- Download the ZIP file to your PC, right-click on it and select Extract All... (i.e. using the Windows built-in extractor) and follow the prompts. Double-click on MOMIFTP.exe to launch the transfer utility or manually transfer the files. If using MOMIFTP -> 1) in the extracted file double-click on MOMIFTP, follow the on-screen instructions and leave the default of "Update Installation". This utility is the same one used in our full release package but contains just the updated files and expects an installation is already present. MOMIFTP transfers files in the correct manner (i.e. ASCII or binary), set file code, and performs file rename of an existing file automatically (i.e. 2 for oldest, 1 for next oldest). You can run MOMIFTP while $MOMI is operating on your NonStop System. 2) continue with step 5 below. If using another file transfer method, follow the steps below but you need only transfer the MOMI suitable for your platform -> 1) On the NonStop System, volume to the location where the MOMI server is installed. 2) To prepare to receive the new object file, the existing file needs to be renamed. The rename convention we use places a number at the end of the file name and the highest number is the oldest. Purge the oldest BWMOMI? object and rename the others: TNS/X purge bwmomix2 rename bwmomix1,bwmomix2 rename bwmomix ,bwmomix1 TNS/E purge bwmomii2 rename bwmomii1,bwmomii2 rename bwmomii ,bwmomii1 TNS/R purge bwmomi2 rename bwmomi1,bwmomi2 rename bwmomi ,bwmomi1 3) Using your favorite file transfer utility copy the needed files as shown below from your PC to the NonStop System in the manner indicated: - BINARY the BWMOMIx - BINARY the BWMOMIi - BINARY the BWMOMI 4) On the NonStop System, alter the file code: fup alter bwmomix,code 500 fup alter bwmomii,code 800 fup alter bwmomi ,code 700 -> 5) SQL compile the object file with the TACL obey file: obey obycsql 6) if MOMI is not running under a Super.Group, also update BWSSG (see below). 7) restart MOMI with the TACL obey file: obey obymomi If MOMI is started under Super.Super or a "Super.Group", skip this section as BWSSG is not needed (i.e. MOMI has the security it needs). Starting MOMI under any other ID means that BWSSG should be created (and secured as indicated below) to indirectly give MOMI the ability to perform PING, Trace Route and System time maintenance (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 - BWMOMIx on TNS/X) FUP GIVE BWSSG, (where your desired ID) FUP SECURE BWSSG,NGNG,PROGID Vproc information ----------------- BWMOMIX Binder timestamp: 25APR2024 15:39:59 LCT, 25APR2024 22:39:59 GMT Version procedure: T8432L01_01OCT2014_CCPXMAIN_O1 Version procedure: T0000G06___V6_17I___2024_04_25 Version procedure: T0000G06___TDS01LT__2021_12_01 Version procedure: T0000G06___TOMCYAP__2014_10_24 Version procedure: T0000G06___UTL02LT__2024_04_25 Version procedure: T0000G06___OSS01SC__2017_05_08 TNS/X Native Mode: runnable file BWMOMII Binder timestamp: 25APR2024 16:02:01 LCT, 25APR2024 23:02:01 GMT Version procedure: T0000G06___V6_17I___2024_04_25 Version procedure: T0000G06___TDS01LT__2021_12_01 Version procedure: T8432H04_26FEB2014_CCPLMAIN Version procedure: T0000G06___TOMCYAP__2014_10_24 Version procedure: T0000G06___UTL02LT__2024_04_25 Version procedure: T0000G06___OSS01SC__2017_05_08 TNS/E Native Mode: runnable file BWMOMI GMT Binder timestamp: 25APR2024 22:59:13 Version procedure: T0000G06___V6_17I___2024_04_25 Version procedure: T8432G10_10MAY2007_CRTLMAIN_ABL Version procedure: T0000G06_S_OSS01SC__2017_05_08 Version procedure: T0000G06___TOMCYAP__2014_10_24 Version procedure: T0000G06___TDS01LT__2021_12_01 Version procedure: T0000G06___UTL02LT__2024_04_25 Native Mode: runnable file