tcl Scheduling

[Keith McLeod]

I have a request to adjust the priority of ADT_A03 message during a given time range.  For instance (midnight to 2 am)… During this time I need to set the priority of the ADT_A03 message so that all other messages will not be bottlenecked. I am assuming I would put the tcl proc into the ADT_A03 route and check the time for each ADT_A03 message that passes and compare to the scheduled start and stop time of the range. Has anyone written something to do this? Or have some suggestions regarding this.  I can’t say I am in favor of this, however they would like to test…..

Topic

[Michael Hertel]

You’re having the old “auto-discharge problem”, huh?  🙂

We have IDX/GE and had them throttle back the discharges on their side.

I have explained that I do have the ability to prioritize the messages in the engine (by setting metadata on the message), but that isn’t going to help if the receiving system has received all the messages and is busy chewing away on them.

A process in Cloverleaf is singleminded. It can’t work on something, put it on hold and come back later. If you hold, everyone else in the process holds.

The best you can do is to route the A03 to an outside thread in it’s own process, hold, then feed it back to the original outbound thread.

-mh

[Kevin Scantlan]

We do 3 things to handle this:

1.  We have auto discharges come out of a separate IDX interface different than the regular ADT outgound interface.

2.  The inbound thread that accepts these auto discharges is in it’s own process and we have a script in the inbound TPS called “slow_down” that delays the message for 1 second.

3.  Before the message is put into the stream with messages from the regular ADT feed, we lower the priority of the auto discharge message.

[Author]

Replies