Killing a Message using PASSCOND logic

[Don Anderson]

I

Topic

[Michael Hertel]

It appears you have a space before and after the value.

I don’t use this proc but you may need to tweak your PASSCOND.

Maybe {PASSCOND ~REGEX NWDiscontinued }

Or {PASSCOND ~REGEX” NWDiscontinued “}

Or something like that, you get the idea.

> NWDiscontinued <

is different than

>NWDiscontinued<

That is why I think it is a space character issue.

Also it looks like your example segment and the example parse are not the same. Based on the example parse, I would expect the segment to look like

ORC|NW|298768133^HNAM_ORDERID| NWDiscontinued ||Discontinued||^Q 04

[Charlie Bursell]

I agree with Mike but we would also have to see the proc in question.

Looks like one of those lego jobs where you pass in a multitude of arguments which in itself makes it more error prone

[Mike Keys]

Lego job?

Hasn’t the “kill_msg” proc been around for quite awhile? I learned about it from a McKesson Cloverleaf instructor back in 2007.

[Charlie Bursell]

The hcitpsmsgkill which Rob Abbot wrote and I later modified has been around since the very early days of Cloverleaf.  It accepts no arguments.  It uses CONTEXT to issue either KILL or KILLREPLY.

I don’t know about a proc named kill_msg.  I referred to it as a lego job since it seems to accept so many arguments to build on.  Just a joke on my part, no intent to offend.

If this is your preferred proc, go for it.  I was just saying I could not answer the OP’s question without seeing the proc.

[Mike Keys]

Charlie…none taken.

Those arguments are part of the kill_msg proc. I use it occasionally for pre-proc filtering.

[Author]

Replies