Conference azur::mcc

    re: .0
    The same question.
    How do we run DECmcc with VMS V6.0?
    There are a couple of notes that say it has been done with a bit of
    hacking.....
    thanks,
    Mike

MY customer experiance exactly the same problems as mentioned earlier. Is CMA
Threads implemented in VMS V6.0 itself, and thus causing the mismatch?

They also gets problem with Time zone as described in #5631.

They have POLYCENTER NEtwork Manager 400, but I'm not sure if they start the
TSAM ass described in the timezone problem.

Bj�rn Olav

>Is CMA
>Threads implemented in VMS V6.0 itself, and thus causing the mismatch?

I don't know for sure but would expect that VMS V6.0 (as the versions 
before) comes with CMA. Since MCC V1.3 works ONLY with it's own version 
of CMA I would suggest to restore the CMA files from the MCC kit to 
sys$library (save the originals before!!!). The files are:

Directory SYS$COMMON:[SYSLIB]

CMA$LIB_SHR.EXE;4                            176/177     30-APR-1992 14:39:20.00
CMA$OPEN_LIB_SHR.EXE;2                        12/12      30-APR-1992 14:39:19.00
CMA$OPEN_RTL.EXE;4                            24/24      12-JUN-1992 16:40:43.62
CMA$RTL.EXE;4                                257/258     12-JUN-1992 16:41:12.77

Total of 4 files, 469/471 blocks.

CAUTION: Other application that need CMA may break now!!!

*Robert

    Well, dont do it.....
    
    If you want to, then place the CMA images in a private area and define
    
    $ DEFINE CMA$LIB_SHR mydev:[mydir]CMA$LIB_SHR.EXE
    
    (Do this for all four images)
    
    Then, when you run MCC, it will use the private versions of CMA and
    not trash the rest of the system.  Getting this to work correctly
    	in all cases is left as an excerise to the reader.
    

    Hello;
    
    I just installed OpenVMS v6.0 on a VAXstation 4000/60, from the
    Sept1993 CDROM.  This kit included PolyCenter 400, which I also
    installed new from the CD.  I have the same error with CMA, as the base
    note, and the Timezone error.
    
    Would someone please post the set-by-step procedure to make
    PolyCenter400 work in this environment?  (virgin machine, on a customer
    site, all new software from CD)
    
    thanks,
    
    JR
    
    

	Here is how I got mine to work. 
	There are 2 problems here. CMA mismatch problem and time differential
	mismatch .

	First the CMA problem

	There are actually 4 process logicals to be defined. 
	Place the CMA files from the MCC kit to a directory 
	(in this case I put it in [SYSLIB.MCC_CMA]). Define the logicals 
	in login.com of the mcc user. 


  $ DEFINE CMA$LIB_SHR   SYS$COMMON:[SYSLIB.MCC_CMA]CMA$LIB_SHR.EXE
  $ DEFINE CMA$OPEN_LIB_SHR  SYS$COMMON:[SYSLIB.MCC_CMA]CMA$OPEN_LIB_SHR.EXE
  $ DEFINE CMA$OPEN_RTL  SYS$COMMON:[SYSLIB.MCC_CMA]CMA$OPEN_RTL.EXE
  $ DEFINE CMA$RTL   SYS$COMMON:[SYSLIB.MCC_CMA]CMA$RTL.EXE

	This should make mcc use the correct cma images and maintain the new
	CMA images for other applications. 

	The second problem with invalid MCC_TDF or SYS$TIMEZONE_DIFFERENTIAL
	logical  is caused by the fact that the SYS$TIMEZONE_DIFFERENTIAL 
	logical takes on a default value of "-46800" seconds which is 
	"-13:00" hours.

	Simply execute SYS$STARTUP:UTC$CONFIGURE_TDF.COM , select option 1
	to modify the timezone information to the correct time zone value
	( +/-hh:mm ). The value should also match the logical MCC_TDF value.

	
	Andrew

    
    	I need to find out what the current official story is on MCC and VMS 
    V6.0. A month ago or so, I was told that everything looked good between 
    MCC and V6 provided that the MCC V6.0 compatibility upgrade kit was
    installed. A couple weeks ago, when I contacted the support center, I was 
    told that there have been new problems discovered between MCC and VMS V6 
    and to not run MCC under VMS for the time being.
    
    	What is the current story? Are there newly discovered problems
    between VMS V6 and MCC? How severe are they? If our customer's system
    is currently at VMS V5.5-2 and they want to upgrade to V6.1, is this a
    good idea at this time as far as MCC is concerned?
    
    	Thank You,
    
    	Dave

    
    
    	Does anyone have any unofficial comments about the preceeding
    question?
    
    	Thanks,
    
    	Dave

    I'd like to know as well as I'm preparing such an upgrade.
    
    Thanks,
    
    Jim C.
    

    I just installed Polycenter Network Manager 200 V1.3 on a VAX VMS V6.1
    system along with DECnet/OSI V5.7.  I'm getting the WRONG_CMA error as
    described in the previous notes.  It was apparently never fixed!
    
    In one of the previous notes, someone mentioned a VMS V6.0
    compatibility kit.  Does anyone know where this can be gotten from? 
    TIMA maybe?
    
    	Thanks!
    		David

>    In one of the previous notes, someone mentioned a VMS V6.0
>    compatibility kit.  Does anyone know where this can be gotten from? 
>    TIMA maybe?

The MCCKRNECO01013 kit should be available via TIMA. (in case it is not,
get it from BIKINI::MCC_DISK:[BMS013.VMS.PATCH]). This ECO is needed for 
MCC to run on VMS V6.*.

ATTENTION: This ECO needs a 'workaround'!!
           Please read MCCKRNECO01013.README
           (it's also mentioned somwhere in this conference).

*Robert