| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Set not matching bit stream? |
« View previous topic :: View next topic » |
| Author |
Message
|
| vixenscup |
 Posted: Thu Aug 12, 2004 11:44 am Post subject: Message Set not matching bit stream? |
 |
|
Newbie
Joined: 13 Nov 2003
Posts: 9
|
Hi,
I have created a message set that has a TDS physical format. The message is a SAP IDOC that has one control record (EDIDC40) and three other segments. One segment is a child of another which is the child of the third. Basically like this....
EDI_DC40......... (non-repeating)
E1MBXYH....... (non-repeating)
-- E1MBXYI....... (optional repeating)
----- ZE1CLAS........ (optional repeating)
The input bit stream contains the control record, one E1MBXYH segment, one E1MBXYI segment and five ZE1CLAS segments. I am receiving the following error..
"CTDSParser::ParseCompoundElement file:/build/S210_P/src/cpi/pwf/tds/tdsparser.cpp line:1056 message:5437.WMQIv210 Missing a group indicator within a fixed length environment , E1MBXYI_CompoundType, E2MBXYI001 , 3614,
2004-08-12 11:20:23.913600 10 >> ParserException BIP5437E: Group Indicator missing in the bitstream
The TDF parser could not parse the data in the bitstream for Fixed Length compound type, E1MBXYI_CompoundType, no Group Indicator, E2MBXYI001 , was present in the bitstream at offset 3614.
The message model definition does not match the bitstream. Check that your model definition is correct and if so, update your bitstream data accordingly. "
At offset 3614 there is no Group Indicator and rightly so. There is only one occurance of E1MBXYI in the bit stream. How do I configure the message to understand that this segment can repeat but not always??? How do you tell it that it is optional? This error goes away if I redefine the element as Repeat = NO. Does anyone out there know what I am doing wrong?
Thanks in advance for any help! |
|
| Back to top |
|
 |
| wooda |
| Posted: Fri Aug 13, 2004 1:03 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
You appear to have modelled this as TDS fixed length. (according the error)
Fixed length is very simple. It chops up the message in fixed lengths. It doesn't look at the message contents to determine what field it is parsing.
It uses the model to determine what it is parsing.
If you insert a Group Indicator then it doesn't use it to determine what field is coming it just expects one to be there.
If you have a repeating field it HAS to repeat a fixed number of times.
I would recomend you model your message using a tagged format (since it has tags) and this will allow you all the flexibility you need. |
|
| Back to top |
|
|
| vixenscup |
| Posted: Thu Aug 19, 2004 5:55 am Post subject: TDS Modeling issue |
|
|
Newbie
Joined: 13 Nov 2003
Posts: 9
|
| But I don't have any delimiters or tags on the individual fields. Just the segments have names. How would I go about defining this data using Tagged Delimited? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
