Built in Resend OB Message in 5.6

Unless you have a special-case need for handling ACKs, you can safely use the built-in resend functionality in 5.6+.

The issue that kept me from embracing it readily was that we stack the following 2 procs in the resend stack:

tps_check_resend_count

tps_resend_ob_msg

The first proc (tsp_check_resend_count) is an argument driven proc to trigger emails/pages when certain resend thresholds are hit.

Here is a typical arument example:

In this example alert notification would occur at the resend count thresholds of {5 15 30 60}.  Since the resend timeouts are set at 60 seconds that would be at 5 minutes of retires, then 15 minutes of retries, etc.

I was concerned that I would be challenged with replacing this capability if I attempted to use the built in resend on cloverleaf 5.6 and I needed all my available time for other things.

I would be interested to here if the built in resend logic in cloverleaf 5.6 can be used and still allow me to use an alertanative method for triggering resend count alerts.

I believe much thought has been given on expanding and improving the cloverleaf alert tool and would like to know if cloverleaf 5.6 has resend count alert capability.

I think the built-in resend feature will be very helpful for newbies not to have to learn the more complex ack handling of the past with the recover_33 procs working together.

I’m my case we had already gone through that learing curve and for us retrofitting exceeds our manpower with such a high number of interfaces.  

Our version of retrofitting is to make the change on future interfaces but not existing interfaces.

We switched most of our interfaces over to utilize the built-in resend functionality, and modified any ACK handling, or resend count procs to be employed in the new paradigm.

Jim Cobane

Henry Ford Health

When writing your own resends be sure and handle the new OBMSGID key if there else you will get serious memory leaks

if {[keylget args OBMSGID obmh]} {lappend dispList “KILL $obmh’}

or something similar

Greetings,

Just a caveat here for auto resend in CIS5.6:  it only works for PDL style TCP/IP protocols using the mlp_tcp.pdl driver.  We had standard (native) TCP/IP bridges (localhost) connections to do site to site or intra site passing of messages and discovered that state 16s do not persist once the connection is cycled.   This was reported as a bug and may be fixed in 5.7 (would have to check the release notes).

To implement resend capability for other than PDL style you need to use recover style procedures.

Enjoy.

Jim Cobane wrote:

Would you be willing to share how you are doing your resend count in the new paradigm.

I have a resend count proc but once I choose the automatic resend I can no longer call that proc from the same place.

Russ,

I stand corrected.  The threads that we are doing the resend counts on are using a REPLY GEN proc (that has been modified to use OBMSGID).

Jim Cobane

Henry Ford Health