Conference azur::mcc

    I have the same problem too. 
    decstation5000/240
    ultrix 4.3
    mcc T1.3.1
    

RE: .0 - I have forwarded your note to the responsible development manager.

RE: .1 - T1.3.1 is old field test code.  Suggest you get the V1.3.0 kit.

I am running V1.3.0, and I also have the problem.  I have traced it to the 
point where mcc_alarm_mgr_ui dies when run either from the launch mechanism or
manually:

cesis/decmcc>whoami
root
cesis/decmcc>pwd
/usr/mcc/mmexe
cesis/decmcc>ls *alarm*
mcc_alarm_mgr           mcc_alarm_mgr_ui        temip_alarm_handling_fm
mcc_alarm_mgr_fm        mcc_alarms_fm
cesis/decmcc>file mcc_alarm_mgr_ui
mcc_alarm_mgr_ui:       mipsel demand paged executable not stripped - version 2.10
cesis/decmcc>mcc_alarm_mgr_ui
Exception: Invalid memory address (dce / thd)
Abort(coredump)
cesis/decmcc>ls -l core
-rw-r--r--  1 root      2121728 Jun  7 15:28 core

    MCC Ultirx V1.3.0 48M local MIR, remote display, no alarm templates
    added yet seems to work
    
    My mcc ultrix system just upgreaded to V1.3.0, and I have run the alarm
    manager with a display on a remote node OK.
    
    Have'nt had the chance to run the software on a local display yet.  I
    have not done anything special like register any more templates etc...
    
    Amrit

    adding the templates and creating the database are options at install
    time, if this was not selected then you will not have a database. The
    prototype has a known problem in that it doesn't return the error
    message when it can not communicate with the database, instead it
    simply exits.  Please load the database from the
    mcc_alm_mgr_templates.com.  It is an MCC command line procedure so run
    it from inside the FCL:
    
    > manage
    DECmcc (V1.3.0)
    
    MCC> do /usr/mcc/mcc_system/mcc_alm_mgr_templates.com
         (check the file name for accuracy)
    
    If there is a problem with the MIR (or the mcc_alarm_mgr_fm
    not being enrolled) this will tell you.
    
    

    one more item,
    
    
    Do *NOT* attempt to run the alarm manager kit supplied with the DECmcc
    V1.3.0 on any other version of MCC!  The alarm manager is bound to the
    kernel version (V1.3.0).
    
    

    Sorry to disappoint.
    
    First,  The command procedure is called
    
    /usr/mcc/mcc_system/mcc_alm_mgr_templates_ultrix.com instead of
    /usr/mcc/mcc_system/mcc_alm_mgr_templates.com 	but this is minor.
    
    I ran this procedure, but it showed that the procedure already ran at
    the installation time. Therefore this didn't help me.
    
    Anything else ?
    
    Regards,
    	Dominique.
    

    Additional info ..
    
    On ULTRIX system level I see two new processes as soon as I start the
    alarm manager:
    
    root   11717  0.0  0.3  364  128 p5 S   0:00 csh -f /usr/bin/mcc_alarm_mgr
    root   11718  0.0  5.3 4668 2840 p5 S   0:00 mcc_alarm_mgr_ui
    
    Does this help ?
    Dominique.

    IMHO , did you check the memory free before you try to launch the alarm
    manager ? this module seems a lot greedy with memory so you better have
    a lot of memory or a big swap file ; is mcc and sql are started you
    have already 32 M eaten ( plus ultrix own memory  use ) so start with
    adding a bigger swap space ( if you have 48 M and a lot of alarms ,
    let-s say about 4 times of disk space ( 180 M ) )
    
    	just a  decmcc user 
    				Pierre-jean selles @too 

    At the moment I run the alarm manager , this is my swapspace,
    but the alarm manager does not come up !
    
    # pstat -s
    255992k swap configured
    120884k reserved virtual address space
            100808k used (28320k text, 1056k smem)
            155184k free, 1648k wasted, 0k missing
    avail: 4845*32k 144*1k
    
    This seems enough I think !!!

    sorry, been away for a few weeks rest and relaxation (THE BEACH!).
    
    Okay could you please check the following:
    
    in /var/mcc the files mcc_alm_mgr*.* do you have sufficient privsd
    (rw) for accessing the database, there should be 4 files there
    by this name.  Also check that MCC_MIR_LOCATION points to /var/mcc
    if not check the privs on the files in MCC_MIR_LOCATION.  Now
    also check the following:
    
    mcc_dap
    DAP> sho class rule_template
    	<DATA SHOULD BE DISPLAYED HERE>
    DAP> exit
    
    If no data showed up in the dictionary then you need to load the
    data in:
    	mcc_dap
    	DAP> load from /usr/mcc/mcc_system/template_svc_if.com
    	DAP> load from /usr/mcc/mcc_system/mcc_almmgr_mgt_if.com
    
    
    From MCC check that the enrollment of the alarm manager FM module
    succeeded.
    
    manage
    MCC> show mcc 0 alm_mgr all ident
    	<THIS COMMAND SHOULD SUCCEED; IF NOT enroll mcc_alarm_mgr_fm>
    
    also check that the alarm manager can see the domains you have
    defined:
    
    MCC> directory domain *
    	<THIS COMMAND SHOULD SUCCEED>
    
    If all this fails, call me.
    

    Jill,
    
    Hope You have enjoyed very much your few weeks rest of the year,
    beacuse at Digital there is no rest possible!
    
    I give the log of all requested operations.
    
    mgkk01> ls -l /var/mcc/mcc_alm_mgr*.*
    -rw-rw----  1 root         4096 Apr 26 17:10 /var/mcc/mcc_alm_mgr_data.dir
     -rw-rw----  1 root        29696 Apr 26 17:10 /var/mcc/mcc_alm_mgr_data.pag
     -rw-rw----  1 root         4096 Apr 26 17:10 /var/mcc/mcc_alm_mgr_template.dir
     -rw-rw----  1 root         5120 Apr 26 17:10/var/mcc/mcc_alm_mgr_template.pag
    
    mgkk01> printenv
    ...
    MCC_MIR_LOCATION=/var/mcc
    ...
    
    mcc_dap
      sho class rule_template
    
    and
    
    manage 
       show mcc 0 alm_mgr all ident
    
    are totally correct.
    
    Now my question about the last operation:
    manage directory domain *
    
    Although the results seems right, I am starting to worry about the
    implcations of that directory command.  Note that we use DECdns
    distributed in a WAN.  Today we have 4 name servers, but this will
    increase to 50 or more, and with a few thenths of thousands of entries.
    
    Is this "directory domain *" command required for the normal operation
    of the Alarm manager ?
    
    Here the result of that command:
    
    MCC> show mcc 0 alm_mgr all ident
    
    MCC 0 Alm_Mgr
    AT 1993-07-14-15:57:06.174 Identifiers
    
    No attributes in the specified group for this entity.
    MCC> directory domain *
    
    Domain bc:.mcc.aln
    AT 1993-07-14-15:57:27.506
    
    Directory successful.
                                 DomainName = bc:.mcc.aln
    
    Domain bc:.mcc.belgacom
    AT 1993-07-14-15:58:59.791
    
    Directory successful.
                                 DomainName = bc:.mcc.belgacom
    
    Domain bc:.mcc.bkc
    AT 1993-07-14-15:59:00.123
    
    Directory successful.
                                 DomainName = bc:.mcc.bkc
    
    Domain bc:.mcc.brs
    AT 1993-07-14-15:59:00.553
    
    Directory successful.
                                 DomainName = bc:.mcc.brs
    
    Domain bc:.mcc.car
    AT 1993-07-14-15:59:00.912
    
    Directory successful.
                                 DomainName = bc:.mcc.car
    
    Domain bc:.mcc.gkk
    AT 1993-07-14-15:59:01.225
    
    Directory successful.
                                 DomainName = bc:.mcc.gkk
    
    Domain bc:.mcc.kas
    AT 1993-07-14-15:59:01.553
    
    Directory successful.
                                 DomainName = bc:.mcc.kas
    
    Domain bc:.mcc.lrh
    AT 1993-07-14-15:59:01.889
    
    Directory successful.
                                 DomainName = bc:.mcc.lrh
    
    Domain bc:.mcc.ohs
    AT 1993-07-14-15:59:02.229
    
    Directory successful.
                                 DomainName = bc:.mcc.ohs
    
    Domain bc:.mcc.rhc
    AT 1993-07-14-15:59:02.561
    
    Directory successful.
                                 DomainName = bc:.mcc.rhc
    
    Domain bc:.mcc.vps
    AT 1993-07-14-15:59:02.905
    
    Directory successful.
                                 DomainName = bc:.mcc.vps
    MCC>

    The story about ALARM MANAGER PROBLEM continues on note 5299.0,
    
    
    	sorry for this inconvenience.
    	Dominique.

A customer of us has the same problem under ULTRIX V4.3 with
POLYCENTER NETWORK MANAGER 200 1.3 and MCC ALARM MANAGER V1.3
(Kit: MCRUAM130 / Alarm Manager V1.0.0 for BMS V1.3.0).
The customer choosed DNS for maintaining the objects.

The alarm manager cannot be started. It exits at once with
error message: an error has occurred while obtaining rule templates
(POLYCENTER and ALARM MANAGER was fresh installed).

After we have created a domain, the error message at start time
of the alarm manager turned into:

exception: invalid memory address (dce / thd)

(like mentioned in .3).

We've checked all the recommendations which are mentioned in the
notes above, but we couldn't find the problem.

He has a second system-disk where we've installed him POLYCENTER
with LOCAL MIR. In this configuration he was able to start the
alarm manager.

The customer acts as root-user and as he told me, DNS-Namespace
is open for root.



Are there any news on this problem?


With kind regards,

Mathilde Schwemmer, Digital Service Center Munich