go to post Robert Cemper · Feb 1, 2021 Good Old VMware Player would allow selecting processors, memory, access rights, ..Docker is definitely no replacement to it. Just a hack.
go to post Robert Cemper · Feb 1, 2021 You should take a look to Using Caché SQL ! Executing SQLhttps://docs.intersystems.com/latest/csp/docbook/Doc.View.cls?KEY=GSQL_basics#GSQL_basics_executing Using the SQL Shell Interfacehttps://docs.intersystems.com/latest/csp/docbook/Doc.View.cls?KEY=GSQL_shell
go to post Robert Cemper · Feb 1, 2021 You can't run a SQL statement from the console prompt.You need to start the SQL shell first: SAMPLES>do $system.SQL.Shell() SQL Command Line Shell ---------------------------------------------------- The command prefix is currently set to: <<nothing>>. Enter <command>, 'q' to quit, '?' for help. [SQL]SAMPLES>SELECT . . . . your statement
go to post Robert Cemper · Jan 30, 2021 https://review.capterra.com/SS-IRIS-Data-Platform-191676-3166957531-en
go to post Robert Cemper · Jan 29, 2021 Sorry,I probably don't understand what you try to achieve.To my understanding ZPM is targeted to IRIS and its applications andNOT to the underlying operating system.- Though I admit that a lot of "hacking" into the OS is possible from IRIS. With the broad range of operating systems supported by IRIS, I rate this as a rather questionable approach, that I wouldn't support.
go to post Robert Cemper · Jan 29, 2021 My workaround was to place apt-get into Dockerfile as User root
go to post Robert Cemper · Jan 27, 2021 ##class(Ens.Util.Time).ConvertDateTime($e(source.{ORCgrp(1).RXA:DateTimeStartofAdministratio}_"000000",1,14),"%Y%m%d%H%M%S","%d/%m/%Y",,.tSC) should save your problem. then default time is 00:00:00 Or without any time ##class(Ens.Util.Time).ConvertDateTime($e(source.{ORCgrp(1).RXA:DateTimeStartofAdministratio},1,8),"%Y%m%d","%d/%m/%Y",,.tSC)
go to post Robert Cemper · Jan 26, 2021 You may use this Python example and use it over CPIPE as shown in my example in OEX
go to post Robert Cemper · Jan 26, 2021 there are 14 programming examples available in OpenExchange related to integration with node.jshttps://openexchange.intersystems.com/?search=node&sort=d.desc
go to post Robert Cemper · Jan 26, 2021 As iristrmd.exe only runs on Windows it is simply localhost:23 Telnet + SMP: System > Security Management > Services > %Service_Telnet enablediris session is not available in Windows
go to post Robert Cemper · Jan 21, 2021 Right. It stands at the first line and <ctrl>+<F5> in Studio starts it It is also in Debug menu / Go I think that the design idea was to have a last chance to set breakpoints.
go to post Robert Cemper · Jan 21, 2021 just tried to reproduce a similar case in Terminal.#0) clear all stored breakpoints (menu: Debug / View breakpoints / remove all)#1) set the breakpoint in Studio using F9#2) attach to process (shell if in Terminal)#3) do ^yourroutine in terminal#4) In Studio: <ctrl>+<F5> let it run if your breakpoint is reached you see the yellow box Hint: try it with some simple 5 line routine first If you never see the yellow box then you just don't execute this line
go to post Robert Cemper · Jan 21, 2021 That's correct if you are already in an .int routine.OTHER relates to cls, mac, .....
go to post Robert Cemper · Jan 20, 2021 As an add on:If you also want to get back the result of your command you may use CPIPE device.See my article and the related example in OEX and this fresh one for Python
go to post Robert Cemper · Jan 19, 2021 Ahh!Studio debugger is based on ZBREAK command.old style BREAK is only useful for interactive debugging in the terminal and ignored in backgroundI always tried not to mix it up. Not sure if this is the reason. I think it's suspicious.
go to post Robert Cemper · Jan 19, 2021 I've seen such behavior during debugging when I fell into some deployed system code (.obj only)A similar effect happened to me when I touched some customized command, function, variable from ZLANG***[which I tried to debug !!!] I could gain control again by some <SHIFT><F11> until returning to some code covered by .intAs Studio stores a lot of info in the Windows registry just killing Studion might cause some confusion.
