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)

Pivital Solutions: Your complete
HP 3000 resource

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)

May 06, 2016

Options for STORE You May Not Know

StorehouseSTORE is the default backup tool for every HP 3000, but this bedrock of backup has options which might exceed expectations for a subsystem utility. Gilles Schipper, the support guru of three-plus decades on the 3000, told us about a few STORE sweet spots.

To start, using the :MAXTAPEBUF option can cut a four-hour backup to three hours or less. Schipper says that increasing the buffer size default to 32K, from the usual 16K, speeds up the backup when STORE sees MAXTAPEBUF. "That's a pretty good payback for one option."

Backups don't need to be specified with an @.@.@ command to be complete. "People should really be using the forward slash," he says, "because it's easy to accidentally omit the Posix file structure if you're not careful constructing your fileset backup." The slash is so much better that a backup specified by HP's TurboStore will replace any @.@.@ operation with "./" Combining @.@.@ with exclusions can lead to omitting files which should have been in a backup.

Schipper says that including a directory on a backup is smart, but private volumes in use on a 3000 need more than :directory as an option.

Read "Options for STORE You May Not Know" in full

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

May 04, 2016

CPR for a Non-Responsive Console

On my HP 3000, after a short power blip, the console is now non-responsive. I can connect to the system's GSP port and the session is connected, but nothing is displayed. Neither <ctrl> A or <ctrl> B works. I type away, but get no response. I can then connect via VT-MGR and take the console :console !hpldevin and I receive all the console messages.

So, the messages are being sent (since I see them on the VT connection), but neither the physical console or the GSP gets any console messages. What can I try?

Gilles Schipper says

I believe a START NORECOVERY reboot is in order here. Since <ctrl> A <ctrl> B do not work, you will need to power-recycle the machine to effect a reboot. Presumably you would want to do this after gracefully stopping all jobs and asking online users to log off, if possible.

Depending upon which patch level your level of MPE is on, the :SHUTDOWN RESTART MPE command may also work from a logged-on session with at least OP capability.

Mark Ranft adds

If you haven't rebooted, I've seen similar issues. From the VT console can you try to do 'abortio 20' until it says no I/O to abort. A WHILE loop may make this easier. I've had luck with this in the past. But since Ctrl-B doesn't work, you may be out of luck.

Read "CPR for a Non-Responsive Console" in full

Posted by Ron Seybold at 10:37 PM in Hidden Value, Homesteading, User Reports, Web Resources | Permalink | Comments (0)

May 02, 2016

New encrypted hardware solves aged issues

Tinned-disk-encryptionSecurity standards have advanced in IT, while HP's 3000 hardware has not. Encryption resolves a key need for data security that's a part of the HIPAA regulations. The 3000 components won't allow for full disk encryption. There's another approach. A replacement hardware solution for MPE/iX -- which is still being used in the insurance industry -- has been on the market for more than four years. In fact, the hardware is all around us.

Encryption solutions for an older 3000 hardware's data are available. FluentEdge Technologies has sold a PCI-ready solution for Ecometry sites for more than five years. A built-in full-disk approach is only an option with a fresher OS, though. We don't mean the environment powering the application; that's still MPE/iX. The control of the hardware is where such new hardware can be put into play.

Virtualizing with the Charon HPA software offers several advantages over relying on HP's hardware. Component failures are a matter of when, not if, in 15-year-old hardware. If the 3000 isn't an A- or N-Class, it's even older. Shrink-wrapping replacement drives won't look as good to security auditors as a full disk encryption of recent-model components. Newer drives include broader options.

The virtualization of the MPE/iX hardware can become an encryption strategy. Alternative methods that rely on legal defenses don't exist like they once did. A security expert friend of mine tells a story about using lawyers instead of encryption. It's a story from a different time: the era when 3000 hardware was not so old.

Read "New encrypted hardware solves aged issues" in full

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

April 29, 2016

Post-migration, there's often more changes

SBCTC timeline


The 2010 timeline update for moving away from the three dozen HP 3000s at SBCTC

Five years ago this spring, work was wrapping up on migrating 36 HP 3000s at a college consortium. This was the largest higher education migration project in the 3000's history, the mission of the Washington State Board of Community and Technical Colleges. When it finished, 34 colleges in the state started to rely on HP-UX instead of MPE/iX. The work took more than two years to complete. The chief of the IT work at the state board will be speaking this June at the annual Discover conference, which is now called HPE Discover.

Migration change usually signals a new way to look at information's value. Taking legacy systems into the next generation of software and hardware is really everybody's mission in the 3000 world. The elegant Hewlett-Packard 3000 hardware is also elderly for any homesteader. Virtualizing the MPE/iX hardware is a migration of sorts, but one that can be completed in about five days, before testing. As for the migration-bound CIO, leaving behind the bedrock of MPE/iX opens up a redesign opportunity. Perhaps more than one.

LIftNShift overviewLeaving MPE/iX was only the start for the SBCTC. It's got a new ctcLink project in play, one that will reach as many colleges as the effort which the organization called Lift & Shift back in 2010. Once ctcLink is finished, it will implement Oracle/PeopleSoft ERP software applications, including Campus Solutions, Finance, and Human Capital Management pillars, at all of its 34 colleges.

Anything that's one step behind what's freshest can be called a legacy solution. Making a migration can be an opening step in a longer campaign. That's why it's a good practice to think further ahead than four years while eliminating MPE/iX applications. Legacy can apply to software that's still being sold and supported, too. The timeline above plotted only the MPE/iX migration at SBCTC. Making a tactical timeline like that one is a crucial step. Ensuring the choices will be seamlessly integrated with the next step, and they will last, is a bigger task. Because no application platform is ever the last one — not if an organization wants to outlive its IT plans.

Posted by Ron Seybold at 04:54 PM in Migration | Permalink | Comments (0)

April 27, 2016

The Remains of Any Need for CPUNAMEing

Dress FormsEarlier this week a reseller in the 3000 market offered an N-Class 3000 with an upgraded CPU. The server's HPCPUNAME, however, reflects a slower model of the system. These names of systems are actually a part of the 3000 process that Hewlett-Packard regards as ongoing business. There are oh-so-many names of 3000 systems. In some cases, what your software sees in the name is not what you get. 

HP's support for the 3000 terminated at the end of 2010, but there are a few HP services that continue today. Name changing is among them. Steve Suraci of Pivital, which sold 3000s as an official reseller until HP stopped that sort of business, says it's a lock that HP didn't do an N-Class upgrade that doesn't have a corresponding HPCPUNAME change. "For sure HP didn’t do the upgrade," he said. Outside the lines upgrades can be a way to skip software upgrade fees.

The only thing pertinent to the current 3000 community is HP's CPU rename service. When HP did this with support engineers at a time plus materials engagement, a software-to-hardware blessing changed the HPCPUNAME and HPSUSUAN numbers for replacement 3000s. When a CPU board dies, or a system needs to be updated at a fundamental level, Hewlett-Packard still owns the only software that can transform replacement hardware into your hardware — complete with reinstated numbers that allow third-party programs to run unfettered.

This service is still available, if you insist, from HP. A server that reports it's a 550 MHz N-Class, while it's actually a 750 MHz system, could use this kind of correction. What's important, though, is whether an N-Class will be fast enough. Reporting a different HPCPUNAME can keep third party software from running. That issue can be corrected by calling the software vendor, who'd probably be glad to hear from an MPE customer.

Read "The Remains of Any Need for CPUNAMEing" in full

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

April 25, 2016

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.

Read "Proving concepts leads to hardware exits" in full

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

April 22, 2016

How to Transform MPE Spoolfiles to PDFs

HP 3000 data becomes more useful if it can be e-mailed as industry standard report documents. After more than two decades of pushing at it, Adobe has made its PDF the de-facto way to exchange documents, even complex ones.

Which might have prompted this question from HP consultant and Suprtool trainer Jeff Kubler:

Does anyone have a lead on a tool that converts spoolfiles to PDF files? Are there any Contributed Library tools?

It won't be in the Interex Contributed Library (because the programs have gone underground; ask your colleagues if they have a swap tape) but the txt2pdf product works nicely to make this conversion. Even in its most advanced version it's about $1,000, at last glance. Bob McGregor reports as much.

Jeff, txt2pdf does this. We have a job that runs that:

1. Checks a pseudo device we have setup for any spoolfiles that are on the device with an PRI >0

2. If it finds a spoolfile, we convert it to PDF and move it to a server

3  Sends an e-mail to the streamedby variable telling them the PDF doc is ready on the server.

4. Alters the priority to 0 to mark it processed

We've been using it for a couple years, and it works great — of course, once we got the bugs worked out. What's cool is if someone delete the file, we just adjust the priority to something greater than 0 and it gets reprocessed.

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

April 20, 2016

Like a Classic Mercedes, Those Old 3000s

Built to last.

That's what a veteran analyst called the HP 3000s at her company. It's a UK firm, The Wesleyan, and it's been running MPE and MPE/iX since at least 1990. Jill Turner says the oldest system is a Series 947. That would be the early part of the 1990s, to be sure.

