September 07, 2016

HP remains in HPSUSAN update business

Update buttonClose 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."

Read "HP remains in HPSUSAN update business" in full

Posted by Ron Seybold at 05:50 PM in Homesteading | Permalink | Comments (0)

Pivital Solutions: Your complete
HP 3000 resource

September 05, 2016

Labor of homesteading lifted by advice

Mother JonesToday 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.

Read "Labor of homesteading lifted by advice" in full

Posted by Ron Seybold at 07:21 AM in Homesteading, Web Resources | Permalink | Comments (0)

September 02, 2016

Open launch has become a workaround tool

Jon Backus 2016Fifteen 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.

Jon Backus 2001“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.

Read "Open launch has become a workaround tool" in full

Posted by Ron Seybold at 12:01 PM in History, Homesteading | Permalink | Comments (0)

August 31, 2016

What To Do To Succeed In Migrations

How-to-succeedIn the 3000 community a major manufacturer is making its way off its ERP system. It will take years. We've been told not to say who, but the more important element of this story is the what. As in, what not to do to make a clean move away from applications that drive finances and manufacturing.

It's been a struggle, but mostly due to poor project planning and project management. Migration partners who've served the 3000 community pride themselves on the planning deliverable. Without such good planning, "it's taken significantly longer than they thought it would, primarily because they chose to ignore warnings."

The top IT management refused to perform any business process analysis before beginning the project.  Business processes have been traced by MPE/iX applications since the 1980s. The software has been lauded for bending to the needs of processes, instead of the other way around. "They knew what they were doing, and didn't think we understood what it would take to implement new systems in our businesses."

Planning comes at a discount as well as with a price. You get the discount when you plan. You pay the price when you don't. Especially in migrating from a legacy system ERP, where the P stands for Planning.

Posted by Ron Seybold at 07:35 PM in Migration | Permalink | Comments (0)

August 29, 2016

How Good Things Are Slow to Change

Change for the BetterFive 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.

Sue KieselThe 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.

Terry Floyd-LobstermanThose 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.

Read "How Good Things Are Slow to Change" in full

Posted by Ron Seybold at 09:15 PM in History, Homesteading | Permalink | Comments (0)

August 26, 2016

Expecting the Best, Even During A Disaster

Aircraft-537963_1920This 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.

Read "Expecting the Best, Even During A Disaster" in full

Posted by Ron Seybold at 11:17 PM in Homesteading | Permalink | Comments (0)

August 24, 2016

Some 3000 magic is beyond SAP's powers

MagicwandSAP 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."

Read "Some 3000 magic is beyond SAP's powers" in full

Posted by Ron Seybold at 05:06 PM in Homesteading, Migration | Permalink | Comments (0)

August 22, 2016

Replacements can trigger re-licensing, fees

Arrow-1238788_1920HP'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.

Read "Replacements can trigger re-licensing, fees" in full

Posted by Ron Seybold at 09:20 PM in Homesteading | Permalink | Comments (0)

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.

Door-lock-407427_1280Thing 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."

Read "Vendor makes its installs a key to emulation" in full

Posted by Ron Seybold at 06:39 PM in Homesteading | Permalink | Comments (0)

August 17, 2016

Crashed IT Versus Staying On MPE's Course

Delta tickets downEarlier 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."

Mobile ACHowever. 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.

Read "Crashed IT Versus Staying On MPE's Course" in full

Posted by Ron Seybold at 09:01 PM in Homesteading | Permalink | Comments (0)

August 15, 2016

Poster anniversary lingers beyond sunburns

OC Register Poster

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.

1996 Poster ChildrenIt 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.

Wirt on the fieldSummed 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."

Poster and housesThey 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.

Read "Poster anniversary lingers beyond sunburns" in full

Posted by Ron Seybold at 01:46 PM in History, Homesteading | Permalink | Comments (0)

August 12, 2016

How to purge UDCs on the HP 3000 safely

Cheshire_catThe 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.

Read "How to purge UDCs on the HP 3000 safely" in full

Posted by Ron Seybold at 01:17 PM in Hidden Value, Homesteading | Permalink | Comments (0)

August 10, 2016

Measure 3000 performance for datacenters

Hp-1715a-oscilloscopeMeasuring 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.

PloticusThere'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.

Read "Measure 3000 performance for datacenters" in full

Posted by Ron Seybold at 08:45 PM in Hidden Value, Homesteading | Permalink | Comments (0)

August 08, 2016

August Throwback: Java and VPlus get cozy

Legacy ContinuesTwenty years ago this month the HP 3000 community was discovering windows into the World Wide Web. At the Interex conference held that month we heard the first about Javelin, a new Java-based terminal emulator that required nothing but a browser to connect a PC to an HP 3000. It was the first MPE terminal to run inside a browser, a technology that was searching for a commercial market in 1996. You requested a session and Javelin delivered one out of a pile of user licenses. At the 25- and 50-user tiers, Javelin got cheaper than Minisoft's MS 92 terminal.

That August was the first one with the NewsWire on hand in the community. Java was sexy and hot and Javelin provided a way to care about it while you managed an MPE/iX system. We reported with a hopeful eye that "Java is maturing as a platform for HP 3000 applications."

The Minisoft product is effectively a Java-based version of the MS92 terminal emulator, and it allows users to connect to HP 3000s without a client-based emulation program installed on their local desktops. Instead, Javelin downloads a Java applet in five to 20 seconds into a Web browser on the desktop. The resulting thin client handles HP 3000 terminal emulation tasks.

But customers won't have to modify existing HP 3000 VPlus application forms to deliver them over browser-based connections using Javelin. It reproduces function keys and special keys as well as performs Windows-grade slave printing. Minisoft's Doug Greenup said the product had been tested against MM/II and MANMAN on the 3000, as well as many custom VPlus applications, Qedit, Speededit, Powerhouse and Quiz.

"It's a little slower than our Windows product right now," Greenup said, "at least with character-mode applications. Block mode screens are faster." He said the product would be a good fit for inquiry and modest data entry applications, as well as public access to HP 3000 databases in government and university settings or for remote sales staff.

The point was to reduce the cost of connectivity and give casual users a simple link to HP 3000s. Java was in vogue at HP's MPE labs at a time when the goal was to give the 3000 an equal set of Web tools. HP-UX and Windows NT were claiming to have all of the momentum at the time.

Read "August Throwback: Java and VPlus get cozy" in full

Posted by Ron Seybold at 06:59 PM in History, Homesteading | Permalink | Comments (0)

August 05, 2016

Whatever you know best becomes a platform

Railway-717852_1280An HP 3000 software vendor called this week to report they put four new installations of their product into customer sites this year. Those aren't new HP 3000s, but they're new customers. In 2016 that's notable. There's a reason there are four new spots for this utility software.

"We turn these HP 3000s into Excel machines," the vendor's founder said. "These new IT managers don't know the HP 3000. But they know what they have used. For these companies, it was important to make these 3000s ready to work with Excel."

There are several ways to do this, and Excel doesn't seem like technology as powerful as IMAGE databases and the deep enterprise-grade applications on MPE/iX. The power doesn't matter. It's the connection to the rest of the IT world, and the familiarity of the staff with the driving technology. "You can't get young guys into these companies who know the HP 3000," the vendor said.

While it's not true everywhere, younger IT pros comprise the workforce for enterprise software management. The HP 3000 can seem like grandpa's server to the CIO who wasn't out of elementary school when the 3000 base was growing strong. (That seems young for a C-level job, but such a CIO could be as old as 45. Think the '80s.) Connecting its data with a newer tool like Excel gives the 3000 a tighter bond to mission-critical work.

What's more, oversimplifying the 3000 as a data resource isn't too far away from its original intent. Wirt Atmar of AICS sold QueryCalc software for reporting and new HP 3000s to companies "who were replacing steel filing cabinets" to access information. Excel is a platform in the same way that those filing cabinets were data repositories. It's easier to integrate a system that at least behaves like the rest of the enterprise. If a utility could attach new value to your older server, for a younger manager, there could be room in the budget for that.

Posted by Ron Seybold at 05:56 PM in Homesteading | Permalink | Comments (0)

August 03, 2016

Migration's prize: more server surveillance

Servers which replaced the HP 3000s were always delivered with a double-edged sword. More flexible. More complex. Whatever you needed to know about the 3000 could be discovered using tools from Lund, Allegro and other vendors. The products had their fans and the companies always pointed out the differences in reporting and tracking capabilities.

