|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Whitespaces getting trimmed |
« View previous topic :: View next topic » |
Author |
Message
|
Om |
Posted: Mon Aug 11, 2003 7:25 am Post subject: Whitespaces getting trimmed |
|
|
Novice
Joined: 11 Aug 2003 Posts: 12
|
Hi,
I am loosing whitespaces in one of the fields in a MRM message, while another field with similar settings is keeping the whitespaces.
I need the whitespaces for both these fields.
Settings for these fields are:
Physical Type: Fixed Length String
Lenght Count : 2
Length Units : Characters
Byte Alignment : 1 Byte
String Justification: Left Justify
Padding Character: SPACE
Skip Count: 0
Encoding Null: NULLLogicalValue
InputRoot.MRM.Field1 is ' ' /** 2 blank spaces */
OutputRoot.MRM.Field1 is '' /** whitespaces are lost */
InputRoot.MRM.Field2 is ' ' /** 2 blank spaces */
OutputRoot.MRM.Field2 is ' ' /** keeps whitespaces */
I am not doing any trimming on my end.
Thanks, _________________ -Om |
|
Back to top |
|
 |
scaryjase |
Posted: Mon Aug 11, 2003 9:21 am Post subject: |
|
|
Novice
Joined: 17 Jul 2003 Posts: 22
|
not entirely sure, but i think this is something to do with the padding character specified for the field. try changing it from space to null (or vice versa!!) _________________ scary |
|
Back to top |
|
 |
Craig B |
Posted: Wed Aug 13, 2003 7:37 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003 Posts: 316 Location: UK
|
In the last update, the respondant said that they were not sure in their answer. Their answer was correct in that the MRM-CWF parser does trim the padding character from its fields when it is parsing an input message.
The padding character is manily intended to be used on output, such that if you create a message tree with values that are not long enough for the fixed length fields, then it will pad out the value (according to Justification of the field) with the padding character. Therefore, the MRM-CWF parser on parsing an input message does the converse operation where it trims the padding character from the parsed value, according to the justification of the field.
The MRM-TDS parser gives the choice as to whether the padding character is trimmed from fields when parsing. Its the shame that the MRM-CWF parser does not offer the same option. _________________ Regards
Craig |
|
Back to top |
|
 |
Om |
Posted: Wed Aug 13, 2003 9:08 am Post subject: Thanks Craig |
|
|
Novice
Joined: 11 Aug 2003 Posts: 12
|
You are right, Craig.
It works after I changed the padding character to NUL. _________________ -Om |
|
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
|
|
|
|