[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

4433.0. "%MCC-E-INVREPOS, invalid Repository ID" by CHILKA::JAGGI () Mon Jan 25 1993 08:59

I have met the following problem in installing DECmcc EMS 2.2 or BMS 1.2.3,
at the point where BMS is executing the BMS startup procedure and try to 
enroll the NOTIFICATION_FM and EXPORTER_FM.

	%MCC-I-REPOSEXIST, repository already exists
	%MCC-E-INVREPOS, invalid Repository ID

Configuration Environment
-------------------------
WorkStation 4000-60 / 48Mb / 2*RZ25
VMS 5.5-2
DECnet VaxExtension V 5.5-1
DECmcc EMS 2.2 or BMS 1.2.3
Local Name Space
DTSS not started
DNS clerk started for (DQS needs)
RDB V 4.1 run time

I have already install EMS 2.2 on a customer running DECnet Phase IV
(not DECnet VaxExtension) with local name space, and I have not got any
problem.

o Do you know what cause could make DECmcc display these error messages ?
o Could these error messages be related with the fact that DTSS is not used
  on this site ?
o Could you comment more these messages, as doc is saying : Programmers 
  look at your code !!!

Below you will find the details of:

a) Extract of the installation procedure, where the two following messages
   are displayed :
	%MCC-I-REPOSEXIST, repository already exists
	%MCC-E-INVREPOS, invalid Repository ID

b) Extract of some investigations. I have uncommented the first line of the 
   BMS startup file in order to get the detail of the startup (OPTION=ENROLL). 
   Below you will find the detail.

c) Image analysis output of EXPORTER_FM and NOFICATION_FM


Any help is welcome

Michel

==========================================
a) 
   Following the DECmcc BMS start-up the DECmcc BMS
   IVP command procedure will be invoked.

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

   Beginning DECmcc BMS Post Installation Procedure ...

   Deleting obsolete DECmcc verbs...

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

DECmcc (V1.2.3)
%MCC-I-REPOSEXIST, repository already exists
%MCC-E-INVREPOS, invalid Repository ID
MCC 0 ALARMS RULE __dummy_test AT 22-JAN-1992 15:04:06 
Data base error occurred while storing rule information.
                   MIR Status =%MCC-E-NOREPOSEXIST, repository doesnot exist
%MCC-E-NOREPOSEXIST, repository does not exist


The MCC_STARTUP_BMS startup procedure for DECmcc V1.2.3 is now ending.
   Completing DECmcc BMS Post Installation Procedure ...

   Beginning DECmcc BMS Installation Verification Procedure ...
   The IVP for DECmcc BMS will now be run.

DECmcc (V1.2.3)
MCC 0
AT 22-JAN-1992 15:04:11
Test Successful

DECmcc (V1.2.3)
MCC 0 FCL 
AT 22-JAN-1992 15:04:16
Test Successful
...
...  all OK up to the following below
...
DECmcc (V1.2.3)
MCC 0 PA
AT 22-JAN-1992 15:05:14
Test Successful

DECmcc (V1.2.3)                       <----------------- ?????
%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 EXPORTER_FM, TO FILE = MCCBMS$OUT.TXT"
   DECmcc BMS V1.2.3  Installation Failed

================================================================
b)
I have uncommented the first line of the BMS startup file in order to get
the detail of the startup. 

$ IF ((OPTION .EQS. "ENROLL") .OR. (OPTION .EQS. "UPGRADE"))
$ THEN
$       IF F$SEARCH("sys$system:mcc_main.exe") .NES. ""
$       THEN
$!              Enroll the Director Management Modules.
$               ON ERROR THEN $GOTO DISPATCH_SET_PROT
$               manage/enterprise/presentation=mcc_fcl_pm
DECmcc (V1.2.3)

                do mcc_system:mcc_enroll_dir.com
                do mcc_system:mcc_enroll_bms.com
