June 30, 2005
Watch for migration's undertow
A lot of people think that a platform's popularity determines its longevity. That might be true in a global sense, but on the local scene, you decide if something is finished at your shop by testing the waters — the underwaters of software. Application and utility flexibility and availability: That's what marks the countdown clock for many users.
PowerHouse is a good example of a product line with layers of undertow, the current below the surface that pulls down unaware swimmers. Lately, the PowerHouse users on the PowerHouse-L mailing list have asked for support to make the language friendlier to the code editors everybody loves. Those are the ones that color-code syntax. Cognos got to work on the request and provided a start on the syntax request. But it included a warning that suggests support for PowerHouse is being reined in, bit by bit. The undertow can be hard to feel at the very first. PowerHouse has versions which don't have what the vendor calls "development support." Read the product manager's reply to see if you feel that tug of the undertow.
That Cognos manager, Bob Deskin, does a lot for the customers reading the PowerHouse list. He's got to stick with the Cognos program for support policy, however:
There is a difference between Customer Support and development support for a particular version or platform. If a customer has a support contract, they can ask about any version. However, once a version is matured or superceded, we don’t provide development support, i.e. bug fixes. Depending on how old the version is, we may not be able to test for bugs. For example, if someone calls up with a 7.10 issue, we’ve still got it installed, so we can try and reproduce a problem. However, 7.10 has been superceded so any fixes would go into the current version. On the other hand, if someone asks about 5.01 (on MPE V and it’s happened), that’s too old to have running. We will try and reproduce the problem on the current version. So if a supported customer calls up regarding 8.13, we can answer questions but since 8.13 has been superceded by 8.43 and now 8.43D1, there is no development support for 8.13.
Using older versions of software is one way that HP 3000 customers ensure stability, odd as that may seem. Better the bug you know than the one you don't, apparently. A strategy that relies on support for older versions — development support, if you will — is going to need a stronger stroke to avoid the undertow. Next thing you know, you might decide that an unsupported feature like syntax coding is reason enough to toss the whole tool overboard, and abandon ship for the migration boat.
June 29, 2005
Deep Enough to Hold a Mansion
Sometimes it takes Google to plumb the vast deeps of HP 3000 heritage. I subscribe to the Google Alerts feature, one that lets you submit a phrase to find matches of news on the Web, or just Web pages. This part of Google has been in beta for months, and my results for the 3000 make it easy to see why. I submitted "HP 3000" back in January, a phrase that has turned up lots of Web pages about engine horsepower and even HP's printer line of the same name. Only a couple of Google's e-mailed news links have ever connected me to HP3000-related "news." (I recently added an alert for "HP3000" — the space in the product's name was added in the 1990s and calls up a whole other set of pages.)
But I got a relevant alert today, even though it linked to more history than news. Mystery Mansion, Adventure — these were games the 3000's deepest resource of programmers used to unwind, though you might think being away from the keyboard would produce more of a respite. Not news to a 3000 veteran, Adventureland's report on Mansion might have been news to Google's Web-bot that trawls the Internet. Those veterans usually wax nostalgic about the days when minicomputers hosted text-only adventure games. But that heritage pays off to any 3000 user — many of these veterans are still working, all while the stability and maturity of their collective efforts performs every day for customers. How long those veterans will be working, and for whom, are the questions among customers who use older code and systems.
That's a lot of heritage still on the playing field for a computer which really is only losing its vendor's support option next year. Yes, there are shortcomings in the 3000, but what computer doesn't have them? How many of them have the ability to continue to run programs with 30-year-old syntax inside? That's an important part of the 3000's value: Being able to make resources last longer.
We ran up against that need for deep knowledge ourselves on the NewsWire team this week. Over the weekend the MPE/iX server that hosted our main Web site wouldn't restart after a controlled shutdown. Our Webmaster Chris Bartram got a workaround running within 24 hours, but fixing the 3000's problems took a couple of extra days, and some deep knowledge of Stage/iX, the 3000 patching software HP first released in 1995. John Burke did a great tutorial on the basics of Patch/iX and Stage/iX a few years back.
Chris had to search on his own in the 3000's community for an answer to get that 918 to reboot. Lucky for us, the veteran who helped was still connected to the community; I haven't found out yet if he ever took a break playing Mansion. Chris thinks the fellow is among a half-dozen in the world who know Stage/iX that deep, though it's hard to say. Knowing it is one thing. Being connected is even more important.
Community, through interactive sources like this blog and mailing lists, is the key to keeping the waters of 3000 knowledge deep. Make a few minutes to share what you know today.
June 28, 2005
A Patchwork Future on the Rise
HP continues to engineer patches for the HP 3000, but customers have been told that service will be curtailed when the rest of the vendor's support stops at the end of next year. Patches are a valuable improvement to 3000 ownership, but many customers look to patches only when they've got a problem they can't fix any other way. Workarounds are a more common method of HP 3000 repair.
I don't want to sell short what HP continues to do this year for the platform. It's a great thing that patches like NSSHD10A — which HP reported left beta status last week — are available to any HP customer. NSSHD10A repairs problems with Network Services on 3000s running MPE/iX 6.5. If you take a peek at the patch details on the HP Web site, you see the latest version of the patch prevents a System Abort 2259 in NSSTATUS — and about two dozen other Service Requests (bug fixes) from earlier in 6.5's lifespan. This is the patchwork that HP offered to continue when it extended its 6.5 support last year.
But companies that support 3000 customers don't see that work of patches as crucial to keeping the servers working in the decade to come.
The future of patches for the 3000 is a topic usually discussed in the wake of source code availability. Next week begins the period (second half of 2005) when HP said it would decide about making MPE source available outside of HP. No source means no more patches. Is that a problem?
Steve Suraci of Pivital Solutions, a third party supporting 3000s, talked about this last year. "Can we find workarounds? Almost always. We haven’t run into a situation yet where we haven’t been able to get a customer back up and running."
Steve Cooper of Allegro Consulting, the MPE support component of Resource 3000, says source code from HP to create patches isn't a critical support component. "We don’t think it’s essential that anybody gets the source. We’re prepared to meet our commitments even without the source code. " And while he'd love to see MPE source get outside of HP, he added in our December interview with him, "To a large degree, that doesn’t much matter anymore. HP has become more and more irrelevant to the 3000 community as time goes on."
Mike Hornsby of Beechglen told us back in 2002, "I have always been skeptical about patches. To paraphrase a famous coach, 'three things can happen when you patch, and two of them are bad.' " He believes customers hit bugs because "they are off the beaten path, trying to do things the hard way. We steer them back, and find a better alternative."
That sounds like a typical definition of workaround to me.
Next month's printed NewsWire lets us hear from another support provider, Gilles Schipper of GSA, who's on the same page as these other support providers, as well as soon to appear on pages of our blog. (That's an open offer to other support companies, by the way.)
"I don't think [access to HP's source] is a necessary thing for the 3000 to maintain its reliability," Schipper told me yesterday in our interview. "I'd like to see it happen, because it may allay the concerns of some customers out there." Schipper, who worked in HP's Systems Engineer (SE) organization before he launched his own business in 1983, added that he'll be posting here in the weeks to come.
June 27, 2005
Give print improvements a try
HP is looking for beta test sites starting this week, companies who want to try out the new networked printing enhancements for the HP 3000. Jeff Vance posted a note on the HP 3000 newsgroup late Friday evening, as well as on the OpenMPE mailing list, asking for beta sites:
The #1 2004 SIB item -- support non-HP printers via MPE/iX network printing -- is complete and ready for beta testing. The patch ID is: MPEMXU1A.
Please, if at all possible, request this patch so that beta testing can complete in a timely manner and thus MXU1A can be placed in General Release (GR) status shortly.
The engineering is designed to make it easier to use non-HP printers with the 3000. HP's done the work by adding a new option in networked printing's configuration file. PCL_ENABLED can be set to false, to remove all PCL sequences at the beginning and end of a spool file. You can also control flushing of the last printed page.
HP offered an update on this work one year ago, agreeing to the engineering project. Vance is referencing the last official vote on a System Improvement Ballot for HP 3000s when he talks about #1, but keep in mind that only 223 ballots rolled in. That's one reason why there was no vote on the many requests submitted for an SIB this year. Lots of ideas on how to improve the 3000, from customers still using the system. But the desire hasn't been matched by numbers that can spring loose more engineering time from HP.
Customers have wanted this kind of flexibility for 3000 printing for a long time. That's why companies like RAC Consulting and Minisoft (reselling the RAC engineering) have been able to sell a first-rate third party package to tie printers to 3000, one with fewer blind spots than this new free patch. HP's offering won't let Windows-hosted printers participate in the 3000 network printing enhancement, for example. And you'd better be on the latest MPE/iX release to use the patch, too.
HP gives a rundown on the functionality of the feature in what Vance calls "a Communicator-like article" on the 3000 group's Jazz Web site. But the vendor warns customers not to expect too much apres-engineering on this new feature one it clears beta testing:
HP will support this enhancement on a “best-effort” basis, meaning we will attempt to duplicate and resolve specific spooler problems, but we cannot guarantee that all ASCII based printers are supported by this enhancement.
June 24, 2005
What's the bail to escape patch jail?
There's nothing like testing to ensure the HP3000 will maintain its reputation for reliability. But the question is rising from users' lips: How much testing do we need in a transition era?
The enhancements that HP has been crafting for the 3000 are starting to dwindle in number. Part of the reduction of effort is all about a lack of testing from the users. In our June issue we outlined the state of patches stuck in HP's beta program. One of the customers we offered as an example reported back with an update on his patch testing efforts. Dave Powell is wondering what it takes to get a patch sprung from the beta-testing jail.
After correcting my report on what MM Fab does — they are a fabric and garment company, not a component maker — he gives the all-clear on a pair of CI patches to enable a user function to call another script or UDC as a function that would return a value using an enhanced CI RETURN command.
"I installed the patches in question back on April 2," he says, "and posted favorable comments about it on the 3000-L that day.
"I see that the two patches in question, MPEMXP9 and MPEMXQ0, are still on HP’s 'Beta Test patches for MPE/iX C.75.00' page, and I am left wondering how many customers have to test a patch before it goes off beta. I called HP in early April to 'officially' report that those patches were good, and since Donna Garverick had posted favorable comments on them months earlier I would *guess* that she would have notified HP too. I thought I read somewhere that HP only needed one customer to approve a patch. Does it take more or is some positive customer feedback getting lost somewhere?"
Good question. We also heard HP say they'd be satisfied with one site's beta test report, a comment offered when HP engineers discussed the lack of beta-test sites last summer at HP World. All we can surmise, until we hear from HP, is that there's more work to do on maintaining MPE/iX than there are engineers to do it. At least at HP.
Which gives the argument for releasing the operating system source to a third party a little more ammunition. But nobody's really battling, are they? HP wants its homesteading customers to succeed, right?
June 23, 2005
Jumbo improvements over time
HP 3000 enhancements can travel like distant starlight: They sometimes take years to show up on customer systems. A good example is jumbo datasets for the 3000's database IMAGE (or TurboIMAGE or IMAGE/SQL, depending on how current your own name is for your system's database.) Jumbos, the 3000's best tool for supporting datasets bigger than 4GB, first surfaced out of HP's labs 10 years ago, just when the 3000 NewsWire was emerging, too. We put our news online in the months before we'd committed to print, and our report of September 1 had this to say:
HP will make the enhancement available as part of its patch system, bypassing the delay of waiting for another full release of MPE/iX. But there are already discussions from the HP 3000 community that a more thorough change will be needed before long — because 40-gigabyte datasets someday might not be large enough, either.
Why care about 10-year-old news? In the conservative timeline of 3000 management, jumbos are the distant starlight, only now becoming commonplace on 3000s. Now it looks like jumbos are finally going to get eclipsed by LargeFile datasets. HP's engineers say their alpha testing to fix a critical bug in LFDS is going well. HP expects to update the community next week.
They will need beta testers, something that's been hard to come by for HP in recent months.
Like the jumbos before them, LFDS are also going to get a slow embrace. How slowly did jumbos go into production systems? Five years after jumbos first emerged, John Burke wrote in our net.digest column " it is hard to tell about the penetration of jumbo datasets in the user community beyond users of the Amisys application." His column also offered some tips on using jumbos, even while database experts in the community continued to lobby for a way to build larger files.
Next week could mark the first time in 10 years that 3000 customers can build a dataset as big as they need. Because up to now, LFDS has been unrecommended for 3000 customers except in experimental implementations.
The nature of the 3000 community's starlight, though, makes a 10-year-old enhancement like jumbos current and vital. LFDS might only start to have an impact on sites several years from now, provided the beta testers show up. Otherwise, it's just another entry on HP's Jazz Web page that describes which new patches are available for testing.
LFDS can corrupt data in its latest release. That's unacceptable for 3000 sites. But 3000 customers are a cautious group by nature, so the LFDS bugs haven't caused widespread woe. Our Online Extra e-mail edition offered field experience with the bug, by way of the Adager labs. HP expects to update the community by way of the 3000 newsgroup. Look for the notice in the "Week 5" June postings, if you don't subscribe to the newsgroup. Or check back here, where we'll have the latest news.
June 22, 2005
Direct payoff, direct layoffs
HP has finally realized a solid return from its Compaq merger right here in Texas. This month HP closed on a sale of more than 462 acres of "excess" land in Northwest Houston, a chunk of real estate that was linked to a Compaq facility in that city. According to a story in the Houston Business Journal, the land will become "a new lifestyle center on the former Hewlett-Packard Co. property in far-flung northwest Houston."
Just a week earlier, the fallout of 3,000 HP layoffs trickled through the 3000 community. One engineer who'd been "affected" posted his availability on a technical mailing list. HP said earlier this year that it would be adjusting its headcount in the Enterprise Storage and Systems group during the second and third quarters, a result of intense competition. The vendor has earmarked $236 million for severance pay in the last two quarters, the kind of harsh trimming that CEO Mark Hurd has done before, at his old job at NCR.
Losing a job at HP is far from the rare thing it was 10 or 15 years ago. Back then, the vendor was so circumspect about layoffs that it used alternative words, like being excessed. The headcount for HP's 3000 operations has always been a closely-held figure, but few of us figure it to be in triple digits today. Prior HP layoffs during 2003 and back in 2001 trimmed the 3000 jobs, along with others.
The company now calls the layoffs by their correct name, so investors and financial analysts get the message. Good talent has always flowed out of HP and into the 3000-related third-party companies. Layoffs hasten this outward flow of experience, skills so rare they can qualify as priceless.
As for the land selloff, its net return to HP is still under wraps. HP started on a path of selling its buildings and land several years ago, a strategy that has helped a bottom line under constant pressure in the commodity markets the vendor has embraced. The vendor has sold a total of 632 acres of property in Houston since 2004. The developer plans for 145 acres of park land, as well as an 84-acre lifestyle center including retail, entertainment, dining and recreation facilities. The developer is spending $1 billion to create Vintage Park, to open in 2007, including a 650,000-square-foot lifestyle center on 84 acres on the southeast corner of Louetta Road and State Highway 249.
June 21, 2005
Commerce off 3000s: Off the page
Just about the same time that e-commerce supplier Ecometry rounded up its best customers, a study surfaced that shows their future efforts will be well off the page. Printed pages, that is, according to Transcontinental Publishing. The company commissioned a survey which shows the paper investment won't be increased for firms that drive their sales with 3000-based catalog operations — companies like Old Glory, Coldwater Creek or Levenger that mail tons of paper.
A hundred such companies participated in the spring survey, and almost four of every five said increasing catalog sales was their No. 1 goal. But the survey noted that "only 35% said they would invest in increasing the frequency of mailings and only 26% said they would invest to improve catalog quality."
This would indicate that Ecometry is driving in a direction its customers will follow when it purchases companies like Blue Martini, whose technology has nothing whatsover to do with catalog commerce. Whenever you're not investing in a technology, it's no longer your leading effort. Transactions from phone and paper catalogs are leading at many e-commerce sites, but future growth is in e-commerce, according to the survey.
"Almost as important among top priorities was growing Web site revenue," the survey said, "cited by 73% of those surveyed. Two-thirds (66%) of all respondents indicated they would make a significant investment in Internet and e-commerce applications this year."
At last week's Ecometry conference, keynote analyst Robert Garf of AMR Research spoke to luncheon attendees on one of the hot topics of the conference, Next Generation E-Commerce Platforms and the key to seamless multi-channel execution. It's a safe bet that Garf has been briefed on Ecometry's product lineup.
Our own survey of migrating HP 3000 sites didn't turn up a single one that's making the jump from Ecometry on the 3000 to the HP-UX version of the e-commerce software. (The biggest group was following Amisys onto HP-UX, while the Summit Technologies credit union software held the second position.) Blue Martini's offerings are Unix-based, something that Ecometry CEO John Marrah has said he hopes will generate more Unix business for his solutions.
An article in BtoB magazine mentioned another 3000 e-commerce site, CDW. The company acquired MicroWarehouse during 2003, and its current managers say they'll continue a mix of paper catalogs, Web commerce and keyword search marketing. But here at the NewsWire we've seen a lot less CDW paper in our mailbox than MicroWarehouse ever sent us.
June 20, 2005
Keeping your update skills sharp
A seasoned HP 3000 developer reported success at updating his Series 918 HP 3000 over the weekend. That's a system still in service at hundreds of HP 3000 sites, if not thousands; the 918 was the most affordable HP 3000 ever, at least at HP's new system prices. Keven Miller's 918 needed new Processor Dependent Code to run MAPPER, the utility program the 3000 uses to give you information about your disk drives, memory, processors and co-processors. MAPPER also allows you to modify any information that you need to change.
Miller posted notes on his success in getting his 918 updated, but before we share that user report, let's take a minute to see why it matters. Back in 2003 when HP stopped selling 3000s, our net.digest editor John Burke took note of the shifting landscape and asked, "Can [HP 3000] firmware be updated without resorting to a technician? This could increasingly become a problem as we move into the out years after end-of-sales and people pick up used machines from various sources."
Miller's success echoed John's, an event he wrote up in our October, 2003 edition of net.digest. You can read that report in the archives of the NewsWire's Web site, as well as on John's first-rate resource, www.burke-consulting.com. Now to Miller's more recent PDC report:
Miller, who's been part of the development team for the eXegeSys ERP application during his career, shared these notes with the 3000 newsgroup in an FYI report:
Attempting to run ODE/MAPPER from a 6.0 SLT fails, telling me to update to PDC 1.3. So I followed the instructions for the PF_CWBR0013 firmware patch.
1. I downloaded firmware patch PF_CWBR0013
2. I did a binary FTP to another MPE box as ./pdc13
3. It's a shell script (reading the first of it)
x - CWBR0013.text
x - CWBR0013.frm [compressed]
mv: Cannot reset uid or gid on file "CWBR0013.frm": Invalid argument
ERROR: wc results of CWBR0013.frm are 5107 31365 659456 should be 5107 21403 659456
-rw-r--r-- 1 MGR.KEVENM KEVENM 659456 Jun 18 09:33 CWBR0013.frm
-rw-r--r-- 1 MGR.KEVENM KEVENM 5812 Jun 18 09:33 CWBR0013.text
12814 1288 CWBR0013.frm
/KEVENM/PUB/callci showdev tape
LDEV AVAIL OWNERSHIP VOLID DEN ASSOCIATION
7 AVAIL (W) (Nolabel) 1600
/KEVENM/PUB/dd if=CWBR0013.frm of=/dev/tape bs=2k
322+0 records in
322+0 records out
4. I booted the box from tape as instructed, interactive with IPL
5. I enter ODE
6. I enter UPDATE
7. I enter RUN
Continue(Y/N)? enter Y
8. About 30 seconds later, the run is done.
ODE/MAPPER now runs!
Miller's experience, and John's before his, represent the level of admin skill an HP 3000 owner is going to have to call upon once HP's support leaves the field. If you're uncomfortable with this kind of admin, but need to keep your 3000s in service, there's a good lineup of 3000 service providers who can help you, all in the third-party market.
June 17, 2005
Less tangled SOX for 3000s
Terry Simpkins, the IT manager at Measurement Specialties, used the HP 3000 newsgroup to announce a respite from some of the Sarbanes-Oxley strain. An SEC document at www.sec.gov/info/accountants/ stafficreporting.htm “says the ISIT ‘General Controls’ are not automatically part of section 404 testing. It’s buried in Section F of the [document], but the key phrase is, ‘For purposes of the Section 404 assessment, the staff would not expect testing of general IT controls that do not pertain to financial reporting.’ ”
Simpkins, whose March report to us chronicled 60-hour work weeks overwhelmed with SOX audit issues, added that “If you don’t know about section 404 testing, or are not involved in your company’s SOX testing, go home tonight and be very thankful.”
Simpkins has been sharing what he's learning as he pushes his organizations, which rely on HP 3000s and MANMAN ERP software, through SOX compliance. Auditors have wanted to know how companies handle the segregation of MANMAN programming functions (testing vs. production) to become Sarbanes-Oxley compliant. One- or two-person shops have been struggling to show auditors how this isn't a risk. Management review of high-level system manager capabilities is key, Simpkins says.
"SOX states that you have to be ‘in control’," he said, "and that can be defined lots of ways. What we have done is say that we are aware of the issue, but because of the small size of the staff, having ‘perfect’ segragation of duties just isn’t possible/practical."
"So I created a control that calls for a periodic review by the CFO of exactly who has the ‘sys mgr’ capabilities. I have created a ‘log’ of what users have access to the ‘sys mgr’ logon/capability, and I review this list with [the CFO] quarterly. He signs off on the list each quarter, as a record of the review."
SOX compliance has been slowing HP 3000 shops from migrating. In particular, shops that need to give broad access to a single administrator are struggling to maintain their processes in the face of SOX audits. One site manager said she's lost her AM and OP capabilities from production accounts, "so trying to get onto a restricted box to look at a problem is...um....er...not so nicely achieved. We've tried to explain what damage this can (and will) do," said Carol Darnell, an IT manager at a very large HP 3000 installation, "but compliance appears to be more critical than being able to support our customers."
Foreign companies and those with market caps of less than $75 million recently got an extension of one year to comply. Instead of meeting the requirements by next month, these "non-accelerated" companies now can work until July 15, 2006 — less than six months before HP turns off its 3000 and MPE/iX support business. An article at the IT Compliance Institute explains the extension. The site also has a useful summary white paper of the SOX requirements.
June 16, 2005
Source code makes tomorrow like so yesterday
Sun is putting a little heat on HP this week by offering an open source program for the Solaris operating system. Open source was a rally cry during the early days after HP announced it would stop supporting its proprietary OS for the 3000, MPE/iX. (Anyone who's developed for any vendor's version of Unix will admit that these Unixen are all proprietary, in the same way that Windows is proprietary. Proprietary is not an epithet, such an honest look at software's reach.) You do an open source program to make sure your OS stays relevant and in broad use. Sun's intention is "to release as much of the existing source code as possible through the OpenSolaris project and for future development of the source to take place in the OpenSolaris community."
Although MPE/iX future development will have to take place in the third-party developer community, open source wouldn't work for the 3000 community — something most customers realized when they got honest about the size of the 3000 development base. You can't count customers to measure the potential of open source resources; you have to look for people capable of doing their own builds of software such as perl, sendmail and the like. HP's Mark Bixby has warned 3000 customers who want to homestead they better get fluent in such development, or get to know a consultant who knows his way around the make command.
But the Sun offering this week reminds the 3000 customer about opening up source, a topic HP has promised it finally weigh in on by the end of 2005. HP's been very quiet on whether MPE/iX source can ever be developed outside HP's labs. Will the announcement come at HP World, in about two months, or at the first HP Technical Forum, during September? Or will HP wait until the end of the year to deliver disappointing news, that MPE/iX is not going to gain more functionality for customers who need it?
There are things such 3000 customers need to ensure a long line of tomorrows. IPV6 support for networking adds security in an era when we seem to care about nothing else so passionately. The SQL99 standard could be added to IMAGE/SQL, a standard which "addresses some of the more advanced and previously ignored areas of modern SQL systems," according to the Web resource faqs.org. IMAGE support of SQL99 could add object-relational database concepts, call level interfaces, and integrity management. It would also give the 3000's database a better chance of staying current with Windows, since Microsoft is already moving to support SQL99 in its SQL engines. Birket Foster at MB Foster has talked about SQL99 support for several years now, since the standard is a topic of study at company's database labs (when they maintain the ODBC drivers included in MPE/iX).
So even though parts of MPE/iX are well outside of HP's labs, the whole wooly bunch of source, millions of lines, isn't a candidate for open source like the Sun project. But it might be, someday. So much of the ground is shifting in intellectual property around software. Sun is making its move to protect itself from the rising popularity of Linux. In our latest survey of migration choices, almost as many 3000 sites were migrating to Linux as were moving to Solaris.
June 15, 2005
HP-UX gains in later results
In our June issue, just now hitting the streets, we reported that the migrating HP 3000 customers are choosing Windows as a heavy favorite transition platform. But the percentage of HP-UX sites is creeping upward since our early-June survey. On June 3, these companies didn't make up even 30 percent of the respondents who were moving. A week later, the raw totals stood like this
Windows: 31 customers
HP-UX: 23 customers
Other Unixes, including Linux, Sun & IBM: 15 customers
iSeries choices got mentioned twice, and one HP 3000 company has moved to Apple's Unix, which most of us know as OS X.
These revised percentage totals keep Windows in the lead. But with 71 companies now reporting their migration plans or accomplishments, HP-UX has managed to poke above the 30 percent mark, to just about one-third of the target platform choices.
Six companies are migrating, but unsure of where they'll end up. Another eight companies told us they were not migrating at all, even though our survey questions didn't ask these homesteaders to fill us in. We're glad to hear their stories, too.
You can read the full story, including comments from the migrating sites at the NewsWire's main Web site. Meanwhile, Windows is still being named in 45 percent of the HP 3000 migrating sites, even with these updated figures.
June 14, 2005
A small step back to the old-school HP
The vendor who offers an alternative to your HP 3000 rolled back the clock a little yesterday, though not far enough to recant its flight from the 3000. But HP announced that it's taking those printer and PC units and splitting them apart, a full about-face from the Carly Fiorina strategy in January of "a bigger HP is a better HP." Now that it's got a new CEO, HP is reorganizing, back toward a business plan that recognizes not all products are alike.
HP put the news of the split-up of PCs and printers in the second paragraph of its press release that announced former PalmOne exec Todd Bradley as new head of a separate PC unit. Don't look for a full spinoff of the printer business from the rest of HP soon. You don't appoint a fellow to run a unit just to spin it off. Duane Zitzner's work to ensure a smooth melding of PCs and printers now is just a memory. Mainstream computing press coverage — at the San Jose Mercury News as well as on CNET — has focused on the flip-flop in HP's strategy
The move looks like the first of perhaps several significant rollbacks to a style that created the HP 3000 and its marketplace. Back in those days of the 1970s, every product line from HP was not only its own division, it often operated as if it were its own company. This was the era that created the acronymn "CSY," meaning Computer SYstems Division. The HP 3000 sensibility lives on in the vendor at cubicles and desktops where virtual CSY employees (yeah, vCSY'ers, they call themselves) still spend parts of their day on 3000 engineering and planning.
What splitting printers from PCs will mean to the 3000 customer depends on your current point of view about HP. If it's the company providing a 3000 replacement, you might be glad that PCs and printers seem like different kinds of businesses once again. Part of the problem with the HP's 1990s management of its computer business: everything was supposed to thrive on the laser printer business model. Smaller direct sales channel, less room for different and superior engineering — this is the fallout of chasing the commodity computing model.
On the other hand, if HP is the company that's abandoning your company's bulwark server, then the PC-printer split-up could mean that Dell might have to sharpen its pencil to get your desktop business. These units get separated to give them room to manuever, especially on areas like pricing.
And if HP is the company you're leaving behind while you are forced to drop off your 3000 in a few years — well, another spinoff of its enterprise computing business, the non-Windows servers driven by the likes HP-UX and OpenVMS, could be just around the corner. That might make IBM more competitive in Unix alternatives, or push Sun even further out into discount land.
June 13, 2005
From Netbase to SQL Savvy
After creating and polishing the 3000 shadowing software Netbase, Quest Software has put a lot of its energy into managing SQL-based databases, especially the kind that are being asked to replace the HP 3000's TurboIMAGE.
Now Quest has come out with Toad for Oracle, a development and admin tool to build queries to Oracle databases. It's also got a more technical layer that lets a DBA debug SQL code, or create and modify database objects. A Flash movie (you need to have a Flash player installed in your browser) gives you a tour of Toad.
IMAGE could be complex to program, but the world of Oracle can make the 3000's database programming seem simple by comparison. Oracle is at the heart of solutions such as the Ecometry Web commerce application, so getting fluent with the SQL database might be easier with tools like Toad.
Quest has also done some migration boasting of late, talking about being the company which has helped along more 3000 migrations than any other. John Saylor of the company posted this brag to the 3000 newsgroup:
Who has done over 100+ Migrations off the HPe3000 platform quietly but effectively?Saylor, Director of Specialized Markets, went on to say his company is "the only HPe3000 Software Vendor ranked in the top 100 DM Review companies."
Who has done the final migration transformation with a ZERO impact to the business environment?
No, it is not a Platinum partner.
It is a Platinum tool provider.
It is a long standing HPe3000 Software vendor.
They are business partner with many of the target vendors you are currently looking at for NEW application solutions today.
Quest has its Bridgeware solution to thank for the migration success. You can look over the offering at the company's Bridgeware Web page.
June 08, 2005
A Bright Light Winks Out
Yesterday I learned that Bruce Toback died. He was a leading light among HP 3000 experts, but it takes far more than that accomplishment to catalogue his genius. I got to know him at first when we worked together on a project in the 1980s; I edited The HP Chronicle back then, and he agreed to contribute a column on languages, if I remember correctly. What stands out much better after all these years was Bruce's sense of humor and scope of intelligence. He and his wife Vicki founded a software company, Office Products Technology, first out of the LA area and then from Phoenix, where they relocated to start their family together.
Bruce was about my age when he died, so the news of his death by heart attack was sudden and sad and of course, a little scary. For the last several years we were both members of a virtual community of HP 3000 veterans — so I got to enjoy his writing, thinking and research even more for the past three years than during those few months when I was lucky enough to call him "one of my writers." He wrote more than 800 messages during the three years since I'd joined this community. He posted on a range of subjects as vast as ice skating, digital photography, real estate transactions, Mac OS X programming, percussion instruments and their science — the list of what he was interested in seemed endless.
The tributes poured in about from the HP community during this week. People told stories about his attention to detail (what kind of light bulb contacts are used in the UK, in preparation for a presentation there) or his devotion to accuracy in education (he and Vicki took their kids down the home schooling path, went one story, because the school was teaching electromagnetism in error, and Bruce couldn't get them to correct their cirriculum.) Many of his colleagues said they wished they knew him better. Through the writing he left behind on the Internet (just type "toback" into the address field on the HP 3000 newsgroup search engine), he won't be gone completely.
His programming lies at the heart of Formation, a ROC Software product which Bruce created as a product for Tymlabs, an extraordinary HP software company here in Austin during 1980s and early 90s. He could also demonstrate a sharp wit as well as trenchant insight. From a couple of his messages:
HP engineer [about a Webcast to encourage migration]: During the program, we will discuss the value and benefits of Transitioning from the HP e3000 platform to Microsoft's .NET.After PFC Jessica Lynch became a media celebrity for being rescued during the Iraq invasion, then celebrated in a song:
Bruce: Oh... a very short program, then.
I have to wonder if all this attention would have been lavished on, say, a PFC James Lynch. My guess is that if the rescued POW had not been a comely female of prime reproductive age, we might have learned more about the folks who actually did the rescuing.A fellow of wry humor, Bruce was a realist and optimist all at once. He wrote a fabulous Web-based summary of the 3000 newsgroup traffic for many years during the 90s for the HP user group Interex, entries often full of wit. He kept up; just from reading his more than 800 posts in that community in the years since I joined, I find he was interested in new colorization algorithms, wrote a QCShow player for the Mac, developed a demo server for RETS (an open standard for exchanging real estate transaction) -- and yet he had squirreled away an HP Journal article on HP EGS, a 20-year-old graphics system run on the HP 3000. His last posting to the Internet noted the revival of assembly language programming.
-- Bruce (who's not saying whether he's pro- or anti-war, but who's definitely anti-coverage-of-war-as-sporting-event)
Through it all, Bruce seemed to be having fun. He once noted a study which reported about 10 percent of all tech gifts would be damaged after the year-end holidays by enraged low-tech users, then added, "Go team!" And I could always feel a kindred spirit in his passion for the Mac's rebirth. He was compiling a list of books "at arm's reach" by HP 3000 technical community members in the weeks before his death, a great idea that was as inclusive as it was incisive. Perhaps his lesson as he left us was to keep your mind open about the relative value of past wisdom and future knowledge. He certainly displayed his gifts for both in the HP community.
He leaves behind a wife and two children, the part of his life that I suspect shone the brightest for him. He told this story on himself in a message about his courtship with Vicki:
Well, as long as we’re confessing, I did take my wife Vicki to HP CSY (or whatever it was called in January, 1978) while on our honeymoon. We had a romantic lunch in the company cafeteria, after which we picked up the full HP3000 manual set I had ordered (all 11 volumes). We then set out on a drive through the redwoods in the mountains south of Santa Clara. I drove while Vicki read selected passages from the Instruction Set and Intrinsics manuals.For any of us in the HP 3000 community who knew him, even a little bit, we'll miss Bruce's light, always reflected in his humor.
N.B., for newlywed techies: I have been paying for this ever since.