Tcl Question

[Jared Miller]

I am using the following to kill messages with FCC in PV1-18:

if {[cequal [crange $segment 0 2] PV1]} {

set fieldList [split $segment $field_sep]

set pv1_18 [lindex $fieldList 18]

         

   if {[cequal $pv1_18 “FCC”]} {

lappend dispList “KILL $mh”

return $dispList

} else {

lappend dispList “CONTINUE $mh”

return $dispList

}

We are doing integrated testing on our Star ADT upgrade to 2.2b and our test merges (A34)  are getting killed even though there is no PV1 segment in an A34.  Why would that be happening?

Topic

[David Barr]

Are you sure the messages are being killed and not just going to the error database?  Do you see the same problem when you run messages through the testing tool?

[Tom Rioux]

From what I can tell, this is merely an excerpt of a larger script.  What happenns below the first IF statement if the segment is not a PV1?  Is there any other KILL statements in the proc?  It may be hitting a KILL statement later on in the script.  If the A34 doesn’t have a PV1 then it shouldn’t even be hitting this part of the code.

Thanks….Tom

[Alan James]

Try using the kill_msg.tcl proc (attached) with the following arguments:

{PASSCOND ~FCC} {SEGNAME PV1} {FIELDNUM 1} {SUBFIELDNUM 0}

[Alan James]

Ooops!  Those arguments should have been {PASSCOND ~FCC} {SEGNAME PV1} {FIELDNUM 18} {SUBFIELDNUM 0}

😳

[Jared Miller]

Thanks Alan!  That worked really nice for me.  Thanks everyone else for their thoughts as well!

[Eric Sligh]

Would that work like this:

{PASSCOND ~REGEX@NULL} {SEGNAME PV1} {FIELDNUM 1} {SUBFIELDNUM 0}

or

{PASSCOND ~@NULL} {SEGNAME PV1} {FIELDNUM 1} {SUBFIELDNUM 0}

[Author]

Replies