Conference azur::mcc

    This is one of those "known" problems... I do not support DECmcc, but I
    use it frequently and have seen this bug... What you want to do is get
    the CMA libraries from your previous version of MCC, V1.3 and place
    those in your system library... 
    
    If you said, NO to purge files as part of the installation, you're all
    set, just rename the older version of the CMA$-whatever files to a
    higher version, reboot and you should be ok... you might want to look
    in the BMS_STARTUP file and uncomment the line that rebuilds the
    dispatch tables... then reboot.  This will ensure you've got a fresh
    copy... Once you've rebooted, place the comment sign back in, it's
    unnecessary...
    
    If you get stuck, send me mail at SCASS1::GALVIN.  I'm out of the
    office and don't have all the particulars...
    
    good luck,
    
    /Mic
    
    PS There was a restriction with OpenVMS V6.2 and BMS V1.4  A patch is
    available and I've tested it out... works fine.  I'll provide a pointer
    for it as well if need be...
    
    cheers
    

    Hi Mic,
    		thank You Very Much for your quick answer.
    
    I could see, as You explain in .1, two solutions:
    
    1. Using previous CMA libraries.
    2. Upgrading OpenVMS to 6.2 and Patches.
    
    The customer asks me for an upgrade of VMS from 6.1 to 6.2 but, looking
    at this conference, MCC 1.4 seems not supported on VMS 6.2.  
    
    If I could upgrade VMS to 6.2 and with patches MCC 1.4 could work, the
    solution 2 is the better solution looking at the future. Solution 1 
    will be implemented only as a remedial to avoid a continously crashing
    situation.
    
    Please send me a pointer to patches if possible.
    
    Thank You Very Much.
    
    Bye
    
    Giuseppe
                                                          

Hi Guiseppe,

I don't remember if it was for you but please find above the status about 
that point.

Formely, DECmcc V1.4 is not supported on VMS V6.2. To help some customers, 
we did 2 different patches which seem to work correctly. But, we never got 
back a real status of how they work in production site. All the tests we 
did here (but there are not stress tests, but manual tests) are ok ! 

Mic Galvin who already answered you has also tried them without any
problem... and he knows very very well DECmcc.

So, with Mic's help, we are confident that the patches solve the problem.

The patches location is : 

TAEC::DISK$USER4:[MCC_PUBLIC.MCC_V140_PATCHES.EXEC.FIX05]

MCC_KERNEL_SHR_DIRECT_CALL.EXE;5        
MCC_KERNEL_SHR_NEWTHREAD_CALL.EXE;2
RELEASE_NOTES_KERNEL_FIX05.TXT;2


where TAEC address is 51.40

Please read carefully the associated release notes to install the patch.
In fact, it's very easy, and you can come back easily too doing the reverse 
procedure. So, any production system will not be impacted too long in case 
of problems.

Note :  I recall you that this OpenVMS version is not officialy supported, but
in case of problem, be sure we will do our maximum to satisfy your requests asap.

Hope this help you.

Best regards,
Philippe Tabone - DECmcc Maintenance Team -

    Phillipe,
    
    My whole career I wanted to be the MCC guru...smile...
    
    cheers,
    
    /Mic