my example as code

Using my previous reply you can do this without need of any custom object:

SAMPLES>read xml
<?xml version="1.0" encoding="UTF-8"?> <session> <session_Id>124364</session_Id> </session>
SAMPLES>set rdr=##class(%XML.Reader).%New()
SAMPLES>do rdr.OpenString(xml)
SAMPLES>zwrite 
 
%SAX=1
%SAX(1)=2
%SAX(1,0)=""
%SAX(1,1)="1" ""
%SAX(1,2)="!>A"
%SAX(1,"N","http://www.w3.org/2001/XMLSchema-instance")=1
%SAX(1,"d")=4
%SAX(1,"d",1)="session"
%SAX(1,"d",2)=" "
%SAX(1,"d",3)="session_Id"
%SAX(1,"d",4)=124364
%SAX(1,"n")=1
%SAX(1,"n",1)="http://www.w3.org/2001/XMLSchema-instance"
%SAX(1,"v")=6
rdr=<OBJECT REFERENCE>[1@%XML.Reader]
xml="<?xml version="1.0" encoding="UTF-8"?> <session> <session_Id>124364</session_Id> </session>"
SAMPLES>

edited and simpler

• if this has an XMl header  <?xml version= ...
• then ##class(%XML.Reader).OpenString(yourxmlstring) will deposit your input in the local aray %SAX()

%BuildIndices is required if the indexed values are manipulated directly in the Global.
OR if the index definition is changed in Class or By DDL
during use as Object or SQL table it is maintained automatically.

• 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

I just gave it a try:

• an 8-bit DB works with code and globals without problem on a UNICODE  (16bit) installation
• I didn't try CSP pages
• in ns %SYS you have a utility ^GBLOCKCOPY converting a 8bit DB to a new 16bit DB  for a DB conversion

According to docs 

processing 8-bit on a unicode install should be possible

Character Width Setting 

,,,, while a Unicode instance can process both 8-bit and 16-bit data.

It's anyhow a tricky exercise 

• 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