Posted: Thu Jul 03, 2008 12:59 am Post subject: dateTime elements gets added 1 hour when writing bitstream
Disciple
Joined: 22 Jul 2005 Posts: 150 Location: Stockholm, Sweden
Hi,
I'm having an issue regarding dateTime elements modelled in a messageSet.
Our flow logic is as follow:
-Parse the message using a FIN messageset (correct time)
-Copy the structure to an XML inhouse standard format (correct time)
-Store the isf to DB (correct time)
-Read the isf from DB and parse it (correct time)
-Copy the ISF structure to the FIN message type in the MRM domain (correct time)
-Call ASBITSTREAM() on the FIN MRM structure to BLOB'ify it (Time gets added by one hour)
The reason for running the ASBITSTREAM and not writing directly to queue is because we have extra data that is not modeled in the messageset.
I've played around with tz settings on the FIN messageset which doesnt seem to change anything at all. The messageSet is by default using the broker local timezone which is GMT +1.
mqsiservice -t reports the correct timezone as well as the date command (solaris)
Were running the 6.0.0.4 version of MB
I'd appriciate all suggestions on where to start looking. _________________ IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower
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