InterSystems supports use of the InterSystems IRIS Docker images it provides on Linux only. Rather than executing containers as native processes, as on Linux platforms, Docker for Windows creates a Linux VM running under Hyper-V, the Windows virtualizer, to host containers. These additional layers add complexity that prevents InterSystems from supporting Docker for Windows at this time.

This time I want to talk about something not specific to InterSystems IRIS, but that I think is important if you want to work with Docker and your server at work is a PC or laptop with Windows 10 Pro or Enterprise.

As you likely know, containers technology comes basically from Linux world and, nowadays, is on Linux hosts were it shows maximum potential. Those who use Windows on a normal basis see that both, Microsoft and Docker, have done important efforts during these last years that allow us to run containers based on Linux images on our Windows system in a really easy way... but it's something not supported for production systems and, this is the big problem, is not reliable if we want to keep persistent data outside of containers, in the host system,... mostly due to the big differences between Windows and Linux file systems. In the end, Docker for Windows itself uses a small linux virtual machine (MobiLinux) to run the containers... it does it transparently for the windows user... and it works perfectly well if, as I said, you don't require that your databases survive longer than the container...

Well,...let's get to the point,... the point is that many times, to avoid issues and simplify, we need a full Linux system and, if our server is based on Windows, the only way of having it is through a virtual machine. At least till WSL2 in Windows is released, but that will be another story and sure it'll take a bit of time to become robust enough.

In this article, I'll tell you, step by step, how to install an environment where you'll be able to work, if you need it, with Docker containers on an Ubuntu system in your Windows server. Let's go...

It's possible to enable Ctrl+C / Ctrl+V in IRIS Terminal for Windows.

To do that, open Terminal and select Edit > User Settings and enable Windows edit accelerators. This setting specifies whether the Terminal enables the common Windows edit shortcuts (Ctrl+C, Ctrl+V, Ctrl+Shift+V), in addition to the basic Terminal edit shortcuts (Ctrl+Insert and Shift+Insert).

After that Ctrl+C / Ctrl+V would work.

Also <SYNTAX> errors after incorrect copy/paste go away.

Docs.

When my COS code is executing in a Caché process it might want to interact with the host operating system. For the purpose of this post I'm focusing on a Windows host, but much of it applies to other host OS platforms as well.

A common example of host OS interaction is when my process wants to read from or write to a file. What credentials will apply when Windows is checking whether or not to allow me access to the file?

To answer that we need to consider another question. How did our process start?

I recently helped a site investigate a problem that appeared after they upgraded their Windows instance of Caché from 2015.1 to 2017.1. A terminal session launched from the server's desktop cube was unable to run OS-level commands using the $ZF(-1) function. For instance, using the no-op command "REM" as follows:

write $zf(-1,"rem")

was returning -1, indicating that the Windows command could not be issued.

On a developer's laptop, having had two or three Ensemble installs with different settings/config changes made, and encountering unexplained errors compiling classes, wanting to scrub as much of the previous installs off the machine before doing any fresh installation... But can't find clear documentation on doing a complete uninstall!

Have stopped the server.

Am I safe to remove C:\InterSystems\Ensemble (for the instance installed into that folder)?

Does anybody else have problems installing the Caché 2017.1 FT for Win_x64?

I'm getting an error "Unable to execute the required file: The following system error has occurred: The system cannot find the file specified. (2)"

This is happening with the very latest version (build 726) and the previous one ( build 720), whereas the builds before were fine.

I've uninstalled Caché to see whether it was an upgrade vs clean install problem but it makes no difference.

Now that the InterSystems IRIS Data Platform Community Edition is available on Docker Hub (https://hub.docker.com/_/intersystems-iris-data-platform), it seems like a great time to try InterSystems IRIS in a container.

This 'feature' have been around for a long time, but I don't see any articles on it so I thought I would make everyone aware.

what happened is, I selected a user to investigate their entries. I didn't enter a start date.

After hitting search, the query timed out, (or i cancelled it, I don't recall).

Now, when I go to that page, the browser processes and nothing is displayed.

I cleared my browser's cache, and I still get a blank page.

I'm running on Win10.

I use Chrome as my default browser. The problem also happens in Fire Fox.

i can log in as a different user and the page displays as expected.

How can I correct this situation?

Thanks!

In Cache for Windows (x86-64) 2018.1.3 (Build 414U) I found something very useful

I want to connect to my local terminal via Eclipse in Windows. I am able to connect to the server but not my own machine. It opens from "cube icon" -> Terminal but I want to open and connect to it in Eclipse.

How should I connect to it?

I am using the free Intersystems Cache installation (CachePCkit V2017.1) on Windows 10 for my own use & personal development.
I am writing routines in Studio & running them in the Cache terminal TRM:3672 (TRYCACHE).
From a routine, how do I control print position within the terminal screen. I have tried using $X and $Y but this does not work and I cannot find what I need within the Cache terminal documentation.

Hope this question is not too simplistic for Members.
Any suggestion would be appreciated.

Greetings.

I'm currently struggling with launching a routine from the command prompt using ccontrol.

Basically I have a routine with a parameter which works fine using the following:
ccontrol cterminal ^ANDYTST(\"c:\temp\\\") USER