UTC to AEST
Moderators: chulett, rschirm, roy
UTC to AEST
Hello All
Source : File
Target : Table
UTC Time: Timestamp (yyyy-mm-dd hh:mm:ss)
I have a reference table where i can get the offset numbers such as 11 or 10 based on the range lookup with the source data.
Is there any inbuilt Datastage function i could use to add the offset numbers with the input time stamp to get the AEST ?
Any suggestion ?
Source : File
Target : Table
UTC Time: Timestamp (yyyy-mm-dd hh:mm:ss)
I have a reference table where i can get the offset numbers such as 11 or 10 based on the range lookup with the source data.
Is there any inbuilt Datastage function i could use to add the offset numbers with the input time stamp to get the AEST ?
Any suggestion ?
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There is no such built-in function. For a small number of rows, where performance isn't a big issue, you could make a call to any of the web services out there that can effect this conversion.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Thanks Ray for cautioning.
In this office somehow a manual process has been implemented as someone who physically update the reference table to get the offset. This table will always (I wish always) have the data for 2 years ahead. So it should be alright as far the data is being updated in time. To handle the risk, i am storing the original value too. In case the reference source fails to update the data, still a manual update can fix the issue.
Again thanks Ray for your comment.
In this office somehow a manual process has been implemented as someone who physically update the reference table to get the offset. This table will always (I wish always) have the data for 2 years ahead. So it should be alright as far the data is being updated in time. To handle the risk, i am storing the original value too. In case the reference source fails to update the data, still a manual update can fix the issue.
Again thanks Ray for your comment.
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.