Is there some deeper reason not to contact LIB-IT DMS  that produced FILERO ?
They should know from the hip where their code is located and how to move it.
As your installation is talking German, there should be no lingual hurdle.

They even offer TeamViewer Support

Are you sure your HealthShare and the related ODBCdrivers are all 64bit?
the ending U of your $ZV might mean Unicode == 64 bit 
And OK. SMP doesn't need any ODBC  
 

If XML content is well formatted
it might be sufficient to remove all trailing text before
<?xml version="1.0" encoding="UTF-8 ?>

still works.
* don't forget all CSP content 
* don't forget to run $SYSTEM.OBJ.Upgrade()   

Way back some years I simple renamed CACHE.DAT to IRIS.DAT with IRIS stopped.
No guaranty this still works.
 

For testing I'd suggest to try an IRIS Community version 
Latest IRIS 2024.1 runs fine on Win11
the testing effort for that archaic code would be the same either for IRIS or latest Caché
the gap to bridge is about 2 decades in any case 

set var="MyClass"
execute "set obj=##class("_var_").%New()"

a bit dirty but matches your request

BTW:  from bash inside the container run

/iris-main -h

to see all available options
 

in docker-compose.yml  set
 

  command: -b "sleep 1d" 

• then you have a full day to access your container
• start IRIS manually  from bash as you need it

CONGRATULATIONS  to the Winners !

thx. fixed

 Guessing after the rater unclear description you are looking for Implicit Join

->  mimic an arrow in plain ASCII  does that

SELECT MySetting -> Name  from MyObj

It acts as LEFT OUTER JOIN 
https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=GSQL_implicitjoins   
https://docs.intersystems.com/iris20241/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_join

Alternate approach:
in SMP SQL  run this:
 

CREATE PROCEDURE ZPM.terminal() LANGUAGE OBJECTSCRIPT
{
 zpm "install webterminal"
 quit 1
}

 and next
 SELECT ZPM.terminal()

the final slash after terminal is important   !

 http://localhost:52773/terminal/

you can verify the installation in SMP  System > Security Management > Web Applications

agreed.
But Switching on/off Journal by process every time you write ^EVENT seems rather uncomfortable.

though it's compact as you know exactly when you need it,
 

depending on the actual long time use you may of course also    
use ^mtemp.EVENT  (in IRISTEMP)    
instead of a journaled ^EVENT in your actual namespace to escape transactions

• LOCK would be indeed the best equivalent to Isolation Modes
• just IRISTEMP doesn't react to COMMIT or ROLLBACK  (there is no related Journal)
• so instead of writing to your ^EVENT Global you may write to a PPG ^||EVENT acting as your  private temp
• after Commit or Rollback you decide if you MERGE  ^||EVENT to public ^EVENT or not.
• from your description, I assume you do it anyhow  

did you check TIMESTAMPDIFF ??