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

If your database or application servers hold local transaction information until the transactions are completed, or 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 resolves a bad pointer reference in the function responsible for destroying mutex objects. The problem corrected would have disproportionately affected state-aware sessions since these use mutex locks to implement request serialization.

Windows installation was trying to apply the WIJ (Write Image Journal) before Caché was stopped. As a result, the WIJ was not applied and installation could fail when a custom WIJ directory was used in the original instance.

This change corrects a problem where the subscript of an array may be become corrupted. The circumstances are rare and involve the encoded form of the subscript being of a different type than the unencoded form, as well as having the subscript be killed and then re-inserted.

This change corrects a problem that could cause an overflow on the string stack when fetching Unicode strings over ECP where the server and client differ in their endianness.

Belgian and other foreign locales use "," as a decimal separator, which causes problems when sending parameters to Caché requiring "." as a decimal separator. This is now fixed.

Previously a user could subvert the $SYSTEM.Security.AddRoles() mechanism and gain access to unauthorized roles at the programmer prompt. This has been fixed by this correction. We now disallow adding roles when a ZINSERT has been made into the user's routine call stack.

The Caché kernel contained internal implementations of the functions MD5Init(), MD5Update(), and MD5Final(). The InterSystems function MD5Final() had a signature (argument list) that did not match that of the reference implementation in RFC 1321.

Solaris includes implementations of MD5Init(), MD5Update(), and MD5Final() that do match the reference implementation. Solaris system functions use these functions internally.

In the Caché kernel, these references resolved to our implementations rather than to the Solaris ones, resulting in an argument stack mis-match.

This has now been corrected.

If a multiply operator near the start of a TRY block results in a <MAXNUMBER> error, the error may not be caught by the CATCH block on a 64-bit platform. This is now correctly handled.

This change fixes a problem in $ZCVT(string,"I","HTML") that could cause either a <TRANSLATE> error or a crash, depending on the platform and on other circumstances. The problem happened when the source string ended on a numeric entity without the terminating ";" (e.g. "&#160") but the memory position immediately after it did contain a garbage byte with ";". The problem affected not only $ZCVT() but also HTML translations done during device input.

In locales based on character set CP1252, two characters had the wrong pattern match attributes.

The fixed behavior is:

$C(215) ?1P (multiplication sign)
$C(223) ?A and ?1L (small letter sharp S)

This change fixes a potential buffer overflow that could happen in rare circumstances when outputting strings with non-ASCII characters to TCP devices using the UTFJS (UTF-8/JavaScript) translation.

This change corrects the unnecessary creation of a file in single-user mode on OpenVMS.

There are at least four related cases of startup hangs. In all cases, one of two daemons was found to be absent (that is, had become <defunct>) when startup hung.

This change corrects a situation where the daemons are exiting prematurely in the control process daemon creation sequence, because they are the two that attempt to obtain a lock on the <instance>/bin/clock file.

In 2010.1, a callout to a utility (for example, Novell Mono) which passes an invalid command can result in a hang of the child process, and consequently the Caché session to hang.

Now this will be detected and the user given an opportunity to abort the child process.

Under certain circumstances the %SYSTEM.License:ProcessList query could encounter an exception, in particular if it is run while a process is running that was started with the emergency diagnostic login argument (-B).

This change resolves a problem where a mirror member may fail to become either the primary or the backup because it has purged some journal files before it had a chance to verify that they contained valid ends. The validation code has been enhanced so that the instance understands that validation of those files is no longer required.

If the rollback journal file did not have the transaction processing rollback point recorded in its header, it logged a message in cconsole.log with the wrong variable name. This is now fixed.

After the backup node has shut down and then restarted, the backup node might fall behind the primary when there are lots of journal records within the same mirror journal file (current journal file). This may cause the backup node to take so much time finding the end of the journal file that it could cause the mirror connection to time out. As a result the backup could not connect to the primary until the primary did a journal switch.

This condition has been fixed.

This change corrects a problem where an unexpected error in the system monitor caused a cascade of other spurious errors.

The multiSelectSet widget had a defect in its initialization code that could manifest itself if the widget was being dynamically created or updated from the server side.

The widget would behave fine for an initial value that was a singular value but would fail to properly check off options if its initial value is a comma-separated string of values. This resulted in visual artifacts where the value of widget on record was not properly reflected on the display and was highly undesirable.

This change traps and corrects this condition, ensuring that the rendering of the value and the internal representation of the value remain in sync regardless of how and when the widget was created.

© 2011, InterSystems Corporation. All rights reserved.