Surveillance-consoleNow another 3000 vendor, MB Foster, is teaming up with Bradmark to serve the non-3000 environments: the Windows, Linux and Unix servers that replaced MPE systems. Bradmark's Surveillance software is being resold by MB Foster. Resale often means extra value to the customer, employing services and expertise. There's a webinar on the product next Wednesday, August 10 at 2PM EDT. IT management needs vary, but there are commonalities. Some of the surveillance capability of these migration platforms simply was not possible using MPE/iX tools. Not even HP's pricier ones.

CPU, disk IO, memory, swap space, file system and process resource utilization can be monitored for the migration target platforms using Surveillance. The software works using a central repository, so a homogenous blend of these servers is handled from a single software console.

The software's list of supported server platforms is broad. In order of 3000 migrator's popularity, Windows Server 2003 or later; Linux x64 - x86; HP-UX, both PA-RISC and Itanium; IBM's Linux POWER and AIX Unix; Solaris SPARC, Solaris x64. Even HP's Tru64 can be included among Surveillance agents. There's also a Surveillance for database administration.

Read "Migration's prize: more server surveillance" in full

Posted by Ron Seybold at 03:21 PM in Migration | Permalink | Comments (0)

August 01, 2016

1,000-plus sessions propel $1 billion in sales

As HP 3000s and MPE hold on, homesteading managers need to justify their use of the solid server. Big-company users sometimes seal the deal. 

Coins-1523383_1280Here's a recent number: One company supports a firm that does over $1 billion in revenue a year — and it has at any given time over 1,300 sessions logged on, up to 2,000 during its busy season. It's not the only 3000 site of that size, either.

None of us have any hard data on how many 3000s are doing work, or how many work that hard. The data is scattered, so anecdotal reports revolve around the experiences from each vendor's 3000 support customers. One software vendor said there are more than 800 active licenses of his product, still paying support. These are hard numbers to verify.

Support for a 3000 comes from places like Pivital Solutions (an all-3000 support shop). There's no magic number of customers by today, although if you wanted our estimate we'd say more than 1,500 servers are running. Support was always a good way to take the 3000 census. But that was fractured, too: HP never had more than two out of every three 3000s under support.

By now the third party support is working at the very large companies using the HP 3000. If nothing but vendor support will do, then a 3000 is on the bubble — but realistically, that kind of support can't be found for Windows or Linux (although support from RedHat is available for its distro). There's independent support all over the business world. You're usually better off with support you've contracted with on your own, anyway. It's tuned up to know when your busy season is — and how to keep hundreds to thousands of sessions online.

Posted by Ron Seybold at 06:56 PM in Homesteading | Permalink | Comments (0)

July 29, 2016

HP's Unix Demise, and Rise of the Machine

Star-Trek-HP-MachineThere it is, HP's nouveau The Machine. Ready to do work in the Star Trek era. A bedrock to 23d Century tech, we're told.

Alternatives to MPE/iX and HP 3000s amount to about four choices. Windows, Unix, Linux, and non-HP environments comprise this list that migration projects assess. Most of the time the choice leads to an application or a suite of apps to replace the MPE computing. When the door of migration has been kicked open by an environment re-boot, though, then discussion of operating systems is worth time spent in study.

HP-UX came of age in an era when the 3000 became the old-era product on Hewlett-Packard strategy slide decks. Unix was an open environment in a simple review. Deeper study showed most Unixes carried a stamp of the vendor selling the OS. HP's was no different. Now the demise of HP-UX is being debated, especially among those who do their work in that environment. Almost 4,000 members of an HP-UX Users group on LinkedIn heard from Bill Hassell about the future of HP-UX.

"Reports of the demise of HP-UX are greatly exaggerated," he said in reply to a taunt from Dana French, a fan of IBM's Unix. The lack of a major Version 12 release is of no concern, either.

Itanium and HP-UX are dead? This is definitely not the case as the attendees at the HP-UX BootCamp found out in April. HP-UX will be fully supported on current and future hardware beyond 2020. With the addition of de-dupe on VxFS filesystems and containers for legacy systems, new features will continue to expand the most stable OS in enterprise server offerings. The lack of version 12 is an acknowledgement to hundreds of application providers (not just Oracle) that a major release number change is very costly in regression testing and certification. Instead, major functionality is released as an update to 11.31.

Rise-of-HPs-MachineHP hasn't been the greatest help in telling this story of the stable HP-UX's holdout, a tale that's important to several thousand 3000 users who've migrated to HP-UX since 2002. Instead, another version of The Machine, the HP computer intended to make all others obsolete, will appear like it's been transported from a starship. This is a product with no known OS. Hewlett-Packard Enterprise doesn't talk much about operating systems. The Machine has been touted this year like it's a keystone to the future. That's why Star Trek's images have been employed to let this tech vision rise up.

There's nothing wrong with continuing to use HP-UX, according to Hewlett-Packard Enterprise. The future belongs to another platform, though. In one of the more surprising aspects to the story about The Machine, the man who hawked it hardest will soon retire from HP. Martin Fink did a lot of work on behalf of keeping HP-UX in orbit, too. It's a matter of debate about how quickly that orbit is degrading.

Read "HP's Unix Demise, and Rise of the Machine" in full

Posted by Ron Seybold at 09:12 PM in Migration, News Outta HP | Permalink | Comments (0)

July 27, 2016

Did PCs hold Hewlett-Packard off the pace?

HPE-vs.-HPQ-Stock-2016Stock activity is the best-quantified way to assess the strength and prospects for a vendor. Few of the HP 3000 vendors ever reported stock pricing, so we always swung our spotlight on the system creator's stock. The results became entertaining after HP stopped making 3000s—but rarely entertaining in a good way. 

Now it appears that shedding its New Money products has pushed Hewlett-Packard Enterprise's stock into fresh territory. HPE hit the low $20s of share price this week. That's a 52-week high, and even higher if factoring in the fact the stock was chopped in two last fall.

Operating systems, software and hardware are only part of the story at HPE. Services were brought across in November, but their performance has skidded. As the break-off firm that reclaimed the HP Old Money business computing that drove enterprises, however, HPE has had a better time since the splitup. HPQ, making a living off the PCs and printers, remained under $14 a share today. The companies started out with equal assets and stock prices. What Enterprise has changed is the company's focus. The vendor is no longer trying to be everything to everybody.

Earlier this summer HPE announced it was getting even leaner. The enterprise services business, which bulked up HP's headcount and revenues as a result of acquiring 144,000 employees from EDS, will now be a separate entity. The move pushes HP closer to the business target it pursued while it was making the HP 3000 soar: sales to IT enterprises of software and hardware. This time around, they want to sell cloud computing too. But the old Apps on Tap program for the 3000 in the late '90s was a lot like that, too.

The extra systems focus, coupled with the stagnant action on the PC-printer side, suggests that straying from enterprise computing was a boat-anchor move. Hewlett-Packard Enterprise has put a new-era spin on the box-and-software pursuit, though. The CEO says putting Services on a separate course makes HPE a company with 100 percent of its revenues channel partner-driven. In effect it means all deals need a third party. This is the course the old HP could never adopt, much to the consternation of 3000 vendors.

Read "Did PCs hold Hewlett-Packard off the pace?" in full

Posted by Ron Seybold at 04:47 PM in News Outta HP, Newsmakers | Permalink | Comments (0)

July 25, 2016

Even archival 3000s are keeping things aloft

Stromasys makes MPE/iX applications last forever, a mission that some manufacturing suppliers are taking to heart. Doug Smith of the vendor tells a story about a supplier to aircraft manufacturers which puts data from archival 3000s back into production, from time to time.

Doug SmithThese suppliers have moved their production IT to platforms such as SAP, he says. But they haven't retired their HP 3000 data. One reason is the amount of work needed to bring processes onto complex platforms like SAP. Rather than move everything into a new application suite, many companies only move open items. They might need others later. That's where an archival MPE system goes to work.

"SAP is so limited," Smith says. "It’s a structure you must fit into. You have to fit your business to work within SAP, more than SAP working to fit the business. You have to meet the software’s criteria just to move on to the next process, and that’s why it’s so much easier just to move the items that are open. Otherwise, you have re-create all of the substructure you had on the 3000 software. A 10-year project could become a one-year project if you only move the open items. You’re talking about saving millions of dollars."

