saving discarded messages

Globalize myfileID, and make sure the “Run Translation Procs in start-mode” is enabled for the process’ option.

Roman,

Here is another thought:

Why not send the filtered message to another thread which is your error file thread (file protocol maybe)?

You still need a filter proc (there are generic ones around) but let Cloverleaf manage the I/O, get the assured delivery, have SMAT, all that good stuff.

Jim Kosloskey

Roman,

Yes that is one way.

One route checks if the message were to be filtered and if so, sends the message on to the error file thread.

The other route checks the same message and if it is to be filtered, kills the message.

So one COPY of the message gets killed, another gets routed to the error file thread.

Another way is to write a Tcl proc that dynalically changes the message routing – but that is not commonly done.

Jim Kosloskey

I used a trxid proc to filter out charges to either pass through to the billing system or to be written out to an error thread.  I then crated the routes that look for the trxid’s defigned in the proc.  Has worked great and is easy to follow.  Below is the code.

######################################################################

# Name: charge_route

# Purpose:

# UPoC type: trxid

# Args: msgId = message handle

# Returns: The message’s transaction ID

#

# Notes:

# The message is both modify- and destroy-locked — attempts to modify

# or destroy it will error out.

#

proc charge_route { mh } {

   set datList [datlist]

   set gh [grmcreate -msg $mh hl7 2.3 cerner23 dft]

   set dh0 [grmfetch $gh {0(0).PV1(0).00133.[3]}]

   set myent [datget $dh0 VALUE]

   set ffour [string range $myent 0 3]

   if { [string compare $ffour “MLMI”] == 0 } {

      set trxId “LTHS”

   } else {

      set trxId “HBOC”

   }  

   grmdestroy $gh

   hcidatlistreset $datList

   return $trxId ;# return it

}