March 28, 2016
For any fate, applications need budgets
At Idaho State University, the HP 3000 is moving into its final months of production use. It's been more than eight years to bring all of the MPE-based applications' duties into a new hosting environment. Sun was the early winner in this migration, but after taking the early round of replacement apps onto Solaris, the university is settling on Linux. This was a migration that didn't give Hewlett-Packard any place as a host.
Even in the realm of replacement software's big bounty, some apps moved across more slowly. Payroll, financials: these things moved in a straight line to Ellucian's ERP software for universities. But telecomm, inventory, motorpool — the 3000 ran all of this — had to be moved separately.
Along the way, the prospect of keeping those extra applications alive included the option of virtualizing the 3000 onto a Stromasys server. The timing didn't work for the university because it was so close to decommissioning its last 3000 apps, according to Senior IT Analyst John MacLerran.
We were hoping to use the emulator for a year or two while we finished migrating our remaining applications off the 3000. However, it was decided that the effort required to obtain software licenses from all of the vendors would be better spent accelerating our migration off the platform.
Whether an application remains on MPE servers, or makes its way to Linux as a replacement or a rewrite, applications require budget. The word "effort" means the expense in man-hours and dollars. Staying has a cost. Analyzing the timing can help a 3000 owner decide when its budget should be turned to departure dollars. It's only possible when the Hewlett-Packard hardware remains sound and healthy."It's not like we saw anything that would keep Charon from working for us," MacLerran said, "but it didn't save us any work in our migration."
The cost/benefit ratio didn't work for us -- we wouldn't have been on the Charon platform long enough to recoup our investment in the emulator. It made more sense for us to pay an additional year of maintenance on the original hardware, since we would've had to do that anyway during the migration to Charon. Instead, we put additional resources into getting the applications migrated.
The University began its look at the Charon solution in 2014, but its thorough evaluation got interrupted when MacLerran was tapped to help a languishing internal project get back on schedule. By 2015, the final evaluation decision was made, based on the finish date of migrating its final MPE applications.
We are in the final stages of shutting our HP 3000s down. Everything we used to use them for has been migrated elsewhere -- much of it to Ellucian, and some of it to other third-party vendors (i.e., where Ellucian doesn't have an equivalent function). The only remaining activity on the HP 3000 is data archival for records-retention purposes.
To satisfy that, we're extracting our data and putting it in Oracle tables. That way, we can query for the information that may still be needed for audit, but not for transactional purposes.
MacLerran said the university expects to pull the plug on its HP 3000s by the end of June, 2016.
Use our search engine to find 20 years
of HP 3000 news and articles
The comments to this entry are closed.