[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

4011.0. "Warning: SSB WaveII and DECmcc phaseIV management" by TOOK::PURRETTA () Mon Nov 02 1992 17:49

It has come to our attention (note 3974) that you cannot manage a
DECnet phaseIV node from MCC if you're running on the SSB version
of the VMS DECnet/OSI software (waveII).  A change they made just before
the SSB release introduced a bug which broke the DNA4 Access Module.

The VMS developer has been informed and is in the process of providing
a fix.

If you are an internal site and wish to use MCC in this manner, I'd
suggest not upgrading your VMS DECnet/OSI software to the SSB version
until this fix is available.

They are also planning to get this fix out to the customer sites
but I don't know the distribution details.

I will update this note with more details as they come available.
    
John
T.RTitleUserPersonal
Name
DateLines
4011.1Fix knownTOOK::PURRETTAFri Nov 06 1992 17:374
    I have just tested a new (fixed) CML.EXE from the VMS development
    group and it does indeed fix the problem.  So a fix is known and
    will be distributed (by them) as soon as possible,
    
4011.2Distribution of bugfixTOOK::PURRETTAWed Nov 25 1992 12:4622
This is how VMS DECnet/OSI engineering plans to fix this problem.
    
    
Subj:	We're working on it


We are still working out the plan by which we 
create and ship fix kits to DECnet customers.
I expect the plan to be finished after some meetings 
tomorrow afternoon.

The fixes will be packaged together and given to 
the CSCs according to Standard 204.

If you believe that the customer is suffering 
a service outage by not having the fix today, 
please contact Pat Taylor and let her know.
We can arrange to send the fix individually, as
long as the fix kit is also sent to the 
customer when it is ready.  

Jim
4011.3Location of fixed CML.EXETOOK::PURRETTAThu Jan 07 1993 12:1522
This was extracted from the DECNET/OSI notes conference on how to
    obtain the fixed CML.EXE
    
    
      <<< BULEAN::BULEAN$USER:[NOTES$LIBRARY]DECNET-OSI_FOR_VMS.NOTE;1 >>>
                 -< DECnet/OSI for VMS (aka DECnet-VAX Wave2) >-
================================================================================
Note 450.1                     CML patch needed...                        1 of 4
BULEAN::TAYLOR                                       11 lines  18-DEC-1992 11:51
                        -< Fix is being made available >-
--------------------------------------------------------------------------------
    
    Hi,
    
    Have a look on the BAGELS:: default directory for CML.EXE.
    
    Colorado has a copy for customers that need it today and
    can't wait for the whole Wave2 fix kit to be made available.  
    The first Wave2 fix kit is in progress.
    
    Cheers,
    Pat                
4011.4DECnet/OSI ECO kit infoTOOK::PURRETTAFri Jan 22 1993 11:4013
      <<< BULEAN::BULEAN$USER:[NOTES$LIBRARY]DECNET-OSI_FOR_VMS.NOTE;1 >>>
                 -< DECnet/OSI for VMS (aka DECnet-VAX Wave2) >-
================================================================================
Note 411.1             Wave2 and DECmcc phaseIV management                1 of 1
BULEAN::TAYLOR                                        6 lines  18-JAN-1993 19:58
                   -< First fix kit is on the way to SQOIS >-
--------------------------------------------------------------------------------
    
    The fix for CML.EXE is in the first ECO kit for DECNET/OSI,
    located on TRUMP::[.DNVOSI]DNVOSIECO01010.A.
    
    Pat
    
4011.5DNVOSI update kit wrong protection on CML.EXETOOK::PURRETTAWed Jan 27 1993 14:074
    The CML.EXE as packaged in this kit gets installed on the system
    with the wrong protection so it doesn't get executed.  After the
    upgrade, change the protection to W:RE, otherwise you'll still
    see the problem.