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.

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?

Agree with you. IMHO, the original question has no definite answer: to get the executed code line offset of the current process, this (arbitrary!) line of code should contain the call of some "checker". Or there should be the limited number of selfsufficient "points of interest" in the code.

ROUTINE ztest
line ; the entry point
  w $Stack($stack,"MCODE"),!
  q

 If run, it would apparently print the current source line... which does nothing but printing itself:

USER> do line^ztestw$Stack($stack,"MCODE"),!

I guess it would not as ZRemove / ZLoad / ZIinsert / ZSave commands are mostly used as tools for the legacy way of editing routines (using routine buffer) rather than for code execution. Of course, one can execute the code inside the previously loaded routine: `zload routine do sub(...)`, but this looks strange if compared with the normal way of doing the same using `do sub^routine(...)` or `set sc=$$fun^routine(...)`. In short, virtually nobody runs code this way.

/// 48 characters:
ClassMethod MinLength(s As %String) As %Integer
{
 F i=1:1:$L(s){S v($L($P(s," ",i)))=i} Q $O(v(0))
}

Alas, it has the similar problem as my original solution: 

w ##class(z.Scratch).Detector("azazz","zaaza") ;should be 01

So, my feeling was right... It's time to quit this golf club for now, at least for me )))

Yes, it can be, while this approach can't win, as I already understood. Size = 67: 

ClassMethod Detector(a As %String, b As %String) As %Boolean{
 s a=$zu(28,a,6),b=$zu(28,b,6) q $tr(a,b)=$tr(b,a)&($l(a)=$l(b))}

This change seems to be applicable to IRIS only.
In Cache log data is still in ^%ISCLOG("Data"); just checked in Cache 2018.1.6.

If you are interested in global moving without downtime there is (live-global-mover)

Thank you, already not as new deployments of our HIS use separate document storage from the very beginning. 

Your solution is beautiful as it allows placing the ECP enabled "moved data" server to some less expensive disk storage. In our case that I've briefly described ECP & Mirror were already in use, so we couldn't place document DB on a separated data server as having several independent data servers would be a bad decision for many reasons.

And to launch IRIS do...

Thanks, Evgeny.

Can't notice a difference between the lines: 1 and 3, 4 and 6. Just a typo?