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.

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.

• Phone:  +1  617  621-0700
• Fax:  +1  617  734-9391
• Email:  support@intersystems.com

A new operation class EnsLib.DICOM.Operation.TCP.Storage has been developed which performs a single storage operation within the context of a single association. It eschews flexibility for simplicity.

The Demo.DICOM.Production.Router, Demo.DICOM.Process.RouterDispatcher, and Demo.DICOM.Process.RouterFiler classes provide a simple demonstration of a receive, dispatch and file storage scenario. The demo is intended to present the simplest possible implementation of such a scenario and is designed to be a model for the user to copy or extend.

Based on available information, there are few/no applications using CacheActiveX with multiple threads, so most applications will not run any differently. Those applications that do use multiple threads must already have the proxy objects isolated to a specific thread (otherwise they would see the problem that this change fixes).

• ECP now implements versioning to help in implementing the ECP cluster server rolling upgrade support. By use of versioning, the ECP session will be dropped if an older/incompatible version takes over.
• ECP recovery uses the ECP session version of the old primary during mirror failover. The approach is that during failover, if the ECP session of the new primary is older than the previous primary, do not recovery the ECP sessions.
• When a failover mirror member downloads ECP session data from the existing/former primary, it now also retrieves a version number. If a node becomes the primary and the existing ECP sessions have an incompatible version number, they are dropped. A version with this change is required in order to correctly inter-operate with 2011.1 (and later) releases.

While the operating system was terminating processes, it was possible for the backup to enter its failover state and make contact with the agent on the primary. Shortly thereafter, the agent process would get terminated by the system. In this case the backup mistakenly thought the primary told it that it was down. The backup could continue and take over for the primary if this occured within the trouble timeout.

However if the write daemon on the former primary was not terminated by the system within the trouble timeout period, it could update its copy of the mirrored databases with a journal position past the last point the backup had retrieved. The consequence of this is that the next time the primary is started, it will refuse to join the mirror because it will detect the inconsistency.