Conference azur::mcc

Hi,

I saw this problem with T1.3.1. The AM's were installed in the following order

BMS
Alarm Manager
LAN Manager (ELMS)
TSAM

From the iconic map I couldn't see any TS icons (nor was there one in the 
toolbox). The IVP ran okay, and I could manage a TS via the FCL.

With SSB V1.3 I installed the AM's in the following order...

BMS
TSAM
LAN Manager
Alarm Manager

Now everything is working fine from the IMPM.

Cheers

Ian

Hi Ian,

Thanks for the confirmation that it has been seen before !!

I have tried installing it that way round, in fact with no Alarm Manager at 
all, but still no success.  I have just now finished installing it again
( yawn !) in the order that you tried, but still no joy.

Anyone any more ideas ??

Regards,

Mark Darvill

Hi, 


I have also seen this problem vhen upgrading from 1.2.3 to 1.3 and then
installing TSAM 1.0.2  all SSB kits.

I fixed it with these commands.


$ set def mcc_common
   $ manage/toolkit/dictionary
   UPDATE class mcc subclass termserver_am from mcc_ts_am_mgt_if.com
   UPDATE class terminal_server from mcc_ts_am_svc_if.com
   exit

/Niklas

Hi Niklas,

Great news.....

I have tried what you suggested.  On firing up mcc I can now access Terminal
Servers via the iconic map.

The only question now is why does this happen in the first place.  It must
be a problem during the installation of TSAM on BMS V1.3.  I will look
on the QAR database and add it if it is not already in there.

Thanks,

Mark

    The problem is as follows.
    
    If you have sufficient disk space the TSAM installation attempts to
    help get around the requirement that NO DECmcc processes may be running
    during an install by makeing a copy of the dictionary, updating the
    copy, and putting the updated copy back.
    
    In V1.2 this worked great. In V1.3 a new dictionary file,
    MCC_FDICTIONARY.CTM was added to speed up "lookinto" in the map.
    
    Since there was no new release of TSAM planned, it's KITINSTALL was
    not updated to copy the extra file back so the map doesn't know about
    the new class.
    
    The only hacks I know of (read - workarounds) is to either artificially
    constrain the amount of free disk space available with a large temp
    file or, as I recently did, wait for the dictionary update to complete
    and while the help files are updating, copy the .CTM file from the
    temp subdirectory under sys$update to a safe place and then after the
    install completes, copy it to MCC_COMMON.
    
    The problem has been reported to the TSAM developer and the fix should
    show up in the next new kit made available.
    
    s/rob

    
    
    Is it documented that TSAM must be reinstalled after upgrading BMS from
    1.2 to 1.3?  I don't remember seeing it in the release notes.
    
    

    I suspect that if TSAM were re-released then it might mention the need
    for a re-install :-) Really, every installation of DECmcc BMS since the
    first has always required all optional modules to be reinstalled
    (with the one exception of V1.2.3 if updating V1.2.0).
    
    s/rob

    
    >I suspect that if TSAM were re-released then it might mention the need
    >for a re-install :-) Really, every installation of DECmcc BMS since the
    >first has always required all optional modules to be reinstalled
    >(with the one exception of V1.2.3 if updating V1.2.0).
    
    
    	That's because the optional modules no longer worked with the new 
    	release of BMS and in almost all cases new releases of the optional 
    	modules were synchronized with the new BMS.
    
    	In this case TSAM V1.0 works under V1.3 but you are required to 
    	reinstall TSAM V1.0.  I would have expected to see this highlighted
    	in the release notes.
    
    	Bill

    fellow MCC'ers,
    
    I too am having problems with the tsam icon, so I issued the command in
    note .3, UPDATE class mcc subclass termserver_am from
    mcc_ts_am_mgt_if.com.  Here's the result:
    
    %DAP-E-ILLEGAL_COMMAND, Illegal command -- Dictionary currently open
    for read-only access
    
    Can someone inform me how to get around this?
    
    thanks,
    
    George

>    %DAP-E-ILLEGAL_COMMAND, Illegal command -- Dictionary currently open
>    for read-only access
>    
>    Can someone inform me how to get around this?

Sure.  
You can't change anything in the dictionary while there are MCC processes
running.   Exit DAP. Stop any MCC process (this includes event sink
processes) on your machine, then try again.   

/doug

    	yep, that did it.
    
    	thanks...

    just finished, got this...
    
    $ manage/toolkit/dictionary
    %MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
    %DAP-S-USE_DICT, Using dictionary file:
    sys$common:[mcc]mcc_fdictionary.dat;1
    
    
            POLYCENTER Dictionary Administrator Program   Version T1.3.1
    
    DAP> UPDATE class mcc subclass termserver_am from mcc_ts_am_mgt_if.com
    Deleting specified class from dictionary file...
    (Control C and Y will be disabled while records are being deleted)
    Percent of file processed = 100%
    Now writing processed records to dictionary file...
    (Control C and Y will be disabled while records are being written)
    DAP> UPDATE class terminal_server from mcc_ts_am_svc_if.com
    Deleting specified class from dictionary file...
    (Control C and Y will be disabled while records are being deleted)
    Percent of file processed = 100%
    Now writing processed records to dictionary file...
    (Control C and Y will be disabled while records are being written)
    DAP> exit
    Using parse table log file: sys$common:[mcc]mcc_fdictionary.log;2
    %MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
    Building containment tree file
    
    Fatal: No VM
    $
    
    after this I opened an MCC map window and still see no tsam icon.                           

1) why are you still trying to install a field test version of DECmcc?

2) Have you read the release notes about how to handle DECthreads?
   The message about CMA is probably significant.

    Erik,
    
    The version of MCC of which is already installed on my system from it's
    previous owner, whom I replaced.  This person installed MCC but never
    actually used it since he is no longer with the company.  I'm mearly
    trying to finish what he started.  Anyway, I was under the impression 
    that I'm running the latest and greatest.  Is this how I know it's a 
    test version: DECmcc (T1.3.1)?  
    
    George  

Yes, T1.3.1 was the second field test version of code that was
released as V1.3.0.  Note 3.something has the latest kit
announcement.  Installing the latest version should also clear
up any CMA problems.

-- Erik