Conference azur::mcc

Hi,

>
>                MCC Errors Using the Director
>    
>    I'm getting the following error message when I click on the MCC icon
>    from the IMPM:
>    
>        MCC UNHANDLED SERVICE REPLY
>        NO SUCH ENTITY:DOMAIN LOCAL_NS:.ROCHELLE MEMBER *
>        DOMAIN LOCAL_NS:.ROCHELLE MEMBER *
>    

I got also this message when I try to look into the MCC icon.
I got this message 8 times I think. I got this message for serveral
Access Modules. Also the AM-child entities of these AM's were not displayed
in the list of AM-child entities on the screen.

This happens after I installed the Polycenter SNA manager. (SNA AM)
I think this will be caused by the new images (eg. new MCC_ICONIC_MAP_PM.EXE,
MCC_REGISTRATION_FM.EXE etc..) which are supplied with the SNA AM.

Two questions:
- Why does the IMPM does a 'show domain xxx member *' for every AM-child entity
  which exist ??
- Is there a workaround for this ??
  ( Now I can't enable my Terminal Server AM from IMPM )


Regards,

/-/	Henk.

    
    Simple solution:
    
    MCC> DEREGISTER MCC 0
    MCC> REGISTER MCC 0
    
    Long answer:
    
    Lookinto behavior has been modified to enhance performance, especially
    on Node Lookintos.  For V1.2.3 this helps a lot.  Some other work we're
    doing for V1.3 seems to have astounding impact on Node lookinto. 
    That's good news.
    
    For entities which are 'DYNAMIC=FALSE' in their MSL descriptions, we
    now use the Registered information in the instance repository instead
    of querying the entity directly.  We still do a direct query for child
    entities which are DYNAMIC=TRUE.
    
    Most of the MCC children (such as CONC_AM) are dynamic=false (which is
    the default if nothing is specified).  If a new module is added, it is
    not reflected in the registered MCC entity lookinto until a
    registration is performed either by deregistering and reregistering the
    global MCC, or by directly registering the new children.
    
    The idea of DYNAMIC=FALSE is for child entities that do not frequently
    change, so our expectation is that this is not too high a price to pay
    for the improvement you will register on Lookinto.
    
    This is what you are seeing.  Check the V1.2.3 release notes; you will
    also need to re-register DECnet/OSI nodes to maximize the value added
    by the lookinto change.
    
    -Jim Carey
    

    
    Jim,
    	Hi there.  You neglected to say whether you need to shutdown the
    server, or get out of the IMPM, or whatnot...?  I turned the IMPM off,
    and from FCL I did, DEREGISTER MCC 0 and then REGISTER MCC 0.  
    	When I turned the IMPM back on, I got the same error messages.  As
    a matter of fact, now MCC is complaining about the BRIDGE_AM also?  Any
    ideas?  I'm on a 3400 Server with a DEC 433 PC, and I'm seeing alot of
    flakey behavior...  I'm wondering if a total reboot might clear up my
    memory pointers, or whatever...?  Thanks for the detailed response, any
    other ideas???
    
    /Mic
    

Hi,

>    Lookinto behavior has been modified to enhance performance, especially
>    on Node Lookintos.  For V1.2.3 this helps a lot.  Some other work we're
>    doing for V1.3 seems to have astounding impact on Node lookinto. 
>    That's good news.


I tried to deregister the mcc entity and register it again but after that I got
the same errors. (12 times)


How can I get V1.2.3 of DECmcc, will the other AM's work with this version???


/-/	Henk.

Hi,

>>    Lookinto behavior has been modified to enhance performance, especially
>>    on Node Lookintos.  For V1.2.3 this helps a lot.  Some other work we're
>>    doing for V1.3 seems to have astounding impact on Node lookinto. 
>>    That's good news.
>
>
>I tried to deregister the mcc entity and register it again but after that I got
>the same errors. (12 times)

I installed V1.2.3 of DECmcc and installed the newest version of SNA AM, but
I have still the same problem.
The MCC child-entities are still disappeared, but the error-messages are gone.






/-/     Henk.