Hello Scott,

I think the following doc section "Deploying a Production" is relevant:


"If a production uses XSD schemas for XML documents or uses an old format schema for X12 documents, the schemas are not included in the XML deployment file and have to be deployed through another mechanism. InterSystems IRIS can store X12 schemas in the current format, in an old format, or in both formats. When you create a deployment file, it can contain X12 schemas in the current format, but it does not contain any X12 schemas in the old format or any XSD schemas for XML documents. If your production uses an old format X12 schema or uses any XSD XML schema, you must deploy the schemas independently of deploying the production. For the schemas that are not included in the deployment file, they can be deployed to a target system by either of the following means:

If the XML or X12 schema was originally imported from an XSD or SEF file and that file is still available, import the schema on the target system by importing that file. XSD files can be used to import XML schemas and SEF files can be used to import X12 schemas.

Export the underlying InterSystems IRIS global that contains the schema and then import this on the target system. To export a global, select System Explorer > Globals, select the desired globals and then select Export. The X12 schemas are stored in the EnsEDI.Description, EnsEDI.Schema, EnsEDI.X12.Description, and EnsEDI.X12.Schema globals. The XML schemas are stored in the EnsEDI.XML.Schema global. See “Exporting Globals” in the Using Globals guide for details on exporting globals."


What schemas do you need? The ASTM schema structure page is the place to start for existing functionality and importing.


edit: I think you edited your comment to add the message you are seeing. I can see on modern ISC products that E1394 is built-in, not sure about on 2014.1.

Hello Nicola,

Pretty open ended question, but perhaps the shortcut reference would be of use to you? Maybe you can elaborate on what you're looking for.


Also, I'm sure somebody would mention VS Code if I didn't. That may be a more cozy programming experience for you depending on your background.

This isn't a topic I'm super familiar with, it probably depends on what you plan on doing with the messages. The following docs might be helpful?


If you're having throughput issues and suspect it is related to the service you're using (is there a particular reason you think that's the problem?), do you have a test environment where you can compare the 2 services?


What's the use case? You might be able to design something with SQL triggers but that feels ripe for complications. You can find people discussing this kind of solution (using triggers) for other databases online, and from what I can tell people generally agree this is a messy option.

If the idea is that people are accidentally executing improper SQL commands, perhaps I would tackle this from a training perspective, or by restricting SQL commands to a more limited audience.

Hello Michael,

If the Ensemble log reports an arbiter loss of connection, Ensemble doesn't really have more logs that can explain why that happened. These messages are just reporting the underlying condition that Ensemble experiences.

Confirming the cause of connection losses is really more a matter of reviewing network/other logging in the environment.

Hello Herb,

Have you checked the connectivity since the error is a timeout?

Can you make an SFTP connection outside of IRIS using a third party application or the command line?

You can debug the SSH portion of the connection via:


Hope that helps.

On top of Robert's answer, I would add - why are you copying from another namespace at all? If you just need the standard interoperability mappings, those get generated from the "enable namespace for Interoperability productions" checkbox.

You can't run 2 productions (even if you assign 2 namespaces) from the same databases simultaneously, so I would probably avoid "copy from" in general, particularly because you are trying to use EnsLib code.

There are probably specific cases where you might want to copy a namespace from another one, but I'd be cautious and make sure that copying is what you actually want.

edit: I am unsure whether using "copy from" on HSSYS is a good idea. Personally, I haven't done that, but I would be concerned that you might have similar issues to copying from %SYS, as HSSYS is a shipped database.


Additional context on what exactly you need to do would probably be helpful.

If this is something critical, I would consider reaching out to the WRC for assistance.

Otherwise, the ^JRNRESTO documentation is where I'd start:


You can restore a backup and then choose what subset of journals to restore.

Hi Niko,

I'm not sure I understand what you mean by "linking that query into a process", but you can run SQL from Object Script code using either dynamic or embedded SQL:


I hope that helps. If you are looking for other general guidance for this, feel free to reply.