InterSystems has performed various system and application benchmarks to determine the potential performance impact after the corrections for Meltdown have been applied.
Project related quality assurance efforts have revealed a number of concerns for the current release of 2017.1.0 and 2017.1.1 on all OpenVMS platforms. In certain situations, the impact can be severe.
We are in the process of using Ensemble for HL7 translations, and wanted to know is it better to use it on Linux Server or Windows Server? We are mostly a Windows shop but just wanted to make sure there is nothing we will be missing out using the Windows application.
Beginning with the next release after 2017.1, InterSystems products will no longer be offered on macOS (OS X) as a Server platform. This platform has been re-classified and will be available as a Development platform in future releases.
Products: Caché, Ensemble
Expected Availability: next major release after 2017.1
Starting with 2017.1, InterSystems is adding Ubuntu (64-bit) as a third linux server platform. Prior to 2017.1 Ubuntu was already available as a development platform and customers could use InterSystems distributions build for SUSE to run on Ubuntu. As a result there are a few license key implications for 64-bit linux versions starting with Caché and Ensemble 2017.1:
a) Customers using RedHat will observe no changes
b) Customers using InterSystems products(1) for SUSE on SUSE will need new license keys (no charge)
Starting with 2017.1, InterSystems has moved macOS from being a server platform to a development platform. 2017.1 will only support macOS 10.12 and will no longer be available as dmg kits.
Verification of macOS 10.12 has not been completed at this time and Field Test kits for this platform are not yet available.
I am pleased to announce the next 2016.2 field test kit, 2016.2.0.605.0.
There are about a hundred changes from the previous field test kit, including the following fixes to problems found by those using the kits in the field:
Is there a recommended way to deal with the unattended reboot that happens when Windows Updates are applied? These reboots cause issues with running Ensemble produtions.
What are the best steps for troubleshooting printing to a Windows printer from Cache. The printer has been configured in the Windows Printer Manager and has been able to print a test page (from the windows print manager).
The device has been configured in Cache -> Sys Admin -> Config -> Device Settings -> Devices with properly formatted |PRN|printer device name and "W" for open parameters and 101 for Alias.
By date