[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

194.0. "MCC and VMS versions?" by BAHTAT::BOND () Fri Jul 20 1990 12:27

    I understand that MCC V1.0 when it ships to customers in November will
    run against VMS 5.3.  One of my customers is planning to begin
    integrating MCC into their shippable application from MCC V1.1 when all
    the other good things like Icons etc become available.   For planning
    purposes, can you tell me whether MCC V1.1 will still play on VMS 5.3?
    
    Can you also confirm that in order to use MCC to manage PhaseV systems,
    your MCC system must itself be running PhaseV?  I know this seems to be
    obvious but you might have put a stripped down DNA CMIP stack into the
    AM itself so you are not reliant on the underlying OPsys stack for your
    comms to other PhaseV systems :-).
    
    chris

T.R	Title	User	Personal Name	Date	Lines
194.1	can manage V from IV	TOOK::DENSMORE	get to the verbs	`Fri Jul 20 1990 14:56`	12
	I can answer your second question. MCC does not require Phase V to manage a Phase V node. It uses the Phase IV DECnet to connect to the CML object on the Phase V node and then speaks CMIP to it. You must give the Phase V node a synonym, however, and that sysnonym must be be defined in your local node's node database as well as in DNS. Example: REGISTER NODE fullname SYNONYM p4name CREATE NODE4 localnode REMOTE NODE p4name ADDRESS aa.nnn You may refer to the Phase V node using either its fullname or synonym. Mike
194.2	1.1 on 5.3	GOSTE::CALLANDER		`Mon Jul 23 1990 09:44`	2
	The current 1.1 field test releases all run on 5.3.
194.3	Press suggests VMS 5.2 for Mcc?	BAHTAT::BOND		`Tue Jul 31 1990 04:40`	9
	"Notes from the UnderLAN, 27-JUL-1990" edited by Sunni Misner (DELNI::MISNER) in its Digital section quotes press releases of 7/9/90 and a PCWeek article saying that the DECmcc director and the management stations V2 require VMS 5.2 and DECnet 5.2 or greater to run against. I understood from internal information and the previous answers to my base note that 5.3 was the minimum version for the mcc director 1.0 and also 1.1. Could somebody please confirm (again!) that 5.3 is the minimum VMS version for mcc and that it will NOT work with 5.2?
194.4	MCC requires VMS 5.3 as a minimum...	KEEL::SAVAGE	Peter Savage	`Wed Aug 01 1990 11:24`	7
	MCC requires VMS 5.3 as a minimum in order to run. Our installation process checks to make sure that you are running this version as a minimum. I hope this clears things up. Peter
194.5		NSSG::R_SPENCE	Nets don't fail me now...	`Thu Aug 02 1990 15:59`	5
	Don't get the DECmcc Director and the DECmcc Management Station for VMS mixed up (like I and others are want to do). It is only the EMA compliant Director modeled versions that require VMS V5.3 or later. s/rob
194.6	it's clear	BAHTAT::BOND		`Fri Aug 03 1990 09:04`	8
	Thanks for the clarification that the mcc director requires 5.3. I guess either Notes from the Underlan or the articles it quoted have got a misprint in them. In response to .-1, the management stations V2 bundle the DECmcc director, therefore they'll need 5.3 as well. thanks for all the responses chris
194.7	misleading	GOSTE::CALLANDER		`Fri Aug 03 1990 12:31`	6
	I went and looked at the underlan article and what they did was a cut an paste. It is talking about the EMS and SMS products and then stated that 5.3 was needed for the directory and BMS products. The info was right just stated in the wrong context, very misleading.