Time in @TM

[Rodgers Hemer]

On Mar 23, 2007, at 1:50 PM, Bill Campbell wrote:

> On Fri, Mar 23, 2007, Rodgers Hemer wrote:
>>
>> On Mar 21, 2007, at 2:10 PM, Rodgers Hemer wrote:
>>> On Mar 21, 2007, at 2:03 PM, Kenneth Brody wrote:
>>>
>>>> Quoting Rodgers Hemer (Wed, 21 Mar 2007 13:55:22 -0700):
>>>>
>>>>> SCO 5.0.7 w/ MP5,  fP5.0.14
>>>>>
>>>>> I have one system that does not return the correct time when using
>>>>> @tm.  The latest maintenance pack for SCO has been installed  
>>>>> and the
>>>>> operating system displays the correct time from the date command.
>>>>> However, @TM is showing the time to be what it would have been
>>>>> before
>>>>> the March 1 DST change.  I can find no difference in the
>>>>> configuration of filePro between this errant system and others to
>>>>> which I have access.
>>>>>
>>>>> Does anyone have any suggestions as to what is causing this
>>>>> aberration and/or how to correct it?
>>>>
>>>> The cause is the change in rules as to when DST starts and ends.
>>>>
>>>> Are the other systems which you have checked also running a patched
>>>> SCO with filePro 5.0.14 or earlier?
>>>>
>>>> --
>>>> KenBrody at BestWeb dot net        spamtrap:
>>>> <g8ymh8uf001 at sneakemail.com>
>>>> http://www.hvcomputer.com
>>>> http://www.fileProPlus.com
>>>>
>>> Ken:
>>>
>>> Yes.  The system I am on currently is a SCO 5.0.5 with a patched / 
>>> etc/
>>> TIMEZONE file (there was no maintenance pack).  I have not yet been
>>> able to get to a SCO 6.0 system that also had a maintenance pack.
>>>
>>> Rodgers Hemer
>>>
>> Ken:
>>
>> I now have a better understanding of the time problem noted in the
>> above post.  As Jay noted, I said that all SCO systems that I deal
>> with are displaying the correct time using the "date" command.  No
>> changes had been made to TZ in any of my systems, and that was the
>> problem.
>>
>> filePro is apparently getting time from TZ and not whatever internal
>> source SCO uses for "date".
>
> SCO uses the TZ environment variable to calculate dates, and gets
> it from /etc/TIMEZONE on boot for many daemon processes.
>
> Is it possible that you have a script in your FilePro startup
> or your login profile that's setting TZ incorrectly?
>
> Bill

No.  I do not alter /etc/profile and the only changes in the  
user .profile is one line to startup filePro and/or setup Facet  
windows, none which involve a separate script or setting new variables.

Please note that the standard /etc/TIMEZONE never explicitly states  
the beginning and end of DST, only that it is used and the time zone  
of the server.  SCO has to look elsewhere for the start and stop dates.

Rodgers Hemer