Conference azur::mcc

5631.0. "MCC_TDF and SYS$TIMEZONE_DIFFERENTIAL mismatch" by KERNEL::SANDYSP () Fri Oct 01 1993 10:59

	Thought it might be useful to warn others of a problem starting
    	the TSAM (v1.0.x) after upgrading from VMS 5.x to 6.0
    	Running @sys$startup:MCC_TS_AM_STARTUP.COM gives
    	
       'Invalid MCC_TDF OR SYS$TIMEZONE_DIFFERENTIAL logical
        %MCC-E-FW_INTERNAL_ERR, Internal framework error
        %TRACE-E-TRACEBACK, symbolic stack dump follows' when run on VMS V6.0
			        
 	Then shows stack dump in MCC_MAIN and 
	MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE

	Then following errors:

	%MCC-F-MIR_INIT_FAIL, the MIR could not be initialized
 	Invalid MCC_TDF or SYS$TIMEZONE_DIFFERENTIAL logical
	%MCC-E-FW_INTERNAL_ERR, Internal framework error
	%MCC-F-TRM_FAILURE, PM unable to continue
 	%DCL-W-SKPDAT, image data (records not beginning with "$" ignored)
	%MCC-F-NOMSG, Mesage number 0326E44C

Cause:

	A new system logical was introduced in VMS V6.0 with default setting:
 	"SYS$TIMEZONE_DIFFERENTIAL" = "-46800"
	The default setting is -13:00 (hours) ie -46800 (seconds).
	This setting will not match the MCC system logical:
	"MCC_TDF" = "00:00"  (or similar)

Solution:

	Check the settings of the two logicals, then if a mismatch run the
	following procedure:

 	@SYS$COMMON:[SYSMGR]UTC$CONFIGURE_TDF.COM

	This will give the following output:

                Configuring the Time Differential Factor

        Enter ? anytime for help

        [0]     Exit
        [1]     Set the Time Differential Factor
        [2]     Display the Time Differential Factor

        * Please pick an option number [2]:
 

	Use 1 to reset to 00:00 or similar (note the logical only displays
	this as "0" but will still overcome mismatch.

	Restart BMS then TSAM ie:
 	@SYS$COMMON:[SYS$STARTUP]MCC_STARTUP_BMS.COM
 	@SYS$COMMON:[SYS$STARTUP]MCC_TS_AM_STARTUP.COM
    
    	Hope this saves a few people some time.
    
    	Trish