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 corrects a situation where Ensemble startup and shutdown could produce extraneous messages in the console log.

Prior to this change, the event log processing which occurred during the OnKeepAlive() callback in Ens.Enterprise.MsgBankOperation was not in any way throttled. The code did handle situations where no events had ever been banked, but in those cases where some events had been banked in the past and a large number of events had been banked in the interim, the code could attempt to send very large amounts of data to the message bank. With this change, Ensemble will now attempt to process at most 10,000 events during each call to OnKeepAlive().

Should users not wish to bank any events prior to the current time, they should disable the Message Bank Operation components and then kill the ^Ens.MsgBank("LastEvtId") global node to get the client code to start banking events starting from the current time.

This change adds a new IsProductionRunning classmethod to the Ens.Director class. The new method is not a foolproof indicator of whether the current production is running, as it does not lock $$$EnsRuntime and thus may not detect situations where a production is changing state. However, it will return a reasonably reliable indicator of whether the production is running without introducing any lock contention on the $$$EnsRuntime global as is present in the more reliable GetProductionStatus() method of Ens.Director.

GetProductionStatus() is still the most reliable indicator of the current production status.

Stop productions properly when Caché is shutting down, namely:

1. When Caché shuts down, it stops productions in various namespaces concurrently.
2. Stop production with timeout specified in production configuration.
3. Call Stop with force=1

This change adds a Reset() method to class %IO.IParts.MetaIO. This allows a stream object of this type to be re-used with multiple output streams without building an ever-increasing list of output streams. Instead, the object can now be re-initialized using the Reset() method before a new output stream is added. (The same also applies to CopyInput streams.)

The logic to ensure that the entire file was downloaded when ConfirmComplete is set to "Size" was flawed and could previously result in incomplete files being downloaded from the FTP server. Furthermore, it was also possible that the adapter would not wait long enough to ensure that the file size was no longer changing before determining that it should be processed.

Both of these problems have now been corrected. However, this may lead to slower processing if ConfirmComplete is set to "Size", as the code will wait at least as long as the FileAccessTimeout to ensure that the file size hasn't changed.

In previous releases of Ensemble, SOAP services were not correctly determining whether the production was currently running, and could attempt to start the service while the production was troubled.

Furthermore, the SOAP service was not checking whether the related business service had been disabled, and could thus be incorrectly invoked when the configuration item had been marked as disabled.

This change corrects both these issues.

DICOM now handles 'UT' data type

This change updates the Abstract Syntax Dictionary which was out of date.

This change fixes the AllowedIPAddresses feature of the TCP Inbound Adapter its hostname resolution sub-feature. This change also adds hostname resolution to the !-IPAddress feature of the TCP Outbound Adapter, supporting a list of allowed remote connection addresses that can be numeric or named.

This change fixes the class EnsLib.HL7.Operation.SOAPOperation to avoid building an ever-increasing list of MetaStream output streams.

When a merge command is executed, there is a chance that subsequent kill operations on a single subscript in the updated array would kill the entire array instead of just the intended single subscript.

This change corrects that.

This change fixes problems with ptrie local arrays. The symptoms are that Caché will gives a <SYSTEM> abort or a segmentation violation. This usually happens when the application is killing an array or executing a $O on an array.

In very rare cases, when a long string cannot be compacted, and the global is subscript mapped, and the global value is accessed using 2 argument $DATA (to get the value during the operation), the server returned value might be corrupted. ghis is now fixed.

In rare conditions, when an ECP request set is partially processed before the server is shutdown or fails, and then the server is restarted, some app-server's session might be rejected and not recovered. This change correct that situation.

This change fixes a rare situation where reverse $ORDER is being pre-fetched by the worker daemon while the previous block is being modified by the ECP daemon; this may cause a deadlock condition and hang the ECP dmn and possibly the system.

After issuing $ZU(11,2), a subsequent GOTO to an entry point with a formal parameter list could get an access violation.

A problem has been corrected where a deferred SQL statement that included a host variable reference of the form oref.prop was not having the proper code generated for it.

This change corrects a rare error that can occur when trying to fetch the privileges on a table using ODBC.

The change corrects a situation where operations that save and restore the internal symbol table used by Weblink Developer might overlay memory and cause access violations in the process.

This change fixes a problem where, after a FileCompaction on a 9GB file, a second FileCompaction gives a <DATABASE> error, and INTEGRIT shows a node pointer to an incorrect block.

A job command using jobservers will sometimes hang and time out. A dump analysis shows the two processes (parent and child) both waiting in the job putsym and getsym (symbol passing) code. This change prevents that deadlock situation.

Repeated use of $VIEW(-1, pid) causes process to hang. This is now corrected.

A $ZF(-1) function that succeeds in a terminal environment hangs in a Web environment. This has been corrected.

This corrects a situation where a cluster recovery could take an unusually long time if run while the cluster was, in fact, operational.

This change addresses an issue that could cause TROLLBACK to fail with the (false) error "journaling is disabled" in certain rare circumstance involving an ongoing journal switch.

This change fixed a possible stale SLM mapping when the destination database location is updated in CPF file before Caché starts. This also fixed an issue with renaming the database name in configuration that does not update the database location in global/routine/package mapping.

© 2011, InterSystems Corporation. All rights reserved.