January 16, 2017
Older hardware, current support, new prices
HP's 3000 hardware is still being offered for sale. Hewlett-Packard Enterprise wants none of this 2017 action. Independent hardware brokers sell HP 3000s today, and by the looks of the pricing the transactions might be simply for parts. How could anyone operate a company while they rely on a $975 server?
The price is one data point on a wide spectrum of a sweeping array of servers, all offered on the 3000 mailing list this week. At the tip-top of the spectrum was a $3,175 system, first introduced early in the 1990s. At the very bottom was the faithful Series 918LX, priced at $675 including a DDS-3 tape drive. The newest computers came in at that $975 price.
The range of power ran from the 918 to the Series 989KS/650. It was a $290,000 system sold new in the late 1990s. The one on offer this week from the broker carried a price tag that was discounted $288,625.
Antiques? Some, perhaps, but not all. Series 918 and 928 servers from HP—both on the list—are running production systems today. Roy Brown, a consultant and developer in the UK and a member of the 3000 list, is running two Series 918s. One much newer server is holding archives at a migrated shop in Texas. While using the old, or very old HP iron one smart customer keeps support current for such boxes. Even when they're not on the critical path for computing.HP's sales ended in the fall of 2001 for those 918s and 928s. In that year the servers were sold for $3,700 at Phoenix/3000, the used hardware outlet operated by the North American HP 3000 distributor. In 15 years' time those boxes have held on to about 20 percent of their price.
The hardware is only one part of the ecosystem that's gotten inexpensive. We've heard of simple support agreements that are just $140 a month. At Republic Title of Texas, Ray Shahan said he's got an N-Class system hosting archived data. Shahan's company has a current support contract for this archival 3000.
It's been over a decade since that 3000 went into archive mode, so long ago Shahan said he's not sure anymore what the actual model is for the HP server. Independent support is around now to keep track of such details.
The original sales prices for those older systems "might be too depressing to hear," according to Terry Simpkins at TE Connectivity. Simpkins is among those 3000 veterans who remember when something like a $311,000 Series 997-500 included MPE/iX license fees charged by the number of users. HP placed value in its databases for the 3000, too. Non-3000 servers were less costly, until you added in the software HP included with MPE/iX.
Today's prices don't suffer under the valuation of included software. Transferrable 3000 licenses remain an audit-worthy strategy. Management rigor won't be stout for licensing software on a $675 backup server, though.
Moving onward to new prices will remind 3000 migrators of the old HP midrange pricing. For example, an LTO-5 tape duplicator—an device useful for anyone keeping archives of older enterprise data—costs $12,000 from TapeMaster today. That's an entry-level 1:1 unit that simply replaces older tape with new. Someday that duplicator will be discounted by 96 percent. It will be sold as scrap or for parts much sooner than a 3000. It won't be working in 2033, 15 years from now. The A-Class servers for sale this week for $1,200 are already 15 years old and are still working in shops like Republic Title.
It's not easy to say for certain it's depressing to see a $311,000 server go on the market for $3,175. The 9x7 line was rolled out before Bill Clinton took office. That a 9x7 is worth anything is a tribute to the stubborn economics of the 3000 line. As Clinton liked to say while winning office, it's the economy, stupid.
Follow the 3000 NewsWire on Twitter
for immediate feeds of our latest news
and more twitter.com/3000newswire.
January 13, 2017
Emulation review will air out all options
On January 26 MB Foster is airing the 2017 edition of its emulation webinar. The 40-minute show will walk 3000 managers through four emulation options. Last year's show had four very different products. Three will address the MPE/iX environment: how to get your applications onto the Windows OS. One will give you emulated hardware. In the first edition of the webinar, Birket Foster called the Charon emulator for 3000 hardware emulation "flawless."
The other three solutions — unless the lineup changes from last year's show — are all based in software methods to replicate databases and surrounding code. They are
- Ti2SQL middleware from Ordat (a holder of an MPE/iX source code license, along with Pivital Solutions)
- Marxmeier's Eloquence database environment
- MB Foster's eZ-MPE
The MB Foster environment emulation solution has been working for at least one customer. We introduced it in 2013. Here's our story from that year for reference. We'll all look forward to the update at 11 AM PST.
MB Foster is announcing a hybrid of solutions aimed at making migrations off the 3000 easier. The company is calling its offering MBF eZ-MPE, and it’s aiming customers at the native benefits of working in Windows once they make their transition. MBF eZ-MPE is a solution for HP 3000 sites that have a keen interest in transitioning to a Windows environment, while they preserve their company’s competitive advantage and legacy applications.
Knowing the computing processes of HP 3000 managers for more than 35 years gives MB Foster the insight to build a complete ecosystem, said the company’s sales and marketing chief Chris Whitehead.
“What we’re really doing here is we’re mimicking the environment that everybody’s accustomed to using,” Whitehead said. “To get all those nuances, you must have all the specific capabilities already there. With all HP 3000 sites they have some similarities. They have UDCs, file systems, KSAM that’s involved with MPE files. They all have an IMAGE database.”
Whitehead says the biggest nuance of eZ-MPE is its focus on custom code and surround code, “to transition to a supportable platform with the least amount of risk. The value of MBF eZ-MPE is its collective ability to mimic the HP 3000 environment — but aiming the customer at the advantages of the Windows environment.
January 11, 2017
Finding the knowledge HP once shared free
In 2008 was the debate, and I don't mean between our now-outgoing President and his rival. The debate was in your community about future knowledge. Where could you expect to find HP 3000 and MPE/iX manuals in the coming years? It didn't turn out to be where it was planned and proposed, but a manager of a homestead 3000 does have options today.
For many years now, MMM Support has hosted the full range of HP's manuals for hardware and software. As of this morning the website is offline, but it's probably a configuration error and not a sign of a company's demise. You'll find plenty of links on our blog to the hpmmmsupport.com site. The manuals are in PDF format and you don't experience any pop-up or page-takeover ads like you see in YouTube.
The newer player in the hosted HP manual arena is TeamNA Consulting. While it's a newer site, the venture is led by one of the older (in history) resources. Neil Armstrong, one of the tech wizards at Robelle, is the NA in TeamNA. Armstrong started with the HP 3000 more than 34 years ago—an era where MPE IV was still a common OS for the servers. Plenty of experience there, and plenty of manuals available too. More manuals than HP will share with the world today. The extra information is hardware documentation.
This wasn't the future the community expected in the days when official 3000 support from HP was nearly gone. Today that support is well-filled by companies like Pivital, the bedrock upon which homesteading and 3000 emulation rests.In the waning years of HP's support, when its Jazz 3000 server was HP's exclusive repository of what the community learned, such independent companies were supposed to hold the tech history of the 3000. Speedware and Client Systems paid for licenses to HP's technical content. The document licenses went beyond the Jazz whitepapers and jobstream scripts created by the likes of Jeff Vance in the HP labs. Those licenses at Speedware and Client Systems were supposed to ensure 3000 manuals remained available to the homesteading community.
Even though the two companies made good on promises to preserve the Jazz content, including programs, the manuals escaped re-hosting there. It was an oversight or perhaps a over-reach on the part of the companies; logging and making access to hundreds of manuals is a big job. Business focus changed as well. Those Jazz links at Speedware (now Fresche Legacy and absorbed with IBM work) are tucked away under hpmigrations.com. Not exactly the place where you'd look for homesteading tools.
This kind of confusion was not supposed (there's that word again) to matter so much. HP said it would keep its manuals online through 2015. A very long time for a corporation where those promises emerged from a division that was being closed down.
The website docs.hp.com lands you on a mostly-useless landing page at HP, Inc. That's the half of Hewlett-Packard with scant link to anything related to MPE/iX. A Google search on hpe.com today unearthed those HP-hosted manuals. Well, some. At this moment they're a collection of 7.x documents, 269 of them, plus a tracer-file for the Jazz content that goes nowhere. That link above is 436 characters long, something that looks like it's going change based on how HP Enterprise keeps rearranging its business. But there it is, for now, keeping HP's promise two years later than the 2015 plan.
As for manual hosting from the companies with continuing business and with knowledge of MPE/iX, the TeamNA and MMM websites are far better Web addresses. Today. Armstrong is like me, a half-generation younger than the most senior wizards in 3000 lore. He's got more years in the future with MPE/iX, probably. Knowing where to get answers and relying on experience can keep us in the 3000 knowledge game.
It's a intern-style assignment to download the 321 manuals off the HP site for homesteading reference. This assignment seems like a good idea. It's certainly easier than locating (and storing) those blue HP binders full of paper—which were the only bibles before PDF was our tabula rasa for knowledge.
January 06, 2017
Friday Fine-Tune: Logging, IP logins, SNMP
Due to a disk crash, I had to reload my HP 3000 system recently. I’ve just discovered that system logging has been suspended. How do I resume system logging?
Paul Christidis replies:
The reason for the suspension of logging was most likely due to a duplicate log file name. When the SLT was created the then-current log number was recorded, and when you restarted the system from your most recent SLT it tried to open the sequentially next log file. Said file already existed.
- MOVE the existing log files to a hold area
- Determine what logfile the system resumed on
- Perform a series of SWITCHLOG commands until the logfile number advances to one more than the highest number in the hold area
- Then move the held logfiles back to the pub.sys group — replacing the ones created by the series of ‘switchlog’ commands.
Is there a way to see the IP address associated with a particular login?
Any user with SM can do the following, for example:
HPSTDIN_NETWORK_ADDR = 172.16.0.30
The command :listf ci.pub.sys,8 will list all sessions and will show their associated IP address.
I’ve got an older model HP 3000 and I'd like to start monitoring it with SNMP for things like CPU utilized, jobs running or whatever other cool stat I can SNMP-grab. The problem I have is I can’t find the MIBs for it anywhere.
Andreas Schmidt replies:
First of all, I do not recommend the use of SNMP on the 3000, for performance but also security reasons. SNMP is not the securest protocol, as you know. Nevertheless, here are some hints:
• In the group NET.SYS you will find the SNMPUDC. This should be set in any case for MANAGER.SYS or on system level.
• Having set this, a SNMPCONTROL STATUS will show you the status of the SNMP subsystem.
• SNMPCONTROL START / STOP are self-explaining.
• The MIBs specific for MPE can be found in the document HP SNMP/XL User’s Guide
January 04, 2017
Future Vision: Too complex for the impatient
Seeing the future clearly is not simple, and planning for our tomorrows is a crucial mission for most HP 3000 owners and allies. Changes easily cloud the vision of any futurist—people who dream up scenarios and strategies instead of writing science fiction.
Or as Yoda said, "Difficult to tell; always in motion is the future."
Economics makes every future vision more compelling. A friend who just became a city council member reminded me of this when she talked about taxis and hotel checkouts. These things are the equivalent of COBOL and batch job streaming—just to remind you this post is an IT report. Disruption surrounds them. COBOL, batch, hotels, and taxis still keep our world on its feet. Nearly all of us reach for a legacy solution when we're finished sitting in the bathroom, too.
The new council member forwarded a futurist's article on Facebook—where so many get their news today, alas—an article that pegged so many bits of the economy that are supposed to be going the way of MPE V. (I think we can all agree it's really over for the OS that powered 3000s before PA-RISC.) The Facebook article says we need only to look at Kodak in 1998 when it "had 170,000 employees and sold 85 percent of all photo paper worldwide. Within just a few years, their business model disappeared and they went bankrupt." The timing is wrong, just like the timeframe predicted for total migration of the 3000 base. Was: 2008. Now in 2017: still incomplete.
The futurism you hear predicts things like "What happened to Kodak will happen in a lot of industries in the next 10 years — and most people won't see it coming. Did you think in 1998 that three years later you would never take pictures on film again?" Nobody did, because it wasn't true in 2001 that film disappeared. Neither had MPE disappeared by 2006. These predictions get mangled as they are retold. This year's IT skills must include patience to see the future's interlocking parts—a skill that a 3000 owner and manager can call upon right now. Since it's 2017, in one decade we'll be facing the final year of the date-handling in MPE that works as HP designed it. I'll only be 70 and will be looking for the story on who will fix the ultimate HP 3000 bug.
I love reading futurist predictions. They have to concoct a perfect world to make sense, and the timing is almost always wrong. Kodak took another 14 years after 1998 to file for bankruptcy. But after I disagreed with my friend, she reached for her own success at using disruptive tech to make her point. Even an anecdotal report is better than retelling abstracted stories. The danger with anecdotes is that they can be outliers. We heard them called corner cases in support calls with HP. You don't hear the phrase "corner case" during an independent support call. The independent legacy support company is accountable to a customer in the intense way a hotel operator commits to a guest. A guest is essential to keeping a hotel open. A lodger at an Airbnb is not keeping the doors open, or keeping jobs alive for a staff of housekeepers. There can be unexpected results to disrupting legacies. People demand things change back from a future vision. Ask voters in the US how that turned out last year.
You can call the OS running Amazon an environment, but Linux doesn't much care if you succeed with it or not. Investing in your success was what brought companies to HP's 3000. It's too much to hope for benevolence from a corporation. However, if we can all stop peeling the paint off of future visions, if only we can stick to the details and know that change doesn't come easily, or quickly, we'll be okay. They're still building hotels in spite of Airbnb, just like you're still maintaining COBOL code and modifying those jobstreams first written in the previous century.
It helps to get the facts right. AirbnB isn't a hotel company at all, and faces laws to curtail its business in US states including New York. It has few provisions for safety and fraud that can stand the test of a court matter. Watch out for auto-driving cars, auto industry. Another slice of folly is that this industry is headed for the scrapyard by the time MPE/iX gets to the end of its CALENDAR function. Auto-drive car tech is more decade away if it can evade the non-auto-drive cars that will litter the roads for decades.
Onward the bright future goes, with tech saving the day by saving lives and shutting down medicine as we know it. Who needs so many doctors when you have a Tricorder X? Revised rules for that tech-doctor device contest say the Tricorder X won't have to detect tubercolosis, hepatitis A, or stroke. "Goodbye, medical establishment," so long as you don't need those conditions detected. 3D-printed houses might be built, but who will assemble them: robots that cost no more than today's tradesman labor? You can get a 3D selfie today, and a gun's parts printed 3D. We were promised code that writes itself, weren't we, when object-oriented computing and Java swept in?
A sweep of futurism helped HP put away its 3000 business. The lives that are changed and jobs lost are not a concern of the futurist. Then another change enveloped the futurist who was certain that selling systems was a secure spot. This year there are rumors Hewlett-Packard could sell off its servers business. That one is a piece of data like those ever-present reports of HP splitting up. They were just rumors for years. Then it came true. Economics, not technology, made that come true.
Nothing is impervious to change, and to celebrate the marvel of technology upending legacy leads us astray. The future is a blend, not nonsense like "Facebook now has a pattern recognition software that can recognize faces better than humans." Or, "In 2030, computers will become more intelligent than humans." How many faces, and how many humans? I'm still waiting on the flying cars I was promised at the World's Fair of 1964.
My council member says that while in Amsterdam last spring she was struck by the stark difference between ornate 16th Century architecture downtown and the simple square box apartment buildings in the suburbs. "I asked our Airbnb host about it and suggested this: There has not been a reduction in human creative intelligence. It's just that in the 1500s all that creative energy was being put into architecture, and today it's being put into the digital world. Our host, a bright young Dutch digital engineer, smiled and said he agreed with me." As every good host does.
Then Uber arrived for the ride to the airport, I presume, using a car that the company wasn't invested in, driven by a person who was working a 12-hour day pitted against a fleet of freelancers that keep Uber's business model thriving for the corporation. "And no money changes hands" was my friend's punchline, overlooking the part of the Dutch economy using ATMs and currency, or the fact that you tip your housekeeper in currency unless you don't pay one.
The futurists want you to be wary. If you don't prepare for the future, "you're going down with Kodak, the cable companies, landline phone makers, Macy's, video rental places, printed books and tape backup media." Or you can find a life keeping yourself in the present, the happiness of the now. Making good things last longer is resourceful and sometimes inventive work. If the last 15 years have taught our community anything, it's that the future arrives slowly and looks nothing like we expect. Even my council member knows the value of legacy, asking "If we close down all our paper mills, who will make our toilet paper?"
January 02, 2017
Where's your backup media in the new year?
Here in the opening days of the New Year it's time to resolve your way to a cleaner 2017. People in the US and the UK voted for changes starting this year and they'll get some, including unexpected ones. You don't want unexpected change on your homesteading HP 3000 system, though. One of the simplest means to forestall a crisis is getting fresh media for your backups. MPE/iX system backups are no better than the media they employ.
Not long ago, a 3000 manager was looking for fresh DLT tape for his backups. Tape remains a part of the backup regimen at some shops, never more true than at a site still using HP's 3000 hardware. DDS drive verification should be among your new year's examinations.
New tape media is available for purchase. New tape all the way back to DDS-1 is on the Data Tech Store website. As a minimum 2017 homestead resolution, write a fresh backup onto new tape.
Disk backup will pull your homestead practices out of the 1990s. As DLT technology fades, cheap high capacity Serial ATA discs took their turn as the method of choice for large backups. Store to disk should be the next generation of MPE/iX backup. Using an SCSI to SATA converter, newer drives can capture backups from 3000s. HP's SCSI storage devices for 3000s are at least a decade old by now. SATA disks work well for smaller systems where Model 20 HP backup units are overkill.
The age of media can be offset by more recent design. Although it's slower and has lower capacity, tape is a seasoned technology. On the other hand, disk has the advantage of being engineered more recently. Pencils versus rollerball pens is a similar consideration. You know exactly how long a pencil can be used. Pens are more indelible but expire unexpectedly.
MPE/iX servers created using the Charon emulator from Stromasys can even employ SSD disks for backups. Verifying any media, new or old, should be on a manager's to-do list for 2017. It's even better to craft a regimen that rotates fresh media, whether you're relying on tape or storing to disk.
If your management style takes incremental steps into change, then using classic backup technology alongside newer host options might work. For example, even while using the Charon emulator, an external DAT device can be plugged in to keep backups. A few years back, Paul Taffel reported on DLT tape options for the Stromasys hosts that use what us old-timers call PCs. Charon will boot up on something as modest as a laptop, he pointed out.
I had a USB-connected external DAT 72 drive and plugged it into my laptop. It is very simple to hook this HP DAT drive up to any PC (server or laptop) running Charon HPA. The drive can read and write older DDS-3 and DDS-4 tapes, and is a very cost-effective solution. I picked one up new for $300. There's also the old-way, which involves adding a SCSI controller card to the server PC, and then connecting a SCSI tape drive.
Independent software support has embraced the mission of taking 3000 backups onto the Charon emulator. Keven Miller of 3k Ranger wrote a utility a few years back that will
- Convert MPE STD (Store-to-Disk) files to/from HPA/3000 Tape Image files
- Create an MPE STD file
- Convert the STD to a tape image file
- Transfer the image to your Charon HPA emulated system.
- Link the image to a tape device
- Put the tape online in your VM MPE
- VSTORE or RESTORE from the STD
You gotta love automation for backup processes, especially while making changes for the new year.
December 21, 2016
Wayback Wed: A Dark Day for Emulation
The future looked dim for hosting MPE/iX on virtual hardware in December of 2009. Your market had little news about the forthcoming Charon HPA 3000 emulator. That software was only in alpha testing. This was the month that Strobe Data announced it was curtailing development of its 3000 emulator. Your community headed into 2010 with the hope of a Stromasys success and HP's promise to announce the new independent holders of MPE/iX source licenses.
Licensing source for an OS that only runs on aging HP hardware has value, indeed. Support customers benefit from outside licenses. It's well worth asking if your support vendor has such a license. But as a model to extend the lifespan of MPE/iX in production, source won't do the work that an emulator does: create new boxes.
Strobe hoped to do that using new hardware. The company started as a venture to emulate Digital computers as well as the HP 1000 real time machines. Many roadblocks stood in the way of a successful 3000 emulator launch in 2009. Strobe's founder Willard West intended to sweep away some obstacles by obtaining new PA-RISC processors. The chips were to be integrated on cards that would go into high-end Windows servers.
But development takes money. The resources for non-Digital development at Strobe did not materialize. It would take two more years for the ultimate winner in 3000 emulation, Stromasys, to bring out a product that needed no special HP hardware—just a special OS to run, MPE/iX.
An economic lull at the end of 2009--HP was reporting declines in all of its businesses except services --set the 3000/PA-RISC emulation work onto Strobe's back burner. The rate of hardware aging made a profound difference to Strobe, a small concern compared to Stromasys.
"We are just trying to survive the lull in government orders right now," the company's Alan Tibbetts said during the dark of that December. "The trouble is that the sales of our [Digital] PDP-11 line are down. The PDP-11s became unreliable more quickly and we have sold a bunch of them in the past, but the easy ones have already been captured." The month was a moment like the epic one in The Empire Strikes Back. Yoda watches Luke fly off Degobah, his training unfinished. "That boy was our last hope," he said. "Now matters are worse."
"No," Obi Wan replies. "There is another."Stromasys announced in the summer of 2009 it was putting its PA-RISC emulation solution into alpha testing in the fall. We reported the Stromasys product "won't rely on hardware components, going to an all-software solution that provides cross-platform virtualization. The emulator will permit MPE/iX to boot up and run on Intel's Xeon-x86 processor family as well as AMD's PC chips." A stalled IT economy looked like it just claimed the leader in emulator work.
Tibbetts said that Strobe has leaned itself up in order to weather the lull and it continues to meet with customers to secure new emulator sales in the 1000 and PDP markets. He added that he's traveling to New York State this week to install an emulation product at BAE Systems, which is testing US military jet engines using 1985-era minicomputers.
The sidetracking of emulator work at Strobe can be viewed in more than one perspective. HP 3000 community members have long wondered if competing emulator solutions could survive in the MPE/iX marketplace. The market has a strong inventory of used hardware, much of which could be considered an upgrade for owners of older 3000s. Companies have already left the market who might have been emulator customers—had HP made technology licensing available sooner to the vendors' R&D teams.
Stromasys bridged that gap, finding new 3000 clients from companies who were not on obvious maps. Two years later the first steps of a public Charon showing appeared on the trail. Watching an emulation company run short of funding didn't spook Stromasys—it also had Digital emulation customers. It had a different concept, through, as well as a broader set of resources to make the design a reality.
December 16, 2016
Friday Fine-Tune: Login recovery strategies
We have changed passwords on MANAGER.SYS—and now we cannot locate the changed passwords, thanks to some staff reductions that made the new passwords unavailable. Any ideas on how to recover them?
John Stevens says
If you're logged on as OPERATOR.SYS, do LISTACCT on all the accounts that may have SM capability, then logon as the MGR/MANAGER of those accounts: TELESUP, and SUPPORT, and there are others; LISTACCT will find them. Login as those users (unless you don't have those passwords either) and LISTUSER MANAGER.SYS. Vesoft's MPEX might help ease some of this as well.
Duane Percox of QSS adds a simpler approach:
Using your favorite editor or other utility search for the string: "ALTUSER MANAGER SYS"
You will notice: PAS=<the pwd> which is your clue.
Steve Ritenour suggests that a logon to the TELSUP account will unlock the passwords.
Some 3000 managers believe the subject itself should be filed in a place not easily found. "These responses are all well and good," said Bruce Collins of Softvoyage, "but shouldn't we be thinking twice about posting this kind of information (i.e. how to hack an HP 3000) to the 3000 newsgroup?"
Bill Lancaster disagreed. Secrecy about password recovery is not really a secret, he said.
A Google search with the right words will yield far more dangerous information about the 3000 that anything in this thread. The genesis of this information being on public networks came through BBS’s in the 1980s. I’m afraid the barn door is already open.
Can the password for MANAGER.SYS be reset?
Gilles Schipper says
Not easily. If you can log on as operator.sys, you should be able to store off the system directory to tape, as follows:
Now that you have the directory on tape, you should be able to look around with fcopy (and the ;char and ;hex options) to find passwords for manager.sys.
John Stevens says
If you're logged on as OPERATOR.SYS, do LISTACCT on all the accounts that may have SM capability, then logon as the MGR/MANAGER of those accounts: TELESUP, SUPPORT, (I can't think of others right now, but LISTACCT will find them). Login as those users (unless you don't have those passwords either), and LISTUSER MANAGER.SYS MPEX might help ease some of this as well.
December 14, 2016
HP: Still a font of talent after all these years
It's Wayback Wednesday, but the 3000's history recall has fresh entries from the current day. A lot of HP 3000 sites turned away from Hewlett-Packard's offerings over the last 15 years. But more than a few have not, even after three CEO ousters and a split up of the company into consumer and enterprise parts. There's still something in the split-off parts to admire. A new book chronicles lasting HP lessons to the industry players who are lapping HP today.
Among the former: thousands of HP employees who've spent decades serving the HP customer. From engineering desk to conference presentation room, too many people to count or name have lifted the level of service. We heard from one today, Guy Paul, who once managed HP 3000s for the vendor and now is working on network storage for HP Enterprise. When asked what's remained stellar about the company where he's worked for 32 years, Paul pointed at people.
In a great book review and summary at the MIT Technology Review, the HP Way is among four lessons Hewlett-Packard's departed leaders still offer for top movers of our current day.
Make sure “culture” is about values, not practices. HP’s founders created what became known as the HP Way in several ways. Examples include insisting that the company enter markets only where it could make a meaningful contribution of valuable technology; asking employees to take pay cuts in tough times to avoid layoffs; and fostering understanding and collaboration between all corners of the company. “Management by walking around,” they called it.
But as the years passed, many employees came to equate the HP Way with particular traditions, such as the daily doughnut breaks meant to encourage conversation, or the right of top performers to earn full product-and-loss authority over their own product groups. That last one became a huge problem for [former CEO] John Young, because building computer platforms requires development of hardware, software, and other technologies that are all interdependent.
The future leaders of today’s tech giants should be prepared for similar grumbling if they have gotten too many employees accustomed to such perks as on-site massages, laundry service, and climbing walls. Dropbox said in a filing this year that it spent $25,000 in perks on every employee.
McKinney took note of the software-hardware interdependence of the mid-1980s Hewlett-Packard. His story about the era when the 3000 was growing fastest includes references to the HP 150, PC software created to enhance the value of such hardware, and a multi-division company that was ready to roll out something way ahead of its time called NewWave for PCs.
He praised HP in that oral history interview and can help us see how people like Guy Paul were attracted to—and stayed with—the HP that was built upon the Way.
When HP got in the minicomputer business...there was the HP 1000 and the HP 9000 and the HP 3000 and the HP 250 and then it kind of got all sorted out and they said, “Oh, we need [to have] one architecture and we need to be able to market [a product line].” One of the interesting parts about HP is it's just a very creative place and somehow it gets rationalized in time and [inter-divisional] doesn't become a general problem.
The part of HP that was split off, PCs, took its first steps in HP as a product to sell to 3000 customers. McKinney explained that 3000 begat PCs at HP.
In the beginning of this period there was still a hope that we could build a proprietary architecture [PC] product. Now obviously, how you sell it was one of the issues. Well I think in the beginning the [market for our PC] was major accounts who were buying the HP 3000. This is a little bit like the saying: “when the only tool that you have is a hammer, then everything looks like a nail.”
The 3000 was that hammer in an era where some top talent worked at Hewlett-Packard. It's refreshing to see that the subtitle of the new book is "Why Strategic Leadership Matters." The answer: you want to be around for decades making a difference and growing by 20 percent a year from 1958-1998. The HP of the Way did that and built the 3000, too.
December 09, 2016
Friday Fine-Tune: Driving Filesystem Checks
In the middle of a full backup, the HP 3000 at James Byrne's shop came to a system halt at 3 AM. It was the kind of halt that puts up those puzzling abort messages not even HP has fully documented. For example, about SA 1458, Robelle's Neil Armstrong said, "My experience with SA 1458 is that it is a catch-all abort. You need to look at the subsystem information and the only way to truly know the root cause would be to get a dump and analyze it." He referenced a webpage that breaks down the process of doing 3000 system failure analysis, too.
When a halt occurs during a backup, there's always the chance the 3000's filesystem has been injured. "I'd say run FSCHECK.MPEXL.TELESUP and check your filesystem," said Keven Miller of 3k Ranger. He added that a former HP support expert, Lars Appel, "instructed me that System Abort messages are in subsystem 98. From the MPE Error Messages Volume 2, Chapter 4, System Aborts, 1458 MESSAGE means A critical process is being terminated due to a trap."
Sure enough, power interruptions at Byrne's shop introduced damage to an Image database.
We reached the point last summer were we were toying with going off-grid simply to avoid the repeated power interruptions. If this sort of thing is causing damage then we will have to consider it. And it seems to; we now have a broken backward chain in one of our Image databases. A thing that I cannot ever recall. Coincidence? We are doing a backup, and then I will be using Adager to go in and take a look.
FSCHECK is an included tool on the 3000. It's simply there to validate extents and scan the table cache for missing files. Better tools include not only the legendary Adager, but independent support suppliers for the 3000 owner. People who know the fast commands of tools like CSTM. "What does your support provider say?" asked one support vendor. Self-support can be backed up by 3000-L questions. Some of the advice about the halt even ran to looking at memory issues. A provider can help eliminate these possibilities.Capricious power service from his utility — a government service that's been privatized — has extracted a price on Byrne's Series 918.
I am simply trying to find out if there is any way of examining whether or not we actually have a failing drive. We have spares but if there really is no need then I would rather not take the system down again after such a short interval. It has been a bad fall for our poor old 918. The system HDD was toasted by a whipsaw set of power outages on October 11; now our data disc is suspected of being ready to let go as well.
While running FSCHECK, Byrne was advised to use the commands
Check all Dev=all
FSCOUNT / 10000
He also received instruction from Mark Ranft on how to scan logs using CSTM to find disk errors.
Sign on as Manager.SYS. Do a LISTF LOG####,2 to find the start and ending Log files. Alter the log file number range in the commands and enter the commands in LOGTOOL.
list log=3404/3477 type=111 "device class"="hard disc",da,ca,"bus converter" out=LogOut1
list log=3404/3477 TYPE=111;'MGR CODE'= 241,242,900,901,951 out=LogOut2
The results are written to two files LOGOUT1 and LOGOUT2. I had this set up to run weekly on my systems. And if the files had errors in them, the job would email the results to me for review. You will see errors due to SCSI or FC resets on every boot, so check the timestamps to tell if the boot caused the error.
At Byrne's shop the Series 918 was recovered after Adager did its repairs. "During the Adager repair an infrequently occurring high-pitched but low volume sound was noted," he said. "This appeared to emanate from the 3000. We have not heard it since the Adager repair completed. A suspicion arose that we might have a disk about to lose a bearing."
Once the recovery was complete and the disk replaced, the trademark wisecracks of long-time 3000 vets began to arise. The sound during Adager's repairs "would have been the sound of the chains being dragged around the disk to put them back straight," said Alan Yeo, "and possibly the sound of a very tiny virtual Alfredo welding a few broken links back together."
Byrne noted that the problems with the Series 918 disks "started I was working on installing the 9.6 version of PostgreSQL on a new FreeBSD host. I wonder if the HP 3000 is throwing a temper tantrum? Naaah. Cannot be."
December 07, 2016
Taking Steps into Open Source with a Plan
A significant number of HP 3000 shops have employed Linux as a replacement over the last 15 years. (Yes, it's been that long that the MPE/iX community has been migrating or homesteading their systems). Over that time, open source software has become so mainstream that an architecture meeting often includes a line like, "Well, what can open source do for us here?"
If open sourcing a commercial datacenter sounds enticing—think of the size of the community you join, for example—it's wise to remember a commercial open source is the way to success. Downloading and testing is always essential, but adding open source has its best prospects when there's a commercial, paid support aspect to the choice.
This week we reported on one HP 3000 site where the system is making a slow exit. Harte & Lyne is still using a Series 918 with MPE/iX 7.5. The operations are being supplanted by what manager James Byrne calls FOSS: Free and Open Source Software. He's got his reservations about doing much more in that direction, though. Byrne said a more commercial—though not vendor-specific—approach to new architecture is in order.
HP was advising this to its enterprise computing customers as far back as 2006. Linux in the datacenter was a lot more exotic in that year, a time when HP was still selling support for the 3000. That vendor-based support is all gone by now, right down to the demise of docs.hp.com webpages where advice and training materials once lived. If you need 3000 support, third parties like Pivital Solutions are the best way to go forward, even if you're going away slowly.
An HP exec of 2006 said it only made sense to look for a supported FOSS design. David Claypool said
The rational thing to do is to choose something from a commercial company, whether implementations available and supported by a Linux distribution or non-affiliated Xen implementations like those from XenSource, Virtual Iron, and now Oracle.
Working together in such alliances was part of what FOSS was all about at the beginning. It would be another four years before Oracle would hire the departing CEO of HP, Mark Hurd, to run Oracle's software business. In 2006 all was pretty collegial between Oracle and HP.Campbell said, in a reply to the story we ran about choosing open source software
Certainly, it's possible and may even be prudent for some to download and run the bits from a raw open source project. But it's incumbent upon the adopter to understand the commitment to self-reliance that's being made if it's being used in any operational or revenue-producing capacity.
Linux was free until users understood they still needed a support provider to contact when things went awry. Support is the enduring part of any software relationship, and it's something critical for everyone who's using computers to drive an enterprise. Even HP 3000 shops need someone to call when the bits get out of alignment.
December 05, 2016
COBOL's Continuing Value for 3000s
The venerable workhorse of COBOL is often maligned during IT strategy meetings. The language usually has to make do with a lot less educational opportunity these days in universities, too. It is verbose and legacy and not ever going to captivate a ping pong table discussion about which platform development platform is best. There are perhaps only 1 million people in the world still trained in using it.
However, COBOL brings a single, enduring asset to the 3000s and other mainframe-caliber servers where it runs. COBOL is a standard, one that's exploited and extended and supported by many vendors, not to mention carried through decades of use. This is no one-man show.
You cannot say that about Powerhouse, or any other fourth generation language. If there's a standard out there for C-Sharp, or the wonders of Visual Basic, it is controlled by a single vendor. Powerhouse users are in a pickle. A single company, Unicom, controls the fate of all users employing the 4GL, and the vendor is jerking its leash on users. When Unicom said it was canceling the license of one customer, James Byrne at Harte & Lyne, then Byrne had a response.
"I am ignoring that," he said. "One cannot cancel a contract without cause."
He went on to point at what sets COBOL apart while he's choosing foundational software. "Not that we use it," Byrne said, "but there is a reason that COBOL is still around. The people who do not understand why are at the root of many of the problems with FOSS." That's open source software he's referencing, something that a vendor cannot cancel, but drifting toward commercial prejudices anyway."Actually, I have come to the conclusion that a great deal of the FOSS environment has exactly the same problem as [Ruby on Rails]," Bryne said. "Too many people are looking forward to their next contracting gig and padding their resumes when they introduce changes into projects. Too few are wondering about who has to maintain the trash that they leave behind."
COBOL won't regain its footing at Harte & Lyne, where a 3000 still supports the logistics vendor. But those ping pong developer tools are going out of vogue.
I have pretty much given up on Ruby-on-Rails, having slowly reached the conclusion that the maintainers are more interested in being fashionable than producing a stable and useful product suitable for enterprise deployment.
We will never return to proprietary software, but we are making some significant changes in our approach. We are presently migrating off of Linux onto FreeBSD—and we are moving away from the tech-du-jour crowd onto something more grounded in the commercial world.
November 30, 2016
This just in: Generalissimo Cobol is not dead
A favorite running gag on the most antique Saturday Night Live shows was Chevy Chase reading the fake news. With each broadcast he'd repeat this joke: "Generalissimo Franciso Franco is still dead." Same result, week after week. A situation with a lot in common with COBOL's current fortunes. Despite what people think they know about it, the Common Business Oriented Language still props up a vast swath of the business data across the world.
Nothing has changed with COBOL's fortunes since we last visited this topic with a podcast in 2014. During that year's spring, the NPR Planet Money radio team posted a show that blamed COBOL for the slow pace of money-changing in clearinghouse transfers. The mistaken report was like fingering English for the outcome of the Presidential election. Yes, the COBOL code in banks turns the IT cranks. The result is not the fault of the tool, but how it has been used. Yes, English was used in the 2016 campaign. [Insert joke about Twittering here.]
Our COBOL correspondent Bruce Hobbs pulled this story back into the light this week. He pointed to an article on the HackerRank blog, examining COBOL's not-dead-yet status once again. If you like numbers, the article included these above. Its still a language that supports 80 percent of all point of sale transactions and routes health care to 60 million patients a day.
To be fair, one of the sources of that graphic is the company still selling COBOL, Microfocus. But Gartner is also cited, an impartial consulting giant. In the NPR show the reporters interviewed an exec from Fiserv, a vendor who might have known better; they made some of their fortunes selling Spectrum/3000 for credit unions.
In the HackerRank piece, the author quotes an article from 20 years ago that surveyed why COBOL has held on so long.
COBOL does the 4 essential business tasks better than most modern languages today:
The capability for heterogenous “record-structure” data
The capability for decimal arithmetic
The capability for convenient report generation
The capability for accessing and manipulating masses of data (typically made up of heterogenous data structure).
“COBOL is either good or adequate in all 4 (except for database access and GUI construction, they were designed into the language from the outset), whereas the COBOL replacement languages, like Visual Basic and Java are good at few if any of them,” notable software engineer Robert L. Glass says.
Since the COBOL community's average age is 55, and the estimated 2 million IT pros who knew the language in 2004 declined by 50 percent since then, the technology that's as old as any Chevy Chase joke on SNL will see a new spotlight soon. Even in replacement, old skills will be in demand. Technology reporter Ritika Trikha looked to the future in her article.
As taboo as COBOL might be in the ping pong rooms of modern startup-driven culture today, its influence and irreplaceability will result in a spotlight on the dinosaur language again. Businesses must figure out who will maintain their mainframes when COBOL programmers retire in the near future.
November 25, 2016
Friday Fine-tune: Adding disks and IP blocks
Is it possible to add a disk drive "on the fly" without doing a reload?
Jeff Kell replied:
You generally have to shut the system down to install and cable the disk to avoid electrical/interface problems. The usual approach is to use SYSGEN to configure the new device on the path where it will reside, keep the new configuration, shutdown the system, install the disk and do a START NORECOVERY.
Once the disk is recognized by the system, you can add it to your running configuration as follows (assuming the new drive will be LDEV 5 in the system volume set):
> newvol mpexl_system_volume_set:member5 5 90 90 (DISC,SPOOL)
[For details, see "Volume Management", HP Part No. 32650-90045 or "Performing System Management Tasks" HP Part No. 32650-90004.]
This will add the volume to the system volume set, but it also has some side effects. Since the new volume is "empty" and the disk space allocation routines attempt to "balance" loads across drives, all of your new files and transient space will be allocated on the new drive until it's capacity approaches that of the other volumes. This will create an I/O bottleneck on that drive, at least initially.
You could selectively :RESTORE certain accounts (or the whole system) to try and balance the allocation. You could also perform an INSTALL and a :RESTORE for better efficiency, but at the cost of a great deal of time. There are also certain third-party utilities that will balance disk utilization across members of a volume set. These utilities work online on a running system and don't require any downtime.
The network configuration of our HP 3000 was originally set up with one block of IP addresses. Now I need to add another block of addresses. Where do I add these in NMMGR?
You can add an IP address using NMMGR the following way:
- After typing NMMGR, select "Open Directory" .
- Then select "Update Dir."
- Now select the "Add" option (F5.)
- You are placed in a screen where you can enter the IP Address of the machine. The type is generally set to 1( IP).
- Now press the "Save Data" (F6) option, back out of NMMGR, and you are done.
November 23, 2016
Mailing news from the HP 3000: an old skill
Internal mail hosts remain a crucial tool in datacenters, even some running MPE/iX. "You still host your own email?" is not a question you'd only pose to a crazy manager. An organization's security standards can be so high that no outside mail server will be trusted. In the earliest days of email, 3k Associates built and sold a beautiful native MPE mailing system, Netmail/3000. It's a smart mailserver, meaning it doesn't require that an organization's e-mail be piped through an Internet provider's mail server for final delivery. Then in the late 1990s, HP's lab started the long process of porting sendmail to MPE/iX.
Now some 3000 sites are looking at how to replace their 3000-based mailing software as they migrate. One of them contacted us this week to ask about an alternative to sendmail. Linux is their migration target, after a history using the 3000 that goes back to the days of HP Deskmanager. Tim O'Neill shared a story while asking about an alternative to sendmail.
I saw that FreeBSD Unix has its version of sendmail. Seeing reference to FreeBSD made me recall a story about FreeBSD running on an old HP 3000, maybe a Series 70 or an early Spectrum system. I think I have read that FreeBSD is at some sites still running in production mode, as MPE and MPE/iX are. It also made me wonder what the installed base of FreeBSD might be — and how that compares to the installed base of MPE and MPE/iX on old hardware and on Charon hardware.
FreeBSD, like MPE/iX, has some surprisingly large companies using it. You might have heard about one of them called Netflix. Of course the Charon HPA emulator from Stromasys makes every remaining product and archival 3000 a candidate for the kind of longevity we see in FreeBSD.
Sendmail has a colorful history. The Unix Hater's Handbook devoted a full chapter to the software's vulnerabilities; sendmail comes from the Unix heritage, after all. By 2003, HP was still patching sendmail to shut down security breaches, although the breaching wasn't nearly as serious on MPE/iX as on Unix variants including Linux. Sendmail's open source capabilities are now under the banner of ProofPoint, the company that purchased the sendmail resources in 2013.
Sendmail's worldwide release was last updated in 2014. HP announced it was testing sendmail to place in the Fundamental Operating System in November, 2001—a month that's famous in the 3000's history for other reasons. But the software moved along to an 8.13.1 release in FOS. It's only one major release behind the worldwide open source version, now advanced to an 8.14 release. Sendmail also includes encryption.Sendmail has included encryption facilities since 8.11. That's where security capabilities descend onto the requirements. Encrypting mail is a common feature in commercial hosting solutions. Sendmail/iX sends mail created by and triggered from HP 3000 applications, given enough technical know-how.
There's a robust webpage about the 3000 mail solution that was started by Mark Bixby. He's the engineer responsible for lighting the fire of open source flames at HP. Keven Miller of 3K Ranger has updated and maintained the page and its knowledge about Sendmail/iX. The software itself is in your 3000's SENDMAIL account in a version-specific group named vuuff.
November 21, 2016
Middleware rescues a Quiz captive, again
Old friends can help with new challenges to homesteading. Minisoft's ODBC software stepped in again to get a 3000 customer away from the pricing schemes of Powerhouse and its Quiz reporting software. That ODBC link between MPE/iX and Windows databases and tools turned out to be the essential component in pulling a client away from Powerhouse, according to the Support Group's Sue Kiezel.
Kiezel said her support client got an eye-popping quote to move Quiz from a 9x9 to an A-500 server: $27,000. Like some sites who are learning about the new regime of pricing from Unicom, this Support Group customer was returning to Quiz support after years of no improvements to the former Cognos product. Quiz made its way onto many MANMAN installations in the during the 1980s on the ERP suite. Getting out from under that legacy required a reasonable tool to connect the data with more modern reporting.
Enter the Minisoft ODBC software. The middleware connected with SQL Server to build a reporting database, data that was used to create the Excel spreadsheets everyone wants to use. As we've seen before, Windows-based reporting solutions like Crystal Reports can carry the 3000's data into departments better than Quiz did.
"SQL Server has turned into a beautiful database," Kiezel says. "You don't need a database administrator for it. Because of this kind of connection, my users no longer need paper for their reports. The middleware opens it up for MANMAN uses, and Excel can make joined tables for reports. Instead of just sending out a paper report, I'm sending out a spreadsheet, with the first three sheets of them working like a visual dashboard."
Visual Basic does analytics in this kind of report solution, too. "We are now in the modern world," Kiezel says. The bonus? Finding an expert to tune up these reports is a $50-75 hourly charge, instead of the $200 hourly that a Powerhouse consultant will charge to beautify and enhance Quiz. There are features and solutions that are worth the extra cost you'll sometimes encounter in MPE/iX. But reporting doesn't turn out to be worth the extra expense in licenses and expertise — not when there's middleware to open up reporting options.
November 18, 2016
Friday Fine-Tune: Tricks with command files
I'm working on a command file on my HP 3000. Is there any way to have it copy part of itself into a separate (temporary) file?
Jeff Vance replies:
MPE does not support the Unix concept of ‘here’ files, where input data for the command can reside in the same file as the command, except in the case of jobs. But even in a job, you may not include inline data for a script or UDC invoked by that job.
The SPOOKHELP script may be of some use. This single script contains the help text for all of the SPOOK commands plus the code to search for and display that text once HELP xyzzy is entered.
How can we execute a command after a user enters the :bye command in MPE?
Olav Kappert replies:
It is possible to execute many commands after the bye has been entered. Simply create a UDC (maybe a cmd file) called bye.
The contents of the UDC for the command bye is up to you. This would be useful if you want to do statistics before the session terminates.
John Pittman adds:
Don’t let them do a bye. We don’t allow any users access to OP system prompt at all. They get a logon no break UDC that runs a menu, and when they end the menu, they get logged off.
Inside that UDC at exit time, we build a string giving user, connection point (LDEV or IP of their PC) connect time, CPU date etc and append it to a log file. Then we know when anybody last used the system, how many users are using different connections, or when different user names are using the same connection point.
November 16, 2016
Noteworthy dates drive views of the future
This week on the 3000 newsgroup, Alan Yeo of ScreenJet picked up the remembrance torch to note the anniversary of 2001's 3000 business shut-off at HP. About your resilient computer he added, "In some ways it seems to have survived in some places in better shape than the HP that announced they were killing it!"
We agree and noted as much in the Nov. 14 NewsWire article. I promised to make not such a big deal about the history of the event; instead I tied it to recent advice about a hybrid of local and cloud-based ERP alternatives.
That event brought some benefit along with all of its carnage. Canceling the HP business operations for the 3000 (never an end-of-life; vendors don't get to define that) also sparked the completion of the first PA-RISC hardware emulator from Stromasys. The software continues to assure us all that the aging HP hardware won't be our only option over the next 11 years or so. Remember, on Jan. 1 2028, at 0000 hours, the dates stop working. Not MPE altogether, however.
A fix for that date issue might become a project for some remaining support company which has an MPE/iX source license. As you might infer from a date in this month's political events, stranger things have already happened.
November 14, 2016
The best wishes for your long life: a Plan B
Congratulations to us all. This is the 15th anniversary of the "we're killing off the 3000" announcement from HP. The end-game hasn't played out like HP expected. In 2001 the company's management didn't see three CEO resignations coming over those 15 years, or the company being forced to split itself to stay relevant to enterprise IT. Those two events are related. Yes, the 3000 got its pink-slip notice at the HP of 2001. So did the overstuffed, unwieldy Hewlett-Packard. The company that lurched toward every business while stepping back from others. It took 14 years almost to the day, but HP is half the size it was: HP Enterprise is the severed sibling from 2001's family.
Inside the 3000's division during that year, no one was talking about emulating the 3000 PA-RISC hardware that the company would stop building in 2003. That's now a reality, a new development since the 10-year anniversary of this sobering date. Hewlett-Packard was going to lead four customers out of every five away from MPE/iX, delivering them to the Unix alternative of HP-UX. Windows was going to get new customers out of the upheaval, too. No one figured three of every four departing companies would choose a non-HP environment.
Here on this date in 2016, the idea of an environment as a crucial strategy is feeling outdated. IT directors always cared about applications. Now they're told they don't have to worry about environments. The cloud computing providers will do that for them. Except when they cannot provide the cloud. Behold (above) the map of Internet outage from last month on an ugly day.
The Support Group's Terry Floyd offered a Plan B strategy to the manufacturing customers of CAMUS last week. More than 30 companies using HP 3000s and MANMAN are in the CAMUS user group. Floyd's company is delivering a fresh alternative to help MANMAN sites move on from the 3000. But he also supports homesteading sites. With a foot in both worlds, he recommends staying safe by having a Plan B, even while you employ cloud computing for your future."I'm still a little bit paranoid about the cloud being out there," Floyd said on the 90-minute RUG conference call. (Keep in mind, he's bringing a traditional manufacturing site's IT onto the Kenandy ERP cloud solution, so he's being extra-careful.) One of the Support Group services runs manufacturing datacenters for some clients.
If any of you are thinking about cloud apps, you should think about a hybrid app. You'd have some stuff in-house on your own boxes, and some stuff out there on the cloud. For instance, we're doing EDI [for a client]. It's pretty much local. We'll be able to receive and send stuff even if the Internet went away for a day. It would kill us not to be able to do EDI. Even hours of Internet downtime would kill us in some situations.
Think about what you might consider really critical to your company—and think about putting some of that stuff in-house. Having shipping on a local server, for example a SQL Server, we'd be able to ship whether the Internet's up or down.
"Sometimes the Internet goes away for different people for different reasons," he said, and it's so very true. DDoS attacks are becoming a too-regular event for the world's Internet. When Twitter, Netfix, Amazon, Tumblr, Reddit and Pinterest can be taken offline at once, as they were on that map of Oct. 22, everyone needs to manage the risk. A Plan B once meant staying on the HP 3000 in spite of HP's community exit. Today it means keeping some computing local, no matter what your enivronment.
November 11, 2016
Friday FineTune: Internal disk plus VA array
FiberChannel Storage Area Networks and shared tape libraries became popular in the years after HP stopped making its MPE/iX hardware. The HP 3000 supports SAN from the XP series of RAID devices to the VA7100 disk arrays. But how much should you rely on a RAID or SAN device? Internal storage devices might seem to be yesterday's tools, but the modest drive inside an HP 3000 can still be very useful — even if a company has invested in the FiberChannel storage solution of the VA7100.
Moving to the VA solution has great benefits, as reported in a story about using a VA7100 array with the 3000s. But booting directly from a VA array — well, you'll need an N-Class server (native FiberChannel installed) or a very expensive HP A5814A-003 Fiber/SCSI router (if you can find such a thing) to employ VA in the 9x9s.
The Crossroads SA-40 Fiber/SCSI switch will link a VA array to 9xx 3000s. It just won't let you boot your MPE/iX system from any of its drives. Craig Lalley of EchoTech recommends the affordable Mod 20 arrays for boot capability.
Internal drives remain as important as the VA arrays for a Series 9xx HP 3000, or even to the XP line of HP arrays. Even important enough to even duplicate them.
A second bootable disk inside your 3000 can take some forethought, but can be essential to smooth recovery of an LDEV 1 failure. James Killam of HP once reported to the 3000 mailing list, "Keeping a bootable image of MPE on one of the internal drives... saved me once at 2 AM when we lost total connectivity to the XP array the system was attached to and we had some serious troubleshooting to do."
Donna Hofmeister, former OpenMPE board member, has noted:
I did one internal disc and it was expressly for memory dumps. A second internal disc with a bootable image would be wonderful insurance. It would take some planning to be able to manage it all, but there’s no reason why you can’t have two bootable discs. I’ll point out the obvious: if LDEV 1 is internal, and you have a multi-disc system volume, and the remaining system storage is on a disc array — uh, what’s the point? If LDEV 1 fails, you’re toast.
Hofmeister said she's had a drive fail on a VA array. "That array worked perfectly and switched over to the spare without a blink. Given that I had two systems sharing this array, I was more than pleased with how well it worked."
Drive failures are among the most likely of hardware problems using HP's 3000 devices. A second internal drive in a system can make a big difference in recovery time. The other way around drive failures is to make your way onto emulated PA-RISC systems from Stromasys.
November 09, 2016
A Response to Being Stunned: No Tribute
Citizens of the US woke up this morning to a turn of political events described everywhere as stunning. There's nothing anyone can do to change that today, but in the event of a stunning relicense quote for Powerhouse products, you can respond with software that preserves your reporting administration. Some customers using HP 3000s can stun right back by leaving Powerhouse, using software from Minisoft to pave their data's way.
Steve Suraci of Pivital Solutions told us that one of the HP 3000 GrowthPower clients he supports has opened up one of those stunning relicense bids. In trying to get their software back onto support with the vendor, the customer received only an offer to relicense the full version of Powerhouse. "The most current product doesn’t even run on the 3000," Suraci said, explaining the folly of the return to support tribute being demanded by Unicom this year.
It's easy to think of back-support fees, levied in a market the size of the 3000's, as tribute: money demanded for nothing in return except a promise of help. A small promise indeed for software like a Powerhouse suite that hasn't had one MPE bit improved in more than 7 years.
The demand made even less sense considering what the customer was using. Quiz, the reporting end of the GrowthPower application, was the only Powerhouse software running on the 3000. "They originally acquired the product embedded in their ERP application," Suraci said. "They ended up purchasing the Minisoft ODBC and recreating the necessary reports using SQL tools like Crystal Reports, SQL Server, and Access."
Minisoft's products have never had an acquiring entity like Unicom take over and then demand such tributes from 3000 sites. Returning to support is a noble practice, something a manager with integrity does. However, this is a good deed that can be punished by ignoble companies. Support returns are a tradition that can trigger back-support fees. You don't have to pay them, but then your data has to live software else to get its support. The situation mirrors the dilemma of more than half of those who voted in the US yesterday. They don't want their President-elect, but they want to be citizens, too. It'll be awhile to see how much tribute the new President will demand. HP 3000 data is in a luckier situation.Data hosted on HP 3000s goes wherever the tools like ODBC can take it. The reports then flow from non-MPE software like SQL Server or Crystal Reports. That GrowthPower site, new owners of the Minisoft ODBC software, are a small division of a very large corporation. Tribute is not about the size of the IT budget, al it's the integrity that stings when a company gets stunned. Responses to being stunned include resistance, as well as reaching for alternatives.
The alternatives are more affordable for the Powerhouse customer who's only got reporting to replace. The full-development installation of Powerhouse faces a much bigger problem when they get their demand for tribute. They have to move their data's house to another country, if you will—transforming their application's platform. One solution for that is the Core Migration software and services. The transformation is a mighty task, though—a bit like thinking you can become an expat after a lifetime in a country you thought you understood.
While the United States was very new, the young country was put on notice by France. Pay us a stunning sum, said the French, and we won't attack you. The demand sparked a classic cry of resistance from the era of Founding Fathers: "Millions for defense, but not one penny for tribute," said Robert Goodloe Harper. When a 3000 site finds a means to defend its investment in MPE, they're resisting all demands for tribute. When you're lucky, your resistance can be as straightforward as ODBC.
November 07, 2016
Work of 3000s Helps Preserve Democracy
Tomorrow is a very special day in America. In a land called the United States we're going to elect a President to unite us. The kind of future we work toward will be chosen on that day. I'd like it to be the same kind of future the HP 3000 community has always worked toward.
This computer is called a business server because it works to meet the needs of business. A business relationship is at the heart of manufacturing concerns, insurance organizations, e-commerce companies and more. Business is at the heart of good relations with others in our world. MPE/iX software has always been a part of good relations. Much it serves the processes of business like invoicing. Going Forward Together might as well be a way to say Make Relations Through Documents. Business documents are the bedrock of your community.
In the earliest part of our 21st Century, Wirt Atmar was holding a seat as the conscience of this community. The founder of vendor AICS Research railed at HP's plunder of loyal customers, then proposed a Plan B to resist needless change. It was a time of high passions. The most crass and base expressions of the IT pros in our world were on display in the 3000-L listserver in that era. But since this is a republic with freedom of expression, although that trolling was revolting, it was tolerated. Much of that era's tone seems gentle compared to what's assaulted our ears and our spirits since this year began.
Back in 2004, Atmar was teaching his community how affordable Web-based lecture software could give minds a common ground. His QCShow product followed QCTerm, and both of those sprang from the makers of QueryCalc. In an HP World demo and lecture, Atmar explained his belief about how an HP 3000 was an alternative to war and atomic armageddon. These are real prospects for an American future. It feels like a disturbing misfit that anyone devoted to MPE, and having built a life's work from it, should vote for anything but a diplomatic leader.
Atmar had a fascinating background, including a stretch of his life when he worked to estimate and calculate the effects of annihilation. Nuclear throw weights -- the number of tons of atomic bomb to destroy various numbers of people and structures -- were his everyday work as a scientist in a government defense contract. He said he hated every day of his life that he had to wake and perform that work.
In contrast, when he created business tools that delivered invoices and orders, he felt his work spoke to the very root of human decency. Invoices, he said, were the everyday diplomacy of enterprises and organizations. I agree to purchase these goods and services, each would say. I agree to make and deliver them as you ordered, replied each sales receipt. A world still sending invoices, he said, ensured that war and revolt was a poor choice. Invoices were an expression of peace and a shining light for democracy and capitalism.
Something approaching half of America has already voted in this year's Presidential election. For those who have not, asking if a leader should respect business partners, find allies, and preserve relationships with respect— these all are a guide for anyone who's ever programmed or managed an HP 3000. Nobody is perfect. Anyone who wants to lead us should respect invoices, contracts and agreements. Tearing up a legacy is a poor start toward the future. Every HP 3000 community member should agree on that, and agreement is a good start toward where we need to go. We don't need to migrate away from working together and moving forward. Rather than looking back, we should take a hand in making history. Vote tomorrow and make some.
November 04, 2016
Reporting software takes over for pricey 4GL
By some estimates the 4GL software from Cognos sat on 7,000 HP 3000s at the 4GL's high water mark. A very serious share of that installed base was using only the reporting tool associated with Powerhouse, Quiz. Manufacturing sites such as those employing MANMAN, plus other applications, relied on Quiz to produce reports for managers and C-level executives. In many instances, these Quiz licenses came without restrictions or separate support agreements.
These are the sites that never had much of a business relationship with Cognos, and none at all by the time IBM bought the 4GL suite in 2007. Some of these sites eventually felt they needed to buy support, though, and some believed maintaining a license was important -- even though they'd become Quiz users when they implemented their application. The majority of Quiz sites stopped paying for support long ago. Like many bits of MPE/iX software, Quiz was frozen in time, a day when a reporting tool could cost thousands to support.
It was a bolt-on module, something that customers could be taught to un-bolt when pricing got outrageous, though. Cognos used to try to tamp down the outrage during the 1990s about license costs. Renegotiations were common, because the default pricing maintained strategies of an era when Windows was not a lower-cost enterprise option.
Steve Suraci of Pivital Solutions supports HP 3000 sites as an exclusive business model. It's an all-3000 vendor. He checked in about the latest shock over Powerhouse re-license prices. In the era of of ownership by Unicom, the licenses have soared agin. But there's another option to letting Powerhouse lock up a company to a 3000 license.
Back in the day, Cognos was always out of their minds regarding pricing. When they were bought by IBM, they got much more realistic and started offering a seat-based licensing model. Then Unicom entered the picture and they lost their minds!
We have a customer that owned the reporting-only version of the product, but was no longer on support. The only option available from Unicom was to re-purchase the full-blown development product in order to upgrade. The most current product doesn’t even run on the HP 3000. Needless to say, we replaced Quiz with something more robust and much less costly.
October 31, 2016
A Scary Kind of October Surprise
James Byrne, a systems manager at Canadian logistics management firm Harte & Lyne, has reported a hair-raising development at his 3000 shop. A straightforward request to relicense Powerhouse from the MPE/iX version of the software to Linux resulted in an eye-popping quote.
The supplier of the software, Byrne said, has told him they want $300,000 to move the 20-seat license. Byrne noted dryly, "I recently had my decision to move our company away entirely from proprietary software validated in a most dramatic way."
It's always possible, when numbers like this surface on a Powerhouse relicense bid, that the wrong person in the Powerhouse business line has responded to a request for a quote. Byrne reported this exchange on the 3000-L mailing list, but didn't want to name the software vendor of Powerhouse. It used to be Cognos, but that stopped being true many years ago.
In a message of nine years ago, the debut of Powerhouse for Linux seemed tied to the fortunes of Powerhouse for HP-UX.
Cognos continues its ongoing commitment to its PowerHouse customers with the upcoming release of PowerHouse 4GL and PowerHouse Web for Linux. This is a direct port of the industry-leading application development tool that is so successful on other UNIX platforms as well as MPE/iX, OpenVMS, and Windows. User-based pricing for PowerHouse 4GL and PowerHouse Web for Linux is the same as for other UNIX versions. Please contact your Cognos Account Representative for availability.
Byrne said the exchange with the current supplier of Powerhouse licenses ended with a termination of the Harte & Lyne license for the software -- just after he was told the annual support fee for the relicensed copy was going to be $60,000 a year.Hopes ran high for awhile when Powerhouse became part of the Unicom Systems software and services business early in 2014. The corporation has a long history of serving the mainframe and IBM communities with products. This legacy business might have made Powerhouse an attractive acquisition more than two years ago.
But the product was acquired from Cognos by IBM just a matter of months after the Linux version of Powerhouse emerged. Even 2007, people wanted to say that Powerhouse was past its use-by date. It became easy to find companies using HP 3000s who were sticking with it, of course. The University of Idaho State was a notable installation, a 3000 site that's moved on to other platforms by now.
Quotes like the one mentioned in Byrne's post are a good reason to try to take a step away from a development platform tied to the rosiest days of 3000 data processing. It's not easy, though -- and doing the right thing by a relicense can generate quite the October surprise of a quote.
October 26, 2016
MPE/iX to private licensees: A new HP way?
Fifteen years ago HP was cutting its 3000 business loose and software vendors scrambled. A few of the bigger ones, like Adager, were looking for a way to buy the MPE/iX assets from Hewlett-Packard. Nothing could be arranged. However, HP recently started posting notices about its patented technology it's trying to license.
The IAM Market (free registration required) has started to hawk the intellectual property of both sides of the HP, a company about to mark the first anniversary of its split-up. Hewlett-Packard Enterprise is offering a range of patents, all designed to let a company use HP technology to serve business users.
HPE Patent Sale – Mission Critical Computing Portfolio
46 issued patents (41 US, 2 JP, 2 GB, and 1 FR) relating to servers and storage products for Mission Critical Computing (MCC). Key applicable areas include High Availability, High Reliability, Replication/Failover, SSD/HDD, System Management.
Except for that SSD element, everything in the portfolio could fall into the realm of HP 3000 and MPE technology. If only such a marketplace existed 15 years ago. More importantly, if only HP was actively licensing its IP back then. Something could have been worked out. Today, at least there's a mechanism for listing patents for sale and finding interested buyers.By the time the 3000 pullout at HP started to set in stone during 2002, the licensing discussion was being steered toward emulator-ready user licenses. Meanwhile, the source code licenses were more than seven years away from being a reality.
For many customers, the only issue that matters is the licensing of MPE to be used on an emulator that mimics HP 3000s running on Intel hardware. Rumors continued to abound that HP is proposing the destruction of a licensed HP 3000 for every MPE license for an emulator that a customer wanted to deploy. The 3000’s longest advocates are howling over that possibility.
“It’s clear that HP’s intention is to limit the MPE user community to the number of licenses at the time of its death,” said Wirt Atmar of AICS Research, “thereafter drawing the population constantly downwards over the years. This is completely opposite to the future that I believe is possible, where MPE would be distributed world-wide, at prices comparable to Linux distributions.”
Emulator licensing makes the Stromasys Charon product a realistic choice for companies keeping their HP 3000s in use, either as permanent archive machines or in production. But the software communnity was reaching for so much more in the months following HP's 2001 notice of a pullout. Perhaps those MPE/iX bits, as well as the related subsystems, are available today.
The only companies who've even seen MPE/iX source, to use as a support and development reference, are the eight licensees of the code. They don't get to sell it or release modified MPE/iX. But it's there as a resource for support providers like Pivital Solutions and software companies as well.
Any dreams of restarting an MPE/iX business would have to begin with IP licensed for commercial use.
Stranger things have happened. The HP WebOS software developed for the Palm smartphones, as well as the heart of ill-fated HP tablet, found its way into LG Smart TVs, after all. At one point, LG was planning a range of consumer devices that would use the HP IP which the vendor sold to LG. LG never got WebOS into its ThinQ line of refrigerators. MPE/iX, should it ever go into the market, might become an item of the IAM Market.
October 19, 2016
Come together to conference with CAMUS
Admit it. It's been a long time since you talked person to person about your HP 3000 with somebody outside your company. User conferences and one-day meetings for 3000 folk used to be as common as leaf piles in October. That's what happens when you live a long time. You can outlive your community and lose touch.
CAMUS, the Computer Aided Manufacturing User Society, has a way to reconnect. At 11 AM Central Time on Thursday, Nov. 10, the Annual User Group meeting of the organization will form around a conference call. Terri Glendon Lanza of CAMUS is organizing the call. It's free.
The agenda, shared by CAMUS member Ed Stein of MagicAire, is 10 minutes of CAMUS announcements, followed by general discussion with the Board of Directors and everyone on the call. It's manufacturing managers who make up CAMUS, but you might have questions about a certain emulator that earned its stripes in the Digital market before arriving to emulate HP's 3000 systems. Both Digital and MPE managers will be at this conference.
Or you may be interested in the new ERP replacement for MANMAN, Kenandy. Experts from the Support Group -- which is installing Kenandy at Disston Tools this year -- will be on the call. You might just want to know something about MPE management that could take only a minute to answer.
Send an email to Terri at email@example.com, or call her at 630.212.4314, to get your conference call-in phone number. The call runs until 12:30 Central Time. You might learn something, or get to show what you know.
October 17, 2016
Rebuilding Systems Faster and Better
I'm looking at how to save as much time as possible in rebuilding an HP 3000's software and directories. My options seem to be using STORE, versus the sysgen tape command "tape store=@.@.@". What's the best way to go here?
Donna Hofmeister of Allegro replies
Unless your system is small (like a 918 with 8-12GB of disc), you don't want to try to do a full backup via sysgen. If you really do a full backup then I prefer this syntax “store /;...” as it is self-documenting and you know that the Posix files will be backed up as well. (On older releases of MPE, @.@.@ did not back up Posix files <eek>)
You want to make sure that you run 'buldacct' periodically (and routinely). You also want to make sure that you are somehow backing up your directory (store /;*t;directory, for example). Between the two, you have belts and suspenders (for recovering your accounting structure).
On older releases of MPE, you want to make sure that the network is shut down prior to making your SLT tape. And it's still a good idea to have the system quiesced when making an SLT, since everything in the sys account (and .pub.sys in particular) will be locked while the tape is being made. Nothing quite like grumpy users to make your day.
Just as a matter of preference, you should normally do a BULDACCT @ at the beginning of the weekly full backup, then the DIRECTORY option along with ;ONVS=MPEXL_SYSTEM_VOLUME_SET, PRODUCTION_SET, etc as a belt and suspenders approach for that day we all hope never comes.
Mark Ranft of Pro 3K outlined the use of sysgen
Here are instructions for a complete backup of basic MPE/iX system via SYSGEN's TAPE option. It is best if everything fits on a single DDS (or DDS-2 or DDS-3 or DDS-4) tape cartridge, but it will ask for a second (additional) tape(s) as needed.
Note: I included a 'second_volume_set' which can be changed or removed
Note 2: The line below is >80 characters, so you have to know how to create a file so that this does not wrap (or make other adjustments.)
Step One - Create an indirect file containing the following as a single line...
Step Two - Create this job
:tellop END OF JSLTALL -------------- EOJ
Feel free to add a BULDACCT to this.
October 10, 2016
Duke diners deliver some wayback news
It's always a great event—since it's so rare now — to see 3000 folk gather in person. Last week an invite over 3000-L and other channels requested the pleasure of the company of anyone in the Bay Area who remembers — or works with — MPE and HP 3000s. The number of lunchtime diners at The Duke of Edinburgh pub was at the intimate level, which is not a surprise. What was interesting was how informed some attendees were.
"Some were finding out about the [Stromasys] emulator," Stan Sieler reported. He was among the few who were still working on MPE tasks. I was surprised that the news of the emulator was just arriving in October 2016, five years after the product's debut in the Bay Area.
In the fall of 2011, about 80 HP 3000 folk gathered at the last HP3000 Reunion. (I won't say final, because reunions tend to hold on until organizers and the ardent alumni lose the ability to travel, drive, and have meals together. We're not young, us 3000 folk, but we're spry.) The story of the Charon HPA product has orbited the MPE solar system for many months. Not everybody looks up at the sky to see the stars, of course.
Those getting wayback news about Charon included one who needed a free hobbyist license. That kind of license went off the market at the end of 2014, when Stromasys transitioned to an all-proof of concept licensing and sales plan. The PoC strategy has yielded a string of green-lit transitions to the non-3000 hardware. Hobbyist/freeware licenses got abused; free software was caught running in commercial settings. Other people might have failed at their no-cost DIY approach. You don't always get news of failures when you never knew about the attempts.
News travels slowly, especially for managers who are not in everyday contact with MPE and 3000s anymore. Sometimes 3000 news has traveled slowly for reasons other than simple oversight, or becoming busy with non-3000 computing.It's been embarrassing to see, year after year, that the events we publish as news just don't stick with all people who rely on 3000s. You can't get everybody in the loop, not on anything. (Okay, all people have heard of Donald and Hillary, if they've heard of the United States.) HP discovered these gaps in the news loop when it started to spread the word that the 3000 was finished. The company that created MPE called the end of its 3000 business an end of life announcement. Almost a decade after that first finale, the computer isn't finished. The HP we knew, that's finished.
The news of an end of life sometimes flows slowly, or too fast like in that End of Life fable above. This afternoon I heard someone register surprise that Arnold Palmer was dead. It's not just a popular soft drink; Arnold was among the greatest golfers ever. Late last night, Abby was pretty sure the actor Rip Torn wasn't alive anymore. Not yet true, and Not Dead Yet could be a regular magazine, sort of a more gruesome What Are They Doing Now?
When HP's news about the end of its 3000 business rolled out -- trumpeted by at least five publications, covered in ABC News, circulated in serious correspondence to the customers paying for HP support -- it took years to become universally-known. That 2001 announcement was still news to customers more than five years later. For other managers who knew, they kept it to themselves, since the computer was still working. What's surprising is that good 3000 news, like Charon HPA, hasn't arrived yet in a few quarters.
In a way, though, that's good news for Stromasys. "They're coming out of the closets," said product manager Doug Smith earlier this year about finding 3000 users who were on nobody's radar. When you're selling a solution that keeps good software in place, it has a better chance of surfacing than reports of the death of a close ally like HP's 3000s.
October 05, 2016
How to fail at mission-critical IT with 3000s
We recently tried to be helpful for a 3000 manager who was desperate to get an MPE/iX server back online in steady, reliable service. Our role was just to feed questions to the volunteer force of experts on 3000-L and then pass back answers to the manager. The experience led us to think about what any company should do to fail at using a 3000 for mission-critical service.
Be assured, following these helpful hints will ensure your 3000 cannot do its work.
- Do your support with someone who'll just help out from time to time. Save your support budget for your other servers that are mission-critical. Let the 3000 fend off errors with volunteer help.
- Let your inventory of spares of the 3000's moving parts take care of themselves. A power supply or a hot-spare CPU board takes up a lot of room; set aside space for more modern computer components. Someone will be able to find something soon enough when trouble comes up.
- When a software or network problem starts to occur, give the situation awhile to work itself out for a few months. Save your support budget for the time when things are crashing because they've gotten serious.
- When your support vendor bills you on your 3000, let that expense take the same place as less-critical services. This isn't a vaccine, after all. It's just support for mission-critical servers.
- Make it clear to your management you're saving money by using the 3000 in a mission-critical role. Reinforce the cost-effective nature of the use of MPE/iX by keeping the software on 15-year-old HP hardware.
- If No. 6 might raise attention you're using MPE/iX, keep the age and support matters internal to datacenter planning. A 9x9 with no support provider is a fine way to ensure the future.
If a 3000's performance is crucial to staying in business, then not doing any of Nos. 1-6 will be a better course for the health of your company as well as your career opportunities. Keeping the investment of MPE/iX applications in top shape is not simple these days. But not having a support expert on the budget, with a monthly retainer, makes success difficult to impossible. The factor of luck shouldn't be a part of your operational formula.
If a 3000 is crucial to a company's success, then a cost as small as $10 a day shouldn't be out of budget. Some 3000 support companies are glad to stay available these days for a nominal fee.
October 03, 2016
Emulation customers got all they wanted
Five years ago this week Stromasys was doing a full technical detail demonstration of its PA-RISC emulation software. Since then, such virtualization has become an everyday choice for interim homesteading (just a few years of use needed) or long-term plans, too.
The software got its debut in front of a sophisticated crowd: HP 3000 veterans at that year's HP 3000 Reunion. In 2011 skeptics were schooled and devotees bowled over.
The rap on emulator choices from out of the past was performance. That's gone away by now, because moving an environment to a quick-growing OS like Ubuntu Linux -- the foundation for the emulator -- gives MPE an accelerating train of processor improvements to leap onto. Itanium won't leap like Intel's Xeon chips will over the year to come with Skylake. Here's a surprise nobody saw coming: the ultimate Itanium chip, Kittson, began development in 2011, and it's still not running in HP's servers. To think, MPE/iX could've had that fate if HP had chosen to port the OS to that chipset.
HP 3000 hardware and MPE experts at the Reunion believed in Charon's emulation future. In 2011 there were more in attendance at the Reunion than could fit in a single-family home. What's still in the years to come is making a home for MANMAN on one Ubuntu-Charon partition of a big Skylake Intel server, and MANMAN's replacement Kenandy on another.Terry Floyd, founder of the Support Group manufacturing and 3000 support firm, posted glowing comments five years ago about the future of Charon in a CAMUS.org report. What he's foretold has come to pass.
It was amazing to learn that within a year, MANMAN (and everything else that runs on MPE/iX 7.5) will be running on Intel/AMD 64-bit machines. MPE Virtualization: what a home run! Dr. Robert Boers, who came all the way from Switzerland to give his speech at the Reunion, showed MPE/iX running on a small Linux PC costing about $600, and MPE/iX is expected to run many times faster than on an HP 3000 A-Class machine. They also had it running on Craig Lalley’s laptop in the same room; he’s been consulting on this project, but now it’s open to any developer with a good reason to download it.
It was non-obvious to me that MPE would need to boot up in 2 or 3 minutes, mainly because all the memory, IO, and disc checking had been done by the underlying OS (Ubuntu Linux in this case), but also because of the PDC rewrite they must have done. No more watching all the dots and 1s, 2s, and 3s etc. going by on the console for 10 or 20 minutes (or longer on large-memory HP 3000 machines).
Later, in a more technical briefing at the Reunion's hotel, Floyd noted that all the right answers flowed from Boers.
It was like Christmas and Boers was Santa Claus (there is a slight resemblance). MPE booted on both the laptop and the little Stromasys server Dr. Boers carried under his arm off his flight from Europe. Fun was had; DEBUG was run; Glance worked in Block Mode! Stan Sieler asked if MPE crashed in all known ways.
September 30, 2016
Earliest birds to eye Charon stick with 3000s
One week ago the 3000 Simulator Project rolled out a new version of software to simulate an MPE V Classic 3000. That news led to a look at the modern emulation product Charon HPA and what has helped make it a success. Diligent engineering and testing of the Stromasys product across the community started just about five years ago. One of the earliest vendors to green-light their software for emulation was a company who's still selling new customers on MPE software: Minisoft.
Founder Doug Greenup called last month to report on some new sales into your market, the one which established his company. He mentioned Minisoft's connection to See's Candies' HP 3000s. See's is using Minisoft's middleware, and the connection between emulation and Minisoft popped up when I found Greenup's earliest report on testing against Charon. Minisoft was the first third party company to announce their products were Charon-ready, including ODBC, JDBC, and OLE DB products. These were the days when PA-RISC emulation was as new as Clarence Birdseye's frozen food was in the 1940s. Greenup's report was so early in the Charon HPA lifespan that the Stromasys software was being helped into the market by independent consultants like Craig Lalley.
Craig [Lalley] gave us access to the Stromasys emulator to test some of our legacy MPE products. The HP 3000 terminal emulators under Windows and Macintosh worked fine connecting up via Telnet. We ran some VPLUS screens with no problems. Connections were reliable and fast. We also tested our middleware drivers, connecting and running queries.
The bottom line is our products worked like they were interacting with an HP 3000. So if any of our customers deploy Stromasys, we are confident our MPE products will work.
Charon HPA needed software vendors who were familiar to the 3000 community to step up and certify. It's satisfying to see that one of the earliest adopters of your market's emulator is still selling software to MPE/iX sites. We'd call those sites 3000 customers, but its possible the HP hardware has been replaced by Charon HPA. Which is precisely why it was good business to step up and demonstrate that the emulator worked just like an HP 3000. Works better, now that HPA is not five years older like those boxes with "HP" on the front.
There's your report. MPE/iX still running at high-profile candy manufacturer. New 3000 software still being sold in a few places. Stromasys now moving toward five years of support from the MPE third party vendors, support that started with Minisoft.
September 28, 2016
Meeting at Building D: the rarest 3000 link-up
Notices were posted this week on the 3000-L mailing list about a rare meeting next Monday, Oct. 3. At opening time 11:30, people who know and remember the 3000 will gather at The Duke of Edinburgh pub. It's a site popular enough with the MPE crowd that it's still called Building D by some seasoned community members. The Duke is on Wolfe Road, just to the west of where the 3000 grew up. As the 3000 group intends to arrive at opening time, it might be able to commandeer the snug (above).
In-person meetings for the 3000 community happen in bars and pubs by now. The last one we heard about this public was SIG-BAR's meeting in London in 2014. Dave Wiseman, a vendor and software maven whose history includes a software project called Millware for 3000s, set up SIG-BAR. The 2014 meeting was announced so far in advance that people were able to plan their summer vacations around a gathering at Dirty Dick's. There's something about English pubs that attracts the 3000 crowd.
The Duke of Edinburgh is within walking distance of a mecca of the 3000 world, now departed: The HP Cupertino campus. Building 48 has been replaced by the rising concrete and steel of the new Apple world headquarters building. There's no word yet if the 3000 friends who meet Monday at Building D will bring their drones to take their tour of the Apple-ized HP campus.
A walk through the HP parking lot and across a cozy margin of poplars used to bring you to the Duke. "It's right across the street from where MPE lived," said Stan Sieler of Allegro while announcing the meeting. As of Monday, MPE's heart will be among the taps and chips of The Duke. Two years ago, Robelle's Bob Green said this about the last in-person meeting at that London pub:
We exchanged notes on the current state of the machine—especially the new emulator—- and discovered what each of us was doing. An amazing number of people are still doing the same thing: helping customers with their IT concerns. But in reality, most of the time was spent swapping war stories from the past, which was great fun.
As for that emulator, Charon HPA is in full swing by now, a certainty of life going forward with MPE/iX systems. For one additional lunchtime, a pub will be emulating the home of the system, even as it continues to move into a virtual existence.
September 26, 2016
3000-L connects again after a silence
As if on cue after our report about its silence, the 3000-L mailing list and newsgroup sprang back to life over the weekend. One problem solved by the 415 readers was how to identify if a store to disk backup is a LZW compressed backup file. A Tracy Johnson report also confirmed that a LISTF,2 can report the time of each LISTF, by writing a specialized job.
Meanwhile, a 15-year-old HP 3000 with network connection troubles got advice from the newsgroup's readers. A Series 969 running MPE/iX 6.0 would not be the first thing you'd choose for interfacing to an internal website. But when a 3000 has data that a user needs over the Web, the server is the place to go.
Trouble started to surface when clients access a webpage which then opens a telnet session with the 3000, grabs the info, and then returns the data to the webpage.
We’ve been getting more and more errors over the last year, culminating in non-stop Could not initialize data in path with TCP, which then blocked anyone accessing us through our webserver. We’ve tried many changes but cannot seem to get past this.
When it locks up, the HP 3000 keeps running but won’t accept any new sessions. Which means our clients can’t run searches. Which is very bad for us. Sometimes we can stopnet and startnet and it will work for a while, but then the errors start again. Eventually, we have to coolstart to be able to have clients log in.
Mark Ranft suggested "If they are already running in the CS queue, here is the likely cause. Is there some new monitoring in place? If so, it may not be behaving well on the network.
What happens is someone uses a telnet or ftp connection to monitor whether the network is up on the 3000. They send the SYN, the hp3000 answers with the SYN ACK, and then the 3000 receives a reset before the connection is complete. This handshake sequence causes this exact error.
Also inetd and other HP3000 networking improved greatly in later versions of MPE/iX. If they must stay on 6.0, they should at least be sure to install the latest patches.
A third party support company served this troubled user until the support vendor folded, "and the only options we found weren't affordable." Getting the 3000 back up will trigger a revisit of that situation. Any server with critical customer data on it—and doesn't have a support vendor—relies on the largesse of the 3000 volunteers of 3000-L. That mailing list did go without a new message for more than a month, a troublesome response time for a critical server.
September 23, 2016
Simulator for Classic 3000 gets third release
A third release of an HP 3000 Series III simulator is now available from the Computer History Simulation Project website. J. David Bryan of the project reports the software which simulates the old MPE V HP 3000 Series III now has a cold dump facility.
Entering the DUMP command simulates pressing the ENABLE and DUMP front panel buttons. The contents of main memory are written to an attached magnetic tape in a format suitable for analyzing with the DPAN4 program provided with MPE. The new SET CPU DUMPDEV and SET CPU DUMPCTL options specify the default device number and control byte for the dump.
Known as the SIMH project, the software is aimed at hobbyists who are using MPE V programs and utilities. Even though a power failure is not a desired event, the simulator has a capability of creating one. This is in addition to yanking the plug out of the laptop or PC running the simulator software.
"The user may simulate a system power loss with the POWER FAIL command and resume powered operation with the POWER RESTORE command," project notes from Bryan state. "The SET CPU ARS/NOARS command determines whether or not MPE automatically restarts when power is restored."
A full set of new features is listed in the release notes that accompany the simulator source files. Aupdated HP User's Guide covers the new commands is provided in Microsoft Word format with the source download. The guide is also available as a PDF file at an MIT website. A preconfigured MPE-V/R disc image available from Bitsavers was not changed for this release.
September 21, 2016
Power outage, or no problems? It's been quiet on the 3000-L. "Yeah, too quiet."
In the classic war movies, or a good western with Indian battles, there's the moment when someone notices the silence on the field. "It's quiet out there, Sarge," says the more innocent hero. "Yeah, too quiet," the non-com replies. That kind of quiet might be the sound we're hearing from the 3000-L mailing list today.
It's been five weeks without a new message on the mailing list and newsgroup devoted to MPE and its servers. Advice and solutions has flowed for two decades and more off a mailing list that still has 498 members subscribed. The number of subscribers has remained steady over the last three years. Like the number of migrations in the market, the exit from the list has slowed to a trickle. So has new traffic, of late.
The silence may not be ominous. In 2016 the 3000-L is used almost exclusively to resolve MPE/iX problems. The hardware posts are limited to the rare announcement of used server prices, messages that the members still howl at if they don't include <PLUG> in the subject. The server hasn't been sold by HP in more than a decade, but its owners still don't like to be bugged by sales messages. They solve problems in a grassroots manner. As a notable ballplayer once said, you can look it up. There might be no problems to solve.
However, no messages at all over 35 days sets a new record for the 3000-L quiet. This 3000 resource was much more lively a decade ago. And 20 years back? Well, HP was still selling enough 3000s in the fall of 1996 to be sending its new marketing manager Kathy Fitzgerald to speak at an Indiana RUG meeting about the new servers. There was also advice on storage compression, because compression-enabled DDS drives were becoming more common.
Good advice: If you can find a DDS tape drive from 1996, you should take it out of service. Your MPE server, no. And evergreen advice from the L is still available online. Jeff Kell, the deceased 3000 guru who started the server on a University of Tennessee at Chattanooga server, built it to last.In 1996 people wrote on the L that they understood most drive and backup software vendors recommend against using both hardware and software compression. "You should try each separately and use the technique that achieves the best result consistently," we reported. Mark Klein of ORBiT Software gave an interesting explanation of what was going on and the compression possibilities.
"Actually, there are cases where multiple levels of compression are useful. But first let me describe the various types of compression available.
"Hardware compression is typically LZW or some variant thereof. This type of compression uses a dictionary of repeating strings that can be dynamically determined on the fly and, as such, doesn't require the dictionary to be stored with the data as with other types of compression. There are other types of hardware compression available, but LZW is the most common found on compressing tape drives. LZW can also be done in software.
"Since the compressibility of the data really depends on the data itself, there are instances where negative compression will be achieved as well as instances where very large files can compress down to almost nothing. In fact, I've seen an instance where a large, multi-Gb database that was mostly empty got compressed into less than 32K using LZW.
"LZW is not effective in trying to compress something already compressed with LZW. This can result in negative compression (the resulting data actually gets larger). For that reason, I wouldn't recommend using LZW software compression on top of LZW hardware compression.
"Another type of compression is called run length compression. This is in essence a combination of a length tag and a string. The length indicates how many times to repeat the following string. For example, a line of 80 blanks would be represented by (80," ").
"Now, using a combination of RLC and LZW one can achieve better levels of compression than with one or the other method. So, if you want to use software compression with a hardware compressing tape drive, I would recommend using RLC compression in software."
September 19, 2016
Re-SUSAN services: off-label, or standard
As the 3000 servers age, their components are failing. It may not be a common event yet, but when it happens, getting an HPSUSAN number transferred to new iron has some options. One of the alternatives is a mighty fan to forestall the re-SUSAN processes.
Pivital Solutions' Steve Suraci reports that HP's still servicing 3000 owners who need an older HPSUSAN moved to replacement hardware after a failure. "In our area HP still provides the service to officially update the SUSAN. That's how we'd deal with it, but I'm sure other providers would differ."
When a 3000 manager has no provider anymore, they're likely to look for an off-label solution. In the drug industry, off-label is a use of a drug for which it was not intended. HP never intended to give independent companies the ability to change an HPSUSAN. That's why its tools were protected with a lockword. Then again, HP intended to move MPE/iX to Itanium, and to serve 3000 owners with no end date for support. Everybody knows about intentions can turn out.
Enter Immediate Recovery Solutions. The Bay Area company's history is using software that gives one key HP support capability to owners of 3000s. The Immediate in the company's name refers to intent: To get a 3000 back online, if HPSUSAN is standing in your way, as soon as they can get access to your console,
If that seems rather intimate for a first encounter—saying here's my console on the Internet, and now do your best — then the value of a relationship with an ongoing support provider becomes plain to you. So on the first day a 3000 needs to be replaced, but keep its original HPSUSAN to preserve booting up old vendor software, the choices are three. Call your support company for standard service. Call Immediate Recovery and go all the way on your first date. Or look around for a hefty fan, if you're lucky.The fan story comes courtesy of The Support Group, where MANMAN customers go for their custom treatment. One server in the MANMAN world had its A-Class box begin to go out when it got warm in the computer room. That's the moment when a server replacement is on the decision tree.
With luck, calling a support company or taking that big plunge on a first date might be delayed by a fan. As with other older 3000 hardware, sometimes putting a big fan in front of the back of the server reduces the heat and eliminates the failures. Older hardware can develop problems when it overheats. We've been told that doing a vacuum of the server's case can cut down the overheating, too.
Immediate Recovery, for the record, is doing what it's done out in the open since 2006. Its SSPWD takes an HP lockword — designed to limit use of ss_update to HP’s support personnel — and delivers the corresponding password to let a support provider start and use ss_update. It's helpful to recall that ss_update, which lives on every HP 3000 still in use, does what HP used to do with SS_CONFIG. The HP of 1999 got very litigious about unauthorized use of SS_CONFIG.
“We’ve seen copies of SS_CONFIG which had a disclaimer, but it just so happens that ss_update doesn’t, or HP didn’t really care,” said Steve Pirie of Advant, a company that identified Immediate Recovery as a "software partner." That HP ss_update program reconfigures HP 3000 SPU boards.
We got a message from "Captain GREB," as the Immediate Recovery owner calls himself. "In reference to having HP come out and change the HPSUSAN on a replacement box to match the original box, we can do that for clients — and we can do it remotely if the client will temporarily connect the remote LAN console port to the Internet. We did one in Germany last month."
The GREB stands for Generic Replacement Box, although anything with an HPSUSAN isn't generic, since the U there stands for Unique.
As Suraci said, there are other companies who use non-HP means to reconfigure 3000s. "Give us a shout if you don't like HP's price for this service," said the Captain. We'd add that while it seems unfair to give HP the business to re-license 3000 hardware, nobody will ever ask for an explanation of that service in case of any audit. We're pretty sure that HP Enterprise knows its way around a license.
September 14, 2016
Dancing the Samba services tune, MPE/iX-style
Ten years ago this week we were promoting instructions on how to use Samba better on HP 3000s. Samba is "a group of programs that allows a Unix host to act as a fileserver for Windows platforms," according the MPE/iX documentation rolled out in 1999. The file-sharing and printer sharing software which has been a part of MPE/iX since the 6.0 release "allows Unix-like machines to be integrated into a Windows network without installing any additional software on the Windows machines. Many different platforms run Samba successfully; and there are nearly 40 different operating systems which support Samba." And many more now, a decade later.
HP brought features of Samba to the 3000 in a port called Samba/iX. "It is a solution for those wishing to access HP 3000 disk storage and printers (both networked and spooled from MPE/iX) from common PC client operating systems like Windows." Samba/iX allows access to disk and printer resources of MPE/iX by providing standard SMB file and printer services that are accessible from PC clients and their applications. An administration tool called SWAT makes Samba so much easier to use.
Samba 3.0.22 is distributed by the following MPE/iX base patches. Your independent support provider should be able to help you round one of these up. They've got the latest functionality.
- SMBMXY6D (BT) for MPE/iX 6.5
- SMBMXY6E (BT) for MPE/iX 7.0
- SMBMXY6F (BT) for MPE/iX 7.5
The (BT) stands for Beta Test. HP never cut the 3.0.22 version loose as a general release (GR) version. For reference, the following are GR versions with less functionality.
- SMBMXG3A (GR) for MPE/iX 6.5
- SMBMXG3B (GR) for MPE/iX 7.0
- SMBMXG3C (GR) for MPE/iX 7.5
Even a total 3000 network newbie can get Samba up and running. Samba must be running before you can run SWAT. Here's some useful info when getting SWAT going.
In SERVICES.NET you'll want a line that reads:
swat 901/tcp # Samba/iX Web Admin Tool
In INETDCNF.NET you'll want:
swat stream tcp nowait MANAGER.SYS /usr/local/samba/SWAT swat
(adjust the path to your SWAT NMPRG)
If you’re running an older version of Samba, you’ll need to modify ‘/usr/local....’ to point to where SWAT actually lives (and case is important). The user needs to match the user in your samba daemon jobs. (For many, it’s MANAGER.SYS, for you it may be MGR.SAMBA) When you're connected to your MPE/Samba server through a browser to access SWAT, you'll be asked for a logon and password. This is a good thing.
After changing your services and inetdcnf files, all that you should have to do is give inetd a swift kick (e,g, :inetd.net -c ) Check inetd’s $stdlist after doing that and you should see that it brought in the new configuration.
In your browser point to http://xxx.xxx.xxx.xxx:901/ (where xxx.xxx.xxx.xxx is the IP of your 3000). Or you can use the name of your 3000 too.
When updating Samba and Apache config files, some are picky about how their records are terminated. Robelle's Qedit can make the needed adjustments. Be sure to know what version of MPE/iX you have installed, including patches.
September 12, 2016
HP sells software business to boring buyer
Micro Focus, which has already bought Attachmate (nee WRQ) and Acucorp (maker of a COBOL that was once fine-tuned for the 3000) is now sitting on what HP was selling that Hewlett-Packard Enterprise calls software. Like Autonomy, for example. The latter is probably valued at one-tenth what the-CEO Leo Apotheker's HP board paid for it five years ago. Admiral Grace Hopper's invention has ultimately provided a harbor for HP's exit from the software sector. The buyer builds COBOL.
The entire transaction only costs Micro Focus -- makers of boring software that drives thousands of businesses -- $8.8 billion on paper. HP's is cashing out of software for application delivery management, big data, enterprise security, information management and governance, and IT operations management. With Autonomy in the deal, the company HP purchased for $11 billion in 2011, HPE gets an albatross off its back.
Here's one shakeout: Minisoft is now the only vendor selling 3000-ready terminal emulation that remains under the same vendor brand. WRQ has been absorbed, and HP's out of the terminal business they started with AdvanceLink in the 1980s. (Minisoft's still selling connectivity software to MPE/iX users, too — as in active sales, this year.) HP sells almost zero 3000 software today.
A Reuters report says the HPE move tilts its business mix hard towards hardware, with two-thirds of what's left at HP Enterprise now devoted to a sector with slim margins. HP has stopped much of its operating system development over the last 15 years, casting off OpenVMS and MPE/iX, then stalling HP-UX short of a transformation to Intel-ready software. Instead, MPE/iX got its Intel introduction post-HP, when Stromasys made its Charon HPA the gateway to x86.
NonStop remains a part of to HP's enterprise group and enjoys development, but it's tied to Itanium chips. Nothing left in the Business Critical Systems group -- HP-UX, VMS, NonStop -- gets any love anymore during HP's analyst briefings.
HP software, aside from operating systems, could provide a frustrating experience for 3000 customers. Transact and Allbase were strategic, until they were not. IMAGE got removed from the 3000-bundled status it enjoyed. HP had to farm out its ODBC lab work to keep up during the 1990s.
The deal between HP and Micro Focus gets more unusual when you see that HPE has to pay Micro Focus $2.5 billion in cash. In exchange, HPE shareholders will own 50.1 percent of Micro Focus. HPE wanted to get its software out of its enterprise business and into the hands of a company with business success in software. Micro Focus built its rep on embracing backbone technology like mainframe connectivity and COBOL.HPE's CEO Meg Whitman said that Micro Focus knows how to invest in software. The company, which owns the Reflection product line, is supposed to keep HP's software stable.
"Micro Focus' approach to managing both growing and mature software assets will ensure higher levels of investment in growth areas," Whitman said, "like big data analytics and security, while maintaining a stable platform for software products that customers rely on."
Reliability and boring are sometimes conflated, but a stable platform is often built upon software with both attributes. UBS analyst Steve Milunovich, who tracks HPE, said HP's sell off of assets is "strategy that works well for current shareholders, who gain significant ownership in better-run businesses." A company whose backbone is COBOL now owns HP's software assets — a line that lost its COBOL compiler when the 3000 was dismissed.
September 07, 2016
HP remains in HPSUSAN update business
Close to 15 years has elapsed since HP chose to step away from the 3000 business. However, the vendor is still serving the needs of any customers who require an HPSUSAN ID to be refreshed onto replacement 3000 hardware.
We looked at this situation several weeks ago. For a customer who's looking over a move away from HP's 3000 hardware — but wants to remain on MPE/iX — Charon HPA from Stromasys is the logical choice. Going with a virtualized PA-RISC box can help sidestep a complication while staying with MPE. Replacement hardware will need either a refresh from a software vendor to accommodate the change in HPSUSAN. Or, in an extreme case, the HPSUSAN of record from the retired hardware would need to be flashed onto the permanent storage of the 3000.
Steve Suraci of Pivital Solutions, a comprehensive 3000 support practice focusing on MPE/iX, gave us an update on the ways to move an HPSUSAN. "In our area, HP will still provide the service to "officially" update the HPSUSAN," he said. "That's how we would deal with it, but I'm sure some other providers would differ."Support providers who continue to work in the community can do magic. If a software vendor has gone out of business — and there's no way to get a copy of software to integrate with the new HPSUSAN — you'll be looking outside of your datacenter for help anyway. One source would be to check on HP3000-L if there's no indie support company for you to call. It's a thought, although it's worth noting that the August traffic on the 3000-L mailing list weighed in at 24 messages for the month.
A better choice is to find your indie support company and let them guide you through a complex process. Many 3000 customers have no worries about third party software vendors going out of business. These sites operate with their own in-house applications and use tools and utilities from bedrock vendors like Adager, Vesoft, or Robelle. Powerhouse found a new home with Unicom.
Hewlett-Packard still keeps the lights on for licensing issues around MPE/iX, even in 2016. It's a good bet the vendor never imagined they'd be needed to keep production business servers online that far into the future.
September 05, 2016
Labor of homesteading lifted by advice
Today in the US we celebrate Labor Day, a tribute to the respect that workers earned during the labor movement of the 20th Century. Many offices are closed including most states' offices. Here in Texas organized labor works in the shadows cast by a business-sotted political engine. Nobody needed a labor movement and its human rights back when the 20th Century started, according to the politicians controlling those times. Mother Jones and other heroes who were radicals got the 11-year-olds out of the coal mines of West Virginia, as a start. Machine guns were employed by the powers in charge to oppose that movement. You can look it up.
Homesteading customers face labors too, and they have long struggled for respect. Their work is no less important than the heavy lifting of migration was. Migrations have tapered way back. It's easy to say there are now more companies working to keep 3000s in production than companies working to get off the platform.
If you are lucky enough to have a holiday today, thank your precursors in the labor unions. For a good look at what labors a homesteader should work on, here's Paul Edwards' homesteading primer from 2004. Homesteading tasks are little-changed by this year, with one exception. All customers have moved the labor of their 3000 support to third parties. The Web resources listed in Edwards' primer are much-changed, however, with a few exceptions.HP’s Web site at www.hp.com knows nothing of 3000s, except for the printers using that number. HP has become HPE.com.
HP manuals are no longer at docs.hp.com. The best independent collection is at HP MM Support. HP did not keep a promise to archive all of the manuals that homesteaders still use.
The HP Jazz site for utility MPE/iX programs and job streams closed in 2008. It's been cloned in large part at Speedware's HP legacy page
Interex passed away in 2005. There's been no user group replacement.
Still operating, from Edwards' list: OpenMPE at www.openmpe.com; the HP3000-L mailing list; and the NewsWire. Thank you for your support of our labor of love.
September 02, 2016
Open launch has become a workaround tool
Fifteen years ago this week I put the finishing touches on a Q&A with Jon Backus. He might be best known to one group of 3000 managers who flagged down his taxi-like service of MPE education — his Tech University had independent experts whocarried people from one point in their MPE careers to the next, better trained. An MPECert program was part of the venture that went into business just before HP changed its mind about continuing with 3000s. Tech University offered an alternative to Hewlett-Packard training classes, vendor-led education that was on the decline in 2001.
However, there's another milestone in his career just as well known. He launched OpenMPE as 2002 began, starting with a conversation with then-lab manager Dave Wilde. On the strength of that talk, the advocacy movement ultimately delivered MPE source code to third parties. It did take another eight years, but hopes were high at the start. HP named a key lab engineer to a board of directors. Minisoft donated middleware and MPE software from some of its licensed 3000s.
Backus began it all when he launched a discussion group on the Internet to explore the ways MPE might be preserved by its customers after HP steps away from it in a few years: a homesteading option. The group moved quickly to a consensus that open source methods didn’t fit MPE very well.
“The feeling and desire is very much not open source,” Backus said at the time. “The vast majority feeling is a migration of support and control of the entire MPE environment, including IMAGE, to a new entity. The source would continue to be closely controlled, similar to the way it is today.”
Starting a education group for HP server customers was a bold move. We interviewed him as one of the last 3000 experts to sit for a Q&A before HP's November 2001 exit announcement. August 2001's HP World was the last show to offer any HP hope for the server. Without OpenMPE and its work to capture that source code, however, to independent support companies such as Pivital Solutions, the trade secrets of MPE/iX would be lost. Instead that source acts as workaround and custom patch bedrock to help homesteaders.
Source for MPE/iX was not the initial goal Backus proposed for OpenMPE, though. The whole of the 3000 business would pass to a third party in his opening gambit. HP took months to even respond to that, saying the computer's infrastructure was decaying. Tech University was already addressing the brain drain before OpenMPE was born."You gradually have a mind-drain of how to use the operating system to the fullest, how to use the third-party utilities to their fullest," he said at HP World 2001. "You end up stuck in a legacy mind-set. Just because the 3000 was created 30 years ago, doesn’t mean it’s frozen in time. It’s evolved. The paradigm shift is that your knowledge of the platform needs to evolve right along with the platform.
"People bash HP for not offering more training. But until you push the boundaries of what your 3000 can do, you don’t have any right to pick on HP for not doing more."
One of the 3000's best HP friends at the time was Jeff Vance, who subsequently spoke for the vendor's intentions from a division-level viewpoint. OpenMPE's ideal of getting the 3000 to a new home outside HP would test the strength of a community that had just been cut off from the vendor.
“We could see if the ecosystem is still deteriorating at the rate we’ve determined, or if customers are willing to accept, say, IMAGE support from a third party,” he said. “That would be my guess at how we’ll get out — and that may lead later on to true open source.”
Vance said that HP didn't have plans to keep its MPE enhancements engineering team together beyond October 2003. As it turned out the team put a few enhancements into the community beyond that date, including an SCSI pass-thru module and a means to connect larger disk storage devices to MPE. Vance said HP resources would be vital to making any new entity successful in extending MPE’s life.
“It has to come soon,” Vance said of HP’s decision on how to help OpenMPE. “We have to make a pretty important decision, and we have to do it quickly. The longer we delay, the more the infrastructure decays.”
This isn't a story with the happy ending Backus and the advocates dreamed about in 2002. But seven companies got limited source code licenses just as HP closed down all of its MPE operations — more than eight years later. If you do business with one of the support companies with a license, that source is there to help solve a problem if needed.
August 29, 2016
How Good Things Are Slow to Change
Five years ago this week I was debating Apple's place in the future of tablets. The iPad was roaring along with more than 60 percent of the share of tablets shipped at the time. I bought one for my wife a few months later, to help her convalesce following a hip surgery. It was an iPad 2, and it's turned out to be the equivalent of a 9x9 HP 3000. It might run forever.
My debating point in late August of 2011 was Apple would not be chased off its leadership of market share anytime soon. In 2011 nobody offered a tablet featured with apps and an infrastructure like Apple's. I heard the word "slab" to describe tablets for the first time. That label predicted that a tablet could become nothing more special than a PC. White box, commodity, biggest market share will eliminate any out-sold competitors.
The trouble with that thinking is that it's the same thing that drives the accepted wisdom about the future for datacenters still using MPE/iX and the HP 3000. Last Friday I attended a 20th work anniversary lobster boil at The Support Group for Sue Kiezel. She left her datacenter career on MANMAN systems to become a part of Terry Floyd's consulting and support company. All through those years, HP 3000 experience has remained important to her work. There's years ahead, too, years with 3000 replacements -- in their own time. Slowly, usually.
Those 20 years also track with the Newswire's lifespan. It's always a chipper afternoon when I visit the company's HQ out in the Texas oaks near Lake Travis. In addition to things like barbecue and cake -- and last Friday, lobsters large enough to crowd a deep pot--reminders of the success of the 3000 are often laying about. Last week I noticed flyers and documents outlining software from Minisoft. Not all of that software is MPE-centric products, but it is all designed for any company that still makes and ships products using a 3000-driven datacenter. Even if that datacenter is hooking up iMacs to MPE/iX, a specialty Minisoft has come to own completely. The 3000 users who remain in the market believe they have a good thing. Change comes slowly to good things, behavior which mirrors human nature.Change came slowly to the iPad's market share of shipped tablets. It took three years for the shipped-per-quarter numbers to drop below 30 percent. At one point they were below 20 percent -- this is share of units shipped, not total overall share of tablets in use. Then the iPad rallied and grabbed more sales. It was and remains a good thing to use if you need a slab computer.
Like the HP 3000s and those MPE/iX users, the tablets made by Apple are built to last longer. That iPad 2 which first sat on Abby's lap while she healed from her hip? Still working every evening here, five years later, streaming Netflix all through the night and delivering emails. Another model of tablet which captured 16 percent share that fall, from newcomer Amazon -- well, those Fires are well-extinguished now. It's not a snipe hunt to find a Fire from 2011. More like the pursuit of a heffalump.
What's similar to the tablet-slab derbies is the way the ownership shifts. People leave iPad ownership when cost of acquisition becomes the primary factor. Why pay the $400-plus when an LG or a Samsung is less than half as much? Why keep using MPE/iX when Linux can drive less costly hardware? Ownership is about much more than capital costs, whether it's an iPad or an MPE server. When the pad -- Abby just calls hers "my computer" by now -- is doing what's needed and doing a good job, then it gets to stay.
And the 3000 and MPE are helped along by companies that retain experience and expertise in products and professionals. Companies with a realistic view of the long term (things will change, but slowly) and devotion to keeping that solution running well. After eight years of using iOS mobile devices, phones and slabs, I finally got my hands on an Android tablet. ATT did the Android brand no favors by giving it to me for free, unprompted. The phrase "We're gonna give you 40 acres, and a mule" rattled in my head after the ATT business rep told me about my upgrade.
Using Android is different than iOS, but in one particular way it's as different as a mule and a Caterpillar tractor. I don't expect this modest LG G Pad to outlast an old mule. It was inexpensive, but as one owner said on the BestBuy site where you can have the tablet for 99 cents, "If you are looking for the cheapest 8-inch tablet with LTE service, this is it, but one gets what one pays for."
And sometimes you get more than what you pay for because it lasts so long. It's easy to find statistics on how much Android holds over iPad in market share. Proof that MPE/iX and its experts have a slim market share is easy to find, too. It's harder to see how many five-year-old tablets are still in everyday use. Or how many MPE-based applications are pushing into their third decade of service. Good things change slowly. That's a blessing in an era littered with tweets that announce a new world order every day.
August 26, 2016
Expecting the Best, Even During A Disaster
This week marked the onset of cheaper air fares. August 23 was the official day for lower fares to be posted by airlines. A fare between Austin and Bejing -- the country where a dozen HP 3000s are driving a manufacturing corporation's operations — is down to $863.
So the impact of airline companies' failed disaster recoveries will recede. There are fewer people to strand when a system goes dark like the one did at Delta Airlines. The disaster was centered around a single building in the Atlanta power grid. It led to people tweeting “I’ll never fly your airline again.” This is just life in 2016. Get used to it: instant reviews, dashed off in the heat of anger and dismay. Tweets motivate spending millions to do good DR.
But the assumptions are that legacy systems are to blame. "Legacy systems stay on way too long," said one blogger who's had some software experience as well as work at Boeing. "Vendor agreements, support and maintenance — and the pain of switching and upgrading a system that’s by and large pretty reliable and so deeply integrated—are things few CTOs want to touch."
Southwest Airlines had no legacy systems at work during its high-season meltdown. The 3000s had been turned off. The plan was to save money by getting more modern. The disaster recovery was not high on the budget list. Customers don't care about IT budgets. They expect the best, even during a disaster. Plenty of 3000s have come through hell and high water.
That reliability doesn’t come out of thin air. The track record the server built during the advent of ticketless flight operations is one reason it still drives manufacturing in places like China and airports serving See's Candies. Celebrating the days of MPE glory won't return it to those places where DR has failed, though. Turning back only happens when a system fails upon installation. Once you're in, it's hard to turn something away at the gate.
Tim O'Neill — a 3000 manager who qualifies for Most Devoted IT Pro to MPE — was moved by our report of a 3000 doing more magic than SAP could at one company.
Yesterday a new user began using our one remaining MPE application. I could say that utilization is growing. If I were a little smarter, I would be able to rewrite the application in C (or some other new programming language on MPE) give the application a Windows look and feel, and then customers who are currently asking to manage their data in the way that only this application does might say, "I want a system like that." And Stromasys would sell them Charon systems.
Charon is ready. The new programming language, not so much; Java was a candidate, but not for long. In that magic alternative world, the thrill would be new MPE customers buying hardware. "I would think I were dreaming," O'Neill said. We can settle upon the dream of keeping MPE alive where it's working. There's still business out there.
One reason business is still in play is that people expect the best. Any company whose product could get you killed, or injured, or create a sleep-in-the-terminal kind of event, should be expected to put in enough DR to avoid a disaster that’s not an act of God. Nobody expects to read in the ticketing side of the Delta website that “You should know we don’t have millions to improve our disaster recovery. Have a good flight, and may the odds ever be in your favor.”
August 24, 2016
Some 3000 magic is beyond SAP's powers
SAP has taken the place of HP 3000 apps in the last 15 years. Not easily and not completely, in some cases. SAP is known for its switches—choices in configurations that sometimes shape the way a company does business. Some enterprises have to bend their practices to fit SAP, instead of the other way around.
At General Mills, SAP replaced just about everything. As it did, the IT manager there thought "If everyone buys and runs the same generic SAP software, how do you get a competitive advantage over your customers? We had spent years creating custom solutions and with SAP, we transformed the business to be... just like everyone else's."
Success stories are out there, too. Alan Yeo of ScreenJet said the SAP migration that he's helped with "went brilliantly."
"It's because the implementation was driven by the user departments who knew exactly what they wanted," he said. "They were given responsibility for doing it, so they used about zero external consultancy. All we had to do was extract the data from the HP 3000. Shame that we lost a good customer."
In another instance that Yeo is aware of, the company began replacing their financials and purchasing systems, went on to billing, inventory and sales. "Then they got to the clever stuff that the HP 3000 was doing and failed. 16 years later they are still running an HP 3000 doing the clever stuff."In public, datacenters like that second example are labeled an SAP success story. Every few years someone in IT looks and finds the HP 3000 magic. There is then an idea to replace the magic. Then there is the giving up, and the carrying on.
"Places like that will go off MPE at some point," Yeo said. But it won't be because they make SAP do what the HP 3000 does.
SAP has been called imanagement by golf course or management by magazine, at some 3000 shops. At one building component manufacturer, "senior executives wanted to play with the big boys, and since the big boys were all running SAP, we also had to run SAP. The implementation budget exploded. The initial promoters of the move to SAP—the ones who gloated when HP pulled the plug on the HP 3000—ultimately lost their jobs because of the huge cost and time overruns."
August 22, 2016
Replacements can trigger re-licensing, fees
HP's 3000 hardware is built well, but aging like any other server manufactured in 2003. Or even longer ago. The boxes are at least 13 years old. Hardware includes storage devices that can be newer. But eventually an MPE/iX server will need to be replaced. No iron lasts forever, even if the 3000 comes closest to feeling that way.
When a 3000 wears out or breaks down, something else that resembles the server takes its place. It could be a system just like what stopped working, delivered right to the datacenter. A new 3000 box will require some license transfers, operations beyond what HP expects for MPE/iX.
Third party software that checks for an HPSUSAN number will find a new one on HP's replacement hardware. This means a call to the software vendor for help in getting the application or tool to fire up again. Some software doesn't do this check. The call won't be required then.
The term re-license can include a couple of things. One of those things is a re-negotiation of fees for use. A few software companies in the MPE world have strict accounting for the size of a server. Only a straight-up replacement box will forestall an extra fee for these vendors.
If somehow you could replace an old 3000 with something much newer, while retaining the HPSUSAN number to skip all this administration, would you do it? What you might choose could have a much newer pedigree, too, iron that was built in our current decade. You might see where this is going.You'll be well served to get some expertise on this matter from your support provider. The one we talked to said replacing a 3000 with HP's iron can come with some administration. In the worst cases, it can be knotty.
"It all depends on how the software does its license check," the support company said. "If the software is HPSUSAN-sensitive and your HPSUSAN changed, you probably have an issue."
Support providers who still work in the community can do magic. If a software vendor has gone out of business — and there's no way to get a copy of software to integrate with the new HPSUSAN — you'll be looking outside of your datacenter for help anyway. One source would be checking on HP3000-L if there's no indie support company for you to call. It's a thought, although it's worth noting that the August traffic on the 3000-L is at 24 messages for this month.
3000-L can be a good resource in part because of its lurk factor. Of those two dozen posts in total this month, 10 of them were about installing an SSD in a PC. But some MPE veterans read it, and the 3000 network might be able to suggest help when a vendor has disappeared.
That newer, same as the old 3000 solution? It looks like it's could be the Stromasys Charon HPA emulator. Stromasys doesn't promise any re-license process will go without a hitch. Nobody can promise what other vendors will do. But when MPE/iX software reboots and the HPSUSAN is the same as it was—well, that could eliminate the need for administration on a server the same power as its HP predecessor.
August 19, 2016
Vendor makes its installs a key to emulation
Customers have not been crazy about paying for services along with their software. You can make a case for doing things differently when the expert arrives to put something mission-critical into your datacenter, though. Hardware integration included installing services for a long time, until the commodity era arrived. Software then slid into self-install territory with the advent of PC apps, and then open source.
Thing is, the 3000 community managers learned lessons from an era when they were sometimes as experienced as anyone the vendor could assign to their installs. By the end of the 1980s, though, the vendors often had sharper software engineers than most customers. But the MPE vendors didn't have big staffs for outreach with installs. Here's a tape, stream it like this. Call us if there's a problem. DIY system management was the first option.
Now, if you got a great third party support company, they'd help you with anything. Few software companies wanted to be in that business, though. Adager's Rene Woc would say they got called for every problem someone ever had with an IMAGE database. Sometimes the calls didn't even come from customers. After the call, there was sometimes a sale, though.
Finally, there was freeware. For the price, there was no reason to believe anyone would help install this at your site. Emails and websites gave advice. This was the moment when Charon HPA stepped in. People needed to see the new product working to believe in its magic. For a couple of years anyone could download the software on a single-user license and mount it themselves. The results depended on how adept your administrative skills were. Everybody likes to think of themselves as well-seasoned. It's sometimes less than true.
Charon HPA is a mission-critical part of enterprise computing. Although it doesn't emulate anything in MPE/iX, this is software that transforms an Intel processor into a PA-RISC engine. MPE users have lots of variations in their PA-RISC configurations. That's what happens after 40 years of commercial computing success.
So freeware Charon downloads ended a few years ago. Then over the last year-plus the DIY option has been ended too. "We do it ourselves to be sure it's done right," said one official at Stromasys. There was the freeware era, then the DIY era with customers installing themselves. Now it's the vendor-install era. The proof of this concept comes from a statement by the HPA expert for 3000 sites. Doug Smith says, "All of our installs are successful now."People who did the DIY route for HPA, and some who made a stab at plugging in freeware, have generated a few considerations while installing. These are mostly anecdotal reports from that DIY era. When you quiz them about issues, you hear things like IP address configurations and printer workarounds. There are some embarrassingly old printers out there attached to 3000s. We've even heard reports of DTC-attached print devices. Really, that's the kind of thing that's best replaced. It's not like the newer generation of printers is expensive, after all.
The undeniable consideration is the third-party software re-licensing for Charon HPA. Most of the push-back we hear about from HPA prospects revolves around costs versus the number of years needed to emulate. Migrating customers do a shorter-span cost analysis. We haven't heard of a single software vendor who's unwilling to re-license, though. Yes, every app and tool vendor gets to pick their price for this re-licensing. You charge what you believe you can get.
In one spot, new-ish 3000 systems are shipped out from a hardware support company to replace failing 3000s. It's the kind of thing that can forestall an HPA prospect. Interesting, because none of that replacement HP hardware is getting newer. Just different. Battery life alone on HP gear might give you some pause. Putting a fan in front of the 3000's backplane to lower the temperature to operating level? More common than you'd think.
Help on Charon HPA comes from Stromasys. Some 3000 sites are accustomed to asking their regular support and service providers to assist. But the buck stops at the Stromasys desk. Everybody wants it that way, even the customers. A vendor takes the lead responsibility in exchange for being a key to a stable, essential datacenter running 3000s.
August 17, 2016
Crashed IT Versus Staying On MPE's Course
Earlier this month Delta suffered an IT meltdown that made Southwest Airlines' disaster of DR look puny. Three thousand canceled or delayed flights went idle in a single day. A hasty DR mashup was using dot matrix printers at one airport. Delta was never a 3000 user. It's an easy retort to say, "Of course not. Nobody in the modern world of commerce would be staying in the 3000 business."
However. You exit a flight and go into the concourse this month, and there's a See's Candy kiosk. Oh yes, the clerk says, we sell right here and it goes straight back to the main office. And you just know, if you keep track of who's staying the MPE course, that the new point of sale terminal is tapping a TurboIMAGE database somewhere in California. Because See's stayed the course while Southwest veered away.
The largest candy shop company in the US was founded in 1921. See's operates more than 200 stores across this country, Hong Kong, Macau, and Japan, plus it counts on online sales. See's is owned by Berkshire Hathaway. Berkshire's iconic founder Warren Buffett called See's "the prototype of a dream business." Buffett certainly knows nothing of See's IT choices, but his managers surely do. He commented on See's dreamy business in a book published in 2012 — more than a decade after HP's plans for the 3000 dried up.
In another state, one of the biggest manufacturers of mobile air conditioning units manages their ERP with MPE. They're moving away from 3000 hardware, in a way. These days you don't need the HP badge on aged hardware to stay the course with MPE applications. You can virtualize and emulate Hewlett-Packard's iron. Yes, MANMAN is still an everyday tool at a company whose name is synonymous with cooled air.A leading AC maker. America's top candy retailer with a footprint that now goes beyond stores and into airport kiosks. The food in those airports' restaurants, some of it cooled in transit by the AC units. The 3000 usually was under the radar of analysts, mainstream press, and CIOs. That situation contributed to HP's business decision. But the business of running corporations is still entrusted to MPE in some places — transit locations where it's been easy to see when other IT can't get off the ground.
August 15, 2016
Poster anniversary lingers beyond sunburns
The biggest statement 3000 users made worked its way onto a front page. 847,000 OC Register readers took note.
Twenty years ago this month the HP 3000 community staged its most prominent protest. The stunt landed the server on the front page of a metro daily paper's news section for the only time in the 3000's history. It also produced sunburns and filled a football field. The lasting impact was memories, like so many computer stories. But a world record was set that remained unbroken longer than HP's product futures were intact for the server and MPE.
It was August of 1996 when a team of 3000 users, vendors, and developers gathered on the football field of Anaheim's Loara High School to build the world's largest poster. The stunt was also a message aimed at HP's executives of the time: Glenn Osaka, Wim Roelandts, Bernard Guidon and especially CEO Lew Platt. "Pay attention to the 3000's potential and its pedigree," the poster shouted. Acres of it, mounted under the Southern California sun of summer. Computerworld (above) was skeptical.
Summed up, the organizers led by Wirt Atmar unfurled 2,650 3-foot x 4.5-foot panels needed to say "MPE Users Kick Butt." Atmar was one of the most ardent advocates for the power of MPE and the 3000. He printed those thousands of sheets off a 3000 Micro XE, a Classic 3000 because why would you need a PA-RISC system? It drove an HP755CM DesignJet printer for two weeks, printing the required 463 billion pixels. Atmar said, after he and his employees loaded and drove the 687 pounds of sheets in a U-Haul truck from his New Mexico offices to California, that "moving the paper into the vehicle was our company's corporate fitness program."
They all had to be numbered and sorted and placed on the field. That was a spot where the winds arrived by lunchtime or so. It would be a race against the clock to build it, but the 3000 was always racing against an HP clock. The statement made for the server moved the needle for existing customers. General Manager Harry Sterling was just taking his job that summer and pushed for funding and lab time to bring the 3000 into parity with Unix and Windows NT servers HP sold. Often, it sold them against the 3000.
The image of the poster made it onto the Metro front page of the Orange County Register. The NewsWire provided lunch and recorded the event for our newsletter just celebrating its first birthday that month. We supplied sub sandwiches and pizzas, recording every request for things like a vegetarian kosher option. It was easier to get media attention than get a kosher veggie delivered to the Loara sidelines, it turned out.
There was so much white paper on the ground that the rising sun began to give the volunteers tans —and then sunburns. The project had to be assembled and taken down in less than eight hours, because football practice started at 4 PM. The field turns on its Friday Night Lights once again in about two weeks.
Computerworld noted that test assemblies extrapolated from a field trial showed that it would take four days to assemble, not four hours. The wind arrived as promised. A hasty trip to a local hardware store delivered 97 pounds of gutter nails to tack down the sheets. Each nail was gathered up at the end of the stunt, using the precision that only software engineers can supply for a computer they love.
More than 100 volunteers were organized and recruited using the HP3000-L mailing list. That nexus of noteworthy 3000 news had been our inspiration and font to unfurl the NewsWire at the previous year's Interex conference. Robelle reported on the show in its "What's Up Doc" newsletter, another staple of that era's news.
"According to Interex, 6,000 attended in addition to the over 2,000 vendor show staff. The Monday night keynote speaker was Scott Adams, the cartoonist of the now-famous The Dilbert Zone cartoon strip. The HP World '96 Daily wrote, "Never has the 22-year-old [sic] HP World '96 (Interex) conference opened with so much laughter and good feelings. Everyone left the room smiling and ready to buy an autographed copy of Adams' book Still Pumped from Using the Mouse."
Multiple sources of coverage, front page notice, a world record, a new general manager and fresh budget. What could go wrong?
The sunburns faded while the profile of MPE rose for awhile. HP later tried to usurp the record with a stunt inside a high school gym, but that was a different category—and challenge met—than the one the 3000 mastered. Grassroots efforts on high school grass kept the 3000 in the Guinness Book for years until then. Even today the largest poster, built in India, isn't so much larger than the one that was created by a community instead of a corporation.
August 12, 2016
How to purge UDCs on the HP 3000 safely
The software vendors most likely to sell products for a flat rate -- with no license upgrade fees -- have been the system utility and administration providers. Products such as VEsoft's MPEX, Robelle's Suprtool, Adager's product of the same name -- came in one, or perhaps two versions, at most. The software was sold as the start of a relationship, and so the relationship focused on the understanding the product provided for people responsible for HP 3000s.
That kind of understanding might reveal a Lewis Carroll Cheshire Cat's smile inside many an HP 3000. The smile is possible if the 3000 uses UDC files and the manager uses only MPE to do a file PURGE. Of course, PURGE ships on all MPE systems. Using that means you'll have to rebuild the UDC catalog. But even that's not enough.
Stan Sieler of Allegro shared a story about this recently. "We recently encountered a site where—somehow—an HFS filename had gotten into COMMAND.PUB.SYS. You can't delete UDC entries with HFS filenames, nor can you add them. I had to edit the file with Debug to change the name into something delete-able." Then there's the rebuilding of the catalog. Keven Miller has contributed a program that sorts and reorganizes UDC files.
There is a more complete way to remove such things from a 3000's storage. You're careful about this because eliminating UDCs with only MPE might leave a user unable to use the server. That grin that lingers is the UDC's filename.
User Defined Commands are a powerful timesaver for 3000 users, but they have administrative overhead that can become foolproof using the right tools. These UDCs need to be maintained, and as users drop off and come on the 3000, their UDCs come and go. There's always a chance that a UDC file could be deleted, but that file's name could remain in the filesystem's UDC master catalog. When that happens, any other UDCs associated with the user will fail, too. It might include some crucial commands; you can put a wide range of operations into a UDC.
When you add a third party tool to your administrator's box, you can make a purge of such files foolproof. You can erase the Cheshire Cat's grin as well as the cat. It's important because that grin of a filename, noted above, can keep valid users from getting work done on the server with UDCs. This is not the reputation anybody expects from a 3000.First you have to find all of your UDCs on a system, and MPE doesn't make that as straightforward as you might think. Using SHOWCATALOG is the standard, included tool for this. But it has its limitations. It can display the system-level UDC files of all users in all accounts. But that's not all the UDCs on a 3000.
MPE, after all, cannot select to show a complete set files by attributes such as program capability. Or for that matter, by last accessed time, or file size, or file security. It's a long list of things that MPE makes an administrator do on their own. Missing something might be the path to looking foolish.
Employing a couple of third party tools from VEsoft, VEAudit and MPEX, lets you root out UDCs and do a foolproof purge, including file names. VEAudit will list all of the UDCs on a server, regardless of user -- not just the ones associated with the user who's logged in and looking for UDCs. The list VEAudit creates can be inverted so the filename is the first item on each line. Then MPEX will go to work to do a PURGE. Not MPE's, but a user-defined purge that looks for attributes, then warns you about which ones you want to delete, or would rather not.
By using MPEX -- the X stands for extended functionality -- you can groom your own PURGE command to look out for files that have been recently used, not just recently created. MPE doesn't check if a purged file is a UDC file.
Such 3000 utilities provided the server and its managers with abilities that went far beyond what HP had built into MPE and its IMAGE database. Now that MPE is moving on, beyond HP's hardware, knowing these third party tools will transfer without extra upgrade fees is like ensuring that a foolproof MPE will be running on any virtualized HP 3000.
They're an extra-cost item, but how much they're worth depends on a manager's desire to maintain a good reputation.
In the earliest days of the sale of these tools, vendors were known for selling them for the price of the support contract alone. That's usually about 20 percent annually of the purchase price. If a $4,000 package got sold that way, the vendor billed for just $800 at first. It made the purchases easier to pass through a budget, since support at the manager-tool level was an easier sell. Think about it. Such third parties passed up $3,200 per sale in revenues in the earliest days. They also established relationships that were ongoing and growing. They were selling understanding of MPE, not just software.
This kind of practice would be useful for the community's remaining software vendors. This is not the time to be raising prices to sustain MPE computing, simply because there's a way to extend the life of the hardware that runs MPE. As the number of MPE experts declines, vendors will be expected to fill in the gaps in understanding. Those who can do this via support fees stand the best chance of moving into the virtualized future of 3000 computing.
August 10, 2016
Measure 3000 performance for datacenters
Measuring the performance of an HP 3000 used to be a leverage point for increasing investments. By now the numbers help justify continuing to use the server in a datacenter with newer boxes. "We think of our HP 3000s as stable, and even reducing in usage over time," says one systems manager, "though actually as the company grows, the data requirements and load on the 3000s increases."
One way to measure a 3000's footprint is the amount of memory it requires. Memory upgrades cost nothing like what they did even 15 years ago. But any spending at all makes that 15-year-old server suspect. HP's Steve Macsisak recommended sessions x 4, plus jobs x 16, plus 64 MB as the criteria for memory usage.
An HP 3000 uses as much of its memory as possible to make processing efficient. The design of the PA-RISC architecture makes memory the most important element of performance, after IO speed. It's not that unusual to see a 3000 using 100 percent of its memory, according to field reports. There's also CPU usage to measure.
CPU percentages can come via the REPORT command. Count up the CPU seconds used in the week, and divide by the total number of seconds available (604,800). But for all of this, it doesn't feel like a graphic report the rest of the datacenter gets from its Unix and Linux systems using SAR. There may be a program inside a 3000 that can help, even if the company never purchased performance tools from Lund. HP's Glance gives away its reporting power in its name, one manager has joked.
There's freeware available to create handsome graphs like the one at left, suitable for showing in a meeting about datacenter resources. Ploticus/iX was written by Andreas Schmidt. It uses data from SCOPE.SYS. Ploticus even works with SAR's data.
Since there's no port of SAR for MPE/iX, something else must stand in. Some systems have HP Scope, the software that dives in deep enough to produce report-ready numbers. It's not the smooth path a 3000 gets from Lund's Clearview Performance Manager. Scope is the HP Performance Collection Software sold by the vendor while it still had an active 3000 business.
Scope includes a program, EXTRACT.SCOPE.SYS, that permits the software to EXPORT its results to a text file. The manual for the software says it has three components.
SCOPEXL, if you are using an MPE/iX system), UTILITY, and EXTRACT. SCOPEXL is the performance data collector for MPE Systems. It continuously collects and summarizes performance data. UTILITY and EXTRACT are the host programs that let you interact with SCOPEXL and manage the data that it collects.
HP's Scope documentation describes how to use the collection and management software: how the host components interact; detailed command descriptions for each program; and suggestions on how to use the programs to analyze and archive data efficiently.