[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

3111.0. "Warning: Installing VMS 5.5-1, VMS 5.5-2 and DECmcc" by TOOK::BURGESS () Mon Jun 01 1992 14:54

	DECmcc v1.2 and VMS 5.5

	1) In VMS 5.5-1xx there is a bug in lib$find_image_symbol (LIBRTL)
	   where the code improperly accesses a string descriptor 
	   and performs a movc3 which clobbers the stack.

	   The problem often manifests itself when attemting to
	   bring up the Iconic map.

	   The bug is apparently fixed in VMS 5.5-2xxx (Amber)
	   which has just been made available for ft2.

	2) CMA.
	   DECmcc t1.2.7 uses CMA bl8+ 
		(image file identification: "CMA X1.0-430K01"
		link date/time:  1-APR-1992 15:44:15.27)

	   DECmcc (latest internal baselevel x1.2.21) uses CMA bl10
                image file identification: "CMA V1.10-029"
                link date/time: 21-APR-1992 07:38:03.80


	   The DECmcc v1.2 installation strategy will be
		If the CMA version on the MCC kit is more recent
		than that on the target system, then provide the
		newer CMA files.

	   Unfortunately, the VMS 5.5-2 FT2 kit is not so thoughtful.
	   If one installs VMS 5.5-2 FT2 *after* MCC x1.2.xxx,
	   then the cma files have been replaced by some older,
	   unusable CMA files (V01-442).  If one then attempts to
	   use DECmcc, then an error message will appear about
	   requiring global, writteable shareable images to be installed.

	   The work-around for users is to either re-install DECmcc
	   from the kit or to copy the CMA files from the DECmcc kit
	   to SYS$COMMON:[SYSLIB].  Or save/restore the CMA files
	   before/after installing VMS 5.5-2 ft2.	   

	   This work-around will appear in the MCC release notes.

	3) What about other layered products?
		Other layered products which have permission from CMA
		to ship CMA files on their kit are requested to 
		follow the rule - Only provide/install CMA from your kit
		if the kit version is more recent than that on the target system.

		Just to be safe you might want to save the MCC/CMA files
		before installing such lp kits, and possibly restoring the files.

T.R	Title	User	Personal Name	Date	Lines
3111.1	Not all 5.5-1's are the same	RACER::dave	Ahh, but fortunately, I have the key to escape reality.	`Mon Jun 01 1992 15:17`	4
	Please note that the VMS 5.5-1xx in the base note refers to VMS 5.5-1E7, not the VMS 5.5-1MA kit. These are different kits and not related. The 5.5-1MA kit does not install on top of the 5.5-1E7 kit.
3111.2	which CMA?	COOKIE::KELLER		`Mon Oct 19 1992 13:33`	24
	Has this problem changed with the SSB V5.5-2 kit? Our scenario is: 1) Installed MCC V1.2 SSB kit on a VMS V5.5 cluster. (MCC kits dated 2-Jul-1992) 2) Upgraded VMS to recent SSB version V5.5-2 The VMS V5.5-2 upgrade changed the CMA images in SYS$COMMON: Image file ident for SYS$COMMON:[SYSLIB]CMA$RTL.EXE is now: "V01-442" Image file ident for CMA$RTL.EXE in MCC V1.2 kit is: "CMA V1.10-030" (This is what was in SYS$COMMON:[SYSLIB] before the VMS V5.5-2 upgrade) MCC appears to be working fine under VMS V5.5-2 running the "V01-442" version of CMA. Are there potential problems with this configuration? (The previous note seemed to indicate that MCC won't even run in this configuration, we appear to be running MCC fine) Should we reinstall MCC V1.2 to get the 'MCC compatible' CMA? Please advise, thanks. Greg
3111.3	Depends on your Karma	TOOK::LYONS	Ahh, but fortunately, I have the key to escape reality.	`Wed Oct 21 1992 20:40`	6
	It all depends on how much you stress the system. If you NEVER do anything like use alarm rules, ot graphs, or have many show commands running at the same time, then you will probably never see the problems. However, if you use these features, then you are likely to get burned at some point in time. Then again, you may have good karma and never see any problems.
3111.4	Requirement or Recomended	BRAT::BUKOWSKI		`Wed Dec 09 1992 14:30`	8
	We are planning on upgrading our 6410 from VMS 5.4-3 to 5.5-2. We are currently using DECmcc SSB 1.2, and we use it fairly heavy and plan to load it down with lots of alarms soon. Oh yes, we also use Iconic Map. Is it a requirement that we RE-install MCC or are you just making a suggestion? Network Management, Mike
3111.5	Depends on what you expect	TOOK::MINTZ	Erik Mintz	`Wed Dec 09 1992 15:20`	7
	I'm not sure of the distinction that you are making. If you try to run DECmcc on a system that has an older version of CMA installed, then you will encounter problems when the system is stressed. If that's OK with you, then go ahead. If that's not OK, then we are telling you how to fix it.