[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

2964.0. "X1.2 > T1.2 upgrade problems..." by POBOX::GALVIN (Mic Galvin, MCI Team) Fri May 08 1992 12:53

    	Upgrade from BMS X1.2 > T1.2 Problems...
    
    	Hi there.  Yesterday I upgraded a BMS X1.2 station to T1.2.  I had
    assumed there was not much to it, and just applied the upgrade.  Now
    all my domains are gone and I keep getting error messages about MM's
    not being installed?
    	Is there a great deal of post installation required after
    performing the above mentioned that I overlooked?   Is it necessary to
    re-install DNS after the installation?  Thanks in advance.
    
    /Mic
    
T.RTitleUserPersonal
Name
DateLines
2964.1Which OS?TOOK::MINTZErik Mintz, DECmcc Development, dtn 226-5033Fri May 08 1992 13:364
The most important thing is that there are NO DECmcc processes
running when you do the installation.  Other than that, it depends
which operating system you are using.

2964.2CAADC::GALVINMic Galvin, MCI TeamFri May 08 1992 19:4928
    Thanks for the quick reply, Erik, the operating system is VMS 5.4-3. 
    Here's a more detailed account of some of the errors we've seen; when
    we startup MCC's Iconic Map we get several notification error messages,
    such as:
    
    "... Notification is unavailable.  Please check that the Notification
    FM is enrolled."
    
    "...The Show Identifiers operation is not supported for Domain
    'system_name_NS:.'domain_name'' Member * Supporting MM may not be
    enrolled."
    
    	When I try to open up a domain that I created prior to the upgrade
    to T1.2.7 I see,
    
    "MCC-E-NOTFOUND, unsupported combination of verb,entity,partition"
    
    	One last comment, are there negative implications to using the
    /TOOLKIT qualifier to convert the DICTIONARY database?  I thought maybe
    we saw some disk corruption or something flukey, thus the
    "...verb,entity,partion..." piece?
    
    	Thanks in advance.
    
    /Mic
    
    
    
2964.3TOOK::MINTZErik Mintz, DECmcc Development, dtn 226-5033Fri May 08 1992 20:0813
It certainly sounds like the dictionary of parse tables on your system
are corrupt.  The quick thing to check for are files in mcc_specific

>    	One last comment, are there negative implications to using the
>    /TOOLKIT qualifier to convert the DICTIONARY database?  I thought maybe
>    we saw some disk corruption or something flukey, thus the
>    "...verb,entity,partion..." piece?

This makes me a bit nervous.  What do you mean by "convert"?

    
    

2964.4dispatch tables?DADA::DITMARSPeteWed May 13 1992 13:0511
sounds like it could also be a problem with the dispatch tables.

Did your installation go smoothly, i.e. the IVP ran with no problems?

Poke around at the mcc_system / mcc_common / mcc_specific logicals to make
sure they're pointing at the right directories.

Check that the dates on the mcc_system:mcc_dispatch_table.dat look at least as 
recent as your installation.  Check the dates on the 
mcc_system:mcc_fdictionary.* files as well.  Those should be close to the
dates on the sys$library:mcc*.exe images.