skipping the escape characters.

[Hina Siddiqui]

Hello everyone,

One of my logic is a straight mapping of FT1 to FT1 (charges messages).

My inbound message has “&” in it which is a sub component delimiter. But i want it to be passed as is.

I have created a pre and post proc to map the “&” to //T// and then back to “&” . It worked for one message but when i try to volume test it with 5 or 10 messages, it doesnt work.

Can anyone please suggest a method to handle this in the xlate itself or any other method.

Thanks

Hina

Topic

[Jim Kosloskey]

Just a point of clarification, the typical escape character is a not a / and the escape for a subcomponent (typically the &) is T not //T//.

In this case it does not matter since you intend to put the subcomponent character back but you should still use the proper escape sequence.

Make real sure the receiving system is not affected by the misplaced & in the message.

Also be aware the FT1 segment does have fields with components which could legitimately have subcomponents. Could it be you reallly just need to use subcomponent notation (or perhaps PATHCOPY) inside your Xlate?

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

Why not simply change the separator characters?  Or, you can change the & to the word “and”

Jim is correct in the escape characters, however not all vendors will convert them the way they should.

[Author]

Replies