Hello All,

At the risk of sounding somewhat thick, can someone explain what a
"superset" is.  I've seen the term used several times on the postings to
this list, but I can't seem to find a good definition of the term.  Does it
derive from supersede? Is it a concatenation? Is is ...?

I've tried to find the word in several dictionaries, including one that
claims to have 315,000 entries; no luck.  Now I guess I can infer (am I
being redundant or is "guess" maybe a superset of "infer" ? :-) ) what a
superset is, but I'd like to make sure I understand what someone means by
the term.

My apologies to those who view such questions as trivialities.

Cary Marshall
-----Original Message-----
From: Jon Cohen [mailto:[log in to unmask]]
Sent: Tuesday, November 24, 1998 12:57 PM
To: [log in to unmask]
Subject: Re: C5506 P3 = what?


While users have been registering complaints for quite some
time, I still haven't heard a suggestion on how to improve this.

Some background:  we reset the V.UU.FF when we come
out with a major "mainline" release, like 5.0, 5.5, 6.0, etc.
In the times between mainline releases, we can come out
with Express Releases (new Powerpatch tape plus a
SUBSYS tape with retrofitted new or updated optional
(purchasable) applications), and with Powerpatch tapes.
Each Powerpatch & Express is typically a superset of its
predecessors.  They are numbers sequentially -- i.e. 6.0
Express 1, 6.0 Express 2, 6.0 Powerpatch 3, 6.0 Express 4,
etc.

Today, if the Powerpatch rolls, we update its V.UU.FF.  For
example, when we went from 5.5 Powrepatch 5 to 5.5
Powerpatch 6, the V.UU.FF went from C.55.05 to C.55.06.
Since the SUBSYS didn't change, its V.UU.FF didn't change.

I am open to suggestions, but here are the constraints:

o  Rev'ing the V.UU.FF for something that hasn't changed
    isn't good.  It causes more confusion.

o  I am bandwidth constrained -- making major revisions to
    existing manufacturing tools will have to compete with
    other worthy projects.

o  At all times, we need to distinguish between all different
    versions of release components, included the internal
    versions that are not generally released.

Given that -- what do you suggest?


Jon Cohen
Commercial Systems Division
Hewlett-Packard


Gary Dietz wrote in message ...
>I would have to respectfully disagree.  The convention is not easy to
follow - at least for us "mere mortals" out here in user-land.  This has
been a bone of contention for years and it continues to amaze me that HP is
unwilling to put this information into plain English.  It would seem to be
such a simple thing to do, and it would make so many people happy.  Sigh...
>
>Gary Dietz
>
>>>> Richard Bayly <[log in to unmask]> 11/23 8:34 PM >>>
>You definitely have powerpatch 6. The 55 is the MPE/iX release (5.5), and
the 06
>is the powerpatch level. The P3 you see is the build no, so it will vary
from
>powerpatch to powerpatch. Personally I was confused by the naming
convention when
>I first started using 3000s, but the convention is easy to follow (us HP
people
>have to stick together).
>
>Richard Bayly
>Hewlett-Packard Response Centre Australia
>
>Stan Sieler wrote:
>
>> Hi,
>>
>> We just received our HP 3000 918DX ... and it got here quickly!
>> (We ordered it last Tuesday).
>>
>> However, we're trying to figure out what HP preloaded on it.
>>
>> The HPSWINFO file shows:
>>
>>    C5506 P3
>>
>> So...is that Powerpatch 3, or Powerpatch 6?  #$%^& ARGH! #$%^&
>>
>> Private note to Jon Cohen:  Yes, the version ID problem of MPE *STILL*
sucks!
>>
>> --
>> Stan Sieler                                          [log in to unmask]
>>                                      http://www.allegro.com/sieler.html
>
!
>

!
>