August 29, 2014
Finding the Labor Your 3000 Site Needs
Homesteading on the HP 3000 — whether it's the bridge until migration, archival operation where little changes except backup tapes, or unlimited future-style — takes labor to maintain. Labor is on our minds here at the NewsWire this weekend, when much of the US has taken a few days off from the office or away from the computer keyboard to celebrate the American labor movement.
We're taking those days off, too. And we'll be back on Sept. 2, like a lot of you with work to do. There's a printed issue for the Fall for me to edit and write for, after all. We're flying in the face of advice that says it's a ticking clock to produce paper based information. We're betting you still count yourself as a pro who knows the movement to digital is not yet complete. When we started the NewsWire, we flew in the face of advice that said, 19 years ago, there was little future for the MPE user.
Your community has been experiencing that much movement, so any tools to track the travels of skilled 3000 pros can be useful. Let me recommend LinkedIn once again. The HP 3000 Community Group at the website -- and LinkedIn has started to specialize in finding people prospects for work -- well, the 3000 group began with a couple of questions that can still kickstart discussions. Again, the LinkedIn advantage is connecting to pros to share with specific work experience details, plus the chance to draw on others' networks through introductions.
Anybody can join for free. Since I launched the HP 3000 group in 2008, we've added 600 members in the group, and there are many others in the LinkedIn network with 3000 experience. Michael Boritz commented on our Group question back at the beginning about who's doing what with the HP 3000 these days.
I’m still working on the 3000. I’ve been working on 3000s since the 1980s, at J.D. Abrams at that time. Since leaving JDA, I worked at Tivoli in Austin (i.e., Unison-Tymlabs) for a couple of years. Since then, I have moved four times — all for new HP 3000 positions.
Pivital Solutions: Your complete
HP e3000 resource
August 28, 2014
TBT: Days of HP's elite software outlook
At the end of August of 1983, Hewlett-Packard mailed out a 92-page brochure that showed HP 3000 owners where to get the software they didn't want to create themselves. The Hewlett-Packard Business Software Guide covered the options for both the HP 3000 and the just-launching HP 250. The latter was a system that would sit on a large desktop, run software written for its BASIC operating system, and receive just six pages of specific notice out of the 90-plus in the HP sales guide.
What's interesting about this document -- apart from the fact that nearly all those photos have people in them -- is that HP's own programming development software and application tools are listed first in these pages. And in that order, too; owners of a system in 1983 seemed more likely to need software to create the bespoke applications so common in a system of 31 years ago. Applications from HP were always pushed before anything without the Hewlett-Packard brand.
But as I paged a bit deeper into this Throwback Thursday treasure, I found the genuine vitality that sold 10,000 of these minicomputers in less than 10 years' time: Third-party software, both in tools and in applications. HP made a distinction in this giveaway document for these programs, which they called HP PLUS software. A product could be Listed, or Referenced. But to get more information on either one of them, HP expected you to purchase a catalog with a lot more detail.
Not only was it an era without a Web, but these were the days when you'd pay for paper just to have a complete list of things you might purchase. The biggest issue was "will this run on my system?" That, and whether it really existed.
August 27, 2014
A Virtual Legacy from the Past to the Future
VMworld 2014 wrapped up this week, with more than 25,000 IT pros and suppliers attending the San Francisco conference. Although the show was wrapped entirely around the VMware offerings -- and few other genuinely available products look to the future as much as the virtual machine vendor's -- there's also a legacy story to be told. As it turned out, that story was a message that virtualized 3000 vendor Stromays got to share.
West Coast sales manager Doug Smith, a 3000 veteran from the enterprise resource planning world, checked in on his way out of the Bay Area to report on the proximity between decades-old MPE/iX and just-days-old VMWare innovations like the enterprise cloud vCloud Air. VMware is offering the first month of vCloud Air free.
"VMWorld is a lot of people looking forward," he said, "and we're pulling people back, out of the past. It was great to see those little guys walking by and knowing what MPE, VMS and Alpha means. People were looking up and saying, 'Oh yeah, I've got one of those HP 3000s in my datacenter.' It was a sight to see."
The CHARON virtualization engine that turns an Intel server into a 3000 runs on the bare metal of an Intel i5 processor or faster, operating inside a Linux cradle. But plenty of customers who use CHARON host the software in a virtualized Linux environment -- one where VMware provides the hosting for Linux, which then carries CHARON and its power to transform Intel chips, bus and storage into PA-RISC boxes. VMware is commonplace among HP 3000 sites, so management is no extra work. But ample server horsepower is a recommended spec for using a VMware-CHARON combo.
August 26, 2014
See how perl's strings still swing for MPE
The HP 3000 has a healthy range of open source tools in its ecosystem. One of the best ways to begin looking at open source software opportunity is to visit the MPE Open Source website operated by Applied Technologies. If you're keeping a 3000 in vital service during the post-HP era, you might find perl a useful tool for interfacing with data via web access.
The 3000 community has chronicled and documented the use of this programming language, with the advice coming from some of the best pedigreed sources. Allegro Consultants has a tar-ball of the compiler, available as a 38MB download from Allegro's website. (You'll find many other useful papers and tools at that Allegro Papers and Books webpage, too.)
Bob Green of Robelle wrote a great primer on the use of perl in the MPE/iX environment. We were fortunate to be the first to publish Bob's paper, run in the 3000 NewsWire when the Robelle Tech long-running column made a hit on our paper pages.
You could grab a little love for your 3000, too. Cast a string of perls starting with the downloads and advice. One of HP's best and brightest -- well, a former HP wizard -- has a detailed slide set on perl, too.
August 25, 2014
Shopping While Lines are Dropping
HP's third quarter financial report showed that a company making adequate profits can also be making products that are not popular any more. The time comes to every product line, but the Hewlett-Packard of 2014 has made steady progress toward commodity-style enterprise computing. The pull into Windows has become a vortex -- and in a bit of irony, Windows' age helped HP's sales this quarter.
The overall numbers were impressive to the markets. Investors lifted the price of HP's stock more than $2 a share, after the briefing, sending it closer to $40 than it's been in years. Meanwhile, the continued downturn of Business Critical Systems scarcely earned a minute's mention. It's off 18 percent from the same 2013 quarter. But it gets less than a minute because BCS products like the HP Unix line, and VMS computing systems -- even the steady but meager business of NonStop -- only comprise 3 percent of the company's enterprise sales. In the circle above, BCS is the rounding error, the most slender slice. Click it to see a bigger picture of that smallest piece.
And Enterprise represents just one dollar out of every four that HP earns in sales. This is activity in the Industry Standard Systems. These are the ProLiant servers driving Windows and Linux, business that grew 9 percent. Specialized operating environments like HP-UX just aren't producing new business, and they're losing old customers. If you look over the last three years of Q3 numbers, each and every one shows a double-digit BCS decline. There's only so much clock time on that product wall before irrelevancy pushes a community off HP's futures map. It happened to the HP 3000, but MPE never ruled over HP business computing like Unix once did.
"When I look at the way the business is performing, the pipeline of innovation and the daily feedback that I receive from our customers and partners, my confidence in the turnaround grows stronger." -- Meg Whitman, CEO
So when HP's business in your installed platform shows poor numbers, what do you do? The rest of the company's report looked tame, although you'd wonder why anyone could be sanguine about the future of the company. Printing, Services, Software and Financial Services all dropped their sales top lines. The Enterprise Group grew its business 2 percent overall on a $27.5 billion HP sales quarter. This was accomplished by $57 million of expense cuts.
Only PC sales grew along with enterprise business. How can a company reporting a 27 percent drop in profits, one that missed its forecast by more than 10 percent, be rewarded on the trading floor? Jim Cramer of MSNBC said there's just enough to like about HP now. That might be due to the history the company has turned back. Everybody on the trading floor remembers HPQ at $12 a share with a fired CEO having followed an ousted CEO. Historic lows are a faded memory now, although the company's gotten no bigger over that stretch of clock time. The good feelings come from a turnaround tale that's still in the middle of its story.
August 22, 2014
30 years ago, 1984 seemed like news
I've been writing about my own experiences of the year 1984, since this has been the week that marks my 30th anniversary of my technical journalism career. It was the era of personal 1200 baud modems manufactured by US Robotics, now owned by PowerHouse's parent company Unicom Global. It was a time when HP's PC, the Touchscreen 150, operated using a variant of CPM -- the alternative to MS-DOS that lost like Betamax lost to VHS. It was a year when HP's worldwide software engineering manager Marc Hoff announced that 1,783 new products would enter HP's price list on April 1, products ranging from less-expensive software to "application-experienced CEs" called CSRs.
HP's new PICS phone support centers in California and Georgia each operated from 8 AM to 6 PM, giving the customers a whole 13 hours a day of call-in "toll-free" support in the US. It was an era when toll-free mattered, too, and to save money in your DP shop (we didn't call it IT) you could read a column on how to make your own RS-232 cables for the HP 3000, based on instructions from the Black Box Catalog. The HP 3000 could output graphics to magnetic tape, files that could be passed to a service bureau to create 35mm slides for your Kodak Carousel projector for those important boardroom meetings. But there are stories that 3000 community members have shared about that year, too. Here's a sample of some.
Alan Yeo, ScreenJet founder - In 1984 I had just gone freelance for a contract paying “Great Money” and spent the whole year on a Huge Transact Project. Actually it was the rescue of a Huge Transact Project, one that had taken two elapsed and probably 25 man-years and at that point was about 10 percent working. A couple of us were brought in on contract to turn it around. We did, and we used to joke that we were like a couple of Samurai Coders brought in to Slash and Burn all before us. (I think Richard Chamberlin may have just starred in the hit TV epic Samurai at that time.)
We were working on a Series 70, configured as the biggest 3000 in our region of the UK (apart from the one at HP itself). We used to have lots of HP SEs in and out to visit -- not because it was broken but just to show it to other customers. That was the year we started hearing rumors of PA-RISC and the new “Spectrum” HP 3000s. It unfortunately took a few more years for them to hit the streets.
I have lots of good memories of HP SEs from that time. HP employed some of the best people, and a lot of them were a great mix between Hardware Engineers, Software Engineers and Application Engineers. Great people to work with who sort of espoused the HP Way, and really made you want to be associated with HP. Where did they go wrong?
Brian Edminster, Applied Technologies founder -- As you've said, bespoke software was the meat and potatoes of the early 3000 market. I still believe that a custom software application package can be warranted -- as long as it gives your business a competitive edge. The trick is to make sure the edge is large enough to justify the expense of having something that's not Commercial Off the Shelf.
August 21, 2014
TBT 1984: The Days of Beauty and Wonder
When I arrived in the HP 3000 world, three decades ago this week, spreading the word about DP was supposed to be an attractive effort. We brought the workmanlike, newsprint-with-staples Chronicle into a marketplace where the leader was a slick-papered, four-color magazine bound like a book and produced as if it were a high-end design assignment.
In a Throwback Thursday covering the week my career started, the covers of Interact look like concept art. Much of what was inside was black and white with line drawings at best. But the outsides and even the big ads on the inside told the story of presentation in '84 style: focus on the beauty of the concept, and tout the details of the wonders of features. And some advertisers reached for the same level of art in their messages. Adager's ads often ran with little except a picture of the tape that carried the software, set in a mountain landscape or like the above, converted to a globe.
How else but with high concept could you make a full page of copy about a terminal that only worked with HP 3000s? There was a story in the HP ad, well-written, but like almost every other page of the user group's magazine, it was bereft of images of people.
The DP workers in these ads look flummoxed and beaten much of the time, because they don't have the invention of the year that will making using their 3000 the value it was promised to be. Some of the magic of the day included HP's Dictionary/3000, designed to eliminate the tedious writing of COBOL Identification Divisions. A cartoon depicts those who still perform this task as cave dwellers. Meanwhile, the wonders of fourth generation languages were touted as if these would soon become as universal as anything such as COBOL. Technically that would have made things like these 4GLs third generation languages. One of the things that made COBOL universal was that everybody knew it and you could find it running anywhere.
August 20, 2014
Small office — but a modest, social market
The building in Austin, Texas wasn't even devoted to the newspaper entirely. Off in the northern side, the single-story offices housed a insurance company and an optician. The beginnings of the HP Chronicle matched the position of the HP 3000 in 1984. It was not the most significant tenant in the Hewlett-Packard building of products. It was never the biggest earner on the HP ledger. It was just the most social office of the HP structure. People built events and associations around it.
HP closed out its fiscal 1984 a couple months after I arrived in the offices of the Chronicle. We were so cautious that we didn't even include "HP" in the publication name at first, because we were not welcomed at that year's Interex user group conference. I heard about the argument on the show floor, where it was plain we'd started a publication to compete with the user group. They'd cashed the check, said the publisher John Wilson. They had to let us in. But seeing that resistance, nobody was going to make us change our name in that kind of environment. Leave the HP off the front page.
It never occured to us to make a big story out of the annual HP numbers which were reported in mid-November. HP wasn't a sexy stock (trading in the mid $40s, with good profits) and its board of directors was full of technical expertise and HP management experience. John Young, the company's CEO on the August day I began, was not the chairman. That job was in the hands of one of the company founders, David Packard. His partner Bill Hewlett was vice-chairman. HP management moves didn't involve mergers or acquisitions as the splashy plays of today. The photo of the HP Touchscreen connected to a 3000 at left was one of just four in the annual report with a person in it. This was still a company that knew how to connect with customers, but struggled to sell its story about people.
There was a full range of things which the 1984 Hewlett-Packard was not. One of them was an adept player at being in a partnership. The Not Invented Here syndrome was in full throat on the day I arrived and looked at the PC 2622 box atop that PC monitor. Walker, Richer & Quinn was selling an alternative to HP's hardware. Within a few years HP would be launching a product to compete with WRQ, Advancelink. Because HP believed that every dollar, from supplies to support, had its best chance to help the company if it were on the HP ledger.
Computer-related sales made up the biggest share of the $6.1 billion that HP posted 30 years ago, but test and measurement systems were not far behind. $3.2 billion for computers, $2.2 billion for test gear. The latter was the best-known product for the company, as the Silicon Valley's hardware engineers were likely to have HP measurement products in their development labs. Test and Measurement was also more profitable than computers. Used in hospitals, medical labs, research facilities -- this was the business that started the company, and it was still the major driver in profitability, with strong sales.
Test and measurement was also completely outside my beat, thank goodness. But that didn't mean I only had the HP 3000 to learn. The Chronicle covered HP 1000 real-time systems and HP 9000 engineering computers, but mostly because our California competitors at Interex did so. The serious ad revenue came from the most social side of HP's $3.2 billion: business computers, charting the lives of companies and their employees. But even a chart off an HP business computer had a radical distinction from today. It used six pens to make its appearance.
August 19, 2014
What Changed Over 30 Years: Bespoke
I arrived here in the community of my career when gas was $1.15 a gallon in the US, the Dow was at 1,200, a new truck sold for $8,995, the Cold War Olympics featured no Soviet atheletes in LA, and Stevie Wonder had a top hit on the record charts. Because there were still records being sold for pop hits, along with cassettes. Nary a CD could be bought. The Mac was brand new and still didn't sport a hard drive. Those fellows to the right were right in style with warm-up suits that you're likely to see in a senior's happy hour cafeteria line today.
There were thousands of applications in the Hewlett-Packard software catalog of 1984. It wasn't a new idea to collate and curate them, either. MB Foster had one of the first compendiums of HP 3000 software, several years before it occured to HP to offer products the vendor did not make (or buy up, then sell back). But in the month when I entered this market, during that August you were at least as likely to find custom, bespoke software running a corporation as any Commercial Off The Shelf package.
People built what they needed. The bespoken software was often created with the help of fourth generation langauges, so Speedware and Cognos' Powerhouse were big players during 1984. Not the biggest of the 3000 vendors, in terms of customer size. Unless you counted several thousand MANMAN sites, all running the Quiz reporting tools that ASK Computer included with the MRP package. Back in those says, Enterprise Resource Planning hadn't been conceived.
Because so much of the community's software was customized, being well-versed in IMAGE/3000 -- not yet TurboIMAGE, let alone IMAGE/SQL -- was a key skill. Mastery of the database was more attainable if you had a database management utility. Adager was most widely installed, with Bradmark just getting off the ground in 1984. I nearly crashed my reputation with Adager and co-founder Alfredo Rego, less than a month after I began my career in the community.
The problem was a lack of MPE and IMAGE experience. Since I didn't understand the technology first-hand, I felt compelled to contribute to the effort of the HP Chronicle. Not by writing an article, but instead closely red-pen editing the writing of Rego. I didn't know yet that anything he shared with a publication -- his technical treatise was a big win for us at the HP Chronicle -- had already been polished and optimized. A writer well-steeped in mastery of his subject can insist an article be published with no changes. In the publishing business, stet means to ignore a change. I'd have been helped if someone had grabbed my inked-up printout of Rego's paper and marked "stet all changes" on the front. He had a legitimate beef.
Instead, we ran it and then I got to enjoy a rare thrill -- having my corrections corrected by the author, live in front of a local user group audience. Writers forming the troika of big independent vendors -- Bob Green at Robelle, Eugene Volokh at VEsoft, and Rego -- certainly had earned stet-all-changes. Their software became crucial in managing a 3000 that was gasping for new horsepower. Creating and maintaining customized software was a popular way to get the most out of the six-figure HP 3000s, already at the end of the line at the top but still more than two years away from getting a refresh.
August 18, 2014
This Is Where I Came In
It's the third week of August, but it's 30 years ago. I wear my wide tie and my oxfords to an office in Austin's northwest tech territory and start to write and learn about the HP 3000. I'm 27, father of a boy not yet two, a community news reporter with a new community to creep into -- because that's how it's done when you don't know anyone or much of anything. You ask a lot of questions and try to understand the answers.
The office is ribbed with wood paneling and mini-blinds and sports an IBM-PC knockoff, a Columbia. It's got an amber display and no hard drive. A box with the manual for Walker, Richer & Quinn's PC2622 software is on top of that monitor. It's connected for something called time-sharing, and it also connects to something called Compuserve. I watch my boss dial up on a phone with a modem -- I knew about those from using an Apple II at home -- and read the news. None of it's about HP, though. That's our story to tell.
Inside my editor's office there's a telephone transcription machine for recorded interviews, plus a Kaypro II portable. It weighs 28 pounds and has a screen that's nine inches across. Imagine two Samsung Galaxy phones side by side, and that's about it. There are two books on the shelf, both printed by Hewlett-Packard. One is a catalog of third-party software and specialized hardware, all written in something called MPE V for a computer people are wild about, the HP 3000. The other book is a listing of the phone number of everyone in HP's Bay Area campuses. HP is not yet selling $7 billion of gear, support or software in 1984 -- and that includes medical and measurement systems that are so much better known than its computer products.
In my first week of a career writing about HP, one of the first things that I learn is that we've been scooped. The latest HP 3000, a real ground-breaker, is already in the pages of Interact magazine. The user group Interex has won again, because being physically near those HP Bay Area offices makes a difference. There's nobody on our staff or theirs who wrote news for newspapers, though, not until this week. It's the only chance we've got to learn something first: Get on that phone, son.
Read "This Is Where I Came In" in full
August 15, 2014
The 3000's got network printing, so use it
Ten years ago this summer, HP's 3000 lab engineers were told that 3000 users wanted networked printing. By 2005 it was ready for beta testing. This was one of the last enhancements demanded as Number 1 by a wide swath of the 3000 community, and then delivered by HP. The venerable Systems Improvement Ballot of 2004 ranked networked printing No. 1 among users' needs.
MPEMXU1A is the patch that enables networked printing, pushed into General Release in Fall, 2005. In releasing this patch's functionality, HP gave the community a rather generic, OS-level substitute for much better third party software from RAC Consulting (ESPUL). It might have been the last time that an independent software tool got nudged by HP development.
The HP 3000 has the ability to send jobs to non-HP printers over a standard network as a result of the enhancement. The RAC third party package ties printers to 3000 with fewer blind spots than the MPEMXU1A patch. HP's offering won't let Windows-hosted printers participate in the 3000 network printing enhancement. There's a Windows-only, server-based net printing driver by now, of course, downloadable from the Web. The HP Universal Print Driver Series for Windows embraces Windows Server 2012, 2008, and 2003.
Networked printing for MPE/iX had the last classic lifespan that we can recall for a 3000 enhancement. The engineering was ready to test less than a year after the request. This software moved out of beta test by November, a relatively brief five-month jaunt to general release. If you're homesteading on 3000s, and you don't need PCL sequences at the beginning and end of a spool file, you should use it. Commemorate the era when the system's creator was at least building best-effort improvements.
August 14, 2014
TBT: Affordable IT in Acquisition Aftermath
There it is, in all of its comfy, trustworthy glory: The only two-page spread advertisement HP ever bought to promote the HP 3000. From a 1998 issue of Computerworld, it's a ThrowBack Thursday entry, from an era when the 3000 was battling for prime position in datacenters. (Click it to have a closer look.) Harry Sterling was the general manager of the 3000 group by that year. Serious business.
As part of another ad series, Terry Simpkins, now the Business Systems Director of Measurement Specialties Inc., testified to the value of running HP 3000 ERP systems. At the time MANMAN was owned by Computer Associates, who'd dubbed the software's owner the MK Group. (Click to have a closer look at his testimony.)
Now comes word that Simpkins' current company -- probably one of the single largest users of MANMAN -- has been purchased. An acquisition can be a trigger for change. Some HP 3000s have been decommissioned as a result of running a company which now must march in a new corporate file.
It may not be so at MSI. We've heard through the MANMAN support network that TE Connectivity Ltd., which will own MSI perhaps as early as next month, was impressed by the low costs of operating more than 10 separate ERP installations around the world. MSI was purchased for $1.4 billion, according to a report in the Wall Street Journal.
There have been some instances in the system's past where the HP 3000 edged out other mid-size enterprise platforms during a merger. AS/400s got replaced in one case. At MSI, the system is running manufacturing for a company that is moving into stronger business.
August 13, 2014
When a taxing situation might shuffle plans
Out in the 3000 community some select customers are seeing subpoenas. According to a source familiar with the matter, a vendor's been having some issues with the Internal Revenue Service, and the US Government is intent on gathering what it believes it's owed.
Tax matters go to subpoena when information is being demanded in a case against a corporation or an individual. We're still seeking confirmation of the information about which vendor's name is now out among its customers, attached to a subpoena. [Update: And we have gotten it, plus a copy of the vendor's response. It's a long-term battle with the IRS, the vendor says. We've found documents going back more than 15 years. They claim that the fight is personal, not related to their company. Nonetheless, the vendor's customers got subpoenas.]
It illustrates the unpredictable nature of doing long-term business in the IT industry. HP 3000 users often do long-term business. They have a reputation for sticking to suppliers, especially in these days when companies are shifting focus away from MPE. When you get a tool that works, and a company that pledges to support it, you stick with it while you stay with the 3000.
"What do I do if they go out of business?" one of the customers has asked. The answer is simple enough: the products will go onto the open market to be purchased as assets. Software with customers who pay support fees, well, that's likely to be bought up sooner than later. An IT manager will have to manage new product ownership -- and perhaps new strategy and roadmaps for the product.
But just because there's change at the top of a product's ownership doesn't mean all else changes. It's pretty easy for a company to acquire a product and change little. Especially if the customer base is providing a profit to the vendor at the same time that the software continues to earn support contract renewals.
August 12, 2014
Where a Roadmap Can Lead You
In preparation for its upcoming VMS Boot Camp, Hewlett-Packard has removed some elements of its roadmap for the operating environment. What's disappeared are no small thing: dates.
HP 3000 customers saw their roadmap get less certain about its destination. At the end of the vendor's interest in selling and creating more systems, an elaborate PowerPoint slide showing multiple levels of servers. The roadmap actually got a cloud creeping in from the right hand margin.
Okay, that was 13 years ago this very month in Chicago. But it was not the last HP World conference -- that would be one decade ago, this month -- not any more than next month's Boot Camp for VMS enthusiasts and customers will be the last. But there have been times when VMS had promises from HP's management of another decade of service. Here's the before, and the after.
Very few products last for lifetimes. Knowing when they're going, and how soon to make plans for replacement, is serious business for an IT manager.
During an August in 2001 when the future looked certain and solid for some customers, a PowerPoint slide told more than could be easily read in Chicago for HP 3000 customers. For the record, the slide below delivered everything promised up until 2003. The PA-8800 never made an entry into the N-Class.
That would be known, in the roadmap parlance, as a PA-8xxx. The PA-8yyy (8900) never made it into a 3000, either.
Roadmaps might be an old tradition, but they're moments to establish and renew trust in a partner. Specific, and follow-through, make that possible. Some VMS customers are already underway with their migration assessments.
August 11, 2014
Classic lines push homestead tech designs
Sometime this week I expect to be updated on the latest restructure at Stromasys. That's the company that has created a 3000 hardware-virtualization product installed in more sites than we first thought. They hold their cards close to the vest at Stromasys, especially about new installs. But we keep running into MPE support vendors who mention they have emulator-using clients. These companies are reticent about reporting on emulation.
3000 people have dreamed about emulators ever since 2002. And for the next eight years, people figured emulation wouldn’t matter by the time HP approved MPE emulator licensing. Better not tell that to the customers who have plans to go deep into the second decade of the 21st century with their 3000. Emulation was rolling by 2012 for the 3000. Within a couple of years between now and 2023, that technology could be well polished for MPE. Enough to stop using HP's 3000 hardware, boxes that will be at least 20 years old by that time. Most of them are at least 15 years old right now.
A great deal of time has passed since the 9x9 3000s had their coming-out, but much has changed that we couldn't predict back then. Come with me to the magical year of 1997. We had little idea what we'd see in just 10 years' time.
It’s 1997. (Humor me a minute, and turn back the year.) You're here? Okay, think about what we don’t have yet. Google. BluRay. DVDs, for that matter. Hybrid cars. Portable MP3 players of any kind. PayPal. Amazon turning a profit. YouTube. eBay was so new it was called AuctionWeb. Thumb drives. Digital TV. Viagra. Caller ID. Smartphones, warmed baby wipes, online banking, Facebook and Twitter. Blade servers, cloud computing, Linux, virtualization — the list of technologies and designs we didn’t have 17 years ago is vast.
We don’t even have to talk about clouds, tablet computers or 3D TVs. Now, roll ahead to 2023. In that year, there will still an HP 3000 running a factory in Oklahoma. That’s the plan for Ametek’s Chandler Engineering unit. By that year MPE will be 50 years old, COBOL more than 75. And what will keep those two technologies viable? Well, probably technology that we don’t even have out of design now, nine years ahead of that shutdown date. People have been throwing rocks at old stuff for years, but it hangs on if it’s built well.
August 08, 2014
Classic Advice: Adding a DLT to an HP 3000
I'm trying to add a DLT to a my HP 3000 939KS and it keeps reporting media as bad. I can FCOPY but not run an Orbit or MPE store. It does mount the tape normally. The MPE store gives the following error:
STORE ENCOUNTERED MEDIA WRITE ERROR ON LDEV 9 (S/R 1454)
SPECIFICALLY, STORE RECEIVED ERROR -48 FROM THE IO SYSTEM (S/R 1557).
The server which this drive is being added to has DDS-3s on it, but we are adding another disk array, so we are going to outgrow what we have very quickly.
DLT8000s have not been manufactured in perhaps 10 years. Even five-year-old drives are SDLTII or DLT VS160, or some form of LTO. Also, using HVD-SCSI is so last century. At any rate, the heads on the DLT drives do get used up depending on the media used. Try another DLT drive, if possible.
Unfortunately, this is the exact issue facing homesteaders and others who are delaying their migration off the HP 3000, especially if they have pre-PCI machines like the 939. The hardware to run with it can be difficult to find, but it's out there, although it can be of varying level of readiness. You have many options open to you, but as time goes by they will more difficult to implement.
August 07, 2014
Who's got our history, and our future?
Migration takes on many problems and tries to solve them. A vendor stops supporting the server. Investing in a vendor's current product by migrating makes that go away. Applications slide into disrepair, and nobody knows how to re-develop them. Ah, that's a different sort of problem, one that demands a change in people, rather than products.
Yesterday we heard a story of a company in Ohio, running a 3000, whose IT manager planned to retire rather than migrate. Telling top management about your retirement plans is not mandatory. Frankly, having an option to retire is a special situation in our modern era. Figuring that you could be replaced, along with all of your in-company experience and know-how about things like COBOL, is far from certain. Legacy systems still run much of the world, but the people who built and tend to them are growing older, out of the workforce.
It's a glorious thing, knowing that your server's environment was first crafted four decades ago. Some of the brightest players from that era are still around, though not much active. Fred White built IMAGE, alongside Jon Bale at HP. Neither are at work today. Fred's now 90, as of April.
In another example of a seasoned 3000 expert, Ken Nutsford's LinkedIn account reports that he celebrates 45 years at Computometric Systems, the development company he founded with his wife Jeanette. In a Throwback Thursday entry, here they are, 10 years ago and now, still together. Not all of us wear so well, but they've retired enough to have travelled the world over, several times, on cruise ships. That's what more than 40 years will earn you.
It's been a decade since there's been a HP World conference like the one pictured at left, hosted by the Nutsfords, complete with a hospitality buffet as well as a board of trivia (below, click for detail) technical details that just a tiny set of experts might know. The number of people who know the operating system and the hardware at hand at that level has been on the decline. Not just in the MPE world, but throughout the computer industry.
BusinessWeek recently ran an article titled, "Who'll keep your 50 year old software running?" Even though the Nutsfords retired from leading SIGCOBOL in 2004, there's plenty of COBOL around. But not anywhere near enough people to maintain it, although companies continue to try.
The baby boomers that brought us the computer revolution, developing the products and programs we now rely on, are retiring. But many companies are still using programs written in such software languages as COBOL and Fortran that were considered “cutting edge” 50 years ago. Indeed, the trade publication Computerworld has reported that more than half of the companies they surveyed are still developing new COBOL programs
"Staffing is the first thing to go these days," said Birket Foster in a Webinar briefing this week. His MB Foster company is still doing migrations, including moving a Unix customer off the Progress database and onto SQL Server. Progress is a youngster compared to COBOL and IMAGE. Some people decide to migrate because of the migration of their most expert people.
August 06, 2014
Password advice for migrating managers
More than a billion password-ID combos were stolen by a Russian gang, according to a report from a cybersecurity company. Mission-critical, revenue-centric passwords are probably the ripest targets.
Once you're making a migration of mission-critical systems from MPE to more-exposed servers, passwords will become a more intense study for you. Windows-based servers are the most exposed targets, so a migrated manager needs to know how to create high-caliber passwords and protect them. Given the headlines in current news, today's probably the day when you'll get more questions about how safe your systems are -- especially in the coming era of cloud computing. Here's some answers from our security expert Steve Hardwick.
By Steve Hardwick, CISSP
Everything needs a password to access it. One of the side effects of the cloud is the need to be able to separate information from the various users that access a centrally located service. In the case where I have data on my laptop or desktop, I can create one single password that controls access to all of the apps that reside on the drive, plus all of the associated data. There is a one to one physical relationship between the owner and the physical machine that hosts the information. This allows a simpler mechanism to validate the user.
In the cloud world it is not as easy. There is no longer a physical relationship with the user. In fact, a user may be accessing several different physical locations when running applications or accessing information. This has lead to a dramatic increase in the number of passwords and authentication methods that are in use.
I just did a count of my usernames and passwords and I have 37 different accounts (most with unique usernames and password). Plus, there are several sites where I use the same usernames and password combinations. You may ask why are some unique and why are some shared. The answer is based on the risk of a username or password be compromised. If I consider an account to have a high value, high degree of loss/impact if hacked, then it gets a unique username or password. Let's look at email accounts as a good example.
August 05, 2014
Boot Camper laying down migration steps
More than a decade after HP began its migration away from MPE and HP 3000, there's another underway among the vendor's enterprise systems. OpenVMS customers are starting to look into what's needed to make a transition off the Digital servers. HP's announced that it will curtail the use of the newest VMS to the very latest generation of hardware. Thousands of servers are going to be stuck on an older OpenVMS.
That will be one element to spark the offers at next month's VMS Boot Camp in Bedford, Mass. We heard from a veteran HP 3000 and MPE developer, Denys Beauchemin, that his company is headed to the Boot Camp for the first time this year. There's engagements and consulting to be made in moving HP enterprise users to less HP-specific environments.
"We migrate them from VMS to Linux or other platforms," said Beauchemin, who was the last working chairman at the Interex user group before the organization went dark in 2005. "Another HP operating system comes to an end."
Boot Camp is a VMS tradition among HP's most-loyal general purpose computing community. (You can't call the 3000 community HP's any longer, now that the vendor is coming up on seven years without a working lab.) Boot Camps in the past were annual meetings to advance the science and solutions around VMS. But in more recent times they haven't been annual. Now there's migration advice on hand for the attendees. Some may view it with disdain, but when a vendor sends up signals of the end of its interest, some kinds of companies make plans right away to migrate.
August 04, 2014
Webinar advice outlines migrating in-house
The biggest share of HP 3000 applications have been written by the owners of the systems. Custom code either began out of raw materials and the needs of a company's business processes -- or they were customized from third-party applications. In the most dynamic part of the 3000's history, companies bought source code from vendors along with the software products.
That's why this Wednesday's Webinar from MB Foster will strike so close to the hearts of MPE users. Migrating Custom In-House Developed HP 3000 Applications begins at 2 PM Eastern, 11 AM Pacific. Birket Foster leads a 45-minute talk and answers questions about risk, mitigating challenges, and how to get started. Regardless of how much life a 3000 has left in any company, the transition process revolves around the applications. Moving one can teach you so much about what might be next.
"It may seem frightening to migrate, but when properly planned, 'risks' are mitigated," says the introduction to the webinar. You can register right up to the starting time by following the links at the MB Foster website.
August 01, 2014
HP doubles down on x86 Intel, not HP-UX
IBM's giving up on another market that HP continues to prize, but the latest one is more relevant to the small-sized enterprise where HP 3000 migrators hail from. (Years back, IBM sold its consumer PC business to Lenovo.) Now the modest-horsepower x86 server field's going to Lenovo, since IBM's decided to exit another Intel-based hardware market.
A longtime HP 3000 software vendor took note of this transition. He wondered aloud if the message HP now sends to its x86 prospects has a shadowy echo of another advisory, one delivered a decade ago. From our correspondent Martin Gorfinkel:
Hewlett-Packard has been running full page ads in the New York Times with the lead, “Building a cloud? Your future is uncertain.” (The “un” in “uncertain” is crossed out.) The ad goes on to say that the "IBM decision to exit the x86 server market impacts your cloud strategy." Thus, they say, move to HP and be assured that HP will not leave you stranded.
Would I be the only former user/vendor in the HP 3000 market to find that advertising hypocritical -- and further evidence that the company we once relied on no longer exists?
The hypocrisy is probably on display for any 3000 customer who was told Hewlett-Packard was making an exit from the 3000 hardware market (and by extension, the MPE software world). Every vendor exits some part of their business, once the vendor gets large enough to sell a wide array of products. IBM is dropping away from x86. HP invites enterprises to "join us to plan your forward strategy." This forwarding strategy of moving to Windows and Linux differs from HP advice of 10 years ago. Going to HP-UX was the strategy du jour, beyond a 3000 exit in 2004.
The full-page ads in four colors in a national daily announce a redoubling of effort to win Intel x86 business. That's going to suck up some energy and mindshare, effort that 3000 customers who followed HP forward on HP-UX are probably going to miss.
July 31, 2014
TBT: Java's promise spun 3000s into style
Just about 15 years ago from this ThrowBack Thursday, the HP 3000 was having its high moment of renaissance at Hewlett-Packard. The computer was going to make its stretch into the world of a Java-based interface for applications, in an era when Java was considered stylish. A new Java library was going to be patched into the operating environment, and the 3000 division was about to enjoy its fourth straight summertime with the same general manager, something we'd not seen in many years.
Harry Sterling pushed at the heartstrings of the customers during his tenure leading the division, and in 1999 he threw out the stops to make the HP World conference update on the 3000 memorable. The 3000 was always in style, Sterling maintained, just like the classics of yo-yos (a popular late '90s show giveaway) and tuxedos. Sterling managed to pull off a combination of the two at what amounted to a State of the Product address.
His hour-long talk was built around the theme of "The HP 3000: Always in Style," and featured a video of customer interviews comparing the system to classic dances such as the tango and the waltz. The general manager finished his talk spinning a yo-yo from his hand.
“Just like this yo-yo and just like my tux are always in style, so is the 3000,” Sterling said. The white-hot dot com boom was on, and Sterling felt the yearning from customers to feel the heat.
"You are seeing a new mindset at HP, doing the things that will make it possible for us all to be a pivotal player in Chapter Two of the Internet. Many of you are saying it’s about time — and I agree.”
July 30, 2014
Find :HELP for what you don't know exists
Last week we presented a reprise of advice about using the VSTORE command while making backups. It's good practice; you can read about the details of why and a little bit of how-to in articles here, and also here.
But since VSTORE is an MPE command, our article elicited a friendly call from Vesoft's Vladimir Volokh. He was able to make me see that a great deal of what drives MPE/iX and MPE's powers can remain hidden -- the attribute we ascribed to VSTORE. "Hidden, to some managers running HP 3000s, is the VSTORE command of MPE/iX to employ in system backup verification." We even have a category here on the blog called Hidden Value. It's been one of our features since our first issue, almost 19 years ago.
Finding help for commands is a straightforward search, if those commands are related to the commands you know. But how deep are the relationships that are charted by the MPE help system? To put it another way, it's not easy to go looking for something that you don't know is there. Take VSTORE, for example. HP's HELP files include a VSTORE command entry. But you'll only find that command if you know it's there in the operating environment. The "related commands" part of the entry of STORE, identifying the existence of VSTORE, is at the very bottom of the file.
Vladimir said, "Yes, at the bottom. And nobody reads to the bottom." He's also of the belief that fewer people than ever are reading anything today. I agree, but I'd add we're failing in our habits to read in the long form, all the way beyond a few paragraphs. The Millennial Generation even has an acronymn for this poor habit: TLDR, for Too Long, Didn't Read. It's a byproduct of life in the Web era.
But finding help on VSTORE is also a matter of a search across the Web, where you'll find archived manuals on the 5.0 MPE/iX where it was last documented. There's where the Web connects us better than ever. What's more, the power of the Internet now gives us the means to ask Vladimir about MPE's commands and the MPEX improvements. Vladimir reads and uses email from his personal email address. It's not a new outlet, but it's a place to ask for help that you don't know exists. That's because like his product MPEX, Vladimir's help can be conceptual.
July 29, 2014
Stromasys spreads word of spreading wings
The makers of the only HP 3000 hardware emulator are not a new company, but Stromasys is starting to outline the new structure of its firm in a communication to its clients and partners. Last week the corporation emailed notice of a set of managers to "strengthen its management team" and a announce the creation of a new R&D center.
In May the company's main HQ was moved to a larger facility in Geneva, and an Asia-Pacific unit will be located in Hong Kong. Some of the changes to the company were reported in brief at the end of 2013. But Chairman George Koukis, who started the banking software Temenous Group and leads that sector of software systems, speaks out in the update about the intrinsic value of CHARON.
"Charon prolongs the life of software by protecting it from constant change in hardware technology," he said. "Temenos' worldwide success meant that I replaced many systems; I am painfully aware of the immense cost of replacing or migrating application software."
Worldwide expansion through a partner network looks to be a key mission objective of the latest communique. When the company was briefing North American customers for the first time in May 2013 on a Training Day, the managers said that a channel structure for partners was being designed. Frédéric Kokocinski is the new Global Head of Channel Management. The new channel strategy focuses on marketing and communication -- including a comprehensive product roadmap -- certification for resellers, plus support through knowledge sharing, as well as a fresh push on sales.
The company has offices in place in Raleigh, NC, Switzerland, and Hong Kong. Gregory Reut is Head of Support. The company is meeting with partners to outline and detail the changes in its organization. Isabelle Jourdain is Head of Marketing. The company's co-founder, Robert Boers, remains connected to the company as a technology advisor to the board of directors.
July 28, 2014
Taking a :BYE before a :SHUTDOWN
HP 3000 systems have been supporting manufacturing for almost as long as the server has been sold. ASK Computer Systems made MANMAN in the 1970s, working from a loaned system in a startup team's kitchen. MANMAN's still around, working today.
It might not be MANMAN working at 3M, but the Minnesota Minining & Manufacturing Company is still using HP 3000s. And according to a departing MPE expert at 3M, the multiple N-Class systems will be in service there "for at least several more years."
Mike Caplin is taking his leave of 3000 IT, though. Earlier this month he posted a farewell message to the 3000-L listserve community. He explained that he loved working with the computer, so much so that he bet on a healthy career future a decade-and-a-half ago. That was the time just before HP began to change its mind about low-growth product lines with loyal owners.
Tomorrow, I’ll type BYE for the last time. Actually, I’ll just X out of a Reflection screen and let the N-Class that I’m always logged in to log me out.
I started on a Series II in 1976 and thought I died and went to heaven after working on Burroughs and Univac equipment. The machine always ran; no downtime, easy online development, and those great manuals that actually made sense and had samples of code. I still have the orange pocket guide for the Series II.
I found this list about the same time that getting help from HP became a hit or miss. I always got a usable answer after posting a question, usually in under an hour. So the purpose of this is to say goodbye, but also to say thank you for all of the help over the years.
I was in a headhunter’s office about 15 years ago and he told me that I needed to get away from the 3000 because I’d never be able to make a living until I was ready to retire. I told him that he may be right, but that I was counting on knowing enough to be able to stay employed and that I intended to outlast MPE. I guess I got lucky and won that argument.
July 25, 2014
Pen testing crucial to passing audits
Migrated HP 3000 sites have usually just put sensitive corporate information into a wider, more public network. The next audit their business applications will endure is likely to have a security requirement far more complicated to pass. For those who are getting an IT audit on mission-critical apps hosted on platforms like Windows or Linux, we offer this guide to penetration testing.
By Steve Hardwick
CSIPP, Oxygen Finance
Having just finished installing a new cable modem with internal firewall/router, I decided to complete the installation by running a quick and dirty on-line penetration test. I suddenly realized that I am probably a handful of home users that we actually run a test after installing the model. I used the Web utility Shields Up, which provides a quick scan for open ports. Having completed the test -- successfully I may add -- I thought it would be a good opportunity to review Pen, or penetration, testing as a essential discipline.
Penetration testing is a crucial part of any information security audit. They are most commonly used to test network security controls, but can be used for testing administrative controls too. Testing administrative controls, i.e. security rules users must follow, is commonly called social engineering. The goal of penetration testing is to simulate hacker behavior to see if the security controls can withstand the attack.
The key elements of either tests fall into three categories
1) Information gathering: This involves using methods to gain as much information about the target without contacting the network or the system users.
2) Enumeration: To be able to understand the target, a set of probing exercises are conducted to map out the various entry points. Once identified, the entry points are further probed to get more detail about their configuration and function.
3) Exploitation: After review of the entry points, a plan of attack is constructed to exploit any of the weaknesses discovered in the enumeration phase. The goal is get unauthorized access to information in order to steal, modify or destroy it.
Let's take a look at how all this works in practice.
July 24, 2014
Using VSTORE to Verify 3000 Backups
Hidden, to some managers running HP 3000s, is the VSTORE command of MPE/iX to employ in system backup verification. It's good standard practice to include VSTORE in every backup job's command process. If your MPE references come from Google searches instead of reading your NewsWire, you might find it a bit harder to locate HP's documentation for VSTORE. You won't find what you'd expect inside a MPE/iX 7.5 manual. HP introduced VSTORE in MPE/iX 5.0, so that edition of the manual is where its details reside.
For your illumination, here's some tips from Brian Edminster, HP 3000 and MPE consultant at Applied Technologies and the curator of the MPE Open Source repository, MPE-OpenSource.org.
If possible, do your VSTOREs on a different (but compatible model) of tape drive than the one the tape was created on. Why? DDS tape drives (especially DDS-2 and DDS-3 models) slowly go out of alignment as they wear.
In other words, it's possible to write a backup tape, and have it successfully VSTORE on the same drive. But if you have to take that same tape to a different server with a new and in-alignment drive, you could have it not be readable! Trust me on this -- I've had it happen.
If you'll only ever need to read tapes on the same drive as you wrote them, you're still not safe. What happens if you write a tape on a worn drive, have the drive fail at some later date -- and that replacement drive cannot read old backup tapes? Yikes!
July 23, 2014
Migrators make more of mobile support app
A serious share of HP 3000 sites that have migrated to HP's alternative server solutions have cited vendor support as a key reason to leave MPE. Hewlett-Packard has been catering to their vendor-support needs with an iPhone/Android app, one which has gotten a refresh recently.
For customers who have Connected Products via HP's Remote Support technologies, the HP Support Center Mobile (HPSCm) app with Insight Online will automatically display devices which are remotely monitored. The app allows a manager to track service events and related support cases, view device configurations and proactively monitor HP contracts, warranties and service credits.
Using the app requires that the products be linked through the vendor's HP Passport ID. But this is the kind of attempt at improving support communication which 3000 managers wished for back in the 1990s. This is a type of mobile tracking that can be hard to find from independent support companies. To be fair, that's probably because a standard phone call, email or text will yield an immediate indie response rather than a "tell me who you are, again" pre-screener.
But HPSCm does give a manager another way to link to HP support documents (PDF files), something that would be useful if a manager is employing a tablet. That content is similar to what can be seen for free, or subject to contract by public audiences, via the HP Business Portal. (Some of that content is locked behind a HP Passport contract ID.) This kind of support -- for example, you can break into a chat with HP personnel right from the phone or tablet -- represents the service that some large companies seem to demand to operate their enterprise datacenters.
There's also a Self-Solve feature in the HP mobile app, to guide users to documents most likely to help in resolving a support issue. Like the self-check line in the grocery, it's supposed to save time -- unless you've got a rare veggie of a problem to look up.
July 22, 2014
A Week When HP Gave OpenMPE the Floor
3000 community members at HP's facility for the OpenMPE meeting that replaced the scrubbed HP World 2005. From left, Walt McCullough, HP's Craig Fairchild and Mike Paivinen, Birket Foster (standing) and Stan Sieler.
It was a Maple floor, to be exact, in the Maple Room of the HP campus that's now long-demolished. On this day in 2005, in the wake of a washout of the user group Interex and its conference, the OpenMPE board met with HP to earn a space for an all-day meeting. HP extended use of its Maple Room -- where many a product briefing for the 3000 line had been held -- to the advocacy group that had fought for more time and better programs for migration and homesteading users.
In what feels like a long time ago, given all else that has changed, Interex closed its doors during this week in 2005 owing $4 million to companies small and large. The unpaid debts ranged from individuals owed as little as $8.30 on the unserved part of a yearly membership, to HP World booth sponsors who paid $17,000 for a space that the group could not mount in San Francisco. Then there were the hotels, which lost hundreds of thousands of dollars in unpaid room reservation guarantees. At five creditors to a page, the list of people and companies which the user group owed ran to more than 2,000 sheets. The file at the Santa Clara courthouse felt thick in my hands.
There was little money left at the end, too. The Interex checking account held $5,198.40, and a money market fund had $14,271.64 — neither of which was enough to satisfy the total unpaid compensation for an outside sales rep ($65,604 in unpaid commissions) or executive director Ron Evans (who had to forego his last paycheck of $8,225).
That OpenMPE meeting in August, in place of the Interex show, was notable in way that Interex could never manage. 3000 managers and owners could attend via phone and the web, using meeting software that let them ask questions and see slides while they could hear presentations.
July 21, 2014
Maximum Disc Replacement for Series 9x7s
Software vendors, as well as in-house developers, keep Series 9x7 servers available for startup to test software revisions. There are not very many revisions to MPE software anymore, but we continue to see some of these oldest PA-RISC servers churning along in work environments.
9x7s, you may ask -- they're retired long ago, aren't they? Less than one year ago, one reseller was offering a trio for between $1,800 (a Series 947) and $3,200. Five years ago this week, tech experts were examining how to modernize the drives in these venerable beasts. One developer figured in 2009 they'd need their 9x7s for at least five more years. For the record, 9x7s are going to be from the early 1990s, so figure that some of them are beyond 20 years old now.
"They are great for testing how things actually work," one developer reported, "as opposed to what the documentation says, a detail we very much need to know when writing migration software. Also, to this day, if you write and compile software on 6.0, you can just about guarantee that it will run on 6.0, 6.5, 7.0 and 7.5 MPE/iX."
Some of the most vulnerable elements of machines from that epoch include those disk drives. 4GB units are installed inside most of them. Could something else replace these internal drives? It's a valid question for any 3000 that runs with these wee disks, but it becomes even more of an issue with the 9x7s. MPE/iX 7.0 and 7.5 are not operational on that segment of 3000 hardware.
Even though the LDEV1 drive will only support 4GB of space visible to MPE/iX 6.0 and 6.5, there's always LDEV2. You can use virtually any SCSI (SE SCSI or FW SCSI) drive, as long as you have the right interface and connector.
There's a Seagate disk drive that will stand in for something much older that's bearing an HP model number. The ST318416N 18GB Barracuda model -- which was once reported at $75, but now seems to be available for about $200 or so -- is in the 9x7's IOFDATA list of recognized devices, so they should just configure straight in. Even though that Seagate device is only available as refurbished equipment, it's still going to arrive with a one-year warranty. A lot longer than the one on any HP-original 9x7 disks still working in the community.
July 18, 2014
HP gives leadership to Whitman top-down
Hewlett-Packard announced that it's giving the leadership of its board of directors to CEO Meg Whitman, after two chairmen had led the board but not the company in the years following CEO Mark Hurd's ouster.
Whitman joined the HP board in 2011, arriving about five months after Hurd left the company, but she didn't take her CEO role until the fall of that year. She's wrapping up her third year as CEO. Analysts see the addition of chairman to her duties as proof that HP's now her company to lead in totality.
Over the last two decades, only three other people have chaired the HP board as well as held the CEO role: Hurd, Carly Fiorina and Lew Platt. It's usually been an ultimate vote of confidence about a CEO's track record. None of the CEOs began their leadership of the company while heading up the board as well. Platt took his chairman's role from founder David Packard within a year of becoming CEO. Fiorina took the post from Dick Hackborn, 14 months after becoming CEO. Whitman becomes the third woman ever to lead the HP board, following Fiorina and Patricia Dunn. The latter took her job in the wake of Fiorina's ouster.
Leadership of Hewlett-Packard remains an issue for the migrated as well as migrating 3000 customers -- at least those who are investing in HP's alternatives to MPE. Whitman's record since taking her CEO duties has been admirable and at times heroic. She presided over a company in the early winter of 2012 with a stock valued at under $12 a share. In the course of her CEO term, Whitman's weathered the detritus of weak acquisitions such as Autonomy as well as the steep slowing of its services business growth. Whitman voted for Autonomy's acquisition as a board member, early in her directorship. But since 2013 she has championed growth through R&D rather than purchasing companies such as EDS and Compaq.
The board now contains only one longstanding HP employee, Ann Livermore, who serves as executive advisor to Whitman. More than 15 years ago, Livermore was passed over for the CEO job in favor of Fiorina -- but Livermore represents one of the last board members whose pedigree is in technology rather than business management. Livermore has been an HP employee since 1982.
Ralph Whitworth, who's reported to be in poor health, resigned the chairmanship he held since last year to make way for Whitman, as well as vacating his board seat. Klaus Kleinfeld, chairman and chief executive of Alcoa, arrives at the board to take Whitworth's seat.
July 17, 2014
TBT: When users posterized HP's strategy
The Orange County Register captured this picture of the football-field sized poster that users assembled to call notice to the 3000 at the annual Interex show. We offer it in our collection of ThrowBack Thursday photos. Click on it for detail.
Recent news about a decline in the health of community guru Jeff Kell sparked a link to another 3000 icon: Wirt Atmar. The founder of AICS Research shared some medical conditions with Kell, but Wirt was never at a loss for gusto and panache. Twenty-eight years ago he started a print job in July, one that wouldn't be complete until the following month, when HP World convened in Anaheim. The 1996 show was held not too far from a high school football field -- one where ardent users of the 3000 wanted to make publicity for their beloved MPE server.
Thousands of panels rolled out of Wirt's HP DesignJet plotter, driven by an HP 3000 at his Las Cruces, New Mexico headquarters, each making up a small section of the World's Largest Poster. HP had set the record for largest poster just a few months earlier, with a basketball court's worth of 8x11 sheets, placed carefully to make a giant picture of Mickey Mouse. Wirt and his league of extraordinary advocates took on another element while they aimed at a bigger poster, by far. This World's Largest Poster was to be assembled outdoors, in the Santa Ana winds of Southern California.
All morning on that summer day the winds continued to climb, testing the resolve of a growing number of volunteers. Panels would spring up in the breeze, which seemed to flow from every possible direction. Atmar, whose company had printed the thousands of panels over a six week period and who had driven the poster in a U-Haul truck from New Mexico, stood alongside the poster's edge and gave instruction on holding it in place, using gutter-width roofing nails pressed into the turf.
But by 11 AM, no more nails were on hand, and the question was on everyone's lips -- where are they? The winds climbed with the sun in the sky, and volunteers were forced to use shoes and poster tubes to hold the panels in place. As a section would rise up, dedicated customers would call out,"It's coming up!" and then race to tack it in place, an organic version of a fault-tolerant system.
The document of about 36,000 square feet was somehow kept in place on the high school football field. The work of printing began in July. When Wirt was finally able to point across the field, at the completed poster, he breathed a sigh of relief and good natured fatigue. He quipped that after printing the four-foot rolls of paper needed for the poster, loading them into a van for the trip to California represented “the summer corporate fitness program for AICS Research.”
July 16, 2014
Kell carries key account of 3000 revival
We've come to learn that community icon Jeff Kell is battling a serious illness. While I wish this keystone of MPE wisdom a quick recovery, and the best wishes to his wife, I'd like to share some insights he relayed about the transition from Classic 3000s to the ultimate edition of the server he's worked on and cared for most of his career at the University of Tennessee at Chattanooga.
I'd asked Kell to explain what the HP CEO during that transition era, John Young, might have been talking about while the CEO told Computerworld in 1985 about the strategy of RISC. As the clipping from Computerworld to the left shows, Young was a lot less than clear about what RISC would do for HP's long-term computing plans. A comment in the second paragraph of the clipping -- about networking, one of Kell's most ardent studies -- made me want to reach out to him earlier this summer. Young's conflation of "9000 series terminals emulated the 3000 architecture in some ways, but not really completely" was something Kell could clear up.
I'm not aware of any similarities [Young noted] between 3000/9000 Series except after adoption of RISC, and they used the same processors/hardware. They may have shared some peripheral hardware earlier, but certainly had little in common until RISC. The 3000/9000 had practically nothing in common prior to that other than perhaps HP-IB peripherals.
Network-wise, the 9000-series was following the ARPA/Ethernet track, while the 3000 initially started down the IEEE/OSI architecture. Ethernet was only accepted by the 3000 as an afterthought, it was a checkbox on the NMCONFIG dialogue if you wanted to allow it, and it defaulted to OFF.
So unless Young was talking post-RISC (timeframe is wrong), I'm not sure how he would compare 3000/9000 lines at all. The initial RISC 3000s were in the last half of the 1980s. If I recall correctly, my "migration training" to the "new" 3000s was at the Atlanta response center around 1985 (or a little later) and we were expecting a 930. We ended up with a 950 (since the 930 sucked so badly.) But I do recall many of the details.
July 15, 2014
3000 jobs still swinging their shingles
The Help Wanted sign remains out in the 3000 community for a couple of positions this week, genuine jobs that involve no migration of the server out of datacenters. Multiple offers inside the same week might actually give the employers a chance to compete with one another. But given the limited number of openings for MPE work, applicants aren't likely to be using one offer to leverage another.
At Cerro Wire, IT Director Herb Statham is looking for a programmer/analyst. Cerro Wire manufactures and distributes electrical wire for the residential and commercial building industries. Statham has been in the news in the past as an IT pro with a serious interest in the Stromasys emulator. Emulator interest has been known to be an indicator of a stable future for MPE applications.
Statham is looking for a P/A who knows COBOL for the 3000, IMAGE, MPE, and Suprtool. There's also Qedit, Adager, Netbase, Bridgeware, and byRequest running at the site in north central Alabama. The job's tasks run to development, change implementation, documentation and design, as well as planning. Applicants can send a resume to Statham at his email address.
Over at Measurement Specialties, the job we first noted near the end of June remains open. Business Systems Director Terry Simpkins is still open to reviewing resumes for a Business Analyst post.
July 14, 2014
Protecting a Server from DDoS Attacks
For anybody employing a more Web-ready server OS than MPE, or any such server attached to a network, Distributed Denial of Service (DDoS) presents a hot security and service-level threat. Migrating sites will do well to study up on these hacks. In the second of two parts, our security writer Steve Hardwick shares preventative measures to reduce the impacts to commodity-caliber enterprise computing such as Linux, Unix or Windows.
By Steve Hardwick, CISSP
DDoS attacks can be very nasty and difficult to mitigate. However, with the correct understanding of both the source and impact of these attacks, precautions can be taken to reduce their impact. This includes preventing endpoints from being used as part of a botnet to attack other networks. For example, a DDoS virus may not affect the infected computer, but it could wreak havoc on the intended target.
One legitimate question is why a DDoS attack be would used. There are two main reasons:
1) As a primary attack model. For example, a group of hacktivists want to take down a specific website. A virus is constructed that specifically targets the site and then is remotely triggered. The target site is now under serious attack.
2) As part of a multi stage attack. A firewall is attacked by an amplified Ping Flood attack. The firewall can eventually give up and re-boot (sometimes referred to as “failing over”). The firewall may reboot in a “safe” mode, fail over, or back-up configuration. In many cases this back-up configuration contains minimal programming and is a lot easier to breach and launch the next phase of the attack. I've had experiences where the default fail-over configuration of a router was wide open -- allowing unfiltered in-bound traffic.
DDoS attacks are difficult to mitigate, as they attack several levels of the network. However, there are some best practices that can be employed to help lessen the threat of DDoS attacks.
July 11, 2014
Understanding the Roots of DDoS Attacks
Editor’s Note: While the summertime of pace of business is upon us all, the heat of security threats remains as high as this season's temperatures. Only weeks ago, scores of major websites, hosted on popular MPE replacement Linux servers, were knocked out of service by Distributed Denial of Service DDoS attacks. Even our mainline blog host TypePad was taken down. It can happen to anybody employing a more Web-ready server OS than MPE, to any such server attached to a network -- so migrating sites will do well to study up on these hacks. Our security writer Steve Hardwick shares background today, and preventative measures next time.
By Steve Hardwick, CISSP
Distributed Denial of Service (DDoS) is a virulent attack that is growing in number over the past couple of years. The NSFOCUS DDoS Threat Report 2013 recorded 244,703 incidents of DDoS attacks throughout last year. Perhaps the best way to understand this attack is to first look at Denial Of Service, (DoS) attacks. The focus of a DoS attack is to remove the ability of a network device to accept incoming traffic. DoS attacks can target firewalls, routers, servers or even personal computers. The goal is to overload the network interface such that it either it unable to function or it shuts down.
A simple example of such an attack is a Local Area Network Denial. This LAND attack was first seen around 1997. It is accomplished by creating a specially constructed PING packet. The normal function of ping is to take the incoming packet and send a response to the source machine, as denoted by the source address in the packet header. In a LAND attack, the source IP address is spoofed and the IP address of the target is placed in the source address location. When the target gets the packet, it will send the ping response to the source address, which is its own address. This will cause the target machine to repeatedly send responses to itself and overload the network interface. Although not really a threat today, some older versions of operating systems -- such as the still-in-enterprises Windows XP SP2, or Mac OS MacTCP 7.6.1 -- are susceptible to LAND attacks.
So where does the Distributed part come from? Many DoS attacks rely on the target machine to create runaway conditions that cause the generation of a torrent of traffic that floods the network interface. An alternative approach uses a collaborative group of external machines to source the attack. For example, a virus can be written that sends multiple emails to a single email address. The virus also contains code to send it to everyone in the recipient's email address book. Before long, the targeted server is receiving thousands of emails per hour -- and the mail server becomes overloaded and effectively useless.
July 10, 2014
TBT: The month fem-power first led HP
You only have to go back 15 years to find a Throwback Thursday photo that captured watershed change for the HP 3000's creators. Carly Fiorina was named as HP's sixth CEO on a Monday in July, the start of the finale for a company's business way which created Hewlett-Packard-designed products as its biggest business.
Fiorina was all of 44 years old when she took a chair that had always been held by men over the first 60 years of HP's existence. In a BusinessWeek story that marked her ascent, the woman who'd become known only as Carly explained that she'd talked Dick Hackborn into staying on HP's board of directors. Telling readers that "Carly Fiorina has a silver tongue and an iron will," reporter Peter Burrows relayed Carly's own admission of feminine business power. The CEO-to-be said she was interviewed in a Chicago airport club restaurant.
"You can't tell me there's a better person for the job,'' she told Hackborn as the Gaslight's waitresses, clad in skimpy uniforms and fishnet stockings, made their rounds. Over the course of three hours, Hackborn agreed [to helm the board]. ''And no, I did not put on fishnet stockings,'' Fiorina says with a laugh. ''Don't even go there.''
At the time of her ascent, the business media had pegged Carly as the most powerful woman in business, with Oprah running number 2. “She is quite simply the ideal candidate to leverage HP’s core strengths in the rapidly changing information-systems industry and to lead this great company well into the new millennium,” said board member Sam Ginn, who led the search committee. It was a move that would lead the staid company into new eras of panache.
HP’s board said it was pushing for the company’s first outside CEO to lead the company in its new e-services push. Heading up AT&T spinoff Lucent’s $20 billion Global Service Provider division, Fiorina was named America’s Most Powerful Businesswoman in 1998 by Fortune magazine. Her selfies with pop stars came later.
July 09, 2014
How to Employ SFTP on Today's MPE
Is anyone using SFTP on the HP 3000?
Gavin Scott, a developer and a veteran of decades on MPE/iX, says he got it to work reliably at one customer a year or so ago. "We exchanged SSL keys with the partner company," Scott said, "and so I don't think we had to provide a password as part of the SFTP connection initiation."
At least in my environment, the trick to not having it fail randomly around 300KB in transfers (in batch) was to explicitly disable progress reporting -- which was compiled into the 3000 SFTP client as defaulting to "on" for some reason. I forget the exact command that needed to be included in the SFTP command stream (probably "progress <mumble>" or something like that), but without that, it would try to display the SFTP progress bar. This caused it to whomp its stack or something similarly bad when done in a batch job, due to the lack of any terminal to talk to.
July 08, 2014
That MPE spooler's a big piece to replace
Migration transitions have an unexpected byproduct: They make managers appreciate the goodness that HP bundled into MPE/iX and the 3000. The included spooler is a great example of functionality which has an extra cost to replace in a new environment. Unlike in Windows with MBF Scheduler, Unix has to work very had to supply the same abilities -- and that's the word from one of the HP community's leading Unix gurus.
Bill Hassell spread the word about HP-UX treasures for years from his own consultancy. While working for SourceDirect as a Senior Sysadmin expert, he noted a migration project where the project's manager noted Unix tools weren't performing at enterprise levels. Hassell said HP-UX doesn't filter many print jobs.
MPE has an enterprise level print spooler, while HP-UX has very primitive printing subsystem. hpnp (HP Network Printing) is nothing but a network card (JetDirect) configuration program. The ability to control print queues is very basic, and there is almost nothing to monitor or log print activities similar to MPE. HP-UX does not have any print job filters except for some basic PCL escape sequences such as changing the ASCII character size.
While a migrating shop might now be appreciating the MPE spooler more, some of them need a solution to replicate the 3000's built-in level of printing control. One answer to the problem might lie in using a separate Linux server to spool, because Linux supports the classic Unix CUPS print software much better than HP-UX.
July 07, 2014
User says licensing just a part of CHARON
Licensing the CHARON emulator solution at the Dairylea Cooperative has been some work, with some suppliers more willing to help in the transfer away from the compay's Series 969 than others. The $1.7 billion organization covers seven states and at least as many third party vendors. “We have a number of third party tools and we worked with each vendor to make the license transfers,” said IT Director Jeff Elmer.
“We won’t mention any names, but we will say that some vendors were absolutely wonderful to work with, while others were less so. It’s probably true that anyone well acquainted with the HP 3000 world could make accurate guesses about which vendors fell in which camp.”
Some vendors simply allowed a transfer at low cost or no cost; others gave a significant discount because Dairylea has been a long-time customer paying support fees. ”A couple wanted amounts of money that seemed excessive, but in most cases a little negotiation brought things back within reason,” Elmer said. The process wasn’t any different than a customary HP 3000 upgrade: hardware costs were low, but software fees were significant.
July 02, 2014
Co-op works out CHARON IO differences
Editor's note: Starting tomorrow it's a business holiday week's-end here in the US, so we are taking a few days to relax in a family reunion on the waters of a very well known Bay. We'll be back at our reporting on Monday.
At the Dairylea Cooperative in the Northeastern US, moving away from classic HP 3000 hardware to CHARON meant a bit of a learning curve. But the changes were something that even had a few blessings in disguise.
Moving files via FTP from the retired HP 3000 would be quicker and easier, said IT Director Jeff Elmer, "but of course it would require the physical box to be on the network. Getting our DLT 8000s to work with the emulator required some research, and some trial and error, but once you know the quirks and work around them, it’s actually quite reliable,” he said.
A new disaster recovery server had to be acquired. Dairylea purchased a ProLiant server identical to the one running what Elmer calls “our production emulator,” The DR emulator is installed it in the same city where the physical HP 3000 DR box was, complete with tape drives. Stromasys supplies a USB key for the DR emulator as part of the support fees; the key contains HPSUSAN and HPCPUNAME codes required to boot up MPE and other software. The key is good for 360 hours of DR operation “and it expires at the same time our annual support does.”
July 01, 2014
Northeastern cooperative plugs in CHARON
A leading milk and dairy product collective, a century-plus old, is drawing on the Stromasys emulator’s opportunity.
A $1.2 billion milk marketing cooperative — established for more than 100 years and offering services to farmers including lending, insurance and risk management — has become an early example of how to replace Hewlett-Packard’s 3000 and retain MPE software while boosting reliability.
The Dairylea Cooperative has been using the Stromasys CHARON emulator since the start of December, 2013, according to IT director Jeff Elmer. The organization that was founded in 1907 serves dairy owners across seven states in the US Northeast, a collective that had been using two Hewlett-Packard brand RISC servers for MPE operations.
Dairylea has taken its disaster recovery 3000 offline since December 1. Although HP’s physical 3000 server is still powered up, it’s been off the network all year while production continues. “Once we made the switch to the emulator, we never went back to the physical box,” Elmer said. ‘We can’t see any reason to at this point.”
“However much we may love HP’s 3000 hardware, the disk drives are still older than half of our IS department. Some of our users never knew there was a change.”
June 30, 2014
Update: Open source, in 3000 ERP style
An extensive product roadmap is part of the OpenBravo directions for this open source ERP commercial solution
Five years ago today, we chronicled the prospects of open source software for HP 3000s. We mentioned the most extensive open source repository for MPE systems, curated by Brian Edminster and his company Applied Technologies. MPE-OpenSource.org has weathered these five years of change in the MPE market and still serves open source needs. But in 2009 we also were hopeful about the arrival of OpenBravo as a migration solution for 3000 users who were looking for an ERP replacement of MANMAN, for example -- without investing in the balky request-and-wait enhancement tangle of proprietary software.
Open source software is a good fit for the HP 3000 community member, according to several sources. Complete app suites have emerged and rewritten the rules for software ownership. An expert consulting and support firm for ERP solutions is proving that a full-featured ERP app suite, Openbravo, will work for 3000 customers by 2010.
[Editor's note: "We meant work for 3000 customers" in the sense of being a suitable ERP replacement for MPE-based software].
A software collective launched in the 1990s by the University of Navarra which has evolved to Openbravo, S.L., Openbravo is utilized by manufacturing firms around the world. Openbravo is big stuff. So large that it is one of the ten largest projects on the SourceForge.net open source repository, until Openbravo outgrew SourceForge. The software, its partners and users have their own Forge running today. In 2009, Sue Kiezel of Entsgo -- part of the Support Group's ERP consulting and tech support operations -- said, “We believe that within six to nine months, the solution will be as robust as MANMAN was at its best.”
From the looks of its deep Wiki, and a quick look into the labs where development is still emerging for advanced aspects such as analytics, Entsgo's premonition has come to fruition. Managing manufacturing is easily within the pay-grade of open source solutions like OpenBravo.
June 27, 2014
Mansion meet takes first comeback steps
A few hours ago, the first PowerHouse user group meeting and formation of a Customer Advisory Board wrapped up in California. Russ Guzzo, the guiding light for PowerHouse's comeback, told us a few weeks ago that today's meeting was just the first of several that new owner UNICOM Global was going to host. "We'll be taking this on the road," he said, just as the vendor was starting to call users to its meeting space at the PickFair mansion in Hollywood.
We've heard that the meeting was webcast, too. It's a good idea to extend the reach of the message as Unicom extends the future of the PowerHouse development toolset.
This is a product that started its life in the late 1970s. But so did Unix, so just because a technology was born more than 35 years ago doesn't limit its lifespan. One user, IT Director Robert Coe at HPB Management Ltd. in Cambridge, wants to see PowerHouse take a spot at the table alongside serious business languages. Coe understands that going forward might mean leaving some compatibility behind. That's a step Hewlett-Packard couldn't ever take with MPE and the HP 3000. Some say that decision hampered the agility of the 3000's technical and business future at HP. Unix, and later Linux, could become anything, unfettered by compatibility.
Coe, commenting on the LinkedIn Cognos Powerhouse group, said his company has been looking at a migration away from Powerhouse -- until now.
I would like to see Powerhouse developed into a modern mainstream language, suitable for development of any business system or website. If this is at the expense of backwards compatibility, so be it. We are developing new systems all the time, and at the moment are faced with having to use Java, c# or similar. I would much rather be developing new systems in a Powerhouse based new language, with all the benefits that provides, even if it is not directly compatible with our existing systems.
The world would be a better place if Powerhouse was the main platform used for development! I hope Unicom can provide the backing, wisdom and conviction to enable this to happen.
June 26, 2014
3000 sages threwback stories on Thursday
Two weeks ago in the modest London pub Dirty Dick's, a few dozen veterans and sages of the 3000 system had their personal version of a Throwback Thursday. This is the day of the week when Facebook and Twitter users put out a piece of their personal history, usually in the form of a picture from days long past.
If pressed for a piece of June Throwback Thursday material, I might reach for our very first blog post. Nine years ago this month we kicked off our coverage of new, every-workday reporting. My first story was a tribute to a just-fallen comrade in the 3000 community. Bruce Toback died in that month the Newswire's blog was born. As I said in that first blog article -- "A Bright Light Winks Out" was already a throwback, before the term gained its current coin -- Toback was extraordinary, the kind of person that makes the 3000 community unique. He lived with a firm grip on life's handrail of humor. He died unexpectedly of a heart attack at age 48. As part of a gentle and generous Toback memorial, David Greer hosts pictures of Bruce like the one above. Many of these were taken as Toback became important to the Robelle Qedit for Windows project.
The passing of a special life is a good reason to celebrate what remains for all of us. That's probably what motivated those London veterans to gather at Dirty Dick's Pub this month to toss off stories and toss back drinks. Bob Green of Robelle (pictured here in a throwback picture in the spring of 2001, when he was working from his Anguilla island headquarters) shared some pub photos and a brief report about this month's Throwback Thursday for your community.
“It was great to catch up with 3000 colleagues from around the world: Steve Cooper, Dave Wiseman, Brian Duncombe, Kim Leeper, Brad Tashenberg, the Nutsfords and many more (about 20 in all). We exchanged notes on the current state of the machine -- especially the new emulator -- and discovered what each of us was doing. [Editor's Note: Duncombe (above) had made this trip in a record 48-hour-complete turnaround, from Canada to the UK and back. The intensity still burns bright for some of your community members.]
Green noted, while posting photos of Cooper and Leeper in conversation, or the sweet couples' photo (below) of Jeanette and Ken Nutsford, "An amazing number of people are still doing the same thing: helping customers with their IT concerns. But in reality, most of the time was spent swapping war stories from the past, which was great fun.
"Here are some photos from the party. Everyone is older, but perhaps you will remember some of them." This photo of the Nutsfords, ever the COBOL and HP Rapid standards-bearers, is something of a coup. The couple retired from the world of the 3000 to set off an epic career of cruise line travels, so catching them for a picture requires some foresight. They are circling the globe in a lifestyle that shows there's another, more rewarding kind of migration awaiting the luckiest of us.
June 25, 2014
What level of technology defines a legacy?
Even alternatives to the HP 3000 can be rooted in legacy strategy. This week Oracle bought Micros, a purchase that's the second-largest in Oracle history. Only buying Sun has cost Oracle more, to this point in the company's legacy. The twist in the story is that Micros sells a legacy solution: software and hardware for the restaurant, hospitality and retail sectors. HP 3000s still serve a few of those outlets, such as duty-free shops in airports.
Micros "has been focused on helping the world’s leading brands in our target markets since we were founded in 1977," said its CEO. The Oracle president who's taking on this old-school business is Mark Hurd, an executive who calls to mind other aspects of legacy. Oracle's got a legacy to bear since it's a business solution that's been running companies for more than two decades. Now the analysts are saying Oracle will need to acquire more of these customers. Demand for installing Oracle is slowing, they say.
In the meantime, some of the HP marketplace is reaching for ways to link with Oracle's legacy. There's a lot of data in those legacy databases. PowerHouse users, invigorated by the prospects of new ownership, are reaching to find connection advice for Oracle. That's one legacy technology embracing another.
Legacy is an epithet that's thrown at anything older. It's not about one technology being better than another. Legacy's genuine definition involves utility and expectations.
It's easy to overlook that like Oracle, Unix comes in for this legacy treatment by now. Judging only by the calendar, it's not surprising to see the legacy tag on an environment that was just finding its way in the summer of 1985, while HP was still busy cooking up a RISC revolution that changed the 3000's future. Like the 3000's '70s ideal of interactive computing -- instead of batch operations -- running a business system with Unix in the 1980s was considered a long shot.
An article from a 1985 Computerworld, published the week that HP 3000 volunteer users were manning the Washington DC Interex meet, considered commercial Unix use something to defend. Like some HP 3000 companies of our modern day, these Unix pioneers were struggling to find experienced staff. Unix was unproven, and so bereft of expertise. At least MPE has proven its worth by now.
June 24, 2014
Robelle shows off uniformizing phone data
The latest newsletter from Robelle Solutions Technology shows off how to normalize phone numbers in databases. (To be precise, this is a process that's different from classic database normalization: It's more like "uniformization," to cobble together a term, since normalization has already been taken, years ago while creating database maintenance procedures.)
The object of this uniformization is to remove the non-number characters from a phone number byte container. Normalization is a significant element in data cleansing. As IT pros on the move in a migration, or just diligent about their use of company resources will report, cleansing doesn't happen only when you're moving data between platforms or app to app.
Suprtool expert Neil Armstrong of Robelle said that "Considering the following data, you see that the phone numbers have all sorts of different formats."
>in myphone >list >xeq >IN myphone (0) >OUT $NULL (0) PHONENUM = #123.456.7890 >IN myphone (1) >OUT $NULL (1) PHONENUM = (123)567-1234 >IN myphone (2) >OUT $NULL (2) PHONENUM = (321).123.5678 IN=3, OUT=3. CPU-Sec=1. Wall-Sec=1.
Robelle -- whose Bob Green also posted news of this month's HP3000 Reunion meeting at Dirty Dick's pub in London -- asked Armstrong to show how all of these phone formats could be fit into a consistent container.
June 23, 2014
New search for 3000 expertise surfaces
New openings for HP 3000 production and development jobs are uncommon prizes by now. Contract firms have been known to solicit MPE help while making a migration happen. Application support suppliers need IT professionals who know the details of mission-critical software, too.
But every once in awhile, a company that's still dedicated to using MPE software sends the word out that it's hiring for HP 3000 and MPE specifics. Such is the case from Measurement Specialties. The location is at the company's Hampton Roads, Virginia headquarters. The job listing from Terry Simpkins, Director of Business Systems for the manufacturer which uses MANMAN, Fortran and VEsoft's MPEX and Security/3000 -- among other platform-specific tools such as TurboIMAGE -- describes both classic and specialized enterprise IT skills.
"The leading manufacturer of sensors and sensing systems" is seeking a Business Analyst.
Areas of responsibility include:
- Daily user training and support
- Participate in projects in all functional areas of the business
- Serve as backup support for HP3000 operations and nightly processing
Key skills and capabilities include:
- Strong MANMAN experience and expertise
- Ability to read Fortran and perform some level of programming
- Strong understanding of MPEX scripting and Security/3000 menus
- Ability to handle multiple concurrent projects and tasks
June 20, 2014
Time to Sustain, If It's Not Time to Change
In the years after HP announced its 3000 exit, I helped to define the concept of homesteading. Not exactly new, and clearly something expected in an advancing society. Uncle Lars' homestead, at left, showed us how it might look with friendly droids to help on Tattooine. The alternative 3000 future that HP trumpeted in 2002 was migration. But it's clear by now that the movement versus steadfast strategy was a fuzzy picture for MPE users' future.
What remains at stake is transformation. Even to this week, any company that's relying on MPE, as well as those making a transition, are judging how they'll look in a year, or three, or five. We've just heard that software rental is making a comeback at one spot in the 3000 world. By renting a solution to remain on a 3000, instead of buying one, a manager is planning to first sustain its practices -- and then to change.
Up on the LinkedIn 3000 Community page I asked if the managers and owners were ready to purchase application-level support for 3000 operations. "It looks like several vendors want to sell this, to help with the brain-drain as veteran MPE managers retire." I asked that question a couple of years ago, but a few replies have bubbled up. Support has changed with ownership of some apps, such as Ecometry, and with some key tools such as NetBase.
"Those vendors will now get you forwarded to a call center in Bangalore," said Tracy Johnson, a veteran MPE manager at Measurement Specialties. "And by the way, Quest used to be quick on support. Since they got bought by Dell, you have to fill in data on a webpage to be triaged before they'll even accept an email."
Those were not the kind of vendors I was suggesting. Companies will oversee and maintain MPE apps created in-house, once the IT staff changes enough to lose 3000 expertise. But that led to another reply about why anyone might pursue the course to Sustain, when the strategy to Change seems overwhelming.
June 19, 2014
Making Sure No New Silos Float Up
Cloud computing is a-coming, especially for the sites making their migrations off of the HP 3000. But even if an application is making a move to a cloud solution, shouldn't its information remain available for other applications? Operational systems remain mission-critical inside companies that use things like Salesforce.
To put this question another way, how do you prevent the information inside a Salesforce.com account to become a silo: that container that doesn't share its contents with other carriers of data?
The answer is to find a piece of software that will extract the data in a Salesforce account, then transform it into something that can be used by another database. Oracle, SQL Server, Eloquence, even DB2. All are active in the community that was once using TurboIMAGE. Even though Salesforce is a superior ERP application suite, it often operates alongside other applications in a company. (You might call these legacy apps, if they're older than your use of Salesforce. That legacy label is kind of a demerit, though, isn't it?)
Where to find such an extraction tool? A good place to look would be providers of data migration toolsets. This is a relatively novel mission, though. It doesn't take long for the data to start to pile up in Salesforce. Once it does, the Order Entry, CRM, Shipping, Billing and Email applications are going to be missing whatever was established in Salesforce initially. The popular term for this kind of roadblock is Cloud Silo.
It reminds me of the whole reason for getting data migration capabilities, a reason nearly as old as what was once called client-server computing. Back in the days when desktop PCs became a popular tool for data processing, information could start out on a desktop application, not just from a terminal. Getting information from one source to another, using automation, satisfies the classic mission of "no more rekeying."
It's a potent and current mission. Just because Salesforce is a new generation app, and based in the cloud, doesn't make it immune to rekeying. You need a can opener, if you will, to crack open its data logic. That's because not every company is going all-in on Salesforce.