Time in @TM

[Rodgers Hemer]

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".
One of my systems uses SCO 5.0.5 and no maintenance pack is  
available, thus requiring a change to /etc/TIMEZONE to specify the  
start and end of DST.  This change permitted filePro to work as  
usual.  However, the other SCO systems are 5.0.7 and 6.0 for which  
maintenance packs were installed.
SCO made no changes to TIMEZONE but "date" works correctly.  Once I  
made the same changes to to TIMEZONE in the 5.0.7 and 6.0 systems  
that I had made in the 5.0.5 system, filePro once again worked  
correctly.

The corrected definition in /etc/TIMEZONE (for the Pacific time zone)  
is:

		"TZ=PST8PDT,M3.2.0/2,M11.1.0/2"

Rodgers Hemer