You can use $ZF(-100) command to execute operative system commands (here an example), with that command you can look for the process that is locking the superserver.

Well, I highly recommend to you to not use the same instance of Health Connect for TEST, DEV and PRODUCTION, even more, I recommend to you to deploy each environmnent in different servers.

It won't be the first time that a code un DEV has a infinite loop creating heavy globals that use all the space in the disk. 

Do you mean Intersystems Reports?

https://docs.intersystems.com/components/csp/docbook/Doc.View.cls?KEY=GISR

You can check the process running for each namespace and the CPU time:

And using de PID you can identify in your Operative System (Windows or Linux) the process to check the memory used.

Congratulations to all the participants!

Here is the documentation for the Nginx in Windows:

https://docs.intersystems.com/healthconnect20243/csp/docbook/Doc.View.cl...

Thank you very much Community!!

Thank you very much! With the Community to the infinity and beyond!

Maybe the error is on the declaration of the table, use the parameter NODELIMITEDIDS for the declaration:

CREATE FOREIGN SERVER server-name FOREIGN DATA WRAPPER jdbc CONNECTION 'mysqlconnection' NODELIMITEDIDS

This is a personal opinion but I think that it means that the restoring of the journal didn't affect all the databases of the system located in different folders.

Hi @Martin Staudigel you only can include DTD in the XSD if you define it using specific flags.

The solution is to create a new class to import the schema in XSD programatically. This is an example of the code:

Class XML.SchemaReader Extends %Persistent

{
ClassMethod ImportClasses(fileName As %String = "C:\Temp\example.xsd") As %Status
{
#include %occInclude
#include %occSAX
		#dim sReader as %XML.Utils.SchemaReader = ##class(%XML.Utils.SchemaReader).%New()
		#dim features as Filero.DataType.String
		set sReader.SAXFlags = $$$SAXFULLDEFAULT-$$$SAXVALIDATIONREUSEGRAMMAR
		set sReader.MakePersistent = 0
		set sReader.MakeRelationships = 0
		set sReader.GenerateXMLNILNOOBJECT = 1
		set sReader.GenerateXMLNIL = 1
		set sReader.KeepEmptyClasses = 1
		set features("BINARYASSTREAM") = 1
		quit sReader.Process(fileName,"ImportedScheme",.features)
}
}

This code will create a package "ImportedScheme" in your IRIS

As the creator of the idea, you have all my support! The localized versions are really confusing with literal translations that have no sense.

If you execute the bat file from the command line of Windows...does it work? Maybe the PATH to the java bin folder is not accessible from the Ensemble user.