Conference azur::mcc

    Here's a few things you could try... first of all, you don't state what
    version of MCC you're using.  I assume BMS V1.3? You might want to
    start by editing the MCC_STARTUP_BMS.COM (or whatever it's called) it's
    in SYS$STARTUP.  There's a call in there that rebuilds the dispatch
    tables for MCC.  It is commented out by design.  Try uncommenting it
    and then rebooting.  Put the comment back in after/if you stablize.
    
    Next you might try a REBUILD of your dictionary.  You need to get into
    MANAGE/TOOL to do this.  Remember, you need to not have the IMPM or any
    FCL processes active or you won't be able to write to your dictionary.
    
    You said you tried the CMA library notes stuff that's plastered all
    over this conference.  I used to use it on a regular basis, since I
    upgraded to VMS V6.0.  I noticed they got it right in T1.4.  If your
    client can wait until March when it's officially released they will be
    able to fix this CMA library problem no doubt.
    
    Out of curiosity, when you say you're receiving these CMA errors, is
    this when you startup MCC (at system startup time), when you use the
    FCL or when you run the IMPM?  I have seen problems with running
    MANA/ENT but NOT when I run, MANA/ENT/INTER=DECW
    
    This is kind of far-fetched, but you put the CMA library files in which
    area?  Did you perhaps, put them in a specific root of a VAXcluster
    instead of SYS$COMMON:[SYSLIB].  They really should go in common...
    
    Let me know how you make out with this... I've got a pretty large
    installation that I'm getting ready to deploy and I'm glad to see this
    product has regained some interest... I can use all the help I can get!
    
    /Mic
    
    

    Mic,

    customer will try to rebuild dispatch tables, hope we'll have results
    in a couple of days.

    About your questions:

    Version is EMS 2.3, so that BMS is 1.3.

    CMA errors are received either in FCL and IMPM. Don't know about startup
    but probably there are also.

    Customer put CMA files in a directory out from system disk. Is this 
    correct?

    I'll keep you informed. Thanks and regards,

    Herminia.

    PS: My personal opinion: i like much more MCC since I know Netview...
    management of entities, performance and reports, it's nicer with MCC!
                                            

Customer has done a reboot to the station this morning with rebuild of
dispatch tables, and problem still remains.

After that she stopped every mcc process and start a 
MANAGE/TOOLKIT/DICTIONARY REBUILD

After processing entity 1 4 9 0 she has obtained a SYSTEM-F-ACCVIO. Don't
have more details about address. Anyway, she can access to her dictionary
normally, with same WRONG_CMA as always.

One question: both operations (rebuild tables and rebuild dictionary) have
been done without defining CMA logical names, so she was using newest 
libraries. Is it correct or should I define logicals pointing old libraries
before rebuild?

If you have any new idea, please let me know...Regards,
Herminia.

Herminia,

 - if the customer does not wants to go back to VAXC (not everybody is a masochist like us)
   can she go the DECmcc V1.4, i.e. POLYCENTER Network Manager 200 V1.4 or POLYCENTER Network 
   Manager 400 V2.4 ? 

   That would solve the CMA image hassle.


 - If that upgrade cannot be done, hang on:

     you need the OLD versions of CMA, which look like:

	CMA$LIB_SHR.EXE;4        176/177     30-APR-1992 14:39:20.00
	CMA$OPEN_LIB_SHR.EXE;4    12/12      30-APR-1992 14:39:19.00
	CMA$OPEN_RTL.EXE;6        24/24      12-JUN-1992 16:40:43.00
	CMA$RTL.EXE;6            257/258     12-JUN-1992 16:41:12.00

     if you have them DO NOT PUT THEN IN SYS$LIBRARY. If you do that
     you will make DECmcc work but al the rest will break. Put them
     'somewhere', far away form where other users might find them.
     Create a special directory for them or something similar

     you need the OLD version of VAXCRTL, which looks like:

	VAXCRTL.EXE;2            209/216      8-JUL-1992 00:54:11.00

     this one should have stayed in SYS$LIBRARY by the installation
     of DEC C.

     make a small DCL procedure like this:

	$ define/job MCC_DECTHREADS  'somewhere'
	$ define/job CMA$LIB_SHR       MCC_DECTHREADS:CMA$LIB_SHR.EXE
	$ define/job CMA$OPEN_LIB_SHR  MCC_DECTHREADS:CMA$OPEN_LIB_SHR.EXE
	$ define/job CMA$RTL           MCC_DECTHREADS:CMA$RTL.EXE
	$ define/job CMA$OPEN_RTL      MCC_DECTHREADS:CMA$OPEN_RTL.EXE
	$!
	$ manage/enterprise 'P1

     this should do the job. P1 can be used to specify /interface=decwindows


Dirk
 

    Second try for the rebuild of dicctionary was successful after 50 hours
    of elapsed time!
    
    After rebuild she still had errors for CMA. She then tried again
    defining logicals as pointed in .4 and now, magically, start working
    without errors.
    
    Probably she had some mistake first time. Thanks Mic and Dirk for your
    kind help,
    
    Herminia.