For example, one aircraft supplier has been building parts for 40 years, work that started when the HP 3000 was brand-new. They didn’t bring all those parts over to their SAP replacement for the MPE/iX applications. "But they can get a call at any time that they need the landing gear for a certain type of aircraft, for example—and they don’t have the part on SAP," Smith says. "So they have to go back to the archive machine to get it processed. It’s not only for regulatory purposes. It’s for serving-the-customer purposes."

Read "Even archival 3000s are keeping things aloft" in full

Posted by Ron Seybold at 09:38 PM in Homesteading | Permalink | Comments (0)

July 22, 2016

3000-free Southwest suffers airline IT crash

Three straight days of system outages cost Southwest Airlines more than $10 million in lost fares this week. The company's COO Mike Van de Ven said that the router crashes which started the meltdown are not uncommon. But then the routers triggered Web server crashes. Finally, the company's disaster recovery plan failed to save the IT operations. Social media posts from customers complained of delayed flight departures and arrivals and an inability to check in for flights on Southwest's website. The running count by Friday morning was 700 canceled flights, with another 1,300 delayed. People could not get to gates without boarding passes.

Southwest-Airline-IT-crashCustomers running 3000s through the 1990s might remember Southwest as a shining star in the MPE/iX galaxy. The system came online with ticketless travel using MPE/iX software developed at Morris Air. When Southwest started to skip the paper, it was one of the very first major airlines to do so. Dispensing with paper tickets was possible because of the 3000's unparalleled reliability.

Stranding an estimate 4,000 customers was never a part of the 3000's history at Southwest. The computer was the dominant ticketing tool in an era before the elaborate security checks in the US. From Wednesday through today, customers on thousands of its flights could not check in at kiosks or via those web servers. The IT failure happened as the Republican National Convention closed out its Cleveland circus.

It's commonplace for a system vendor who's been shown the door, like the 3000 group was in the first decade of this century, to say "It wasn't on our watch" when a crash like this hits. But being commonplace won't recover those millions of dollars of revenues. Maybe they were a small fraction of the overall savings while leaving the 3000. The reliability of an airline is worth a lot more than delivery of a product, though, like an auto. Hertz was a 3000 shop for many years, and their portion of the travel business didn't suffer these woes, either.

Both companies made their IT 3000-free while the worst fact about the system was that HP stopped selling it. They both had plans to expand, strategies MPE/iX wasn't going to be able to handle easily, too. When a vendor ends their business plans for a server, the sweater of coverage unravels one thread at a time. Mission-critical systems are never supposed to leave a publicly traded company naked from the waist up, however.

Read "3000-free Southwest suffers airline IT crash" in full

Posted by Ron Seybold at 01:06 PM in Migration, Newsmakers | Permalink | Comments (0)

July 20, 2016

Manufacturing alternatives rise for 3000 sites

Modules-in-softwareHP 3000 sites are migrating away from their ERP and MRP applications. One of the largest MANMAN users in the world on MPE/iX has started its transition to SAP. That's a long journey for a company with almost a dozen manufacturing sites. But SAP and other software has the potential to give companies customization, features and flexibility beyond MANMAN. It's not to say that MANMAN can't do the job, but the effort to change it requires expertise at many steps.

One of the experts in MANMAN — arguably the leading advisors — say that software designed in the modern era improves ERP for longtime MANMAN users. For example, says Terry Floyd at the Support Group, the software at Nissan Calsonic's US plant made the leap from MANMAN to IFS, a project that Floyd's group engineered and completed this spring.

"IFS is much more suited to what Nissan Calsonic is doing than MANMAN ever was," Floyd said. "They had more modifications [to MANMAN] than anybody." The number of the mods slows the march of change. It also shows how far the business processes of users have drifted beyond the stock architecture of MANMAN. A product like IFS was built to accommodate pinpoint processes, in part because IFS was built at the dawn of the object-oriented era.

IFS has its basis in the late '80s, early '90s, he explained, and pieces of that ERP solution "have some of the earliest object-oriented programming stuff ever written. So IFS has a heck of a head start on other products. They're rewritten things a few times and changed interfaces like everybody has to, in order to stay modern."

Read "Manufacturing alternatives rise for 3000 sites" in full

Posted by Ron Seybold at 10:31 AM in Migration | Permalink | Comments (0)

July 18, 2016

Samba-3000 sync and Formspec data tips

Samba sharing on our 3000 using Windows Explorer is slow, but it gets the job done. However, if I take down networking on the 3000 and bring it back up, Windows Explorer tells me the 3000 is inaccessible. Ping works, Reflection connections work and Internet Explorer has no trouble connecting to our Apache/iX web site. What's happening to the 3000's networking?

Frank Gribbin resolves and explains:

Samba-on-3000After rebooting the PC, everything works again until networking on the 3000 is refreshed. Your solution should address the fact that Windows is maintaining a table of connections that needs to be refreshed in DOS. From the DOS command line, issue the command nbtstat -R or nbtstat -RR.

James Byrne also points out:

You can get into trouble with cached credentials with Windows Active Directory as well. You can clear them from the command line with:

net session \\samba.server.ip.address /delete

Or you can do it through the Credentials Manager on the workstation's Control Panel. However you clear the cache, you still need to restart the workstation with the problem cache — because the credentials are still in memory.

Read "Samba-3000 sync and Formspec data tips" in full

Posted by Ron Seybold at 08:09 PM in History, Homesteading | Permalink | Comments (0)

July 15, 2016

An HP chieftain's last dream is Trumped

Carly TumblingBill Hewlett and Dave Packard were HP's most famous CEOs, but aside from the founders, the most notorious HP chieftain was Carly Fiorina. With the news today of Donald Trump's VP candidate choice -- not Carly, but an Indiana governor with genuine political chops -- this may be the time when Ms. Fiorina finally settles into that Fox News chair which is the terminus of her trail. As the picture above recalls, announcing Trump's rival Ted Cruz as the next President, then falling through a trap door onstage, might have ended her political hijinks.

Or not. Nobody can be really sure what Ms. Fiorina will do next, which seemed to make her an ideal pairing with The Donald. Unlike the presumptive nominee, she's better known by her first name, as if she was Cher or Hillary. So what follows will cite her as Carly. 

I've written about this shiny and shallow CEO since her first day. In 1999, in a July of 17 years ago  there was still an active 3000 business to manage at HP. We probably have different reasons to relay a smarmy track record of Carly's at HP, but the headlline "Carly Fiorina pans TSA on Yelp" pretty much sums up how she's always trying to fail better, apparently to teach us her new rules. Yelp, after all, is not so fraud-proof.

Her latest birthday cake was decorated with her Super PAC's logo. It was a show of hubris as raw as forcing out Dave Packard's son from the board of his father's company, or trying to get that board to pay five times what PriceWaterhouse turned out to be worth.

Carly pushed the HP cart into a ditch when she loaded it with Compaq, but she was just one of several CEOs in a row, all hired from outside HP, who ransacked R&D and spent acquisition money like it came off a Monopoly game board. Carly, Hurd, Apotheker. Three people whose smell of success has helped HP focus on enterprise computing once again -- after Carly yoked the company to those Compaq tigers who took over the company's spiritual campus. At least HP's business computing organization got the ProLiant out of it all.

An old friend of the 3000 at HP who watched the wreck of Carly break onto company shores recently marked his 30th anniversary with the system. Carly was called She Who Must Not Be Named inside the workplace, but SWMNBN's CEO behavior was a slap in HP's face as sharp as anything in 2016 politics.

SHMNBN’s disregard for ‘the little people’ has long been demonstrated. Her inability to sync with the company middle management was evidenced by a growth in employment during her self-declared hiring freeze. Then when the cuts did come, rather than having your boss or lab manager inform you, some VP you’d never met invited you to a meeting and delivered the news. From where I sat hard it was to tell if she was just a person encased in an over inflated bubble of self-regard who’s lost touch with reality.

This may be the last time we'll have Carly to kick around, as President Nixon said of himself in 1962. That didn't turn out to be true, either.

Read "An HP chieftain's last dream is Trumped" in full

Posted by Ron Seybold at 08:38 PM in History, Migration | Permalink | Comments (0)

July 13, 2016

How HP's OS's Become Virtually Free

KiteThe 3000 community has been receiving updates for simulator project this year. This isn't the software that virtualizes the PA-RISC servers which were the ultimate boxes in HP's 3000 line. This simulator software is strictly shareware, strictly free, and strictly built to emulate a previous generation's HP 3000s. The SIMH project can turn a PC into a Classic HP 3000, the sort that used MPE III, IV, or V as its operating system.

