HP3000-L Archives

August 1996, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Duane Percox <[log in to unmask]>
Reply To:
Duane Percox <[log in to unmask]>
Date:
Thu, 15 Aug 1996 08:14:38 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (120 lines)
The following text is my quick analysis of what I heard/learned from
various sources at HP World related to the life of MPE and the 3000.
 
Some of this information comes from sessions given by HP, some from
major talks given by HP execs (like Harry Sterling). Additional
information comes from sources outside HP in either sessions or
conversations held during the conference.
 
Please folks - these are my comments. Do not assume my conclusions are
absolute fact. I am posting this to motivate positive discussion so that
we might somehow influence HP's decision making. Besides, your take on the
same information might be entirely different. Let the dialog begin.
 
Information/Rumor Points I Gathered
-----------------------------------
0. Talks given by HP top management mentioned the HP 3000 in the same
   sentence as the HP 9000. The slides they showed didn't have any references
   to the HP 3000 or MPE. When they did reference server type systems they
   most always said: "HP 3000 and HP 9000" or "MPE and Unix". They obviously
   paid attention to the audience demographics.
 
1. Attendees gave the HP management roundtable quite an earful and from
   comments it appears they (HP) got the message: support the HP 3000!
 
2. Harry Sterling (boss of the HP 3000) was very passionate about continued
   support for the HP 3000 and protecting customers investment in the
   product line.
 
3. MPE has been ported to the the PA-8000 (in 32 bits, not 64) and systems
   will be announced in the fall (the first ones will be midrange). 64 bit
   support will be investigated in fiscal 1997.
 
4. In addition to the PA-8000, there are now two faster chips HP has announced
   MPE support for: PA-8200 and PA-8500. The PA-8500 was not originally
   planned, but due to delays in the HP/Intel chip faster PA-RISC chips
   were needed.
 
5. HP won't shut down PA-RISC immediately after the HP/Intel chips begin
   shipping. Comments indicated about a 1-3 year overlap depending on
   the source.
 
6. 64 bit support using the PA-8xxx chip set is a tough issue for HP. This is
   another fundamental platform shift and they are worrying about how to
   continue support for the non-64 bit PA-RISC systems if they move forward.
 
7. HP has committed to telling us their plans for supporting the HP/Intel
   chip in January 1997 (strategic video conference). They have committed to
   giving us "a five to 10-year growth map for the HP 3000 product line" at
   the same video conference.
 
8. George Stachnik gave an interesting talk and from it I gleaned that:
   - the costs to port MPE to the HP/Intel chip came in much higher than
     was anticipated. Due in part to having to rewrite all the low level
     i/o subsystem stuff (what do I know...I'm a Cobol programmer)
   - creative solutions have been proposed internally from making MPE a
     subsystem of HPUX or NT to sharing the low-level i/o modules from the
     HPUX team. In addition, multiple funding models have been proposed to
     support the port.
   - HP is working now to crunch all these ideas and come up with their
     best plan for possible support of the HP/Intel chip. They have been
     given marching orders from Harry to have it figured out in time to
     announce it in January 1997 (see item #7).
 
9. It appears more and more of MPE software products are being farmed out to
   'mature' status. This means no active enhancement unless the SIG enhancement
   lists give the item high priority. Unfortunately, the compilers find
   themselves in this category.
 
10. Rumor has it that a number of MPE engineers are still working for CSY, but
    have been contracted out to GSY to work on the HP-UX Kernel. Hopefully this
    is a way to keep the MPE talent in an age of shrinking revenue/budget and
    they will be able to move back to MPE projects. If not, there still is a
    benefit if they can bring MPE solutions to the HP-UX systems team.
 
11. There was lots of talk about MPE 5.5, but nothing on 6.0. I think item
    #10 might have something to do with this.
 
12. HP 3000 sales revenue is not growing much if at all.
 
Subjective Comments Based on the Whole
--------------------------------------
1. It seems HP is working hard to make HP-UX more stable and bullet proof.
 
2. It seems HP is working hard to grow the NetServer line to support larger
   NT installations.
 
3. It seems HP is working hard to give people an easy path from the HP 3000
   to other options (HP-UX/NT).
 
4. It seems HP has come to the conclusion they will not get any major software
   vendors to port to the HP 3000 (I would agree with this).
 
5. There are many s/w vendors who only support the HP 3000 who are still doing
   a bang up job selling systems (in spite of HP).
 
 
My Forecast (remember, these are my opinions - not facts)
---------------------------------------------------------
1. MPE will not be ported to the new HP/Intel chip.
 
2. Therefore the HP 3000 has a ten year growth life span. The platform
   will be around for much longer than that and will continue to be
   supported ala MPE/V systems.
 
3. HP 3000 systems will be ported to all PA-RISC chips including
   the unannounced versions that will be developed during 2000-2003.
 
4. HP will make a 64 bit MPE only if their survey of major customers
   indicates this is needed. Otherwise we stay at 32 bits. However,
   we will get some pseudo 64-bit support like a larger file system.
 
Of course, we'll know for sure in January 1997!
 
 
Duane Percox  (QSS)
[log in to unmask] (v:415.306.1608 f:415.365.2706)
http://www.aimnet.com/~qssnet/
 ftp://ftp.aimnet.com/pub/users/qssnet/
Don't miss the 'Land of QWEBS'... http://qwebs.qss.com

ATOM RSS1 RSS2