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 file: \relnotes\cache\relnotes.htm

This document provides a list of the changes between Caché 2007.1.4 and Caché 2007.1.5.

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 evaulating 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

Windows installation will detect when it is running on a Windows 2008 or later cluster and install and register cluster resources.

In rare conditions, ECP recovery may hang if there is an ECP server or network outage during a long string SET.

This change adjusts the ECP application server heartbeat interval to detect an idle system network outage more accurately. A large number of async packets originated by the database server may prevent it from sending heartbeats. Decreased the app-server heartbeat interval to keep the db-server pending heartbeat count more accurate.

In a very rare condition during the ECP server recovery window, if the database server failed and if the remote databases were not mounted in the same order as at startup, then ECP synchronous requests (that is, $DATA, $GET, $INCREMENT) that were being formulated at the time of the database server failure might have referred to the incorrect database number. This has been corrected.

Consequences of an incorrect database number vary (in part depending on the Caché release): the ECP daemon may crash or the request may not be directed to the correct database. In the latter case, unexpected application errors may result or (in rarer cases) incorrect data may be fetched.

This change fixes an error when using the expression $DATA(global, target) over ECP when the data in the global has Unicode characters in it. Without this fix, the value of <target> could be set to an invalid string.

Prior to this fix, if a string in excess of approximately 64Kbytes were modified by the application server while the block which will contain the string was being sent to the same client as a consequence of an earlier request, the app server and database server would end up with different versions of that block.

An incorrect permission issue prevented a Cache Terminal console login from writing messages to cconsole.log on Windows Server 2008. The problem was caused by a change in the default ACL on the \intersystems\cachesys\mgr\cconsole.log file on Windows Server 2008. This is now fixed.

When running Studio in a Japanese locale, when a class is compiled the output window may go into a recursive loop resizing slightly, which causes continuous repaints. This change corrects this.

This change corrects an issue where a function such as $SYSTEM.Encryption.Base64Decode, when it returned a long string, could cause a memory access violation.

When the output of Base64Decode was longer than 32K characters, the length of an internal buffer was sometimes erroneously calculated leading to a potential buffer overrun.

This change corrects an issue where cstat displayed pointers as eight hexadecimal digits. This showed only the lower-half of the 64-bit pointer value. Cstat now displays the full pointer value.

This change addresses an issue with running an error trap after a <STORE> error. In some situations, the trap routine was not loaded correctly, resulting in a memory access violation.

This change corrects an issue that could have arisen when there was a small amount of memory available in the partition and an exclusive NEW command was issued. In that situation, there was a possibility for the memory queue to become corrupt, resulting in a CPU loop or an access violation at some later point.

This change fixes a problem in the algorithm that counts the number of CPUs and cores on Solaris. In particular, when running on some Sun Fire T1000 and T2000 configurations, counting an incorrect number of cores could result in license restrictions.

This change fixes a problem in the UnicodeLittle and UnicodeBig NLS translations that, when used with fixed length READs in TCP devices, could lead to some bytes being dropped in the connection if the translation type were changed on the fly between different records.

This change corrects a problem with reloading stack registers after certain types of function calls involving OREFs. Because of this Caché could halt under seemingly random circumstances.

This change corrects an error in comparing floating-point values. In certain rare circumstances, the comparison of different types would not first convert them to a common type.

A problem was resolved on UNIX systems where CacheTemp fills the disk and subsequently space is made available so that the delayed writes can complete.

If Caché became idle for 5 minutes or more, the control process might incorrectly decide that the write daemon was stuck because the internal counts of how many blocks needed to be written had gotten out of sync with the number of blocks which actually needed to be written.

A longstanding error affecting AlphaVMS and Alpha/Tru64 platforms has been resolved.

The issue involved an internal stack discipline problem which, under rare circumstances, could cause problems such as spurious <STRINGSTACK> errors in extrinsic function calls, or seemingly random access violations.

A problem has been resolved on 64-bit Windows machines where loading a large number of XML files sometimes caused an exception resulting in the closure of the terminal window.

This change corrects an issue in the CacheHung.sh script, which displays different cstat options based on the Cach%eacute; version number. The script did not properly recognize the year-based release naming format.

A problem has been corrected that prevented creating the permitted number of databases with an Entree license.

The built-in databases of an Ensemble installation are no longer counted as part of the database limit for E2 (Entree) and E4 (Elite) license keys.

Databases that implement the Ensemble product are no longer counted toward the database limit imposed by E2 and E4 Ensemble licenses.

The function, $SYSTEM.Security.AddRoles() can no longer be called from the command line, or from within the debugger. Doing so could allow a user to inadvertently leave their process with elevated roles when the call returns. Calling the method in this way will fail to elevate the roles, and the error

ERROR #940: Insufficient privilege for operation

will be returned as the value of the function.

The counter for Routine Cache Misses has been added to the mgstat monitor utility.