Conference azur::mcc

The errors you are getting from the IVP show that either the dictionary and
parse tables, or just the parse tables have not been updated. When it 
asked you if you wanted to update the tables what did you respond?

The IVP can only succeed if you update the dictionary with the concentrator
and rebuild the parse tables. The reason it is optional at instal time is
so that multiple modules can be installed and then the dictionary and
parse tables updated once for all.

jill

	Finally I have a running DECmcc EMS with ELM010!!

What did  not work:

- Restoring all the Dictionary, Parse Table and Help files as described in the
  ELM010 release notes
- Reinstallation of ELM010 (purging old files) and updateing Dictionary,
  Parse Tables  and Help Library  and running the IVP immediately after the
  installation.

ELM010 failed as described in .0 during the IVP

What did also not work:

- Reinstallation of EMS V2.1 (purging old files)
- Reinstallation of ELM010 (purging old files) and updateing Dictionary,
  Parse Tables  and Help Library  and running the IVP immediately after the
  installation.

ELM010 failed as described in .0 during the IVP


What did work:

- Recopying the whole saveset over the network
- Reinstallation of EMS V2.1 (purging old files)
- Reinstallation of ELM010 (purging old files) and updateing only the
  Dictionary, but not the Parse Tables  and Help Library  and running the IVP
  immediately after the installation.
- Reinstallation of all other option modules and updating the Parse Tables and
  Help Library during the installation of the last option module.


				Regards

				Roland

    I am having the same problem installing elm010. I will follow Roland's
    advice but I think it is pretty crummy to have to go through this. I am
    doing this to preapre for a customer demo. But I sincerely hope no
    customers experience this problem.
    
    After installing elms (with the IVP failing), I also found many
    inconsistencies in the bridge object as described in note 1417. FDDI
    state and optical bypass state show up on the iconic map when you pull
    down the show menu for a line. But if you try to show those things, the
    command fails. 
    
    I have read the release notes. Are we missing someting with this elm
    installation? Or is this a very fragile release?
    
    Liz
    

    I have encountered the same problem exactly.
    
    I am currently trying the installation of ELM010 AM again, but updating
    the Dictionary only.  I hope it works.
    
    What has happened here?  This is a very important customer issue
    requiring some immediate attention.
    
    Please help.
    
    -dh

    I'm the person responsible for kitting and installation of the next ELM
    package.  I'll make sure that these problems are addressed in the next
    release.

    RE .4 -- Did any of the things mentioned in reply .2 help?  Are you
    able to install the Concentrator AM, or are you stuck?

    I'm trying to avoid re-installing everything again since I have an
    implementation schedule to meet.  I have tried manually rebuilding the
    parse tables.  No go.  I'm stuck.
    
    -Dan

Installing of MCCELM010 on a DECmcc BMS system failed during the IVP. 

	mVAX 3800, 16 MB, RF71
	VAX/VMS V5.4-1, 	DECmcc BMS V1.1
	Modules installed 	SNMP V1.0
				TSAM T1.0.1
  	       		Upgrade	SNMP V1.1.1 (+CHIPcom EMM 5100M-MGT private MIB)

The test directive worked successfully with the bridge AM, but not with 
the CONC_AM.

Also registering a concentrator does not work correctly.

Nevertheless, CONC_AM is seen as a child entity of MCC director global
entity ; directives applied on it seem to work correctly.

	Iconic Map directive SHOW MCC 0 CONC_AM ALL CHARACTERISTICS

			Component Version : V1.0.0


Registering a Concentrator with the Toolbox returns the following error
message in window box :
 
"Entity class specified is not currently enrolled. Please check spelling."


Output from the FCL interface:

MCC 0 BRIDGE_AM
AT 23-AUG-1991 10:22:27

Test successful.

test mcc 0 conc_am
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed

show mcc 0 bridge_am all char

MCC 0 BRIDGE_AM
AT 23-AUG-1991 10:22:58 Characteristics

Examination of attributes shows:
               Component Identification = "DECmcc Bridge AM"
                      Component Version = V1.2.0

show mcc 0 conc_am all char
%MCC-W-ATTRUNKNOWN, unknown attribute CONC_AM



During a first installation, a capacity system disk problem made, via
AUDIT_SERVER process, all VMS processes suspended. So, when I discovered the
situation, I did PURGE/LO sys$sysdevice:[000000...] and SET PROC/NONSUSP/ID=...
to continue the installation.

Because IVP phase failed and previous written problem occurred, I rebuilt the 
Parse Table (in fact, the Dictionary itself seemed to have been updated 
correctly -command $MANA/TOOL/DICT and SHOW following by USE CLASS CONCENTRATOR
and SHOW again- all seemed to be OK). After rebuilding, the problem still
existed. So, I restored MCC_DICTIONARY.DAT, MCC_MIR_DIRECTORY.DAT,
MCC_DEFINITION.DAT and MCC_MIR_ATTRIBUTE.DAT and did the installation again
(with rebuilding non-restored HELP files).

The results were the same as previously. 


Is there anyone who has an idea of solution ?

Many thanks.
Renato

PS : The parse tables are rebuilding again, maybe...

    

    See if there are old files in MCC_SPECIFIC.  When you run MCC, make
    sure you are pointing at the correct dictionary, parse table and
    dispatch table.

    Also, try re-enrolling the AMs:

    MCC> enroll mcc_bridge_am mcc_bridge_am
    MCC> enroll mcc_concentrator_am mcc_concentrator_am

    If these don't help, I can't think of anything else to do other than
    do the installation again.

    
    DEelm AM V1.0 now works correctly !
    
    Effectively, an old version of parse tables existed in MCC_SPECIFIC 
    (ie SYS$SPECIFIC:[MCC]), the new none is located in MCC_COMMON 
    (ie is SYS_COMMON:[MCC]). 
    I confirmed the problem by using $SET WATCH FILE/CLASS=ALL and 
    doing $MANA/ENT -> the files (names and versions found) are displayed.
    
    So now, all is ok.
    
    Thank you for your help !!!
    
    Regards,                                              
    Renato