Filter out messages

This can be done in as many ways as you can skin a cat.

Simple create a route going to your destination and route the A01 then create a second thread going to file “/dev/null” and route everything else. This is not perfect, but it is quick and easy.

As John said you can do this as many ways as there are to skin a cat.  However, I wouldn’t bother creating two threads.  I would just create one thread and put a simple tcl proc in the IB tps that kills all messages except the A01’s you want.   Then just forward the A01’s for xlating or whatever.

Hope this helps…

Tom Rioux

You could… but the question is “why?”   I would assume you would want to use the lookup table witin an xlate and not within a tcl proc.  Why route extra messages to an xlate only to kill them?   Way too much overhead.  A simple proc in the inbound TPS will do the trick and it would only have to be a very short one.   Let me know if I can help you in any way.

Hope this helps…

Tom Rioux

You can use a table lookup in a pre-proc filter.

Yup – do that all the time.

We use one proc for all of our filtering and we can lookup if we want.

However, for messages where I can use routing, I use the routing to determine where things should or should not go as this makes things more obvious (IMO) in the GUI and elsewhere.

Use the attached proc with the following arguments:

{PASSCOND A01} {SEGNAME MSH} {FIELDNUM 8} {SUBFIELDNUM 1}

With regards to using a second route to a trash bin thead configured to go to /dev/null, you don’t even need the extra trash bin thread.

You can do a static route right back to the inbound thread and use a hcitpsmsgkill on that route to eliminate everything, then have another route for the ADT_A01 messages.

As stated already there are many valid ways to do this.

I mentioned this one because we used a trash bin thread early on but gravitated away from that method and more often use the one discribed above, which might mean we have a preference for it.