I made such an example years ago, you can look at GitHub. This example maybe not so correct by this time, but can be useful. When you have to run only ECP clients, it becomes a bit easier. You should not care about volumes, in most cases, all the data stored in ECP-client is temporal. So, you mostly should care only about buffers. In my example, you can find how to configure instance during docker build to work as ECP-client.

Well, now a few questions.

Does it mean that any new requested features will be declined to implement?

Any possibility to implement new features by own?

How about the future of Atelier API?

If InterSystems not going to extend Atelier anymore, maybe it's time to open sources Atelier or at least Atelier API.

Currently, it sounds like Atelier will get the same future as Studio, it means no future. Or am I wrong?

In addition to other answers, if want to operate with bits, you can use functions:

  • $zhex - converts integer to hex and vice versa, be careful with type of variables. If you pass string it will convert from hex to dec, if you will pass integer it will convert from dec to hex.
  • $factor - converts integer to a $bit string
  • $bit (with bunch of $bit* functions) - operates with bitstrings.
  • You may possible need some encryption functions, you can find
  • And possible zlib, $system.Util.Compress and $system.Util.Decompress from class %SYSTEM.Util 

If you are going to work with H.264, I would not recommend to try to implement it in COS, it will not be fast enough. I'm not very know with this technology but I'm sure I know, it is too complicated and encoding should work in GPU. But it is impossible with Caché. I don't know why exactly do you need it, but I would recommend you to look at external tool ffmpeg, which is very useful and leader on work with video. And I think you can connect ffmpeg.dll, to work from Caché with $zf functions.

Well, there is mostly only one reason, why you can't mount your database and this issue mostly happens when anybody tries to migrate between different versions on different machines. And it is different localization settings. Like, your database uses some national global collation, and you try to copy it to the instance with different settings, where this collation does not supported. You should find mention about  wrong collation in cconsole.log. So, then, you should set the same NLS, as in the first system and try to mount again.

Another possible reason is different blocksize in the Database. By default Caché uses 8KB blocks, but it is possible to have different block size, and instance should be configured for this particular blocksize, as well. cconsole.log should also contain error in this case.

Some other issues, which you can face, but they do not prevent database to be mounted.

  • 8-bit or Unicode, when you install Caché you still able to choose it, when Ensemble, HealthShare, and IRIS is Unicode only. In this case, if your data not in English, possible data should be converted from 8-bit codepage to Unicde.
  • cache.lck file next to CACHE.DAT, it is a lock file, prevents to mount database with exclusive access. But Database in this case should be mounted in read-only mode.

Function $zf(-1) just executes a command passed as the second argument, you passed only file name. it is not complete, you should add command del  for Windows.

set status = $zf(-1, "del c:\sys\text.txt")

it should return 0 if the command was successful.

If you want just delete a file, you can use %File class, useful for many different operations with files and folders.

set result = ##class(%File).Delete("c:\sys\text.txt")