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\relnotes.htm and \relnotes\ensemble\relnotes.htm

This document provides a list of the changes between versions 2008.2.1 and 2008.2.2.

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 avoids problem with the IIS V7 Native Module Interface that prevented chunked CSP responses displaying correctly (that is, responses sent using HTTP chunked transfer).

This correction only applies to x64 platforms.

Also, this build strengthens the code that checks for systems management forms: if the PATH_TRANSLATED field for the request is empty then the Gateway will use the value of SCRIPT_NAME instead to determine the extension of the requested file.

This change corrects a problem in the code responsible for sizing the buffer requirements for configurations containing huge numbers of server and application path definitions. The issue could potentially result in UNIX and OpenVMS based Gateway installations not loading all the configurations listed in the CSP.ini file at start-up time. This, in turn, would result in applications not being able to access the resources that had failed to load (for example, access to particular Caché servers).

This change resolves a security problem that prevented the use of Shared Memory under Windows 2003 (and later).

The availability of shared memory is not critical to the Gateway and CSP can function normally without it. Shared memory is currently used as means for communicating between the Systems Management and Run-time module. For example, it is used to cache the security tokens used to protect access to the Gateway management forms for configurations where the administrator chooses to password-protect them. As a result, one visible consequence of an inability to access shared memory is the need to repeatedly log in to the Gateway management forms.

The Gateway, on failing to secure shared memory under Windows writes the following message to the Event Log:

cspSHMinit : Startup error 
Unable to create a handle to a shared memory block - code: 5 - Access is denied.

This change resolves a race condition caused by multiple frames accessing the Gateway data block responsible for registering state-transitions (preserve mode changes) against incoming sessions IDs.

The functionality responsible for managing the transmission (and caching of) response data between the Cache/CSP engine and the hosting web server has been redesigned in order to resolve occasional memory management issues when GZIP compression is used.

The new design greatly simplifies (without introducing any extra overhead) the management of memory and the relationship between the response streams and the Gateway cache. It also simplifies the processing of response data that must be locally cached for the purpose of generating a content length field for the HTTP headers.

A fault in the Apache API module which could occasionally result in a failure to dispatch HTTP response headers for which there was no following content has been corrected. This fault could affect HTTP redirect headers. A failure to dispatch the headers under these circumstances would typically occur when KeepAlive connectivity was in use.

This change corrects an issue that resulted in wildcard requests (*) for all CGI environment variables (as specified in the Gateway configuration) not being honoured by the CSPnsd module.

This change corrects a situation where updating a production could cause extra, duplicate alarms to be set in the scheduler for the production. Actively modified productions could accumulate many, many such alarms.

ScheduleSpec is to be specified in $ZDATETIME($H, 3) format; it can include wildcards ("*") for all fields and "WEEK" for year value.

ParseScheduleSpec looks at all the ScheduleSpec values, resolves the wildcards and returns the next closest event in absolute time. In ParseScheduleSpec, there is code that parses the ScheduleSpec looking for the special values and copies the non-special values to the output which is in $ZDATETIME format.

However, when the values in ScheduleSpec are malformed, it could cause the $ZDATETIME to be malformed. For example, "2008-11-04T*:00:00S" is such a value with an extra "S" at the end. This would yield a malformed $ZDATETIME value "2008-11-04T19:00:00S".

This change forces a normalization to numeric value of each field when constructing the output $ZDATETIME.

Before this change, the week-count value was not normalized. Now it is.

There was a circumstance where the attempt to identify dead jobs created ghost job nodes with increasingly long names that eventually led to generating a <SUBSCRIPT> error.

This has been corrected.

This change corrects an internal error where Ens.MonitorService:Purge was using the wrong global to search for jobs to terminate.

This change corrects a situation where the use of the WEEK syntax in scheduling events could cause a tight loop that wasted processor time.

This corrects issues in constructing reply messages that could cause an infinite loop while attempting to contruct a message reply.

This change fixes an <UNDEFINED> error in the code for HL7 and X12 'AckOut' Operations.

This change fixes an issue where EnsLib.HL7.Segment.OutputToIOStream causes the segment terminator characters that may optionally be appended to the pSeparators argument to appear in the MSH:2 field where the field separator characters should appear.

This change fixes an error with IN conditions used in the Message Browser search criteria. An empty IN condition would always be generated regardless of the user's specification.

This change corrects the segment references used in "leftoversegs" PathMap entries. Leftover segments are the remaining ones in an HL7 message after BuildMap() has parsed all the segments it can parse. Typically they are Z segments, but they can be any kind if the schema does not match the document.

The silent upgrade of an instance which does not have "Caché Engine" feature installed will no longer result in "dialogs out of order" error.

This change causes Caché to release its cached line tables when internal free memory is low.

This change causes Caché to examine successively higher-level cached routines to free when it is about to run out of memory in the routine cache.

