Conference azur::mcc

| After installing ELM V1.0...

    Do you really mean V1.0, or do you mean T1.2.4?  Onto what base system
    are you installing which ELM kit?

    The ELM T1.2.4 kit only installs on BMS T1.2.4.

| I then went back to a system where ELM had not
| been installed and the directives were there for the bridge subclass
| line.
    
    I don't understand.

    How could you have a system without ELM installed where there were
    dictionary entries for bridge?

    Yes, 
    
    I really meant ELM V1.0, on BMS V1.1.
    
    Steve

Hi Steve,

For DECmcc BMS (and DIR) V1.1 systems, new entities must be augmented
to get the EXPORT and RECORD directives.

For the BMS V1.1 kit, the Bridge entity was already in the dictionary.
This dictionary had the Bridge EXPORT and RECORD directives in place.

When you installed ELM V1.0 (which contains an "extended-functionality"
Bridge AM) the new BRIDGE information replaced the existing stuff,
in effect erasing the EXPORT|RECORD directives.

The ELM AM V1.0 Release Notes should describe how to augment BRIDGE (and 
CONCENTRATOR) to get them added back in...

						Chris 

P.S. This problem disappears in V1.2,
     since all entities get these
     directives automatically.

    As part of the installation procedure of the ELM V1.0 kit, the bridge
    entity was augmented for the Exporter and Historian.  Here are the
    lines from the KITINSTAL that did this:

$ manage/toolkit/dictionary
    [...]
 AUGMENT CLASS BRIDGE FROM MCC_HIST_BRIDGE.COM
 AUGMENT CLASS BRIDGE FROM MCC_EXP_BRIDGE.COM
 AUGMENT CLASS BRIDGE SUBCLASS LINE FROM MCC_BRIDGE_LINE_STATISTICS.COM
 exit

    Did the ELM V1.0 installation procedure run to completion?  There were
    options to put off updating dictionary/parse tables/help files.  Were
    these operations performed at a later time?

    You could try these commands manually and see what happens.  If you
    don't have the .COM files on your system, I can get them to you.

Before looking at .4, I started looking at the MCC_ELM_BUILD_DICT.COM file
provided with the install kit.  I believe it is missing 2 lines:
	$ @mcc_hist_aug bridge line
	$ @mcc_export_aug bridge line
This belief is based on the comments in MCC_HIST_AUG and MCC_EXPORT_AUG where
it states that the hierirchy (SP) needs to be pulled out, the MCC_HIST_AUG 
showes examples for the NODE entity and children.  The problem here being that 
once the dictionary had been build by MCC_ELM_BUILD_DICT, its too late to
go back as the directives for the line entity lo longer exist.

This would seem to necessiate a complete reinstall of MCC and ELM, so that 
MCC_ELM_BUILD_DICT can be edited to include the 2 lines indicated above before 
building the dictionary and parse tables.  I am in the process of testing this
at this time.

MCC_ELM_BUILD_DICT.COM at in the install kit.
$!
$!	This command file builds the DECmcc ELM dictionary for following
$!	base systems:
$!
$!	DECmcc BMS,  DECmcc SMS, DECmcc EMS.
$!
$ set default mcc_common
$ @mcc_hist_aug bridge 
$ @mcc_export_aug bridge   
$ manage/toolkit/dictionary
 update class bridge from mcc_bridge_am_svc_if.com
 update class mcc subclass bridge_am from mcc_bridge_am_mgt_if.com
 load class concentrator from mcc_conc_am_svc_if.com
 load class mcc subclass conc_am from mcc_conc_am_mgt_if.com
 AUGMENT CLASS BRIDGE FROM MCC_HIST_BRIDGE.COM
 AUGMENT CLASS BRIDGE FROM MCC_EXP_BRIDGE.COM
 AUGMENT CLASS BRIDGE SUBCLASS LINE FROM MCC_BRIDGE_LINE_STATISTICS.COM
 exit
$ delete MCC_HIST_BRIDGE.COM;*
$ delete MCC_EXP_BRIDGE.COM;*
$ exit

Well installing ELM without building the Dictionary or Parse tables 
at install time, then editing MCC_ELM_BUILD_DICT.COM to include:
	$ @mcc_hist_aug bridge line
	$ @mcc_export_aug bridge line
then executing MCC_ELM_BUILD_DICT.COM fixed the problem.  Now all the
record/export directives are present for the bridge line entity.
    
    

    We simplified the installation procedure for V1.2 -- you no longer have
    the option of putting off updating the dictionary, parse tables, and
    help files.