Hi Alexey.

I'm not aware of such event handler.

However, I wonder why do you need it at all? If you provide use case, perhaps we can advice some other way to achieve it.


you don't have DeepSee Model and DeepSee Analyze enabled in "Extended feature codes". That's why these menu options are grayed out.

Check with InterSystems Sales to get a license with these bits enabled.

Seems to work. Please provide small standalone example, so that we can reproduce

C:\InterSystems\ENSEMBLE2017x2x2\bin>set AA=22

C:\InterSystems\ENSEMBLE2017x2x2\bin>echo %AA%

C:\InterSystems\ENSEMBLE2017x2x2\bin>cache -s ..\mgr

Узел: ru-akoblovW10VM, Экземпляр: ENSEMBLE2017X2X2

USER>w $system.Util.GetEnviron("AA")

Hm, I don't understand why do you need to do zzdump in background? I would just log to debug globals any variables / expressions I need. And later, when doing output, I would zzdump them.

Thank you Alexey. Yes, you are correct, second statement is correct. I've asked to modify first statement.

Hi Fab!

Changes to globals mapped to non-journaled databases are still journaled inside transactions. Unless globals are mapped to IRISTEMP or journaling is completely stopped at the system.

Quoting the docs: "While updates to non-journaled databases that are part of transactions are journaled, these journal records are used only to roll back transactions during normal operation. These journal records do not provide a means to roll back transactions at startup, nor can they be used to recover data at startup or following a backup restore."


Please see this comment in Configuring a REST Service to Use CORS

A Caché REST service supports the OPTIONS request (the CORS preflight request), which is used to determine whether a REST service supports CORS. This request is executed by the CSPSystem user. This user should have READ permission on any databases used by the REST service; if not, the service will respond with an HTTP 404 error. 

No, indirection does not introduce additional stack, as far as I know. It works with variables that are visible in public (global) scope, not in private scope of procedure.