"Hint"? It looks like the millisecond values aren't being returned correctly in this one case, or does this error refer to 2 entries spaced (just a bit more than) 12 hours apart?
So that would cancel out a problem with some 12-hour overflow occuring, it is just a timing event. The millisecond values retrieved from some UNIX variants aren't always that accurate, so it might just be a cross-process timing issue - which explains why this is a warning and not a fatal error. I see shades of Thiotimoline here.
I don't know much about that as I never got this error but this is part of unix(AIX) and not related to DataStage. As it says the description is the man page of gettimeofday.
The two values in the warning are not related to execution time but they are current time of the server.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.