Conference azur::mcc

	Raja,

	When you  say  you  "installed DECmcc v1.0 at a customer site",
	you really mean  DECmcc  SMS  V1.0  or  DECmcc  EMS  V1.0.   We
	recently have shipped DECmcc  SMS  V2.0  and  DECmcc  EMS V2.0.
	Both  SMS  and  EMS are  package  names.    They  both  contain
	individual products such as LTM, RBMS,  TSM,  NMCC,  *and* with
	the V2.0 include DECmcc BMS V1.0

	There will be a relase of SMS  and  EMS V2.1 which will include
	DECmcc BMS V1.1

	Over time all the point products such as  LTM,  ETHERnim,  TSM,
	etc. will be replaced by the DECmcc BMS.

	Confused?  Don't worry if you are.

	The packaging is being re-worked although there isn't any  sure
	fire easy way to describe it.  We are trying to improve it.

	Regards,

	JCE

    John,
    
    Thanks for the explanation. There are few other things that I noticed
    that didn't quite make sense.
    
    The release notes was not part of the manual (it was part of the
    saveset); and the strange thing is, after installing the product (the
    release notes gets copied to sys$help), I read the Rel. notes and it 
    advises you to read the Rel. notes before installing !!!
    
    Also, the installation guide says that it is enough for the MCC station
    to be a DNS client, but most of the mcc_system:MCC*.com files look for
    dns$control (available only on the DNS servers).
    
    So much for my griping.
    
    Raja

    your "gripes" are legitamate concerns. I have forwarded these items
    to the V1.1 DECmcc dir/bms project lead. It is up to him to decide
    how to best address your concerns.
    
    thanks for the feedback.
    

  You can install any product and just get the release notes.  That is, the
  release notes are copied to the system (SYS$HELP) but nothing else is
  done in terms of the installation.  The release notes, and the documentation
  indicate that the release notes should be read, in their entirety, before
  the installation of the product is done.  This is VMSINSTAL OPTIONS N.
  Then, after reading the release notes, you can go back and do the full
  installation without OPTIONS N.

  DNS$CONTROL is used (extensively) in MCC_DNS_SETUP.COM.  This procedure
  is a tool which is used to set up your DNS environment.  You are right
  that this must be used on the DNS server, which may not be where you are
  installing DECmcc.  I just finished reviewing the DECmcc V1.1 Installation
  Guide, which calls this out along with what files must be taken over to
  the node where the server lives.  I don't know explicitly how this was
  documented in the DECmcc V1.0 installation guide.  However, although the
  MCC_DNS_SETUP.COM procedure uses DNS$CONTROL, you should not have to use
  DNS$CONTROL directly to set up for DECmcc.
								- Dave

    Well, I don't work for DECmcc engineering, but.... Re; .-1
    
    On one hand, the RELEASE NOTES are always expected to be read before
    installing a product. That's why VMSINSTAL provides a way to get at
    em without installing the product first.
    
    On the other hand, I guess it wouldn't hurt to point out early in the
    installation manual that the release notes should be checked for any
    information that might have not made it into the doc set.
    
    s/rob

    
    Raja,
    	
    	You should have read the DECmcc Management Station Installation
    Guide, Section 1.5, Page 1-6 Release Notes, which says,
    
    	"The distribution kit includes release notes, which contain
    information that is not in this documentation.  Digital Equipment
    Corporation STRONGLY RECOMMENDS that YOU read this information BEFORE
    proceeding with the installation"
    
    It continues to describe how to access them.
    
    Hope you did this....
    
    
    Kandha 
    CSSE