MercedesThat 947 and four other HP 3000s including an N-Class, are going offline in 2017. "We are a financial services business, and the HP 3000s hold all the policies sold up to about 2010," she said. "These are serviced daily, weekly, monthly, yearly depending on the type of policy."

Turner called those 900 Series systems, including a 987 and 969, "old proper machines." They're the sort that never quit. They do eventually get out-performed by newer models, or can't run Oracle, or have experts with knowledge about 3000s retiring soon. The hardware does age, though, as it does for all owners. That's not why the 3000s are leaving The Wesleyan.

"The Wesleyan are currently migrating the data from the HP 3000s onto a new system," Turner said, "and we expect everything to be migrated by mid- to end of 2017. As technology moves forward the company is moving to other platforms, and I think the new systems are hosted on IBM Pureflex servers."

Turner admits to being biased in favor of the 3000s. This can happen after a couple of decades of success, when a migration choice is based on the age of the hardware instead of the utility of the software. You can't beat the cost of owning a 3000, she adds.

Read "Like a Classic Mercedes, Those Old 3000s" in full

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

April 18, 2016

A Parts Supply Non-Problem for HP's 3000

CR2032One part of Hewlett-Packard's end-game fantasy about the 3000 pointed to parts. This was a server the vendor wouldn't build after 2003, HP warned. You could not be sure your server and its essentials could be serviced -- where would the parts come from? For the last decade and more, HP's 3000 parts have come from everywhere. About the only hardware services supplier constricted by the halt in HP manufacturing of parts was -- wait for it -- HP.

While practicing the careful shrink-wrapping of HP-built replacement motherboards, disks, IO buses and power supplies, the market has shared and sold ample hardware to replace 3000 systems. One reseller reported on the 3000-L he has hundreds of HP 3000 terminals on hand and was ready to send them to the scrapper. There might be sites where HP's tubes are essential for production operations, but I hope not. The scrap heap looks like the next stop for those 700/92s.

On the other hand, there are a few consumable items that make HP's hardware hum. One is essential to smooth operation of a service processor. You can get a replacement part for this processor at your grocery store.

Read "A Parts Supply Non-Problem for HP's 3000" in full

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

April 15, 2016

Use GSP and More for 3000 ID, control

GSP boardThere's been plenty of change in the 3000 manager's life over the last 15 years. Some of the change is a little easier by exploring the use of the Guardian Service Processor. It can help in changing the location of HP 3000 consoles from one part of a shop to another. There's even a story out there that says the identity of the HP A- and N-Class hardware resides in the GSP.

Kent Wallace, while a 3000 manager for Idaho-Oregon healthcare delivery system Primary Health, needed to move his 3000 console.