enroll MCC_ALARMS_FM       MCC_ALARMS_FM
enroll MCC_NOTIFICATION_FM MCC_NOTIFICATION_FM
%MCC-I-REPOSEXIST, repository already exists           <---------- ?????
enroll MCC_COLLECTION_AM   MCC_COLLECTION_AM
enroll MCC_HISTORIAN_FM    MCC_HISTORIAN_FM
enroll MCC_EXPORTER_FM     MCC_EXPORTER_FM
%MCC-E-INVREPOS, invalid Repository ID                 <---------- ?????
enroll MCC_PA_FM           MCC_PA_FM
%MCC-S-VERIFYEXIT, exiting command procedure DKA200:[MCC]MCC_ENROLL_BMS.COM;2
          create mcc 0 alarms rule __dummy_test expr=(sample foo user bytes sent = 50), proc=nl:

MCC 0 ALARMS RULE __dummy_test
AT 22-JAN-1992 16:25:02

Data base error occurred while storing rule information.
                 MIR Status = %MCC-E-NOREPOSEXIST, repository doesnot exist
%MCC-E-NOREPOSEXIST, repository does not exist
                ! Place management module specific MCC commands above this line,
 IF APPROPRIATE
                exit

=========================================================================
c)

MCC_NOTIFICATION image analysis
-------------------------------
        Image Identification Information

                image name: "MCC_NOTIFICATION_FM"
                image file identification: "DECMCC V1.2-2"
                link date/time:  6-NOV-1992 16:35:11.46
                linker identification: "05-05"
        Patch Information

                There are no patches at this time.


MCC_EXPORTER image analysis
---------------------------
        Image Identification Information

                image name: "MCC_EXPORTER_FM"
                image file identification: "DECMCC V1.2-1"
                link date/time:  6-NOV-1992 19:23:48.01
                linker identification: "05-05"
        Patch Information

                There are no patches at this time.

T.R	Title	User	Personal Name	Date	Lines
4433.1	Check the year	TOOK::GUERTIN	MCC Managing everything for everyone everywhere	`Mon Jan 25 1993 10:48`	4
	Looks like a problem with your system time. Your log files shows the system time set to the year 1992. -Matt.
