dschlieder
Well Known Member
Finally have all the new DST patches applied to the servers and all of the clients.
If I change a record in an application, it gets the correct time stamp.
If I submit a job to the server, the submitted time is an hour off, the last activity time is correct.
If I submit a job from the server with runube, the times are correct.
When I view a UBE the log file gets the correct time, however the entry in the log file is an hour off.
The date/time on the file is Mar 15 13:38
2792/2660 Thu Mar 15 12:38:43 2007 JDEKNUBE.C4129
d:\jdedwardsoneworld\ddp\b7334\PrintQueue\R55PMWO_FMC0001_674875_PDF.pdf
This is true in a number of the logs as well - the file date is correct but the last entry in the log that caused the file to be updated is an hour off.
Haven't stopped and started the services but I wouldn't think this would be an issue.
We don't use the scheduler so we didn't change the rules for that until a bit ago to see if that would have an effect which it didn't.
Can't stop and start the services until later when we get everyone out but I'm not convinced that this will take care of the issue.
Anyone else seen this? If you fixed it, how did you do that?
Thanks,
Dave Schlieder
If I change a record in an application, it gets the correct time stamp.
If I submit a job to the server, the submitted time is an hour off, the last activity time is correct.
If I submit a job from the server with runube, the times are correct.
When I view a UBE the log file gets the correct time, however the entry in the log file is an hour off.
The date/time on the file is Mar 15 13:38
2792/2660 Thu Mar 15 12:38:43 2007 JDEKNUBE.C4129
d:\jdedwardsoneworld\ddp\b7334\PrintQueue\R55PMWO_FMC0001_674875_PDF.pdf
This is true in a number of the logs as well - the file date is correct but the last entry in the log that caused the file to be updated is an hour off.
Haven't stopped and started the services but I wouldn't think this would be an issue.
We don't use the scheduler so we didn't change the rules for that until a bit ago to see if that would have an effect which it didn't.
Can't stop and start the services until later when we get everyone out but I'm not convinced that this will take care of the issue.
Anyone else seen this? If you fixed it, how did you do that?
Thanks,
Dave Schlieder