[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

3065.0. "Wrong time. DECMCC is stuck in the past. " by BRSTR1::PIGEON (VAX Vobiscum...) Fri May 22 1992 13:23

    I have installed DECMCC 1.1 on a VMS 5.5 vaxstation.
    
    Now when I run DECMCC any operation will have a time stamp
    wich is 2days and 4hours in the past. 
    
    An export without defining a begin time (default is now) will
    start in the past also.
    
    The system time is correct. The DNS last skull is correct with
    respect to the system time. Only DECMCC seems affected.
    
    I haven't defined any new default. I checked with the display
    command.
    
    In the iconic map, calling the operation time window will
    show all empty fields, with a black dot on the 'NOW' box.
    HOWEVER, if I click on the begin time, the CORRECT SYSTEM
    TIME will appear in the box ! So in that case DECMCC will
    get the system time. Apparently it is the 'NOW' value wich
    is false . ???? 
    
    I have stopped all recordings and exportings. I have restarted
    DECMCC. I even rebooted the system, DECMCC is still running
    almost three days in the past...
    
    I haven't seen any such problem in this note file.
    
    Any idea ?      (Completely confused now...)

T.R	Title	User	Personal Name	Date	Lines
3065.1	Check the MCC_TDF logical	TOOK::GUERTIN	It fall down, go boom	`Fri May 22 1992 13:57`	13
	There were a couple of notes on this a while back. Usually, this is because the mcc logical MCC_TDF is set wrong. Sadly, it is very easy (too easy) to do. For example, "-4" is minus four DAYS, and "-4:00" is minus four HOURS. Please make sure that the MCC_TDF logical value is correct: "MCC_TDF" = "[-/+]hh:mm" The sign is optional iff it is +. The colon should be there to separate hours from minutes. Otherwise, the value may be interpreted as days. -Matt.
3065.2	TDF is "+2"	BRSTR1::PIGEON	VAX Vobiscum...	`Mon May 25 1992 10:02`	15
	Interesting but strange... MCC_TDF is set to "+2" (My time zone is +2 as defined in DNS) Should it be "+2:00" ? I will try and see if it changes something. I'll keep you informed. But as I said in .0 the error is minus 3 days and about 20 hours. I have searched this note file already but I will look again. Still confused...
3065.3	Problem solved	BRSTR1::PIGEON	VAX Vobiscum...	`Mon May 25 1992 12:09`	13
	Matt, You solved my problem. Defining mcc_tdf as "+2:00" works. When its defined as "+2" the error is actually -2 days 20 hours and 16 minutes as the timestamp on any command will show. This is very puzzling. The wrong define comes from sys$startup:mcc_logical_dir.com Thanks you for your answer.
3065.4	mcc_logical_dir.com	TOOK::L_GROSSMAN		`Tue May 26 1992 09:38`	7
	I am curious how the mcc_logical_dir.com file received a "+2". Did someone edit the file? What was the last version of MCC installed? I ask because the current DECmcc installation checkes for the correct syntax.
3065.5	during installation	BRSTR1::PIGEON	Alpha = (YB)^2	`Wed May 27 1992 05:13`	5
	re. -1 Definitively not. I did install the product myself. I have probably entered "+2" during the installation. The name of the kit was MCCBMS011.A.
3065.6		TOOK::L_GROSSMAN		`Thu May 28 1992 18:10`	3
	Yes, The DECmcc V1.1 installation did not check the MCC_TDF for validity. The V1.2 installation will only allow MCC_TDFs of the form [+\|-}hh:mm where hh is from -12 to +13, and mm is from 00 to 59.