New post
AllAccepted answers
Robert Cemper · Feb 25

From Ensemble.inc:
 

#define TRACE(%arg)             $$$catTRACE("user",%arg)
#define sysTRACE(%arg)          $$$catTRACE("system",%arg)
#define catTRACE(%cat,%arg)     Do:$$$DoTrace ##class(Ens.Util.Trace).WriteTrace(%cat,$$$CurrentClass,$$$CurrentMethod,%arg)
#;
#define DoTrace                 $S($D($$$EnsJobLocal("DoTrace")):$$$EnsJobLocal("DoTrace"),1:##class(Ens.Util.Trace).DoTrace())
#;
#define EnsJobLocal         %Ensemble
#;
. . . . 
Class Ens.Util.Trace [ Abstract, ClassType = "", ProcedureBlock, System = 4 ]
{
ClassMethod DoTrace()
{
	Set tJobConfigName=$$$JobConfigName
	Quit $G($$$ConfigTrace(tJobConfigName),0)||(""'=$G($$$JobTraceDevice))||$$$IsTerminalDevice($IO)
}
Robert Cemper · Feb 19

I see a general problem in interpretation of the "spiral" 
so I took some drawing for aquadratíc and a rectangular matrix. 

  1. depending on the starting point you have to take a pre-designed direction
  2. if you hit the diagonal you have to turn right
  3. you have to invalidate the row/column you just were on
  4. proceeding to invalid points is not allowed.
  5. start a the central point is an immediate termination as it has no direction to proceed

The diagonal came to my mind thinking how to NOT increase the imaginative radius of the spiral.
The related subscripts for the diagonale points of an n*m are found as (-n/2+x,-m/2+y) 
The pink subscripts are obviously (n/2,m/2) and might be just virtual.   

As subscripts start with 1 and first  piece position  is also 1
some more adjustment of coordinates is required

I haven't written any useful line yet.

Robert Cemper · Feb 16

The clockwise logic is simple for a  3*3 matrix
though starting with 4*4  there is some rule missing on how the handle a dead end
Starting at a corner (1,1) or similar is trivial. 
BUT:  starting at any other point may create a rathole or miss some boxes 

        Set matrix($Increment(matrix)) = "C,O,D,E"
        Set matrix($Increment(matrix)) = "U,C,H,G"
        Set matrix($Increment(matrix)) = "M,U,F,O"
        Set matrix($Increment(matrix)) = "S,I,F,L"

Start (1,1) is in the example but
Start (1,2) runs ODEGOLFISMU what is the next to (2,1) ?  (1,1)  or (2,2) or ??
worse with Start(2,2) already the first according to description could be
up (1,2) or right (2,3) or left (2,1)  leaving dead ends clockwise.
And this is only with N=4  larger grids may create multiple lost cells.
Clockwise spiral is just not detailed enough for a UNIQUE result to collect ALL cells
A rule how to handle / skip already consumed cells might improve.
Just as I type a non straight spiral solution to (2,2) consuming the full matrix
might be CUISMUCODEGOLFFH
 I fail to imagine grids >5*5
  

Robert Cemper · Feb 4

I just identified a possible source of the hidden Python installation:
https://docs.intersystems.com/iris20243/csp/docbook/DocBook.UI.Page.cls?KEY=GEPYTHON_prereqs#GEPYTHON_prereqs_version

Microsoft Windows does not come with a default version of Python, and
as of InterSystems IRIS 2024.2, the InterSystems IRIS installer for Windows
no longer installs Python for you.

I did an upgrade from my previous  IRIS 2024.1 

Robert Cemper · Feb 4

After un-install of my own python versions
PY was still there in a different hidden and protected version unknown for me.
I detected it using regedit 
C:\\Program Files\\WindowsApps\\PythonSoftwareFoundation.Python.3.12_3.12.2288.0_x64__qbz5n2kfra8p0\ 

I fail to explain where it came from (pre-installed win ?? )
Manual killing it and reinstallation of an official Python distribution fixed it.

BIG THANKS for your advise and help- 

Robert Cemper · Feb 3

Your file format doesn't fit, but you are close.
UDL Header is missing, also leading blanks in the lines as you have no labels.
And you have to switch to namespace %SYS and back to make it work.

ROUTINE DisplayDB[Type=INT]
 new $namespace
 zn "%SYS"
 set db=##class(Config.Databases).DatabasesByServer("",.dbList)
 for i=1:1:$LENGTH(dbList,",") {
   set dbName= $PIECE(dbList,",",i)
   write dbName,!
 }
 quit