Want to get rid of Google Ads, click here.
+ Reply to Thread
Results 1 to 7 of 7

Thread: timezone

  1. #1
    Member
    Join Date
    Dec 2001
    Location
    Switzerland
    Posts
    36

    Default timezone

    using CIT 3.2.1 on W2K, receiving data from TEC, sending to SC

    from the TEC-Connector we receive a date "04/02/17 18:00". In SC eventin it arrives in the same format, if I look at the data in the (task) record, it is displayed as "04/02/17 19:00". This is because my operator record has timezone "Europe/Middle".

    The CIT Scenario is running on a PC having TimeZone "Europe/Middle" as well (GMT+1).

    How/where can I setup the date corrections? I have tried to change the timezone of the user (falcon) which is used in the scenario, but no succes. Also changing the timezone on the PC running my scenario to GMT didn't help. :roll:

    Thanks for any hint.
    Martin

  2. #2
    Administrator tommy's Avatar
    Join Date
    Nov 2001
    Location
    Copenhagen
    Posts
    4,270

    Default

    How weird..... I just sent an email to the GPUG mailing list regarding a similar question to point the user to this topic:

    http://www.sc-resources.net/viewtopic.php?t=17871

    Around the middle I mention a workaround using RTECALL's to set the timezone on the eventrecord which should should any problems regarding correct time zone.
    Best regards Tommy
    Blog - - ITIL certified - Accredited Integration Specialist – HP OpenView Service Management

    Want to keep this site alive? Consider making a donation. Click here.

  3. #3
    Member
    Join Date
    Dec 2001
    Location
    Switzerland
    Posts
    36

    Default

    Tommy,

    thanks for your help, the "set.timezone" solved our problem!

    However we are a little bit surprised that SC saves the date from the eventin record "as is". We were asuming that it takes the settings from the company record into account ...

  4. #4
    Junior Member
    Join Date
    Jul 2007
    Posts
    3

    Smile

    Quote Originally Posted by tommy View Post
    How weird..... I just sent an email to the GPUG mailing list regarding a similar question to point the user to this topic:

    http://www.sc-resources.net/viewtopic.php?t=17871

    Around the middle I mention a workaround using RTECALL's to set the timezone on the eventrecord which should should any problems regarding correct time zone.
    I'm having the same problem as described in this thread. The above link no longer works - I don't suppose someone would be able to point me to its new location?

    Cheers!

  5. #5
    Junior Member
    Join Date
    Jul 2007
    Posts
    3

    Default

    No worries guys its been sorted out.

    For the benefit of anyone browsing this thread in the future, we had to put the line that you were referring to:

    $L.void=rtecall("rinit", $L.rc, $L.file, "tzfile");$L.void=rtecall("select", $L.rc, $L.file, "name=\"Australia/NSW\"", , );set.timezone($L.file)

    into the expressions section on the first event map for the class - in our case problem close (pmc).

    A nice screenshot for you:



    Cheers!

  6. #6
    Senior Member glg's Avatar
    Join Date
    Aug 2004
    Location
    Chicago, IL, USA
    Posts
    714

    Default

    Two thoughts on this:

    1. Don't use $L.file. It gets used so heavily in the system, that it's a bad idea. make up your own variable, something like $L.tectz
    2. Even better place to run this then on the first map is in the initialization expressions on the event registration.

  7. #7
    Junior Member
    Join Date
    Jul 2007
    Posts
    3

    Default

    Yeah I tried putting that line in the initialization expressions on the event registration, but it just didn't want to work. As soon as we moved it into the first map record (as suggested on one of the HP forums) it worked fine. No idea why - but so long as its working i'm happy

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts