^SPOOL(docIdx) approach allows spooling sharing across ECP network, while ^SPOOL($j) does not :)

%IS is an utility which allows to choose devices by CHUI routines users and %SPOOL utility can manipulate with spool files opened using the %IS utility only.

It seems that initial purpose of spooling facility has gone with such a users and such a printers (strictly character based, w/o ability of font selection, etc), while its usage still can be actual in rather exotic cases like this one.

Yeah, but it should be used with precautions. Let's see what happens when two processes access spooling device concurrently: 

USER>f {q:'($zh\1#20)} k a o 2 f i=1:1:10 {s a(i)=i*100} u 2zw a c 2; process #1
USER>s i="" f  {s i=$o(^SPOOL(1,i),1,line) q:i=""w line} ; look inside ^SPOOL(1)...
a(1)=100
a(2)=200
a(3)=300
a(4)=400
a(5)=500
a(6)=600
a(7)=700
a(8)=800
a(9)=900
a(10)=1000
{66892,65205{11

USER>f {q:'($zh\1#20)} k a o 2 f i=1:1:10 {s a(i)=i} u 2zw a c 2; process #2
USER>s i="" f  {s i=$o(^SPOOL(1,i),1,line) q:i=""w line} ; look inside ^SPOOL(1)...
a(1)=100
a(2)=200
a(3)=300
a(4)=400
a(5)=500
a(6)=600
a(7)=700
a(8)=800
a(9)=900
a(10)=1000
{66892,65205{11

As you can notice, one process's output suppressed the other's one. To avoid it, firstly RTFM: OPEN and USE Commands for Spooling Device, and implement some synchronization pattern, e.g. 

USER>f {q:'($zh\1#20)} s docIdx=$i(^SPOOL) k a o 2:(docIdx) f i=1:1:10 {s a(i)=i*100} u 2zw a c 2; process #1
USER>s i="" f  {s i=$o(^SPOOL(docIdx,i),1,line) q:i=""w line}
a(1)=100
a(2)=200
a(3)=300
a(4)=400
a(5)=500
a(6)=600
a(7)=700
a(8)=800
a(9)=900
a(10)=1000
{66892,66645{11{

USER>f {q:'($zh\1#20)} s docIdx=$i(^SPOOL) k a o 2:(docIdx) f i=1:1:10 {s a(i)=i} u 2zw a c 2; process #2
USER>s i="" f  {s i=$o(^SPOOL(docIdx,i),1,line) q:i=""w line}
a(1)=1
a(2)=2
a(3)=3
a(4)=4
a(5)=5
a(6)=6
a(7)=7
a(8)=8
a(9)=9
a(10)=10
{66892,66645{11{

Each process has got it's own output in ^SPOOL(docIdx) now. This approach works if every consumer of spooling facility follows the same pattern; incrementing ^SPOOL is just an easiest approach, while it would be better avoid touching system globals and increment something else according to your taste.

Another possible solution is to write a small wrapper around curl.

I'd like to collect tables based on logs

In general, such approach is far from optimal for Caché like databases because logs (which are usually called  "journals" in Caché/M world) are being written on global (= lowest possible) level, disregard of data model used by an app (SQL, Persistent classes, etc). Reconstructing app level data from underlying globals can be a tricky task even for Caché guru.

That was one of the reasons why colleagues of mine took another approach for close to real-time data export from Caché to external system. In a few words, they used triggers to form application level data packets on Caché side and pipe them to the receiver. This approach saved CPU time preventing its waste for filtering out unnecessary journal records and minimized cross-system network traffic.

$sequence can leave "holes" in numbering which can be undesirable in some cases, e.g. when meaningful IDs are assigned: it seems to be strange to have APP-DD-99 and APP-DD-101 without APP-DD-100.

Setting $ZTZ affects the current job only (the job, which sets $ztz), so there is no danger for other processes

What about REST services or web apps? Isn't there one process possibly serving several clients' requests?

Hi Olga,
Is the roundtable record available?

Hi Sylvain,

Is it possible to publish more details of the scenario which showed such impressive figures?

The same case is with Native API for Python.

+1

Both global traverse only 1st level in $order

It seems that you are a bit confused with these levels. Globals are B* trees physically: all subscripts are concatenated into one key, therefore even when you logically traverse only 1st subscript, you traverse all of them physically.

my real global has more than 6-8 subscripts and takes 110

What is the result of

write$$AllocatedSize^%GSIZE($name(^RealGlobal))/1024/1024

a similar global with 6-8 subscripts ... and takes only 15 to 16 seconds

What is the result of

write$$AllocatedSize^%GSIZE($name(^SimilarGlobal))/1024/1024

Done, expecting that InterSystems ObjectScript was the right choice for the kind of issue.

Establishing of source control based development technology needs some efforts, while gives much more advantages. It's possible even with Studio, while easier with VS Code.
Besides, when each developer has its "own" methods it would be easier to resolve possible merge conflicts.

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.

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!