Originally posted by: jryan76

Hi,

I'm finishing off a version 9 Tradacoms order map and am running order files through my local copy of WTX. When I run the WTX map with the file in question it fails and I get the following errors in my trace file.

(Level 2: Offset 1338, len 0, comp 1 of 3, #1, DI 000000FC:)
Data at offset 1338 ('END=3'...') does not match INITIATOR 'MHD='
of TYPE X'00C0' (MHDR Envelope Control TRADACOMS EDI).

(Level 1: Offset 1338, len 0, comp 5 of 6, #1, DI 000000FC:)
Data at offset 1338 ('END=3'...') does not match INITIATOR 'EOB='
of TYPE X'00C2' (EOB Envelope Control TRADACOMS EDI).

(Level 2: Offset 90, len 3, comp 9 of 8, #2, DI 00000010:)
TERMINATOR ('Terminator Delimiter Control TRADACOMS EDI') found; has value ''<CR><LF>'.

(Level 0: Offset 0, len 1338, comp 1 of 0, #1, DI 000000FD:)
Data at offset 0 ('STX=ANA:1+501354...') is INVALID data of TYPE
X'0003' (Inbound Interchange EDI).

Looking at the sample order file problem sppears to be that the END segment has a terminator of '. All other segements have a terminator of '<CR><LF>. Does WTX look at the first terminator and expect all others to be the same?

I've set up my list of terminators to cater for both ' and '<CR><LF> so I'm confused as to why this is happening. I know I can set up a literal terminator on the END segment but would like to avoid that if possible.

The trace file is attached.

Any help or advice would be appreciated.

Thanks.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: jvanboga

Normally the trees would look for the first terminators and use the thru the rest of the file.

I notice your terminator appeared to be defined a '<CR><LF>. If so and the reset are <CR><LF> you'll have a validation problem. Also, if the value ' is part of the delimiter you may want to confirm that it is part of the delimiter element's valid values.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange