The release notes are available in the \Docs subdirectory of your installation.

Late-breaking information about this kit can be found in: \relnotes\readme.1st

Release notes from prior kits are combined in the files: \relnotes\cache\prenotes.htm and/or \relnotes\ensemble\prenotes.htm

This document provides a list of the changes between versions 2008.2.3 and 2008.2.4 for Caché and Ensemble.

Topics include:

• General Announcements
• Restricted Rights Legend
• InterSystems News, Alerts, and Advisories
• Online Documentation
• Description of a Change Report
• Change Reports for This Maintenance Kit

Customers running on any prior released version of Caché may upgrade to this version of Caché during installation. When upgrading across multiple versions, intermediate upgrade steps may be necessary depending on the inter-release compatibility requirements. The release notes for the intervening releases will contain that information.

After each upgrade step, the following conditions apply:

The following guidelines apply to the process of upgrading ECP configurations:

If you have questions or concerns about how to upgrade your ECP configuration, please contact InterSystems Worldwide Customer Support.

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

When acquired by the Government, commercial computer software and related documentation bearing this legend are subject to the following:

1. Title to and ownership of the software and documentation shall remain with the Contractor.
2. Use of the software and documentation shall be limited to the facility for which it is acquired.
3. The Government shall not provide or otherwise make available the software or documentation, or any portion thereof, in any form, to any third party without the prior written approval of the Contractor. Third parties do not include prime contractors, subcontractors and agents of the Government who have the Government's permission to use the licensed software and documentation at the facility, and who have agreed to use the licensed software and documentation only in accordance with these restrictions. This provision does not limit the right of the Government to use software, documentation, or information therein, which the Government has or may obtain without restrictions.
4. The Government shall have the right to use the computer software and documentation with the computer for which it is acquired at any other facility to which that computer may be transferred; to use the computer software and documentation with a backup computer when the primary computer is inoperative; to copy computer programs for safekeeping (archives) or backup purposes; and to modify the software and documentation or combine it with other software. Provided that the unmodified portions shall remain subject to these restrictions.

From time to time, InterSystems publishes items of immediate importance to users of our software. These include alerts, mission critical issues, important updates, fixes, and release announcements.

The most current list can be obtained from the InterSystems Website.

Users should check this list periodically to obtain the latest information on issues that may have an effect on the operation of their site.

As a convenience to our users, InterSystems provides online access to documentation for recent product versions at the InterSystems Website. From the home page, choose the Support & Education tab, then choose the Support menu item for the product you are interested in, for example, Caché Support. Links to the available documentation can be found on the support page for each product.

To help you assess the impact of this maintenance kit on your applications, the remaining topics in this document describe each modification in detail.

If you need assistance evaluating the effect on your application(s), system(s), or related plans, please contact the InterSystems Worldwide Support Center:

• Phone:  +1  617  621-0700
• Fax:  +1  617  734-9391
• Email:  support@intersystems.com

This correction fixes Ens.Rule.RuleDefinition:PurgeRuleCache to delete routine pointers. Without this change, it is possible to have two different rules pointing at the same routine in the rule cache.

This change makes the queries generated by the Message Browser use %ID instead of ID in naming the IDKEY field of message body classes. This allows the browser to correctly retrieve messages whose IDKEY field is named something other than "ID".

This change modifies %SQLGatewayConnection.Fetch to properly handle the end-of-data condition when using ODBC stored procedures that return dynamic result sets. In this case, the result set indicates whether more data is available; previously the adapter had been depending on SQLCODE to indicate this condition.

This change corrects the message trace display to function properly when the production is not running.

Before this, the display depended on the production being in a running state. When this was not true, events related to the production may have been omitted from the display.

In the details pane, the time logged for events was not being converted from UTC to local time. This change adds this conversion.

Users might experience performance problems using the Ensemble Message Trace when there is a high volume of Event Log entries. This problem has been resolved. In addition, there are now search filter criteria that allow users to have more control over the inclusion of events in the trace diagram.

When a message trace diagram is displayed, if the user clicks on the canvas a form containing fields with search criteria appears in the bottom frame. The control information provided is:

• IncludeEvents:

  Check the box to see Event Log items related to the session included in the trace, or uncheck to omit them. Default is checked.

• EventsWindow:

  Number of seconds, after latest time processed or EndTime field, whichever occurs first, to look for events to be added to the diagram. Default is 30 seconds.

