<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic timezone problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421339#M111</link>
    <description>In Britain we have just switched to British Summer Time&lt;BR /&gt;(BST), ie. GMT+1hour. Within our ITO system (based on ORacle) we have the &lt;BR /&gt;problem that the message alerts seem to hold GMT times in the database (viewed &lt;BR /&gt;with SQL), but when using the OpC Gui frontend to look at the data, the &lt;BR /&gt;timestamp is right (ie in BST).&lt;BR /&gt;&lt;BR /&gt;We are sitting on an HP-UX machine with 10.20.&lt;BR /&gt;Our TZ is set to GMT0BST.&lt;BR /&gt;&lt;BR /&gt;Any ideas?</description>
    <pubDate>Wed, 12 Apr 2000 04:00:44 GMT</pubDate>
    <dc:creator>Graham Brown_5</dc:creator>
    <dc:date>2000-04-12T04:00:44Z</dc:date>
    <item>
      <title>timezone problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421339#M111</link>
      <description>In Britain we have just switched to British Summer Time&lt;BR /&gt;(BST), ie. GMT+1hour. Within our ITO system (based on ORacle) we have the &lt;BR /&gt;problem that the message alerts seem to hold GMT times in the database (viewed &lt;BR /&gt;with SQL), but when using the OpC Gui frontend to look at the data, the &lt;BR /&gt;timestamp is right (ie in BST).&lt;BR /&gt;&lt;BR /&gt;We are sitting on an HP-UX machine with 10.20.&lt;BR /&gt;Our TZ is set to GMT0BST.&lt;BR /&gt;&lt;BR /&gt;Any ideas?</description>
      <pubDate>Wed, 12 Apr 2000 04:00:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421339#M111</guid>
      <dc:creator>Graham Brown_5</dc:creator>
      <dc:date>2000-04-12T04:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: timezone problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421340#M112</link>
      <description>a) if you have not stopped and re-started your oracle &lt;BR /&gt;environemnt, it has this bad habit of not picking up the right timezone. The &lt;BR /&gt;best practice for oracle is to&lt;BR /&gt;stop and re-start&lt;BR /&gt;&lt;BR /&gt;b) check the timezone in the oraenv  environemnt, it &lt;BR /&gt;may not be set right.</description>
      <pubDate>Wed, 12 Apr 2000 04:56:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421340#M112</guid>
      <dc:creator>Terja Lange_1</dc:creator>
      <dc:date>2000-04-12T04:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: timezone problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421341#M113</link>
      <description>All Unix systems keep internal time as GMT (aka, UTC or Zulu time).  The $TZ env parameter is used by the many library routines to translate GMT to the value represented by $TZ.  Unix is unique in that users all over the world can login and after setting $TZ to their local timezone, all commands and proceseses will display local time (complete with Daylight Savings Time switches). This is all controlled by /usr/lib/tztab entries.&lt;BR /&gt;&lt;BR /&gt;However, processes that operate as daemons or in cron jobs do not login and may not inherit $TZ.  See the man page for crontab where the (very simple) environment is discussed.  There are 2 kernel parameters that can be used for daemons and cron jobs: timezone and dst. Read the Help-on-Context information in SAM for details on setting timezone and dst.</description>
      <pubDate>Mon, 29 May 2000 20:16:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/timezone-problem/m-p/2421341#M113</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2000-05-29T20:16:52Z</dc:date>
    </item>
  </channel>
</rss>

