Issue with resend_ob_msg

Mike,

You will need a tcl proc that handles the reply you receive.

Mike,

Here is a proc to check the replies (written for 5.6, using the OBMSGID handle).  Modify as you see fit.

Hope this helps.

Jim Cobane

Henry Ford Health

Hi Mike,

As you are using ‘resend_ob_msg’, I assume you have all the ‘recover_xx’ procs available.

You can use the ‘validate_reply’ in TPS Inbound Reply. You can define your own VALIDEXP and set RETRIES to 0 so no message is resend. You can even set ERRORDISP so the error-message is written to the log instead of to the error-db.

I think this is what you are looking for.

Mike,

If you are not on version 5.6 (or greater), then the proc will need to be modified to use the older logic of the saved ob message handle, rather than the OBMSGID handle. As Robert pointed out, you should have the recover_xx procs available, and you can use the ‘validate_reply’ proc, modifying as needed.  

Jim Cobane

Henry Ford Health

Mike,

Try using the ‘validate_reply’ proc instead of the ‘checkHL7_reply’. And have a look at the code (and documentation/comments) of the ‘validate_reply’ proc: it explains a lot.

I am wondering if you have the recover_xx proc-file. I’m using recover_38.tcl right now and all the procs have the number in their name: save_ob_msg_38, resend_ob_msg_38, validate_reply_38 and kill_ob_save_38. Either your proc-names have been changed or you are using an old version. I think you can get the latest version of recover_xx through support. Not sure if I can post these freely.

Mike,

With 5.6, you can turn on the ‘Resend OB message” option under the “Timeout Handling…” and remove the save_ob_msg and kill_ob_save procs from your configuration.  The engine automatically saves a copy of the outbound message (to state 16, hence the use of the OBMSGID logic in the proc), and the checkHL7_reply proc uses this saved message and also kills the saved message handle after it’s processed the reply.

Our threads are configured this way.

Hope this helps.

Jim Cobane

Henry Ford Health

One and All,

Recollecting from the Annual Conference of 2009,  the only official recover procs have either 33 or 56 in the name – anything else is not an official distribution from (now) Healthvision/Lawson.  That is names = recover_33.tcl or recover_56.tcl.  I usually keep an original unspoiled version in our shop and then clone/modify as needed.

There are myriads of clones and creations out there in user-land so buyer beware.  These are not official versions.

Enjoy.

in case of receiving system NOT returning a reply at all …what would be the best method of handling this situation.  Does not seem that 56 addresses this situation.

Thanks

There is the ability to wirte a TCL proc to proactively do whatever you want when a message times out and gets resent.

For example, you could write each resent message out to a file or simply increment a counter if that is all you need.

Here is one of my old posts illustrating how a resend TCL proc sends out an alert once a message is resent x number of times, which you could use as a tangible example and leverage for you own needs:

    <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1862&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1862

You might also want to read this URL since resend procs can only be used if opting not to use the built in resend capability with later versions of cloverleaf from what I currently understand:

    <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=4212&highlight=tspcheckresendcount&#8221; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=4212&highlight=tspcheckresendcount

Anyway this is the main reason we are still on the older method plus no need for us to retrofit everything.

Our tps_check_reply_2 proc does some of the things you are asking about like it can write the NAKed message to a file and has an argument to keep on going after skipping that NAKed messages or shutdown completely, plus send out alerts if desired.

Here is a URL where I already posted our tps_check_reply_2 proc:

    <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1997&&#8221; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1997&amp;