This is also a project that points to the lifecycle of HP's operating system products in the public domain. A hobbyist -- or a company that could get along with a 3000 with circa 1991 power and OS -- needs a copy of MPE V to make this freeware simulation work. Where you get this software is up to you. But it's not a secret, either. The process to free involves the passage of time, the end of commercial sales, and perhaps HP's tacit approval.

The creators of SIMH are assuming HP won't be reining in the 20-year-old OS built for the previous MPE generation. Dave Bryan, who posted a note about a new version of the SIMH simulator for the 3000, said that the HP Computer Museum in Australia has helped to make MPE V available for simulator use via a website.

I assembled the kit from the tape image in that directory, which was supplied to me by Al Kossow of Bitsavers. Al then posted the kit and tape on his site.

Before undertaking the 3000 simulator project, I verified with Al in 2011 that he would be able to post an MPE image, and he confirmed that he could.

This year marks a milestone in the 3000's Classic generation: a moment to download the needed MPE V OS without a license concern. If Kossow's upload is legal, this version of MPE V has become freeware.

This kind of open source status is what the 3000 community pursued for MPE/iX for the better part of a decade. As the ultimate 3000 OS, MPE/iX hasn't moved into the state of a GPL license (for sharing). Not yet. But there was a time when HP's MPE V was closely guarded and licensed, too. Nowadays, not so much. The transfer to open access for an OS requires time. HP hasn't sold an MPE/iX system in almost 13 years. The company stopped selling MPE V servers 21 years ago. The clock might be running toward an unfettered MPE/iX.

Read "How HP's OS's Become Virtually Free" in full

Posted by Ron Seybold at 09:42 PM in History, Homesteading | Permalink | Comments (0)

July 11, 2016

How to Use Input to Create Output Files

Intrinsics are a wonderful thing to power HP 3000 development and enhancement. There was a time when file information was hard to procure on a 3000. It was a long time ago, as I was reminded by Olav Kappert in a call about his HP 3000 history. "The high point in MPE software was the JOBINFO intrinsic," he said. Kappert started with the 3000 in 1979.

Fast-forward 37 years later and you'll find questions from a different programmer still working on a 3000, adding features to a system. The Obtaining File Information section of a KSAM manual on MPE/iX holds an answer to what seems like an advanced problem.

I'm still using our old HP 3000, and I have access to the HP COBOL compiler. We haven't migrated and aren't intending to. My problem is how to use the characteristics of an input file as HPFOPEN parameters to create an output file. I want that output file to be essentially an exact replica of the input file (give or take some of the data). I want to do this without knowing anything about the input file until it is opened by the COBOL program. 

I'm using FFILEINFO and FLABELINFO to capture the characteristics of the input file, after I have opened it. After I get the opens/reads/writes working, I want to be able to alter the capacity of the output file.

Francois Desrochers replies

How about calling FFILEINFO on the input file to retrieve all the attributes you may need? Then apply them to the output file HPFOPEN call.

Donna Hofmeister adds 

You might want to get a copy of the "Using KSAM XL and KSAM 64" manual. Chapters 3 and 4 seem to cover the areas you have questions about. Listfile,5 seems to be a rightly nifty thing.

But rather than beat yourself silly trying to get devise a pure COBOL solution, you might be well advised to augment what you're doing with some CI scripts that you call from your program.

Read "How to Use Input to Create Output Files" in full

Posted by Ron Seybold at 09:12 AM in Hidden Value | Permalink | Comments (0)

July 08, 2016

Is there something you desire in MPE/iX?

The 3000 homesteader probably misses the System Improvement Ballot, a way to petition HP for improvements to MPE. The results of these requests were often unveiled at an August user conference. It was like unwrapping a Christmas present for some customers, or finding a lump of coal in the stocking for others who sadly watched their requests bypassed.

But there’s still a way to meet desires for MPE/iX functionality. The answer lies in open source. Brian Edminster explained.

Unless a miracle occurs - we've probably seen the last of a 'Systems Improvement' survey/ballot.  That's a real shame - because there's still quite a lot of life left in the system - and there'd be more if we could teach her some new tricks.

Perhaps, though, we could find an equivalent:

Seems to me, because much open source software is of a subsystem or utility variety - perhaps it would be worthwhile to poll the community for what packages they need but can't get (i.e. not ported yet?), or need — but the existing ports aren't current enough and need updating.

If nothing else, it would provide those of us that tinker in this area with a bit more direction than just what we might currently need.

The community of 3000 customers could offer requests and help through the 3000-L mailing list, or leave a note here. Open source software was a breakthough for the 3000 in the late 90s. It's not too late to let a port change things.

Posted by Ron Seybold at 08:51 PM in Homesteading | Permalink | Comments (0)

July 06, 2016

Low-code solutions give ERP a new face

ERP software such as MANMAN has always carried a burden: it's most useful when it's been modified. Mods, as the customization is called, locks a company into the technology and business choices of the past, though. The old style ERP demanded coding to stay fluent. Software of today wants to avoid all that.

Rainbow faceSalesforce, whose engine drives the Kenandy ERP replacement for MANMAN and the like, says that "Low-code development platforms are transforming the way we build apps, opening up app development to a whole new world of point-and-click app developers and designers." Watching a demonstration from the Support Group's Terry Floyd of Kenandy showed how straightforward fine-tuning has become—once you know the settings to make the software dance.

Floyd's company has started taking Disston Tools to Kenandy, leaving behind more than two decades of MANMAN use and a heavy reliance on EDI software bolted into MANMAN. Floyd is providing in-service experience to Disston, based on his own company's use of Kenandy. "It's overkill for us to run our [consulting and development] company on," he said, "but we've learned so much about how to set it up for our clients."

There's configuration to set up internal email in Kenandy for example, the Chatter that can attach notes and comments to items like purchase orders. Kenandy always billed itself as Social ERP for this reason. It puts a new face on how resource planning should work. But it also gives companies of all sizes a way to take charge of changes with less programming.

Read "Low-code solutions give ERP a new face" in full

Posted by Ron Seybold at 08:14 AM in Migration | Permalink | Comments (0)

July 04, 2016

Celebrate Your Independence Today

As this is the Fourth of July in the United States, we're taking time away from the news desk to celebrate Independence Day, as we call it. If you think about it, your choice to remain on an HP 3000 -- even if it's on a long journey toward migration -- is a celebration of independence.

As examples of what that means in practice, have a look at the following articles:

On support for 3000s: HP's 3000 support clears away for indies

On MPE licenses, and the need for them in the post-HP era:Customers debate definition of a licensed HP 3000

On how respecting an HPSUSAN supports independent software vendors: 3000's IDs protect independent SW vendors

UK BuntingEmbrace your independence as an HP 3000 partner or customer, whenever that new course suits you. If you're migrating, your company's internal schedule will determine your new platform and when you will move. It's obviously not based on HP's support deadline, which is just as expired as George Washington. This is a holiday we celebrate to mark the country's trip down a new path independent of its founding authority figure, Great Britain. I am told the British celebrate today as "the anniversary of the time we got rid of those pesky colonists."

Which goes to show how anything can be viewed from more than one point of view, so long as you have an independent mind.

Posted by Ron Seybold at 08:56 AM in Homesteading | Permalink | Comments (0)

July 01, 2016

Celebrate independence this weekend

Fireworks-74689_1920Over this weekend in the United States, we celebrate Independence Day by vacationing from work, driving cars on some of least expensive gasoline in the world, and reflecting, between fireworks' starbursts, how lucky we are to choose. For a lot of people, this time around it's a four-day holiday, more largesse we enjoy if we're fortunate.

Although July 4th is a distinctly US holiday, a British friend of mine says it's the UK's independence day, too — as in, "We're rid of that dysfunctional colony once and for all." Think for a moment, if you're reading this on the holiday or the days that follow, the items you can celebrate leaving behind while you continue your use of the HP 3000.

You are independent from inflexible pricing on 3000 support (what non-HP entities could compete when HP was in the market in a serious way?), as well as the need for HP-branded storage. Now there's the Stromasys solution to replace aging hardware, if you have concerns about disks that are dozens of years old. Or use newer ones. Plenty of SCSI disks will work with 3000s without bearing the HP badge. The SCSI pass-through driver will embrace even more, once the software is applied to the task by the community's experts.

Read "Celebrate independence this weekend" in full

