| Author |
Message
|
| GYR |
 Posted: Thu Nov 18, 2004 6:14 am Post subject: Fixed length question in TDS MRM message |
 |
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
| I have an MRM with a TDS physical format that has a delimiter of $ (don't ask why its the clients idea) when it is parsed fromt he input node it fails saying there is no fixed length associated with said elemens in the format, why is it looking for fixed lengths when the purpoise of have tag delimitation is to make it variable length. I thought i had seen somewhere where you make the elements variable but can't find it now. Thanks for any help. |
|
| Back to top |
|
 |
| GYR |
| Posted: Thu Nov 18, 2004 6:21 am Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
| It ok i found it it hink in .mxsd properties to set to variable length element, but the trace is still suggesting it should have a length surely thats the point of variable length is its not fixed or am i interpreting this wrong. Any ideas welcome |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Nov 18, 2004 6:33 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| It's the TDS Data Element Separation property of a complex type or group that you need to set. The default is 'Fixed Length', sounds like you want 'All Elements Delimited'. |
|
| Back to top |
|
|
| GYR |
| Posted: Thu Nov 18, 2004 7:17 am Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
Shanson - that what i set when i said i found it but the actual bit says "Variable Length Elements Delimited" but is still asking for element length values in the trace as if it is fixed still
example
Message Set Name : 'GTS_tds_Set'
Message Set Level : '1'
Message Format : 'TDS1'
Message Type Path : 'TDG_HENKEL_ORD_GTS_IN'
Review further error messages for an indication to the cause of the errors.
2004-11-18 14:27:05.930151 3216 ParserException BIP5421S: Tagged/Delimited String Format (TDS) parsing error
Current message : 'TDG_HENKEL_ORD_GTS_IN'
Path to current element : '/TDG_HENKEL_ORD_GTS_IN/54^HID_RJRECORD'
Offset from start of message : 0
See following errors for more details.
2004-11-18 14:27:05.930333 3216 ParserException BIP5422E: No Length associated with fixed length data
and i had removed both flow and message set from the exec groups and redeployed. |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Nov 18, 2004 8:21 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| I don't understand why the error is appearing, but in general should only use 'variable length elements delimited' when you have a mixture of fixed length fields and delimited fields within the same complex type. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Nov 18, 2004 6:08 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Make sure your message set dictionary file is updated before deploying to the broker. It'd be better to give an example of your input data and list down the properties for each element/complex type.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