I must move the 3000 console another 10 feet farther from the rack (it's an N-Class HP 3000/N4000-100-22). What are the 3-pin positions on the wire that I need to extend its RS-232 cable?

Our blog contributing editor Gilles Schipper chipped in with a solution offering even farther movement:

If you want to extend the range of the console to anywhere on the planet (at least where there’s Internet access) you could consider the HP Secure Web Console to replace the physical console. Depending upon the condition of your physical console, this solution may also save a bit of wear and tear on your eyeballs, instead of adjusting those pins.

Schipper wrote us a great article on setting up such a web console. The GSP is quite the tool.

Read "Use GSP and More for 3000 ID, control" in full

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

April 13, 2016

Stromasys returns to webinar lineup April 19

The NaturalEmulation and virtualization vendor Stromasys returns to the web airwaves next week with an event that examines the return on investment for its Charon family of software products, including its HP 3000 model HPA. The event begins at 11 AM EST for US viewers, 5 PM CEST for Euro IT managers. 

The company last did a webinar for the 3000 market in 2012. At the time, Charon HPA was still a nascent product, without the portfolio of success stories and case studies it's built in the 3000 market. The previous show explained the concepts and demonstrated administration and management of the software. The April 19 event will reach for more strategic perspectives, but will include a technical angle, too.

Worldwide Strategic and Global Accounts manager Ray LeBrun will be joined by Systems Engineer Darrell Wright on the one-hour webinar. Doug Smith is the HP 3000 product manager for the company. Smith is managing a limited-time discount offer on Stromasys services for Proof of Concept and full integration of Charon HPA.

The company promises the webinar will offer

An overview of legacy system pain points and the difficulties businesses like yours may encounter as they determine how to move forward with their legacy systems. Learn how your organization can improve the ROI of your legacy systems while also minimizing risks of unplanned downtime.

Stromasys says that space is limited for the webinar. The event includes information for Digital and Sun systems as well as the 3000. Registration is online, which yields a confirming email that provides login instructions for the GoToWebinar event.

Posted by Ron Seybold at 06:48 PM in Homesteading, Web Resources | Permalink | Comments (0)

April 11, 2016

Yes, Virginia, there is MPE at the Terminal

VIT logoOne of the first HP 3000 migration success locations might have hung on to an MPE/iX app since its story was introduced by the vendor. A lively discussion popped up last week when Don Seay asked on the 3000-L mailing list about running Speedware on the Stromasys Charon HPA virtualizer software. The chatter included updates on the work to cross the 2027 hurdle for MPE/iX use, as well as reports on the speediest settings for Charon.
VIT photo

Seay was emailing from an address at VIT.org, the legacy location of Virginia International Terminals. It's the port authority for all shipping in Norfolk, Newport News and environs. A shiny website handles just about all of the data requests at portofvirginia.org. But there's still data being fed to VIT.org, and Seay's request seems to hint that an application continues to work there. We're checking in with him.

Taking a full-on approach to a migration is a typical opening strategy, but there are sometimes good technical reasons why apps remain on 3000 hardware. This didn't seem likely when we first heard about the 3000 and VIT in 2002. HP was promoting the practices and concept of retiring 3000s during that time, the first full year after Hewlett-Packard's announcement it would leave the 3000 marketplace.

VIT’s assistant IT director at the time, Clark Farabaugh, said at HP World 2002's migration roundtable the decision to shift to HP’s Unix servers “has changed our shop, for better or worse.” That summer, IT began to migrate at VIT. The organization took delivery of a HP 9000 rp8400 server to replace its HP 3000s, and Farabaugh said “we were the first ones on board.” We took note of the report of 13 years ago.

The applications running at VIT handle shipments through a terminal with 7,000 international longshoremen at work, and a desire to Web-enable the apps led VIT away from the 3000. The IT director said the migration project will take 12 to 18 months to complete using the 45-person IT staff, taking apps from Speedware on the 3000 to Speedware on HP-UX.

Read "Yes, Virginia, there is MPE at the Terminal" in full

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

April 08, 2016

Hardware's emulation puts software at ease

MirrorIn the earliest days of the 3000's Transition Era, advocates for MPE/iX formed the OpenMPE user group. But the first campaign for these engineers (and a few businesspeople) was for the emulation of MPE itself. The ideal was that if MPE/iX source code could be turned over to the community -- since HP had no real interest in the future of the 3000 -- then the OS and its subsystems would be pushed onto newer hardware.

The ideal was open source for MPE/iX. That campaign assumed plenty of change was in the future of 3000-based software. The reality that formed about compatibility of software is illustrated in the everyday experience of Charon users.

One checked in this month with a summary of how smooth his software slipped into the Charon HPA environment. The emulation that paid off was virtualizing the RISC hardware. The caliber of the solution made things easy for Jeff Elmer.

I can say that since what is emulated is the PA-RISC hardware and not MPE, it seems unlikely that there would be any software incompatibilities.  Everything we use (multiple third-party tools plus in-house COBOL/IMAGE software systems) just worked.  It really was true that no one would have noticed a difference unless we told them.

The single item that we had to modify was in our backup job stream.  We had a tape rewind command in the job that was no longer needed and which the emulator at that point (in 2013) did not understand.  The "fix" took less than 60 seconds when I removed that clause from the job.

Read "Hardware's emulation puts software at ease" in full

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

April 06, 2016

Stromasys reports aim at speed, and help

InstrumentsThe fine art and craft of tuning an Intel-based server to mimic HP's 3000 hardware has evolved. The Charon HPA emulator has been in production shops for more than three years. In the beginning, the software's demands on hardware were outlined in a table of preferred servers. Or in calls to a product manager. The latter has always produced more robust performance than the former. A recent string of messages on the 3000-L showed why. They also showed that a 3000 jobset that ran three times faster, after "setting power management to dynamic."

Performance tips on the L about selecting and tuning for the best hardware have included the following advice

Set other settings for performance
System Isochronous Mode enabled
Hyper-thread off or 1
Turbo-boost enabled
c-states enabled
Intel Speed Step enabled

If this set of instructions doesn't make much sense to a prospective user, it illustrates why Charon HPA is a fully-guided product by now. Customers and prospects buy services from Stromasys to deploy this solution. There's no other way. Downloadable freeware copies left the marketplace last year.

Emulating a legacy hardware server to run enterprise-grade applications is not a hobbyist's mission. Stromasys product manager Doug Smith says the customers have been better served with engineering-driven integration insights. He's got success statistics to prove it.

Read "Stromasys reports aim at speed, and help" in full

Posted by Ron Seybold at 09:30 PM in Homesteading, User Reports | Permalink | Comments (0)

April 04, 2016

Working to Set MPE's Future to Forever

AbacusWhen a 3000 manager asked about running Speedware on the Stromasys Charon HPA emulator, the question evolved quickly. In just a few hours, MPE experts were talking about how long the OS could keep running. The detour of the 2027 CALENDAR intrinsic came up. It turns out the community experts are already working on that.

Jeff Elmer of Dairylea Cooperative, whose success story with Charon was part of our 2014 reporting, told the readers of the 3000-L that he's pleased with the way the Stromasys product cut out HP's MPE/iX hardware. The words "run MPE forever" were part of his message.

We used HP's 3000 hardware for 30 years. We've been using the HPA3000 emulator in production since December 2013. Our users would have never known the difference if we had not told them.

We had a 969KS 100 and went to a 2-CPU A-Class on the emulator. Performance is essentially identical but all concerns about "ancient" hardware went away. (Our RAID array hard drives were older than our web developers). Charon is running on a 1U "off the shelf" Proliant server under the Red Hat Linux environment (if we didn't have a DLT8000 and a DDS tape drive attached to it, all that it would take up in the rack would be the 1U). We run our disaster recovery version of the emulator in another location under VMware on OmniCube hardware, although we have never used it for anything other than testing.

Forever"Based on our experiences we would recommend it to anybody," Elmer said. "You could run MPE forever with this setup and over time your performance would only improve as you put newer, faster hardware under it." Whoa, forever? It's the promise of virtualized servers that emulate antique hardware. But MPE/iX has that calendar problem that'll rear up at the end of 2027, right? Not so fast there, said one MPE expert.

Read "Working to Set MPE's Future to Forever" in full

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

April 01, 2016

MPE source code ID'ed as key to encryption

In a news item that appeared in our inbox early this morning, the researchers at the website darkstuff.com report they have identified the key algorithm for iPhone cracking software to be code from the 1980 release of Q-MIT, a version of MPE. The iPhone seized as part of an FBI investigation was finally cracked this week. But the US government agency only reported that an outside party provided the needed tool, after Apple refused to build such software.

IPhone crackThe specific identity of the third party firm has been clouded in secrecy. But the DarkStuff experts say they've done a reverse trace of the signature packets from the FBI notice uploaded to CERT and found links that identify Software House, a firm incorporated in the 1980s which purchased open market source code for MPE V. The bankruptcy trustee of Software House, when contacted for confirmation, would not admit or deny the company's involvement in the iPhone hack.

A terse statement shared with the NewsWire simply said, "Millions of lines of SPL make up MPE, and this code was sold legally to Software House. The software does many things, including operations far ahead of their time." HP sold MPE V source for $500 for the early part of the 1980s, but 3000 customers could never get the vendor to do the same for MPE/iX.

Lore in the 3000 community points to D. David Brown, an MPE guru who ran a consulting business for clients off the grid and off the books, as the leading light to developing the key. An MPE expert who recently helped in the simh emulation of Classic HP 3000s confirmed that Brown's work used HP engineering of the time in a way the vendor never intended. Simh only creates a virtualized CISC HP 3000 running under Linux, so MPE V is the only OS that can be used in simh.

"Lots of commented-out code in there," said the MPE expert, who didn't want to be named for this story. "Parts of MPE got written during the era of phone hacking. Those guys were true rebels, and I mean in a 2600-style of ethics. It's possible that Brown just stumbled on this while he was looking for DEL/3000 stubs in MPE."

The FBI reported this week that its third party also plans to utilize the iPhone cracker in two other cases that are still under investigation. Air-gapped protocols were apparently needed to make the MPE source able to scour the iPhone's contents, using a NAND overwrite. The air gapping pointed the DarkStuff experts toward the HP 3000, a server whose initial MPE designs were years ahead of state-of-the art engineering. "Heck, the whole HP 3000 was air-gapped for the first half of its MPE life," said Winston Rather at DarkMatter. "It's a clever choice, hiding the key in plain sight."

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

March 30, 2016

Big G anniversary recalls era of 3000 crunch

Wheaties 3000This month marked the 150th anniversary of General Mills, the benevolent cereal giant that started its business just after the Civil War milling flour. The maker of Wheaties, Gold Medal Flour and Play Doh, the company known as the Big G got a rousing eight minutes of celebration on the CBS Morning News this weekend. When the report turned to Wheaties, it triggered a memory of one special era for the HP 3000. MPE/iX once managed a giant boxcar-load of operations for the food company, a firm so large it acquired fellow 3000 customer Pillsbury in a 2000 deal that teamed century-old rivals to make the world's fourth-largest food company.

Powerhouse was an essential part of the Pillsbury legacy, but the reach of the 3000 was even deeper at General Mills. Mark Ranft, who operates the Pro 3K consultancy, said his time at the Big G covered the years when core corporate functions were controlled by a fleet of 3000s.

"I was the system admin for all the HP 3000s at General Mills," Ranft said. "At one time they had 30 systems.They were used for plant, logistics, warehouse management and distribution applications. We had a proprietary network called hyper channel that allowed fast communications between IBM mainframe, Burroughs (Unisys), DEC and the HP 3000 systems."

It was an era where the 3000 community dreamed of earning attention from Hewlett-Packard, as well as enterprises which were considering Unix. The 90s were the period when HP-UX vs. MPE was in full flame inside HP as well as among customers. In 1993 Hewlett-Packard ran an ad in Computerworld and InformationWeek touting the use of the 3000 at General Mills. One of the best pieces of HP advertising about its longest-tenured business system, the ad captured the flavor of the cereal giant.

It also helped us on the way to another anniversary being celebrated this month. Ranft dropped us a congratulations, along with other 3000 lovers, on the 21st anniversary of the first stirrings of the NewsWire. "I am so happy that you have done this for us for all these years," he wrote us. Growing notice of the large customers of the 3000 pushed Abby and I to start a business plan, project revenues, and research readership and sponsors during March, 1995.

Read "Big G anniversary recalls era of 3000 crunch" in full

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

March 28, 2016

For any fate, applications need budgets

Fate-destinyAt 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.

Read "For any fate, applications need budgets " in full

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

March 25, 2016

Replacing apps: a migration option, or not?

More than seven years ago, HP was still offering advice to its HP 3000 customers about migration. The vendor sent everyone down an evaluation path once it announced it was dropping the 3000 from its 2007 lineup. Sales halted in 2003; the HP Services lineup included MPE and hardware support for another seven years, though.

Sourdough-hopeThat's by way of noting that HP's plans saw lots of waffling before its time ran out for stewardship of the servers. In the years between its cutting-out announcement and the end of formal support, HP plans to migrate had two major options. Rewrite whatever you had running on MPE, or replace it with a work-alike app. At the time, HP had a VP who'd talk about this. Lynn Anderson was the last HP executive who would even address the 3000 before the press. Her expertise was in services. You can imagine how replacing apps set with her. Bad idea, she said at the time. Bake a fresh loaf, using the sourdough starter of 3000-based business processes.

Anderson was pretty unique in the HP management ranks. She could show IT experience on the HP 3000. She started her career working on an HP 3000 in the mill town where she grew up. A Series II system displayed her first MPE colon prompt. Later on in programming and system engineering for HP, she was a network specialist for MPE, a job that included the high point of bringing up the first HP 1000-to-HP 3000 local area network.

To the HP of 2008, a rewrite looked like the best way to preserve what you'd created. However, MB Foster is going to talk about replacing apps next week. Wednesday the 30th at 2 PM Eastern, George Hay will examine this Replace option. "You will learn the factors that affect application replacements and the steps in the replacement process," the company said in its email notice of the webinar.

In 2008, Anderson spread HP's message that the company preferred rewrites to getting an off-the-shelf app to duplicate years of architecture and development under MPE/iX. She cited an HP-funded study that predicted nearly half of the 2008 IT workforce would be retired by 2011 — a figure that had all the accuracy of HP's 2002 prediction that 80 percent of its customers would leave the 3000 by 2004. Speaking at the HP Technology Forum, Anderson talked about replacements chosen to match existing MPE/iX apps, versus rewrites.

"Matching can disappoint," she said at the time. "We say don’t look at what you want your application to do today, but what do you want it to do tomorrow. For the DIY customer, do you have the personnel?" The question was about brain drain, a very real prospect for a legacy technology customer. It was also the question you'd expect to hear from a services vendor.

Read "Replacing apps: a migration option, or not?" in full

Posted by Ron Seybold at 07:00 PM in Migration, Web Resources | Permalink | Comments (0)

March 23, 2016

Putting a CPUNAME on HPSUSAN's profile

The MPE is a most unique creature of the computer ecosystem. This is software that does not have its own license, specifically. According to HP, the ownership of any MPE/iX version is determined by ownership of an Hewlett-Packard 3000 server, one built to boot up MPE/iX. When a copy of MPE is moved onto a Charon virtualized server, it must come from one that's been assigned to one of HP's 3000s. 

SusanWe reached out for clarity about this when a major manufacturer was looking into replacing HP's 3000 iron with Charon licenses on Intel systems. After the MPE/iX software is turned off on any replaced 3000 hardware, does its hardware-based license then expire? The operating system license, according to HP's MPE Technical Consultant Cathlene Mc Rae, is related to the HPSUSAN of the original HP hardware.

So wait a minute. Are these HPSUSAN numbers of 3000s considered de-licensed, even if they're going to be used on the Charon emulator? Mc Rae explained.

The HPSUSAN number is different from the MPE/iX license, although there is a relation between the two. The ability to use MPE/iX on the emulator is a result of completing a Software License Transfer. The original MPE/iX license on the HP e3000 would then no longer exist. 

In the hardware world of HP 3000s, HPSUSAN takes the original serial and model numbers on the system. It remains the same, as long as the customer owns the system. This combination was used to ID the hardware and enable diagnostics for the correct system.

However, that transferred license for the MPE/iX installation on the Charon emulator -- available via a $432 Software License Transfer Fee -- won't be getting a new HPSUSAN number during the process. HPSUSAN gets re-used, and so it leads us to see what HPSUSAN stands for, and how the HPCPUNAME is a key in emulator installations.

Read "Putting a CPUNAME on HPSUSAN's profile" in full

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

March 21, 2016

Free software worth the time to track it down

It's entertaining and heartening to discover someone who's new to the HP 3000 and MPE. Fresh users tend to run in the hobbyist lanes of the IT race these days. Sometimes, however, they can ask questions that uncover values for the existing managers of the MPE server.

FreeThat's been the case with Michael Kerpan. He's just discovered the new freeware simh emulator engine for creating MPE V Classic HP 3000s. Kerpan is just pursuing this as a hobby project. "I'm not retired, but I'm also not in the IT business at the moment," said, "though I do maintain my SF club's library catalog server, which is a Linux box."

On the HP 3000 front, his box is a Windows server running simh, but Kerpan wants more than just the stock MPE V Fundamental Operating System to use. Kerpan specifically asked about the old Interex Contributed Software Library. The CSL started out as a swap-tape built from reel tapes that attendees at conferences brought along. Drop off the programs you wrote on your reel -- or eventually, DAT tape -- and pick up a compilation of such contributed software when the conference adjourned.

The CSL dropped off the radar of the 3000 community once Interex went bankrupt. The collection of programs wasn't even listed in the organization's bankruptcy assets. In some places out in the community CSL tapes still exist, but trading them hasn't been a compelling pasttime. However, MPE contributed software, now called open source and freeware, still exists. Knowing where to track it down is often worth the effort, if managing a 3000 is still your job.

Read "Free software worth the time to track it down" in full

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

March 18, 2016

Big files get zipped, moved on HP 3000s

ZipperA computer manager who's new to the HP 3000 is looking for CSL files this week. The Contributed Software Library is just an oasis to this IT veteran, something shimmering in his future that holds a highly useful thicket of utilities and more.

Someone in the 3000 community is bound to connect our new user with this CSL, for one reason: he's looking for MPE V programs to supplement his discovery of the emulated Classic HP 3000, simh. That's the MPE V-ready version of a virtual HP 3000: what amounts to a CISC skin for a 3000 on top of the simh code. Whenever the newbie connects with a CSL resource, if they've got their files on a 3000 they're bound to need to send about 24MB to him. That's going to require zipping them.

The act of zipping to compress for a transfer is an essential in 3000 management. Although the code for compressing files on HP 3000s is more than a decade old, like a lot of things on the system, it continues to work as expected.

Tracy Johnson, who manages the Invent3K server operated by OpenMPE, noted he's using the MPE/iX Posix shell's compress and uncompress. "It creates a file that ends in capital Z. Seems the compressed format is compatible with both GNU-zip and Winzip programs or any other Unix/Linux machine."

Lars Appel, who ported the Samba file sharing tool to MPE, offers a comprehensive answer. He points to an HP 3000 Web starter software kit that resides on a development server, open to the public.

Read "Big files get zipped, moved on HP 3000s" in full

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

March 16, 2016

Brain drain reduces migration options

Retirement exitAt a large Eastern Seabord organization in the US, the exit of MPE-skilled staff has cut away the migration choices for its HP 3000 operations. The server ran the organization's management of equipment parts. Some of the parts are being tracked back into the 1980s, so unique are those components.

It's like taking the durability of an HP 3000 and applying its model to vehicles, for example. Old F-150 pickup trucks, or the most beloved Jeeps, need parts that might've been designed decades ago. Get a large enough fleet and you need an extensive and fast database. 

IMAGE/SQL drove all of the enterprise business operations until 2002, when other solutions started to rise up at this enterprise. The HP 3000 9x9s there stepped back into a support role, running the parts application. When HP announced the 3000 was leaving its product list, the organization started to plan for a database migration.

"I still had a licensed HP-UX server (HP9000/I70) with paid software support at that time," said the IT manager, who didn't want us to use his name. "The plan was to purchase Eloquence for HP-UX, move IMAGE data to Eloquence, and rewrite our data entry and retrieval programs from their original Pascal to something on HP-UX, which might have been Pascal (if available) or C."

The migration to Eloquence, with what the manager called "universal homing capabilities," would be moved to Linux, which might have required another program rewrite. It could have been as simple as going from C on HP-UX to C## on Linux. Then expertise started leaving the organization.

Read "Brain drain reduces migration options" in full

Posted by Ron Seybold at 11:33 AM in Migration, User Reports | Permalink | Comments (0)

March 14, 2016

Upgrade bargains on 3000s remain in play

FilenesAlthough the prices on the systems remain on the slide, there are still customers in the US who look to beef up their HP 3000 hardware from time to time. 

"We still have units that are licensed and salable," said Pivital Solutions' president Steve Suraci. "We still have customers occasionally looking to upgrade."

Prices for even the largest of HP's MPE system line are being quoted below $10,000, and in some locations, a deeper discount than that. Like the goods sold in the basement at the legendary Filene's, the word cheaper comes to mind—because the pedigree of each 3000 system's MPE license is sometimes the most important element. (Healthy disks are pivotal, too.)

Bonafide machines have valid HPSUSANs. It's essential for moving MPE apps and utilities during an upgrade. In the scruffiest days of the 3000 resale history, HPSUSANs were being slapped onto HP's L-Class hardware with rogue software, making a 3000 out of a cheap 9000. People went to jail over that episode from the end of the 1990s.

But even a valid HPSUSAN is not the same thing as a proof of license. A continuous chain of ownership paper trail makes for a fully-licensed system. Such a license can be important to the customers who care about keeping auditors happy. That level of validation isn't required for a support contract, though, since HP's long been out of of the MPE/iX business.

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

March 11, 2016

New 3000 simulator looks back, not ahead

Hp2112bCommunity members on the 3000-L newsgroup have been examining a new entry in the emulation of HP hardware. However, this simulator creates a 3000 under Windows that only runs MPE V. The MPE version of SIMH — a "highly portable, multi-system simulator" — is a Classic 3000 simulation, not something able to run PA-RISC applications or software.

Some 3000 users are embracing this software though, maybe in no small part because it's free. It's been more than 15 years since HP supported MPE V and the CISC-based systems that launched the 3000 line starting in 1972. One of the experts in PA-RISC and MPE/iX computing, Stan Sieler, briefed us on what this freeware simulator can do, and what it cannot  — in addition to not running MPE/iX.

Currently only Charon from Stromasys runs PA-RISC. Thus, the SIMH runs only the Classic HP 3000. At the moment, it’s an old version of MPE V (Q-MIT, release E.01.00)

And, the machine probably has no networking support. It probably has some kind of serial datacomm support, but I haven’t looked at that yet (all my use has been via the simulated console, LDEV 20).

I’ve put several hundred CM programs on the “machine” to see which will load and run. Many won’t, because they use newer features (e.g., FLABELINFO intrinsic which came out on the T-MIT with the Mighty Mouse).

So, you ask, can you put a newer version of MPE V on the emulated 3000?

Read "New 3000 simulator looks back, not ahead" in full

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

March 09, 2016

Powerhouse MPE futures clouded in silence

Unicom GlobalUsers of Powerhouse have a mailing list, much like the one that HP 3000 owners and managers have enjoyed for decades. Powerhouse-L has traffic on several flavors of the Cognos creations. It's that range of product platforms that gives readers a chance to compare.

The news for MPE users of Powerhouse is that there is no news. This isn't a fresh take on the future of Powerhouse, Quiz, and the other products like Axiant which remain in use in the homesteading marketplace. Ken Langendock, a consultant in the market, asked on Powerhouse-L about the future of the products. He added that getting a response from Unicom Global, the owner of the products, has been difficult for his boss. It's not a good sign when a customer cannot get multiple calls returned.

Langendock was plain-spoken about which Powerhouse he needed an update for. A webcast from the vendor on March 4 didn't include Powerhouse futures by the 30-minute mark, so he pulled the plug on his viewing. He said MySQL support was high on his list of needs.

"The HP version to me is dead," he said. "I expect nothing more to happen on that version." That tracks with the reality of 2016 management from Unicom. When the software changed hands at the start of 2014, hope for changes to licensing and features rose in the MPE user base, but not for very long. Unicom owns scores of products by now, using a model that runs smoothly for Infor, owners of MANMAN.

Ownership of a product includes a paid support option, but not much will change for the 3000 world. An update from Bob Deskin, longtime Powerhouse product manager who consulted with Unicom in 2014, made no mention of MPE/iX after he reported his contact with Unicom.

We've reached out to Russ Guzzo, who heads the company's communications efforts and led the integration of Powerhouse into the company, but didn't get a reply to our question about, as Landendock put it, "doing something with Powerhouse."

Read "Powerhouse MPE futures clouded in silence" in full

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

March 04, 2016

3000-L breaks silence with DTC primer

DTC NetworkOn the verge of four weeks without a new message, the 3000-L mailing list and newsgroup delivered a primer on the control of DTCs on MPE/iX networks. A longtime contributor to the community set up a question about using these venerable devices that connected HP's terminals and other devices to a 3000.

I have multiple HP 3000s sharing one DTC.  My problem is, which one controls the DTC?  In the event of  a power cycle, there is a race between them for which 3000 will download the new configuration.  I need system A, my A-Class, to be in charge. However, systems B or C are most likely to download first, leaving me with the manual step of unplugging the network from B and C, power-cycling the DTC, and then waiting for the A-Class to download the configuration. Is there anything that can be done to just leave the A-Class in charge?

Tracy Johnson replied, "It's always been a crap shoot. I'm of the opinion the first HP 3000 to notice the DTC needs downloading will do the job. Which usually means the less busy machine." As it was just the first answer on the newsgroup, there was still a need to do unplugging.

Read "3000-L breaks silence with DTC primer" in full

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

March 02, 2016

Data in motion follows 3000 archival project

HMSHostHMSHost has been an HP 3000 shop since long before the start of this century. The company that operates duty-free outlets in major US airports has made changes to its datacenter structures that have put its 3000 in cool standby. Regular operations have moved to another server. Archival has become the mission for the MPE/iX server.

Brian Edminster told us about the changes to the company's IT operations, having managed the 3000 solutions for HMSHost for many years.

The live and current data that was hosted on the application under MPE has been migrated to systems belonging to the new owner of the retail division of HMSHost.  Several years ago, HMSHost sold off their retail division to World Duty Free, USA (the US arm of the global World Duty Free Group, WFDG). In a surprise move, WDFG was then acquired by one of its rivals, Dufry. In talking with some friends that still work there, the former-3000 data will likely need to be migrated to yet again—to the Dufry systems. Talk about “data in motion!” 

But as it turns out, the historical 3000 data (from before WDFG acquired the retail unit) still has to be retained for compliance reporting for about three more years. They've decided to keep an A-Class system, basically in a cool backup environment. The server is still racked in their server room, but is kept powered off, until one of these events occur: 

1) a compliance report and/or analysis is required (a fairly low probability), or

2) a quarterly reboot/confidence check is scheduled.