Posted by Ron Seybold at 09:02 AM in Homesteading | Permalink | Comments (0)

June 29, 2016

Date format variable help for MPE/iX

What would be the easiest way to get a variable date in the format "06/29/16" on a HP3000 OS version 7.0 and 7.5?

Michael Anderson replies

First echo:

echo ![str("!hpyyyymmdd",5,2)]/![str("!hpyyyymmdd",7,2)]/![str("!hpyyyymmdd",3,2)]

Then setvar:

setvar mydate '![str("!hpyyyymmdd",5,2)]/![str("!hpyyyymmdd",7,2)]/![str("!hpyyyymmdd",3,2)]'

(Note the usage of single-quote and double-quote in the setvar command.)

Allegro's Barry Lake adds

Please note that the HPYYYYMMDD variable is already a string variable:

Frodo: calc typeof(HPYYYYMMDD)
2, $2, %2

So you don't have to dereference it with ! inside double quotes. In other words, the following works just as well, is easier to read, and might even execute a bit faster:

Frodo: echo ![str(hpyyyymmdd,5,2)]/![str(hpyyyymmdd,7,2)]/![str(hpyyyymmdd,3,2)]
06/29/16

Read "Date format variable help for MPE/iX" in full

Posted by Ron Seybold at 08:11 PM in Hidden Value, Homesteading | Permalink | Comments (0)

June 27, 2016

Refitting Migration to Look Like Emulation

Stromasys White Paper ArtIn a webinar about emulation solutions last week, MB Foster offered a new take on some old tools. The subject was an exam of what 3000 sites could do if their budgets didn't let them take on a full migration on their own. Viewers heard about Stromasys Charon, of course, a software tool that has always proposed the OS in charge will remain the same: MPE/iX. The hardware gets emulated. 

The webinar took note of some Charon considerations, but none that haven't already surfaced. Software must be licensed to the new Charon emulated hardware. The greatest percentage of vendors are making that transfer a formality. Many don't even charge a fee to move from HP's PA-RISC iron to the emulated hardware. Of those who do, the fee can be nominal. Issues about revising hardcoded IP addresses were mentioned. Issues about historic data procedures and archival come up for any solution that changes things.

The other solutions in the webinar didn't have any of their issues examined.

Marx200_300On the subject of those other emulation solutions in MB Foster's perspective, some well-established products received a new label. Eloquence, the database that doesn't run under MPE/iX but has a TurboIMAGE Compatibility Mode, got its seven minutes of fame. The Marxmeier product has always been sold as a migration tool. For years the ads on this blog called it "Image migration at its best." Users on the call testified to the strong value of Eloquence.

Another third party tool, resold and supported by MB Foster, got a mention in the webinar and a label as an emulation solution. Ti2SQL, software that moves IMAGE data to SQL databases, was released by Ordat in the early years of the migration era. In 2003, Expeditors International included ORDAT’s Ti2SQL in Expeditors' rollout away from the 3000 because the software emulates IMAGE inside a relational database. The end result produced CLI calls native to a Unix-based database.

"Ti2SQL uses CLI," said MB Foster's Chris Whitehead. "Think of it as going to a complete native environment, while leveraging/using all of the business logic developed on/for the HP. Additionally, Ti2SQL allows someone to go to an off-path server and database, such as AIX and DB2."

Read "Refitting Migration to Look Like Emulation" in full

Posted by Ron Seybold at 09:33 PM in Homesteading, Migration | Permalink | Comments (0)

June 24, 2016

A Hybrid Solution to Staying and Going

Editor's note: we ran the following story about eZ-MPE on the product's announcement three years ago. The software suite came up for mention during this week's MB Foster webinar, and since it's offered as a modern solution, it seems useful to revisit the original release story.

HybridMB 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.” 

For example, the database environment mimics the IMAGE database, Whitehead said. A command line utility manages other functions and data types.

The eZ-MPE solution evolved during the migrating of custom code for customers into a Windows environment, the target environment for eZ-MPE migrations. For example, MBF Scheduler has been replacing the features and comprehensive functionality of HP 3000 batch scheduler and job control software including independently managed queues and a “job fence”, mimicking a module which is embedded in MPE/iX.

Read "A Hybrid Solution to Staying and Going" in full

Posted by Ron Seybold at 09:35 PM in Homesteading, Migration | Permalink | Comments (0)

June 22, 2016

What's MPE got to do with emulators?

Thoroughbred-horsesCompanies that want to use their MPE/iX applications a long time might count their timelines with two eras: Before Emulator, and After Emulator. The B.E. period left the MPE/iX user locked to Hewlett-Packard hardware and waiting for upgrades to HP boxes. The A.E. era uses virtualization via Charon to permit many beefy Intel boxes do the MPE/iX work. But what does MPE/iX code have to do with the magic of Charon? Not much, which is a good thing.

There's a stubborn story we hear about how the gem of MPE's source code is at the heart of what Charon does. What a virtualization engine like the Stromasys product delivers is a new capability for Intel hardware. An Intel box can pretend to be a PA-RISC processor, thanks to the software engineered by the creators of similar products for the Digital market.

But Charon doesn't rely on MPE/iX secrets to do this magic. It's like thinking a jockey is the being who's running a 2-mile racetrack course. He's the rider, and the horse in this metaphor is Charon. The basic design of Charon products, like the ones that virtualize the Sun Sparc systems and the PDP systems of DEC, creates the expertise for booting up Intels like they're 3000s. Nobody expects the ancestry of the jockey to play a role in making the horse faster. We don't sit in the grandstands to watch jockeys hoof it around the track.

Read "What's MPE got to do with emulators?" in full

Posted by Ron Seybold at 08:58 PM in History, Homesteading | Permalink | Comments (0)

June 20, 2016

Solitary backup tape spurs fresh MPE plea

When a 3000 site did its backups recently, the process did more than protect data on the business server. The procedure made a case for moving off the original HP 3000 hardware. Or keeping a couple of key tapes well protected.

Solitary ManLast week Greg Terterian left a request on 3000-L for help with a client. "They had problems with their disk storage and were going to do a reload," he said. "However, when backing up they were using the same tape over and over for the past three years."

As you might imagine, a solitary piece of backup media used repeatedly developed a problem over those years. The tape's no good. "Now they want to know if they can get or purchase, or if someone will be willing to donate, the MPE/iX 7.5 operating system."

There used to be a way to request new media for MPE/iX from HP, but that's a part of the 3000's legacy by now. Client Systems could once handle upgrade requests for part of the MPE/iX subsystem, but they were not answering calls at the start of 2016. The last HP 3000 distributor, Client Systems' domain is now parked.

