| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS ints with leading zeros |
« View previous topic :: View next topic » |
| Author |
Message
|
| chrisc |
 Posted: Tue Jan 15, 2008 4:00 pm Post subject: TDS ints with leading zeros |
 |
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
Hi everyone,
We are doing some Broker 5 (CSD8) development work - Windows for development, z/OS for test / prod - using some tagged delimited message sets provided by a third party.
We've come across a problem where the field contains an int value represented as "0034" on input. We need to be able to stream this out again in the same form, i.e. padded with leading zeros to length 4, but it is always outputting as 34 only.
The logical type is int, and the physical properties of the field are:
Tag: abc
Data pattern: blank
Length: 4
Justification: Right justify
Padding character: '0'
This field is used in a Type with a complex type (basically a string), followed by the field above, followed by another complex type (combination of strings). The Data Element Separation is Tagged Delimited, no group indicator or terminator, but a Delimiter has been specified. The Tag Data Separator is also specified (as opposed to the Length of Tag).
The feedback we received from the vendor was to check the "Observe Element Length" checkbox on the type, but I have tried this and it made no difference. The IBM website indicates that this checkbox only affects the messages where the Data Element Separation is "All Elements Delimited".
Does anybody know what needs to be done to support having the integer value padded with leading zeros in a TDS message? I don't want to just arbitrarily change the vendor's message sets, but the people in these forums seem to be better versed in the intricacies of these things than the vendor is! 
Any help would be greatly appreciated!
Thanks,
Chris |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Jan 16, 2008 1:32 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Observe Element Length should work with Tagged Delimited. ( so the online docs are not accurate there ).
Not sure why it is not working for you. Another solution would be to change the element's simple type from integer to string. |
|
| Back to top |
|
|
| chrisc |
| Posted: Wed Jan 16, 2008 7:57 pm Post subject: |
|
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
Hi Kimbert,
Thanks for the response. It looks like it might be a limitation in v5, because apparently it definitely works in v6.
It looks like your suggestion of just using a string rather than an int may be the way to go here. I just gave it a try and it came out fine (as you would expect).
Thanks,
Chris |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jan 17, 2008 2:10 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Yes, I investigated this. It was only available for use with the TLOG messaging standard in v5.
btw, my colleague was asked an almost identical question via email yesterday. That query involved a SWIFT message set supplied by Dublin. Are you part of the same group, or is this just a bizarre coincidence? |
|
| 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
|
|
|
|
