Conference azur::mcc

    re.0
    
    The access violation error only occurs if another process runs DECmcc
    i.e. Alarms Batch Job or User running interactive DECmcc.
    If I start DECmcc on the System alone and enble Notifacation at this
    time, no MAP error messages or access violation appears. After the
    notfication is enabled, I submit the Alarm Job in batch. If the alarm
    detect an error, the Notfication will be stopped for the Domain where
    the alarm was detect, with the same MAP error message in .0.
    But the Access violation error on the process screen, where DECmcc was
    started, did not appear.
    
    Uwe  
    

My guess is that your 400 domains are probably all dynamic domains, and that
a significant portion of those domains contains a majority of the others.
I am curious to know if the entire 400 domains are setup in a single
hierarchy?!

When you start up the map, notification is started for each dynamic domain
within the domain that was started (all the way to the bottom of the
dynamic domain hierarchy). This, along with alternate identifier translation
are what is taking so long. For V1.2 some changes will be made to move some
of that processing down into the notification FM. Doing this will allow us
to put the request in an seperate thread, allowing the UI to continue while
the setup is on-going (user visible performance enhancement, but events won't
start coming through until setup is complete).

As to the accvio and errors, if you have the alarms error that would help
in figuring out what is going on. One potential problem could be memory.
I need to know how your domains are structure so as to estimate the number of
threads (and the amount of memory) that is being used to setup the notify
commands. Also if you have the time, I would like an FCL log of the
equivalent function.

$ deassign mcc_init
$ define mcc_fcl_pm_log 28
$ define mcc_notification_fm_log 8
$ manage/enter
MCC> notify domain xxx

You will need to do a notify command for each domain in the hierarchy (dynamic)
under xxx. Best to run it using a set host/log to capture it all.

thanks
jill

    About the IMPM problems when you have the alarms batch running before
    starting IMPM, there was another note somewhere in here that had a 
    similar problem.  I believe the problem is due to a bug in the IMPM
    where we are not locking global data structures that are shared.  What
    is most likely happening is that the map structures are still being
    initialized, and the notification code is attempting to read/write
    to those structures because notification is being received.  
    
    We are in the process of putting mutexes around these global
    structures, in time for v1.2.
    
    Christine
    

I have a customer who was experiencing problems similar to those reported
in .0 and .1.  He had in excess of 100 domains that I believe are all dynamic.
Some of the domains were created just to represent pc's on the wan that
could not be registered.  They wanted representation of the pc's so information 
about the lcoation etc. could be stored.

They have removed the domains that were pc's and got the total down to 88.  Now
notification doesn't get stopped as it originally did.  He has even added some
of the domains back and is now at a total of 98.

Is there some magic number of domains at which point the notification fm can't
handle the load?  Is it based on the number of alarms also or is it just due
to the number of domains?

My customer is an internal DEC person working as a resident on a customer site
and could probably provide more information as needed.

Thanks'

Walt

    it is based on the amount of memory you have. Each domain requires
    the notification FM to request gevents for that domain from the alarms
    FM. This memory usage adds up. Please use reference entities instead
    of domains for displaying non-manageable devices.
    
    jill
    

    Reply to .6
    
    Is there some way to increase the amount memory that DECmcc has
    available in the event that all of the domains are true domains and not
    being used for keeping track of the pc's?  Can I check to see how much
    memory is being used for notification?  Could you also expand on
    'reference entities'?
    
    Thanks
    Walt

    please be patient with us, we are in the middle of reworking the
    notif/alarming interaction so that it scales better for the larger
    (read that as alot of domain) environments. We should have this
    resolved shortly so that this becomes a non-issue for you.
    
    As to reference entities, this is a new class of entity that was
    defined as a "place-holder" for non-manageable (either because they
    really are non-manageable or just because you don't want to manage
    them). You can maintain reference information on them but nothing more.
    They are useful for drawing pictures of your environment, or
    maintaining inventory information on miscellaneous hardware.
    
    jill