[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

3430.0. "What time is it where you are?" by CAADC::GALVIN (Mic Galvin, MCI Team) Sun Jul 26 1992 15:00

    		MCC "TDF" parameter
    
    I had an interesting dilemma this past week that raised a question in
    my mind about the "TDF" logical within DECmcc.  We've got DECnet VAX
    extentions installed on the system, which contains a mechanism to
    "synch" the system time on your system, depending on what region you've
    installed it.  
    
    We installed the MCC station in Chicago (US/Central Time) and used the
    proper formula for determining the TDF within DECmcc.  I believe it was
    -5 or something...it's been 4 months now.  
    
    Anyway, we imaged the MCC station and built an *identical* server for a
    customer demo in Colorado Springs, (US/Mountain Time).  When we
    rebooted the Server, and the DECnet VAX Extentions startup saw what the
    system time clock was, it said, "oh no...you are CENTRAL time and
    promptly changed the system time to an hour ahead!.
    
    I mucked around abit with the logicals for the MCC Director, and
    changed the TDF to (what I thought was accurate Mountain Time).  I
    couldn't changed the time by stopping and starting MCC, couldn't
    changed the time via DCL SET TIME=, and upon an additional reboot, I
    got the same result.
    
    I believe I've tracked down VAX Extentions as the culprit, and I will
    know on Monday if I've found the fix, I was just wondering if there was
    a way to dynamically changed the TDF parameter and/or the system time
    within DECmcc.  BTW, we're not using MCI's standard of Greenwich
    Meantime, we're using the time of the region.
    
    /Mic

T.R	Title	User	Personal Name	Date	Lines
3430.1	DECmcc listens to DECdts for timezone	TOOK::T_HUPPER	The rest, as they say, is history.	`Tue Jul 28 1992 12:05`	16
	DECmcc cannot set the system time or timezone. It depends on whatever the system thinks is happening. By "DECnet VAX Extensions", I assume you mean DECdts (Distributed Time Service). If DECdts is running, it sets up a logical "SYS$TIMEZONE_DIFFERENTIAL" which contains the timezone information for the system. If this logical is defined, DECmcc will use it in preference to its own "MCC_TDF" logical for the timezone. This makes the system more integrated wrt time. Note the DECmcc will not dynamically track changes to the "SYS$TIMEZONE_DIFFERENTIAL" logical. It must be stopped and restarted to pick up any changes in the timezone. Tweak DECdts to get the correct timezone. Ted
3430.2	Good Explanation!	CAADC::GALVIN	Mic Galvin, MCI Team	`Thu Jul 30 1992 00:47`	5
	Ted, Thanks for the info... I'll give it a shot! /Mic