From: S.Sandrock 
                                                           Date: 23 Oct 1997

=
	VLT-SW-NOV97 - RELEASE NOTES FOR VCC CONFIGURATION
        ==================================================

* Fixed Problems
----------------
  SPR 970256: vccEnvStart returns too early
  SPR 970335: vccEnvCreate: Problems overriding the LCU host
  SPR 970366: vccInfo/msql: Better diagnostic message in vcc


* Off-line environment creation support
---------------------------------------
  One can create the environment files now on an off-line machine, eg:

    vccEnvCreate -env lasm0 -dest woff:

  would create the files on woff, with a warning like:

    Warning: Files are created on woff, but only operational when moved to wasm!

  Note however that the on-line machine is still asked via remsh about the
  physical path to VLTROOT, INTROOT, etc., so that the user running vccEnvCreate
  must have on-line access to the final target host (don't forget .rhosts).

  vccEnvDelete will similarly delete the off-line files.
  For the other vccEnv* programs off-line operation makes no sense,
  and is ignored or will yield an error.


* LCU multi-network & multi-CPU extension
-----------------------------------------
  So far only single-CPU systems with one ethernet port were supported.

  The vccEnv* programs as well as the vccConfigLcu panel support now
  LCU environments with multiple LAN interfaces (in connection with
  NET01 boards and net01 driver) and those with master and slave CPUs.
  See the man-page vccConfigLcu(1) for a detailed description;
  the changes - also with respect to the ACC database - are summarized 
  below.

- Multiple network interfaces:

  Instead of only one hostname, there are up to four assigned in the ACCDB:

        station_name  - the booting interface
        station_name0 - the on-board ethernet interface
        station_name1 - the 2nd ethernet interface
        station_name2 - the 3rd ethernet interface

  For vcc purposes, station_name0 may be left empty for non-slave CPUs.
  Then is implicitly station_name assumed as on-board ethernet interface.
  Interactive configuration with vccConfigLcu is supported.

- Multi CPU systems:

  Master and slave CPUs need a differently configured VxWorks kernel.
  The selection is done exclusively from the BSP value, eg:

  "mv167"       - normal kernel for single CPU systems
  "mv167-p0-s8" - for master CPU (#0), 8MB memory size
  "mv167-p1-s8" - for slave #1, 8MB memory size

  All further configuration is then done by setting the proper
  options for the VxWorks kernels, see vccConfigLcu(1).

  These kernels need to be present under $VXROOT/config/.
  As restriction, the IP addrs for these systems MUST implicitly be in 
  ascending order; since they are assigned at VxWorks level, the ACCDB
  contents must be consistent with that.

- ACC database:

  Three fields in the table prog_environment have been added,
  namely station_name0/1/2.
  This requires that all existing SQL data sources for the ACCDB must be
  changed. With this command-line one can do it automatically:

   sed -e "s|\(prog_environment.*\)\(, *[01][^,]*\)|\1,'','',''\2|" <file>

                               ___oOo___