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.5 and 2008.2.6 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 change prevents the call to the PurgeAll method of the Ens.Purge class from removing the error history. Users who wish to clear this must do so explicitly by deleting the global, ^ERRORS

This change corrects an error that did not properly adjust the transaction level in error traps invoked during a transaction rollback.

This changes forces Ensemble to respect the default CSP application timeout when opening DTL in the Studio. Previously, this was overridden to be set to "never", which caused CSP session licenses to be held in perpetuity; only manual intervention or an Ensemble restart would release the licenses.

This corrects an error that occurred when adding two numbers where:

• Each number consisted of 19 significant digits.
• Each number had one digit after the decimal point.
• The sum of the two numbers would not fit in 64 bits.

In this case, a <SYSTEM> or other error wold result when trying to save or use the result.

This fixes a problem with dealing with multiple subscripts where:

• The subscript is a number between 0 and .01.
• The value has an odd number of leading zeroes before the first non-zero digit.
• There are 10 digits after the leading zeroes.
• The value of the non-zero digits considered as an integer lies between 1000000001 and 4294967295, inclusive.
• The value is encoded as a number instead of as a string (that is .0001220703125 rather than ".0001220703125").

This only occurred on 32-bit platforms that do not support 64-bit arithmetic.

ECP establishes its connection on the first reference to any remote global. While establishing a connection, if the ECP client daemon creation fails, it may leave the connection in "in progress" state.

This change detects the errors associated with this situation and attempts to recover from it. It also attempts to fix itself when daemon creation fails.

This change fixes a rare condition where a long string could be dropped or lost if the database server was restarted right after the last data transmission, but before the journal became durable.

It also fixes issues with long string SET command recovery across ECP. If the server or connection fails in the middle of a SET involving a long string, the assignment may fail with <NETWORK> error or the SET may be dropped altogether.

In rare cases, when the ECP work daemons cannot keep up with activity, and there are many activities queued, the session that originated the work in the background may go away. It may also reconnect with leftover activity from the previous session. This modification prevents any old or stale work from being processed after a disconnect (and/or reconnect) by removing it from the work queue during session cleanup.

Under very rare conditions, if

• The ECP server is a different endianness than the application server;
• There is a SET in the process of being propagatedto the client;
• The SET involves a non-compact Unicode string;
• The block that the SET will modify has arrived at the client;

then the cache may be updated with the wrong endian value.

This change corrects a deadlock occuring between the finalizer of com.intersys.classes.CacheRootObject.releaseInternal() and com.intersys.cache.DatabaseWithReferenceMap.releaseFromMap() when using connection pooling in TomCat.

This change fixes a memory corruption when the binding server was used by Java on OpenVMS. The symptom was a <NULL VALUE> error reported on %SYS.BINDSRV

This corrects an issue where a number in $DOUBLE format could be stored in these datatypes.

This corrects an issue where signalling a message for an undefined event, or undefined process id will cause the event to be allocated but never used. This could cause a memory leak.

This change corrects an error in handling message timeout conditions that can occur when starting a remote ECP database from the Management Portal.

This fixes a problem where a core dump can occur when running INTEGRIT.

This change fixed a possible <NAMESPACE> or <DIRECTORY> error that can occur if the system is re-activating the namespace table while a namespace is being edited.

$ZUTIL(193,x,1) converts date to UTC. If the date represents the first day of the year, where (year mod 4) = 1, the result might be incorrect. This error has been fixed.

This changes corrects a problem where $ZF functions were calling out to external routines at the wrong privilege level.

This change corrects a situation where, in rare cases, the write daemon could hang if it attempted to start while license-related queries were being run.

This change corrects an ECP lock inconsistency during ECP recovery when ECP server restarted.

This corrects a problem that can occur when Caché is shutdown while a callin invocation is active. Control returns to the callin program, but not at the point where the callin was made. Further execution is unpredictable.

If the callin program was updating a global when the forced return was made, there is the added possibility of database corruption.