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 change modifies the control block to align data items so that references to them do not cause bus errors on 64-bit systems.

This corrects a serious situation that occurs during shutdown. At this time, all outstanding alarm requests are lost. On subsequent startup and resumption of the production, the processes that are waiting on their alarm requests will not receive them.

The change is to save the alarms, preserving them across the shutdown/startup and make them available to the applications when they resume operation.

This change causes the class EnsLib.SQL.GatewayResultSet used by the SQL Adapters to write only complete LOB chunks to the underlying stream global rather than storing each sub-chunk as it arrives over the xDBC channel. This prevents journaling of the partially completed chunk multiple times which reduces the total amount of journaled data to the minimum necessary.

This change increases the TOP clause in the SQL used to purge messages from 1,000,000 to 100,000,000.

When the JDBC Gateway's JVM is restarted while a Production is running and SQL Adapter activity is in progress, it can happen that the Adapter has an open connection instance that is no longer viable. In this case, when the Adapter attempts to prepare a statement, the prepareStatement() command to the JVM will fail. The adapter needs to interpret this as a disconnect event so that it will jettison its connection instance and establish a new one.

This change makes the Adapter detect the failure and interpret it as a disconnect event.

This changes adds support for versioning of CPA instances. CPA instances are now stored using an IDKEY of the CPAId and the Version property. A new instance method BumpVersion() will find the next highest Version number for the specified CPAId. CPA instances can also be "disabled" by setting the new Status property to disabled. A new helper method has been added:

    CPAForCPAId(<cpaid>)

This will locate the CPA instance by CPAId and find the highest version that is marked as active.

Some external situations require that additional XML tags be present in the ebXML Manifest, in this specific case, it is a Payload tag. The existing implementation allowed for this, but would capture the XML as a string in an "any" property. However, this turns out to be useless because the original namespace information was included in the SOAP envelope and unavailable to the user.

This change captures the Payload tag properly.

This change modifies the TimeToLive property of the CPA so it is treated as a string, in an XSD duration format.

Not all users will track messages or associate a deferred response with a message in the message tracker. In this case, where tracking is needed, but responses are not pre-fetched, this modification ensures that Ensemble does not call SendDeferredResponse() unnecessarily.

Some DICOM client software sends empty instances of DICOM transfer syntax specification in the association negotiation phase. While this is confusing, it is not specifically prohibited in the standard. This correction changes the TCP adapter to just ignore the irrelevant data.

The "time created" timestamp was needed for auditing purposes, which was in fact present in the implementation, but wasn't visible to DTL. This change makes it visible.

This corrects a situation where $ORDER or $QUERY would return incorrect results under certain boundary conditions, for example, finding the first item in a newly created local array.

This correction fixes an error where a class load or save across ECP may raise an unexpected error (<ROUTINELOAD> or <STORE>), when the routine object global cache is empty and the load/save references a routine > 32656 chars.

This change redefines /checkuptodate qualifier in Export group to make it compatible with that of the Compiler group, but still accepts the older values of 0 and 1.

This change fixes two problems with the the projection class for the Cache %Time datatype in the C++ binding and Light C++ Binding.

The first problem was that d_time::operator!=(const d_time&) always returned true. The second problem (in Light C++ Binding only) was that it stored d_time in a different format ("hh:mm:ss") from the format used by SQL and other object APIs (which store time as a string representation of the number of seconds elapsed since midnite).

Thus, times stored by LCB could not be correctly read by SQL, and vice-versa. With this change, times are stored in the same format used by SQL, and can correctly read times that were stored in either format.

This change causes MDS to correctly ignore object fields which are defined as interfaces, and do not have any actual type specified. Prior to this change, MDS got an access violation within MDSNodeReference.setTypeInfo if called for a class containing such a field.

The Remote Gateway has a Closed flag that indicates whether its TCP connection to the JVM is open or not. This change ensures that, in disconnecting or failing to connect the Gateway when the connection is unexpectedly lost, the Closed flag is correctly updated.

