Daylight saving affects VP scheduled reports

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • campb9
    Member
    • Apr 2011
    • 3
    #1

    Daylight saving affects VP scheduled reports

    Hi,

    I set-up a sheduled report at the beginning of last month to run at 18:15 daily. Daylight savings came into effect for us on 27th March 2011 (GMT+1) and since then the report has run at 19:15. I want it to stay running at 18:15. The RH system time is correct and is in the correct timezone.

    Is this a known issue? Is there a way of disregarding the time change for scheduled reports? Has anyone else encountered this?

    Thanks,
    Neil
    Tags: daylight, reports, saving, scheduled, vpms
  • zjiteshthakk
    Member
    .
    • Mar 2011
    • 7
    #2
    Hello,

    Could you please share the following details:

    1) Voice Portal version
    2) Linux version (avayatized/RHEL)

    Thanks.

    Comment

    • campb9
      Member
      • Apr 2011
      • 3
      #3
      Hi,

      AVP is 5.1 sp1 and it runs on the corresponding version of Avaya-tised Linux.

      Thanks,
      Neil

      Comment

      • zjiteshthakk
        Member
        .
        • Mar 2011
        • 7
        #4
        DST automatically changes the system time, so that is expected behavior. With DST, the report will run after as hour if that is the DST difference. What you need to do is schedule two reports considering the DST and keep timings accordingly.

        Comment

        • campb9
          Member
          • Apr 2011
          • 3
          #5
          Sorry - I'm not quite following you. Are you saying that the scheduled reports are effectively locked in the timezone in which they were created and don't take account of DST?

          So, for example, if I schedule a report to run at 12:00 GMT and the next day DST changes to GMT+1 (i.e. BST - British Summer Time) then the report will still be using the GMT timezone and run at 13:00 GMT+1? Where I actually want it to be 12:00 GMT+1 (11:00 GMT).

          This seems an awfully big oversight to me. Why can't the scheduler software check the actual (DST-adjusted) system time?

          It's not possible for me to set up two reports to cover this - it's a daily report and the interface does not allow a range of recurring dates to be entered. Can I do something on the OS level instead with e.g. crontab?

          Comment

          • crossjam
            Aspiring Member
            • May 2011
            • 1
            #6
            Scheduled reports not adhering to DST rules

            I don't know if this is a known issue or not - but have you tried recreating the schedule that runs your report?

            Comment

            Previous template Next
            Loading