Originally posted by: paul.brett
This is where it goes wrong:
(Level 2: Offset 7, len 9, comp 2 of 2, #1, DI 000000000002:)
Data at offset 7 ('9291316~B') was found to be of TYPE
X'0010' (TSCtrl# Element V4010 ANSI EDI).
(Level 2: Offset 7, len 9, comp 2 of 2, #1, DI 000000000003:)
Type X'000A' (ST Segment V4010 ANSI EDI) is known to exist.
(Level 1: Offset 2, len 14, comp 1 of 15, #1, DI 000000000003:)
Data at offset 2 ('*204*9291316~B') was found to be of TYPE
X'000A' (ST Segment V4010 ANSI EDI).
(Level 1: Offset 2, len 14, comp 1 of 15, #1, DI 000000000004:)
Data at offset 2 ('*204*9291316~B') was found to be of TYPE
X'0009' (Segment V4010 ANSI EDI).
(Level 1: Offset 2, len 14, comp 1 of 15, #1, DI 000000000004:)
Type X'0008' (Transaction #204 Inbound Partner Set V4010 ANSI EDI) is known to exist.
(Level 1: Offset 16, len 0, comp 2 of 15, #1, DI 000000000004:)
Data at offset 16 ('2**CIKM****16020...') does not match INITIATOR 'B2'
of TYPE X'0011' (B2 Segment V4010 ANSI EDI).
(Level 1: Offset 16, len 0, comp 2 of 15, #1, DI 000000000004:)
COMPONENT number 2 of TYPE X'0008' (Transaction #204 Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.
'9291316~B' is read in as the TSCtrl# Element, so the data does NOT match the Typetree definition.
That said, when I use this Typetree to create the output, no delimiter is placed in the output, and I get:
ST*204*9291316B2**CKIM
Where did the Typetree originate? If it was supplied by IBM, I recommend you open a Service Request.
Thank-you.
Paul
Follow me on Twitter
#DataExchange#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender