Text 5459, 105 rader
Skriven 2005-03-20 13:09:37 av Gerald Miller (1:342/512)
   Kommentar till text 5450 av Dan Ceppa (1:123/666.0)
Ärende: Time deja vu
====================
Hello Dan,

    Responding to a post in the WIN95 area:
    On Sunday March 20 2005 at 15:14,
    Dan Ceppa [1:123/666] wrote to All,
    about: Time deja vu

 DC> @PID: OMX 1.00.DOS [NR]
 DC> @MSGID: 1:123/666.0 423d9358
 DC> Well, some time back, finding the setting of ZTUC=-0700
 DC> cured my main problem.

 DC> But, I now have another (though not major) one.  As it is,
 DC> mail goes out and comes in.  And, I'm not accused of dups!

 DC> Using that setting, I'm seeing messages as being written
 DC> 5 hours early than they realy were.  The Terminate data base
 DC> gives the correct time.  I then process the JAM message base through
 DC> OMX and then use BW for reading.

 DC> Once in BW, a message that TM shows with a time stamp of 11AM
 DC> shows up as being displayed as from 6AM

 DC> I've checked some messages that with were written with the ZTUC
 DC> parameter and not.  They seem all to have the 5hr time shift.

 DC> I could almost understand it if my setting was ZTUC = -0500,
 DC> but that is not the case.

 DC> If you reply, please include the approximate time you sent
 DC> your message in the body of the message.  Your time zone may
 DC> be of help, too, but it seems it's more global than that...

 DC> Thanks

 DC> 10:19 AM   10:19:00

 DC> --- OMX/Blue Wave/DOS v2.30
 DC>  * Origin: Soundly on the Fault Line (1:123/666.0)
 DC> SEEN-BY: 10/3 15/0 17/23 106/2000 6018 109/568 120/544 134/77 140/1 2
 DC> 153/307
 DC> SEEN-BY: 153/7715 220/12 221/0 250/501 270/1000 292/100 854 297/11
 DC> 342/5 9 512
 DC> SEEN-BY: 348/105 382/61 772/1 2613/118 3828/7 7105/1
 DC> @PATH: 123/666 500 106/2000 140/1 342/5

Please forgive me for "over" quoting your entire message (hidden headers
and hidden footers as well).

In my mailer (FrontDoor) batch file, I have the lines:

  SET TZ=MST7MDT6,M4.1.0/02:00,M10.5.0/02:00
::
::        ADJUST THE TIME ZONE ACCORDING TO PROVINCAL LOCATION __AND__
::        ACCORDING TO STANDARD __OR__ DAYLIGHT SAVING TIME!!!
::
iff %@filedate[C:\4d\4b\D&S_COL.BTM] eq %STD_DATE then %+
::        MST     -0700   Mountain Standard Time
  set TZUTC=-0700
elseiff %@filedate[C:\4d\4b\D&S_COL.BTM] eq %DAY_DATE then %+
::        MDT     -0600   Mountain Daylight Saving Time
  set TZUTC=-0600
endiff

and this "seems" to be acceptable to my system for the Mountain Standard
Time Zone.  In approximately 13 days and some hours, the D&S_COL.BTM file
will run and and the above snippet will adjust everything for the Mountain
Daylight Time Zone factor.

Now, (a presumption is required here) if my system is correct, then your
settings could put you in my Mountain Time Zone instead of the Pacific Time
Zone (Washington State is in the Pacific Time Zone, I believe).  Also, if
your state observes the Daylight Saving Time factor, then your timestamps
should change twice a year (from Standard to Daylight _and_ from Daylight
back to Standard).

Try changing your "ZTUC" variable to "TZUTC" (possibility you may have
mistyped it)...  I think the long name is Time Zone Universal Time
Constant. ???

The "grunged" timestamp with your message writer is something else again
because I have found that _most_ do not accept the time zone variables...

I think that I inserted the:

  SET TZ=MST7MDT6,M4.1.0/02:00,M10.5.0/02:00

to deal with how GoldED was dealing with the time issue and you may be able
to get away with something like:

  SET TZ=PST8PDT7,M4.1.0/02:00,M10.5.0/02:00

but your mileage may vary.  ;-)))

I rather doubt that entering my local time in this message is going to help
you much because this message can sit on my local board until the mailer is
ready for an outgoing message event, but...

Local time: Sunday, March 20, 2005 13:59:04

           Cheers ... Gerald

... Great Canadian Lie #132: "We're just going for one beer..."
--- GoldED+/DPMI32 v1.1.5-040330 [msg of March 20, 2005]
 * Origin: Annoying Crossover in Music... Techno-Death Mamba. (1:342/512)