|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Suppress the Trim on input property at field level in TDS |
« View previous topic :: View next topic » |
Author |
Message
|
MQEnthu |
Posted: Wed Dec 07, 2011 7:34 am Post subject: Suppress the Trim on input property at field level in TDS |
|
|
 Partisan
Joined: 06 Oct 2008 Posts: 329 Location: India
|
Hi All,
Message: Fixed length
Wire format: TDS
In the TDS message set properties, there is option to set the "Trim on input" which describes how the trimming has to be done. Mine in this case is set to the default value "Leading and Trailing Whitespaces". i.e. it trims the leading and trailing white spaces of the fields with a physical type of Text.
It trims the spaces (leading/trailing) of the field of data type INTEGER as well. My requirement is that I do not want to trim the leading/trailing spaces, instead throw error for integer fields if they spaces at end.
I know that by setting the property to "Trim Padding Chars", we can avoid trimming the spaces in integer characters (instead it trims the padding characters mentioned).
However I do not want to use this solution as message set contains the many message definitions and we do not know the impact of chaning this property at the message set level on other integrations using diff. msg definitions.
I am checking if we can suppress this property at the field level. Suppose, if I just want to not to trim a perticular field, can I do it.
Hope my question is clear.
Please help . _________________ -----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
Back to top |
|
 |
kimbert |
Posted: Wed Dec 07, 2011 8:10 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
I'm afraid that TDS does not offer an element-level trimming option. Your best bet is to create another message set for use by this integration only - or else rely on your regression tests to catch any accidental changes in the other integrations.
FYI, the new DFDL parser in v8 will be able to do exactly what you require - every DFDL property can be either be defaulted or specified on a per-element basis. |
|
Back to top |
|
 |
MQEnthu |
Posted: Wed Dec 07, 2011 8:27 am Post subject: |
|
|
 Partisan
Joined: 06 Oct 2008 Posts: 329 Location: India
|
Thank you Kimbert for the info.. _________________ -----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
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
|
|
|
|