[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

3053.0. "VMS V5.5 upgrade on DECmcc T1.2.7" by PYRO::VANZUYLEN (Ron S. van Zuylen) Fri May 22 1992 01:36

    VAX/VMS DECmcc T1.2.7 installs it's own CMA* (DECthreads) files.  If,
    say, a V5.4-3 node with DECmcc T1.2.7 was upgraded to V5.5... would
    DECmcc need to be re-installed?  (To my knowledge, the upgrade would
    replace the DECmcc CMA* images with the older (?) V5.5 images.)
    
    --Ron

T.R	Title	User	Personal Name	Date	Lines
3053.1	Also burned	RACER::dave	Ahh, but fortunately, I have the key to escape reality.	`Fri May 22 1992 09:21`	7
	I got burned by this, and also by the Common Agent (RCMP version) doing the same thing. Yes, you need to KNOW if the CMA RTL files get replaced, and I have put the BL9 files back after the upgrade to 5.5-1 with no apparent problems for the system. Every kit that includes CMA files needs to be MUCH smarter about it deals with replacement of those files.
3053.2	Future convergence and interoperability	TOOK::BURGESS		`Sat May 23 1992 15:55`	21
	When DECmcc ships both VMS and ULTRIX(toolkit) kit installation procedures will CONDITIONALLY UPDATE the system with the CMA files piggy-backed on the the MCC kit. We have been working with CMA folks and other clients of CMA for months to establish standard proceeds for insuring upwards compatibility of CMA and interoperability of layered product installations. Because of last minute bugs (CMA) and kits installation problems (MCC) T1.2.7 followed the "don't drink the local water" principle and unconditionally provided CMA files with the MCC files. ( :-( ) MCC (and DCE and ADA - the bleeding edge clients) will install their version of CMA only if their version id is greater than that on the system. The obvious gap is the base-system (VMS/UTLRIX/...) installation which still probably will install CMA bl 7 over CMA bl10. In future version of VMS the 'right thing' might happen. In future version of MCC (v1.3, v2.0) we hope to be able to use the 'local version' of CMA. For ULTRIX (which doesn't use shared libraries ) the only conflict is for MCC toolkit developers. For VMS the problem will be for all run-time clients of CMA.