Compatibility is the capacity for two systems to work together without having to be altered to do so.
Documentation (http://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls…) states that it looks like:
IRIS for Windows (x86-64) 2018.1 (Build 487U) Tue Dec 26 2017 22:47:10 EST
Does it really true, or just a documentation typo?
I have one in my testing environment. According to https://community.intersystems.com/post/licensing-ubuntu-and-suse-20171-and-later, I should move to native Ubuntu build with 2017.2. So I downloaded Cache for UNIX (Ubuntu Server LTS for x86-64) 2017.2.1 and tried to update my existing 2015.1.4 installation. What I got was:
Upgrade from lnxsusex64 platform is not allowed.
No packages will be installed.
Meanwhile new Cache 2017.2 instance was installed without any problem.
The question is: how to upgrade an existing one?
I'm having trouble with a vb6 application attempting to connect to a Cache 2017 release. It uses the older Cacheobject.dll instead of ActiveX. The application currently works with a 2010 release of Cache. Is Cacheobject.dll supported in later releases?
I looked through documentation and posts and did not find an answer.
Thanks in advance for any response.
I was wondering if there was a way to if the user is using Studio and changes a file to get the users name and have a function run when the file is changed.
Ive got this working for .int files but not for .csp or .js or .css or any other kinds of files.
When we edit code we are logged in to the Cache backend’s server through Studio by using an iPaddress (which is on our network).
I know now there are concepts of file locks and logs for when certain tasks are ran or when a user maybe edits a file
When I open a BPL in Atelier and right click 'Open diagram editor' I get a Java Incompatible browser error message (see below).
I'm using Windows 8.1, Atelier 1.0.190 and IE 11.
All the M.S. updates are up to date.
I also have firefox and chrome installed.
Trying to change default browsers etc. did not work.
As Bill has mentioned earlier in his post, we have carefully reviewed the JSON capabilities and made some adjustments to ensure they deliver the best benefit to you. In this post, I am going to describe the modifications in more detail and provide guidance for you to understand the implication for your code base.
As we've all heard 2016.2 draws near and brings the removal of system methods with it.
There are two ways to make the code compatible with 2016.2:
The last version of Caché, Ensemble released for VSI OpenVMS is 2017.1. Unlike HP OpenVMS (Alpha and Itanium), VSI OpenVMS on Itanium continues to be supported. This means that critical corrections or changes required to support customer’s hardware purchases will all be based on 2017.1 or earlier versions.
Related announcement: https://community.intersystems.com/post/platform-compatibility-hp-open-…
Starting sometime at the end of last week your posts like
http://blog.intersystems.com/compatibility/2015/03/24/supported-platfor…
and others have been receiving a number of spam comments.
The class %Compiler.UDL.TextServices arrived in 2015.1, bringing us methods for exporting a class in UDL format (i.e. looking just like we're used to seeing it in Studio), and importing a UDL format definition back into a namespace. Some source control tools including our Deltanji are now able to use UDL format, resulting in diffs that are easier to understand.
This announcement is to inform clients about changes in our 2016.2 and 2016.3 field test programs.
The 2016.2 field test has been extended in order to address important syntax changes related to JSON. Simply stated, the JSON syntax introduced in 2016.1 had several inconsistencies that we did not want to perpetuate. This is now addressed and the updated 2016.2 field test will be published today. Concurrently, the syntax changes and guidance for developers will be posted on the Developer Community shortly. JSON is critically important to our Caché roadmap.
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.
Hi All,
I have SourceControl utility class as in sys namespace
Class %MW.Web Extends %CSP.Page {... }Previously with Cache 2010.1 and below there was no problem accessing it through
localhost:57772:/csp/myns/%MW.Web.cls
But now with newer version at least with 2016.2 I' ll get Forbidden message from it.
With Web Gateway HTTP Trace Facility
GET /csp/ipanax2/%MW.Web.cls HTTP/1.1 --> HTTP/1.1 403 Forbidden
How can we make it accessible again?
Mikko
Hi -
When upgrading a Health Connect deployment from 2014 to 2016 do I HAVE to recompile? or is the "just upgrading" enough?
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.
We are finally planning to migrate some ancient Caché applications that are run on Caché 5.0.21 to a new server with Caché 2016.2.0 or so.
I wonder if we could use Shadowing between those to keep the data on the new server up to date?
We would copy the Caché backup from the old environment to the new and do a RESTORE there and then start shadowing.
I know than 5.0.21 is no more officially supported by ISC.
Caché 2016.1 introduced some very powerful JSON features. Unfortunately, the syntax used in the 2016.1 release is going to be changed in the 2016.2 release to bring it closer to Caché ObjectScript syntax. This will mean that code that works in 2016.1 may not be forwards compatible. See this announcement and this article for more details about the changes.
Windows 7 and some other Microsoft Operating Systems can shutdown too fast for large applications, such as a Cache instance with a large amount of data and changes, to close gracefully. This results in the instance being forced down by the OS and so causing problems on the next start up.
To solve this we can change the OS shutdown timeout values to give Cache more time to close gracefully. We do this by editing some settings in the Registry.
1.Click Start (on Win 7) and type “regedit” and make sure you run registry editor as administrator.