david.ruprecht
Member
My question is regarding the JDE EnterpriseOne Job Scheduler in relation to times zones and Daylight Savings Time. The question is stated after the background information if you are not interested in the details.
Background Information: Our E1 system is setup with UTC as our local time. In other words, our Enterprise server location is where there is zero offset from UTC/GMT. We have essentially setup our system with GMT as our local time. This requires users to be setup not for their time zone but for "System Time" which does not offset any of the displayed times in E1. Instead the time is simply read straight from the database with no offset.
Job Scheduler: When viewing our job scheduler application we use processing options that are set to adjust the job scheduler times for our local time zone and also for Daylight Savings Time.
My question is: Why do we need to use processing options to adjust for our local time zone when viewing the list of scheduled jobs? Why doesn't the job scheduler run based on the adjusted UTC as oppose to the time we are setting the jobs to run at (with local time zone offset)?
An example: When looking at the job scheduler I set the processing options to adjust for UTC-06:00 and also adjust for Daylight Saving Time. This allows me to see all the jobs we have scheduled and at what times. If I schedule a job to run at 06:00 the job will run the next day at 06:00 which is actually not what I would expect. What I would expect that the job should run at 11:00 because that is what the UTC equivalent would be if I was not viewing the list of scheduled jobs. Isn't it the case that the job scheduler will run the scheduled job based on the UTC time the job is scheduled for?
Background Information: Our E1 system is setup with UTC as our local time. In other words, our Enterprise server location is where there is zero offset from UTC/GMT. We have essentially setup our system with GMT as our local time. This requires users to be setup not for their time zone but for "System Time" which does not offset any of the displayed times in E1. Instead the time is simply read straight from the database with no offset.
Job Scheduler: When viewing our job scheduler application we use processing options that are set to adjust the job scheduler times for our local time zone and also for Daylight Savings Time.
My question is: Why do we need to use processing options to adjust for our local time zone when viewing the list of scheduled jobs? Why doesn't the job scheduler run based on the adjusted UTC as oppose to the time we are setting the jobs to run at (with local time zone offset)?
An example: When looking at the job scheduler I set the processing options to adjust for UTC-06:00 and also adjust for Daylight Saving Time. This allows me to see all the jobs we have scheduled and at what times. If I schedule a job to run at 06:00 the job will run the next day at 06:00 which is actually not what I would expect. What I would expect that the job should run at 11:00 because that is what the UTC equivalent would be if I was not viewing the list of scheduled jobs. Isn't it the case that the job scheduler will run the scheduled job based on the UTC time the job is scheduled for?