4433.2	invalid Repository ID	CCEI0::RAOULT		`Mon Jan 25 1993 10:57`	181
	Hello, I had the same bug. I was installing EMS 2.2 . configuration (from scratch) : VMS 5.5-2 motif 1.1 decnet en LNO The MCC_STARTUP_ELM_AM startup procedure for DECmcc V1.2 is now running. Note: The DECmcc Director or BMS Startup procecures should be run prior to executing this procedure. DECmcc (V1.2.1) %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced MCC 0 ALARMS RULE __dummy_test AT 22-JAN-1992 19:19:14 Data base error occurred while storing rule information. MIR Status = %MCC-E-NOREPOSEXIST, repository does not exist %MCC-E-NOREPOSEXIST, repository does not exist The MCC_STARTUP_ELM_AM startup procedure for DECmcc V1.2 is now ending. Completing DECmcc ELM AM Post Installation Procedure ... Beginning DECmcc ELM FM Post Installation Procedure ... The MCC_STARTUP_ELM_FM startup procedure for DECmcc V1.2 is now running. Note: The DECmcc Director or BMS Startup procecures should be run prior to executing this procedure. DECmcc (V1.2.1) The MCC_STARTUP_ELM_FM startup procedure for DECmcc V1.2 is now ending. Completing DECmcc ELM FM Post Installation Procedure ... Beginning DECmcc TSAM Post Installation Procedure ... The startup procedure for the DECmcc Terminal Server Access Module V1.0.0 is now running. DECmcc (V1.2.1) MCC 0 TERMSERVER_AM AT 22-JAN-1992 19:20:00 Normal operation has begun. The startup procedure for the DECmcc Terminal Server Access Module V1.0.0 is now ending. Completing DECmcc TSAM Post Installation Procedure ... Beginning DECmcc ETHERnim Post Installation Procedure ... Completing DECmcc ETHERnim Post Installation Procedure ... Beginning DECmcc LTM Post Installation Procedure ... LAN Traffic Monitor V1.2.0 initialization procedure Completing DECmcc LTM Post Installation Procedure ... Beginning TSM V1.6 Post Installation Procedure ... Completing TSM V1.6 Post Installation Procedure ... Completing DECmcc EMS V2.2 Post Installation Procedure ... Beginning DECmcc EMS V2.2 Installation Verification Procedure ... Beginning DECmcc BMS Installation Verification Procedure ... The IVP for DECmcc BMS will now be run. DECmcc (V1.2.1) MCC 0 AT 22-JAN-1992 19:20:17 Test Successful DECmcc (V1.2.1) MCC 0 FCL AT 22-JAN-1992 19:20:28 Test Successful DECmcc (V1.2.1) ... ... all OK up to the following below %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 EXPORTER_FM, TO FILE = MCCBMS$OUT.TXT" DECmcc BMS V1.2.2 Installation Failed *********** $ mana/e MCC> use ver MCC> @mcc_common:mcc_enroll_bms.com %MCC-S-VERIFYENTER, entering command procedure SYS$COMMON:[MCC]MCC_ENROLL_BMS.CO M;1 enroll MCC_ALARMS_FM MCC_ALARMS_FM %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced enroll MCC_NOTIFICATION_FM MCC_NOTIFICATION_FM %MCC-I-REPOSEXIST, repository already exists ***************** enroll MCC_COLLECTION_AM MCC_COLLECTION_AM %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced enroll MCC_HISTORIAN_FM MCC_HISTORIAN_FM %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced enroll MCC_EXPORTER_FM MCC_EXPORTER_FM %MCC-E-INVREPOS, invalid Repository ID ******************** enroll MCC_PA_FM MCC_PA_FM %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced %MCC-S-VERIFYEXIT, exiting command procedure SYS$COMMON:[MCC]MCC_ENROLL_BMS.COM; 1 MCC> Thanks in advance. FabricE Directory SYS$SYSROOT:[SYSUPD] MCCEMS022.A;1 270 21-SEP-1992 11:25:51.00 MCCEMS022.B;1 702 17-SEP-1992 13:42:59.00 MCCEMS022.C;1 1386 17-SEP-1992 13:43:15.00 MCCEMS022.D;1 198 17-SEP-1992 13:43:39.00 MCCEMS022.E;1 324 17-SEP-1992 13:43:47.00 MCCEMS022.F;1 306 17-SEP-1992 13:43:56.00 MCCEMS022.G;1 2898 17-SEP-1992 13:44:05.00 MCCEMS022.H;1 594 17-SEP-1992 13:44:46.00 MCCEMS022.I;1 2340 17-SEP-1992 13:45:02.00 MCCEMS022.J;1 80172 17-SEP-1992 13:46:06.00 MCCEMS022.K;1 1026 17-SEP-1992 14:05:46.00 MCCEMS022.L;1 3168 17-SEP-1992 14:06:13.00 MCCEMS022.M;1 1206 17-SEP-1992 14:07:11.00 MCCEMS022.N;1 2808 17-SEP-1992 14:07:57.00 MCCEMS022.O;1 3312 17-SEP-1992 14:08:58.00 MCCEMS022.P;2 5832 3-DEC-1992 10:58:45.00 MCCEMS022.Q;2 8802 3-DEC-1992 11:00:20.00 MCCEMS022.R;1 5274 17-SEP-1992 14:14:01.00 MCCEMS022.S;1 3654 17-SEP-1992 14:15:14.00
4433.3	See reply .1	TOOK::GUERTIN	MCC Managing everything for everyone everywhere	`Mon Jan 25 1993 11:28`	0
4433.4	Same problem, same solution, and same difficulties figuring it out	DATABS::KOHLS	Ruth Kohls	`Mon Feb 01 1993 12:50`	14
	Hi Matt, If I hadn't seen this note I would never have guessed that it was the mis-set system time that was causing MCC installation to fail. I didn't do the system or the MCC installation, they were done by different people, and the people who did the MCC installation are justifiably mad and mystified. How is anyone supposed to guess what is going on from that error message? I have an inkling what both sides are up against, and I so I'd suggest adding some error handling for items of this sort to the IVP. The mad and mystified user is going to demand their money back, not use the product. �And in this case, I get to take the flak. Ruth Kohls
4433.5		RAMPAL::GUERTIN	MCC Managing everything for everyone everywhere	`Mon Feb 01 1993 13:25`	11
	Hi Ruth, Yes. It is a bug. But since it is rooted in a misconfigured environment and the workaround is straight forward, it never became more that a medium priority qar. And you know what happens to medium priority qars when the product has a difficult deadline to meet. All I can do is put it on the list for the next release. -Matt.