Conference azur::mcc

    
    1) The latest version of the AM guide refers to a YOURMM framework
    module in chapter 11. Is this framework part of a new release of the
    toolkit, and if so, is this new toolkit available ? 

The design framework is new for EFTU.  It will be available with EFTU.

    2) What services does an AM have to provide in order to be able to
    REGISTER entities using the CONFIG/ REGISTRATION FM ? Does it have to
    provide a REGISTER entry point, or does the Register command simply
    call, say a <SHOW, entity, all id> to check if the entity exists? Maybe
    I skipped something in the documentation, but I have been unable to
    find this information. 

Yes, this info is missing from the Guide ;)--sorry.


This is from a mail message from Kathy Joe Nelson, PL for the Config FM --

One of the requirements for putting global objects on the map is  that
they  be  REGISTERed.   REGISTERing entities means storing the current
values of the intance identifiers in the DECdns namespace.

MCC is a global entity, and therefore,  instances  of  MCC  should  be
REGISTERed so that they can be found by other MCCs, appear on the map,
and be managed by MCC.  Inorder to put MCC instances into  the  DECdns
namespace  (i.e.,  REGISTER  MCC instances), we defined MCC to have an
instance identfier.

The management of MCC through the iconic interface requires  that  the
instance  identifier  of  MCC  and  its components be available to the
Configuration FM through the DIRECTORY directive.

Support of this  requirement  constrains  the  Management  Modules  to
supply  a  SHOW  IDENTIFIERS entry point for the Management Module MoM
interface.  In addition, the Configuration directives should be  added
to the management interface MSL of each Management Module.
    
The SHOW IDENTIFIER entry point should return a null instance.  The
following code should be used to construct the null list returned in 
out_p.

put param begin (reply code)
put cons begin (arg code) mode = list
put cons end
put param end
       

    re: .1, answer to question 2
    
    The answer only seems to address registering instances of MCC. I expect
    the original question was getting at the more important question of
    registering the entities with which the AM is providing the manager
    access.
    
    The answer is not as simple as I'm about to present - but I'm sure the
    experts in the area will fill in the details (- hint!)
    
    In general, to be able to Register the entities your AM is allowing to
    be managed only requires that the AM support the SHOW <entity> ALL
    IDENTS service. In special cases - typically where the AM needs to keep
    orphaned attributes (whatever they are :-}) on behalf of the entities -
    would the AM need to provide a REGISTER <entity> service.
    
    Of course, if you read the Registration (n�e Config) FM chapter in the
    MRM, this will all be explained clearly.
    
    And of course the Guide will/does (Darryl?) explain this too?
    
    Colin

    Thanks for these answers. Colin has indeed clarified my question, I am
    concerned about registering my own entities. Thanks anywyay to .1 as
    this explains why I haven't been able to place the MCC Icon on my map ! 
    
    Concerning the "MRM", is this the same as the "MCC Configuration FM
    System Reference Manual Appendix" (The one I have dates back to octobre
    1989) ? Are the MRM's available on the net ?
    
    Thanks, 
    
    Philippe. 
    
    

    To add (slightly!) to what Colin has stated.
    
    Entities that require a register entry point currently include:
    
    	BRIDGE, STATION, TERMINAL SERVER, TRANSLAN, and <probably>
    	all of our existing 3rd parties.
    
    A REGISTER entry point is needed for your entity at least in those
    cases where:
    
    	(1) Your entity has identifiers that are not in a locally
            accessible database, and FullName is foreign to the
            Agent -or-
    	(2) Your entity uses more than just FullName as an identifier,
            and User is specifing the others (i.e., Ethernet Address
            for Station/Bridge/ Terminal Server/Translan) -or-
    	(3) Config/Registration FM has not added special-case code to
            handle you automatically (I believe SNMP is being special-
            cased)
    
    I believe that Darryl will be adding information about this to the
    Guide to Writing an AM (and eventually code into the Framework).

    						Chris Brienen