Posted: Thu Nov 24, 2005 8:10 am Post subject: Trailing skip count behaviour when a field is null
Novice
Joined: 22 Nov 2005 Posts: 10 Location: UK
I'm trying to use trailing skip count to skip over some bytes in a cwf message.
The message contains several types of fields. The app sending me timestamps doesn't always include the fractional second part. So I tried trailing skip count to skip over the last 7 bytes (the length is always right its just that some times it will be populated,sometimes not)
On the timestamp fields when data is present the skip works fine, but if the field is empty (as in just blanks) the skip count is throwing out of alignment the rest of the message.
I tried modelling the message without the skip and used a string of 7 bytes to follow the 19 byte timestamp and that worked fine.
Joined: 10 Dec 2003 Posts: 14 Location: IBM Hursley
I'm assuming that you are using WBI-MB v5.
It looks like there is a problem (in v5) using trailing skip count and null values in CWF (i.e. 'null permitted' = true)
This problem has been fixed in WMB v6.
If you do not require the null handling support within the MRM, you could try deselecting the 'null permittted' property for this field. (You could also try this to confirm my theory ! )
Joined: 10 Dec 2003 Posts: 14 Location: IBM Hursley
Although if you do disable null handling for this field, you may well run into invalid date/time issues when your field contains only blanks (if you have defined this field to be a DateTime field rather than just a string).
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