TimeStamp Formatting
Posted: Thu Feb 09, 2006 1:12 pm
I am having trouble formatting the timestamp in the manner I need.
In the database, the timestamp is being formatted as
%yyyy-%mm-%dd %hh:%nn:%ss.6
THe datastage project default is
%yyyy-%mm-%dd %hh:%nn:%ss
I have tried overriding the timestamp format at the job level(Job properties/defaults tab) to read
%yyyy-%mm-%dd %hh:%nn:%ss.6 (I also tried %yyyy-%mm-%dd %hh:%nn:%ss.%6 and %yyyy-%mm-%dd %hh:%nn:%ss.xxxxxx) as the documentation suggests.
However, I don't feel that the override is working, because if I call a row generator to a transformer, and in the transformer specify current timestamp --- it gets created in the format %yyyy-%mm-%dd %hh:%nn:%ss without the 6 digits of microseconds after it that I have specified in the job defaults tab.
This causes me a problem because when I try to read the timestamp from the database Datastage blows up. My only other option that doesn't involve way too much coding would be to truncate the timestamp in the SQL itself --- though I don't feel I should have to do this.
Any ideas on how I succesfully bring this timestamp in without truncating and without datastage blowing up.
Thanks
In the database, the timestamp is being formatted as
%yyyy-%mm-%dd %hh:%nn:%ss.6
THe datastage project default is
%yyyy-%mm-%dd %hh:%nn:%ss
I have tried overriding the timestamp format at the job level(Job properties/defaults tab) to read
%yyyy-%mm-%dd %hh:%nn:%ss.6 (I also tried %yyyy-%mm-%dd %hh:%nn:%ss.%6 and %yyyy-%mm-%dd %hh:%nn:%ss.xxxxxx) as the documentation suggests.
However, I don't feel that the override is working, because if I call a row generator to a transformer, and in the transformer specify current timestamp --- it gets created in the format %yyyy-%mm-%dd %hh:%nn:%ss without the 6 digits of microseconds after it that I have specified in the job defaults tab.
This causes me a problem because when I try to read the timestamp from the database Datastage blows up. My only other option that doesn't involve way too much coding would be to truncate the timestamp in the SQL itself --- though I don't feel I should have to do this.
Any ideas on how I succesfully bring this timestamp in without truncating and without datastage blowing up.
Thanks