[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

253.0. "DECmcc-BMS Startup Warning Messages?" by WLW::ZIGLER (Tom Zigler, DTN 432-7541) Mon Aug 13 1990 17:08

    After installing the DECmcc-BMS EFT Update on our VMS V5.3 system
    previously running DECmcc V1.0 EFT, the IVPs for both the BMS and
    DIRECTOR components were both successful.  Also, I seem to be able to
    create and delete alarm rules successfully as well.  However, whenever
    I invoke @SYS$STARTUP:MCC_STARTUP_BMS, I get the following two warning
    messages:
    
    	MCC-W-VEINVALID, ENTITY MCC IS NOT VALID WITH VERB CREATE
    	MCC-W-VEINVALID, ENTITY MCC IS NOT VALID WITH VERB DELETE
    
    What is the explanation for these warning messages?  Do I need to be
    concerned or fix anything?
    
    Please advise.
    
    		\Thanks in Advance

T.R	Title	User	Personal Name	Date	Lines
253.1	0?	MKNME::DANIELE		`Tue Aug 14 1990 15:53`	13
	> MCC-W-VEINVALID, ENTITY MCC IS NOT VALID WITH VERB CREATE This is the message I see when I forget the mcc instance identifier '0'. Could you check the startup file for the lines create mcc 0 alarms rule .... delete mcc 0 alarms rule .... and see if it says "create mcc 0 alarms" or "create mcc alarms"? Just a shot, Mike
253.2	mcc 0 alarms rule	TAZBOY::ZIGLER	Tom Zigler, DTN 432-7541	`Tue Aug 14 1990 17:09`	6
	re: 1 It says "create mcc 0 alarms rule" and "delete mcc 0 alarms rule" ... that is why I am puzzled.
253.3	Please check date of any/all mcc_startup files	TOOK::GUERTIN	Wherever you go, there you are.	`Wed Aug 15 1990 10:55`	3
	I would do a $directory/date on sys$startup:mcc_startup*.com. There may be an archaic version laying around. Did you install over an older version of MCC?
253.4	Checking Into It...	TAZBOY::ZIGLER	Tom Zigler, DTN 432-7541	`Wed Aug 15 1990 12:31`	13
	Yes, not only did I install over the first DECmcc EFT (T1.0.0) release but I also, for the DECmcc-BMS install, elected to point myself to a different disk to conserve system disk space, since the installation of the DECmcc-BMS EFT (T1.0.1) update gave me that option. Therefore, some MCC files now exist on BOTH sys$sysdevice (DKA100:) and DKA200:[MCC]. The MCC_COMMON logical now points to DKA200:[MCC]. I am in the process of providing Jill Callander with a DIR/OWN/PROT MCC directory structure and a copy of the SYS$STARTUP:MCC_STARTUP_BMS.COM file for further analysis. Thank you for your suggestion...I shall check into it today!
253.5	symbols in init file	GOSTE::CALLANDER		`Wed Aug 15 1990 17:59`	9
	answered off-line. startup errors were due to a conflict caused by defining symbols for the word "alarms" and "rule" in a system wide initialization file. These redefinitions caused the startup commands to fail (because the symbol substition caused the commands to be garbled). jill
253.6	Please have FCL confirm symbol definitions	TOOK::GUERTIN	Wherever you go, there you are.	`Thu Aug 16 1990 07:21`	14
	Symbol substitution can cause all kinds of weird behavior. This is the second time I seen this happen. Maybe FCL could display a confirmation message whenever a symbol is defined. Something like: MCC> define node node4 "node" now defined to "node4" MCC> show node p4node all char This way even if a symbol is defined in an init file, it gets displayed to the user. I noticed that even the VMS debugger does this for key redefinitions. Presumably because of similar problems. (BTW: I hope no one actually does redefine node to node4). -Matt.
253.7	1.1 work list	GOSTE::CALLANDER		`Fri Aug 17 1990 18:29`	3
	Already on the 1.1 work list. Also it has been added to the manual under diagnosing problems.