Arguments for kill_msg proc

[Don Anderson]

The argument is choking on a facility that has a space in it’s name. Is there a special character I can substitute for the space. When placed in the argument field it looks like a carrage return, the rest of the argument after the space drops to the next line

{PASSCOND REGEXGREENVILLE|INTERMOUNTAIN|LEXINGTON|PHILADELPHIA|PORTLAND|ST

LOUIS|SHREVEPORT|SPOKANE|TAMPA} {SEGNAME PV1} {FIELDNUM 39} {SUBFIELDNUM 0}

Topic

[Jim Kosloskey]

I don’t know this proc but it looks like it is using a keyed list.

If you surround the value associated with the key with double quotes or curly braces I think it might work.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Don Anderson]

What I found was the entire list including the regex  must be with in double quotes, putting curleys or double quotes around the value in question didn’t work

{PASSCOND “REGEXGREENVILLE|INTERMOUNTAIN|LEXINGTON|PHILADELPHIA|PORTLAND|ST

LOUIS|SHREVEPORT|SPOKANE|TAMPA”} {SEGNAME PV1} {FIELDNUM 39} {SUBFIELDNUM 0}

[Jim Kosloskey]

Don,

That is the key value that you encapsulated. The pieces of that value (the things between vertical bars) are just that pieces.

The key is PASSCOND  and the value is REGEXGREENVILLE|INTERMOUNTAIN|LEXINGTON|PHILADELPHIA|PORTLAND|ST LOUIS|SHREVEPORT|SPOKANE|TAMPA.

White noise (a space for example) delimits the ke/value set of a keyed list. So the space in between ST and LOUIS told Tcl that the keyed list value ended there and that broke the syntax.

By using double quotes around the value like you did allows Tcl to treat the entire value as a single value and ignore in essence the white space imbedded.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Don Anderson]

Thanks, An explaination like that really helps in my over all understanding

[Author]

Replies