filter based on fields

Here’s an old one that will get you going.  Important thing is the foreach construct for looping through the segments in the message.

run {

           keylget args MSGID mh

           set msg [msgget $mh]

           set fld_delim [cindex $msg 3]

           set disp “CONTINUE”

           # Find PV1 segment, get disch date from it.

           foreach elem [split $msg “r”] {

     if { [cequal [csubstr $elem 0 3] “PV1”] } {

                          set pv1_list [split $elem $fld_delim]

                          set disch_date [lindex $pv1_list 45]

                               if { $disch_date > 0 } {

                                  set disp “KILL”

                                  break

                       }

                 }

           }

Change this line:

if {{$PV1_41 == “PRE”} || {$PV1_18 == “REF”} || {$PV1_18== “RCR”}} {

to

if {[cequal $PV1_41 PRE] && ([cequal $PV1_18 REF] || [cequal $PV1_18 RCR])} {

Hope this helps,

-mh

I think it has to do with variable substitution.  The curly braces would be forcing tcl not to substitute the $ with the actual value of the variable.

I would pay attention though, to what Michael is recommending above in your use of “ands” (&&) and “ors” (||).

You just need to replace the braces with parentheses:

if { ($PV1_41 == “PRE”) || ($PV1_18 == “REF”) || ($PV1_18== “RCR”) } {

Steve

You will need to use the example the Michael gave you.   In the following example:

if { ($PV1_41 == “PRE”) || ($PV1_18 == “REF”) || ($PV1_18== “RCR”) }

…this will kill the message if ANY of the conditions are met.  So you could have PV1_41 equal to “PRE” and PV1-18 equal to ABC and it would still kill the message.

In Michael’s example below:

if {[cequal $PV1_41 PRE] && ([cequal $PV1_18 REF] || [cequal $PV1_18 RCR])}

…this will kill the message ONLY if PV1_41 ==”PRE”  AND PV1_18 == “REF” or “RCR”

Hope this helps….

I agree with Michael’s answer with the exception that you should use the string commands now and not the “C” commands.

In other words:

if {[string equal $PV1_41 PRE] && ([string equal $PV1_18 REF] || [string equal $PV1_18 RCR])}

The string commands run several orders of magnitude faster than the old TclX “C” commands

You should NEVER use numeric compare in place of string compare (==, !=, etc.).  It is very inefficient and may give an incorrect response.

Also, NEVER loop if you can help it!  The lregexp command to get the PV1 segment is MUCH more ergonomic than looping through all of the segments.  FWIW, in place of lregexp which is not a core command you can now use lsearch if you are on Tcl 8.4 (Cloverleaf 5.4.1 or higher)treated as lieteral $PV1_41, not as a variable.

As for why the curly braces did not work.  When you quoted with the curly braces the variables were not evaluated.  For example, $PV1_41  was  treated as a literal, not a variable.

Just my $0.02 worth

Just look what you can learn by posting your old Tcl out there!!!

(i.e. You’re a rusty old integrator, you don’t read e-mail for comprehension and you better get current on the Tcl shizzle!)

I had a feeling Charlie was gonna say that. 🙂

Somehow I have this mental thing with using “[string equal” when “[cequal” is shorter. (One word instead of two). Too bad we can’t alias commands.

As Dave suggests, I too, need to get current (and like it and use it) with the Tcl shizzle.