• EventsMaxRows:

  Maximum number of table rows in table Ens.Util.Log that will be scanned, within the time limits defined plus EventsWindow, to look for events that match the session. Default is 1000 rows.

  The purpose of this limit is to contain scanning of the Event Log table. If the upper time limit is reached, the search stops; if not, in case there is a cluster of intense activity going into the Event Log, which is very unlikely, Ensemble will stop after searching this number of records.

If any of the above filter properties is changed, the change will remain for the duration of the Portal session. The other search fields affect the current diagram only. Clicking the Reset button reverts the properties related to events back to their defaults, reverts SessionId, and clears the other fields.

When running the management portal over HTTPS, the following SVG graphics would fail to render: Production Configuration diagram, Message Trace diagram, Dashboards and Business Process diagram. This problem has been fixed.

In the Production Configuration page of the Ensemble Management Portal, after sliding the frame dividers, if the user exited the page and later returned to display another diagram, he would see just the title frame and nothing else but a blue background.

The reason is that IE8 would set an incorrect size for the title frame. When it restored the previous sizes it would acquire that wrong size. This wasn't a problem with IE7 and IE6; it has been corrected by this change.

This change consolidates all the fixes to the Message Trace related to performance issues when there is a high volume of Event Log entries.

This change modifies the SQL generation logic used in the Ensemble Message Browser. The improvements made with this change are:

• Do not use the TOP phrase when SearchTable terms are involved or when not using SessionStart
• For a simple equality test of a single SearchTable property condition, do not use an IN subquery
• For negation operators (!=, DoesNotContain and so on), generate a NOT IN of the inverse positive operator. This makes it possible to exclude messages that have several property values where one of them satisfies the negative condition.
• For = or != an empty-string, use logic that includes or excludes messages that have no virtual document property at all of the specified type.

TAP833 modified the queries generated by the Message Browser page when there is only one simple equality SearchTable condition. This change fixes that modification to work when there is only one *enabled* SearchTable condition (and it is a simple equality condition). Disabled conditions no longer count.

This fix corrects an error in the platform detection logic of InstallShield that would detect a Windows 2003 PDC as Windows XP.

If a breakpoint was set on the line immediately following a ;;comment, the breakpoint would be ignored.

This is now fixed.

This change corrects an error where an attempt to start a remote database in ECP via the Management Portal on Solaris systems caused the ECP server to hang.

This change improves the checking of IP addresses to account for the fact that IPV6 addresses do not support wild card characters as IPV4 address do (for example, 192.168.*.*).

Prior to this change, output parameters in ODBC linked stored procedures were not accessible in the case where dynamic result sets were returned. This change also modifies the return value of %SQLGatewayConnection.Fetch. It no longer reports an error if SQLCODE=100. The user should check SQLCODE for errors when the end of data is reached.

These changes correct an issue where certain activities in Studio caused temporary information to be left in CacheTemp. Repetition of these activities resulted in expansion of the CacheTemp database to the point where it degraded system performance.

When a user disables syntax checking (Options->Editor->Syntax Check and Assist->Enable Syntax Checking "unchecked"), this change also disables all syntax-check parser-related actions, including studio assist, tooltips and context sensitive menu for particular syntax element will be disabled.

This change corrects a problem where the output of Japanese characters is garbled in Studio Debugger output window. Attempting to write

Japanese : <ASCII(12354)>

would result in

Japanese : B0

instead of

Japanese : <Japanese symbol>

This change assures that the currently active namespace is properly re-established when a routine search follows mappings to other databases.

With this change, Caché now allows the definition of custom i/o tables at the locale level that use built-in translations for input, output or both sides. Previously, attempting to use such tables would cause an access violation.

Application extensions to the Caché SNMP MIB were not getting registered on UNIX (or OpenVMS) when the Caché ^SNMP sub-agent started, and no instances of the user's MIB could be queried. This is now corrected.

This change corrects a problem where certain Unicode strings with sequences of repeated digits was stored in a compact form on the disk, but then decoded incorrectly in a situation where the encoded repeat sequence crossed a disk block boundary on disk.

This change works around an issue on Solaris with Zones configured. If LC_COLLATE is set, translation of strings in scripts fails. Because of this, an attempt to start a remote database in ECP via the Management Portal causes the ECP servier to hang.