• for a NEW created index this is "work in progress" that shouldn't be used until completed.
• if it's a matter of repair  $SYSTEM.OBJ.ValidateIndices() might be more useful.
  see my article Fix broken index 

Hi @Ben Spead !
My personal congratulations to see you here!
Working with you and your team on the worldwide HERMES project was one
of my highlights during my time at InterSystems.
It was due to your interpersonal skills to make this team so successful.

It was so special to me to participate and share this experience.
As a Sales Engineer with no local office I often felt "at the outer border of the milky way".
Not lost in space but almost.
But working in your team gave me the feeling of a "technical home".
As Engineer I enjoyed to style and create a product.
Which was more important to me than to consult, advice, and teach how to use some features.

Big THANKS for that!

Robert   

from class documentation:

You can import files exported in

• XML format,
• %RO format,
• CDL format,
• UDL format,
• %GOF,
• and CSR/CSP files.

You should do an export of one of this types and then see
how this may match your .vm  thing.

Your screenshot is definitely some XML
But it doesn't match any formatting structures or rules required  in IRIS or Caché.

another hack:

• create an SQL Procedure in SMP
• once compiled use Test Feature in SMP to execute it

Example:

CREATE PROCEDURE ANY.NAME()
LANGUAGE OBJECTSCRIPT
{
 ;;;  fill in whatever you want to do
}

or over SQL using OEX package SQL-for-ERRORS-Global

• in OEX you find 13 matches for SWAGGER already
• and 6 articles in this forum

simply search

This docu on Cached Queries  may be an explanation of what you identified 

• how do you identify 2 cached queries generated at the same time?
• and if so,  what is the difference ?

object code is just binary content.
not even debugger can decipher it.
I've never seen a decompiler (like for java)  the last 25 years.

1. in SMP >  System Explorer > SQL you place your query and tab SHOW PLAN tells you the best approach with lowest cost
   -
   
2.  As any data in IRIS (Caché,...) are stored in Globals B+Tree structure always applies by design.

Basically every SQL statement whether internal or external is cached for eventual reuse in future
You can find Cached Queries from  SMP > System Explorer > SQL > Cached Query

clicking on one in the list you get the details

Tab SQL Statements shows much more details

Click on SQL Statement Text offers a further drill down into details

How can I run this from my Win 11 +  Desktop Docker ?
it actually fails, issue is reported  https://github.com/grongierisc/iris-flask-template/issues/1

How can I run this from my Win 11 +  Desktop Docker ?
it actually fails, issue is reported https://github.com/grongierisc/iris-django-template/issues/1

How can I run this from my Windows 11 Docker Desktop ?
install fails. https://github.com/grongierisc/iris-fastapi-template/issues/1

check if your external webserver listening to 8080 is started at all

You probably should ask this in an Oracle forum.
This is definitely not the best place to discuss such idea

any MIRORING is technically GLOBAL Mirroring
read in docs https://docs.intersystems.com/iris20242/csp/docbook/Doc.View.cls?KEY=PAGE_high_availability

4 options:

• map it to namespace %ALL
• naming it with  % as first character places in %SYS namespace (e.g. ^%MUTHU) 
  • that traditional approach is possible but not recommended
• naming it ^mtemp.*,  ^CacheTemp*, ^IRIS.Temp* allocates it in db IRISTEMP
• subscript level mapping allows partial mapping  (e.g. to IRISTEMP)  

Manipulating time values is a risky ground. See this simple example.
 

USER>write ?1%, $ZTZ," : ",$zdt($ZTS)," : ",$zdt($now())," : ",$zdt($h)
               -60 : 07/04/2024 16:03:42 : 07/04/2024 17:03:42 : 07/04/2024 18:03:42

• $ZTZ  is the geographic offset to UTC in minutes
• $ZTS is UTC time  (no daylight saving !)
• $NOW() is UTC adjusted by $ZTZ   (no daylight saving  or special time zone adjustment)
• $H is based on the time set in your server OS  

So for international applications using anything else than UTC is an open trap you might be caught in.

This was the original motivation to use UTC in ENSEMBLE and it's descendants and followers 

traditional style:
 

Set From = "2024-07-04 13:21:16.477"
Set To = $tr(From," -:")\1

Pls be more precise:
- where do your data come from and how?
- where do you expect to store them ?
- what do you mean by "linked servers" ?
NO ODBC: in general in  IRIS almost every table can be accessed also as object..