[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

1888.0. "T1.2.3 Failed" by DUCAT2::FOUR62::LICAUSE (Al Licause (338-5661)) Fri Dec 06 1991 10:17

I've recently installed the T1.2.3 version of DECmcc on my VAXstation 3100
with 16MB memory.

I was running V1.1.

The installation failed while running the IVP.

Looking at the BMS_IVP it appears that it began to fail at the HISTORIAN_AM
because this and the following AM's (EXPORT, COLLECTION, NOTIFICATION)
all appear to have problems.

When I first installed the kit, I chose to use DNS. I assumed this may
have contributed to the problem due to the fact that I am also running
WAVE II DECnet (DECnet/OSI) and did encounter problems using V1.1 remote
DNS server.

I reinstalled the T1.2.3 kit, this time chosing to use the local MIR
database, and it failed in exactly the same manner.

When I try to run MCC, and do a SHOW MCC 0 whatever_AM ALL CHAR, the
above named module fail:

"SHO MCC 0 HISTORIAN_AM ALL CHAR%MCC-W-ATTRUNKNOWN, unknown attribute"
"HISTORIAN_AM"

Any help greatly apprecaited

P.S. I've been receiving the warning mesages regarding unsupported terminal
type for quite some time now under V1.1.

Enclosed is a log of the installation:

The MCC_STARTUP_BMS startup procedure for DECmcc T1.2.3 is now running.

DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

%NONAME-W-NOMSG, Message number 00000000
%NONAME-W-NOMSG, Message number 00000000
%NONAME-W-NOMSG, Message number 00000000

MCC 0 ALARMS RULE __dummy_test
AT 5-DEC-1991 14:43:30

Software logic error detected
MCC Routine Error = %NONAME-W-NOMSG, Message number
00000000

MCC 0 ALARMS RULE __dummy_test
AT 5-DEC-1991 14:43:31

Entity did not exist.

The MCC_STARTUP_BMS startup procedure for DECmcc T1.2.3 is now ending.

Completing DECmcc BMS Postinstallation Procedure ...

Beginning DECmcc BMS Installation Verification Procedure ...

The IVP for DECmcc BMS will now be run.

DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0
AT 5-DEC-1991 14:43:45

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 FCL
AT 5-DEC-1991 14:43:54

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 REGISTRATION_FM
AT 5-DEC-1991 14:44:08

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 DNA4_AM
AT 5-DEC-1991 14:44:19

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 DNA5_AM
AT 5-DEC-1991 14:44:29

Test Successful.
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 ICONICMAP
AT 5-DEC-1991 14:44:39

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 DOMAIN_FM
AT 5-DEC-1991 14:44:48

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 SAMPLE_AM
AT 5-DEC-1991 14:44:59

Test successful.
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 ETHERNET_AM
AT 5-DEC-1991 14:45:08

Test successful.
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 TCPIP_AM
AT 5-DEC-1991 14:45:18

Test successful.
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 CIRCUIT_AM
AT 5-DEC-1991 14:45:27

Test successful.
DECmcc (T1.2.3)
%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 ALARMS
AT 5-DEC-1991 14:45:36

Test successful.
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

MCC 0 HISTORIAN_FM
AT 5-DEC-1991 14:45:45

Test Successful
DECmcc (T1.2.3)

%MCC-W-NOFORMS, forms mode is not supported on this terminal type

%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition

The following command failed.

"MANAGE/ENTERPRISE TEST MCC 0 PA, TO FILE = MCCBMS$OUT.TXT"

DECmcc BMS T1.2.3 Installation Failed

%MCC-F-FAILED, fatal DECmcc error

*********************************************************

Fatal DECmcc BMS T1.2.3 event occurred during installation

*********************************************************
%VMSINSTAL-E-IVPFAIL, The IVP for MCCBMST V1.2 has failed.

VMSINSTAL procedure done at 14:46

T.R	Title	User	Personal Name	Date	Lines
1888.1	More info...	DUCAT2::FOUR62::LICAUSE	Al Licause (338-5661)	`Fri Dec 06 1991 10:46`	34
	On further examination of the IVP, I discovered that it is doing the MCC TEST, so I tried it by hand the the components that fail are as follows: MCC> test mcc 0 historian_fm 1 2 3 MCC 0 HISTORIAN_FM AT 6-DEC-1991 10:43:37 Test Successful MCC> test mcc 0 pa %MCC-E-NOTFOUND, unsupported combination of verb, entity, partition MCC> test mcc 0 exporter_fm %MCC-E-NOTFOUND, unsupported combination of verb, entity, partition MCC> test mcc 0 notification_fm %MCC-E-DSPMMLOCFILERR, dispatch local management module file access error during probe MCC> test mcc 0 collection_am MCC 0 COLLECTION_AM AT 6-DEC-1991 10:44:48 Test Successful.
1888.2	Entered as QAR 1787	TOOK::MINTZ	Erik Mintz	`Fri Dec 06 1991 10:58`	2
	Entered as QAR 1787 at priority 3.
1888.3	Did you check your license?	TOOK::GUERTIN	Don't fight fire with flames	`Wed Dec 11 1991 06:59`	3
	The last time I saw problems like this was when the license expired. -Matt.
1888.4	Checked lmf	DUCAT2::FOUR62::LICAUSE	Al Licause (338-5661)	`Wed Dec 11 1991 11:20`	16
	RE:.3 I did have muliple licenses for DECmcc and variants so I deleted all known instances of DECmcc license using LICENSE DELETE MCC.../AUTH=.... I then doubled checked to make certain that the only remaining licenses were the two listed in the T1.2 directory. I then rebooted the system and saw the same results as in .0. I suspect it is more then likely some combination of T1.2.3 and V5.5 of VMS and V1.0 of DECnet/OSI (aka WAVE II), as witnessed by one of your engineers who has dialed into my system. Thanks for the suggestion, Al
1888.5	please check your dispatch table	TOOK::CALLANDER	MCC = My Constant Companion	`Tue Jan 14 1992 10:45`	7
	are you sure that you ran the mcc_startup? and that you have a new dispatch table. check the date on the mcc_system:mcc_dispatch_table.dat. Make sure that you only have one (if you have two the on in specific will be the one used), and that the date on it is new.
1888.6	DECmcc with DECNET/OSI (VMS 5.5)	TEMTY::L_GROSSMAN		`Wed Jan 15 1992 09:10`	7
	We determined that the DECmcc EFT V1.2 contains a routine that reads the physical ethernet address. Wave II decnet does not support the IO function that we used. Once we overcome this incompatibility (code is being rewritten) we will have a better understanding how MCC works with DECNET/OSI