QMessage Monitor

October 2019

Version 8.13
  • Fixed issue with escalation procedures that use the status 'unanswered' not working correctly.

May 2019

Version 8.12
  • Fixed an issue where MMTEMP library was getting full and causing an error because some objects were not being deleted. These objects are now being deleted.

  • Procedure GetFileList works as expected now with a very large number of QHST* files.
  • An audit journal monitoring error message was occurring within Change of User Profiles when using QMM on IBM i 7.3, but this has now been fixed.
  • Program MM8430C has been changed to monitor for the error and recreate the message queue if it doesn't exist.
  • Support for "<", ">", "<=", and ">=" operators as supported message field values has been added to the F1 help.
  • A new version of MM2000A has been created which will cope better with CPIB8F1 messages that contain a large amount of message text..
  • There was an issue with filtering by message data, but this has now been fixed.
  • An F4 prompt has been added to the Automatic Responses/Message Data screen. This allows the user to select a message field and fill in the start/end positions on that screen.

  • Fixed an issue where having more than one rule within UCP0001 was causing the rules to trigger incorrectly.
  • The QRemote Control installer has been modified to more closely resemble the Robot Monitor installer.

  • The old QMessage Monitor installer has been modified to more closely resemble the Robot Monitor installer.

  • Users now have the option to escalate without having to forward to console.

  • Programs MM8600B and MM8700B were changed to remove trailing blanks from the email subject.

April 2017

Version 8.11
  • We removed the limitation on the number of records you can have with QHST monitoring.

  • We updated V7R3 support for MMAUDJRN monitoring.
  • The MMAUDJRN queue won’t fail even if the message queue is full.

  • Monitoring two message queues with the same name no longer fails.

  • An issue that caused systems to drop due to CPF2526 “job message queue cannot be extended” has been fixed.

February 2016

Version 8.10
  • Updated the FWD function to Tivoli using FTP so that Tivoli can now receive the messages through that protocol.

  • Updated the process for clearing the MMAUDJRN message queue so that MMM0189 messages are generated.
  • Changed the processing of the MMRNM (Rename System) command to include MMCONTROL and MMSYST data areas.

  • Resolved an issue where changes to automated responses were not applied to remote systems.
  • Updated the Maintenance module to allow proper processing of the exclamation mark character (!). This also fixed an issue with entering the exclamation mark as a prefix for value lists.

  • Enhanced Shift Maintenance to prevent multiple timespans from being configured with an identical sequence number.
  • Resolved an issue where MMAUDJRN messages were not deleted when the user attempted to delete them from the Maintenance module.

  • Updated the Audit Journal so that the message filters work properly.
  • Added TLS support for outgoing email. While SSL encryption was already supported, this release adds support for TLS.

  • Enhanced the product licensing.

October 2015

Version 8.9
  • Messages that are automatically replied to will now also be sent to the correct support group.

  • Upgrades will now be successful on PCs with names that are up to 10 characters in length.

  • An issue was fixed where queue monitoring was ended when a reply trace error was received.

  • In PC Maintenance, you can now reliably save an automated response that has the option "Less than or equal to" (severity) enabled.

  • After running MMRNM, the data area MMCONTROL will no longer be locked.

  • Running MMRNM will now properly update MMLICIP.

  • Escalation job processing has been improved to better handle SNDDST failure errors.

June 2015

Version 8.8
  • Improved the Audit Journal monitoring performance, specifically aimed at very large volumes of journal records or monitoring requirement configurations.

  • Augmented the functionality of environment variables by adding some variables that were not included in the last release.

  • Fixed various errors in the Audit Journal messages.

  • Remodeled the returned Audit Journal data fields by converting some of the hexadecimal data that was being returned into EBCDIC text. This improved legibility.

  • Refined Activity Log disk usage by allowing the database to re-use deleted records to help reduce the need to run a RGZPFM.

  • Enhanced QHST monitoring if the required product-related PTF has not been installed so that the API is not called unless it exists.

  • Corrected the year-end time zone processing for events when the remote system was specifically two hours ahead of the host system.

  • Amended the Database Server monitoring, as messages were not always being logged when a Group filter was employed.

  • Fixed a few discrepancies (5250/GUI) for enable/disable Automatic Responses and Copy & Paste processing.

  • Enhanced the Pager Format deletion so that it now deletes any Email Body Format data as well.

November 2014

Version 8.7
  • Added Paging “limits” functionality to assist managing costs.

    • You can stop more than a user-defined amount of SMS messages from being sent in a specified time period.

    • When more than the amount is to be sent, Panic List users (from QRemote Control) will be notified.

  • QMessage Monitor Rename command.

    • A command, similar to MONRNM, has been created to allow a system record in QMessage Monitor to be renamed along with all associated data. This is useful when system names are changed for operational or business reasons.

  • Added two-way email support. You can now send messages to email addresses using SMTP, with optional SSL support. You can also receive replies via email using POP3, with optional SSL support.

  • Improved per-job message frequency processing. Qualified job details can now be included to provide granular level frequency processing if required for specific jobs.

  • Automated Response processing:

    • An option was added at the level of an individual automated response that allows it to be enabled and disabled. A disabled automated response is ignored in message processing.

    • Message Data comparisons (right-padding) and Enable/Disable display processing issues have been resolved.

    • Per-job frequency for auto replies has been added to the existing message frequency processing.

    • The F10 key in auto replies now passes the &KEY parameter properly

  • Upgrade/installation process:

  • Improvements have been made to the GUI installer, MMDSTIP, character handling, initial start-up, and joblog monitoring.

  • Changes were made to the installer so there are no longer issues when upgrading systems that have a large number of processors

  • Console changes:

    • Virtual Server support has been improved by adding separate user logins.

    • After you click OK to Clear Messages in the GUI console, you no longer have to confirm it again.

    • The labels and text in the Clear Messages dialog box have been improved to make the options clearer

  • Escalation procedures:

    • You can now acknowledge an escalation procedure from a remote system and not just the host system.

    • Fixed an issue where an escalation procedure could, at times, use an incorrect support group when it also uses an SNMP trap

  • QMessage Monitor now uses the system value QUTCOFFSET for the system’s time zone, rather than its own settings.

  • A user program has been provided to add the ability to process messages in joblogs.

  • A memory leak that existed in the QHST processing has been plugged.

  • The products have all been tested on a V7R2 network.

  • The command MMARCLOG was enhanced so that you can tell it to wait for the submitted jobs to finish before returning.

  • Activity Log: The search no longer fails when using the RG (date range) parameter.

  • MMCVTLOG now monitors for empty members.

  • F5, Refresh, was added to the log inquiry, MMLOGINQ.

  • QMMESC: The MMEMLMNT command was added to the QMMESC menu.

  • DB Server: Database monitoring messages are no longer issued without a matching filter.

  • SYSMAINT: Selecting Options > Reload Cache when SYSMAINT is not connected no longer causes the module to crash.

June 2014

Version 8.6
  • Updated processing of expiry codes.

December 2013

Version 8.5

No updates for this release.

November 2013

Version 8.4
  • Updated Auto Responses to show reply statistics and reply history.

  • Added reply simulation mode.

  • Added notes to SNMP messages.

  • Enhanced message clean-up.

  • Updated audit journal categories.

  • Created new database filters for Database Access Monitoring.

Back to Product Index