How to Transform MPE Spoolfiles to PDFs
The Remains of Any Need for CPUNAMEing

Proving concepts leads to hardware exits

Exit-graphicThey've been called straw men, and more lately proof of concept projects. These assessment steps have often represented significant change at HP 3000 sites. Few migrations got the green light to proceed with the raw change and full-on expense without demos of replacement apps. Even when the change was limited to applications only, with no platform replacement, testing with production data was the most secure choice.

That's why the strategy sounded familiar when Stromasys hosted its first webinar in years. The company calls its assessment engagement to test Charon a proof of concept. Led by Global Accounts Manager Ray LeBrun and system engineer Darrell Wright, the talk included a note on how essential the PoC step has been to success with the Charon virtualized system.

"We're pretty confidant that if we engage in a PoC with you, then we're 99-plus percent sure Charon will work for you," LeBrun said. "We will not engage if we're not confident this is the right solution for you."

Stromasys works with a site's production data to prove the concept of giving HP's 3000 hardware an exit date. MPE/iX and the applications, and of course the data, stay in place. However, LeBrun said Charon has also been "a bridge to allow you to get to a migration. We have folks who say, "I'm only going to use that [3000] application for another two years. Well, two more years oftentimes becomes three, four, and five years."

The technology concept behind virtualization is well known by now. People are so familiar with it that LeBrun said the vendor gets asked regularly when HP-UX Integrity server virtualization via Charon is coming. The question came up in the webinar, too.

"It's not in our roadmap anywhere," LeBrun said of a Charon built to give HP's Unix hardware an exit date. "Even if it was, I probably couldn't say anything about it, but it'd certainly be viable if there was a business case for it."

A business case for migrations — either off HP's hardware, or away from an operating environment — usually gets built at a customer site only after the technology has been given an all-clear. Stromays Proof of Concepts are paid engagements, because they include vendor staff hours spent onsite, services to transfer data to the Intel-based Charon system, and training a customer's IT staff to use the software.

A five-day onsite engagement, followed by a 30-day test period, makes up a PoC. "We basically do a live install of your application [on Charon] in your environment," LeBrun said. "You're not testing for look and feel. You're testing your application with your data."

Comments