Read "Data in motion follows 3000 archival project " in full

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

February 29, 2016

Making the Years Count in One that Leaps

He was once the youngest official member of the 3000 community. And for a few more years, he still has the rare distinction of not being in his 50s or 60s while knowing MPE. Eugene Volokh celebrates his 48th birthday today. The co-creator of MPEX must wait every four years to celebrate on his real day of birth: He was born on Feb. 29 in the Ukraine.

Like the HP 3000 and MPE itself, years do not appear to weigh heavy on the community's first wunderkind.

Eugene at 48Although he's no longer the youngest 3000 community member (a rank that sits today with Myles Foster, product manager for MB Foster in this first year after his recent double-degree graduation from Carleton University) Eugene probably ranks as the best-known member outside our humble neighborhood. He built and then improved MPEX, VEAudit/3000 and Security/3000 with his father Vladimir at VEsoft. Then Eugene earned a law degree, clerked at the US 9th Circuit Court, and went on to clerk for now-retired US Supreme Court Justice Sandra Day O'Connor -- all en route to his current place in the public eye as go-to man for all questions concerning intellectual property on the Web and Internet, as well as First and Second Amendment issues across all media.

Eugene's profile has risen enough since his last birthday that the Associated Press included him in its latest "Born on This Day" feature. He's appeared on TV, been quoted in the likes of the Wall Street Journal, plus penned columns for that publication, the New York Times, as well as Harvard, Yale and Georgetown law reviews.

