🚀 go-pugleaf

Regarding the license and maintenance fees, many of us have no control over
that...but being as close to the product line as we are we do have some
thing to do with making sure SCI earns the money they are charging. I think
we should keep after SCI on the bundling and integration of their product line.

For example:

1) with exception of "revenue enhancement" there appears to be no other reason
to exclude VMSPOOL from the VMCENTER II bundling.

2) it took a long time to interface VMSCHEDule and VMBATCH.

3) NDM doesn't talk to anything (except ever so crudely (vmbatch)) in the
whole VMCENTER line.

4) Features implemented on one platform aren't kept at parallel releases
on the other platforms (NDM again).

5) SCI products need to support new hardware concurrently with release by
major vendors.

I'm sure there are other opportunities for their product line to be mutually
supportive to a greater extent than today.  I believe we should hold their
feet to the flame to deliver value for the money charged.

One might be drawn to the hypothesis that with all the marketing stuff on
Net/Master (and becoming a network oriented company); that VM tools is:
a) a hobby (b) a cash cow to support the "real" mission of the firm
(c) something that they will divest themselves of (like they did with
the database tools they had.

I've heard SCI lurks on the list. We didn't send anyone to last years
conference, but I'd think it beneficial for SCI to occasionally drop in
on the list and engage in dialog on upcoming plans for the product line,
features, documentation needs, whatever.

  +------------------------------------------------------------+
  |  MCI Mail:  JSchunk or 100-7026                            |
  |  Telex (MCI/WUI): 6501007026   Ans: 6501007026MCI UW       |
  |  Internet:  JSchunk@MCIMail.Com                            |
  |  X.400: C=us; ADMD=mci; S=schunk; G=joseph;                |
  +------------------------------------------------------------+