>>FROM: Eric Schubert <[log in to unmask]>
>SUBJECT: Re: My vision for the HP3000 and MPE
>DATE: Thu, 15 Feb 1996 17:05:28 -0500
>
>>From: Alfredo Rego:
>>
>>Important issues for us at MPE-land:
>>
>>(s) Storage
>>
>>From my (admittedly narrow) perspective of MPE as viewed through
>>database-colored glasses, I consider the "HP3000 package" (composed by the
>>HP3000 hardware, the MPE operating system and the IMAGE/SQL database
>>management system) as a huge repository of bits.  While these bits are in
>>the HP3000's custody, they must be kept safe, private, and consistent.
>>THIS is where the HP3000 excels.
>
>DFS can distribute them globally.  In a global secure and manageable manner.
 
Good.  But you have to deal with lots of Unix vagaries.  If you want to
deal with Unix, that's ok, and more power to you.  However, there are a few
conservative business types out there that would rather deal with MPE and
reserve their sleepless nights for running their businesses.  They don't
want to hire Unix gurus!  That's the whole point.  Admittedly, this is a
matter of taste.  Some people would rather fiddle with Unix.  There is
nothing wrong with that.
 
 
 
>>(i) Input
>>
>>Bits COME IN through a variety of means (people typing away at dumb
>>terminals, or PCs, or Macs, or Unix workstations; barcode readers; batch
>>input from other computer platforms; and so on).
>>
>
>And don't come in by way of open standard protocols.  No surprise the 3k is
>not known on the Internet.
 
I don't quite understand this negative reference to "open standard
protocols" (i.e., DO they or DON'T they come by way of open standard
protocols?)   Perhaps I should understand this as "[they] don't come in [to
the HP3000] by way of open standard protocols" (meaning that the HP3000
uses its own non-standard protocols)?  If so, then I second your desire to
provide standard protocols to the HP3000.  PDQ.
 
 
 
>>(o) Output
>>
>>Bits get REPORTED to people (or to other machines) so they can make
>>decisions based on the states of those bits.  These reports range from
>>old-fashioned reams of line-printer paper to pretty colorful PostScript
>>pages, from ASCII-only dumb terminals to fancy GUIs on Macs, PCs or Unix
>>workstations.  Let's not forget batch transmissions to other computer
>>platforms.
>>
>
>Same arg as Input.
 
Same support for your request.  PDQ, too.
 
 
 
>>(c) Connectivity
>>
>>These comings and goings of bits happen through serial connections, through
>>Ethernet connections, through TCP/IP connections, or through a combination
>>of these (and other) protocols.
>>
>
>To borrow President Clinton's 1992 campaign 3 second sound byte, "It's the
>economy stupid" - replace "economy" with "protocols".
 
I absolutely agree.  That's been one of my points (even before Clinton's era):
If we don't have standard protocols, we cannot have outstanding components.
 
 
 
>Alfredo simply described a generic computer system.  Just as any business
>knows if you can get a solution done faster, cheaper, better than the next
>guy AND CAN DELIVER IT,  you are a winner.
 
Is "Alfredo simply described a generic computer system" a complaint or a
compliment?
 
The only reason anybody bought an HP3000, to begin with, is that the HP3000
was "a solution done faster, cheaper, better" and the only reason for my
concerns is that I would like it to CONTINUE being so.  This only requires
a little bit of tender loving care on HP's part.
 
 
 
>The critical part in today's computer environment is the interfaces and
>delivery methods.
 
Right on.  Let me reiterate from a few paragraphs above:
 
>To borrow President Clinton's 1992 campaign 3 second sound byte, "It's the
>economy stupid" - replace "economy" with "protocols".
 
I absolutely agree.  That's been one of my points (even before Clinton's era):
If we don't have standard protocols, we cannot have outstanding components.
 
 
<< snip some good stuff >>
 
 
>If you want customers, you must remove entry barriers.  The ultimate
>examples of removing barriers is free Internet software (netscape clients
>and free Adobe PDF readers) and hang on to the things you can control - like
>the servers and the Adobe editor. And standard interfaces, like VT100 Telnet
>protocol clients - and now WWW.
 
Agreed.  In 1992 (again, before Clinton's era) I fought for (but lost)
having the SQL interface for IMAGE freely distributed to EVERY HP3000.  I
can still remember, distinctly, Glenn Osaka (the General Manager of CSY at
the time) telling me that "it would not loook good in his report card."
Sigh!
 
 
 
>NS/open is another example of barrier removal (but just a nudge).
>
>This is yet still another aspect of the whole picture.  It doesn't address
>the eroding advantages of owning a 3k.  I still like my VOS (Virtual
>Operating System) idea, but only Mr. Hewlett or Mr. Packard can call that one.
 
You have just brought in the right level of HP management, Eric   :-)
 
 
 
>Radical Change for sure.
 
Nothing short of a radical change (by definition) will accomplish your
worthy objectives, Eric.  Your objectives, by the way, are shared by the
entire HP3000 community (with the few exceptions that are necessary to
prove the rule).
 
 
 
Radically yours,
 
 
 
 
+---------------+
|               |
|            r  |  Alfredo                     [log in to unmask]
|          e    |                           http://www.adager.com
|        g      |  F. Alfredo Rego               Tel 208 726-9100
|      a        |  Manager, Theoretical Group    Fax 208 726-2822
|    d          |  Adager Corporation
|  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
|               |
+---------------+