The SELECTMODE parameter can now be specified for class queries of type %Library.Query. For these queries, SELECTMODE is declarative and it is the responsibility of the query author to properly format the column values according to the SELECTMODE parameter setting. If that setting is RUNTIME, then the current runtime SELECTMODE can be retrieved from $system.SQL.GetSelectMode().

The default value for SELECTMODE for queries of type %Library.Query is LOGICAL. If existing queries are having problems with client software and data formats then the existing query might have to be updated to specify a different SELECTMODE value so that the values as formatted by the query are properly recognized.

This change avoids a situation where an attempt to restart the JDBC Gateway could result in a <SUBSCRIPT> being generated.

This change fixes two problems with the d_time class (the projection class for the Cache %Time datatype) in C++ binding and Light C++ Binding. The first problem was that d_time::operator!=(const d_time&) always returned true. The second problem (in Light C++ Binding only) was that Light C++ Binding stored d_time in a different format (a string in "hh:mm:ss" format) from the format used by SQL and other object APIs (which store time as a string representation of the number of seconds elapsed since midnite). Therefore, times stored by LCB could not be correctly read by SQL, and vice-versa. With this change, LCB now stores times in the same format used by SQL, and can correctly read times that were stored in either format.

This change makes the SQL Adapter JDBC LOB logic ignore $C(0) (Ascii NUL) if it appears as the sole content of a block of data that is not the first block. This works around an error in the lower levels of the JDBC Gateway that causes such a NUL character to be returned if there is no more data after retrieving a full chunk.

This change corrects a situation in SQLServer on 64-bit Windows where different code pages could be used for character translations by the kernel and the ODBC driver resulting in "?" being displayed for unrecogniized characters.

The change causes the regional setting defined as the code page for character trranslations.

This change modifies the Studio client to support loading package information by explicitly specifying the package name when using %Dictionary.PackagDefinition.

This change corrects a memory leak that occurred when importing a large number of files in one operation.

When using private variables within a procedure, a <SUBSCRIPT> or <UNDEFINED> error could be reported as <WIDE CHAR> or could show an incorrect variable name in the error text.

This situation is now corrected.

This change modifies Caché to load the routine and object components in batch mode; after being loaded they are cached in routine buffers and not used again. It also modifies Caché to release the retained buffers after loading a routine.

This modification fixes a problem that could cause an access violation on 64-bit Windows if an application tried to submit a string with surrogate pairs for output translation with a table that does not support this feature (for example, JIS instead of JIS2004).

This change causes the clean daemon to free gfowner resource properly. Previously, the resource was not properly returned.

SIGUSR2 appears blocked on DECUNIX clusters. This change restores its functionality.

This change corrects a timing issue which prevents a single kill command from killing both ISCAgent processes on HP-UX when sent a SIGTERM. The remaining process was preventing the ISCAgent from being upgraded.

This change corrects several known problems that occurred if the backup ran out of space to store a journal file from the primary system.

When the system is configured to do so, mirroring generates the following email level alerts (severe log messages) for:

1. a node becomes the primary
   (in the future this could be modified to exclude situations where the backup becomes the primary after the primary is shut down gracefully, but for now Caché generates an alert any time a node becomes the primary.)
2. backup disconnects from primary and fails to either become the primary or reconnect as a backup
3. system starts up and fails to become the primary or a backup. This includes async members which fail to connect to the primary at startup.

In addition there are less severe cconsole messages for:

• backup disconnects (warning)
• backup connects (info)
• backup demoted from active (warning)
• backup promoted to active (info)

A problem has been resolved where a backup might fail to take over when agent contact required is set to no and the mirror is idle at the time of the failover.

This change fixes a situation where when the backup node has been down more than 14 days, the primary node might purge the journal files needed by the backup node to catchup.

This change corrects a problem in adding and deleting VIP scripts on SunOS where the check for running as root was improperly done.

When modifying the LockSharedMemory or LockTextSegment parameters in the management portal and setting the value to True, the values written to the memlock= parameter in the CPF file were incorrect. This could cause the memory to not be locked upon a subsequent restart of the system. This has been corrected.

© 2010, InterSystems Corporation. All rights reserved.