UPoC Protocol Advanced Scheduling

[Ted Mech]

We’re trying to stack multiple events in the Advanced Scheduler for a PROTOCOL:upoc thread.  The events are set up on independent schedules but seem to run together:  the 1st in the stack will run on the schedule set for the 2nd.  After bouning the process, sometimes the 2nd event will run, either on the 1st schedule or on its own.  The events are spaced  & the proocessing is limitedso that the schedules don’t overlap.

How do I get each event to run, as scheduled, so that I can use a single thread to handle multiple scheduled events?

Topic

[Mark Thompson]

Ted,

You didn’t mention what version of Cloverleaf you are running.  I believe multiple events in advanced scheduling appears as something “fixed” in the 5.4 release notes.  If you are on an earlier version you might want to schedule using ‘cron’ instead.

- Mark Thompson
HealthPartners

[Ted Mech]

Mark,

Thanks for that info.  We are still on 5.3 but your posting may be the incentive we need to accelerate our 5.4 upgrade.

Thanks,

Ted Mech

[Mark Thompson]

Reviving a very old thread.  On CL 6.2 is there a way to view the Event (aka Description) for messages created by a UPOC timer thread with Advanced Scheduling?  Looked through everything I can find in metadata.  Is there a global value or something else I can check?

- Mark Thompson
HealthPartners

[David Barr]

By event, do you mean the time in the schedule that it ran? I’m not sure what you’re asking. It’s possible that the Proc that created the message needs to populate the event in the message metadata (USERDATA field). What’s an example of an Event for a message?

[Mark Thompson]

In NetConfig, the Advanced Scheduling panel has 3 columns: Description, Recurrence and Procs.  In our case, the thread has multiple entries that all call the same proc (a generic script wrapper).  We are trying to make the proc smart enough to determine which scheduling entry called it.

My thread has these fields defined:

Description “timerTest”, Recurrence “1 * * * * *”, Procs “upocRunScript”

I can see the Description (timerText) in the process log:

[is  :ISEv:INFO/0:        frog1:11/14/2017 12:51:20] *** Next Interval = 41, Event(timerTest|1) time = Tue Nov 14 12:52:01 2017

[pti :even:DBUG/0:        frog1:11/14/2017 12:51:20] tiRegistering TIMER (timerTest) event 0x318d3278 for tid 2

[pti :even:DBUG/0:        frog1:11/14/2017 12:51:20] evRegistering TIMER (timerTest) event 0x318d3278 for tid 2

[pti :even:DBUG/0:        frog1:11/14/2017 12:52:01] Processing TIMER (timerTest) event 0x318d3278

[is  :ISEv:DBUG/1:        frog1:11/14/2017 12:52:01] *** Next Interval = 0, Event(timerTest|1) time = Tue Nov 14 12:52:01 2017

Just wondering if the upocRunScript proc has access to this information anywhere.

- Mark Thompson
HealthPartners

[Author]

Replies