Good Job! Very useful tutorial!

Ok, if we are talking about code in deployed mode you simply can't do this. You must get a code compiled for your actual version.

You can try with $SYSTEM.OBJ.Export which export the obj, but you will probably get the same error.

Hi, you could check what's happening using Wireshark to analyze the TCP traffic and the request that you are doing.

Are you getting this error on the server side, what you got on client side?

Seems that they are not communicating or the server is getting something wrong

Hi, you simply got an information (0 in the log), these are system db so you can choose to not backup them (they are included in the installation) and running the task as another use won't solve the problem (that is not a problem).

Also mounting them as rw is a bad bad thing because you can end up in modifying the DB (Andi you don't want this).

You should simply ignore the message and if it's a monitoring system that warns you, set it to check for 1 or above severity (I'll go for 2 or more).

If you really really want to get rid of it and still backup every db, write a custom backup routine tanto mounts the db row, backup them, get them ro again. But this would be a waste of time because it's just an info

why don't you use ^%GOF and ^%GIF? They should be compatible i think.
Else the "bad" workaround is do something dirty, you could try to:

Create a new DB in the old instance
copy the global in that db
copy the db on the new instance
attach the db
move your global where you like

Don't know if this works, it "should"

Hi Scott,
not an expert for zstop, but what you are looking for cannot be developed with the zstop.

With an "iris force", hardware failure (hard power off, server fault,... anything that is not a "polite" shutdown) or other similar condition where iris simply is killed, no zstop is executed. You can only be aware of an unclean shutdown at the iris restart, but that's too late for what you are looking to do.

What you can do is to have an agent that monitors the iris instance (qlist, process, messages.log) and execute action when certain conditions are met.

Moreover i haven't found anything on the "shutdown" cause, it's just a shutdown inside iris i think

Pietro

Hi,
the most straightforward thing to do is to use the upload manager that will take care of everythings.
But if you want to go via code, as Davide said, you should use ##class(User.SSUser).%New() to create the user.
Keep in mind that the user at first login MUST change the password. To avoid that, you have to have 2 row in the password table, so you should change the password one time via class and then the user should be able to login with the specified credentials.
So the main suggestion is to go with upload manager and, may be, ldap as a backend for password auth.

Iris doesn't show the file but uses the directory. Make a new dir with iris.dat in it and create a new database pointing to that dir in iris.

If you are on Linux make sure that the file is IRIS.DAT all caps. In every platform consider make an exception for the antivirus...

Hi,

First one is in STU routine where you are probably having a problem with the installation. Contact WRC, probably you will need to make a "repair" installation

Second error is just a subscript that doesn't exists. It's trying to access ^oddCOM("") that doesn't exists. But probably everything is related to a bad upgrade.