Thank you.
In Caché 5.0 and earlier versions there were no web portal at all; those version were supplied with so called GUI Utilities: System Explorer, Configuration Editor and so on.
System Management Portal appeared in Caché 5.1, and many people still call it by its initial name often abbreviating it to SMP.

Hi Hiroshi,
Can you explain the difference between "Management Portal" and "System Management Portal"?

Hi Luis,
Thank you for the article.
Did I understand right that its main purpose was to introduce the mirror concepts to novices? If so, it's great, while in real life: if the host goes down, all three containers would go down.

Chad, thank you for complete explanation of available options. As to you questions:

1. We have a TASKMGR task which calculates the size of each global in all databases. It's usually scheduled by our customers for daily run.
2. The main purpose of collecting such info is the ability to quickly answer the questions like this: "why my database is growing so fast?". Integrity Check is not used for the similar purpose because it can't be scheduled for daily run due to its relative slowness in our versions of Cache and IRIS.

You can use ^$ROUTINE to return information on the OBJ code version.

while one can list routines of any given code type using the OP's approach.

Hiroshi, take it easy - everybody can make a mistake.
Meanwhile, I'm sure that $ZIO was initially intendent for terminal devices only. Here is the oldest link I was able to find: https://cedocs.intersystems.com/documentation/cache/cache41/olr/olrvzio....
Why not use ##CLASS(%SYS.ProcessQuery) for similar purposes? It's more powerful and better documented than some "mystic" system variables and functions.
Happy writing!

I should check docs before any "quick testing": only terminal (TRM:), telnet and file current devices can provide $ZIO with non-empty values. No client/server!

Hiroshi,
May I ask you where did it ever work?

Here are the results of quick test in Studio Output window: 

w "*"_$zio_"*"
**
w "*"_$zutil(67,12,$j)_"*"
*MYPC*
w ##CLASS(%SYS.ProcessQuery).Open("P"_$j).ClientNodeName ; prefered (documented) way
MYPC
w ##CLASS(%SYS.ProcessQuery).Open("P"_$j).ClientIPAddress
10.8.3.37

Alternative program which supports CacheActiveX connection showed the same results, by the way, regardless of server's platform, whether it was UNIX/Linux or Windows.

IRIS for Windows (x86-64) 2021.1 (Build 215U) Wed Jun 9 2021 09:39:22 EDT

while results were similar in all previous Cache/IRIS versions I managed to run.

It seems to be an IP of its first network adapter, probably of virtual one.

Thank you, Vitaliy. Corrected.

The suggestion on the transaction was to avoid needing to lock and block by read processes

Hi Alex,
How can transactions help to avoid locking/blocking by read processes if they need to see a consistent database state, taking in account well known fact that transactions are not isolated in IRIS?

> This avoids the need wait with locks / blocking

If so, why the common practice is to write something like this:

 tstart
 lock +^smth
 set ^var1(x1,...xn)=...
 ...
 set ^varN(x1,...xm)=...
 lock -^smth
 tcommit

Robert,

I guess you meant Lock +^myReload

It would be nice if this was not be hidden when View -> Output panel is visible.

Standard queues provide at-least-once delivery, which means that each message is delivered at least once. FIFO queues provide exactly-once processing, which means that each message is delivered once and remains available until a consumer processes it and deletes it. Duplicates are not introduced into the queue.

..so I guess that you mean standard queue with several worker processes dequeuing items from the queue. In this case the CPU utilization would likely depend on the number of workers, wouldn't it?
 

Then if you have an preinstalled IRIS, you will keep the private server

Do you mean that in the case of preinstalled IRIS 2022.x the private server would be kept after the upgrade to 2023.1?

Dmitry inspired me for the next question:
what will happen if IRIS 2022.2 development instance (with PWS inside) will be upgraded to 2023.1? Will PWS be wiped off during upgrade or not?
If not, will VS Code and SMP be still operational with that PWS?