When I last heard Eugene's voice, he was commenting in the middle of a This American Life broadcast. He's a professor of Constitutional law at UCLA, and the father of two sons of his own by now. Online, he makes appearances on The Volokh Conspiracy blog he founded with brother Sasha (also a law professor, at Emory University). Since his last birthday, the Conspiracy has become a feature of the Washington Post.

In the 3000 world, Eugene's star burned with distinction when he was only a teenager. I met him in Orlando at the annual Interex conference in 1988, when he held court at a dinner at the tender age of 20. I was a lad of 31 and people twice his age listened to him wax full on subjects surrounding security -- a natural topic for someone who presented the paper Burn Before Reading, which remains a vital text even more 25 years after it was written. That paper's inception matches with mine in the community -- we both entered in 1984. But Eugene, one of those first-name-only 3000 personalities like Alfredo or Birket, was always way ahead of many of us in 3000 lore and learning.

Read "Making the Years Count in One that Leaps" in full

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

February 26, 2016

21 days of radio silence on the 3000-L

Right_WirelessTelegraphThe slowing current of 3000 communication showed a fresh signal by the end of this month. As we write it's been 21 days since a message of any kind on the 3000-L MPE newsgroup. The resource that carried 45 messages during last February has 10 for the current month. All of this month's traffic was wrapped around finding resources: Brian Edminster of Applied Technologies and Vesoft support. Both were located.

However, the three weeks without a new message is new territory for the community's log of technical help and outreach by cohorts. Among those who were posting during 2015, several told us they're on the mailing list-newsgroup out of habit — rather than needing details for their datacenter's 3000s.

"I’m still on the list out of inertia, nostalgia and mild interest," said Dave Heasman, a UK IT manager. "My employer got rid of their 3000s and me in 2008. Bought a series of packages to replace a big bespoke brokerage/investment system."

Robert Mills said he "remained a member of the list, mainly as a lurker, to keep appraised of what was happening in the 3000 community. Except for three requests in September 2012, December 2014, and February 2015, I've only posted to the list when I felt that the 3000 knowledge I had would help somebody solve a problem." Mills said he retired when his company went insolvent in 2009, but he's kept his hand in IT.

"I have been involved with the GnuCOBOL (formerly OpenCOBOL) Project on SourceForge since October 2014, and decided to write a macro preprocessor that emulated the functionality available on the 3000," he said. "The preprocessor, CobolMac, is now in its 5th version (B.04) and has received good reviews by its users."

Others who contacted us said they haven't worked on the 3000 since the days that HP sold support for MPE/iX. "I have been a BizTalk developer full time since 2008," said Kent Wallace. "I needed to work, and this was the direction the world was going." The 3000-L still has more than 500 subscribers on its mailing list rolls, but much of the messaging comes from consultants and vendor experts, supplying answers to questions and tips. A total of 45 messages have passed through the list since the start of 2016. The IT pros like Wallace have taken the path to other platforms, first to HP-UX, then to Windows.

Read "21 days of radio silence on the 3000-L" in full

Posted by Ron Seybold at 05:01 PM in Hidden Value, Homesteading, Migration, User Reports | Permalink | Comments (1)

February 24, 2016

Bringing a First 3000 Love Back to Life

Antiques RoadshowStories of HP 3000 longevity are legend. Less than 10 years ago, Paul Edwards could report on a Dallas-area customer who was running a Series 70 system in production. Paul was circumspect about who the lucky company was — lucky because they were still leveraging a system HP stopped selling in the late 1980s.

Area-code-716-new-york-mapWe heard from a longtime 3000 lover in Buffalo recently who wants to turn back the calendar on his Series 42 system. By his system, we mean that literally: Matthew Bellittiere took personal possession of the same system which he learned MPE upon in the early 1980s. The 42 was a server that considered a DDS tape drive an upgrade. Reel to reel was the standard backup peripheral for any computer HP first sold during the early half of the 1980s. HP gave the Series 42 its debut in 1983.

Series 42Bellittiere waited awhile to rekindle his old flame. About 20 years ago, he took the Series 42 into his home, but only this month is he working on getting it up to speed. A system that is 30-plus years old, that hasn't been started in 10 years: some might think this is scrap, or worse. But listening to his request, we hear a man who's finding a long ago sweetheart, rescued from the mists of time.

This HP Series 42 is the first HP mini mainframe that I started on around 30+ years ago. I arranged many updates over its active life. Some of the updates include increasing the memory by exchanging the 1/2 meg cards with 1-meg boards. I upgraded to the HP670H disc drives, and also to the DDS tape drive. In 1996 the company upgraded to a Series 947, and HP did not want the 42 back. It was going to scrap, so I requested it and it was given to me. I have had it ever since with plans to get it up and running.

