go to post Alexey Maslov · Mar 22, 2023 It seems to be an IP of its first network adapter, probably of virtual one.
go to post Alexey Maslov · Mar 6, 2023 47 (pure COS w/o undocumented features :) a q:$i(r($a(w,$i(i))#32))=2 0 q:i>$l(w) 1 g a
go to post Alexey Maslov · Mar 4, 2023 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?
go to post Alexey Maslov · Mar 4, 2023 > 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
go to post Alexey Maslov · Mar 3, 2023 58 s r=1 f i=1:1:$l(a){s r=$i(r($a(a,i)#32))<2 q:'r} q r f i=1:1:$l(a){s r=$i(r($a(a,i)#32))<2 q:'r} q r
go to post Alexey Maslov · Feb 13, 2023 Hi Ben and John, now I've got some food for thought, thank you.
go to post Alexey Maslov · Feb 8, 2023 It would be nice if this was not be hidden when View -> Output panel is visible.
go to post Alexey Maslov · Jan 19, 2023 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?
go to post Alexey Maslov · Dec 20, 2022 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?
go to post Alexey Maslov · Dec 19, 2022 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?
go to post Alexey Maslov · Dec 16, 2022 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.
go to post Alexey Maslov · Dec 15, 2022 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^ztest w $Stack($stack,"MCODE"),!
go to post Alexey Maslov · Dec 15, 2022 Hi Anna, You can look at the property CurrentSrcLine of %SYS.ProcessQuery class (guess SMP uses it showing process details on Process page). Keep in mind that there is more sense to examine the state of some other process rather than the current one as in the last case you will see the very code line where you are examining the process :).
go to post Alexey Maslov · Nov 15, 2022 When I inserted your sample call of %apiOBJ nothing bad happened with the parser, maybe the update would help yours. Meanwhile, more standard way of doing the same: do $system.Status.DecomposeStatus(sc,.err,"-d") is apparently better supported with VS Code: pop-up help and parameters prompting are rather handy, aren't they?
go to post Alexey Maslov · Oct 18, 2022 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.
go to post Alexey Maslov · Sep 14, 2022 /// 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))}
go to post Alexey Maslov · Jul 27, 2022 Hello Stefan, Thanks for the reference, while I'm still not sure about the step #2 as ^JRNRESTO provides the (defaulted) option to disable journaling of updates during the restore to make the operation faster, see the step #10 of Restore Globals From Journal Files Using ^JRNRESTO. Besides, this is the only option compatible with parallel dejournaling. So the idea to switch off journaling system-wide looks excessive. Regards,Alexey
go to post Alexey Maslov · Jul 20, 2022 The manual says I should (in short): Stop journaling with ^JRNSTOP Which manual does it say? Any manual I've read last 20 years says quite opposite: never stop journaling unless you want to get your system in troubles.It seems that you should not bother on the subject at all: during the database restore it can't be involved in any users' activity, so there would not exist any journal record on its change.