Whether Terterian's client gets replacement MPE/iX files isn't the point of the story. (If you're donating, his email address is here.) The lesson is that a single backup tape is a solution that HP's hardware can let you stumble into, because restoring from tape is the norm for non-virtualized MPE/iX systems. If you're using an emulated 3000, however, your backup and bootup happens using disk files off images stored on stock PC hard drives. You could even back up to a cloud service like CrashPlan or Carbonite, if your MPE server runs off such Intel PC hardware.

Read "Solitary backup tape spurs fresh MPE plea" in full

Posted by Ron Seybold at 09:12 PM in Migration | Permalink | Comments (0)

June 15, 2016

Throwback of mid-June marks much change

Amid the midpoint of June, we have reported a lot of change in that month of the 3000 community's calendar. In the blog's first year of 2005, this report said HP's Unix was named in about a third of migrations.

HP-UX gains in later results (2005)

These revised percentage totals keep Windows in the lead. But with 71 companies reporting their migration plans or accomplishments to us, HP-UX has managed to poke above the 30 percent mark, to just about one-third of the target platform choices.

And there remains in the community a vibrant devotion to migrating to Windows. Linux was less than 10 percent back then. How enterprise tastes have changed.

New, independent training begins (2006)

MPE-Education.com becomes the hub for 3000 training as of this week, since HP has called off its training courses for the platform. Many companies still have years of HP 3000 use in front of them.

Paul Edwards and Frank Alden Smith revitalized HP's 3000 training materials and put the education experience online at $1,750 a seat. The market didn't materialize for the noble, useful service.

So much to see, so far to go (2007)

RibbonsOn a rack in one of the Mandalay Bay's wide lobbies at the Encompass show — lobbies so wide that a semi truck can pass unfettered — a stand of adhesive badges sparkles. The array of ribbons stamped with silver letters lays out the known future for an HP customer or prospect.

To no one's surprise, no "MPE/iX" ribbons. This is a conference which looks toward a new future with HP, instead of the past, or MPE's ongoing tomorrow without the vendor. 3000 community members are coming here to make plans for something new from HP—or hear from vendors and experts about how to make better use of something else from Hewlett-Packard.

The new Las Vegas digs for the annual user group show "improved its curb appeal," said the user group president. A sprawling show in a Vegas casino resort still showed off HP-UX training. "Windows on HP" suggested the vendor was scrabbling to keep customers on its platform.

Read "Throwback of mid-June marks much change" in full

Posted by Ron Seybold at 08:19 PM in History, Homesteading, Migration | Permalink | Comments (0)

June 13, 2016

2016 Advice: Emulate Your 3000 System

No kidding, the above strategy is bona fide. It will be online, with time for your questions, next Wednesday at 2 PM Eastern.

Emulation-3000-berryMB Foster has a novel webinar scheduled next week, and no, that's not an hour about writing a bestseller. The Web meeting on June 22 will walk through four different HP 3000 emulation options. All of them will mitigate risk, protect investments, and reduce year over year costs. In the end, every one of them should use MPE/iX apps, if they are bona fide emulations. Why else would you be emulating? The webinar promises a tour of how to replace the 3000 hardware, it seems.

As hardware emulation goes — and that's the most popular agent of change — there's only one supplier that we know about. Over the last three years Stromasys has enlisted HP 3000 advocates and experts and customers to embrace the Charon software. We're told that each new customer seems to draw out another.

There are other ways to consider emulation, however. Some of them have been around a long time, if preservation of in-house MPE/iX apps is the goal. AMXW was a sort of emulator: Automated Migration to UniX and Windows. It's a shell that runs atop those two platforms, plus Linux and IBM's Unix, connecting to commodity databases and surround-code tools while preserving the 3000's app code.

"MPE specifics, such as JCL batch jobs, file equations, JCW, UDCs, command files and variables are all supported — allowing the MPE environment to run as is on the new platform." Okay, this is probably a migration solution. You're not supposed to need to change your apps, though. HP's 3000 hardware gets dropped, too.

The two other options? We'll be online to see what they are. Registration is online at the MB Foster website, as always.

You can't say that emulation is the right choice for everybody who needs to change things. Cloud-based ERP and manufacturing is on the horizon from Kenandy, for example, a company with ASK MANMAN roots. Terry Floyd of the The Support Group says Kenandy is MANMAN done better, because the software seems simpler. He's developed and managed MANMAN installs since the 3000 was very new. Floyd goes to work migrating Disston Tools off MANMAN starting next month.

We agree that any range of emulation options must mitigate risk, protect investments, and reduce costs. Risk is in the eye of the manager; we've said that since 2002, when the Transition Era started. Foster says moving away is too risky and costly for customers who have data on HP 3000s.

Read "2016 Advice: Emulate Your 3000 System" in full

Posted by Ron Seybold at 06:52 PM in Homesteading, Migration | Permalink | Comments (0)

June 10, 2016

What A Newer MPE/iX Could Bring

What would HP 3000 owners do with a new MPE/iX release, anyway? On some IT planning books, the frozen status of the operating system counts as a demerit in 2016. Even still, enterprise system managers in other HP-sold environments face a nearly-glacial pace of OS upgrades today. Even while paying for HP’s support, the VMS system managers are looking at a lull.

Click for details on roadmapHP says it still cares about OpenVMS, but that OS has been moving to a third party. Support from a system maker still looks newer and shiny to some companies than the independent support managers available from third parties like Pivital. As it turns out, though, it’s that frozen-as-stable nature of MPE/iX which makes third party support just as good as HP’s—back when you could get support from HP.

“MPE's so solid,” Doug Smith said in a recent interview, “and these applications have been out there forever. There’s not a huge concern out there in the community about needing to have a new release of MPE.” Smith leads the way for Charon emulator installs at 3000 sites.

OpenVMS roadmaps were updated this week. The map shows how slow OS updating can proceed. 

Read "What A Newer MPE/iX Could Bring" in full

Posted by Ron Seybold at 05:13 PM in Homesteading, Newsmakers | Permalink | Comments (0)

June 08, 2016

Blog's birthday marks 11 digital years

Birthday-candlesThey're like dog years, these digital years: each counts for much more considering the change that they chronicle. This space on the Web has now been open 11 years. On June 8 of 2005 a death in the 3000's family rose into the news. Bruce Toback, creator of several 3000 software products and a man whose intellect was as sharp as his wit, died as suddenly as HP's futures for the HP 3000 did. I wrote a brief tribute on that day, because Toback's writing on the 3000-L made him a popular source of information. His email posts signed off with Edna St. Vincent Millay's poem about a candle with both ends alight, which made it burn so bright.

Like the best of the 3000's community leaders, Toback flashed bright ends of technical prowess and a smart cynicism, the latter which couldn't help but spark a chuckle. His programming lies at the heart of Formation, a ROC Software product which Toback created for Tymlabs, an extraordinary HP software company here in Austin during 80s and early 90s. Toback could demonstrate a sharp wit as well as trenchant insight. From one of his messages in 2004:

HP engineer [about a Webcast to encourage migration]: During the program, we will discuss the value and benefits of Transitioning from the HP e3000 platform to Microsoft's .NET.

Bruce: Oh... a very short program, then.

Without the news and developments of migration, though, we might not have arrived at this space with as much copy by now. Today there's more than 2,800 articles here going back 11 years, and there are 10 additional years of reporting and commentary on the 3000newswire.com site as well. (You can search it all through the link at the left, and people do every day.) After more than a couple of decades of this work, we thank the community — and in particular, our sponsors — for the opportunity to blog about the present, the future, and the past.

Read "Blog's birthday marks 11 digital years" in full

Posted by Ron Seybold at 10:58 PM in History | Permalink | Comments (0)

June 06, 2016

SLEEPER, Awakened for the Masses

Sleep-1389978_1280The contributed program SLEEPER is probably the software cited most often as proof of the riches of the Contributed Software Library. First created outside of the IT shops of Boeing (according to its first writer Ray Legault) the program was among the most classic of solutions for straightforward jobsteam management. You wouldn't mistake SLEEPER for something professional like Maestro, or even the free MasterOp. But SLEEPER was contributed to the 3000 community, not cast into the free wilds like MasterOp was after its commercial career ended. It was meant to be shared.

The trouble was, SLEEPER disappeared from the community's shelves when Interex died. The CSL tapes (and eventually CDs) went off the grid, another skid-mark left when the user group careened into the void in 2005. It's been 11 years, though, and it's finally time to at least make SLEEPER ready for a wake-up call. We've got the two simple source files to share.

Nobody has liability anymore for HP 3000 contributed software. SLEEPER was never released with support or a license; it was simply part of being an Interex member at a certain level. And let us take a minute to recall that Interex folded owing millions of dollars to members and vendors. After 11 years, it's time to make this software a community resource once more. "Hey, I know a guy who can get you that" has been the means to share the utility over the last decade.

Surprisingly, it's just a well-packed 184K of SPL and FORTRAN code. MPE magic never took up much space. That's one of the reasons it was magic. SLEEPER is also a fine example of how 3000 managers helped one another.

Read "SLEEPER, Awakened for the Masses" in full

Posted by Ron Seybold at 10:06 PM in Hidden Value, Homesteading | Permalink | Comments (0)

June 01, 2016

Recovering Your Lost Logins

BWManIn the world of 2016, losing a password can be a time-bending experience. Apple's ID logins for its iCloud services, iTunes, and App Store only bear five attempts at most before they close out access to the phone. From there, you're on to a lengthy call to Apple. The smartphone is a tiny computer. The larger ones are not as strident about refusing repeated attempts, including the HP 3000.

They are secure, though. In these times when the servers can go dark for awhile as cold-start archive systems, though, a login can get misplaced. We're not supposed to write these things down, after all. What do you do when you have a question like the one below?

I restarted a 3000 9x7 after a few years in mothballs to run an old in-house app. I was able to boot up and login as OPERATOR.SYS, but cannot remember or find the password for MANAGER.SYS. Is there anyway to reset, clear, or overwrite the password file? I know the old machine is a very secure one, but now I am hoping there is a way around it.

What follows are a couple of suggestions to get back into the manager's driver's seat. However, you'll need to at least have a ticket to ride in OPERATOR.SYS.

Gilles Schipper shares what he knows.

There's not an easy way around the security. But since you can log on as OPERATOR.SYS, you should be able to store off the system directory to tape, as follows:

:file t;dev=tape
:store command.pub;*t;directory

Now that you have the directory on tape, you should be able to move around with FCOPY (and its ;char;hex options) to find the password for MANAGER.SYS. And that's all assuming you haven't implemented the directory encryption feature available with HP's security product Security Monitor/iX.

There's one other way. It's a good thing, because the alternatives do not include a rescue call to HP. There's nothing like Apple's password recovery support left for the HP 3000, as the vendor has long ago left the field. However, a good support contract for an MPE/iX server can be just the thing, and we know where you can get one.

Posted by Ron Seybold at 05:11 PM in Hidden Value, Homesteading | Permalink | Comments (0)

May 27, 2016

A Weekend Memorial to the Future's Past

Here in the US we start our Memorial Day holiday weekend today. Plenty of IT experts are taking a few days off. I reported the start of the HP 3000 emulation era over a Memorial Day weekend, five years ago. We'll take our long weekend to celebrate grandkids and a cookout, and see you back here next week.

In the meantime, here's that first report, a three-parter, showing that Stromasys set and met its development schedule, one that gave the 3000 homesteaders a future beyond the lifespan of HP's MPE/iX hardware. One year later, the software, called Zelus at the time, had a formal debut at a Training Day. Now as Charon it's preserving MPE/iX applications.

ZelusBoot-e3000-a400-2

During that 2011 springtime, Stromasys offered screen shots of the PA-RISC emulator as evidence the software could serve as a virtual platform for the 3000’s OS. The screen above shows the beginning of the boot sequence (click for detailed view). HP provided internals boot-up documentation to assist in the software's design.

A product journey toward a 3000 hardware emulator took another significant step this spring, as the Zelus cross-platform software booted MPE/iX on an Intel server.

CTO Dr. Robert Boers of Stromasys reported that the OS has come up on a version of the emulator that will managed, eventually, by Linux. Although the test screens that Boers sent were hosted by Windows, the "fairly preliminary version" will be released on an open source OS. "Windows is a little passé," Boers said. "But we now have a first prototype."

Stromasys said it has now been able to use Zelus to tap PA-RISC hardware diagnostics to get the bugs out. "The way we had to debug this was just looking at the code instruction by instruction," Boers said, "to figure out what it does. That took us a long time." Compared to the emulators for the DEC market, "this is by far the most complex emulator."

Read "A Weekend Memorial to the Future's Past" in full

Posted by Ron Seybold at 01:34 PM in History, Homesteading | Permalink | Comments (0)

May 25, 2016

MANMAN to journey to cloud-based ERP

Diston SawsThe first project to move a MANMAN HP 3000 site to Kenandy's cloud-based ERP has an official start date. Terry Floyd and his team at The Support Group have a one-year mission to move Disston Tools from MANMAN to the Kenandy software, starting at the beginning of July. A manufacturer whose roots go back to 1840, Disston is dependent on EDI, an aspect that will help to prove that Kenandy is a good fit for MANMAN migrators.

"It’s an incredible ERP system – a completely new design concept and paradigm for ERP," Floyd said of Kenandy. "There are no modules; it’s all one thing. It has amazing functionality… and it's ready for MANMAN companies now, as I predicted four years ago."

Terry-FloydLike many MANMAN sites on the HP 3000, Disston has a complicated company structure and MANMAN has been modified. Floyd has an insider advantage in leading the journey away from MPE/iX, "since I first started working on their FORTAN in 1986." He adds that they have given themselves a year "to get everything right and do one big cutover." He's been a guru for MANMAN sites through the software's many owners, from the earliest days when he worked for ASK Computer, then on his own and into MANMAN's Computer Associates days, forward to the SSA Global era, and finally to Infor's current stewardship of MANMAN. Kenandy feels like old blood, in a good way, he said.

"All of us [at the Support Group] spent a week at Kenandy Partner Training sessions. We met everybody and what a group they are. It’s just like ASK in 1980." By that Floyd means the creators of MANMAN, ASK. The company's founder Sandy Kurtzig was crucial to getting Kenandy's software ready for the marketplace. Floyd has been talking about the solution since 2011, pegging it as a good destination for MANMAN sites who want to leave the HP 3000. 

Read "MANMAN to journey to cloud-based ERP" in full

Posted by Ron Seybold at 07:35 PM in Migration | Permalink | Comments (0)

May 23, 2016

Moving off a 3000, or just some MPE/iX app?

Wednesday afternoon MB Foster leads another of its webinars about migration advice. The company is the community leader in data migration, data migration projects, data migration service. You're moving, they're the folks to contact. On Wednesday at 2 PM EST they're reaching out to explain the methodology the company uses to process departures from the 3000 world.

Moving VanThe options on exits "have not changed much over the last decade," the company's email teaser says. "They include; Stay, Rehost, Replace/Buy, Rebuild. The best choice for you depends on growth expectations, corporate standards, risk and cost." The other determining aspect is how much exiting a migration prospect must do immediately. Several of the current generation of migrators have gone to the app-by-app model.

The largest single migration of educational 3000s, 36 of them at the SBCTC, was pulled off in some pieces. This usually follows a methodology of getting a key app onto another platform in a lift and shift. Rewrites have become rare. Later on the lifted app can be replaced. Sometimes, as is the case at SBCTC, the whole migration platform shifts. Eloquence database to Oracle was the shift there. Another higher-ed site, at Idaho State University, moved its apps a few at a time over several years.

It's always worth mentioning the choice that MB Foster notes: a choice to stay on the HP 3000. But you won't even have to do that if all you need to accomplish is an update of hardware. Choosing Stromasys and the Charon emulator is also a move off the HP 3000: the Hewlett-Packard servers and disks get left behind. New PC hardware and a Linux control center take the place of the HP iron.

Read "Moving off a 3000, or just some MPE/iX app?" in full

Posted by Ron Seybold at 06:42 PM in Homesteading, Migration | Permalink | Comments (0)

May 20, 2016

Cloud patterns now private, MRP affairs

Moving CloudsTwo years ago this week we reported that Hewlett-Packard would be spending $1 billion on developments for HP Helion, its private and public cloud offering for enterprise customers. The spending was scheduled to take place over the coming two years, so now's a good time to examine the ceiling of clouds for HP. It turned out to be lower than expected.

That spending plan for Helion outlasted the public version of the cloud service. Within a year of the $1 billion mission statement, HP was saying the company had no business in a cloud space dominated by Amazon Web Services and others. By this January, the final cloud customers at the Helion public service had moved their clouds elsewhere. HP Helion private clouds march onward in a world where the vendor controls all elements in a deal, rather than competing in a tumultuous market. A private cloud behaves more like the HP 3000 world everybody knows: a means to management of dedicated resources.

The use of cloud computing to replace HP 3000 manufacturing applications is reaching beyond hypotheticals this summer. Terry Floyd, founder of the manufacturing services firm The Support Group, has been working with Kenandy to place the cloud company's solution in a classic 3000 shop. A project will be underway to make this migration happen this summer, he said. 

The 3000 community that's been moving has been waiting for cloud solutions. Kenandy is the company built around the IT experience and expertise of the creators of MANMAN. They've called their software social ERP, in part because it embraces the information exchange that happens on that social network level. But from the viewpoint of Floyd, Kenandy's was waiting for somebody from the 3000 world to hit that teed-up ball. Kenandy has been tracking 3000 prospects a long time. The company was on hand at the Computer History Museum for the ultimate HP3000 Reunion in 2011.

Read "Cloud patterns now private, MRP affairs" in full

Posted by Ron Seybold at 08:52 PM in Migration, News Outta HP | Permalink | Comments (0)

May 18, 2016

Tape drive changer a powerhouse for MPE

Autochanging HensAutochanging tape drives used to be the stuff of science fiction among 3000 managers, but those days passed by before HP cut off making Classic 3000 MPE V systems. Just because an autochanger is a 3000 storage option does not make it automatic to program, however.

A question posed to the community by Ideal Computer Services Ryan Melander reached for help on programmatically controlling such autochangers -- to select a slot, and load the tape and come to ready. "I am trying to configure an old DDS3 auto-changer, one that I don't believe will unload and load the next tape," he said.

Gilles Schipper noted that the command ad ldevno id=hpc1557a path=?? Mode=autoreply configures the device, and to advance tape after use, employ the command (from Devctrl.mpexl.telesup) ldev eject=enable load=online 

DAT tapesDenys Beauchemin mentioned HP's pass-through SCSI driver as a tool to drive the device's robot. The software was built by HP's labs and labeled as "not for the faint of heart" by engineers, but can assert a programmatic control over autochangers. Some third party programs such as Orbit's Software Backup+/iX can also do this work.

If ever there was a theme song for an autochanger at work, it would be a tune called Powerhouse. Children of the Fifties and Sixties will know it as soon as they hear it, if they've ever watched a Warner Brothers cartoon.

Read "Tape drive changer a powerhouse for MPE" in full

Posted by Ron Seybold at 09:16 PM in Hidden Value, Homesteading | Permalink | Comments (0)

May 16, 2016

A Spring When The Web Was New to You

May 1996 Front PageTwenty years ago this month we were paying special attention to the Web. We called it the World Wide Web in May 1996, the www that does not precede Internet addresses anymore. But on the pages of the 3000 NewsWire released in this week of May, a notable integration of IMAGE and the Internet got its spotlight. We've put that issue online for the first time. The Web was so new to us that our first 10 issues were never coded into HTML. Now you can read and download the issue, and it's even searchable within the limits of Adobe's OCR.

As an application for higher education, IRIS was serving colleges in 1996 using MPE/iX. The colleges wanted this new Web thing, popular among its professors and students, to work with the 3000 applications. Thus was born IRISLink.

IRISLink is not a product that Software Research Northwest will sell to the general market. But SRN's Wayne Holt suspects that a generic version of something like it is probably being built in the basement of more than one third-party vendor for rollout at this summer's HP World meeting.

"The message traffic on the HP 3000-L Internet list shows that a lot of sites prefer the COBOL lI/IMAGE model over writing piles of new code in a nonbusiness oriented language," Holt said. "But people are telling them that won't fly in the world of the Web and - take a deep breath here - the time has come to dump their existing well-developed COBOL lI/IMAGE infrastructure on the HP 3000. Not so."

The integrators on this project made themselves big names in the next few years. David Greer convinced Holt at a face-to-face meeting at a Texas user conference where "I listened to him share his vision of what the Web would someday be in terms of a standard for access to resources and information." Chris Bartram was providing a freeware version of email software that used Internet open systems standards. Take that, DeskManager.

It was far from accepted wisdom in 1996 that the WWW would become useful to corporate and business-related organizations. Even in that year, though, the drag of COBOL II's age could be felt pulling away 3000 users from the server. An HP survey we noted on the FlashPaper pages of that issue "asks customers to give HP a 1-5 rating (5 as most important) on enhancements to COBOL II that might keep you from moving to another language." There wasn't another language to move toward, other than the 4GLs and C, and those languages represented a scant portion of 3000 programs. Without the language improvements, some 3000 customers would have to move on. 

Read "A Spring When The Web Was New to You" in full

Posted by Ron Seybold at 09:38 PM in History, Homesteading, Web Resources | Permalink | Comments (0)

May 13, 2016

Creating 3000 Concept-Proving Grounds

Proving GroundThree years ago today, Stromasys hosted a community meeting at the Computer History Museum. It was the coming-out party for the debutante HP 3000 virtualization product Charon. The software had been running in several production sites for awhile, but the CHM meeting collected several dozen partners, prospects, and Stromasys experts. Some spicy slide decks were shared, along with promises that saving MPE/iX applications just got easier. This was billed as training.

In the 36 months since that day, the Charon HPA software has been enhanced twice to better its performance levels as well as establishing more complete emulation of the HP hardware environments. One major change to the solution came by eliminating an option — a kind of addition through subtraction that's pushing the software into production use more often. The Freeware A-202 of 2013 has been removed, replaced by Proof of Concept. PoC is pretty much the only gateway to using the software that transforms Intel-Linux boxes into PA-RISC 3000 servers.

3000 sites "are coming out of the closets," said product manager Doug Smith when he flew into Austin to update me about the product. He's running a program that discounts PoC engagements, with savings based on the size of the license. Companies that few of us knew were using 3000s have surfaced to adopt Charon, he explained. There's also a 6-way and 8-way configuration of the software that moves above the performance levels of the biggest N-Class server. Meeting and beating HP's 3000 iron performance is a big part of the approval process to get Charon sold and installed.

A proof of concept engagement takes real production data, integrated into the software-server combo of Charon over a period of five days, and shows managers in tech and the boardroom how seamless emulation can look. Smith says that MPE sites don't even need a Linux admin to do this virtualization. One part of that is because of the proof of concept phase gets everything in place to run. Three years ago, the issues to resolve were license-based in some prospects' eyes. By now, putting Charon in play involves five days of time and a license that can be either annual or perpetual. 

But Smith says just about all the Charon licenses sold to 3000 sites today are perpetual. This might be one reason why going to Computer History Museum for that 2013 coming-out seemed so fitting. Legacy and history are often co-pilots that deliver stable applications.

Read "Creating 3000 Concept-Proving Grounds" in full

Posted by Ron Seybold at 06:06 PM in History, Migration | Permalink | Comments (0)

May 11, 2016

Migrations include data: How to handle bags

BagsonbeltEarlier this week I wrote about a collective of Washington state colleges that moved away from the HP 3000 and MPE in 2011. The work started years earlier and had a dead-end for awhile, but the 36 HP 3000s eventually became just six Integrity servers. They used the TurboIMAGE data and lifted apps, but the data was the most crucial part of the migration.

Moving data is fraught with challenges, from doing it in a way that the new apps can make sense of it, to making sure everything got transported safely. Good HP 3000 managers are like Marines: no bit of data is left behind. They leave behind applications often, because programs go obsolete or get replaced. Not data.

Later today MB Foster is having a demo of its UDACentral software. There's still a few hours to register, but you need to be at your browser live at 1 PM today, May 11. This is an HP 3000 story, too. Migration is more complicated sometimes than just STORE and RESTORE. Mapping a database to another one is easier with good software.

The demo will show "how to drag and drop and map data from source to target, automatically create migration scripts, and migrate tens of millions of rows per hour." A free trial of UDACentral can be downloaded from the MBFoster website.

"This is a 3000 story, and beyond a 3000 as well," Birket Foster says. "A story of evolution and learning to use data."

Read "Migrations include data: How to handle bags" in full

Posted by Ron Seybold at 07:28 AM in Migration | Permalink | Comments (0)

May 09, 2016

First came MPE's migration—now, the apps

Bull-Elk-migratingBy mid-2011, the Washington State Board for Community & Technical Colleges (SBCTC) stopped using the 36 HP 3000s that had powered 34 campuses since 1982. Even at that time, though, after the largest transfer of educational apps off MPE, SBCTC knew the target HP-UX systems would see another migration. One migration began another. Migrating off MPE hosts was a prelude to another migration, four years after landing on HP's Unix.

Michael Scroggins, the CIO at SBCTC, checked in with us after we spotted him on next month's HPE Discover conference speaker list. He's talking about the role of a CIO in today's IT. Why Would You Want to be a CIO? promises insights.

The CIO is a high-risk position. There are many thoughts and much advice related to surviving as a CIO. You’ve got to get there first. This discussion will center on strategies and considerations that you can use to get there. Why would anyone want to be a CIO? It is the best job in the world… if you have what it takes.

SBCTC has been taking its data forward for more than 13 years, proposing and moving and re-moving its data since 2003. SQL Server and Windows NT was the first target announced, and by 2009 that HP-led initiative had been shuttered while HP repaid what it hadn't finished to the colleges. The Lift and Shift Project was next and took about 18 months. Then in 2014, the eight HP-UX Integrity servers at SBCTC were upgraded to Itanium 4 systems. The original MPE/iX apps were lifted onto Integrity servers after being virtualized.

"We used AMXW’s MPE virtualization environments," Scroggins said, "and consolidated multiple colleges onto isolated environments on the HP-UX instances of Itanium 2 blade servers on the C7000 chassis. The solution leveraged the state’s data center where all colleges are centrally hosted." Lift and Shift cut the colleges' server count from 36 down to eight, all in a consolidated state datacenter.

Another move, off the lift and shift apps, was always in the plans, however.

Read "First came MPE's migration—now, the apps" in full

Posted by Ron Seybold at 07:20 PM in Migration, User Reports | Permalink | Comments (0)

Search