This is a permission issue.   The ^ZUSET routine needs to be able to write to the database and cant because it was mounted read-only because of the IRIS.lck issue.   There is a permission issue at the linux level on the directory where your database is stored.   Need to make sure it's set properly so that the user which IRIS runs under has write permissions to the directory.
Then you can unmount and remount the database and it should solve your problem.

You could do one of a couple things.

1.Export all the ROUTINES to a file using %RO and then use a linux tool or something else to make the global replace

or

2.Simply use the %RCHANGE utility at the IRIS command prompt to do the global routine change.   I certainly would recommend verifying each change.

Ignacio

This is a good reference document to follow.

Now you need to create a Namespace that uses your RPMS database for routines and globals.

Refer to the doc link I sent earlier on Creating Namespaces.

Did you add a new local Database under Local Databases?

Ignacio-

You can find instructions on adding databases and creating namespaces in the online documentation.   Please review the sections Configuring Data and Configuring Namespaces in the docs at the link below.

https://docs.intersystems.com/iris20193/csp/docbook/Doc.View.cls?KEY=GSA_config
 

No.   You should place your FOIA CACHE.DAT into it's its own directory and then in the system management portal create a local database and namespace.   When creating the database you will identify the directory where you placed your IRIS.DAT file.

further, the url you are using indicates that you are connecting thru the internal web server installed when you installed the instance which is intended for SMP access only and development.  You should switch to a production quality web server for SSL support

Oh, it must assume that you wouldn't need it for classes.  :(

Interesting, what platform (win/linux, etc)

What version are you running?

Definately would always recommend full commands.   I remember the day when we had to write code this way however it isn't the case anymore.

That said, it's good to be able to read code like this because it still exists out there.

This is referring to mapping between SDA and Health Insight cubes.

Please PM me so we can discuss your need further.   I am one of the Sales Engineers working with the VA.

Simply select the code to convert and then select Edit -> Advanced -

 And then either Expand or Compress  Commands.

You can use the foundation production as a router if you want, the difference is that in that scenerio you would be adding all of the components that you needed to the production manually.   Configuring a routing production should give you the basic components needed, e.g., a service for input, a router for applying rules based routing and then an operation.   It provides the basic building blocks needed to route messages.

A generic interoperability production can route messages as well.

Stephen
An Interoperability production is a general integration production, vs a routing production is one that automatically includes some basic business hosts needed for routing messages.

Typically you would use a routing production if you wanted to route HL7 messages, for example.

An Interoperability production is a blank slate allowing you to add whatever business hosts you need.

There is no real difference in capabilities other than what is automatically created as part of the production configuration when it is first created

What does your full URL Map look like?