This change corrects an error that could cause an <ACCVIO> when merging two arrays that had only integer subscripts.

This corrects a situation where $ZDATEH() could return an error when the date ended with a trailing space character.

If a routine has two or more references to a label that is within a dotted section of code or procedure block, all but the first reference would be compiled incorrectly, causing them to branch to an incorrect location in the code. This has been fixed.

To support ECP recovery the database server syncs its activities in the journal before the client can drop them. This change modifies ECP to not perform the synchronization when the request does not insert any journal entry.

In rare conditions in low load environments, the ECP client may delay flushing pending requests. This modifies the client to flush as soon as possible.

This change forces the ActiveX binding to use %Library.Decimal for numeric return values.

Before this change, CacheActiveX and the dynamic interface ofthe C++ binding projected %Numeric and %Decimal values as doubles. Now they are projected as decimal values, so the server and the client receive the data without any conversion.

This corrects a situation where an Export qualifier had an incorrect entry in its list which caused an error when used.

This change corrects a problem in which, when the Light C++ Binding stored an index entry for an index on a property of type %Timestamp, the month was 1 less than it should be (for example, it stored 0 instead of 1 for January). Timestamp values were (and continue to be) stored correctly in the data, it was only the index entries that were stored incorrectly.

This change fixes a problem in which Light C++ Binding failed to lock when checking for duplicates on a unique index, which could lead to incorrectly violating a unique index constraint if multiple threads near-simultaneously attempt to store objects with the same index value.

This change affects Light C++ Binding C++ code generation, so after upgrading to a version containing this change, any Light C++ Binding generated C++ code must be re-generated and recompiled.

This change makes the ReadLine() method of class %IO.StringStream work properly when more than one LineTerminator character is specified. That is, it should break the line at whichever terminator appears first, and if the terminators are CR/LF it should return them both as a single detected-terminator string.

Use of an XDEV in CacheSAX or CacheXSLT requires a callout to return a string representation of a pointer value. The printf specifier that was being used would truncate a pointer on a 64-bit system. This has been corrected.

This change notes the rebuild of the Xerces Libraries for x64 in 2008.2.

A correction has been made to the SQL privilege checking. Before this change, it was possible to CREATE, DROP, or ALTER an index even if you did not have %Alter_Table privileges.

A problem has been corrected where a DDL statement added a UNIQUE constraint or PRIMARY KEY constraint to a table with existing data, and the data for the constraint was not unique, an error was not returned.

This change corrects a problem with linked tables. If an application contained a query that was over 4000 characters long, an extra character would be added to the SQL that could result in an invalid statement and an <UNDEFINED> error at runtime.

This change corrects an SQLError that results when ODBC attempted to set up an environment header, if the connection has not been established.

This corrects an error caused by incorrect version checking in the Caché server. The error message that resulted was "class '%Studio.Debugger', method 'Attach': too many arguments". It is present in 2007.1 server when the maintenance version is higher then 5.

Under some circumstances, the current location shown by the debugger could be one line before the correct line. This is now corrected.

When searching for a routine to load, if any namespace is reconfigured, the unused namespace is released. Without this fix, an incorrect and freed namespace is associated with the current routine context. If the freed memory is reused for something else and if the routine namespace context is required for $TEXT or error trap, the consequences are unpredictable.

This change modifies the number of routines cached to be dependent on the amount of shared memory to be allocated per process. Prior to this, attempts to explicitly set the number of routines could result in <STORE> errors.

Previous changes to the viewbuffer message made the defined length of the viewbuffer too small, causing overwrite which corrupted the message queue pointers. Users might see <ACCVIO> in the message queues during view operations.

This has been corrected.

This change allocates the storage needed for monitoring or debugging a routine in the routine buffer itself.

A minor issue where the control process might have suspended the write daemon for 1 second after Backup.General.ExternalThaw() is executed has been resolved.

This situation could have occurred any time ExternalFreeze() was in force for more than 10 minutes. In this case, when ExternalThaw() is called there was a window while the write daemon was waking up where the control process does not see the extended time window set as part of ExternalFreeze() and tries to suspend the system. The write daemon starts running and the control process unfreezes the system one second later.

While this could have been seen on Windows or VMS systems, it was most likely to occur on a Unix system.

This change fixed a ExternalThaw() hang when the write daemon is suspended by ExternalFreeze() and no global buffers are available.

Previously, the ExternalThaw() would hang when it is started from a command line of a different Caché job from the job called ExternalFreee().

This change addresses an issue where the write image journal info was not kept up-to-date when journal files were being switched many times in a short period of time (for example, if the maximum size of a journal file was configured too small, and there was heavy journal activity).

If the system crashed during this time, the journal recovery at next startup may take a long time due to the outdated journal info.

This change corrects an issue that caused cluster journal restore to abort with an <UNDEFINED> error.