Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-04-2011, 08:40 AM
campb9 campb9 is offline
Member
 
Join Date: Apr 2011
Location: London, UK
Posts: 3
campb9 has 10 reputation points
Question 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
Reply With Quote
  #2  
Old 04-26-2011, 04:36 AM
zjiteshthakk zjiteshthakk is offline
Member
.
 
Join Date: Mar 2011
Posts: 7
zjiteshthakk has 10 reputation points
Default

Hello,

Could you please share the following details:

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

Thanks.
Reply With Quote
  #3  
Old 04-26-2011, 04:50 AM
campb9 campb9 is offline
Member
 
Join Date: Apr 2011
Location: London, UK
Posts: 3
campb9 has 10 reputation points
Default

Hi,

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

Thanks,
Neil
Reply With Quote
  #4  
Old 04-27-2011, 07:00 AM
zjiteshthakk zjiteshthakk is offline
Member
.
 
Join Date: Mar 2011
Posts: 7
zjiteshthakk has 10 reputation points
Default

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.
Reply With Quote
  #5  
Old 04-27-2011, 08:04 AM
campb9 campb9 is offline
Member
 
Join Date: Apr 2011
Location: London, UK
Posts: 3
campb9 has 10 reputation points
Default

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?
Reply With Quote
  #6  
Old 05-12-2011, 10:15 AM
crossjam crossjam is offline
Aspiring Member
 
Join Date: May 2011
Posts: 1
crossjam has 10 reputation points
Default 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?
Reply With Quote
Reply

Tags
daylight, reports, saving, scheduled, vpms

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:28 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.