I had to ask: Is the Series 42 project a hobby, or a work system? "Yes," Bellittiere admitted, "it is more of a project for me." But he needs the help of MPE V experts in our community to bring his old flame back to life.

Read "Bringing a First 3000 Love Back to Life" in full

Posted by Ron Seybold at 08:56 PM in Homesteading, User Reports | Permalink | Comments (0)

February 22, 2016

Technologies to study beyond MPE skills

Open-source-in-handAs 3000 experts have seen their jobs eliminated, and their employers focus on other platforms, they have faced a challenge. What should they study next to learn marketable skills? One obvious answer is the tools in the community for migration. Some of these open a new world of learning to 3000 veterans. Learning the tools provides an entry to get familiar with new concepts. 

However obvious it has seemed to study .NET and Visual Basic, there are many shops planting outside that Windows-box. Open source software is the choice for prospects that reach farther.

Michael Anderson left the Spring, Texas school district six years ago to found his J3K Solutions consulting practice. Even then, when Linux and open source did not dominate IT plans as they now do, Anderson knew Microsoft wouldn't hold its market share.

In 2009 he suggested a good place to start learning beyond MPE were tools like ScreenJet and Marxmeier Software's Eloquence. "Ordina-Denkart's WingSpan, as well as ScreenJet, are both great products," he said. "They are both great models for software design. I have not found anything that compares to them that's within reach of small companies and independent developers." That's a statement on pricing as well as capability.

A caliber of tools like this is not yet available in the Linux/open source market, though. James Byrne, an IT manager at Harte & Lyne, says his company's "progress towards a final departure from the HP 3000 has not been as rapid as we had hoped. The main reason is the primitive nature of the tools in common use by the *nix community. These have improved greatly over the past decade, but they are still nowhere near the effectiveness of efficiency of software I used on the HP 3000 in the 1980s."

Complaints about the "Cognos Products," now owned by Unicom after a five-year adoption by IBM, have legendary status. But the gripes have been about licensing and pricing, not the subtle efficiency those advanced development tools provided. Byrne's company has been using Powerhouse and its cousins since before the products were named as such. Close to 40 years after they were introduced, the tools are still doing a better job for Byrne than open source alternatives.

Read "Technologies to study beyond MPE skills" in full

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

February 19, 2016

How hot plug disks can replace DDS offsite

300 GB Ultra SCSII need to find an alternative to DLT and DDS tapes for offsite storage. Sure, there's DS2100 and Jamaica drives. But a few $35 300GB Ultra SCSI drives would hold a lot more data with less points of failure. I'll set up a BACKUP_VOLUME_SET and use the internal disks to do store-to-disk backups of the system. 

I've always used my A-Class and N-Class systems with fiber-attached disk. Are the internal disk drives hot-pluggable? 

Jim Hawkins, IO maven for HP 3000 systems at HP, replies with details.

There are multiple layers of changes for actual hot plugs or swaps to work.  

  • You need the disk HDD to handle this electrically.
  • You need HDD physical carrier and physical interface to comply.
  • You need the system physical interface and receptacle to comply. 
  • You need your Host System Bus Adapter (HBA) to electrically support this.
  • You need the OS to be aware enough of the HBA to not get flustered by absence of the device and deal with any notifications from the HBA of the activity.   

Given that the N-Class disk cage has a screw-based cover and the HDD carriers have no quick release levers (as compared with HASS/Jamaica or VA7400) I would state definitively that there is no hot-plug intention.  

At the same time, the SCSI bus is pretty low power and low voltage, so it would be generally not-too-unsafe to experiment. But you're also close to AC inputs and they are not low power.

Read "How hot plug disks can replace DDS offsite" in full

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

February 17, 2016

Free trial UDACentral makes its debut

A corporate-grade migration tool gained a free trial version for datacenters including the HP 3000 this week, as MB Foster introduced UDACentral's latest version.

Datacenter racks"Data migrations are challenging when you need to change database types or attempt to perform data transformations during the migration," said Myles Foster, the company's new head of product development. "With the availability of a free trial our data migration product UDACentral is now easier than ever to obtain.

Along with the free version, MB Foster is also offering corporate and enterprise Software as a Service (SaaS) licenses for UDACentral. "I realized that SaaS models of UDACentral will help companies reduce costs to free up capital for other business priorities," Foster said, "and enable strategic decision-making around IT investments."

UDACentral isn't limited to MPE/iX hosts, but Foster said the tool's target includes HP 3000 sites. The software began its lifecycle in 2002 as a means to "gives migration projects the centralized switchyard for replacing data securely while preserving its integrity,” said Birket Foster at the product's rollout. For more than a decade the software was employed in migration engagements, integrated by MB Foster’s Platinum Migration Partner team, working alongside a customer’s IT group.

Read "Free trial UDACentral makes its debut" in full

Posted by Ron Seybold at 04:51 PM in Migration | Permalink | Comments (0)

February 15, 2016

Details deserve closer look for XPs and 3000

Bullet holeLast week we reported that late-generation XP storage arrays from HP work with the HP 3000. Two system integrators supplied more details on how to make a beast like the $14,000 XP20000 serve an MPE/iX server -- along with other hosts running more popular operating systems. HP ran a YouTube video back when the system's top-end was the XP12000. The video was called Bulletproof, featuring an array that continued to work after it was shot with a high-calibre rifle.

Craig Lalley pointed out some warnings about these new XPs. He called them catches, as in, "there's a catch."

The last XP array sold when the HP 3000 was given HP's death sentence was the XP1024. In order for the 3000 to talk to and control the XP array — i.e. split the mirrors, resync the mirrors and mirror status — the HP server uses a piece of software called RaidMgr. It is on every HP 3000, and it goes out with Posix. You find it in the account /tmp/raidmgr

However, the newer systems, XP10000 and up, require a different version of RaidMgr. Usually it can be found on the XP array CD. That CD holds all the firmware and documentation.

Pivital Solutions also sells and supports disk arrays. The company aids 3000 sites through MPE/iX software contracts as well as hardware service. Steve Suraci of Pivital had stronger reservations about using the XP20000 and XP24000.

"In theory, I can’t see why not — but in practice, I would be a bit hesitant," he said. "I’m not sure that a customer big enough or savvy enough to want one of these would be a good candidate to be a guinea pig, testing a theoretical solution."

Read "Details deserve closer look for XPs and 3000" in full

Posted by Ron Seybold at 06:49 PM | Permalink | Comments (0)

February 12, 2016

How to get specific about IP access for PCs

I want to give a 3000 a static IP, so I can permit a user to access the HP 3000 from that PC with that static IP. Is there a way to force a particular user ID to use a specific IP address?

Tracy Johnson replies:

A simple logon UDC should suffice:

IF HPREMIPADDR = "aaa.bbb.ccc.ddd" then
  ECHO Welcome.
ELSE
  ECHO Evil message here.
BYE
ENDIF

Bob Schlosser adds:

You can set up a logon UDC that checks that the var HPLOCIPADDR is equal to the device (PC) that you want them to use. Something like this:

LOGON
OPTION NOBREAK,LOGON
IF "!HPLOCIPADDR" <> "123.456.789.321"        change "123.456.789.321" to
your IP address
  BYE
ENDIF

Using this, we verify that the user is on the correct (assigned) IP address, and log them off if not.

Read "How to get specific about IP access for PCs" in full

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

February 10, 2016

Linux box feeds Series 918 for daily needs

Data pipelineHP never designed a smaller PA-RISC 3000 than the Series 918. The server that was released in the middle 1990s helps untold 3000 sites keep MPE/iX in the production mix. While surveying the customer base to learn about the 2016 state of the server, James Byrne of Hart & Lyne reported that a 918 at the company processes data FTP'd from a Linux system. The reason for sticking with MPE/iX, Byrne said, is the state of today's toolset for Unix and Linux. We'll let him explain

By James B. Byrne

Our firm has been running its business applications on HP3000s since 1982/3.  First on a time-share service, and then on our own equipment. Our first in-house HP 3000 was a Series 37 ("Mighty Mouse") running MPE IV, I believe.  Anyway, that is what my little brown MPE software pocket guide tells me.

We subsequently transitioned to a Series 42 and MPE V, and then a 52, and then to a Series 925 and MPE/XL, which soon became MPE/iX. Then through a 935 to our present host, a Series 918LX running MPE/iX 7.5.

And in all that time we ran the same code with the same database. We still can produce reports of transactions going back to 1984.

Presently the HP 3000 runs the greater part of our online transactions and handles all of our billings and payables. Due to changes in our business model, our main business operational application is now provided by a service bureau. Twice each working day a separate process, written using the Ruby on Rails framework, scans the PostgreSQL database, extracts all unbilled items, and produces a transaction file that is then forwarded via FTP to the HP 3000. Once the transaction file is transferred, the same FTP process triggers a job on the HP 3000 to process that file into invoices.

