HP3000-L Archives

May 1999, Week 2

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:
John Zoltak <[log in to unmask]>
Reply To:
John Zoltak <[log in to unmask]>
Date:
Fri, 14 May 1999 10:44:31 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Ron Seybold writes:
> NewsWire: What's the latest word on the decision to support
> Classic 3000
> 16-bit code in 64-bit HP 3000s?
>
> Wilde: We have looked at this a little bit, but it's much too
> early to say
> anything conclusive about it. We need to figure out what the
> customer needs
> are and what makes sense technically as we plan our roadmap.
>
> Our gut feeling at the NewsWire is that CSY will support this
> code, so long
> as there are enough customers out there who need to run it on
> the IA-64
> systems

To answer this, just look at PUB.SYS and see how many PROG's there are.
You have to say HP is a big customer of 16 bit classic code. Some of the
PROG's I found that really stick out are, DBRESTOR, DBSTORE, EDITOR,
ENTRY, FCOPY, FORMSPEC, HPSLATE, HPWORD, IDSCHAR, IDSFORM, INITNLS, LOAD
- a big one here, NMMAINT, NMMGRVAL, SORT, TTUTIL, VMERGE.

Seems to me that HP still has a lot of classic code that would have to
be reworked, big time. If it hasn't made it into native mode by now, who
knows if it will later.

John Zoltak
North American Mfg Co
Cleveland Ohio

ATOM RSS1 RSS2