May 09, 2013
Socializing can lead to contained footprints
Our friend and columnist Scott Hirsh just called to confirm he'll be at tonight's Stromasys HP 3000 Social at the Tied House. I took the walk over there today, because it's just down the street from the Caltrain Station as well as the terminal for the San Jose light rail. Buffalo burger is today's special.
But what's more special is the range of 3000 sites who'd be Charon HPA/3000 prospects, if only they knew how to focus on fitting into a new server paradigm. One site that Scott visited out in Union City, Calif. was discussing available IT datacenter floor space. "How are you fixed for that?" says Scott.
"Well, we've got this big system in the back of the datacenter we have to keep running," the IT manager says, explaining the server keeps significant parts of the company running. Even though Scott is out there in Union City to help the manager with Dell solutions, he's curious about what this box is.
"We're pretty sure it's an old HP 3000," the manager says. Scott's invited him tonight for some beverages and heavy appetizers, but there's been no RSVP yet from Union City. If you're in the area, come by tonight, or tomorrow at the Computer History Museum. You might find a way to free up floor space while you don't have to throw your critical MPE applications overboard.
Hope to see you tonight over a pint. You never know what opportunity might bloom, like those curbside flowers growing out of a beer cask on Villa Street at the Tied House.
May 07, 2013
Emulator's days are not so early after all
"It's early days," say more than a few community vendors about the lifespan of the Charon HPA/3000 emulator. They point to a lack of reference accounts. Some note that no third parties are engaged to teach and train and support the virtualization solution. Even the vendor acknowledges the performance of this 3000-on-Intel magic needs to surpass the power of a 4-way N-Class system.
But it's not early according to Adager's CEO Rene Woc. We tried out the accepted wisdom and found him pushing back on the popular view. It's misguided, by the reports he's getting from customers small, medium and very large. He reached out for a Yogi Berra quote to guide his outlook. "The future ain't what it used to be," Yogi said. That's especially apt when customers are gathering license data for your software, to be used on Charon. Or when they share their intentions, which is to keep MPE software running well into that future. How different it is than it used to be.
These are customers getting information about Adager's license transfer plan. "It's just another MPE machine," Woc reported. "We are treating the emulator just like HP3000 hardware."
As has been well-chronicled by now, there's no technical issues in this complete emulation. "Our customers didn't come across any issues," Woc said. Given the reputation of the Adager labs -- a tight-knit group that uncovered the last, corruptive bug in IMAGE and alerted HP to spark a repair -- "no problems" means Charon runs as expected.
Adager charges a $975 license transfer fee to move software from one HPSUSAN number to another. The software does not cross check with an HPCPUNAME, so moving the HPSUSAN to the emulated server, plus that transfer fee, covers the extent of Adager's operations. This is one vendor that 3000 users don't have to work out a license with. One of many (like Minisoft) who see continuing business coming out of emulated 3000s.
"It's to Stromasys credit they've been able to distribute this news about it," Woc said. "Our customers have made the decision to go ahead with it. It's beyond testing. It's between decision and testing, and then putting it to work. We've gotten very encouraging signals, and not necessarily from hobbyists. From actual companies that are at different stages. People have moved on from testing to ordering their license transfers [from us].
"People have called to order a trial Adager license" as a result of Charon HPA/3000 testing, he added. "At this stage it's taking off. As far as tangible results right now, I think it has a good psychological effect. People feel comfortable knowing that they're not facing a closed future."
Yogi's comment about the future that "ain't what it used to be" was a darkening one in the old days of software and systems. A computer fell out of product lineup, then the vendor ended support. The customers fled and the independent software community curtailed support. Now the future includes many years of 3000 production for these license transferring customers.
And Woc said that customers include some very large corporations, because Adager has always been in shops very large and very small. Robelle is on the Stromasys bandwagon too. These kinds of software products don't make up applications off the shelf. But to be honest, software off the shelf has not been the 3000's specialty for a long time. Ecometry and MANMAN aside, and a few dozen Amisys sites -- the 3000 keeps working on customer-written apps. Only these tool providers, like VEsoft and its MPEX -- need to agree to licenses for Charon. The rest of the solution is code a customer owns because they're built it themselves.
The emulator product "takes the pressure off in the sense that MPE cannot be continued," Woc said. "It will run on the latest and greatest Intel hardware." He added that VMware, part of the solution, "is a fully supported product. From that point of view, I think people feel confident they have an option -- knowing also that the [off the shelf] 3000 applications have very little development. The shops that depended on Ecometry and the like know they will still have an engine to keep running their business."
If the economy fully recovers, some of these emulator sites will move ahead with migrations. "We will see. If they can still handle their business, even after that, they may just stay. If a new business model comes up, like mail order became ecommerce so many years ago. It's so hard to predict." These days are early for some application users. For others, it's a matter of scheduling an emulator product that's a small fraction of the cost of a migration -- both in capital cost as well as the price of disruption of what's not the future, but today.
April 24, 2013
Program for legacy with a legacy dev tool
Good tools don't always survive bad times. When HP pulled its plug from the 3000 dynamo, popular development tools began to slide. One of our favorite COBOL legends and 3000 consultants, Bruce Hobbs, was looking for ways to connect to the legacy community for such a dev tool, Programmer Studio.
"I have a vague recollection that you published something awhile back regarding the demise of Whisper Technology, and the situation for anyone now interested in using the Programmer Studio product," Hobbs said. "Could you please point me in the right direction?"
The genesis of Programmer Studio comes from the days when HP was still buying print ads for the HP 3000 in the general computer industry trade press. Ads that astounded the installed base -- like the one at left -- because they were so rare, and resonated so well with the established consumers. The 3000 had giant corporations using it, something HP had to admit from time to time while it labored to create a business computing market for Unix. Whisper popped up often when we surveyed the legacy developer community in December. This is unsupported software, but it's still in use at the occassional programmer's bench, such as the one that Michael Anderson operates at J3K Solutions.
I was never much for purchasing tools for development. However, since the late '90s onward, I used Programmer Studio from Whisper Technologies as a "character based" editor. In the latter years of working on MPE, the languages I used also included Java, Perl, and SQL.
(In a bit of circular technology, the Robelle programming tool for the HP 3000, Qedit for Windows, also knows a lot about Suprtool -- since Supertool is also a Robelle product.)
"But today I don't use the HP 3000 much any more, nor Windows," Anderson added. "For years Programmer Studio kept me tethered to Windows as my favored editor. Recently I've started using JEDIT on Linux. JEDIT doesn't know how to access the HP3000, so for that I still use Windows along with Programmer Studio."Authors and creators tend to dig in with their tools. Hobbs asked about Programmer Studio because of its reputation, but he understood the software had not survived the HP purge.
But for that matter, that kind of afterlife is where other 3000 software resides today. The developer of the Programmer Studio has moved on to other things, according to the Whisper Technology founder Graham Wooley. In 2009 he said
Unfortunately Whisper Technology is no more. As the developer, Greg Sharp had looked after Whisper and Programmer Studio by himself for the last three years, but he has now moved on to other things and the company has now closed.
The UK's Whisper built and promoted the Programmer Studio PC-based toolset, then sold it as a development environment which understood exchanges with the 3000, but could also be used to create programs under Windows. Robelle responded promptly with a Windows version of Qedit, and for more than five years the 3000 ecosystem had a lively competition for programming tools.
Survival is one of the better measurements of quality, but good technology sometimes has to succumb to business issues and investment strengths. Such was the case for HP's business with the 3000 and MPE. Like Programmer Studio, MPE is no longer supported by its creators. Unlike Programmer Studio, MPE has third party support, as well as an emulation engine being sold this year. These things are markers of survival.
An experienced 3000 developer like Hobbs probably won't care much about support for a programmer's tool. Wooley's company was a lively bed of 3000 ardor in the 1990s. At one point, he placed a bet with Adager's Alfredo Rego. Wooley was so concerned about HP's treatment of the 3000 in 1993 that he wagered with Rego that HP wouldn't advertise the system -- mostly as a prod for HP to do so. Wooley lost his bet, happily, when Hewlett-Packard put ads in both US and European publications for the 3000 at the 11th hour of that year.
An abandoned but beloved product is usually passed along from one user to another, with each exchange marking another step into the public domain. HP's been vigilant about MPE to keep the OS out of this sort of drift. People admire it in the same way that Programmer Studio advocates praise that product.
The difference is that you'll still be able to buy support for MPE from independent professionals, some of whom have a source code license for the software. Adager is on that source code holder list. So are the indie support firms Pivital Solutions, Allegro Consultants, Beechglen Development and Terix. They are all eating their Wheaties, surviving into our new era.
April 19, 2013
Where Everybody Knows Your CPUNAME
The iconic TV show Cheers splashed a theme song about the fictional Boston tavern every Thursday, way back in the 1980s. It was a drinking outpost "where everybody knows your name, and they're all so glad you came." If attendance works out well for Stromasys at its HP 3000 Social -- four weeks away -- they're likely to have the same sort of turnout. The Tied House will be a place where everybody knows your name because so many will be familiar to each other. That's what more than three decades of community gives you.
This week the blue and white postcards arrived in mailboxes announcing the combination of Social and Training May 9-10. We found one in our mailbox, but word of the event is spreading beyond the reach of the US post. Vladimir Volokh of VEsoft called to report he'll be at the Tied House. Neil Armstrong, developer and curator of Suprtool, has also been tracking the event closely.
These VIPs of your community will be joined by people experienced in 3000 matters who seek a way around aging HP hardware for MPE. And there will be some stopping by to see the names that they know and meet new ones with something in common. Everybody there will be listening for news about licensing. Right now this is a rare brew that prospects are thirsting for if they want to emulate a production machine.That postcard doesn't share much of the agenda for the meeting, some details of which are revealed at the Stromasys RSVP webpage. (The whole thing is free, by the way, right down to the heavy appetizers where everybody knows your name.) More to the point, it doesn't reveal the strategy that will drive your feet to that bar where everybody will know your name. Your interest in the emulator is assumed. Knowledge and experience and boasting and whining, laced with humor, were always the prime reasons for attending an HP 3000 user group event. In the absence of a user group, this kind of gathering will have to provide those usual incentives. Expect a lot of "we migrated awhile ago, and here's how it went" along with "we don't want to, and here's the license and support issues we need to solve."
The technology is not an issue. The training on May 10 will prove that to anyone who hasn't seen a demo yet, and the take-home freeware A202 version will give attendees an easy way to do a proof of concept.
Will the system administrator who's moving away from Powerhouse -- slower than expected -- be at Tied House, or the Computer History Museum the next day? Stromsays is keeping track of the RSVPs. Such an attendee would be interested in how the licensing is going with IBM, the keepers of the Cognos products. Powerhouse users have recent memories about investigations about their licenses, with demands for upgrade fees.
We've begun the effort to get Charlie Maloney of IBM, formerly of Cognos, to tell us anything about licensing Powerhouse for the emulator. No comment yet, after about a week of attempts. But Charlie is busy being the Software Sales Representative at IBM Software Group, Information Management, so he might need repeated attempts. I'll keep trying.
I anticipate that if the Tied House and CHM are filled with more than tire-kickers who want to talk about an emulator in demonstration, they'll get down to license discussions. An IT analyst up at a higher education institution said if license fees to move to the emulator match the annual HP 3000 hardware maintenance contract, it's a deal-breaker.
The issue that would destroy the cost-neutrality concept would be software licensing fees. To save costs during our migration to the ERP software, we let software maintenance lapse on all of the utilities that were permanently licensed -- that is, all of those that would continue to run without a refreshed license key each year.
It almost sounds like utility vendors on that system haven't earned a dime during the migration. Taking those utilities onto the emulator, sans support, is only even remotely possible if the emulator is stopgap on the way to a migration. We'll leave it to the reader to judge if its fair.
Migrating customers will look at these license vs. support tradeoffs and see the challenge of staying with MPE. They've made the decision to stay with hardware that demands a support contract of significant investment, but at least their software licenses have no surprises. It doesn't mean the software is anything close to free, since the 15-20 percent application support fees are in place. All that IBM, nee Cognos, will charge for its 8.49F Powerhouse is Vintage Support.
The tough part for that analyst is that his Powerhouse license is 8.49E, not F. The F version had all of its platform-upgrade fees removed, we learned. The way from 8.49E to F is as uncharted to me as Maloney's reply.
There's always the possibility that customers who know each other's name could get together to arrange a group negotiation with such upgrade-fee vendors. Stromasys won't do this officially; it's up to the emulator customers. As for those utility support dollars, they ought to be going to the vendors if those utilities are key to keeping a production system online. That's the 3000/MPE tradition: guaranteed uptime.
We hope it's a rich brew of license and support insights at Tied House, blended with the eye-opener of the training that includes a Linux cradle for the emulator the day after.
April 02, 2013
CAMUS schedules Spring webinar for April
The ERP and manufacturing user group CAMUS will host its every-springtime user group event on April 17, including discussion about the future of MANMAN led by community advocate and 3000 veteran Terry Floyd of the Support Group.
Terri Glendon Lanza, the founder of the Ask Terri ERP and manufacturing consultancy, has announced the call-in and PowerPoint meeting, which will begin at 10:30 Central US time. After an hour of talk and questions about the upcoming years for one of the oldest MPE applications -- still running in several hundred companies -- 3000 homesteading advice starts at 11:45.
Steve Suraci, owner of support and systems provider Pivital Solutions, talks first about Resources for Homesteading. Tom Bollenbeck of Ideal Computer follows up, on the same topic, at 12:05.
The user group's traditional and lively Talk Soup puts a signature on the meeting, which is free. An open discussion is scheduled to start at 12:25. You sign up at the Sign Up Genius website.
Up for discussion: MANMAN Modifications, and a possible CAMUS give-away. "Help us outline contents, actions, or a submission list for modifications with financial assistance from CAMUS," Lanza said in her April 2 announcement. "We could talk about the emulator during the open discussion if you want. Everyone is welcome."
Details for the webinar phone-in and log-on will be emailed to registrants prior to the meeting. You can send questions to Lanza at firstname.lastname@example.org, or call her at 630.212.4314.
CAMUS is also prepared to help support a springtime in-person 3000 Social and Stromasys Training event. This is allegedly being held in May, but we're waiting on final confirmation from Stromasys. Once again, the Bay Area's Computer History Museum in Mountain View has been proposed as the setting.
"CAMUS would consider helping sponsor events whenever it may happen, spring or fall," Lanza said. The user group was one of the sponsors the HP3000 Reunion, held at the Museum in September, 2011.
March 29, 2013
Hope floats today for a 3000 resurrection
As a former Catholic altar boy, I learned a lot about resurrection during Springs in the 1960s. But the headline above isn't early April Fool's blasphemy. Some 3000 users -- more than a dozen, like disciples -- believe that an emulator in their market is a reason to believe in the server's revival.
They're somewhat correct, but how accurate is a revival of MPE/iX, versus the hardware to host it? Stromasys has accomplished the latter miracle with Charon HPA/3000. Servers as common as bottled water are running MPE/iX today, in production environments or proving the concept that PA-RISC systems have come back from a state of doom. Some are even succeeding with untested chips from AMD, somehow, rather than the approved Intel processors.
We've just approved a comment here on our blog that invests the emulator with these regenerative powers. HP would need a revival of its spirit to start to sell proprietary servers again, but at least there's powerful spirit among a few customers. None of them are paying HP any longer for the 3000. We'll get to that in a minute, and how it affects the salvation of critical MPE/iX applications. But to that prayer:
I say that with the advent of Stromasys and the interest from application developers who wrote for the HP 3000, there is now the opportunity for the community to form a company to begin marketing MPE/iX. The world is ready for a stable, secure, alternative to the out-of-control Linuxes and the costly well-known operating systems.
This manager doesn't want his name or company mentioned, but I assure you he's real and in charge of several HP 3000s. Third parties provide MPE and 3000 support at his site, and he runs HP's final low-end model of 3000, an A-Class. Although this is the season of miracles for hundreds of millions, marketing MPE/iX would demand a change of ownership at Hewlett-Packard. To kick-start it, people like our manager above would have to become customers of HP once more. The company took a conservative view of "customer" and "owner" five years ago this month. Nothing's changed there yet.
The issue of enabling Intel hardware to host MPE/iX is settled. Over and over, we've heard that the emulator runs the 3000's OS just as well as HP-built iron, the boxes HP stopped building nearly 10 years ago. The big rock to roll back is the status of software ownership. Many of the largest software companies take a dim view of operating their programs on fresh hardware. At least without any notice of the shift in platform.
Some companies -- and the 3000 veterans know who they are -- want a license fee upgrade if there's significant performance boosts on the new platform. The change that triggers this is the HPCPUNAME. Unless it still reports "Series 929" or somesuch, this emulated installation is a newer 3000.
Other software vendors are simply delighted their products will continue to work at customer sites. A customer site, however, is often defined as a company which pays a regular fee to maintain a relationship with the vendor. There's a lot of dropped-support software running out in your community. Vendors always have to live with this. Now there's a new wrinkle with the change of platform.
"If I was a paying customer of a software vendor, I'd keep quiet about using the emulator," one vendor said. He added that he's got no problems with his own customers using Charon. Any company prohibiting a switch "would be stupid, because you'd be losing revenue."
Earlier this week, however, I heard a statement that's true. "There's no application company yet which has approved a license for running software on the emulator." There's one story of Cognos permitting Quiz to run on a production emulator at an Australian insurance corporation. Warren Dawson, who plunged into the emulation pool, got it arranged by his Cognos reseller. Who's dealing with IBM these days, since Big Blue bought Cognos long ago.
IT managers can be lured into beliefs that run afoul of the computer vendor's catechism, however. Some managers believe they own their software once it's abandoned by the vendor. HP made its case that MPE/iX will always belong to HP, and always did, even while people were buying support from HP in 2008.
At a user meeting that year, the business manager of 3000 operations at HP Jennie Hou made HP's position clear.
Hou confirmed the clear intention that HP will cede nothing but "rights" to the community after HP exits the 3000 business."The publisher or copyright owner still owns the software," Hou said when license requirements beyond 2010 were discussed. "You didn't purchase MPE/iX. You purchased a right to use it."
Several years ago, a European Union judge gave an advisory on a case about PC software. The judge said if a company walks away from a product, anybody has any right they'd like to use it in any way. There's a lot of defining to do to arrive at "walks away." It was only one judge. But things are changing very quickly in the world of intellectual property.
To see the cross that such hopeful disciples bear, look at what I wrote five years ago, after hearing HP's statement and seeing the slide below.
We were writing about independent support and source code -- which at the time wasn't released. Now MPE/iX source is in the hands of seven companies. One recently reported they'd used their source to create workarounds for support customers -- just the limit HP hoped for the use of its MPE/iX source.
I wrote in 2008
It's a mystery how HP can give any significant use of MPE/iX to third parties in the years after the vendor won't offer services for the 3000 community. A third party owns nothing under these rules, but should build a business model and employ experts on this basis? Risky business, that.
A third party will just have to hope to rely on access to MPE/iX source. And nothing else but hope. In any contract no better than a typical customer's, a support firm would own nothing but that Right To Use what HP owns. Support for the third party support supplier for MPE/iX from HP? Shut down, by 2010. Support suppliers could consider that deal a sketchy foundation to build a business upon.
The 3000 community can only hope that's not HP's intention for support providers: To make any alternative support for the 3000 community remain sketchy. HP retains its ownership, but the intention of this 2005 announcement was to "help partners" do support business. Here's that HP 2005 statement, as a reminder of Hewlett-Packard's intentions.
"When HP no longer offers services to address basic support needs of e3000 customers, HP intends to offer to license HP e3000 MPE/iX source code to one or more third parties — if partner interest exists at that time — to help partners meet the basic support needs of the remaining e3000 customers and partners."
You generate partner interest with customer purchases, now that HP's made hardware emulation legal. Then you step out of the way and let licenses evolve. For the disciples, the back half of that resurrection is a revelation they must arrange on their own.
March 25, 2013
Searching for help in all the right places
Today a long-time 3000 site in the candy business called to find out if anybody was available to help with a little contract work. Maybe about two or three years' worth, because that's how long it would take this 3000 stalwart to pull out of their existing 3000 applications.
They've already pulled out of some. Oracle Financials now takes the place of an MPE/iX app, for example. But while Oracle is more popular with the market's experts, the in-house software that it replaced performed better.
The search for 3000 expertise led us to recommend a couple of favorite webpages. The OpenMPE contractor-consultant page has added new consultants in the last few weeks. Over at LinkedIn, the HP 3000 Community is fast approaching 600 members. And while LinkedIn would like the employer prospects such as our candy company -- and its Call Center, Order Entry, Order Fulfillment and Sales Audit apps, all running on N-Class servers -- to pay $295 to list a job opening, it's not needed. You can start a discussion in several places for free about an available job.
Three months ago we dipped our line in the water to attract two dozen applicants with 3000 experience in just under 36 hours, using the redoubtable 3000-L mailing list. We heard from long-time consultants, independent contractors, and even 3000 pros who thought their current company's use of MPE/iX looked a little shaky.
LinkedIn will take on any discussion in the 3000 Community group, regardless of whether it mentions jobs or not. It's hard to describe how many of the nearly 600 are available for work there, but it's not a miniscule percentage.
There's also an HP 3000 Jobs subgroup, which is part of Bill & Dave's Excellent Machine out on LinkedIn. Apply for the Bill and Dave's membership (it's free) and the Jobs subgroup is open to your offering and your seeking, too. Bill and Dave's is another 780 members big, and it's got lots of retired HP 3000 expertise in there. You never know who will want to take on an outside contract, after leaving the good ship HP.
March 20, 2013
Emulator connects to terminals, POC efforts
What was restarted as a pilot project more than four years ago at Stromasys is now a full-fledged product. The CHARON-HPA/3000 operations inside Stromasys are receiving continued investment, according to company officials. The emulator is a proof of concept project at several companies who've contacted us, but it's a full-fledged software solution at the vendor which created it.
The software's starting to caper through springtime on laptops and low-cost desktops across North America and elsewhere. One manager who briefed us about the POC work at his site said he put up the A-202 Freeware edition on an HP desktop with an i3 Core Intel chip. The desktop came off eBay with a $150 price tag. The demonstration yielded "a sigh of relief I could hear across the room." Top IT managers are happy to see a way for MPE applications to run onward into the future, independent of HP-built servers.
Installing the emulator software and setting it into service requires an ability to know how to put an IP address into a terminal emulator, in order to connect over a network. Any A-202 freeware users who have limited networking skills are presenting special support needs to Stromasys. The company says it's working in a couple of directions to find a method to help such users in a cost-effective manner.
Stromasys has two versions of the HPA/3000 documentation, one for the A202 Freeware Edition and one for the Demo-to-Production Edition. The company is restructuring these documents to turn them into User Guides, an upgrade from the comprehensive collection of notes available at the moment. Fortunately there are very few issues that only concern Freeware users, so having to spend time supporting freeware users — with advice and instruction that doesn't benefit the vast majority of its customers and prospects — has not been an issue.
Product manager Paul Taffel is at the nexus of this springtime growth. "The momentum is certainly building," he said, "and it really is fulfilling to talk to users who had no hope of finding a solution like CHARON, and to be able to show them such a high-quality product."
The HPA/3000 edition of CHARON will have a fresh release this spring, "and we have also started working on some major enhancements to improve our high-end performance."
Every 3000 manager uses either physical terminals, or a terminal emulators running on a PC (or very rarely on a Mac) to connect to their HP 3000. "This doesn't mean that they're running old-fashioned applications," Taffel said. "It's still the way that everyone who uses an HP3000 connects users to it."
Some sites may use fancy network connections to allow users running PC-based programs to access information stored on the HP 3000, without using a terminal emulator. But pretty much everyone uses software like Reflection or Javelin to open up a terminal emulator window when then need to log on to the system to issue commands or start up programs.
There are very few users still using serially-connected physical terminals (which require a DTC to connect to an HP 3000). Almost everyone who is using Reflection, for example, uses it to connect to their HP 3000 over a local network.
Contrary to our earlier reports, Stromasys believes the HPA/3000 will work with DTCs, although it hopes an enterprising user to try to hook one up and report their findings. And while Alan Yeo has reported that CHARON won't work with DDS tape drives, Stromasys says that's not true.
"My home test system — that $1,300 one — has a DDS-3 drive built in," said Taffel. "Warren Dawson (our first user) built his test system with a tape drive, but then decided against building one into his production system."
VMware can demand some close management in a few cases. When the CHARON Freeware Edition is run inside VMware on a laptop, users normally connect to the virtual HP 3000 machine by running Reflection on the same laptop. Despite the fact that Reflection and CHARON are running on the same physical PC, you connect them to each other using the network. If your laptop is plugged into a wired-network, Windows is provided with an IP address on the network -- and you must configure your virtual HP 3000 to have an address on the same network. When you do this, Reflection can talk to CHARON with no problem.
In VMware, things get much more complicated if your laptop is connected to a network using a wireless adapter. Stromasys has solved the problem of connecting Reflection to CHARON using a laptop connected to a wireless network.
If that laptop isn't connected to any network (wired or wireless), then connecting Reflection to CHARON requires yet another solution. This configuration is also being documented as part of the User Guide.
Freeware users of HPA/3000 are providing opportunities to solve problems such as wireless access points from inside VMware, and document it for the greater good of the 3000 community. Freeware users expect support for their experiments with emulation.
March 07, 2013
Enterprise Failure: Selling to the Consumer
COBOL expert and 3000 veteran Bruce Hobbs shared a story with me this week about selling straight to a product's users. That's the way HP 3000s moved into tens of thousands of companies during the 1980s. Back in those simpler sales days IT directors -- we called 'em DP managers in the day -- did the selecting and purchasing of corporate computer assets.
The sale happened in the office of the head computer honcho. This person was the consumer, if you will, of the product being offered. More than anything, they wanted something that would work and be a joy to use. (Joy being a relative term, considering it was the 1980s and ENQ/ACK was still a big part of what we called datacomm. Not networking, which was an even deeper black art.)
The story Mr. Hobbs shared was from the world of Apple, where a blogger took note of Why Nobody Can Copy Apple. In summary, Apple wants to sell directly to the user of its computing solutions. The mobile arm of this vendor now has a large footprint in corporations because of this. People are Bringing their Own Devices to the office. It's enough of a phenomenon to trigger a recent webinar on the topic from MB Foster.
However, current enterprise computing sales -- the kind that displaced the 3000 -- take place in an office outside of DP Departments (as we used to call them in the '80s). Corporate Purchasing began to buy systems, or the perhaps the selection happened in the Office of CFO. These officers were accountable to the cost of what they purchased, more so than how reliable or flexible or value-driven systems behaved. This is what put Intel PCs and Windows onto so many desks, long after the users curtailed all manner of love for these affordable choices.
This is the kind of technology selection that's gotten developers and IT administrators removed from decisions. Now IT must present its applications as a portfolio of assets, just to win a place at the boardroom table. No vendor cares less about enterprise-driven sales than Apple. And yet somehow the company has made itself a permanent resident in the plans of corporate IT. BYOD proves that consumer sales work.
You don't talk for long about Apple's culture without invoking Steve Jobs these days. It's a lot like the Bill and Dave stories that once cradled any Hewlett-Packard business computing discussions. Jobs had this to say about selling directly to the user of any computing device.
What I love about the consumer market, that I always hated about the enterprise market, is that we come up with a product, we try to tell everybody about it, and every person votes for themselves. They go ‘yes’ or ‘no,’ and if enough of them say ‘yes,’ we get to come to work tomorrow. That’s how it works. It’s really simple.
With the enterprise market, it’s not so simple. The people that use the products don’t decide for themselves, and the people that make those decisions sometimes are confused.
We all have sad memories of 3000-using companies who were hounded away from MPE by confused corporate purchasing departments. In the realm of the most price-driven organization, government, coming in just 8 percent lower in a bidding contest will earn a sale of something less worthy.
So the 3000 can sometimes earn its owner -- the technologist who still tends to it -- unfair emnity. "Our HP 3000 lives on here, to the immense annoyance of all those who do not understand and love it," said one DP Manager who talked to us on background. "I am personally hated because of my association with it, and viewed hereabouts as a dumb cluck with a degree in useless knowledge."
But corporations don't make products great. Consumers do that, especially when they recognize what they need and delight in getting it. Even when it's different, like Apple or the HP 3000. It doesn't take long to get to the passion then, those moments where the consumer uses the word love on an inanimate object.
March 06, 2013
Emulator earns exam for test databases
An HP 3000 manager is exploring the option of using the Stromasys emulator to host archived test databases as well as an inventory of vehicles and parts. If Stromasys could supply its software, the system could emulate an A500 server installed recently to replace a vintage Series 996.
The 32-year veteran of 3000 programming and management said he'd consider it "a rise in my personal stock if I could go to management and say the emulator could replace TurboIMAGE, VPlus and Pascal programs onto Intel hardware and mass storage.
"If that were true, and we could make it happen for $25,000, we might become a Stromasys customer," he said.
Their app tracks reliability and maintainability of vehicles. Reports have been created using Query and a few dozen customized Pascal programs. One portion of the application is still live: several parts and equipment databases for a warehouse operation. "They still have parts coming in and going out," the manager said.
The HP 3000 is also hosting data that's been static for more than three years. "We're required by regulation to have a way to bring it back online, or keep it there," he said. That 3000 archives hundreds of IMAGE databases that haven't been converted to Oracle.
"There's no new development," he said. "We do not have any COBOL, either,"
However, the situation at the testing center could be tailor-made for the emulator. There are virtually no third-party tools or apps to license, and the application that's online runs off basic HP FOS software, with the exception of those HP Pascal reports. Switching to Intel-based MPE can provide hardware security, so long as software licenses don't get in the way.
He convinced his managers to buy a used A500 HP 3000 several years ago, but the computer requires an ongoing maintenance contract and has had its problems over the last year. It would have been easy to make the case for an emulator while that server was experiencing problems, but the solution wasn't released at that time.
Mass storage support has become a lure for an emulator, too. A disk failure in that Series 996 was on a list of items for this manager to resolve. Emulation could tie newer storage into the system.
"I could have an IMAGE database, and Query files. That's incredible."
Third party solutions like the emulator have seen a rise at the center since HP's decline in the 3000 business. While HP provided support, "As we got to know more, and HP got cheaper, the amount of hand holding from them seriously declined," he said.
March 04, 2013
Modern COBOL awaits in migrations
Migrating 3000 sites, as well as prospects, can expect one element to remain the same: COBOL. Unless a company is buying an off-the-shelf application to replace their 3000 suite, COBOL will remain in control even on a platform as novel as Linux. We haven't heard many reports of 3000 sites rewriting from COBOL to anything else, simply to maintain their mission-critical in-house apps. (Ruby, an object oriented programming language, has been stepping in for COBOL at QSS, the K-12 application provider with 3000 customers.) What tips the scales in favor of sticking with COBOL is more than a developer's comfort with the language. Relaxed formatting and structure are hallmarks of any modern COBOL.
Is sticking with COBOL in 2013 a sound choice? To be sure, many 3000 users wouldn't choose COBOL for a brand-new app. Many are developing in other environments (Visual Studio) on what we call surround platforms. The key data remains on a 3000 for now, feeding those other-apps.
But COBOL has changed a great deal, and for the better, if you decide to move away from HP's COBOL II. The language once had a reputation of being verbose. Okay, that hasn't changed. But COBOL in updated flavors has dropped all the fixed A/B margin formatting, uppercase-only text and rigid division-section structure that was still in place when HP left the languages business.
COBOL supporters in your community still like to talk about how readable and maintainable COBOL still is, even in the face of the brace-and-bracket languages world. George Willis of investment house Fayez Sarofim migrated the MPE applications using AMXW, "so that we could 'lift and shift' our COBOL and Powerhouse code with somewhat minimal changes." The company chose HP's Unix as its platform last year, but AMXW works with Windows and Linux, too.
The exception to COBOL is FORTRAN in the 3000 world. MANMAN relies upon FORTRAN for its MRP work, and many a manufacturing site has coded in customizations using FORTRAN. But outside of the manufacturing base, COBOL rules the past as well as the future.
The advantage to starting with a clean slate for a mission-critical application: you choose whatever language fits best. But 3000 sites don't get a clean-slate restart, since the data is always of legacy vintage. You wouldn't write a mobile application in COBOL. But when you consider the tasks 3000 apps perform -- rely on transactions, used record-structured data, handle heavy loads -- COBOL still fits well.
A white paper from Creative Intellect Consulting says that "COBOL's past shortcomings don't compromise its appropriateness for the future." That is only true, however, if a modern COBOL is waiting on the other side of a migration. Everything is more modern than COBOL II, and right at the end of HP's 3000 futures one company modernized COBOL II. The suite that emerged was called AcuCOBOL-GT.
Acucorp released the product as a revamp of MPE/iX COBOL, but it emerged within a few months of HP's 2001 exit announcement. Now AcuCOBOL-GT has been absorbed by Micro Focus, whose Visual COBOL 2.1 is still adding more compatibility for AcuCOBOL. Some companies that made the jump to things like AMXW embraced AcuCOBOL as part of their move.
There are still macro issues to resolve, for the companies which employed them in their 3000 applications. Consultant Michael Anderson of J3k Solutions reports that the way he handled macros in COBOL II while moving to HP-UX is "to compile the original source on MPE, and then use the listfile as the new source code for HP-UX-based AcuCOBOL or Micro Focus COBOL. Then do some cutting and pasting into new copy books (COPYLIBs) on the HP-UX server."
Visual Studio, probably the most widely adopted development environment for companies that rewrote code to .NET, is supported by the Micro Focus product. That support lets customers edit, compile and debug using Visual Studio 2012 or 2010. This COBOL support isn't widely known, if you're examining Visual Studio from the world of Windows. Support for Visual Basic, Visual C#, Visual C++ is built in to the free "Express" versions of Visual Studio. But if your frame of reference for development is COBOL rather than Windows, you'll know that going Visual doesn't mean leaving COBOL behind.
MicroFocus doesn't own all of the modern COBOL choices. There's COBOL-IT, a commercialization of the OpenCOBOL open source code. COBOL-IT has been built by former Acucorp managers, using the same model that's worked in other open source advances: improve upon features without erasing compatibility, then add professional-level support. As recently as two years ago, Speedware (now Fresche Legacy) was promoting the use of COBOL-IT in migrated environments. Fresche is now working closely with Micro Focus, too.
There's also Fujitsu's NetCOBOL, which includes support for .NET as well as Windows' Visual tools. There's a difference in pricing as well as reach between Fujitsu and Micro Focus. NetCOBOL supports Linux and Solaris along with Windows, and it doesn't use a runtime pricing model. The Micro Focus tools -- and there are a mighty raft of them, considering the company aquired Borland, too -- run everywhere. (Well, maybe not under MPE. But there's that Acucorp heritage inside the software, after all.)
Proven success keeps COBOL running much of the world's business computing, more than 50 years after the language was invented. It's hard to refuse something that's worked for this long -- if its community keeps reinventing it. If your IT efforts include care for languages and programs, like so many do, then caring about your next COBOL should be an issue to investigate.
February 27, 2013
Some version management required
Like the old saying of "some assembly required," the more current demands of application development will require version management, at the least, for 3000-bred apps. They are mission-critical programs, and we've not heard terrific reports about off the shelf replacements for 3000s during a migration. It's possible and has been accomplished, but many more stories are in our files concerning existing code, working on a new platform.
If you're moving code away from a 3000 to another platform, some version management is the minimum you will require. More likely, the solution will integrate a compiler suite with Windows Studio tools. There's something on the market called COBOL Studio from ATX II Tecnologias de Software, S.A. More familiar targets would include the Visual COBOL for Visual Studio, from Micro Focus.
What does it look like when a 3000 is doing more beyond a good programmer's editor? Perhaps like the story that Walter Murray -- who moved from HP's languages lab to a job managing 3000s for the California Corrections System -- shared with us.
For version management, I use HP SRC. I have one master library and one person responsible for keeping it in sync with what's in production. We archive not only the source, but also the compiler listing, object file, and executable, each time a new version is migrated to production. We also archive job streams, UDCs, tables, and so on. We have separate libraries for personal use and projects.
That last part might be just as important as any other Murray mentioned. Good developers have a yen for creating programs, and the ones you'll want to attract will have personal projects. The most broad minded companies set aside time for the code creators to work on these projects.
You never know when some personal coding will yield a breakthrough that can be applied to a mission-critical roadblock. But without management for version changes, the chain of succession for a development team is much weaker.
Murray had other recommendations for the coders who will stay on the 3000 to homestead. (After all, SRC is an MPE/iX tool.) He likes to use Quad, but notes that
the only bothersome limitations with Quad are that it doesn't handle files with variable length records (of which we have very few any more) and the search is case-sensitive (which leads us to avoid lower case in COBOL source code except for comments).
For debugging, I use XDB (HP Symbolic Debugger/iX). It's well worth the time spent learning to use it, even if it's not as good as HP Toolset as a symbolic debugger for COBOL.
February 26, 2013
All Star year may be on horizon for 3000s
This is the story of two Tims, one who you may know and one you probably don't. But they have something in common. Tim Duncan and Tim O'Neill have enjoyed success over long careers with underrated groups. They're both seeking additional years providing their fundamentals at a great value. And they're both optimistic about unsung but praiseworthy futures.
Tim Duncan is a man with fans. The two-time MVP for the San Antonio Spurs is called the Big Fundamental in his basketball career. This Tim can be easy to overlook at awards time in the NBA, because his game is based on superior execution of the fundamentals. Passing. Blocking shots. Rebounding. Scoring. All without flash to call attention to his efforts. He makes success, selflessly.
Tim O'Neill makes his first appearance in public in this month's printed Newswire. He's been managing HP 3000s since the system was only seven years old. He came to his work by way of a career in math and statistics. He is reaching out for more years for his 3000 by way of the new emulator. His organization, a test facility for the US military, has sustained itself using only the fundamentals: IMAGE, VPlus, Query, plus some HP Pascal.
Both Tims are looking for extra years in what they do well. Making memorable minutes on the court. Making MPE do its work quietly, providing the best value.
Like the HP 3000, Duncan's Spurs are being overlooked. They lack the youthful dazzle of teams from LA or even Oklahoma City. But like the 3000, it's a group he leads that's been elite for an extraordinary period. Duncan's Spurs will earn a playoff spot this year for the 16th straight season. There's been nothing like it in sports, not even the New York Yankees. But alas, unheralded today.
O'Neill wants to extend the value of his expertise, like Duncan. His systems run without software problems, thanks to the fundamentals of MPE. He'd like to keep running that environment without a need for HP-built hardware. The ability of the emulator to lift MPE into Intel hardware? "Incredible," he said while he learned about its particulars.
The ability of a 36-year-old power forward to stay among NBA leaders in blocking shots, rebounding, making points and minutes happen? Some might say incredible, but they'd probably have to live in Texas. In the wider consciousness of the basketball world, his team and effort are considered old.
But as all of us in this community get older, we believe there's no fundamental flaw in being old. A friend and former Newswire columnist, Scott Hirsh, is working for Dell this year, after providing mass storage savvy with a half-dozen other vendors. Before that, Scott was the SYSMAN Special Interest Group leader. He says with humility, "These days I'm usually the oldest one in the room" when companies seek their tech futures. "I used to be one of the youngest."
At the same time that the HP 3000 is considered one of the oldest servers in the datacenter's room, it is gaining one of the younger technologies in the enterprise. The 3000 hardware has been virtualized. And as anyone who's had hardware dropped by a vendor knows, virtualization can extend the months and years of service for a server environment. Digital's servers got this virtualization during the past decade. Virtualized servers are among the bedrock elements in a modern IT architecture.
At Tim Duncan's workplace, the extra pass to the open shooter becomes a bedrock element. On the Spurs' end of the court, a team effort makes for what the experts will admit is basketball the way it was built to be played. No single player needs to overwhelm an opponent. The Spurs practice a "good to great" habit in delivering the ball to a shooter. What they all covet isn't stardom. It's winning.
At Tim O'Neill's workplace, simple and elegant designs that have served for three decades are at the bedrock of tests and tracking. The subjects are military vehicles, the fundamentals of modern defense. All he wants to do is keep MPE working. He says any hardware that keeps his environment winning will get the job done.
You don't find many customers who can tease apart the 3000 success to say that it's the software that made the system a winner. But like "good to great," the software that represents the 3000's fundamentals makes a winner.
This month Tim Duncan earned a spot on the NBA All Star team. He was overlooked for the award in 2012 for the first time. "I thought those days were over for me," he said this year, a reasonable belief at age 36.
In the same way, many IT architects think that MPE's days as a fundamental are over. Tim O'Neill thinks otherwise. He's not ready to put in a purchase request yet for the emulator, even while it sounds incredible. But if he does, his procurement department will have it easier in one respect than when it bought 3000 service recently. They need to take the low bidder. There's nobody who can virtualize 3000 hardware other than Stromasys.
It will be a marvel to watch a 30-year-old application take its place on the IT court of today, on an emulator. Much like a marvel of watching Duncan pass the ball the length of the court, like a touchdown pass to the end zone in football. There's nobody else in the game who can make that play turn into points more often.
In a few more months we'll know if Duncan can repeat his championship success. He already has four titles, an elite number in the NBA. But if his Spurs sustain their "Drive for Five," he will be the player with the greatest number of seasons between first championship (1999) and the last.
Watching a fundamental All Star regain elite status is fun. It's the kind of game that makes being a Spurs fan, or a 3000 reporter, such an incredible experience during 2013.
February 22, 2013
Where You Can Check for 6 and 7.x
All 3000 customers have MPE/iX installed, but the operating environment comes in three flavors. In the homesteading world of 2013, two of those three will need to be served up by your community's comrades.
Last week 3000 manager John Watson -- one who says he worked for HP for awhile -- asked around to see who had a copy of MPE/iX. He was after a version 6.x or 7.x. If that request was for a 7.5 release, it's easy to obtain. In fact, the Stromasys freeware HPA/3000 emulator can be downloaded with a 7.5 MPE/iX included. No subsystem software, of course.
But the earlier MPE/iX versions? Ask your neighbors, because there's no official way to get that software. Pivital Solutions' Steve Suraci, whose company was among the very last to be an official HP 3000 reseller, confirmed the comrade-swap situation. Pivital continues to support 3000 sites, as its primary business. But that won't make the earlier MPEs any more available, by the book.
"HP has made no provisions for this situation that I am aware of," he said. "My guess is that this customer will easily come across what he is looking for. But we would not be able to legally provide it to him."
Resolving this problem is not as simple as moving up to 7.5 from other releases, for reasons that anyone managing a 3000 would know well.HP built the 6.5 release to accomodate Large Files features that were needed by Amisys/3000 healthcare customers. The 7.0 release included support for the new PCI IO bus. These releases tend to have been frozen in place around the homesteading community. Customers are loathe to change these, because things remain stable if they do not.
You've got to be careful about which MPE/iX SLT you use from another system, too. "I just recently got a 939," said Watson, "but the SLT tapes I have from 2006 have been cut from a different model. I think patch MPEMX90 should have been applied before cutting the tape."
Without the patch, his 3000 "just hangs a little about you try start norecovery," he said.
Problem? What problem? When the community decides HP is done with the 3000, it can share what's needed. And nobody needs to know who has helped.
February 15, 2013
3000 pro uses open source version control
We've been polling the 3000 community about its choices for development tools, but the range runs wider than QUAD or versions of Notepad. One enterprising veteran has tapped the free, open source toolset git to create a batch transfer system for EDI.
The git solution is one of those software choices that seems to defy the traditional structures for care and feeding of software. Like the Joomla Content Management System, git is supported by a vast range of users, comes free of charge for any Windows, Unix or Linux-based workstation or server, and is used by very large companies as well as untold thousands of smaller ones.
One 3000 IT pro, James Byrne of the trading specialist and freight forwarder Harte & Lyne Ltd., checked in to report how git is helping him manage the development of new modules which connect to newer enterprise environments. The git techology supports Behavior Driven Developments. BDD provides developers and business analysts with shared tools and a shared process to collaborate on software development.
Last year I had to create an EDI batch transfer system from one of our suppliers into our billing system hosted on the HP 3000 and written in PowerHouse. For that project I created a git repository for the HP on our source archives' Linux host, and then transferred over all of our source code, job files, udc and cmd files -- and anything else I believed to be locally developed source -- into the git repository using the HP 3000s HFS layout.
I then checked out the specific directories and files into a working directory on my Linux workstation, wrote the new stuff and edited the old stuff in GVim, and checked everything back into the remote repository.
Byrne said he then FTP’ed the new stuff onto the HP 3000 and ran it. "If there were any bugs -- and when are there not? -- I edited the source on the workstation, checked it in to the repository, and FTP transferred it from there to the HP 3000 for the next iteration."
It seeems to me that written out it appears more cumbersome than it actually is. It all went fairly smoothly once most of the gotchas and ‘oops-I didn’t-know-that’ were gradually uncovered and weeded out the the workflow.
One of the major benefits of doing things this way was that everything was built using BDD methodology and the new systems is covered by reproducable tests. Recently a change occured external to our system that broke one of the transfer scripts. We were able to identify the exact problem in our code and fix it with remarkably little effort in an amazingly short time, all because the test suite identified exactly where the exception was occuring and in what way the new behaviour varied from what was expected.
Byrne said the next thing he expects to be writing for, if not actually on, the HP 3000 is a set of Quiz reports to extract the company's 3000 database data into XML files, for transfer and loading into a new billing system. "After that is done," he said, "it seems very likely that then we will bid adieu to our old workhorse."
January 28, 2013
Five years after, which environments died?
Five years ago this month, the OpenMPE volunteer group was running another slate of directors for its election. Micro Focus had assimilated Acucorp in its mission to become all things COBOL to all platforms' users. The Greater Houston RUG was releasing details for its 2008 conference, one that would feature Alfredo Rego as keynote speaker. At HP, its 3000 lab savants were starting up their final year of development of patches.
Meanwhile, Windows XP users were lobbying Microsoft to save their OS from extinction. An InfoWorld article reported that a group of users had launched a petition.
With Microsoft saying it will stop both OEM and shrink-wrapped sales of the OS come June 30, the clock is ticking. But we know lots of you want to keep XP alive, to not be forced to upgrade to the less-than-stellar Vista. Millions of us have grown comfortable with XP and don't see a need to change to Vista. It's like having a comfortable apartment, one that you've enjoyed coming home to for years, only to get an eviction notice.
Windows XP just dropped below a 40 percent market share last month, according to Net Applications. That firm uses signatures from Web browsers to calculate these figures. Windows XP patches are still available for free. So are patches for MPE/iX. XP has not changed any more than the 3000's OS during these five years — so they have that in common, too.
But obtaining your free MPE/iX patches might take quite a bit of waiting on hold with the HP Response Center now, five years after HP stopped creating the patches. In a bit of special handling, MPE/iX users got a free pass, literally, on patching, a savings that users of HP's Unix, VMS and NonStop do not get. It's just that acquiring the patches means explaining you want a patch to an enterprise server, not an HP printer.Five years is a long time in the computing business. It's such a long time that the competitors in the enterprise sector now consider cloud computing their best bet to grow a customer base. It's a strategy that didn't even exist in early 2008.
The wait time for seeing enterprise server growth feels like the kind of endurance required to extract MPE patches directly from HP.
"Right now I am on hold with the HPRC, trying to find any existing security patches for MPE/iX 7.5," a 3000 manager told us last week via email. He didn't succeed, ultimately, after more than an hour. It's a good bet that an independent 3000 support company would get whatever patches are needed. There's not that many, compared to the number of patches for XP, or even Windows.
But just like those users of XP, the customers still relying on MPE/iX will not be deterred by a vendor's newer products. The complaints of 2008 were about Windows Vista, and from the looks of them they appear to be spot-on, in a historical review. This year the complaints from these "homesteading" XP users are about Windows 8 -- although Windows 7 has finally gained the largest share of desktop server market.
Put another way, it took Windows XP about five years after Microsoft announced it would stop sales of the OS to cede its No. 1 ranking as the world's most-installed OS version. The same five years have seen the departure of OpenMPE elections, the elimination of RUG groups of all sorts, lab experts from HP's MPE group working at indie software companies, and Micro Focus turning toward the homesteading 3000 sites as a source of new customers.
There are enough prospective 3000 sites out there to encourage a company the size of Micro Focus to pursue them in a North American campaign. It takes a long time to exterminate a user base completely. There are ways to try to do it quickly, like Hewlett-Packard did more than a decade ago. But pushing toward commodity solutions when older ones are working is like extreme pest control. You can release poison gas in the house to get rid of rats, but something that severe harms the existing business, too.
Microsoft never tried to eradicate its XP users this way. But HP performed this on MPE, and now the company's feeling the effects of poison gas over its enterprise practices, with the proprietary legacy profits and growth all but dead. MPE/iX never had a majority of HP's OS business like XP did at Microsoft. It just pattered along on quiet feet doing things like recording tests of military vehicles, a software system still in use today in the US, we've learned.
The manager at that site said today that "I like the idea of keeping MPE alive, even if I don't have a 3000 to run it on." He's got a test archive and a 3000, but would prefer to use modern hardware along with an OS that HP last patched in 2008. He has a sound idea: it's the environment and the software that make a customer stand fast, whether it's MPE or XP.
An emulator probably won't make the 3000 market pick up new customers. A modern development suite can aid in growing new applications. However, if growth in your organization isn't as keen a mandate as stability is, it's feasible to take refuge in a technology designed to cradle MPE and keep it alive.
January 25, 2013
Raise your stock, maybe, with emulation
You might not have any COBOL running at your 3000 installation. We just heard from a customer who was in this unique position, this week. He is also a candidate to let the Stromasys emulator take over for his 3000 iron -- even at the regular production-grade emulator price of $25,000.
We haven't seen much of this yet. Most of the inquiries are "will it run?" or "how can I get it for less?" or "what promise do I have my software can be licensed on it?" That last one is the least predictable, unless you have your own application in-house, and use only MPE utilities from third parties. No problems there.
Apparently in that in-house situation, a Maryland IT manager asked me if it's feasible to let the emulator make him a hero, by raising his stock in his career at his company.
The transfer from PA-RISC HP systems to Intel-based hardware -- of Pascal programs -- would do the job to get to heroic reality.
Do you realize how much my personal stock would rise if I could go to management and say this?
"Our existing legacy TurboIMAGE data bases on the HP 3000 and the code that runs them (a few Pascal programs that drive VPlus for entry, a few more Pascal programs, and a few Query files that generate reports) can be replaced by Intel hardware and mass storage."
If the above statement (in quotes) were true, and we could make it happen for $25K, we might become a Stromasys customer.
Is it realistic?
We'll see once we interview him and learn about licensing. But with a budget ready, in-house code at hand, and nothing but standard MPE/iX FOS software, there shouldn't be a problem here. This may be a way to get a stock rise -- something Apple would love to see happen pretty soon. Personal stock is easier to lift than the corporate securities. Switching to Intel-based MPE provides security, so long as the software licenses don't get in the way.
January 23, 2013
Developer tools for 3000 redux, not re-dos
We asked 3000 veterans what they're using while they do development in the MPE environment. Several steady and stable solutions emerged, over and over. Like a lot of life in the 3000 world, there's a lack of surprises that contributes to higher productivity. Just because there are more elaborate developer tools on migration platforms doesn't mean that the MPE tools don't serve 3000-caliber needs.
For example, Tracy Johnson of Measurement Specialties uses three editors to maintain and develop on the 3000.
I'll use whatever editor suits my need for the moment. Qedit lets me edit a file that someone else may want to open at the same time. (I only need single user access when I need to do a KEEP.) Especially those pesky SECURCON or STREAMX config files that something else may open for less than a second. Saves me the extra step of having to make a copy then edit the copy. Then their full screen feature lets me use the arrow keys.
Quad has those convenient WHITEN and DEBLANK commands. The faux full screen seems easier for one-key page flipping than Qedit's real full screen.
EDITOR has LENGTH and RIGHT commands if I need to change the record width. Also, it is my editor of choice for mass changes with MPEX's hooked EDITCHG command.
Consultant Roy Brown of Kelmscott Ltd, describing himself as a hired gun, says "I'll use whatever the client possesses. Basic FOS tools, at a pinch -- Query, FCOPY, KSAMUTIL, etc." But he recognizes the better, third party favorites and wants to use them whenever possible.
I'll take MPEX, QEdit and Suprtool if I can get them. Quad rather than EDITOR at another pinch. I carry a file that, executed in Quad, sets the userkeys for me.
I also carry Reflection, and hope that the HP 3000 end of that will be on the client's machine.
But these days, I like, where permitted, to copy all the source to my Windows PC and work on it with UltraEdit and UltraCompare. The productivity boost is amazing.
Brown likes to sign his emails with the William Morris quote, "Have nothing in your houses that you do not know to be useful, or believe to be beautiful."
January 18, 2013
Bridges to Cross Before Useful Emulation
It's been a month since the community got its hands on a freeware version of the Stromasys emulator. Some reports from these freeware testers have emerged. But the next installment of this saga comes from more installations and software license agreements. An MPE license is in place, but the subsystems such as COBOL II are not covered. More bridges lie ahead for this software to bring some homestead systems back to the future.
One example reported to me came from a manager of healthcare 3000s, all doing work with customized code in a healthy-sized datacenter. The company hears the clock ticking on the life of their MPE commitment. The veteran manager there, already experienced in the consulting world, says some more time needs to elapse with success stories and production testing before his employer would consider HPA/3000 as a new path toward some extra years on the 3000.
He approached the freeware release with gusto. I heard from him more than two weeks before the pre-Christmas unveiling of the A-202 version, crafted to two users only and licensed for non-commercial use -- unless you're evaluating it for production purchase. "I downloaded the emulator as fast as I could the Monday that it became available," he said two weeks ago.
I've been playing with it since, and am currently looking for a new (to me) computer to host it. My current computer is an Intel i3 Core with 6GB of memory. The emulator runs fine on it, but I'd like to find a computer that I can dedicate to the emulator, so that I can have my desktop PC back.
So far I'm happy with what I've seen and have run into only one issue. That being, accessing a remote tape drive. I'll get back to that issue later and gather more info, because I'm not sure of the cause.
I hope to get a copy for my customer so that we can demo it, and hopefully get them to buy a license. But we've got a ways to go before that happens.
Indeed, one vendor of software for the 3000, who's also helping companies migrate, said he's still concerned about protecting his products in a HPSUSAN license strategy that revolves around a USB key. It's a design that is just one removal of a thumb drive away from stopping a production machine, although Stromasys could replace that key in a matter of days, or maybe even hours.
The issues with licensing third party software remain untested, although Robert Dawson in Australia got Cognos software and some other packages transferred without incident. He left his reseller of Cognos to do the finagling. There's plenty of software tool support from the likes of Robelle, Minisoft and more, but application vendors are still in the process of letting their emulator policies be known.
In case the replacement of non-MPE versions of things like healthcare software doesn't go as smoothly as planned, there is an important place for HPA/3000, even in migrating shops. But while an emulator's lifespan is measured in decades, there are only fewer 3000s running as the calendar pages of 2013 flip away.
It needs more than technology success. Out front and obvious commitments from app companies in the 3000 space; controlling virtual disk behavior that might let multiple copies of software run at the same time (a concern voiced by two veteran MPE companies); file transfer that needed to be addressed by a tool from indie software consultant Keven Miller of Ranger 3K; a lack of testimony in regard to scaling the solution -- there is much to document and announce about this invention in order to give it wings in 2013.
We hope there's good information on all this coming out to retain 3000s in production status, using the emulator. The alternative is a freeware hobbyist tool or a clandestine consulting solution (2-user, 948 horsepower 3000s would do nicely for consultants). Not the destiny for something built to carry MPE over the bridges to the future, however.
January 14, 2013
Could migrations be sparked by fresher development environments?
In a recent poll I conducted about the tools of the 3000 developer, I found a lot of classics. Finding classics at work is common among the 3000 community. And just because technology is steeped in legacy doesn't make it a fool's tool. Micro Focus likes to tell customers who are using its COBOL and development environment software, "Just because it's old doesn't mean it's not gold."
However, nearly all of the three dozen veteran coders -- architects, designers, maintainers and more -- use something first released in 1980s. And only one who replied to our December poll mentioned any change management or version control software as part of coding and creating for MPE. Perhaps everybody works with code they created, on a small team --perhaps as slim as just themselves.
So when these experts said their software toolset runs to Qedit, QUAD, EDITOR/3000, MPEX, Suprtool -- or in one gruesome report, the bare-bones vi -- we assume they're using what they grew up getting adept with. Success breeds habits, and then practices. It's a good strategy for decades if nothing much changes. But when a corporation acquires other companies and IT environments, it eventually gets a datacenter architecture too big for a few favorite tools and nothing else. These kinds of companies and corporations are on the path to migrations away from the 3000. What they'll use to create systems on the new boxes will be designed to embrace change while it feeds multiple-platform developer teams.
The question is, can these advanced and high-productivity tools ever push a maybe-migrator across to engaged status? Put another way, can the likes of Visual Studio, Eclipse, or InDesign sell a company on Windows PCs, Linux enterprise servers or networks of iMacs? Can a toolset lead a company to modernize its enterprise environment? Perhaps it can, when you consider what IDEs yield: application software, the element that's supposed to trigger all enteprise platform decisions.
There's a nifty IDE primer online at the Mashable website, but it's more of a way of understanding what types of IDEs are out there. It admits it's only a sampler of everything available for enterprise developers.One long-time 3000 vendor, now in heavy engagement with migrators, calls this strategy "offering a great set of tires to try to sell a car." Better development tools are more than just very good tires, though. A better analogy might be smartphones. Apple wants your iPhone purchase, and they lure you with App Store gems. Google wants to sell Android phones, and their hook is the superior contact, syncing and mapping tools built into that phone OS.
Many 3000 companies who are left using the server rely on bulletproof solutions, running at a cost they can justify. Something more than the loss of HP-branded support, or worries about parts supply chains, will have to be at work to get them to migrate. Newer tools might not be enough by themselves. But there's always the skills of newer developers, the kind a company must hire eventually when veterans retire or depart. Younger development teams will expect collaboration and coordination. The 3000 experts are so good at this they don't seem to need an integrated development environment.
In the 3000 world, among those who are not yet migrated, there's no apology about using the battle-tested favorites. "I designed on paper and pencil -- still do, but have added Visio for the diagrams," said the community's security expert Art Bahrs. "Then I used editors on my PC and uploaded the code, compiled/ran/said proper incantations, and debugged on the PC. I repeated the cycle until done."
Chuck Trites, an independent consultant and developer, said "I still use EDITOR, and have used Quad and others too. I also use Ultra Edit, which is nice for large files and large rec sizes. Still doing FORTRAN and COBOL. I use MPEX and Suprtool and a few other gadgets."
Other 3000 sites have a simpler answer about what to use to develop. "Contractors," said Tracy Johnson, a former OpenMPE director who works on the IT staff of Measurement Specialties. Perhaps that means that the tools that a contractor brings along are the spark for any changes and modernizations.
At one point, Acucorp offered a COBOL development environment that hooked up with ScreenJet and Eloquence, all in the service of speeding up modernizations. Acucorp developed a 3000-aware COBOL, just about the time HP was announcing its end-game in the 3000 business. Then Acucorp got acquired by -- wait for it -- Micro Focus. It sells Visual COBOL for Visual Studio 2010. Mike Howard, whose Unicon Conversion Technologies is one of the companies who have made 3000 migrations across to .NET, testifies about Visual COBOL. He calls it the fountain of youth for legacy COBOL shops.
A supplier of COBOL solutions tries to make its developers more powerful and aware as they stick to an olden, golden language. Micro Focus is nearly the only game in the COBOL community by now, aside from Fujitsu. If the language remains constant but expanding across vendors, then the differences might lie in IDE feature sets.
January 11, 2013
What If: Fault lay not in the 3000, but in HP?
In the early years of my HP reporting career, the company tried to sell PCs against IBM. It had innovative technology in touchscreen HP 150s with strong links to enterprise office software via those PCs. HP's ad slogan began with an invitation to a customer to imagine something more connected to the customer than IBM: "What If?"
It's a good question today, nearly 30 years later, especially when used to evaluate HP 3000s. HP lopped off its futures with the server in 2001, less than a year before it attacked the PC market by purchasing Compaq. Some products had to go, if HP hoped to convince institutional shareholders that a $25 billion acquisition was good business.
So the 3000 was derided and deprecated by HP. The server had a failing ecosystem. Customers wanted other HP products, like PCs for businesses, running Windows. Over a few more years, HP acquired even more love of outside products. It changed itself as a company, while it fled from the challenge of asking customers what if about its unique technology like the HP 150. Now there are calls for HP to return to the company that it was before it became a consumer-obsessed, low-touch customer service juggernaut that's careened into a financial ditch.
What if the fault lay not in the HP 3000's starry design, but in HP's leaders themselves? When Steve Jobs takes a walk through the neighborhood of Palo Alto to counsel an ousted CEO of HP, you can be pretty sure that a great deal had changed for HP, and none of it for the better. And that walk took place more than two years ago. Jobs believed that Mark Hurd should've never left HP.
That's how completely Hewlett-Packard had faulted from its enterprise line. A leader who slashed R&D, and rubber-stamped even more pell-mell pursuit of the consumerist strategy, was now the bulwark. Proof enough HP had changed completely, and offered in a story this week from the Apple community.If the HP 3000 were a sound product -- and it has been HP that's grown unsound since that 2001 Fall of the Compaq and MPE disasters -- perhaps we can hear a "What If" about the indelible value in the 3000 concept. A computer whose intellectual property, from silicon to software, is controlled by its creator. A system built on the use-it-forever designs of PA-RISC, rather than the churn of commodity systems.
Today I interviewed a former 3000 manager at Dayton T. Brown, the largest and most thoroughly equipped independent engineering and testing laboratory in the U.S. They purchased a Series 917 and a Series 937 in 1994. They stopped using them completely in 2007. That's 13 years at a major US business running on servers built to last. By way of contrast, that was a typical kind of enterprise product. When Dayton T. Brown bought their 9x7 systems in the early 1990s, only HP's printers were commodity items driving enterprise IT.
In the Apple world, this lifespan is the equivalent of desktops from 2003 still running the largest printer and mailing house in Austin. iMacs from a decade ago are still on the job in shipping, planning, even design at Touchpoint. Apple controls all of that intellectual property in those Macs, just as HP once did with the 3000.
The story circling in the 3000 community this week about Steve Jobs has him imploring Mark Hurd to return to HP. Hewlett-Packard was an essential part of the Silicon Valley ecosystem. Losing another CEO -- Carly Fiorina had left five years earlier -- was going to be bad for HP. MacRumors reports that Bloomberg Businessweek is telling this story about that fear of HP's faults.
Three days after he’d resigned as CEO under pressure from the company’s board of directors, Hurd received an e-mail from Steve Jobs. The Apple founder wanted to know if Hurd needed someone to talk to.
Hurd met Jobs at his home in Palo Alto, according to people who know both men but did not wish to be identified, compromising a personal confidence. The pair spent more than two hours together, Jobs taking Hurd on his customary walk around the tree-lined neighborhood. At numerous points during their conversation, Jobs pleaded with Hurd to do whatever it took to set things right with the board so that Hurd could return. Jobs even offered to write a letter to HP’s directors and to call them up one by one.
The BusinessWeek article takes a look at how HP fell from its dominating position in tech. and if new CEO Meg Whitman can pull it out of the ditch. She's hearing many analysts say a split of HP -- into what it once was in the 3000 days, and another part of what it became afterward -- is the only way.
What if Hewlett-Packard wasn't right for the HP 3000 anymore, by 2001? The company had let its board fall under the spell of consumerist forces which made printers the primary profit engine. PCs were a natural product to follow a printer, and Compaq owned a dominant part of that market. That's why HP bought them -- to become number one and overtake Dell.
By now, the advice that's become rampant among investors -- the same audience that cheered HP into buying Compaq -- is that enterprise systems like the 3000, or Integrity, will continue to fail when paired with PCs.
And at Dayton T. Brown, no more HP servers run the largest labs in the US. Dell's servers, running Microsoft's Windows, have replaced the Hewlett-Packard products from the old HP Way. If HP wasn't right for the 3000 anymore -- instead of the other way around -- there's hope in a future where the gleaming heart of the system, MPE, can live beyond anything that HP might become over the coming year. As Shakespeare might have told the HP board and braintrust, "The fault, dear Brutus, lies not in the stars, but in ourselves."
January 03, 2013
Panel producer pursues PDF processes
Norbord, an international producer of wood-based panels, runs some of its operations on an HP 3000. This $1 billion company with 13 operating sites around the world needed to create PDFs on its 3000, a task assigned to John Pickering of the company. He went to the 3000 newsgroup for advice on how to do this, working to discover free, online resources already stocked away by indie support companies.
Pickering began by pursuing shareware, which is can sometimes be the budget choice for 3000 shops. (There's a superior and tested PDF-creating solution from Hillary Software, byRequest, which does this for 3000s as well as other enterprise systems.) But if a site wanted to bale together shareware like the txt2pdf software, a manager like Pickering needs Perl to run.
I'd be happy to use the shareware txt2pdf, but I don't know where to begin. The Sanface web site indicates that Perl is required, but that isn't on this 3000, either.
Allegro Consultants, supporting 3000s and crafting MPE software even in 2012, ponied up the Perl that Pickering needed to run txt2pdf.
I've placed TXT2PDF.c version 1.1 from Phil Smith onto my site (It's MPE Software item #13) for those that might want to review it.
It's most likely not as advanced as the Sanface product. Probably need to change its name also.
Finally, Robert Mills reported that while he managed 3000s at Pinnacle Entertainment from 2001 to 2008, txt2pdf version 1.1 never gave him many problems in production use.
I had to increase the size of either the pageObs and/or locations arrays, because some of our reports were causing an abort (think that I doubled the size of them).
We didn't have HP's C compiler, so I downloaded GCC and it worked fine. Also, I had some other utilities that were only available in C source, which also compiled and worked when using GCC.
The Gnu C Compiler (GCC) Mills mentioned is the public domain bootstrap software of the 3000's open source software era. It was first forged in the 1990s by Mark Klein, whose DIS International hosts the compiler's software. The latest versions of GCC and related tools may be downloaded from DIS.
An open document format such as PDF was once locked away from HP 3000s until such open source options appeared. We chronicled the other aspects of PDF techniques for HP 3000 use in a story almost two years ago.
The longer that HP 3000s remain online worldwide, the more these updated features will need to be added to the MPE toolbelt. The community is not shy about sharing its experience, and it seems to be well-stocked in what's needed to use open source solutions.
December 28, 2012
2012 marks 3000 flights of Linux penguins
By Ron Seybold
Third in a series
The year 2012 might have been the first to signal a significant decline in the number of migration projects among the HP 3000 installed base. But for those who were making their transition, Linux was more popular than ever, in either a supporting role to protect HP 3000s, or as host environment.
Add in the 2012 doubts about Oracle's database support for Itanium -- with the attached concern about HP-UX -- and Linux took steps forward to stand as an equal migration target to HP's Unix. In an allied story, since Oracle's technology looked doubtful for HP's Unix futures, other database solutions took a higher profile among 3000 migrators.
Marxmeier Software's Eloquence database 8.20 gained indexing features in 2012 so valuable that the 3000 community members once paid extra for them. With a decline in the availability and future of the '90s-era Omnidex indexing tech, Eloquence's creators added a fast indexing technology, one which its advocates called "like a Google search through your database" in speed. The database has been in 3000 migration toolsets since the earliest days of the transition era, in part because Eloquence applies relational database management for Linux (and HP-UX and Windows) in an IMAGE workalike design.
Migrations in total started to show some significant declines at selected service-providing vendors during 2012. Speedware became Fresche Legacy in the spring of the year, a shift that embraced IBM midrange migrations. The company's president said that the period from the start of 2011 through March of 2012 posted no new 3000 migration projects. Fresche's Chris Koppe said he didn't think the era of migration had ended for the community, while fellow Platinum Migration vendor MB Foster said it was still engaging new 3000 migration business.
The shift in the community's migrations was running down to individual companies, said the Eloquence database creator Michael Marxmeier, after ISV customers finished their transitions. "By now the majority of that migration business is over, and that's okay," said Marxmeier. "ISVs have settled in place; they've probably already moved on. At the beginning they had to come up with a solution to keep their customers successful, and quickly."Linux, grown up from more than a decade of hobbyist work and the zeal of open source devotion, started proving its production worth in 2012. Europ Assistance launched the work to replace its MPE host with a Linux system, right down to considering a Powerhouse license re-purchase for the new environment. Linux comes at a price point for purchase and maintenance which matches MPE better than server-grade Windows or Unix environments.
Even HP had its preferences for Linux hosting over HP-UX. HP's clouds are pretty much a non-starter for existing long-time HP customers. You can't host HP-UX apps in HP's cloud.
HP's Odyssey project wants to bring "hardened" HP-UX features to RedHat Linux, since HP doesn't want to be left out of the Linux currents. While there's a clear five-year future of HP-UX, the years beyond that are less defined. Since companies like Europ Assistance are going to take multiple years to make a migration, few of them want a future shorter than a decade.
More analysts and developers spoke up in 2012 about considering Linux the next, best alternative for the customer who doesn't want to embrace a proprietary Unix. (All of the Unix environments are proprietary, starting with HP's Unix, Sun/Oracle's Solaris, as well as IBM's AIX. Code created for one OS must be revised to work in another.)
These changes, however, loom larger than the strategy of moving from a Unix to one of the Linux distros such as Ubuntu (favored for the 3000 emulator) or RedHat. Marxmeier said this kind of migration wouldn't be painful for an Itanium Unix customer.
Itanium certainly has its users, and it’s hard to tell if it will make it or not. However, this shouldn’t be a concern to the customer. But if they’d like to move to something else, the proven technology of Linux is readily available. About half of our customers are using Linux these days.
Bill Highleyman of the High Availability Journal said the HP Odyssey project, one which aims HP-UX key features at a hardened RedHat, could make Linux an easier choice than HP-UX.
"If Project Odyssey is wildly successful, it may drive a huge competitive advantage for HP," he said. "However, if HP customers embrace the move to highly reliable standard operating systems, HP-UX may be the first to go, since migrating Unix applications to Linux is a reasonable task."
December 20, 2012
What'll you use to code in the New Year?
A few weeks back we began to ask the 3000 community about its tools for development. Companies committed to the platform need to develop, as business opportunities arise, acquisitions close, or efficiencies of scale trigger changes. The answers from the developers using MPE/iX included many well-known tools.
But anything resembling a development environment, with change management or a workbench of testing tools, looked like an unknown in the first phase of our survey. There's code being cut and maintained, but lots of the change management is happening with the ol' noggin, as we suggested in the LinkedIn version of our poll. (Take a minute and tick a box there, to give us all even more data.)
Cortlandt Wilson, an independent consultant and contractor who's aided MANMAN customers for many years, watched the reports of Quad, Qedit, vi, Edit/3000 and more roll across the 3000-L replies. He believes there's more in the developers' toolbox that wasn't being mentioned.
"I wouldn't be surprised if others use some kind of Software Change Management or version control software on their PCs but didn't think to mention it," Wilson said. This is the kind of toolset that coders in the non-3000 worlds take on faith, because there are so many options there.Only one respondent among those who replied on the 3000 mailing list mentioned version control (SCM).
"It's what some software engineers call zero-eth level software engineering," Wilson said. "In other words, a very basic tool.
To give an example of life beyond MPE/iX, Wilson described his current setup.
I'm currently working on a small PC based (non-MPE/iX) project to reconstruct which Excel spreadsheets were updated -- a job that a proper SCM environment would track for us. Small software companies still repeat the same stupid mistakes even though the proper tools are much more ready to hand than they were with MPEiX. In this case, the company already uses an open-source project management system that includes SCM integration, but they won't authorize the time to hook it up.
Wilson added that automating the compile and link process is also part of the SCM process, an element that was mentioned by several respondents.
The potential for development doesn't demand stepping away from COBOL. Micro Focus has been making the case for years that COBOL doesn't make IT antique. Or as the company says, "just because it's old doesn't mean it can't be gold."
December 07, 2012
Attempt at migration preceded emulation
At the newest HPA/3000 Charon emulation site, IT manager Warren Dawson said the decision to keep MPE/iX running was not the first choice for his company in Australia. Migration was a prospective strategy at the organization, but it didn’t pan out for the application.
“We were rewriting our software in a VB and .NET version, but in the end it turned out to be taking too long and being too costly,” Dawson said. “In the meantime we’d tied down the migration of the databases into SQL databases, so that was already running smoothly. Now they use those databases for other applications. We’ve done that migration, but our main system is still the TurboIMAGE/SQL system." A nightly extract through Minisoft's ODBC drivers creates a mirrored version of the database in SQL Server.
Even while the company has eliminated the risk of hardware failures, the challenge of finding replacements for its 3000-savvy talents remains the same. “COBOL programmers here are few and far between,” Dawson said. “In terms of my own job security, it’s cemented that somewhat — great for me, but from the company’s point of view it’s an issue. It will be an issue to get someone to replace the skills in COBOL, because that’s what we mainly use."The parent company of Dawson’s firm has been talking about an adoption of the corporate system, “but that’s at least five years away. So even with a 947 with failing hardware, it was still well worth going with the emulator.”
By making the HPA/3000 solution a keystone in the company, Dawson feels like he’s retained the best part of the 3000 computing experience. “I’ve found that it’s not the hardware that I liked, it’s the operating system.”
Crucial to the process was the support from the creators of the Charon HPA/3000. “I’ve been very pleased with Stromasys themselves, because any issue I raised, they fixed it as fast as they could,” he said. “I was unaware that any of my issues had already been raised, because the way they treated me was that anything I said was important to them, even if they’d heard it before. Not saying they’d already heard it, but saying, 'Tell me about this, and let’s go through it.' ”
"The biggest issue I had which I was asking them about was the security key that’s got to be connected into the host PC. We were planning disaster recovery, but we didn’t have a key to replace that one. They said they’d give us a temporary key we could use for a number of hours. So they’d already addressed that possibility."
Support issues with timezone differences haven’t presented a problem. One key Stromasys engineer bridges the gap between Australia’s workday and the one in the US headquaters, Dawson said. The Stromasys labs include operations in Moscow as well as North Carolina.
December 06, 2012
Software allies smooth path onto emulator
Customers of the HPA/3000 emulator will be watching to see which software companies want to collaborate with Stromasys, to make sure this source of modern, updated MPE/iX servers on Linux iron gets into 3000 shops.
The first HP 3000 manager to take an emulator into production moved the services of very old iron onto a very new MPE/iX platform. IS Manager Warren Dawson’s company was using a Series 947 server which was more than 20 years old to take care of mission-critical operations.
Nearly all of Dawson's third party vendors have come on board and made efforts to ensure their software works. “One was a little slow in doing so, so we made a workaround," he said, "and I made it a permanent workaround. I didn’t know when they would come on board. They came on just before we went live, and we’d already decided to move away from their product.”
In the case of the switch in backup processes, Dawson’s procedures now back up twice as much data, using HP’s standard STORE and RESTORE programs — in less than than when the backup was done using the third party software on the 3000 box.
The change from using HP’s native iron to emulation has also reinvigorated some of Dawson’s MPE software vendors.“I’ve even gotten better support from some of our vendors now that we’re emulating. They see that there’s an extended life in the system, and so a couple of them have made efforts in that regard. We’ve been paying support for years, and for some software we’d hadn’t asked for support in 10 years. They’ve come back to our requests to help us and been very good about it.
One backup software solution didn’t make the transition from 3000 hardware and storage devices to the emulated system. DAT tapes presented an extra effort. Dawson used a utility to copy the tapes to disk, “and for some reason when I did that, it didn’t work properly in the backup software. There was some sort of SCSI issue which was at Stromasys’s end, and they’ve since resolved that issue. But the backup vendor said initially they weren’t supporting the emulator, so we worked something else out.
The Quiz reporting tool from Cognos is part of the software set that’s made the step onto the emulator. The company buys and maintains its Cognos licenses through a reseller, and that partner has handed the relicensing of Quiz onto the emulator. “I haven’t dealt directly with Cognos for a long time,” Dawson said.
Minisoft’s ODBC drivers run on the emulated system, since part of the application’s project is to extract data. Since the databases and the application have been emulated, Dawson’s remains able to use Visual Basic programs, using the ODBC drivers, to do reports as well as updates. However, the complexity of moving toward Windows 7 has raised issues that Minisoft has been helping to solve. Dawson singled out the company as taking extra time to help make the emulation succeed.
“Minisoft’s been the most helpful, because that reporting system started out being the most troublesome. We’ve been having a VB 6 program issue, where those programs ran under Windows XP but are an issue under Windows 7. These programs were written 10 years ago, and the people who wrote them are long since gone. They explained how I could run their software in different ways, with the old driver under VB 6 on XP versus a new driver for .NET on Windows 7.”
Crucial to the process was the support from the creators of the Charon HPA/3000. “I’ve been very pleased with Stromasys themselves, because any issue I raised, they fixed it as fast as they could,” he said. “I was unaware that any of my issues had already been raise, because they way they treated me was that anything I said was important to them, even if they’d heard it before. Not saying they’d already heard it, but saying, “Tell me about this, and let’s go through it.”
The biggest issue I had which I was asking them about was the security key that’s got to be connected into the host PC. We were planning disaster recovery, but we didn’t have a key to replace that one. They said they’d give us a temporary key we could use for a number of hours. They’d already addressed that possibility.”
Support issues with timezone differences haven’t presented a problem. One key Stromasys engineer bridges the gap between Australia’s workday and the one in the US headquaters, Dawson said. The Stromasys labs include operations in Moscow as well as North Carolina.
December 05, 2012
First production emulator wins IT's respect
The first HP 3000 manager to take an emulator into production moved the services of very old iron onto a very new MPE/iX platform. IS Manager Warren Dawson’s company was using a Series 947 server which was more than 20 years old to take care of mission-critical operations. That 3000 had 112 MB of memory. Now it’s working on the HPA/3000 Charon emulator with 2 GB of memory. “We’ve really increased our speed, our memory and our disk,” Dawson said.
“I was testing the emulator over the last 10 months, and I was most impressed with the speed gains,” he said. The gains on month-end processes on the emulated 3000 system slashed the time from almost 10 hours to 65 minutes. “That was phenomenal, and it was on the main database. The guys at Stromasys were very pleased to hear some of the statistics I was churning out. They could emulate, but couldn’t have someone hit it every day, and hit it hard.”
“The users are very happy. They’ve notice their reports are coming up a lot quicker. Instead of 15-20 minutes, in a few minutes it’s done. Performance gains are bigger in some areas than others. The lowest performance gain I’ve found is in backup itself.”Justifying the cost of the emulator became simpler because the HP 3000’s disks kept failing on a regular basis. The HPA/3000 eliminated the difficulty of replacing that type of hardware.
“Because you’re not dealing with physical devices, it’s now made it a lot easier to consider even expanding what we have," Dawson said. "We had a failure of the HP 3000 box every one or two years, and it’s been really hard to source parts here in Australia. The last failure we had was an LDEV 2 disk, and so that became a SCSI disk with an adapter.”
In another instance, an internal cable for a tape drive failed. Parts supply remains an issue throughout the country, Dawson said, since there are few 3000s still running there. But he added that the company searched around the world for that cable. “The best we could get was a two-week wait for it, and we could not wait two weeks for something as critical as that.”
Over the years of moving drives in and out, the cable was pinched and then broken, and “we could not source another cable. We ended up making our own.”
The company has turned off its HP 3000 production machine. “In the end, we had the confidence to do that,” Dawson said. We’ve gone to modern hardware we can get at the drop of a hat, We can almost go into the shop and and saying that one and that one, and one in blue. It removes the need for having specialized spare parts.”
Emulation created a new range of storage space. The company had a project to split its database, due to legal requirements. To do the split, they needed to duplicate the database, and “we wouldn’t have had the space to do that on the Series 947’s disks.”
VMware hosts the virtualized partition where the HP 3000’s emulation resides. “We’ve taken the Stromasys software and moved it to its own VMware environment. It’s by itself, so nothing will impact it there. It’s running really smooth.”
November 28, 2012
As Itanium speeds up, sites fly to Windows
Within the next week, HP's going to ship a new generation of Itanium-based servers. Using the Poulson chipset known as the Itanium 9500, these blade-based systems are going to outperform the current generation of Integrity servers by a factor of 3.29, according to HP.
The engineering gains are impressive. HP tested the new Integrity blades that use the 9500 series against the Itanium 9300-powered servers. Blades start at $6,490 for the 9500-based systems. "For those remaining committed to Itanium and its attendant OS platforms, notably HP-UX, this is unmitigated good news," said Forrester's analyst Richard Fichera. HP's building these new servers exclusively in Singapore, so it can offer three times the computing speed at about the same price.
But even with all that improvement, HP needed to remind the market that these gains were also heading to its Intel x86 Xeon systems. The reason for that reminder: more of HP's customers, such as those leaving the 3000 in migrations, are moving to Windows.
We're not hearing nearly as many reports of migrations which landed on HP-UX systems. The latest news arrived today from Bob Thorpe of National Wine and Spirits. At the Detroit-area IT center, this 3000 pro turned migrator said their customized system is being moved, COBOL and all, to Windows.
"We are in process of having our in-house designed app (using COBOL, IMAGE, and VIEW) converted to NetCOBOL," he said. "We will migrate to a Windows Server platform by March or April next year."
It doesn't matter so much that it took NWS 12 years to leave MPE/iX. What seems more meaningful is that in spite of the Itanium speed-ups, HP couldn't lock NWS into its single-vendor, OS-plus-Itanium environment during those dozen years.The newest Itanium muscle will arrive a little more than two years after HP's 9300-generation Integrity boxes rolled out to customers. These newer blades consume 21 percent less power, led by a new entry-level server, the Energy Star-certified Integrity rx2800 i4.
But dropping the cost of ownership for Itanium has mostly been a pleasure for the existing HP-UX customer. Oracle cast a year's worth of doubt over the chip's future until the courts made the vendor cease, and pledge to support HP-UX and the other operating systems which rely on Itanium. That's one reason HP reminds the market about Itanium's advances and where the improvements will end up: Xeon systems.
With advancements in availability and reliability, HP’s mission-critical Converged Infrastructure will continue to enhance established HP Integrity platforms supporting HP-UX, HP NonStop and OpenVMS operating systems. Over time, these advancements will cascade to mission-critical x86 platforms delivering a single, unified infrastructure for Unix, Windows Server and Linux environments.
That means this "i4" line of Itanium-9500, with its new server blades of a two-socket BL860c i4, the four-socket BL870c i4, and the eight-socket BL890c i4 -- all of these are simply pilot units for the inevitable transfer away from Itanium. How inevitable depends on the customer's trajectory. Windows-bound sites like NWS don't much care how much Itanium can outperform Xeon.
At TechWeek Europe, one writer there interviewed the European head of HP's Integrity business. The website's Peter Judge didn't hear HP expecting to sway many new customers.
According to VP of Business Critical Systems for EMEA Mark Payne, customers still see plenty of performance benefits in the Itanium platform, and would not move across until the x86 platform can match that. Itanium-based systems like Integrity have better mission-critical performance, and users won’t move away until, at the very least, x86 can equal that, said HP.
Unix systems are obviously changing their role in the datacentre, and no one at HP actually suggested they would start to win back business against x86 servers. However, there was a clear expectation that the end of the Oracle lawsuit and the new chips would unlock demand from uncertain customers.
Judge compared the Unix vs. mainframe battles to the future facing the installed HP-UX base. "When we hear that the Unix ecosystem is doomed, we should take some perspective, and expect a similar process to occur. There seems every reason to expect Unix to last as long as the mainframes it failed to dislodge."
HP's message off its own Itanium website shows that it considers "legacy systems" to be its own older Integrity servers. A business case study of manufacturer Steelcase started with the company's use of the Tru64 OS and PA-RISC, then movement to Superdome Integrity. HP seems just as enthused about seeing fewer Oracle licenses needed in the more powerful configuration.
Itanium once had a clear power disadvantage against the PA-RISC chips that drove the ultimate HP generation of 3000s. It took as many as three years for Itanium to catch PA-RISC after the Intel-based systems began to ship. Somewhere in the future of HP's migration campaign, customers like NWS will be hearing more about Xeon systems than Itanium servers. Windows Server, not the Integrity server, is luring migrations.
November 16, 2012
Running a Freeware Emulator: Just Ducky
Editor's Note: I asked several HP 3000 veterans to see how well the installation of the new freeware version of the Charon HPA/3000 emulator worked for them. In yesterday's article, Alan Yeo of ScreenJet led us through a weekend-long journey to get the right VMware and a 2GB Player-ready file onto a server, rather than a desktop. A genuine HP 3000 played a key role. Now with an ISL> prompt on his screen, Yeo plunges forward.
By Alan Yeo
Second of two parts
Okay, so with no documentation at hand (as of last weekend), let’s try ISL>START NORECOVERY
This starts the MPE launch, I get prompted for date and time which I correct, and it continues with a normal 7.5 launch, right the way through to starting JINETD and logging on as OPERATOR.SYS.
You know what they say. "If it looks like a Duck and quacks like a Duck, it’s probably a Duck," and this thing looks like an HP 3000 and would have probably quacked like one if it could.
As far as I can tell I'm sitting at the console of an HP 3000! I’m running in a Putty Terminal, so I'm not going to be able to do any block mode stuff, but it’s good enough to run a whole load of MPE commands and have a look at the created environment. Yes, it still quacks!I don't want to try doing too much perched on my stool in front of a rack in the computer room, so can I access this thing from our network? Immediate answer, is No. It is configured with some strange IP address, so I need to reconfigure it for our network. On an HP 3000 easy just go into NMMGR, but that's in block mode and I'm connected via Putty.
Looking around the screen I see another icon, which turns out to be for xhpterm (a nearly usable HP Terminal Emulator). I launch it, up pops a colon prompt and I logon as Manager Sys. So far so good, let’s try NMMGR; it loads and runs and I do some basic network configuration, validate and exit — and darn I have lost my connection as the IP address has changed. Now what do I do? as I don't seem to have any way to change the IP address that xhpterm is using, and my Putty window has disappeared somewhere.
Let’s try connecting from a real terminal; nope no luck, looks like I have broken this, maybe this demo version only works with its fixed IP? Anyway back to the i7, and decide that I'll shut down the VM and maybe reload. It may have been me but I couldn't find a way to shut down the VM without saving changes, which I didn't really want to do as I had obviously screwed something. So I saved changes.
I thought maybe I'd have to blow the files away and re-extract the CHARON files again, but I thought, well let’s just launch it again! I did, it went through the boot sequence again, during which I spotted that the new IP I had set had taken effect, and magically when I launched xhpterm again it connected. They must have configured it to use the current IP address of the emulator.
Can I get to it externally via Reflection now? Yes! Okay, now we are "Cooking with Gas." (For those non UK readers you'll have to Google that). File transfer a bunch of stuff, and everything works!
Think I'll finish tidying up in NMMGR, but it won't run from Reflection! Why not? What normally stops NMMGR running? Yep, hptypeahead was turned on, but how — I hadn't done it and it’s not a default. A quick search shows that this box has a whole bunch of SYSTEM UDCs set including:
setvar hpsysname 'CHARON-DEMO'
setvar tz 'PST8PDT'
setvar hptypeahead true
Now fine and dandy if I had actually been in Pacific Time, and if I had wanted hptypeahead set (I NEVER have hptypeahead set!).
Bit of a cleanup job to get rid of UDCs and replace with a set from one of our HP 3000s. Driving an HP 3000 with someone else's UDCs is rather like walking around in someone else's oversize boots. They are still boots, they keep the water out, but it just feels a bit uncomfortable, and you can't run!
I do a bunch of file transfers and restores, some COBOL and Transact compiles, restored a database, ran some programs, everything worked. And to be honest I didn't expect it not to!
For those of you thinking of trying the emulator, don't waste your time trying to find something in MPE that doesn't work properly, or a program that gives different results, You won't. I know this sounds too good to be true, but it isn't.
I was fortunate enough to have Mike Marxmeier explain to me a year ago how a hardware emulator works, and basically if you can get the OS to boot, it’s a done deal and anything that runs on that OS hasn't the faintest idea that the hardware has changed. And this is the real MPE we are booting, not an emulated MPE.
The only thing that is emulated is the hardware, so the only place where there might be problems would be in handling peripherals, or possibly the interpretation of error codes from them. Believe me, way beyond my capabilities or desire to go investigating.
So we now have a virtualised MPE 7.5 HP 3000 running on an Intel i7 server (which we have called "Sharon"). It only permits two concurrent users (hey, this is the free version) and I'd defy most people to logon and know that it wasn't a real HP 3000.
I don't know what the final hobbyist version of the CHARON-HPA 3000 package will look like, as I was just being used as a guinea pig tester by Ron. However, this 7.5 box came with all the subsystems I needed to do anything I wanted. If the final hobbyist version doesn't, then unless you already have a 7.5 box with an MPE license then it will be virtually useless to you.
CHARON-HPA 3000 is exclusively 7.5, so you won't be able to take subsystems of your aging 6.0/6.5 9x7/9x8 and use them. My opinion is that for the Hobbyist Licensed version this shouldn't be a problem, as it’s restricted to two users so it’s not like HP would be opening the floodgates on the use of unlicensed subsystems. What’s more, anyone moving from an earlier version of MPE already has a licensed version of them anyway. However, HP is a strange company these days, so I guess we just wait and see what happens.
Commercially, I'm sorry it works, as it will give people more excuses to homestead instead of using ScreenJet's software to migrate. Personally, I like it, as it sticks two fingers up in the air at HP and says "see, if you had wanted to keep all those HP 3000 customers you lost it was technically possible.” And who knows — as ScreenJet's Transact and VPlus migration products also run on MPE, and we now have a new MPE platform, maybe there may be emulator customers interested in advanced versions of Transact or VPlus with all the bugs fixed. And versions that are far more capable than the original HP versions, and are supported!
November 15, 2012
Installing the Emulator: Ahoy, the Disruptor
Editor's Note: As soon as the freeware personal edition of the Stromasys 3000 emulator went live for downloading, I sent the FTP links to several HP 3000 veterans to see how well the installation worked for them. Before we'd follow through on helping to host this freeware, I wanted to see the state of the packaging. Allegro's Gavin Scott also installed it at our request, and his report appears in the forthcoming 3000 NewsWire print issue.
By Alan Yeo
I'm not sure why I agreed to Install the Stromasys CHARON-HPA/3000 freeware. It's disruptive technology to the HP 3000 migration business that my company depends upon. However, as I have spent most of my working life using an HP 3000, it would be nice to always have one available after all the old hardware dies or becomes uneconomic to keep alive.
This is almost one of those stories that went nowhere. There seemed so many stupid obstacles to overcome that I almost gave up a few times -- and that was mainly down to lack of documentation that could have saved hours of work. There was also the fact that instead of wanting an emulated HP 3000 on my desktop, I wanted one on a server where a few of us could test drive it.
Hopefully, the lack of documentation last weekend will have been resolved by the time you try the freeware. But here, over today and tomorrow's articles, is the tale of getting my HP 3000 Emulator into the delivery room and smacking its little bottom until the first little colon prompt appeared.
Part 1: Getting things downloaded and installed, starting with a compatible VMware Player and a 2GB Stromasys file.
My only documentation for this was an email from Ron Seybold at the Newswire, with a link to a 2GB download on the Stromasys site.
- Intel i7/i5 or Xeon CPU with SSE4.1 support; 2 GHz minimum, 3GHz or above recommended.
- 8 GB RAM minimum.
- dDsk space - 0.1 TB + space required to keep HP3K disk images.
- 20 GB is the minimum requirement for the freeware package.
- Two Ethernet ports.
This is the full 2GB VMware kit, uncompress and open with VMware Player. (And an FTP link followed)
CHARON HPPA runs under any of three supported 64-bit Linux Desktop distributions.
Ubuntu 11.10 is our recommended Linux distribution, and is available at no cost. Ubuntu 11.04 is also supported; versions 12.04 and 12.10 can also be used for testing. Fedora 16 Desktop Edition (64-bit). Fedora is available at no cost. Fedora 15 and 17 are also supported. Red Hat 6.2 (64-bit) is available at www.redhat.com; it is a commercial distribution.
Fortunately we have an Intel i7 server that already has Ubuntu 11.10 Desktop as the host OS. Unfortunately it has Virtualbox installed not VMware, and there were a number of horror stories on the net about running VMware and Virtualbox on the same host. This it turned out was not true, however your mileage may vary.
So the first problem was getting the 2GB download. I don't have fast broadband, and to be honest I didn't see the "GB" and read it as "MB" (as who the hell downloads 2GB?) so it was a bit of a surprise when I browsed to the ftp location and started the download and was told it was going to take 23 hours! I think I looked at the screen for a few minutes just to let it sink in that it did say 23 hours and wasn't going to change its mind, it didn't and I killed the process.
The next day with the weekend looming I thought okay, I'll start the download to my PC in the evening and pick it up the following evening (if the connection has managed to stay up that long). This time it told me that it was only going to take just over five hours (don't know what had happened in the intervening day) but five hours meant I was able to check before bed, and as the download completed, plan to do some work on it the following day.
Saturday: The Second Shoot of the season, and me and the dogs were out after Pheasant and Duck, so "Sharon" was going to have to wait. Evening, glass of wine, let’s take a look at where to get this VMware Player thing. Find the VMware site, find the latest version downloads, Oh blast, another 200MB download. Ah I know, I'll logon to the i7 server and download it direct. Strange, if I went to the website from my PC with IE I was offered the downloads. If I browsed there from the i7 with Firefox I got the page, but no downloads offered. Since it is evening I can't be assed to find out why, so resort to downloading the correct Linux version for x86-64 to my PC, and will pick up the following day.
Sunday: Really nice sunny day, unlike the crap we have had for weeks, did I want to spend time working indoors? No, but if I didn't I might never get back to it. Fortunately as it transpired everything took so long and was so broken that all I had to do was wander back and check on progress every hour or so.
Okay I have this 2GB download I need to move from my PC to the i7 server. Easy I'll cut a CD, Windows refuses to copy the file! CD burning software refuses, nay, won't even show me the file to select! That's okay, I'll FTP it. Windows FTP won't even show me the file with a DIR let alone let me PUT it anywhere!
How do I move a 2GB file from my PC to the i7 server if I can't FTP it and can't burn a CD or DVD of it? I could try playing with my PC to see if I could share its drive and do an FTP GET from the i7, but life's too short. I then thought, I wonder what Reflection thinks of the file? Sure enough, it’s happy to show it, maybe it will transfer it? Where to? I need something with PCLink installed.
Ah what about an HP 3000? No problem, Reflection starts transferring the 2GB file (in Binary format Streams) to one of the HP 3000s. It says it’s going to take a fair while even over a 10MB link, but the sun is shining and I can wait.
Becoming a VMware Player
Okay, let’s get this VMware Player set up on the i7 so it's ready and waiting. 200MB is easy to move via a memory stick. Got the file on the i7, follow instruction to right click and open with gedit, it’s a shell script file that it says will do everything for me, including extracting and installing VMware Player if it isn't already installed. Off we go, it has to process the file but shouldn't take long —this is an 3.4Ghz i7 quad core with 8GB RAM.
Time passes. Time passes. Look at the bottom line of the screen: it says it is processing line 450827 and counting, Time passes, the count is on 600 thousand and something! How many lines could there be in a 200MB file? Time passes, I wander back about 30 minutes later it’s on line one million one hundred thousand and something, and as I'm watching it pops up a box to say its finished, but it has an error with some of the characters, do I want to continue? in which case the result will probably be bad! Or do I want it to try a different character set encoding to translate the characters? Okay, says I, "have a go." Oh blast, it’s gone back to line one and started processing the whole frigging file again! Yep running just as slow, time to get outside and do some real work and come back in another hour and a half.
I notice that the Reflection transfer of the 2GB file has finished to the HP 3000, so now I need to get it from there to the i7. No problem: open an FTP connection from the i7 and get the file (binary) leave it running, go get that sunshine.
Pop back a couple of hours later. I have a nice 2GB "Sharon" HPA/3000 file on the i7, and the VMware Player extract has finished! But has the same error! Okay, so on the latest 200MB VMware 5 something is broken and won't install. Give up, or get a long spoon and ask the evil Goggle Empire what it might know.
Okay, lots of horror stories about getting VMware Player 5 running (or rather not) on Ubuntu 11.10. But quite a few people having success with the older Player 4.5 version. Browse to the links from the i7, and this time I can see the version 4 downloads! Select the latest, slightly smaller, and let the download run. Come back, it’s finished, and this time the file has a .bundle extension, so I click and run and it unpacks and installs like a dream,
What next? Okay, find the now-installed VMware Player, and run it, up it comes. But what do I do next (remember, I have NO documentation). It must have something to do with that 2GB file that has a GZ2 extension, so let’s try opening it. Right click, get offered an open by something, which I do and then get an "extract" option. Okay, in for a pound, in for a penny, so off we go, everything unpacks clean as a nut.
Okay, there must be something I select from VMware Player. I click open and browse to the directory where everything "Sharon" had unpacked, and it showed me a single file that it obviously thought it could use. I select it and click open, and wait. I get a warning that something is trying to open Ethernet1 in "promiscuous mode" but that it has been denied, and that if I want to read all about it, a web link was supplied.
At this point I have been playing fast and loose with a bunch of software, so I don't give a damn about something else being a bit promiscuous. Wow! I get a "Sharon" screen, and then a Putty terminal window opens in a bright green. (I start thinking Putty, that ain't going to do Block Mode) but low and behold in the Putty window I see an HP 3000 going through a recognisable boot sequence ending with an ISL> prompt.
November 05, 2012
Accepting Irregular Statistics
We're on the eve of the US national elections today, so a lot of stories are being told about statistics. In many segments of the country, one-third of the registered voters have already cast ballots. We are told that statistically there are under 1 percent of the voters who remain undecided.
A small percentage might continue to matter. And the trends often do matter statistically. For example, Microsoft's Windows XP still represents about half of the PCs still in use, according to metrics company Net Applications. And just this week, the number of Mac users who are clinging to three-year-old Snow Leopard Mac OS still leads the installed base.
And maybe just as surprising, some large and well-known companies are still continuing to embrace their HP 3000s. It's irregular to believe that major corporations continue to use an operating system this dated. Well, maybe not so dated. MPE/iX got its last security patches in 2008, just a little bit farther back than Snow Leopard was created. Maybe because of their stability, both Snow Leopard and MPE/iX continue to serve in the market. One place we discovered this morning is PC Mall, an online sales outlet selling computers that will run Snow Leopard and Windows XP. And they're doing it off software written for MPE/iX.PC Mall is providing an irregular statistic, but they also prop up a trend. The adoption of non-MPE/iX platforms by the installed base has slowed to a crawl. Migration suppliers all predict that 2012 will one of the least active migration years since, well, the 3000 transition era started in 2002.
What's more, PC Mall isn't a complete outlier. Unisource, a $5 billion company, continues to run its operations on HP 3000s.
Both of these pieces of information come by way of the LinkedIn's HP 3000 Community Group. There's 538 of us in that group, numbers that start to approach the membership of the 3000-L newsgroup. Except you can see and connect with every LinkedIn member. New members come on, like those from PC Mall and Unisource, every week. Chris Enderle of Unisource checked in when he signed up.
I still work at Unisource based out of Atlanta and we are running strong on the HP 3000. Unbelievable that we are still running a $5B company on the 3000, but like I tell our CIO, as long as we keep electricity to them, they will chug on forever. We have very bright people writing code, and they do some amazing things compared to when I wrote code.
Code from bright people is creating interesting statistics about the prospects for our election, too. And in about 36 hours that exciting code will give us results of a hotly-contested election. I hope you've voted already if you're in the US, or that you will do so tomorrow if you haven't. It takes full participation and complete tabulation to get to the point where you can accept irregular statistics for what they are -- part of the greater truth.
October 30, 2012
Personal 3000 iron offered for shipping cost
The HP 3000 emulator is still en route toward its freeware personal version. But in the meantime there's still plenty of equivalent HP-badged iron out there in the marketplace. One spot to look is in the shops of the recently-migrated companies.
Lane Rollins of Boyd Coffee sent us a notice about a pair of Series 918s he's been wanting to move out of his datacenter. (There's a Series 979 on hand that's not going away, even though the company has been migrated for several years.) Rollins was looking for a good home for his rack-mounted Series 918 and a standalone 918. Both of the systems are the same power as the personal version of the HPA/3000 emulator software. The rack-mounted unit had an added benefit of an extra SCSI card as well as HASS storage.
This kind of hardware is still circulating in the community, even if it's got as much cost attached to it as that personal freeware emulator. If you can find something like this out on the market, Steve Suraci of Pivital Solutions -- which still sells 3000s -- says you shouldn't be paying more than shipping. Although his company collects systems like this for their depot parts value, they also keep an eye the shipping costs.
We still take them on at times when it makes sense. Some gear is too far away to make sense. By the time we get a mover out there to collect it all, and get then have it shipped back to us we have more into it then we could ever get back.
But the closer a 918 sits to your own shop, the better value it can be -- so long as it's offered free, plus shipping.
"Someone local may be interested if they could pick it up," Suraci explains. A migrating customer who's holding deactivated Series 918s may have to help out on the costs to ship away. To be frank, this kind of server is a better value to the buyer than the seller. Some kind of pickup fee, even from a scrapper, would usually be part of moving out this lower-end 3000. At Rollins' shop, the offer included an LPQ 500 printer with LAN card, a Printronix-based unit, and a few p405 printers.
"The resale value is just about nothing on this lower-end 3000 gear," Suraci said. "Any of the printers might have some value, because of the fact that they are used in non-3000 shops. Shipping cost would still probably be a concern."
October 26, 2012
Taking Care of Too-Great Expectations
Apple is weathering the woes today of an entity which is managing expectations that are too great. Migrators may be laboring under the expectations of moving too much of an HP 3000 to another platform at one time.
Of course, these are very different times for these subjects. Apple set a record for a single quarter. At $35.9 billion in sales ending Sept 30 -- a boost of 27 percent over last year -- it's on a run rate that can make it a $143 billion company during 2013. People continue to call Apple a consumer company, although millions of its devices are powering the mobile needs of business. You simply cannot sell 40,000 phones and tablets -- a whopping $24 million worth -- in a brief 90 days just on the whims of consumers.
So Apple's on a mobile computing upswing, but not enough for the finance analysts. These experts who predict how much a company will earn guessed a little more than Apple posted. So today's a down day for the stock, just at $593, the first time under $600 since last August. HP used to suffer from such Great Expectations. Today, not so great.
However, the HP 3000 has expectations as well. Not for the growth of the platform or an increase in the revenues from its economy. 3000 expectations run to how much of its databases and applications need to be mined and moved -- and how much can remain on a 3000 in near-line storage, ready for the ultimate extraction.MB Foster walked customers through the benefits and strategies of using its UDA Central software this week. This time out in its fortnightly webinar, the company's founder Birket Foster compared the subject of data migration to the expected needs for such a journey. You don't have to bring everything over, even though UDA Central makes it drag-and-drop easy to do so -- even for databases and servers which have little to nothing to do with HP 3000s.
Foster noted during the webinar that some customers are even purchasing 3000s for the specific reason of putting data onto the equivalent of a railyard siding. Of course, that's a a low-speed track section distinct from a running line or through route such as a main line or branch line or spur. But the sidings might still connect to higher speed sections.
"Among the things we've discovered is that when you go to extract your data, obviously you're reading a lot of data," Foster said. "That has an impact on the amount of CPU cycles and bandwidth being used to help data across to the other machine. You have to make sure you understand the timing of when you do that. It wouldn't be a good idea to do that in the middle of the day." But then came the surprises in expectations: 3000s on some kind of new mission, as well as what you can expect to move.
For that extraction reason, some of our customers have gone and bought a separate 3000 to stage the data. They just move the database. They don't move any of the code. They take that database and use it as a staging area to work with it. On the final extraction, they'll go back to the production database. At least they've got a working area where they're not interfering with day-to-day production. You might be able to come up with a very low-cost HP 3000.
There was more to consider about too-great expectations of migration of data.
Some of our customers have been able to work with us to get a methodology that allows them to move just the last month's records, or the last week's records, at the time of moving between systems. That's because all the rest was already staged. History is just history. As long as you can prove that the totals of all of the above equals the total of what you've moved, there's not a problem. Except in cases where you've got revisionist history, the history shouldn't be changing. If you look at it, about 90 percent of your database of transactions didn't happen in the last week or month.
Using this method, a customer could do a first run of data extraction, make adjustments to the process (item names that might be reserved words, different transfers between datasets), and then take a larger segment of the database and repeat. If a migrator has great expectations of making a complete move of data in one pass, they're overlooking these adjustments.
"We've seen customers where it actually takes two days to move all the data, and it ran into some kind of problem," Foster said. "Then we had to check the logs for details." Naturally, UDA Central has a comprehensive logging capability.
A customer from the UK in the webinar, who's moving off a version of Ecometry to an app using SQL Server, said he'd need to check on his permissions to access that target database. It's also essential to be adjusting the expectations for the time to clean up and route these extractions correctly, Foster said. Then there's the understanding that not everything's got to be migrated.
"Customers don't think of all the issues that there might be during the initial stages," he said about more typical sites. The fact that the UK user was on the call showed some foresight. "It's not until they get deep into the project they realize there might be any problems."
You consider how much data you expect to keep, "not only from the accounting perspective, but also for marketing, merchandising and purchasing," he said. "We suggest people start a migration by looking at how much must happen, and do it early. If they discover during that look they need an extra six months, it's better than learning they don't have any time left at all. Know how long it will take from the beginning of the data dumping to the end."
October 24, 2012
Speeding Along Migration's Silver Linings
Migrations off HP 3000s come in varying degrees of difficulty. One set of choices gives sites a way to move their MPE-based environments with the Fresche Legacy (Speedware) AMXW. Even heading to HP's Unix servers, this kind of project can take more than a year. George Willis of the investment portfolio management house Fayez Sarofim talked about their project that moved COBOL and Powerhouse onto Unix.
Coupled with Eloquence as their database, the migration took around 16 months, "largely due to the volume of code that we used," Willis reports.
We used Speedware to help us migrate our portfolio accounting system, “DataVestor”, to HP's Unix Itanium servers. The Unix server was the best choice for us because we leveraged AMXW to emulate the MPE/iX environment -- so that we could lift and shift our COBOL and Powerhouse code with somewhat minimal changes.
But moving away from older HP 3000 hardware uncovered an advantage. "The silver lining to being pushed off the HP 3000 by HP is that our overnight batch improved three-fold," Willis said. "That means we now have a comfortable recovery window before users log onto the system in the mornings."
October 17, 2012
Changing Engines, or Cars? It Depends
Homesteading customers are looking at the Stromasys emulator product as an interim solution before migrations. Dan Miller, a consultant in the community whose roots go back to using MPE in 1975, helps a client who wants to know if the HPA/3000 will perform in place of a Series 9x8 server.
The customer of Miller's runs their 3000 without HP support, but the site has risk avoidance measures in place.
As insurance, they have an additional redundant HP 3000 system on-site should hardware parts become immediately unavailable; besides HP, there are many third party hardware resellers available to replace or repair their hardware. They are assured of software support, as I am retained on an on-call basis should they run into system or software problems. They can also contact the local HP office or other third party vendors for pay as you go software support.
But Miller noted an unusual profile for the homesteader. The company is running "lights out," which in this case means operating with no IT staff in place, except for the on-call Miller. The arrangement which gives ERP and financial processing to about 35 users has been flawless, "but time marches on," Miller says, "and a future migration is inevitable." Perhaps not nearly as close as it might be, if the emulator meets Miller's definition of viability.
For another aspect to the question, customers will weigh how cost-effective any emulator will be. That's a subject where ScreenJet's Alan Yeo says the costs depend on a customer's comfort with MPE's limits and the success of current applications.Miller points out that his consulting client's operations to support a hardgoods distribution business is running without DP staff.
Although they have knowledgeable mangers to handle the day-to-day operations problems, they have no DP staff! Because of the reliability of the HP hardware and the demonstrated success of their custom software, they have been able to avoid the cost of hiring a System Manager, Programmers, or Operators – they run “lights out” and are extremely satisfied with the results of these executed plans.
Needless to say, they are skeptical and hesitant to move away from their current system.
When is that kind of migration due to arrive? Yeo says the same choice befalls an owner of a comfy and reliable car which needs to be certified for a long trip. Buy a new engine, or spend the money on a down payment on a new car? Even at a reduced level of licensing, HPA/3000 is still going to cost in the realm of five figures. Yeo examines the question, "Is an emulator cost-effective?"
If you are keeping HP 3000 hardware running for a couple of thousand bucks a year, then No. If you are reliant on your HP 3000 applications, are happy with the constraints of MPE, and think that will hold true for a few years, then Yes.
The analogy is rather like running an old car that you like and feel comfortable with as your daily transport. It's inexpensive to keep running; the local parts store and local garage seem to be able to supply and fix everything for a few hundred bucks when it breaks. But you have a nagging doubt that if you decided to undertake a cross-continent journey that the engine might just expire with a loud bang. Now someone comes along and offers you a brand-new engine for $5,000 -- what do you do?
1) Decline the offer as too expensive, and carry on as now.
2) Accept the offer, and continue driving your comfortable old car for a number of years, confident that it's got a good engine that's going to be reliable.
3) Decide that if you're going to spend $5,000, that you may as well use it as a deposit and buy the new vehicle that you would really like, one that will better suit your needs for the next decade.
Which is the best most cost effective choice? Ah well, only you can know that, for as with so many things the answer is "It Depends."
October 11, 2012
COBOL You Know, vs. COBOL You Don't
Migrations are in play all over the world between HP 3000 systems and Linux environments. Nobody seems to be reporting very many at the moment, but the Little OpenSource Environment That Could is a regular replacement when a 3000's futures go a-wanting.
All well and good, in many instances. Hiring Linux help is never an issue, but the know-how and replacements for the rest of the 3000 ecosystem are more complex. For example, a customer who's been using scripts in their HP 3000 ops needs a replacement. MB Foster's created one for Windows in UDAXpress, which the company has been demonstrating this year.
COBOL, however, becomes an element that might be integrated tighter than you'd imagine in a 3000 program suite. For example, one recent migration project we heard about included a 4GL-to-4GL Powerhouse.
The decision was made to move the application largely as is, to Powerhouse on Linux, and to Oracle. Porting Powerhouse is not too onerous; apart from a few limitations and differences, you just port the code across and recompile it with Oracle as the target database, and off you go.
There was one catch, and it might become one in a migration near you. Some core calculations can be enshrined in a set of COBOL routines. Maybe they were too complex to write in Powerhouse. So at this point, a Linux-bound customer is looking seriously for a COBOL replacement. They can reach for commercial products which run on Linux, or look to the open source community at OpenCOBOL. Some such migrations are moving from a COBOL they know, to a COBOL they don't. The commercial COBOLs have support staff and training. Open, not so much, unless a third party gets involved.A seasoned migration engineer on an adept team says that OpenCOBOL and Linux had to be blended without help from the OpenCOBOL online forum. This typical sort of knowledge repository for open source "seems to have been read-only, for newcomers at least, ever since last January." When nobody's posting to a help forum, any questions had better be the same as they ones already answered.
OpenCOBOL is open source code that has a commercial counterpart, just like Red Hat commercialized Linux. You can download COBOL-IT to get started with this blend. Freshe Legacy, the former Speedware, was drawing attention to COBOL-IT during 2011.
But 64-bit OpenCOBOL, running on RedHat Enterprise Linux 5.3, eventually assumed the core calcuations which the 3000's COBOL once did. The calculations were in surround code. Sometimes Powerhouse is an application's surround code, but sometimes it's COBOL.
The 3000's COBOL can be compiled on OpenCOBOL 1.1. (Actually running it against a database like Oracle is another matter. There's the calls to HP's intrinsics, plus the exchange of data with IMAGE, to rewrite into Linux intrinsics and Oracle calls.) But there's also a thorough pre-requisite to simplifying the COBOL from the 3000.
1.Remove all the code relating to long-dead product ranges that would never be purchased again. Good policy in all migration cases. Your migrations should well begin by studying all the programs that need not be migrated, because the end-users don't use them anymore.
2. Make the code almost completely ANSI-compliant, using COBOL's functions for date calculations instead of any home-grown ones. The 3000 COBOL's ENTRY points are already simple enough. They might be a lot of trouble to code around, and OpenCOBOL supports them anyway.
The blend of OpenCOBOL and Powerhouse works very differently than the 3000's, which requires this bit of technical refitting: keeping the OpenCOBOL on 64-bit.
A 32-bit OpenCOBOL is needed if Powerhouse, itself 32-bit, is to call COBOL subroutines. So you do a COBOL wrapper for the subroutine, which makes it possible for Powerhouse to RUN it as a separate executable -- and 64-bit OpenCOBOL will be okay, now passing and returning the variables in a file.
If all of the above sounds like the effort of home-grown application development from the 1980s and 1990s -- workarounds galore -- of course it is. These migrations are moving applications that were constructed during that era. It might also serve as a leg in the journey moving the COBOL you know to a COBOL you don't on Linux. Especially if that COBOL is open sourced. The reputation that Linux bears -- being a hands-on environment -- survives, especially powered by reports like this.
Database: vendor-supported. Environment: same. COBOL: Perhaps best chosen as a commercial tool with support. And be vigilant about the run-time costs, which never existed under HP's COBOL II. That was the final COBOL, by the way, that HP ever created, using a well-honed languages lab. By the time COBOL became important to Unix or Linux, HP had left the compiler business to third-party experts.
October 01, 2012
When HP's SUSAN Won't Say Enough
Emulator vendor Stromasys has sold a few instances of its Charon HPA/3000 virtualization engine. But there's even more interest in the free version of the product. Not much surprise there, considering the average budget for a company that's sustaining its 3000 in production use.
However, there's another kind of 3000 user who's looking at this personal freeware. Developers of MPE/iX code -- mostly consultants, and some tool and utility providers -- are expressing an interest in downloading the freeware version. When they do this, they'll require some strategy to tell their other software that the emulator is actually an HP 3000 with a valid HPCPUNAME and HPSUSAN number.
The HPCPUNAME and HPSUSAN combination is used by third party vendors to validate a license. If the combo doesn't match, most software won't load at all. (At best, you might get a demo version, but that's more of a personal computer fallback.) Stromasys is looking at the issue for the freeware it calls the A200. The paid version of the product uses a USB stick with these numbers encoded, which makes any Intel i7 Core PC capable of running a utility like Adager or an application like Ecometry.
But the days of that HPSUSAN being a unique number -- identifying only one MPE/iX licensee -- are over. CEO Rene Woc of Adager said that as HP began to use and re-install these numbers, creating its own 3000s out of HP 9000 servers, duplicates have emerged. But the combo of HPCPUNAME and HPSUSAN is still needed for verification. Even it it's not unique, it's still not generic.
"Way back when, with an HPSUSAN I would be able to tell you the HP 3000 model, and even the serial number, I believe," Woc said. "Today that's not true anymore. It's not a unique number."
This leads the users interested in freeware HPA/3000 to a challenge which Stromasys must master: How to give hundreds of freeware emulator users a way to employ their valid HPSUSAN numbers with third-party software. Only using the full complement of software on the emulator constitutes a complete test, Woc said.Stromasys founder and chairman Robert Boers is examining this challenge. He ran one concept past me last week.
In the commercial version of the virtual HP 3000, the HPSUSAN is located in the license key (set to the number the customer specifies). The freeware A200-sized emulator has no license key. We can program into the code a fixed number (such as 123456.) Would that work for non-commercial use?
Commercial or not, a fixed HPSUSAN won't verify third party software which expects a number registered with the vendor. While a fixed number would satisfy MPE/iX so it could boot up on the virtualized 3000, it doesn't seem likely that it would meet the validation requirements which utilities, development tools and even some applications require.
And if you're going to test it, you cannot ignore the third-party software.
A lack of that kind validation might render the A200 HPA/3000 -- Stromasys calls it equivalent to the power of a Series 918 -- nothing more than a proof-of-concept demo.
"If you're going to test it, you cannot ignore the third party software," Woc said. "At some point Stromasys might offer a freeware version where they charge a nominal fee for the administration of producing a USB device with some HPSUSAN and HPCPUNAME that would work with the third party applications and software. The third parties would have to update their license algorithm," Roc said while he considered the challenge, in order to use a generic number. To avoid triggering upgrade fees during the testing, that HPCPUNAME would be the lowest possible tier of 3000. A Series 925 comes to mind, probably the slowest 3000 ever released into the market.
But HPCPUNAME is half the value for those algorithms. And even a user who has valid HPSUSAN numbers will need to deploy them on a personal freeware A200 model of the emulator. For example, Taylor Lumpkin of the Hire Experience consultancy continues to develop for Ecometry e-commerce users. Hire Experience was founded by key employees who designed and built the Ecometry app suite. Lumpkin loves the idea of skipping the use of more 3000 hardware with an emulator -- just like his company has skipped Windows hardware by virtualizing the OS on Macs.
"We continue to develop for Ecometry on MPE/iX," he said, "and being able to run it on one of our existing i7 Apple machines, right along all of our Windows virtual machines, would be of great benefit. We could deploy machines to our remote developers and eliminate the need for connectivity."
We are still a HP Partner, and HP have allowed us to have free MPE for over a decade now. We also own a small pile of 918s which all have legitimate HPSUSAN numbers with the HP license converted into our name by HP -- back when they still did that.
We love virtual machines and have not had to run any hardware on Windows now for seven years. This has proven to be a huge resource saver -- as we have eliminated all downtime which used to accumulate to 7-8 person days annually, all by running our desktop and server hardware on OS X exclusively.
Intel i7 distinctions aside -- the only i7s referenced by Stromasys so far have been PC hardware running Linux -- the profile of a developer customer usually matches lowest-speed units. Developers rarely need the commercial-grade, production-level horsepower of 3000s to cut and maintain code. But a free version of a 3000 might get in the way of a Stromasys sale.
Simply put, using the HPA/3000 freeware as a development tool would only benefit the developer. Stromasys seems to want to introduce the A200 product into the end user customer base -- a group of users who would likely need a paid version of the software to put the emulator into production.
If the HPSUSAN licensing challenge could be solved, the A200 could become the realization of the mythical Series 908. That was a model of 3000 which HP was going to sell to its developers in the 1990s for as little as an equivalent PC development system. The 908 was much more of a programmer's wish than a genuine HP product. But it illustrated just how little budget was available to development teams for 3000s.
Instead of the Series 908, HP introduced the Series 918DX. The server was only available to members of HP's DSPP developer program. Each came loaded with all of HP's subsystem software. But it was sold by the vendor that created the 3000, so each 918DX had an HPSUSAN which could be registered with any third party for software validation. A few third parties included their software with the 918DX. Most saw the low-power system as a prospective sale, instead of way to expand their installed base through a reference or a proof of concept. The emulator, being novel technology that appears to be a marvel to much of the market, could use proof of its concept.
September 25, 2012
App design changes induce homesteading
At the e-commerce site Musical Fulfillment, ERP manager Chris McCartney would prefer to remain on the HP 3000 with an app which has been working well. But migration mandates at these kinds of satisfied sites are triggered by many things, including the loss of HP support or acquisitions by larger companies.
Musical Fulfillment has used the Ecometry application for more than 10 years. The company even moved up to the N-Class HP 3000s just a few years ago. "We were hoping to get a few more years out of it before we had to make a decision to upgrade or move to a different ERP system," McCartney said. Her firm is the parent company for musical suppliers such as American Music Supply.
"Personally I love HP 3000s," McCartney said. "They are sturdy, they run forever, and they are just one box with none of this load balancing across multiple servers."
The alternative path away from the 3000 induces changes, sometimes ranging beyond a new environment. It starts with a new vendor, in McCartney’s case. Red Prairie acquired Ecometry’s creators last year.
Accomodating a new vendor for your app induces change, but a shift in the product's designs through a replacement version can be more serious. It might be difficult to duplicate all software functions with a replacement package, even the Unix and Windows-based replacement from Red Prairie.
Customers want to carry their business rules and customized code to another platform. It can be tough if application changes have drifted away from the MPE designs. More than five years has elapsed since the vendor last cut Ecometry code crafted for MPE/iX.
One question to put to a vendor inducing a migration to a commodity replacement version: What have you got in software that's going to emulate the operations of our last MPE/iX release, for a minimal amount of change to my site's configuration? If you don’t like the answer, getting more years out of the 3000 is another plan.
Making a stand on MPE, or the 3000 hardware, poses a different challenge to delay a migration. One way to go is some kind of emulation, to get MPE/iX onto newer, non-HP 3000 hardware. AMXW, an emulated platform, lets a company move their MPE environment to a Windows, Linux or Unix host. The product creates a shell above the host hardware.
Another ploy to stay with an MPE application that's working well might be to deploy the MPUX software, from Ordina Denkart. (It's sold as part of the company's ViaNova 3000 solution.) MPUX is really meant for a move to HP-UX. MPUX hasn't been moved forward to Windows 7 yet, and there's no mention of Windows 2008 on the Ordina Denkart website. Additionally, it would not be a good fit for an Ecometry client.
"Most Ecometry sites go to Windows," said MB Foster's Chris Whitehead. "Therefore, MPUX is not a fit. Secondly, most Ecometry sites want to convert Suprtool, COBOL and JCL to native scripts."
Newer e-commerce solutions which run on other hardware platforms have licensing practices in place with application vendors. For something like the Stromasys HPA/3000 emulator, an Ecometry Direct Commerce customer would need a license from Red Prairie to run Ecometry on it. This licensing for emulator is an area where the app vendors are waiting for customers who want to go to a 3000 hardware emulator.
Open Systems Ecometry looks to be the path of least change for an MPE Ecometry customer. Whatever ROI there might be could come from eaving the 3000 community (and its need for MPE IT skills) behind. At this point in the assessment, customers ought to ask themselves if they could hire someone to replace their MPE/iX experience.
However, the adoption of SQL Server or Oracle represents another significant change in using Open Systems Ecometry, plus new exposure to reporting tools which are unlike Cognos Quiz.
At least Suprtool — also key surround code for Ecometry — runs on HP's Unix. Many more Ecometry sites have moved to Windows when they stayed with Ecometry. Suprtool is also within reach of running on Windows, because Robelle has made tech changes enable a new version for Linux, too. Some sites remain on watch for a more sensible package to replace Ecometry on MPE.
September 24, 2012
E-commerce sites examine migration plans
One year after the Red Prairie buyout of Ecometry's owner Escalate, the e-commerce suite is getting a more secure open systems future. Ecometry once represented the largest and most vital part of 3000 growth, especially during the dot-com boom of the late 1990s. A list of 3000 customers circa 2003 showed that one customer in five was using the e-commerce software.
When satisfied users of 3000 apps are sparked to make a migration away from the server, they often rely on the considerations of their longtime app vendor. At e-commerce and catalog firm Musical Fulfillment, manager Chris McCartney is still searching for a solution that will improve on the 3000-based Ecometry software she's managing. Her company serves several e-commerce sites such as electricguitar.com.
Even though the Ecometry app's supplier Red Prairie sells a commodity version of the software, that migration target is not registering a higher note at McCartney's company.
"Unfortunately there is very little ROI in an upgrade to the Open Systems Ecometry," McCartney said, "so that is a hard sell."
The application and its creators have moved from part of the Escalate software group to an even less prominent part of Red Prairie, which now has 43 software solutions in its stable after a series of acquisitions during the last three years. But recent signs point to protection for this application suite -- at least its versions built for non-3000 environments.Red Prairie has now found some gusto in keeping the Ecometry solutions in its portfolio, according to Birket Foster. His MB Foster company partners with Red Prairie to help migrate Ecometry sites like Musical Fulfillment. Companies still looking for the right moment to make their migration cover a wide scope.
"They're either really, really small, or really, really large," Foster said. A tough economy stalled smaller customers, while the larger ones might be hemmed in by corporate IT procedures. An app that's doing its job won't always be put in flight by a vendor's support changes. Costs are always a factor, whether the customer is large or small.
"You pay Red Prairie to migrate your application," Foster said, "then pay someone else to migrate your surround code." Migrating off Red Prairie products might cost $5 million, while shifting to an open Ecometry version could be $2 million, he estimated.
McCartney has been researching alternatives to the MPE-based Ecometry software called Direct Commerce. The alternatives don't improve the application capabilities at the company which fulfills orders from American Musical Supply, zZounds.com, ElectricGuitar.com, and SameDayMusic.com. A competitor, Musician's Friend, made a migration off Ecometry to Junction Solutions several years ago.
"We have been looking at other solutions like Junction Solutions," McCartney said, "but I have yet to find a good reason or some fantastic functionality that the others provide that we don't already do with Ecometry/Direct Commerce. Maybe I am missing something."
If there's a silver lining in the situation for the Ecometry sites still running a 3000, it's the renewal of vows on the part of Red Prairie. There's a version that runs under Windows, and another that runs under Unix. But Red Prairie is no longer in danger of running off Ecometry sites to one of the other software packages in its sea of ships, Foster said.
"There was a question of whether they would keep Ecometry in the boat," he said. "That was a year ago, though. The management shuffles are done."
Just as MB Foster has hundreds and hundreds of customers who continue to rely on its products for MPE/iX, McCartney would prefer to remain on the HP 3000 with an app which works well.
The company has used the application for more than 10 years and moved up to the N-Class HP 3000s a few years ago. "We were hoping to get a few more years out of it before we had to make a decision to upgrade or move to a different ERP system," McCartney said. "Personally I love HP 3000s – they are sturdy, they run forever, and they are just one box with none of this load balancing on multiple servers."
September 06, 2012
Core memories spark a cold start for 3000s
Editor’s Note: Jon Diercks, the author of the only comprehensive MPE/iX administration book, offered us this story of the 3000’s very first year. It was a time of HP retreat from the minicomputer market: HP staff resigning, others unselling a system touted just months earlier as “a happening,” as the slogans of 1972-73 said in HP labs and offices.
Diercks worked at Anderson University in the 1990s alongside Tom Harbron, who’d been the college’s computer department director during 3000’s first months on the market. Diercks said Harbron was heavily involved in early discussions with HP about MPE and IMAGE.
The institution began as Anderson College, and its very first HP 3000 was one of the earliest models. Diercks said the bragging line in those days was "Anderson College has the first HP 3000 ever installed anywhere between the Rockies and the Appalachians."
Harbron’s report on the 3000’s 1973 is part of Diercks’ 3000 memories, and so he’s contributed the writing as part of our 3000 Memoir Project — in all of its authentic, human and humbling beginnings. It's the first story I've read that details the 3000's retreat. An HP employee who couldn't look his customers in the eye about the 3000, and so resigned. A man whose job was to unsell the 3000s -- and later would bundle the greatest software HP ever wrote, IMAGE, to the Classic hardware, which not long after, fell behind the state of the art.
By Tom Harbron
Reports of problems with the HP 3000 operating system, MPE, continued to be received in the opening weeks of 1973. While it was not encouraging, I had confidence in the basic soundness of the 3000’s design and the integrity of Hewlett-Packard to ultimately deliver what had been promised.
HP’s Phil Oliver called and scheduled a meeting with me for February 6, 1973. He brought along Bob Stringer, who had replaced Ed Pulsifer as the District Sales Manager; Ed McCracken, who was now HP's Market Manager for Government, Education, and Medical Markets; and Jay Craig, who was a new HP salesman from Indianapolis. McCracken would tell me, years later when he was the 3000 division manager, that the morning in my office was the most difficult day of his career. The people that HP hired were, mostly, an honorable group of people.
On that day in 1973, they had some bad news to deliver. Specifically there were seven points:
1. HP cannot bring the software components of the system up to full specifications before Fall 1973.
2. They are devoting “maximum resources” to correcting the problem.
3. The system will currently support no more than 4-6 simultaneous users.
4. HP will loan an additional 64K bytes of core storage to bring the system up to this 4-6 user level of performance. (We had ordered the system with 64K bytes of core storage.)
5. IMAGE will be further delayed to January 1974.
6. Because of hardware difficulties, a slower console printer would be provided.
7. They would like us to cancel the contract. Lacking that, they wish to amend the contract.
It was a tense meeting. McCracken was going about the country, visiting customers, and unselling the 3000. It was hard for everyone. Phil Oliver would return to his office later that day and resign. He told me he couldn’t look his customers in the eye. Ed Pulsifer had already resigned for similar reasons.
I resisted their pleas to cancel the contract for four fundamental reasons.
First, I had faith in the basic design of the system. I had run benchmarks that had come in almost exactly where I had predicted from the timings in the ERS. MPE was clearly a better design than nearly anything else then available. The combination was more cost effective than anything else by a factor of two or three. Moreover, I had met many of the people involved with the project and had confidence that they could do the job, given the time and resources.
Second, there really were no viable alternatives on the market at the time. DEC tried long and hard to sell us, but in the end their salesman conceded that the systems DEC had were either too feeble or far too large for our needs; the HP 3000 was a perfect fit. IBM tried hard to sell us on various timesharing patches to their systems, none of which worked well. The only systems available that would do the work were the XDS Sigmas and they cost five times as much as the 3000.
Third, I thought that HP had to make the 3000 succeed if they were to remain a growth company. At that time, HP had about half of the instrument market and could not significantly expand their market share without anti-trust problems. Their other market areas, such as microwave, were respectable, but in small markets that were not growing very fast.
The only way that HP could continue to grow at historic rates was by entering the computer business in a major way. With $25 million already invested in the 3000, they were unlikely to write off that investment and content themselves with their existing markets. If the 3000 failed, they would have had to immediately start over on another computer project.
Fourth, we had already invested several man-years in application development for the HP 3000 at the time that HP was trying to unsell the system. It would have been a financial disaster for us to write off all of that work and begin again with a different system. We really had no option beyond the 3000.
Years later, in a speech before the Users’ Group, McCracken said “I want to thank those of you who had faith that the HP 3000 would succeed at a time when many at HP had profound doubts.” I’m sure he was thinking of that cold February day he spent in my office.
August 17, 2012
NorCal transit will run its 3000 route again
Anybody who wonders where HP 3000s are hanging on can grab a rider strap on the Alameda-Contra Costa transit service. The public entity AC Transit just opened up a one-year contract to maintain its two HP 3000s, along with the applications.
The systems under maintenance are a Series 957 and a Series 987. If you're scoring at home, these are servers built and sold during the 1990s -- still powering a California organization with duties to ferry 191,000 riders daily with a fleet of 584 buses. The District’s service area extends from western Contra Costa County to southern Alameda County, and the organization employs 1,863 employees.
As if that's not enough, this contract -- which is out for bids until Tuesday, Aug. 28 at 10 AM -- has a provision for extension. The district isn't sure when it will be able to stop using those 9x7s.
There are many 9x7s -- well, more than you'd think -- still serving the public or working in private firms. Keeping these two servers online 24x7, including holidays, is going to demand that a winning bidder can prove they know the 3000 and MPE. Things being the way they are in California municipal government, this contract starts its period of performance three days before the bids are due. We'd bet they're going to approve a support supplier pretty quickly.
At the sole discretion of the District, the contract may be extended up to 12 additional months in increments of three months. This is to accommodate the uncertain end date for the District’s use of these HP 3000 computers.
The minimum requirements sound like they could be from any HP four-hour response contract.
- The Contractor will provide a toll-free telephone number, staffed during typical local business hours, to allow one or more AC Transit contacts to report all service requests.
- The Contractor will provide unlimited telephone consultations for both 957SX and 987SX systems during AC Transit business hours.
- The Contractor is responsible for all parts, labor, travel, testing equipment and phone consultations on covered equipment and necessary on-site visits.
- The Contractor shall provide staff to make at least one weekly on-site visit to manage the tape backups and perform a physical systems health check.
- The Contractor must provide staff that can physically attend to these systems and operate independently 24x7x365 with or without a District Information Services escort once an appropriate District security badge has been provided.
- The Contractor is required to demonstrate proficiency in HP 3000 system support by compiling a checklist for AC Transit review and approval. The selected contractor will employ this checklist daily to determine and report on the hardware and software health of both systems.
- The Contractor must have access to a local facility that stocks good-order hardware equipment in a location such that needed parts have been tested and are delivered and installed within four business hours of the incident opening for priority 1 and priority 2 incidents.
Whoever takes on the maintenance "will create and employ a 24 hour/7 day automatic alert system that will alert them to a hardware failure on the Series 957SX and/or the Series 987SX." That's far from commonplace. There are plenty of businesses that don't have auto-alert failure systems.
All this by console “via a dedicated workstation with a serial connection to each of the two HP 3000 computers.” It doesn’t sound like networked remote console access, but that wasn’t a big part of the 9x7 experience anyway. IT at AC Transit calls the shots on application maintenance requests.
It's not a static system, by the looks of the bid. Item 7 calls for a contractor to "Perform ‘software application support’ allowing I.S. staff to make program or application changes. These changes would require that the affected application have no user access while the changes are being made."
There are 37 pages of this RFP, but some of them even do a good job of outlining the base competencies for any 3000's management. Like the 30-item list at left (click for details). It'll be interesting to see what AC Transit eventually replaces those 9x7s with -- and when -- considering that it's got such a customized app suite on its hands. At least there's 12 months of work here, and probably more, for a persistent bidder. Got to keep the buses running in the public's interest. Yeah, buses: as fundamental a transport technology as a Series 9x7.
August 16, 2012
Moving Data in Migrations: the Tools, and Who Uses and Develops Them
Arby's sandwich chain turned off some HP 3000s recently, but moving its data stocked a menu's worth of practices and tools. Based on a report from Paul Edwards, the journey worked smoothest when expertise could be outsourced or tapped.
Edwards described part of the project as a move to Oracle's databases, facilitated by Robelle's Suprtool and Speedware's software. The former supplier has retained its name for 35 years by now. The latter has become Fresche Legacy, but DBMotion as well as AMXW software is still available for data transfers. In the photo at left, the veteran Edwards is in motion himself, flying on a 1968-69 US Navy tour on the USS Hornet. He figures he's been working with 3000s half his life, which would give him enough time in to witness Robelle's entry into the market, as well as the transformation of Infocentre into Speedware, and then to Fresche Legacy.
I'm standing on the right. The two young guys kneeling down are the enlisted operators that ride in the back of the plane. The guy standing on the left is our Crew 13 Aircraft Commander. The aircraft is an S-2E Tracker Carrier Based Anti-Submarine Warfare Navy aircraft. It has a large propeller attached to a 1500hp Wright R1820-82 engine -- one of two on the plane.
Some of the data moves at Arby's went to Oracle, he reports. "They were using Oracle for part of their operations. Using Speedware with Oracle was interesting. Most of that was dumping data with Suprtool or Speedware, then formatting it in the layout they wanted." Suprtool has been guided and developed by Neil Armstrong at Robelle for nearly two decades. He recently marked his 20th year with the vendor, according to the Robelle newsletter.
Arby's also took its payroll application off the 3000, "and it went off to a service bureau. We had the file layouts that bureau wanted, and so it was a lot easier. We just said, 'this field is the one on the HP system, and this field on your layouts is equivalent.' We just matched them all up. We had some where we could say 'forget about that field, we won't need it.' "
But the transition to Oracle, as performed by a team that was supposed to be experienced in the database, was not so easy.The Oracle contractors "had absolutely no clue about how to do migrations," Edwards said. "They'd never done any before."
The migration of data from a well-polished, longtime set of 3000 applications is just as crucial as moving code, selecting a replacement app, or testing what's been moved. And it's not as easy as it might seem to find contractors who've done a migration, especially any who know MPE. Plenty of systems from other vendors haven't been worth the time to migrate. The HP 3000, with its lengthy lifespan, often sports apps that are decades old. Almost as entrenched as Armstrong has been at Robelle.
The avid racing cyclist this summer completed 20 years' worth of "helping to make Qedit and Suprtool great products," Robelle reported in its newsletter.
Neil worked at one of our customers in Ontario, then worked for us in British Colombia, then worked for us in Alberta. At one point Neil moved to Anguilla in the Caribbean to work on Robelle software with Bob Green, our president. Lastly, he moved back to Canada and works on Suprtool and Qedit near Niagara Falls. He is currently our Software Architect, chief systems programmer and a big help for difficult technical support questions.
During his time in Anguilla, Armstrong raced in the 2004 John T Memorial Bike Race. The photo at left shows him with Bob Green cheering him on at the finish. Armstrong has been quick to the pedals for as long as I've known him; as a fellow cyclist, he rides at a rate I can only dream about. But his work in Suprtool -- especially in recent years getting it to Linux, and soon to Windows -- must have been as steady and careful as a rider navigating a busy, two-lane, no shoulders road. That's a tool that began its life in the 1970s, when Edwards was still in the Navy Reserve and working at HP as an SE. Imagine what's been changed in Suprtool over those decades to get it to Suprtool Open.
Sometimes great care to advance a product unveils its rewards when it's compared to other migration methods. It helps if you can call on some military precision during critical transits, too. At Arby's, Edwards and the IT staff seemed to be glad Suprtool was on the migration menu.
August 06, 2012
What You Need to Do and Check for SLTs
At a recent visit to a customer's shop, VEsoft's Vladimir Volokh spread the word about System Load Tapes. The SLTs are a crucial component to making serious backups of HP 3000s. Vladimir saw a commonplace habit at the shop: Skipping the reading of the advice they'd received.
"I don't know exactly what to do about my SLT," the manager told him. "HP built my first one using a CD. Do I need that CD?"
His answer was no, because HP was only using the most stable media to build that 3000's first SLT. But Vladimir had a question in reply. Do you read the NewsWire? "Yes, I get it in my email, and my mailbox," she said. But like other tech resources, ours hadn't been consulted to advise on such procedures, even though we'd run an article about 10 days ago covering CSLTs. That tape's rules are the same as for SLTs. Create one each time something changes in your configuration for your 3000.
Other managers figure they'd better be creating an SLT with every backup. Not needed, but there's one step that gets skipped in the process.I always say, "Do and Check," Vladimir reports. The checking of your SLT for an error-free tape can be done with the 3000's included utilities. The venerable TELESUP account, which HP deployed to help its support engineers, has CHECKSLT to run and do the checking.
There's also the VSTORE command of MPE/iX to employ in 3000 checking. If your MPE references come from Google searches instead of reading your NewsWires, you might find it a bit harder to locate HP's documentation for VSTORE. You won't find what you'd expect in a 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.
It's also standard practice to include VSTORE in every backup job's command process.
There's another kind of manager wouldn't be doing SLTs. That's the one who knows how, but doesn't do the maintenance. You can't make this kind of administrator do their job, not any more than you can make a subscriber read an article. There's lots to be gained by learning skills that keep that 3000 stable and available, even in the event of a disk crash. Management might not respect the 3000's ability to take on new developments. But a company always respects the 3000's reliability.
CHECKSLT, and care and feeding of SLTs, are well-covered in a NewsWire column written by John Burke almost 13 years ago. His advice still holds today.
HP’s documentation tells us we need to have a current SLT. And that it can be created using the TAPE command within SYSGEN. If you look hard enough you will also find the warning that the CSLT you may have created when doing an update or manage patch is not adequate. That is about it for SLT recommendations.
Is this recommendation correct? Well, in the sense that it is necessary to have an SLT created by the TAPE command, then, yes, it is correct. You can re-install your system in the event you lose a drive in the system volume set using this SLT and appropriate other backups. But is this recommendation complete? I think not.
As has been proven countless times, the people who write manuals (and not just at HP) are not out in the real world. They are not running shops where if you get a six-hour maintenance window once a month you consider yourself lucky. They are not running shops where you have to have procedures that can be understood and followed by someone with only basic training in system operation. They are not running shops where cell phones go off like July 4th fireworks as soon as anything unusual happens.
You can find HP's VSTORE page in that 5.0 command manual online, just like the NewsWire's advice. Vladimir, you find him in your office, if he's traveling your way. But managers also find that he recommends our advice -- perhaps because we first get the instructions to do it, and then have our reports checked. Do and Check are words to live by, not just for managing 3000s.
August 01, 2012
Just how good were those good old days?
NewsWire subscribers who receive our email updates have heard that I'm collecting stories about the early 3000's days. I'm working on an autobiography of the 3000, written "as told to" me, by the system. I've fielded phone calls and gotten some nice email stories. Today's was great fun to read and instructive, too. That's because the negative experiences in our lives are remembered clearer than the positive ones.
What I mean to say is that war stories are more fun to read, chock-a-block with details. Before I offer an excerpt from today's story, I want to make an observation about the 3000's life. It wasn't always the better time we prefer to remember.
Even the president of the Connect user group falls prey to this memory. In his column in the latest user group magazine, Steve Davidek remembered days when HP was packed with people eager to service a 3000 customer. After a disk head crash in 1984, Davidek recounted three HP employees he knew by name who chipped in to resolve the problem. A different time indeed, when Davidek managed just one Series III HP 3000.
Our HP sales rep would visit every month or so just to see how we were doing. Some months he'd even bring a Systems Engineer along to check on things. It was amazing.
Dave Wiseman, who says that "Most of you will know me as the idiot dragging the alligator at the Orlando conference, or maybe as the guy behind Millware," told us a tale of days even earlier in the 3000's life. Buying a system from HP in 1978 meant investing in a terminal to test your application -- before HP would even fill the system order.One of the first three HP 3000 customers in Southern England, Wiseman was managing at an IBM shop looking for a better system. "I called the HP salesman and asked him in," he says.
What HP never knew is that if the project went well, there was a possibility that they would get on the shortlist for our branch scheme – a machine in every UK branch office. That would be 45 machines when the entire UK installed base of HP 3000s was around 10 at the time.
So the salesman came in and I said that I wanted to buy an HP 3000, to which he replied, “Well I’m not sure about that, as we’ve never done your application before. Why don’t you buy a terminal and an acoustic coupler first and make sure that your application works?"
"Okay," I said. "Where do I buy a coupler from?"
"No idea," he replied “but the 2645A terminal is $5,000."
So he bought the terminal, and then tested against HP's 3000 in a UK office. "I started dialing into the Winnersh office. (I still have the telephone number and address engraved in my heart). On occasion when I needed answers, I would drive over there and work on their machines."
Wiseman goes on in his early history to praise the improvement that the 3000 delivered to Commercial Union Assurance.
I recall our durability test was to unscrew the feet on the 50MB disc drive and push it until the disc drive bounced off its HP-IB cable. On more than one occasion the cable came out and you could just plug it back in and carry on working. Try that with an IBM and you could expect two days of work to get it restarted.
The IBM guys couldn’t understand how we could run so many users on such a small box, but we were always looking for improved performance -- as we already had the largest HP 3000 around. There were no tools available in those days, so we used tricks like putting a saucer of milk on each disc to see which one curdled first. (Okay, that's not really true. But we did spend a long time just standing there touching the drives lightly just to see what got hot.) We did a full system unload and reload every three months, and unloaded and reloaded most databases at the same time.
Davidek recalls his warm feeling of having ample HP support, but he does recognize it as a bygone emotion. "The customer experience today is probably not ever going to return to those days, but I would love to come close," he writes. "HP is working on this issue, and with a little luck, we may get there."
War stories are useful for more than the warnings about potential pitfalls. Even from 30 years ago, they remind us the good old days were not as good as we remember. They also remind us how our initiative made the bad times manageable. That's a confidence builder in these uncertain career times.
A 3000 manager needed a little luck, all the way back to the beginning. I'd like to hear about your lucky and unlucky days. Call me at 512-331-0075 if you want to chat, or email me. By recalling both the good and the bad, we can chronicle the middle path for that autobiography.
July 31, 2012
How Support (With)holds Key to Emulation
At some HP 3000 sites, the servers are working to deliver IT services to a subset of customers. One site in Virginia which handles healthcare administration is keeping an N-Class server online using Amisys/3000. But the issue which concerns the company isn't so much the tech capability of the Stromasys HPA/3000 emulator. Licenses with existing vendors worry this prospect.
Cognos/IBM is at the top of the list for this company, even through they dropped Powerhouse support long ago. Powerhouse has been an integral part of the Amisys surround code. Cognos wasn't the friendliest company to negotiate with during the MPE heydays. An emulator license for Powerhouse would have to be arranged with IBM.
Other arrangements would include a license for Amisys itself, which is part of the McKesson Group by now. This is one of the software programs running in Virginia where support is being paid -- Adager is another -- and so there's a better chance of getting that license transferred. A transfer license is what's needed for this market. However, it's a lot harder to start up a transfer discussion after you've terminated support.
There are going to be other kinds of prospects where the Stromasys software has a better chance today. The sites where support is intact, or there's plenty of in-house code with no vendors to negotiate with, will have a smoother path. In a spot like that Virginia IT shop, licenses are linked to vendors which will likely expect some support.
This support renewal raises the price bar for the emulator, of course.We've reported on other strategies on how much an emulator ought to cost. Comparing it to the value of the company works, so long as the 3000 drives the entire company's IT. That's not the case in Virginia. HP's BladeServers drive Windows, while the HP-UX systems are running Facets (another healthcare app), but are soon to be replaced by Sun's hardware and Linux. (Take that, HP; Oracle has won that contest.)
The IT pro we interviewed at the shop asked first about technical capability, and the HPA/3000 has been shining there. In very short order he asked about licenses. Hewlett-Packard's emulator licensing is ensured, and companies like Adager, Robelle and VEsoft have expressed little concern about licensing their software for an emulator. (There are tests to be run at some vendor labs. Robelle reported early this year that the HPA/3000 passed all of its tests through February).
Although it might seem like it's hard to convince a CTO or CIO to maintain support contracts on 3000 software, extending support can keep some options open -- especially if there's no clear migration project timeline. Support relationships, renewed regularly, look like they're holding the key to admit the emulator.
July 24, 2012
Make backups, but a CSLT is just as vital
Many homesteading HP 3000 shops are working with limited system administration. If you're reading this blog, that probably doesn't apply to your own 3000 shop. But you can pass on advice about backing up to any 3000 site you know. A backup of applications and databases isn't enough.
The CSLT needs to be fresh and available, too. The Custom System Load Tape tells the 3000 how the configuration is set up for devices attached to the system that you're restoring. (The original SLT that was distributed from HP has a generic configuration. This customized SLT reflects your physical configuration of your specifically-built system.) Also referred to as a boot tape, it contains the system load utilities, diagnostic subsystems, base system files, and other HP system files such as IMAGE, FCOPY and EDITOR.
A CSLT is generated with the system generator (SYSGEN) utility. You can build a CSLT for individual systems, each with a different configuration, after updates. These configurations tell the 3000 what other volumes are available to accept data. You can also put a full backup on the end of a CSLT, but it's better to have that backup on separate tapes. (Separating a backup from the CSLT also speeds up creating a CSLT.) Consultant Paul Edwards advises that managers make a CSLT at least every other time during a backup, plus having two tape drives on each system. "Being paranoid makes for a good system manager," he says. "If you're not paranoid enough, you better have a good resume."
Overlooking the CSLT is so common that even some admin pros have done it from time to time. For one such pro, an A-Class 3000 was recently rebuilt and had its apps consolidated. But the rebuilt system didn't have its CSLT freshened, which was discovered when the boot volume failed.
We lost LDEV1 in the 'system' volume-set. The apps and databases are fine, but I'd neglected to make a fresh CSLT once the rebuild/configure/setup was complete. Fortunately, all the data volumes are protected with Mirror/iX -- but rebuilding the system volume accounts, network config, administration jobs and so on has been a pain.
An honest mistake like this is not one you need to make yourself. Even if, as another 3000 consultant notes, your shop has gone into Frugal Mode while it makes in-house moves. You have the right to be wrong in Frugal Mode. But you really don't want that right, unless you've got plenty of extra time."This is not a mistake I'll ever make again," said our CSLT rebuilder. "Until it's complete and stable, I now make a new CSLT at the end of each day's changes (in addition to the regular backups we do as Store-To-Disk, and then FTP to a NAS). Hopefully I'll never have to go through this hassle again."
AUTOINST updates temporary copies of the system libraries and then creates a CSLT. This can take up to two hours. One set of instructions to do this is available in HP's MPE/iX 7.5 Maintenance Manual. The process hasn't changed much from the 6.0 release of MPE/iX, either. We've got a pointer to each manual; just search for "CSLT" in each PDF file.
We've previously published a paper by Gilles Schipper on the use of BULDACCT versus the STORE command while backing up. The ;DIRECTORY and ;ONVS= options are a key there. What's more, one of our most prodigious contributors Brian Edminster is sketching out a technical, but easy-to-use, Automation of Backups and Effectively Eliminating Use of Tapes article.
Do all the backup that you need when protecting that HP 3000. It's a computer that established the gold standard for recovery in case of powerfail situations. But the success of its backups falls in the lap of the system's managers or owners. (Running CHECKSLT from the TELESUP account will verify if a CSLT is still good enough to boot your system. You'll want that CSLT to run on any tape drive, not just the one it runs on. Alignment issues kick DDS drives out of service regularly.) Don't forget about keeping your CSLT healthy.
July 18, 2012
Disbursing 3000 Gear to the Next Life
Some 3000 shops which have made migrations are looking for a new home for older equipment. At the Boyd Coffee Company -- whose motto is "Fuel, not fashion" -- director of IT Lane Rollins has systems which once did good work but might be ready for retirement. Or repurposing.
"I need to get some clutter out of here," he said, "and I'm not sure who is reselling HP 3000 gear these days, or if anyone would be interested in the stuff. We’ve been off of the 3000 for five years now."
His list includes two Series 918s, including a Jamaica storage unit (HASS) and an extra SCSI card. Also on hand at the Coffee Company's shop: DTC controllers, an HP line printer with a LAN card, plus terminals.
If the gear doesn't seem like it could launch a thousand ships, it could well be equipment to keep a 3000 ship afloat. This kind of inventory won't draw much resale value, but some service companies need it for their spare parts depot. There's nothing quite as good as replacing a failed bit of hardware with an identical unit.If your 3000 gear simply needs a fresh home outside of your datacenter, contacting the support firms which do business in depot repair is a good place to start.
Pivital Solutions' Steve Suraci made a point of this kind of resource earlier this year. A manager announced a need for a 3000-model HP router to keep a storage unit linked up to a 3000. A search across the Web -- rather than a text message to their service company -- eventually solved the problem. Suraci said that's not an acceptable service level.
That provider was willing to take this company's money, without even being able to provide reasonable assurance that they had replacement parts in a depot somewhere in the event of failure. There are still reputable support providers out there. Your provider should not be afraid to answer tough questions about their ability to deliver on an SLA.
Other companies with a need for 3000 parts might be found on our sponsor list: Genisys, the MPE Support Group, or The Support Group. Sometimes a migrated manager simply needs a volunteer to accept a 3000 shipment, or perhaps defray the cost of getting the older gear onto a UPS truck -- or even into the back of a pickup, if the support vendor is nearby.
Boyd's is completely migrated, but there's one last piece of 3000 gear that's not going anywhere yet.
"Someday the 979 will go away, but need to keep it for the time being," Rollins said. We'd bet that some historical archiving is at the heart of that hardware's duty. If you're interested in the Boyd's gear, you can contact Rollins via email or at 503.907.2555.
July 17, 2012
Find SSD on SCSI? It might be time for 3000
SCSI remains the primary method to connect disk to HP 3000s. That means that most of the Solid State Disk (SSD) memory-based devices won't serve for MPE/iX storage. But it's not impossible to make the quantum leap from rotational to RAM storage. It might be worth the experimentation, given the upsides. In short, if a manager can find the SCSI, honey, find the time -- to experiment.
Starting at about $250, the devices are not costly anymore. And even in the more-rare SCSI units, 120-480 GB models are available in online stores.
"You would need to find a SCSI SSD," said Larry Kaufman, a systems engineer with BayPointe Technology. "They are out there, but there are not a lot of choices. Here is something to consider: When a SSD fails, the failure is likely to be catastrophic, with total data loss. HDDs can fail in this way too, but often give warning that they are failing, allowing much or all of their data to be recovered."
Kaufman offered a note about the old HP's "silverback" disks used with 3000s. "They would make tons of noise for weeks, sometimes months, before they would die."
That sound of rotation is also the sound of slower operation, of course. Once you go non-rotational, you won't go back, said one consultant. Using SSD tech in a 3000 carries the usual warning that was often quoted in the 1990s and onward: This is a storage unit not tested for MPE/iX. But there's plenty of tests not yet performed for SSDs. Like any advanced technology, SSD has also got some emerging downsides now being discovered in the field.
For example, there's the lifespan of an SSD unit, which at its heart is just a array of RAM devices. To be fair, some HP 3000s are running with rotational storage that was built before Y2K. SSDs are still new enough, and have tech advancing so quickly, that an MTBF for them is matter of belief in marketing rather than tests.
Arrays help extend these Mean Time Between Failures and offer hot-swap. The 3000's array choices run to the XP and VA models from HP. It can be surprising to see that some well-schooled 3000 managers haven't explored array choices yet. Everybody has something to learn, whether it's RAID or IPv6.
There's also some experimentation going on with setting up a redundant array of SSD units. One tech white paper reminds users that the TRIM command for controlling SSDs should be supported in order to array SSD units, and that older operating systems usually don't TRIM. And by older, the paper's author means Windows XP, which was last released about the time MPE/iX was getting its last disc design. No TRIM in MPE/iX, of course.
The question for the typical 3000 manager is whether SSDs are more reliable or less reliable than hard disc arrays. Choosing XP or VA arrays is a more commonplace storage upgrade for HP 3000 storage configurations. On that subject, Craig Lalley -- who lives to update your 3000 storage -- arrayed the choices.
You could put an XP array with 128GB of cache as a disk subsystem. HP has a whole line of these high speed fault tolerant arrays: XP256, XP512, XP1024, XP12000, XP24000 and a name change to the newest P9500. They all work with MPE. They have software options that provide "hardware mirroring across the WAN", local mirroring and snapshots.
The XP array is much newer, in that they are still making them and the models get updated every other year. Also the XP array is extremely fault tolerant, it is built to be set up, turned on and never turned off.. You can add cache, replace boards without losing data or host connectivity. The VA array only holds 4GB of cache, 2GB per controller.
The XP is several steps above the VA (to put it mildly). You can literally connect hundreds if not thousands of hosts to an XP Array. Comparing an XP array to a VA7410 is like comparing a VW Beetle to a Formula 1 car.
There's a similar speed increase available by moving to SSD. Native support for SSDs on the 3000 was being explored as far back as 2009 by one indie support company. In the current state of the art, the best way to exploit this new storage technology for MPE/iX will be using the Stromasys HPA/3000 emulator. It employs whatever storage is attached to the Intel i7 Core PC running the emulator.
July 16, 2012
Still ample time to study IPv6
A new guidebook to learn the latest-generation Internet protocol will be a useful tool for 3000 pros, at least any who are expanding their networking skills. And while it's true the HP 3000 won't ever support IPv6, this style of trailing the current net technology has been part of the 3000's experience for decades.
In 1984, for example, IBM's System Network Architecture (SNA) ruled a vast swath of a very diverse computing landscape. Almost three decades ago, 75 percent of corporate-level data processing was performed on an IBM or "plug-compatible" system. And about half of those systems were supporting SNA devices. So there you had it: a networking protocol used by more than a third of the world's corporate computers, and completely unsupported by Hewlett-Packard's business computers.
In a story in the venerable InterACT magazine, Sharon Fisher wrote this dominant and rising technology wasn't for sale, just adoption.
The most important fact to remember about SNA is that is is not a tangible product, but an abstract concept. You cannot buy SNA; it is neither hardware nor software. Instead, it is definitions, rules, protocols and formats that govern the structure of hardware and software.
So HP embraced SNA for the 3000, its only business computer, but late. As usual. Adopting standards early might look good in a tech planning presentation, but in practice can be as useful as messaging between a fridge and a TV. We heard as much from a veteran of standards-based networking in the 3000 community.Chris Bartram manages networks for a DC-area company today, practicing so far forward he's a field expert on HP Site Scope, an enterprise monitoring tool that lets you do a variety of agentless monitoring tasks such as web page checks, database queries, and TCP port checks. But he made his name delivering 3000-ready networked products through the 1990s and onward. Netmail/3000 was his best-known product, email for the 3000 at a time when proprietary HP Deskmanager mail systems dominated the MPE landscape. Netmail was built upon standards like MIME, technology far more complex than a corporate-controlled standard such as SNA.
Bartram, who since 1995 has managed a server in Virginia that's hosted 3000 NewsWire web pages, checked in with us about IPv6. Like 3000 net guru Jeff Kell before him, Bartram doesn't see support of IPv6 as much of a practical payoff for most companies. "I’m fairly up on IPv6 in general," he said, "though I don’t plan to implement it anytime soon. There’s just no real incentive yet."
Some of the big guys have finally started pushing it into the real world, but since I’m operational and accessible on IPv4 – and many of the tools and some of the OS network stacks really haven’t seen that much public exposure yet -- so I’m not ready to take on that extra overhead. Perhaps if I was just launching an Internet presence and my ISP was only granting IPv6 addresses (as Cox or someone like that is doing) then it might force my hand. But for the moment the hackers probably have a better handle on all things (and vulnerabilities) IPv6 than I have time to keep up with, so I’ll hold out a while longer. IPv6 gets blocked completely at my firewall.
Since we’re never going to see a working IPv6 stack on any of the 3000s, we’re going to be trapped forever in the “compatibility zone” anyway. But that’s okay – I don’t think I’ll ever feel the need for my 3000s to be able to chat with my refrigerator or microwave or light bulbs.
Bartram refers to the IPv6 promise of enough IP addresses that anything smart enough to network can be given its own address. It could be a good while longer before IPv6 takes a practical role in IT management anywhere but at Internet service providers. But it's probably not a bad thing to study if you're seeking fresh employment, though. O'Reilly has a fresh book on the subject that includes references as current as Windows 8 and Windows Server 2012.
It's entirely possible that only Linux will be fully engineered to understand and adopt IPv6 by the time the next-gen addressing standard becomes practical technology. But it's become a different computing world that it was in the '80s and '90s, when HP routinely played catch-up to the more dominant vendors' standards. That was the typical HP tech strategy, even in those fastest-growth days of the 3000. However, it was an era when being first could be on par with being the best implementer. "HP wasn't always in the forefront," consultant Olav Kappert said while he reviewed his 3000 history with us last week. "But when it came out and it was done by HP, it was done right."
July 11, 2012
Web console resets, environment rebuilds, dumping form printers lead Hidden Value
I switched from an A400 to an A500 some time back, and I only realized I had not set up the remote web console after the console was down. Where can I configure this? This last time my only access was via VPN, or verbally over the phone. ("What can you see? Okay, so type...") I want to be able fix this myself next time. The console is the built-in one, and not an external box.
Gilles Schipper replies
You can configure your web console from the main console via the GSP interface. Specifically, the command you're looking for is LC (LAN configuration).
This command can be invoked even while the system is up and running by typing ctl-B (control and B together). For more help, at the GSP interface, type HELP, then HELP LC.
Craig Lalley adds that if you arrive at a password roadblock and need to clear a console back to the default login, "at the physical console, hit the GSP reset in the back of the system, then press P on the keyboard. It will reset the passwords."
I need to rebuild an environment from one HP 3000 system to another. Trouble is, we want to have groups from the same account end up on different user volumes. Is there a way to do this using BULDACCT?
Keven Miller adds
BULDACCT was made for processing complete accounts. Do BULDACCT CHC%VSACCT=MEDADV_1. Then edit BULDJOB1 for the other group, changing MEDADV_1 to _2
After Donna Hofmeister notes that "newacct has to be done on both volumes," Mark Ranft replies
What I usually do is use BULDACCT to move the entire accounting structure. Then I surgically PURGEGROUP and NEWGROUP (with the appropriate HOMEVS= and ONVS= options, plus CAP= and ACCESS= etc) to duplicate the special groups.
Jim Hawkins notes
MPE/iX RESTORE supports changing volume set specifications on RESTORE (vol, volclass volset) . That is, you can take files/groups/accounts originally on one volume set and place them onto another volume set.
We are still using multipart pre-printed forms and RS-232 dot matrix printers, all direct connected to our HP 3000 for our MANMAN purchase orders, invoices and checks. Obviously, these old HP printers are getting tired and problematic. Our immediate target is the printing of purchase orders. Are there ways to migrate from these form-based printers without breaking the bank?
Lisa Christiansen replies
One option that would work without requiring programming expertise is using ByRequest software from Hillary. We are taking the print ques from MANMAN and overlaying the form/jpeg to print the forms. We also have it set up so that the reports (invoices, POs, and electronic payments) can be emailed to the various parties.
Ed Stein adds
We moved to the ability to laser-print, or email purchase orders in PDF format, using eFORMz and eDirect from Minisoft. For vendors who require a faxed purchase order, we email the PDF of the purchase order to an email-to-fax service, otherwise we email them a PDF copy. We only laser-print purchase orders for vendors who either require a mailed copy or do not have an email address or fax number.
Can I configure a disk larger than 36GB on MPE/iX 5.5? The reason the customer is locked into 5.5 is they use Oracle 7.3 — so I'm now trying to set up a test bed to see if I can move the system up to 7.5 and still have all the wheels stay on. But we might not be able to migrate off 5.5, and the only way to get the enough disc space is to try going to 73GB drives. It doesn't look like 73GB are supported, but that doesn't mean someone hasn't been able to make them work
Jim Hawkins replies
Although your mileage may vary, there is nothing "unsafe" about trying to access 73 GB on 5.5. Of course, there is a 4GB cap on LDEV1, regardless of disk's physical capacity). What's unsafe is the fact that you're likely running on 15-plus year old equipment -- and running on disk-to-firmware-to-HBA combinations they were never tested by us at HP.
When researching "Large Disk" support in early 2000s, my observation was that disk size constraints were last re-engineered around the 4GB mark during MPE/XL 2.x (early 1990s). From there, most of the code worked pretty well up until 512GB, where we run off the rails of some 30 bit limits.
What didn't work okay up to 512GB was addressed by the "Large Disk" patches for 7.5. Things like REPORT running out of space to display a sector count, DISCFREE output etc. The only allocation change I made had to do with trying to spread IO across disks in a more granular way -- really an optimization, rather than an inherent limit.
Allegro's Stan Sieler adds
I remember that when Allegro encouraged HP to handle big disks, I found some definite problems in some obscure things — and that's why we filed a number of bug reports (including JAGad48770 in 2000) and then lobbied with Mike Paivinen, Louis Runnestad, and the CSY lab manager at the time to get really big disks supported. (Ironically, that triggered extra work for me... I had to make sure that De-Frag/X supported them, too.)
Unfortunately, I can't recall the details of what things had problems. Some of the things were offline utilities (for example, DISKCOPY, or DISCUTIL's SAVE command) that could be significant. Some were cosmetic (e.g., incorrect output from DISCFREE).
In the back of my mind, I have a suspicion that on some releases MPE might create some disk-based data structures that are too small — in a way that could potentially cause an overwrite of data ... but I really don't remember what it was, or which MPE release (might have been *very* long ago, sorry!).
My old notes say that 5.5 with PowerPatch 5 had an "official" max disk size of 18 GB and that I thought I'd seen a working 36 GB drive on a system. The same notes say that the base release of 5.5 officially had a 9 GB max disk drive size.