Conference bulova::decw_jan-89_to_nov-90

    DECwindows/VMS is part of VAX/VMS V5.1
    It can be seperately and optionally installed (using DECW051)
    because it is a very large amount of software and many customers with
    smaller system disks would not have room for it.
    (even most customers with larger system disk tend to fill them up)
    
    I would look in the VTX infobase for the VMS V5.1 SPD.

    Just curious: are there parts of DECwindows (is the "official" name of
    DECwindows for a VMS system called "DECwindows/VMS") that are in VMS
    before the DECW051 kit is installed. In other words, is DECwindows/VMS
    a semi-SIP? Or another way: is there any parts of DECwindows/VMS that
    can be used before the DECW051 kit is installed? If not, couldn't you
    say that any layered product is "a part of VMS"?
    
    Thanks,
    
    -Glenn-

RE: .2

SIPs are things that ship with the VMS kit but that we charge separate license
fees for.  Examples are the DECnet multi-node support and volume shadowing.
DECwindows ships on the VMS kit (in a different group of save sets), but you
do not need any additional license to use it.  Therefore, it is not a SIP.
As mentioned previously, the ONLY reason that DECnet comes in separate save sets
from the rest of the VMS kit is that it is large and not all systems need the
files installed.

--PSW

Actually the main reasons that DECwindows comes in a separate save set is
because

	1.  We were building and field testing separately for a good long time
	2.  We did not have time to work out all the procedures for completely
		integrating.

The current plans are for separate save sets to be eliminated in future versions
of VMS.  However, last I knew, the installation procedure was planned to be
smart and not install unneeded things on small disks.  Plus there will always
be the VMSTAILOR facilities.

But in any case, the answer to .2 (I think...asking if there are pieces of
DECwindows in the VMS save sets):  the answer is essentially yes.  Things like
RMS, COPY, FAL, ... support for tagged files, as well as extensions to loginout
were done as part of DECwindows,
but are currently on the VMS save sets.  Essentially these are components that
initially part of VMS, but modified for DECwindows.  The stuff currently in
the DECW save sets is completely new files.  (General rule...there may be
exceptions).

Burns

The term SIP was invented with CDROM in mind.  In the future "ships
with the VMS kit" won't mean much because everything will be in
the kit in the sense that the customer will consider the CD to be
the VMS kit and saveset tactics will be a detail.

Thus SIP is meant to make a business/quality/engineering statement
along the lines:

	"A System Integrated Product is one that is closely
	integrated with the base operating system to obtain
	enhanced performance, seamless operation, and improved
	quality."

When positioning against competition, we can point out that the
SIP engineering style beats the layered style.

When you think about it, those really _are_ the underlying
reasons we consider when deciding that DECnet, VAXcluster,
Journalling, Shadowing, and DECwindows will be engineered
by a close team, on the master pack, and on the kit.

A SIP is a lot more than "just on the VMS kit".  If RUNOFF
was separately licensed, we still wouldn't call it a SIP.

- greg

After coining this term a product manager suggested that "Integrated
System Product" might be better.  I agreed but it was too late to
turn the ship again.

- g