Our intent is to move off of the HP 3000 and onto Linux, moving away from proprietary solutions to open source computing. This includes bringing our operational software back in-house and off of the service bureau. We are actively developing software in pursuit of this strategy. However, the progress toward a final departure from the HP 3000 has not been as rapid as we had hoped.

There are many reasons for this but the main one is the primitive nature of the tools in common use by the Unix-Linux community. These have improved greatly over the past decade, but they are still nowhere near the effectiveness of efficiency of software I used on the HP 3000 in the 1980s.

Read "Linux box feeds Series 918 for daily needs" in full

Posted by Ron Seybold at 08:05 PM in Homesteading, User Reports | Permalink | Comments (0)

February 08, 2016

Newer XP storage works for HP 3000s

XP20000HP 3000 systems often use antique disks for storage and as boot drives. No device HP has integrated in a 3000 server is newer than 2003 in age, and even some later-generation disk arrays have design dates that throw back to more than 10 years ago. (We're looking at you, XP12000.)

Thankfully, there's newer storage available to HP 3000 sites. The XP20000 and XP24000 can be integrated with HP 3000s. We know of a couple of support and resale companies which do this work. Pivital Solutions continues to support 3000 sites, including integration like this. Newer storage can assure more confidence in the HP-built versions of the 3000. Older hardware gets dinged during datacenter audits, after all.

Other companies that don't write 3000 support contracts are able to connect these XP arrays. One of the other providers calls these newest StorageWorks devices "amazing storage devices for HP 3000 servers." HP put out an end-of-life notice for these arrays' XP12000 predecessor more than two years ago.

Read "Newer XP storage works for HP 3000s" in full

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

February 05, 2016

Number, Please: Finding the 3000 Set

Number-pleaseWhen I started in this line of work in 1984, writing about the Hewlett-Packard community, I had a directory. Literally, a perfect-bound directory of HP staff that worked in the company headquarters and labs in California. HP shared it with me as HP Chronicle editor, updating it every year. When someone's number at HP came up missing, you'd call up company HQ and ask for the division operator. It was the 411 of the middle 1980s. It's obvious the 3000 world needs something similar today.

As it turns out, the community does have it. The most dynamic directory resource is the 3000-L, still in use this month to locate information about contacting experts. What makes it powerful is the wetware behind the bits. Knowing which of the 3000-L posters are customers, rather than consultants, is one example of the power of that wetware.

As the week began, Bob from Ideal Computer was searching for Brian Edminster, he of Applied Technologies. Bob slipped a message under the door of 3000-L, then got an answer back about a current email address. I followed up today, just to make sure Bob got something useful. Brian's on the lookout for consulting opportunities, as well as longer engagements.

Yesterday Al Nizzardini was seeking an email address for Vesoft. A couple of replies on the L misinformed Al that Vesoft doesn't use email. That might have been true 10 years ago, but the address vesoft@sbcglobal.net lands in the offices of Vladimir Volokh and his team. Vladimir far prefers to use the phone, but he's old-school enough to enjoy an in-person visit, too.

In another update, 3K Associates and Chris Bartram are now at 3kAssociates.com. Bartram, one of the very first of the 3000 community to set up shop in the Internet, sold his two-character domain name 3k.com for a tidy sum. "We continue to sell and support our entire like of HP 3000-based software products from 3kAssociates.com," he reported on the L.

Read "Number, Please: Finding the 3000 Set" in full

Posted by Ron Seybold at 06:58 PM in Homesteading, Web Resources | Permalink | Comments (0)

February 03, 2016

MPE site sizes up Linux distro for Charon

Linux KVMWhen we interviewed one HP 3000 manager who's homesteading, James Byrne had a question about the kind of Linux that's used as a platform for Charon on the 3000. Byrne's heart rests in the ongoing lifespan of MPE apps, a thing Charon can help make possible. There's a matter of spending additional money on a proprietary solution, though, no matter how stable it is.

There's another issue worth looking at in his organization, Hart & Lynne. The Canadian logistics company has Linux wired extensively into its datacenter. Having been burned with an HP pullout from MPE, the solutions that go forward there have to meet strict open source requirements to run in the datacenter there. Nobody wants to be caught in the vendor-controlled blind alley again.

Bynre's got a problem about about something called KVM, and how genuine open source Linux needs to adhere to that product. Byrne described KVM as a Linux-kernel-based virtualization system and is therefore Open Source software.

Doug Smith, the HP 3000 Director of Business Development at Stromasys, said KVM isn't a part of the Charon installation set. "KVM is part of the Linux kernel, the part that allows Linux within itself to create virtual machines—kind of like a hypervisor. This is not utilized by our software."

KVM users have strong feelings about hard-line open source licensing. Byrne's issue is that VMware's software—which isn't required for every Charon install—looks like it might be operating outside the General Public License that many open source solutions utilize.

Read "MPE site sizes up Linux distro for Charon" in full

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

February 01, 2016

Loyalist, laggard, loser: who are you now?

Loser GloveWhen 2016 arrived on our calendar, we looked for signs of the 3000's present and its future. A survey of frequent 3000-L contributors was answered by about half of those we polled. Among that group we found half of these IT pros — selected to be sure they owned 3000s, not just consulted on them — have plans for MPE/iX in their companies in 2016 and beyond.

If you're still using HP 3000s here, getting on to 15 years after HP announced the system's "end of life," then who are you? Among your own kind, you're possibly a loyalist, devoted to tech that's still better than the alternatives to your company. After all, almost 5 percent of every Mac user runs their systems on Snow Leopard, an OS released six years ago and decommissioned by Apple in 2013. Some experts in the community say it runs faster on the newest Macs than any other OS release, though.

The glove on this page came from a Mac conference of 2006, when Snow Leopard was three years away. Maxtor was sure we'd be losing files unless we backed up to their disks. They gave us a set of three instead of a pair of gloves. The way things turned out, Maxtor lost its company status that year, purchased by Seagate. The Maxtor brand went dark in 2009, the year Snow Leopard made its debut. The OS got a small update this month, though, to keep the door open to a newer OS X.

Your 3000 loyalty may label you a laggard. That's one way to describe somebody who's among the last to migrate somewhere when anybody who's savvy has already departed. Tough word, that one. It can inspire some dread and maybe shame about holding out. Or holding on. If the vantage point and the capabilities of MPE/iX in 2016 suit you, though, laggard is just a way to segregate you from someone else's visions.

The implication and suggestion is that laggard would mean loser. Nobody will actually use that word while identifying advocates for old tech. It surely doesn't fit when your applications are solid and cannot be replaced by a migration project priced at more than a full year's IT budget. There's also the matter of keeping IT headcount lean. The most expensive parts of running a datacenter are the people. That's why cloud solutions are getting airtime in boardroom planning. MPE demands fewer heads.

"We're still using our HP 3000s," said Frank Gribbin, running the servers for the law firm of Potter, Anderson. "It's just too useful a tool to do without."

Read "Loyalist, laggard, loser: who are you now?" in full

Posted by Ron Seybold at 11:12 AM in Homesteading | Permalink | Comments (0)

January 29, 2016

Building manufacturer joins MPE, Windows

MDFPlenty of migration stories put HP 3000s to rest, either outside of the production circle or off the premises entirely. At Victor S. Barnes, which fabricates plastics, MDF, and fiberboards, the MPE/iX server which continues to run does both kinds of duty. It's an archival system, but for one key client, the 3000 continues to process orders.

"As a company we have moved on to a Windows Server package to run our company," Tom Hula reports. "The HP 3000 is largely used for reference. With that said, we are still relying on the 3000 to process orders for a large customer."

The newer Windows server package doesn’t yet support the needs of that customer. When the needed changes have been made, than the 3000 will be reference only, and eventually not used at all.
 
The route of migrating to a package has it’s pros and cons. I would say that the largest drawback is a loss of flexibility... of having to depend on others for making needed changes, or even having to tell someone something can’t be done because of the software's constraints. On the other hand, we see the largest advantages as new capabilities on the Windows package, ones that were never going to be possible on the HP 3000.

Read "Building manufacturer joins MPE, Windows" in full

Posted by Ron Seybold at 08:39 PM | Permalink | Comments (0)

January 28, 2016

TBT: A Terminal Commemoration

ChallengerThirty years ago today I sat at a Columbia PC, reading the reports of the Challenger disaster on Compuserve. The news flashed over an amber display attached to the PC, an IBM wannabe that had another life for us at the HP Chronicle. That PC was our link to an HP 3000 in downtown Austin. A printer there managed our subscription database. The software that made it possible was PC2622. The product from Walker, Richer & Quinn was the first independent terminal emulator in the Hewlett-Packard market, a way to link to 3000s without purchasing a dedicated terminal.

PC2622 boxThe purple PC2622 box sat atop that amber monitor like it perched in many 3000 shops. HP's 2622 terminal was a staple in an installed base that was growing from 10,000 to 20,000 installed servers. The HP products were priced much higher than third-party terminals. There was independent hardware to mimic the HP engineering inside the 3000-only boxes. By 1986, however, PCs were in every office and companies needed desk space for the new tools and wanted to reduce costs with a single tube at each workstation.

PC2622 disksHP was trying to promote a combo idea of its own in the era, the HP 150 PC. It was not compatible with much of the software of the day, but a Touchscreen 150 was automatically ready to be a console for MPE applications. In contrast, the Walker, Richer & Quinn PC2622 gave companies compatibility on both fronts: MS-DOS, and MPE. George Hubman was the point man for pushing the purple boxes into 3000 shops. An array of resellers around the world was making converts, too.

The late Doug Walker, founder of the company who recently died in a tragic accident, said the earliest days for PC2622 were entertaining in a "may you live in interesting times" setting. HP was not giving ground to the strategy that independent companies could deliver key software. Well, the management wasn't. But HP's field engineers, the SEs of the day, were big fans of terminal emulation, according to Walker. 

"Version 1.1 of the product had an HP 3000 file transfer program," Walker said. "The problem was how to get the file transfer program onto the 3000 side."

Read "TBT: A Terminal Commemoration" in full

Posted by Ron Seybold at 05:21 PM in History | Permalink | Comments (0)

January 27, 2016

Keeping up lets you receive what you give

Support heartWe've been checking in on how companies are keeping their MPE/iX servers up to date. One element is consistent in successful updating: continuing maintenance contracts for the software that's in production or development use. It's the heart of a healthy body of IT resources.

In one recent story we followed up on Reflection, the Attachmate HP 3000 terminal emulator product. Things have changed in PC desktop environments, since Microsoft has been hawking its Windows 10 update automatically. To get the latest Reflection version from Attachmate, keeping up on support is required. It's a paid enterprise to work on making changes to software like Reflection to support new environments such as Windows 10. Not many software solutions update themselves, said Birket Foster.

"Even free, open source software has programmers that are paid," he said when we checked up on Reflection updates. MB Foster has sold many copies of the product over the last 25 years. "Even for open source, there's some support and other positions also being compensated if these volunteers are working for a university or a large company like HP."

Foster says yes, there is an upgrade fee to bring Reflection up to date. "For customers that have been using the software for 10 years, they might want to remember that there is a cost to keeping the software in sync with the Microsoft changes," he said. "Continuous development is required and the programmers need to be paid."

One alternative to Reflection terminal emulation is Minisoft 92, from the company of the same name. CEO Doug Greenup said his product's got Windows 10 support, but even more interesting is the fact that it's got as many as 25 sites using the Charon emulator. Moving from HP's 3000 iron to Charon is a complimentary relicense at Minisoft, without a fee — so long as there's a current support contract.

Read "Keeping up lets you receive what you give" in full

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

January 26, 2016

Migrating apps creates years of 3000 work

Calendar pagesA double-handful of HP 3000s, 10 in all, remain on duty a few more years at a North American manufacturer with multiple sites. The systems are a mix of 9x9 and N-Class systems, waiting on a project to complete that will replace the 3000 apps with comparable software on Windows.

This app replacement is an example of one of the three flavors of migration discussed tomorrow (Jan. 27) in an MB Foster webinar. The first of a four-part series, Application Migrations / 3R's of Migration, starts at 2 PM Eastern US time.

At the North American manufacturer, according to systems engineer Dan Barnes, the Fortune 1000 company uses Lawinger Consulting for HP 3000 application management.

Our client has four remaining production locations using individual HP 3000s, plus one EDI server and one development server.  All are awaiting conversion to a Wintel-based application alternative, which is still two-to-five years down the road for them. We have an additional 4 DR servers as backup to these systems.

Read "Migrating apps creates years of 3000 work" in full

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

January 25, 2016

VMware solution assists Win10's 3000 debut

Windows 10 is making its way into HP 3000 shops. Earlier today a manager had loaded up Win10 and then discovered that Reflection, the terminal emulator built for HP 3000 access, wasn't working anymore.

Win10 upgrade"My Attachmate Reflections v14.1.3.247 does not work — it has an error when trying to start," said George Forsythe. He wanted to know about any available updates for the former WRQ product. It's not a former product, but Reflection for HP, as it's known today, is a Micro Focus product. Last year Micro Focus bought Attachmate, the company that purchased WRQ.

The short answer is version 14.1.543 (SP4), according to Craig Lalley. It's a matter of an update, but a mission-critical connection might demand a faster solution. One well-known program that aids Windows migration of 3000-attached desktops was mentioned by Neil Armstrong, developer of the Robelle data utility Suprtool. VMware can have your back if you're taken a PC onto Win10 and something critical like the 3000 connection stops running, he said.

This is why I've "virtualized" some key environments that are used for development. If something like this comes up, you're not stuck with a critical problem at a key moment.

Read "VMware solution assists Win10's 3000 debut" in full

Posted by Ron Seybold at 05:13 PM in Homesteading, User Reports | Permalink | Comments (1)

January 22, 2016

A 3000, awaiting replacement, still at work

If the above headline sounds like your homesteading situation, then you're an interim homesteader. Or a wannabe migrator, which can amount to the same thing if the pain of retaining a 3000 and MPE is low. In the hospital they ask you to rate your pain on a scale of 0-10. Nobody says 0, unless they're deep into morphine. There's usually some.

Pain ScaleAt Cerro Wire, the pain level must be not more than a 2, but the 3000 is being targeted for replacement. As part of our survey of the 3000 managers who speak up on the 3000-L, we got a report back from Herb Statham. He's led the 3000 computing at the manufacturer based in Alabama, with operations elsewhere in the US, too. Statham notes that the MPE server at Cerro continues to work. It's something like staying on your job even after you've been laid off, because they can't find a replacement yet.

Uncommon for an employee. Commonplace among interim homesteading systems. Statham, who was hiring for 3000 operations as recently as 2014 -- and had a contract 3000 expert at work until October — reports that Intel-based systems are preferred now at Cerro.

We are still running an A500 box at Cerro Wire. The game’s afoot to replace our current business applications with ones that are Intel- and Microsoft-based. I do not know when the final decision will be made, but the HP 3000 just keeps chirping along. I am trying to get “semi-retired” to only work two or three days a week, until the “new and better” system is in place.

Intel had prospects earlier at Cerro, in a different capacity. Statham was public about a 3000 emulator's chances there, even before the Stromasys Charon software had a big footprint. Cerro was going to be a classic 3000 manufacturer pushing their MPE apps into a long-running role. Leaving the HP hardware behind looked to be important, but other apps on other platforms were already working there.

Read "A 3000, awaiting replacement, still at work " in full

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

January 21, 2016

Taking a Charge at Transition's Costs

Changing your IT infrastructure might become more critical in 2016. Hardware is older, especially the hardware HP built and sold to run MPE/iX servers. One solution is to migrate to a new OS environment. Another refresh for IT might come from emulating the PA-RISC servers with Intel-based servers. But in either case, some software will have to come along, a move to help contain transition costs.

BatonLicense transfer practices come into focus during these projects. While moving from MPE/iX to another OS, most shops would like to keep what's been working, if the software's got prospects to grow along with IT's needs. In some cases that's possible, because the vendor has put in its work to adopt a new platform. A couple of middleware providers have done this. MB Foster and Minisoft both reached out to HP-UX users coming out of their MPE/IX environments. Minisoft's Doug Greenup reported this week that Summit Information Systems Spectrum users — whose vendor is now Fiserv, post-migration — headed to HP-UX when leaving the 3000 credit union application. Their target was Eloquence, the database designed to embrace IMAGE applications into an SQL world.

"We have quite a few Eloquence customers," he said, "more then 100. Many of the Fiserv Credit Union customers moved from MPE to HP-UX and use our ODBC driver for Eloquence." Minisoft's also got an ODBC for IMAGE product. That's an example of a cross-platform development strategy, something to keep costs under control. When your existing vendor does a version of your product for a migration target, that's fortunate. It's even more fortunate when you're not expected to re-license the product.

Last week the Minisoft ODBC for IMAGE product became the target of a competitive upgrade campaign. MB Foster says it will let a Minisoft ODBC customer switch to UDALink for MPE/iX for the price of a support contract. We took note of that campaign, a classic move from the days when new MPE/iX software was being sold in a market active enough to support multiple vendors for a single product like middleware. Going into competition, and retaining customers in the face of it, smacks of moxie in a market that's quiet and stable by now. It helps if your product has feature differences, so a 64-Bit ODBC driver, and the ability to use Suprtool's Self Describing (SD) Files, are getting touted in that offer.

Both vendors say they support Windows 10 with their middleware. No matter how much grief the new Microsoft environment is causing, it's still a certain part of IT futures. Windows 10 support is essential to keeping a 3000 current with the latest PC clients tapping IMAGE/SQL data.

Vendors in the 3000 market had to go where new system sales were happening, though. For MB Foster, its HP-UX version of UDALink is preserving investments at a site where the biggest single group of 3000s was migrated. At the same time, this site is using Minisoft's middleware on HP-UX, too. The situation at the college group looks like a lesson in preventing extra costs in a transition. Migration has plenty of prerequisite costs.

Read "Taking a Charge at Transition's Costs" in full

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

Search