Best way to "do this after another class compiles"?

Question

Question

#Coding Guidelines #Compiler #InterSystems IRIS

I have a class with a projection that creates some persistent classes (chunks) and a non-persistent "Daemon" class that I want to have running in the background, doing some processing. The daemon needs to look at the "chunk" classes, and I want it to be simple to start the daemon -- I am currently calling the daemon's start method at the end of the CreateProjection method. When I do this, I get a <CLASS DOES NOT EXIST> error from the daemon when it tries to query against one of the chunk tables. But, if I add a "HANG 5" at the beginning of the daemon start method, this runs fine. I am assuming this is because the chunk class compilations are being jobbed away, so we fire the daemon start method before the compilations finish.

"HANG 5" or similar feels like a bandage solution, and with larger projections that need to compile more chunk classes, 5 seconds might not be enough. Is there a way to programmatically "wait for this compilation to be finished and then do a thing?"

I am also not sure if compilation gets jobbed away, if anyone has any insight into that, that would be wonderful as well.

Please let me know if there is other useful information I can provide. Thank you!

Product version: IRIS 2025.1

$ZV: IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2025.1 (Build 225_1U) Fri May 16 2025 12:22:16 EDT

Discussion (8)4

Log in or sign up to continue

score 0 · Answer 1 · 2025-06-23T11:40:12-04:00

Matthew Giesmann · Jun 23

Would /multicompile=0 force the behavior you want?

0 0

score 0 · Answer 2 · 2025-06-23T11:53:04-04:00

Justin Millette · Jun 23

Tried /multicompile=0 and did not see a change.

0 0

score 0 · Answer 3 · 2025-06-23T11:48:40-04:00

My other thought would be to (carefully!) take out and release the oddDEF lock for the class

//adjust timeout
lock +^oddDEF(class):5
//check $test and handle timeouts appropriately
write $test
1
//make sure this happens
lock -^oddDEF(class)#"I"

score 0 · Answer 4 · 2025-06-23T21:26:07-04:00

Ben Spead · 15 hr ago

@Mark Hanson - any thoughts on this one?

0 0

score 1 · Answer 5 · 2025-06-24T00:25:56-04:00

I would safegueard the code execution in the daemon by checking %Dictionary.CompiledClass to see if the chunk classes are compiled yet.

score 0 · Answer 6 · 2025-06-24T10:29:23-04:00

This is what I landed on. Since the "setup" part of the daemon only needs to run once at daemon startup, this solution doesn't pose any timing problems/long waits. Thanks!

score 0 · Answer 7 · 2025-06-24T03:37:03-04:00

I would like to see a small code example to understand how to help you.

According to the documentation^{%Projection.AbstractProjection}, there is a parameter DisableMulticompile and methods EndCompile, QueueClass. Do you somehow use them in your code?

score 0 · Answer 8 · 2025-06-24T10:32:10-04:00

EndCompile looks like it would be super helpful! I landed on a different solution, but EndCompile looks like it would do exactly what I want.

Also, thanks for noting QueueClass -- I was directly calling $SYSTEM.OBJ.Compile() which is not ideal :)