Conference azur::mcc

Because the CMA issue has not been properly resolved, there are
problems with DECmcc on VMS V6.0.  We see the problems when
we install DECmcc only; they go away if we install the version of
threads that ships on our kit (however, we have committed not to
replace later CMA images, so our installation procedure does not
install our images on CMA V6.0 by default).

There is no "official" resolution to this problem yet.

-- Erik

    WHAT!!!!
    
    Since Polycenter 200/400 will not install on VMS V6.0, because of the 
    CMA problem and it appears that extracting the CMA*.EXE files is now a
    no-no, what is the customer to do??? We at the CSC have been telling
    them to extract the CMA*.EXE file and copy them to SYS$LIBRARY.  This
    has worked fine, have we done something in-correct??  If there was a
    agreement between MCC engineering and VMS engineering not to superceed
    these file, why were the support centers not informed of this
    agreement?  How are we to handle this FEATURE in the future, CLD all of
    them??  Sould we reserect all past calls where this was done and CLD
    those as well??
    
    How about a little direction here!!!
    Steve Woestemeyer
    CSC/CS - Network SUpport Team

Whoah, sorry to raise your blood pressure.

Our agreement with VMS was that our installation procedure would not
automatically supercede later versions of CMA.

The fix you have recommended does in fact resolve the problem for DECmcc.
The risk is that if some other product depends on the later version of
CMA, then replacing the CMA images could create a problem for them.

-- Erik

Erik,

The issue is what message should be provided to the customers and what action
should be taken by Customer Services when presented with this dilemma?  This is
really an issue for product management and this notes conference is probably not
the place to "officially" raise this issue.  With all the activity lately around
Polycenter and DECmcc, I am unsure just who the product manager is.  If you
could post that information here I will continue working this offline with that
person.

Thanks
Doug Dickerson

    Um,
    
    My blood-pressure isn't soaring, skyrocketing is more like it.  This is
    not an acceptable answer to customers who already feel shaky about the
    support of this product, given the latest "program announcement.
    
    To me this says that every call on mcc and vms 6.0 has become a
    definite CLD.  While I realize resources are limited, we need much
    better answers on the support of this product with vms 6.0.  That or a
    silver bullet and garlic as an alternative.
    
    Meg Evans
    Also in Customer support on mcc with people who want to upgrade

I don't know what else to tell you at the moment.

As the Netview announcement indicates, we will be supporting DECmcc
on V6.0 of VMS.  But right now there are problems, as explained in
my first reply.  The workarround that you are using is fine, so long
as no other CMA dependent product is broken as a result.

I have forwarded this issue to Gail Ferreira to give the word
from product management.

-- Erik

Could anybody tell me how to proceed with CMA to make DECmcc BMS 1.3
running with VMS V6.0 ?

CMA version ?
CMA* files which must be copied/installed ?

Thanks in advance,
Jean-Mary.

    There are a couple of changes that must happen, to make PolyCenter 1.3
    work under VMS060.
    
    I took the advice in Note reply 5349.6  (how to make the CMA work, and
    fix the TimeZone issue), but I still have problems losing the window
    manager (see note 4624.*) when opening more than three Polycenter
    windows.  I've dropped back to using the command line, when I want to
    do something complex.
    
    I expect to hear something soon about the fix for the Motif window
    manager.
    
    JR
    
    
    

My collegues teaching decwindows tell me
on VMS 6.0 we install the same motif kit as on 5.5-2
So you may try Mwm$02_U1055 or its file
   [PATCHES.MWM.VMS]DECW$MWM.EXE;2                           457 

Wolfgang