Stop Process when message hits Error Database

[Gordon Koch]

I have seen a few threads related to this topic, but have not seen a solution put in place where a process (which includes only the thread that should be down) is stopped when a NAK hits the Error database for that thread. I have tried to include the following in tps procs for TPS Inbound Replies in the Outbound tab – Inbound Replies pane (where the message is successfully put in the Error db) and in Error Database Procs on the Properties tab:

exec hcicmd hcienginestop -p <process>

but the proc fails on the above line.

I have seen it posted where a shell script would stop the thread, but how is the Error DB interrogated?

Any examples of this scenario working for others would be greatly appreciated.

To note, an Alert was set up to stop the process, but this did not work in a consistent fashion.

Thank you.

 

Topic

[Charlie Bursell]

I have always created a shell script which I placed in the site scripts directory so it is the path and then put the hicienginestop command in there to run in the background.

When you exec this from the engine you must make sure the process does not receive any more messages since the stop command may take a while.  You can do this by just not returning from the proc.  You will have to take care of messages in the database afterwards.

[Author]

Replies