Remaining MRM-related Bugs / RiverWare 6.1 / January 26, 2011

Bug Filer* Filed Description Analysis
3960 AG 5-2006 GUI Dialogs have user input issues This is mostly about DMI. It mentions MRM dialogs too, and those problems have been resolved.
3977 AG 6-2006 Output Manager slot lists need to be export/importable (MRM Manager is just mentioned as an example of the desired functionality: The Slot List window).
4066 RC 9-2006 MRM Run failure to provide meaningful error message when failed. Index Sequential error needs better reporting.
4192 JV 2-2007 MRM Output Control File related Assertion Failure Assertion Failure related to filename handling
4321 AG 9-2007 Feature Request: Pre/Post Execution DMI issues (MRM is mentioned as having the correct behavior).
4351 BV 10-2007 internal error with MRM consecutive run Limitations of the design and implementation of Consecutive MRM runs.
4671 Bill 12-2008 DMI might be doing extra work during MRM Performance and Memory Leak concerns
4719 LL 3-2009 In the middle of running a MRM, a window error message stating "riverware.exe has encountered a problem and needs to be closed." And RiverWare closes. See David's Analysis in bug report.
4977 David 10-2010 Initialization rules and expr slots don't deal well with HasRuleFiredSuccessfully (Includes suggestion that the solution to this RPL problem should also work for MRM rules).
4989 Alan 11-2010 MRM does not close rule set after each trace Needs determination of whether the observed behavior is undesirable. NOTE that the MRM dialog Qt4 port work made it easier for the user to Open an MRM's Rulesets. So, maybe closing them, as Alan suggests is that much more reasonable. But it's not clear that this is really a problem.
5014 David 1-2011 Assertion Failure in MRM Run when required data is missing Run error handling error.

*Filers: