Conference azur::mcc

    Carlo:

      Hmmm...  
 
      First of all, Can you show some rules?

      SHOW MCC 0 ALARMS RULE * ALL CHAR

      If you get the same error (and I suspect you will), then somehow 
      MCC_MIR_DIRECTORY.DAT (in mcc_common) is not pointing to the two 
      alarms' repository files in mcc_common.

      Did sys$startup:MCC_STARTUP_BMS.COM run correctly when the BMS kit was
      installed?  This file CREATES and then DELETES a dummy alarm rule to
      force the creation of the alarms repository.

      If you have no rules in mcc_alarms_attribute_mir.dat and 
      mcc_alarms_instance_mir.dat, then I would suggest that you 
      delete these two files and then try creating a rule again.
      These two files will get automatically created.

      > I'm now running The T1.0.1 IFT2 Version.

      BTW, I think that you mean the T1.0.1 EFT Update version?
   
      Some more questions:

        Were all MCC files in mcc_common deleted before installing the 
        T1.0.1 EFT Update BMS kit?  Maybe some leftover .dat files are 
        causing this anomaly?

        What are the values of the mcc_system, mcc_specific and mcc_common
        logicals?  mcc_system should be a search list that points to 
        mcc_specific and then to mcc_common.

      Hope this helps.  Let me know if it doesn't...

                                                                      - Jerry
     

  Jerry,	
 
>>     First of all, Can you show some rules?

	No I got a similar error this time for read the database.


>>    Did sys$startup:MCC_STARTUP_BMS.COM run correctly when the BMS kit was
>>    installed?  This file CREATES and then DELETES a dummy alarm rule to
>>    force the creation of the alarms repository.

	Yes the whole installation for the EFT update run fine and after THIS
	installation I could also store and use alarm rules perfectly.
	The problem started after I installed the "MCC V1.1 internal field
	test kit" .

>>    I'm now running The T1.0.1 IFT2 Version.
>>    BTW, I think that you mean the T1.0.1 EFT Update version?
 
	The way I see it,I had the updated version EFT running in the 
	installation referred to as MCCBMSUT011 also DECMCC BMS T1.0.1 
 	also MCCBMSUT V1.1 , and after this I installed MCC V1.1 Internal
	Field Test also X1.1.0 also MCCBMS2X V1.1...... Confused?
      
	So I'm running the MCC version with the domains and icons but if I
	fire up MCC the displayed version looks like this:
	$mcc
	DECmcc (T1.0.1)
	MCC>

	Anyway,
>>    If you have no rules in mcc_alarms_attribute_mir.dat and 
>>    mcc_alarms_instance_mir.dat, then I would suggest that you 
>>    delete these two files and then try creating a rule again.
>>    These two files will get automatically created.

  	I did this but the result was the same.
   
	Then I manually run MCC_STARTUP_BMS.COM which enrolled MCC_ALARMS_FM ,
	MCC_ENET_AM  and MCC_BRIDGE_AM  and afterwards tried to store a alarm
	rule all worked fine and MCC_ALARMS_ATTRIBUTE_MIR.DAT and 
	MCC_ALARMS_INSTANCE_MIR.DAT were created!!!.

	
	There is one other thing I wonder,
	If I do:
	$mana/enter/pres=mcc_decw_pm     Which is in the documentation of the
	DECMCC_USE_V11_IFT2 Guide (page 2-3)  I get:

%LIB-E-ACTIMAGE, error activating image $1$DUA7:[SYS12.SYSCOMMON.][SYSLIB]MCC_DE
CW_PM.EXE;
-RMS-E-FNF, file not found
%MCC-E-FINDUSYM, Failure finding universal symbol (!AS) in shareable image (!AS)

	But if I run it like this:
	$mana/enter/inter=decwindows    All works fine and I can draw my map.

	Regards Carlo.
	        
       
     

    
    That is an error in the manaul. The windows interface name if
    MCC_ICONIC_MAP_PM, use the command:
    
    $MANGE/ENTER/PRES=MCC_ICONIC_MAP_PM
    
    This should work for you. The writer has been informed of the error.
    
    

  Carlo:	
 
    > Then I manually run MCC_STARTUP_BMS.COM which enrolled MCC_ALARMS_FM ,
    > MCC_ENET_AM  and MCC_BRIDGE_AM  and afterwards tried to store a alarm
    > rule all worked fine and MCC_ALARMS_ATTRIBUTE_MIR.DAT and 
    > MCC_ALARMS_INSTANCE_MIR.DAT were created!!!.

    I looked into this problem a little bit more...

    It seems that the BMS2 kit T1.0.1 IFT2 kit installed the following file:

      [MCC_ROOT.BUILDS.UT1_0_1.SAVESETH]MCC_MIR_DIRECTORY.DAT;1

    over the one which already was in mcc_common from the installation
    of the EFTU kit.

    As mentioned in my previous response, this file contains pointers to all
    the repositories.  Thus the pointer to the Alarms respoitor was wiped out 
    by the installation of the BMS2 kit.

    This is a bug, but I'm not sure what will be done about it.  The fact
    that the BMS2 kit installed *over* the EFTU kit is (supposedly) a one 
    time only phenomenum.  Anyway, I'll pass the word along to the kit 
    install person to make sure that this doesn't happen again in the future.

    Deleting the two Alarms files and executing the BMS startup command 
    procedure is the only way to take care of this problem.  If there are rules
    in these files, I suggest that the Alarms extract rules utility be run
    prior to installing the BMS2 kit over the EFTU kit.  Then you can re-create
    the rules after the BMS2 kit has been installed.

    Sorry for any inconvience and thanks for pointing out this problem to us.

                                                                       - Jerry
   

    
    Jerry,
    
    Thanks for the quick answers and good support!
    
    Carlo.

  Re: .3

    That's correct, MANAGE/ENTERPRISE/PRES=MCC_ICONIC_MAP_PM will do it, but
    with the IFT Update the preferred way to invoke the Iconic Map is

		 MANAGE/ENTERPRISE/INTERFACE=DECWINDOWS

								- Dave