January 15, 2015

New service level: personal private webinar

Software and service providers have long used webinars to deliver information and updates to groups. Now one vendor in the HP 3000 market is making the webinar highly focused. MB Foster is scheduling Personal Webinars.

CEO Birket Foster is available for private bookings with customers or prospects who need questions answered on a variety of topics. According to an email sent this week, the list from the company's Wednesday Webinars over the past few years includes

  • Application Migrations, Virtualization, Emulation, Re-host, Retire, Replace
  • Data Migration, Transformations, Decommissioning
  • Big Data
  • Bring Your Own Devise (BYOD)
  • Data Quality, Governance, MDM (Master Data Management)
  • Decision Support, Advanced Analytics, Dashboarding
  • User reporting, ad hoc query and analysis
  • Using Powerhouse in the 21st Century
  • Enterprise Windows Batch Job Scheduling
  • ITIL and APM
  • Document Management
  • Enterprise Data Storage

The vendor says to schedule this one-to-one briefing contact Chris Whitehead at 905-846-3941, or send a request to info@mbfoster.com, along with the desired topic and available dates and times.

Read "New service level: personal private webinar" in full

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

Pivital Solutions: Your complete
HP e3000 resource

January 14, 2015

(Still) ways to turn back time to save apps

Editor's Note: Nine years ago this week we ran these suggestions on how to get abandoned software to keep running on HP 3000s. It's still good advice while a manager and company is homesteading, or keeping a 3000 alive until a migration is complete.

Turn back timeSome HP 3000s are reduced to a single application these days. But the one program that will never move off the platform, however vital it might be, could see its support disappear on a particular date — with no help available from the creators of the software.

A few utilities can help rescue such applications. These products were popular during the Y2K era, when systems needed their dates moved back and forth to test Year 2000 compatibility. Now that some HP 3000 programs are being orphaned, clock rollback utilities are getting a new mission.

A customer of SpeedEdit, the HP 3000 programmer's tool, had lost the ability to run the program at the start of 2006. Both Allegro Consultants' Stan Sieler and former NewsWire Inside COBOL columnist Shawn Gordon offer products to roll back the 3000's clock. These companies don't sanction using their software to dodge legitimate licensing limits. But if a software vendor has left your building, so to speak, then HourGlass/3000 or TimeWarp/3000 (both reviewed) are worth a try to get things running again.

Read "(Still) ways to turn back time to save apps" in full

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

January 13, 2015

Shedding a Heavy Burden of History

Racking railOn Monday we reported the release of one of the first training videos hosted by computer pro in their 20s, demonstrating equipment from the 1970s. The HP 3000 is shedding the burden of such old iron, just as surely as the video's creator is shedding the equipment used to make the video.

Mark Ranft of Pro3K is making room in his operations in Minnesota by moving out equipment like the HP 7980 tape drive that was the centerpiece of the video. Ranft, who also manages at the company which took over the OpenSkies airline ticketing operations from HP 3000 servers, said his daughter Katie (above) was showing off MPE gear that will soon be out the door at Pro3K.

"We created this video as we soon we will no longer have the capability to create it," Ranft said. "We are downsizing. I will no longer have all this great old equipment."

Three of the tape drives, including a couple which have HP-IB interfaces. Drives so heavy that our reader Tim O'Neill said he had to remove his 7980s from HP racks using a lift table.

Only last month did I dismantle and ship out the last two remaining 9-track tape units from HP, which were the flat-laying vacuum chamber kind. I think they were Model 7980A (as though HP were going to make B and C models.) They were mounted on heavy duty racking rails in HP cabinets. They had not been used in a while, but were retained just in case someone wanted to read a 9-track.

Old iron is moving out, because the MPE/iX services of the future can be performed using drives so lightweight they'd fit in a lunch pail. Drives hosted on ProLiant servers of current era price lists.

Read "Shedding a Heavy Burden of History" in full

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

January 12, 2015

Video helps with 30-year-old tape operations

Reel Tape Drive video screen capA Facebook page has a new video that assists with decades-old technology. Reel to reel tapes get the how-to treatment on the page of the Pro3K consultancy, a support and operations firm that's run by Mark Ranft. The video shows a restore of a 31-year-old tape.

Using a detailed review of all the steps needed to load and mount a tape, Mark's daughter Katherine demonstrates how to handle the oldest storage technology in the MPE world. While reel to reel was popular, MPE V was in vogue. Some archival backups still have to be pulled from reel to reel. Meanwhile, there are other elderly HP 3000s that will only take tape backups. If a 3000 doesn't support SCSI, then it's HP-IB ready, so to speak. 

Katie RanftIf you've never enjoyed the inner workings of the vacuum loading systems on HP tape drives, you might be fascinated by what you see. There's also a guest appearance of the fabled 4GB disks for 3000s. Katie explains that the standard iPhone has four times as much storage as one of these disk drives.

She also notes that the 31-year-old tape "is four years older than me." Ranft said his daughter has been studying for potential consulting opportunies, and lives in the Chicago area.

Katie might qualify for the youngest person in 2015 who's instructed the world on the operations of an HP 3000. If you visit the Pro3K Facebook page, give it a Like. We like this trend: this is the first ops training for the 3000 ever posted on Facebook.

Posted by Ron Seybold at 06:45 PM in Homesteading | Permalink | Comments (1)

January 09, 2015

Virtualized storage earns a node on 3000s

Another way around the dilemma of aging 3000 storage invokes virtual data services. In specific, this solution uses the HP DL360 ProLiant server as a key element of connecting RAID storage with MPE/iX. Instead of older storage like the VA arrays, this uses current-era disks in a ProLiant system.

DL360 Gen 8Because there's an Intel server involved, this recalls the 3000 virtualization strategy coming from Stromasys. But the product and service offering from Beechglen — the HP3000/MPE/iX Fiber SAN — doesn't call for shutting off a 3000. It can, however, be an early step to enabling a migration target server to take on IMAGE data. It also works as an tactical tool for everyday homestead operations.

Beechglen's got both kinds of customers, according to Mike Hornsby. He summed up his offering, one that's available as an ongoing data service ($325 a month for 6 TB mirrored) or a $4,900 outright purchase with a year of support included. The company leveraged an MPE/iX source code license to build the SAN.

Having the source code to MPE/iX allowed us to provide an interface to our in-house developed FiberChannel targets that run on HP DL360s. This allows up to 6TB of RAID 1 storage in 1U of rack space, and provides advanced functionality, like replication and high availability.

He adds there are IO performance improvements in this solution, starting at twice as fast up to 100X, depending on what's being replaced. The company recommends an upgrade to an A-Class or N-Class to take advantage of native Fiber Channel. The SCSI-to-Fiber devices tend to develop amnesia, he explained, and the resultant reconfiguring for MPE is a point of downtime. "Those were never built for MPE anyway," he said of SCSI-to-Fiber devices.

The Fiber SAN runs CentOS Linux, and the MPE/iX LUNs are files.

Read "Virtualized storage earns a node on 3000s" in full

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

January 08, 2015

Keeping 3000 Storage On The Road

Since data storage is one of the biggest assets in any HP 3000 environment, it's fraught with risks and opportunities. Those are devices with moving parts that capture, exchange, and archive the precious data. A moving part wears out. A good plan to Sustain a 3000 site includes a strategy to protect that data.

Mr. ToadIf a system goes down these days, it's most like to do so because of a storage device failure. Mike Hornsby of Beechglen just reported that, "in our support efforts for both onsite services and being largest provider of hosted HP 3000s, the main ongoing issue is storage." Keeping it available and up to date is like keeping a car on the road.

In particular, the recovery time for a 3000 can be extended or limited by how fast the site manager can restore from a backup. The time to receive off-site backup tapes for restoring might be minimal. But a good plan will account for the expected amount of time. Every minute of it costs the company something.

Read "Keeping 3000 Storage On The Road" in full

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

January 07, 2015

End Days for Antique Disk Drives

HP 3000 servers which use drives made a decade ago are still running. It's not so far back, from a support perspective. Hewlett-Packard was supporting 9-GB and 18-GB units through 2008, and the 36-GB model A5595A through 2009. Those are the end of support dates from the manufacturer. Independent support companies back those models today.

AutoRAID 12HThey do it by replacing devices when they fail, not servicing dead drives. Any 3000s still operating off decade-old storage units are into magic time: those end days when it's a marvel just to see something that old still crucial to a system. Hard disks are the only moving parts of a 3000, after all. Even the redundant ones will fail, since all drives do.

The 3000 community has been facing its aging hardware a very long time. People were checking during 2006 on those end of support dates for the 3000's most common boot drives. A call for sensibility at the time went out from Donna Hofmeister.

It's more than time for many MPE shops to "smell the coffee," or perhaps more accurately, smell the looming disaster. If your disc drive is less than 36GB, odds are it's ready to be replaced. It's past it's expected life span, and you're living on borrowed time. If you got any plans to keep on running these systems, it's more than time to get onto new drives. With how prices have dropped, it's hard to not justify going to new drives. 

Hofmeister added "I wouldn't want to have to explain why, following a disc failure, you can't get your MPE system running again." Replacing these wee discs with newer technology is possible, of course. Little SCSI drives that can be seen by MPE are harder to find by now, though. HP's last significant extension of MPE was to expand the server's vision of storage units, so the 3000 could see devices up to 500GB. But half a terabyte is a small drive today.

Finding an AutoRAID 12H replacement gets tougher still. Not tough to locate. Tough to justify.

Read "End Days for Antique Disk Drives" in full

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

January 06, 2015

Essential Steps for Volume Reloads

When a 3000 drive goes dead, especially after a power outage, it often has to be reloaded. For example, when an LDEV2 has to be replaced. For a cheat sheet on reloading a volume, we turned to our Homesteading Editor Gilles Schipper.

By Gilles Schipper

Assuming your backup includes the ;directory option, as well as the SLT:

1. Boot from alternate path and choose INSTALL (assuming alternate path is your tape drive) 
2. After INSTALL completes, boot from primary path and perform START NORECOVERY. 
3. Use VOLUTIL to add ldev 2 to MPEXL_SYSTEM_VOLUME_SET. 
4. Restore directory from backup (:restore *t;;directory) 
5. openq lp
6. Perform a full restore with the following commands
:file t;dev=7(?)
:restore *t;/;keep;show=offline;olddate;create;partdb;progress=5 7.

Perform START NORECOVERY

Read "Essential Steps for Volume Reloads" in full

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

January 05, 2015

Securing cloud promises hardware freedom

Threat-manager-sensor-imageRackspace's cloud hosting security can include Alert Logic Threat services for enhanced security. MPE managers are likely to insist on the advanced service.

If a 3000 manager or owner had one wish for the new year, it might be to gain hardware assurance. No matter how much expertise or development budget is available in 2015, not much will turn back the clock on the servers -- the newest of which were built not very long after Y2K. The option to escape these aging servers lies in Intel hardware. Some sites will look at putting that hardware out in the cloud.

Say the word cloud to an HP 3000 veteran and they'll ask if you mean time-sharing. At its heart, the strategy of the 1970s that bought MPE into many businesses for the first time feels like cloud computing. The server's outside of the company, users access their programs through a network, and everyday management of peripherals and backups is an outsourced task.

But the cloud of 2015 adds a world of public access, and operates in an era when break-ins happen to banks without defeating a time lock or setting off a security alarm. Time-sharing brought the HP 3000 to Austin companies through the efforts of Bill McAfee. Terry Floyd of the MANMAN support company The Support Group described the earliest days of MPE in Austin.

The first HP 3000 I ever saw was in 1976 at Futura Press on South Congress Avenue in Austin.  Bill McAfee owned Futura and was a mentor to many of us in Texas. Futura was an HP reseller, and aside from a wonderful printing company, they wrote their own software and some of the first MPE utilities. Interesting people like Morgan Jones hung out around Futura Press in the late 1970's and I can never thank Bill and Anne McAfee enough for the great times.

Series 42Jones went on to found Tymlabs, the creators of one of the bulwark MPE backup products. The HP Chronicle, the first newspaper devoted to the 3000, processed its typesetting using that Futura server. For all practical purposes this was cloud computing, delivered off mid-range HP 3000s such as the Series 42 (above), even deep into 1984. But 30 years later, this category of resource has become even more private and customized. It also relies on co-located hardware. That's where Rackspace comes in. It's the target provider for the new cloud-based installations of Charon. The Rackspace mantra is "One size doesn't fit all." That harkens to the days of time-sharing.

Read "Securing cloud promises hardware freedom" in full

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

January 02, 2015

What to Expect in Performance This Year

Legacy systems like the HP 3000 remain entrenched around the world. The reason? Their durability and their standing in the company's business legacy. What's a business legacy, you ask? It's the history of what kinds of servers and programs get used to process business. All MPE/iX applications are business legacies by now. They're more than a decade old. They run, and their performance is adequate. There seems like there's little to be done about making them faster.

Orders-of-magnitudeBut employing an emulator to replace the Hewlett-Packard models of 3000s can change that. The promise is more performance from more modern Intel-based hardware. There are limits, however. Here in 2015, the performance gain is limited by the size of 3000 that's running this week, the first of the new year. This week we read about "orders of magnitude" performance gains, but that's usually a number only applicable to a first order -- times 10. And even that might be a few years away for 3000 managers.

Given enough time, everyone who uses a 3000 emulator will outstrip the raw processing power of the HP-brand iron. Those HP boxes will never get faster, unless you can top them up on memory. In contrast, the Stromasys emulator will get more efficient; 2015 sees a newer, faster version now available. And Intel-based iron will grow stronger, too, at its top-end. The phrase "top-end" matters a great deal. If you're using top-end HP hardware, it might be too soon to look for a significant performance boost from virtualization.

Top-end means the fastest N-Class servers. Those will need to be replaced by top-end Intel hardware: servers with many available CPU cores, and many CPUs. Faster might not be a goal, however, for 2015. As-fast might be enough, to enable a manager can leave behind the aging HP iron.

It's easy to misunderstand. At a website called The VAR Guy, written by former InfoWorld editor in chief Michael Vizard, Stromasys' potential got noticed. "After all," he said, "the latest generation of Intel processors provide orders of magnitude more performance than VAX, Alpha, HP 3000 or Sparc systems that can be more than a decade old." Um, sometimes. But when you're working at the top-end of the old hardware, orders of magnitude is a far-off, wishful goal. If your HP 3000 has a tiny 3000 Performance Unit rating of 2.7, for example, then the first order of magnitude would be 27. The next order is 270, and so on. Several orders may be possible — at the lower levels of 3000 performance.

Simply beating the existing performance is still a valid desire, though. Matching what you're using — so you can leave old hardware behind — is a bona fide need in the 3000 market.

Read "What to Expect in Performance This Year" in full

Posted by Ron Seybold at 04:37 PM in Homesteading | Permalink | Comments (0)

December 31, 2014

Top Stories Lead MPE Into New Year

The remains of 2014 are down to just a few hours by now, a year that saw the virtualization of the system take new wings while migrations proceeded at a slower pace. We reported stories about surprising homesteading sites and new players in the community which counts MPE as a significant piece of history — and for some, a platform into 2015 and beyond.

But no story of the past year would be complete without a passage devoted to the passing of the enterprise torch into a smaller Hewlett-Packard. The company that created MPE and the 3000 passed the total management mantle to CEO Meg Whitman in the summer, making her chair of the full entity. A few months later it divided itself along enterprise IT and consumer lines. The year 2014 will be the last when HP stands for a complete representation of the creations of Bill Hewlett and Dave Packard. By this time next year, a spinoff will be vying for attention of the computing marketplace.

1. HP decides to break up the brand

HP Enterprise Corp. StrategyAnd in one stroke of genius, it became 1984 again at Hewlett-Packard. October brought on a new chorus for an old strategy: sell computers to companies, and leave the personal stuff to others. But one of the others selling personal computers and printers usually connected to PCs is a new generation of the company. The CEO of Hewlett-Packard is calling the split-off company HP Inc. But for purposes of mission and growth, you could call it HP Ink. Genius can be simply a powerful force for good or for ill. Definition 3 of the word in Apple's built-in dictionary on my desktop calls genius "a person regarded as exerting a powerful influence over another for good or evil: He sees Adams as the man's evil genius." It's from Latin meaning an attendant spirit present from one's birth, innate ability, or inclination.

The company to be called Hewlett-Packard will concentrate on a business lineup that harkens back to 1984 a year when the LaserJet joined the product line. CEO Meg Whitman said Hewlett-Packard, devoted to enterprise business, and HP Inc. can focus and be nimble. From a 3000 customer's perspective, that focus would have been useful 13 years ago, when the lust for growth demanded that HP buy Compaq and its PC business for $25 billion on the promise of becoming No. 1.

2. 3000's time extended in schools, manufacturing

SB County schoolsThe San Bernadino County school district in California was working on moving its HP 3000s to deep archival mode, but the computers still have years of production work ahead. The latest deadline was to have all the COBOL HP 3000 applications rewritten by December 2015. That has now been extended to 2017

And with the departure date of those two HP 3000s now more than two years away, the school district steps into another decade beyond HP's original plans for the server line. It is the second decade of beyond-end-of-life service for their 3000.

In another market segment, 3M continues to use its HP 3000s in production. What began as the Minnesota Minining & Manufacturing Company is still using HP 3000s. And according to a departing MPE expert Mike Caplin, the multiple N-Class systems will be in service there "for at least several more years."

In both cases, the 3000 is outlasting the deep expertise of managers who kept it vital for their organizations. It's taking a :BYE before a :SHUTDOWN, this longer lifespan of MPE than experts.

3. Virtual Legacy Carries MPE from Past to the Future

Stromasys took its virtualization of enterprise server message to VMworld's annual conference, where the event was pointing at cloud-based Platform As A Service (PaaS) for the years to come. The CHARON virtualization engine that turns an Intel server into a 3000 operates on the bare metal of an Intel i5 processor or faster, working inside a Linux cradle. Plenty of customers who use CHARON host the software in a virtualized Linux environment -- one where VMware provides the hosting for Linux, which then carries CHARON and its power to transform Intel chips, bus and storage into PA-RISC boxes. VMware is commonplace among HP 3000 sites, so management is no extra work.

Read "Top Stories Lead MPE Into New Year" in full

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

December 30, 2014

2014's Top Stories: Recapping A Year

Here in the days that lead to the end of 2014, it's a journalism tradition to review events whose effect will last beyond their original dateline. We're not about to break tradition, a feeling that 3000 managers and owners will understand. We also invite you to nominate an important event below, in our comments.

1. Unicom sees PowerHouse as iconic real estate

The new owners of the PowerHouse software products began talking about their end of 2013 purchase in a way that the 4GL's users haven't heard since the golden era of the 3000. While Unicom Systems was still fleshing out its plans and strategy, the company is enhancing the legacy technology using monetary momentum that was first launched from legendary real estate -- an iconic Hollywood film star home and a Frank Lloyd Wright mansion.

2. The Unix-Integrity server business keeps falling

Sliding-cliffHP's proprietary replacement for the 3000 continued its slide. As early as February, HP's CEO said "We continue to see revenue declines in business-critical systems," Whitman said. Only the Enterprise Group servers based on industry standards -- HP calls them ISS, running Windows or Linux -- have been able to stay out of the Unix vortex. "We do think revenue growth is possible through the remainder of the year on the enterprise [systems] group," Whitman said. "We saw good traction in ISS. We still have a BCS drag on the portfolio, and that's going to continue for the foreseeable future." By year's end the management team had given up on any growth via Unix — because the product line has dropped 20 percent of sales per quarter.

3. Applications swallowed by big vendors tread water

Even the migrated apps such as Ecometry were not immune to a classic business development: smaller bases of application customers seeing road maps get cloudy once they slid into a big product portfolio. JDA and Red Prairie merged, and even a year later the former, which owns the Ecometry suite, had no road map on how the app would grow and go forward. JDA is large enough to join forces with Red Prairie in early 2013. But not large enough to deliver a futures map for the Ecometry customer. These customers have been loath to extend their Ecometry/Escalate installations until they get a read on the tomorrow they can expect from JDA. "I think it's possible there's nobody left in JDA who can even spell MPE," said MB Foster CEO Birket Foster, "let alone know what it means to Ecometry sites."

Read "2014's Top Stories: Recapping A Year" in full

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

December 29, 2014

Moving Pictures of HP's Contribution Origins

10,000th

HP's Origins video, filmed nearly a decade ago, includes this picture of employees celebrating the shipment of the 10,000th HP 3000, sometime in the 1980s.

You can't find it on the Hewlett-Packard website, but a 2005 movie called "Origins" is still online at a YouTube address. The 25-minute film chronicles what made HP such a groundbreaker in the computing industry, and it includes interviews with the company's founders. Bill and Dave didn't appear much on camera, being businessmen of a different era and engineering managers and inventors at heart.

The link here takes the viewer directly to the Contribution segment of the story. While it is history by now -- the company transformed itself to a consumer and commodity goods provider thanks to the me-too of CEOs Carly Fiorina and Mark Hurd -- the film represents ideals that anybody in the business can set for their own career or decisions. Joel Birnbaum, whose HP Labs leadership helped deliver RISC computing for the business marketplace for the first time in 3000, sings his praise for the love of making a product that could make a difference.

Opening Up VideotapeBut that contribution era passed away once uniformity became the essential feature of enterprise computing. By the middle '90s, HP was busy selling the 3000 as another tool that could handle open systems (read: Unix) computing. In truth, Unix was no more open than any other environment, including Windows. But Unix had some similarities between versions that could be leveraged by large enough software developers. In the videotape at left, HP offered an interview from an unnamed SAP development executive. He said his application suite had been through a test port to MPE/iX, and he believed the software had 99.5 percent code compatibility from Unix to MPE.

That half percent might have presented a technical challenge, of course. It would be thousands of lines of code, considering SAP's footprint. The MPE version of the application never made it into the vendor's price list, however. One specific client may have used SAP on a 3000 via that test port, but it was never offered as a manufacturing solution by its creators. HP's enterprise execs very much wanted an SAP offering for the 3000. That creation would have been as me-too as any product could get. "You could run that on a 3000 instead of a 9000" would've been the HP account rep's message in 1992.

SAP's exec on the video admired the 3000 customer community for its understanding of enterprise applications. But a level of misunderstanding lay at the heart of the SAP organization, whose speaker in the video said the database for HP-UX and MPE was the same. IMAGE, of course, was nothing like Oracle or even Allbase, and the latter had only a thimble's worth of adoption in the 3000 community. IMAGE gave that community its understanding of what enterprise applications should do. 

Read "Moving Pictures of HP's Contribution Origins" in full

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

December 23, 2014

Gifts for MPE Owners This Season

Turned OffThe managers and owners of MPE systems have seen much taken from them over the past decade and more. Vendor development, support that's unquestioned by top management, even the crumbs of MPE security patches and bug fixes. A lot has gone dark in this winter of the 3000's seasons. But here on the eve of Christmas Eve, there's still some treasures under the tree of 3000 life as we know it.

Stromasys-logo-smallFuture hardware. Stromasys has made a business mission out of preserving applications written for MPE. The company has done this with Charon HPA, software whose foundation was laid in 2009 and is receiving an updated, speedier release this year. Companies that are relying on MPE apps for many years to come -- so many they need brand-new hardware to host the 3000's OS — can count on the software that makes Intel behave just like PA-RISC. You won't be able to run a company on a laptop, but MPE boots fast enough on what we once called a Portable PC to show off this virtualizer in the boardroom.

Screensie MBFA logoA future for applications. Migration can be messy, feel risky and command a big chunk of budget and human resource, but several companies are still devoting their business missions to transitions. MB Foster comes to mind first here, and there are others with tools, like ScreenJet. More than 12 years after HP announced its pullout, and with a declining number of migrations in the offing, companies still deliver expertise on the biggest IT project a company will ever undertake. Something like doing an aircraft engine replacement while at 30,000 feet.

Series 928Software and help for it. On the cusp of 2015, you can still purchase software that manages enterprise-caliber jobstreams, the tools to manage the 3000's filesystem or its database, and more. The ones that aren't sold still have support lines. Companies like the Support Group host hot spares and help manufacturers keep stately legends like MANMAN online. Even a 20-year-old 9x8 deserves some respect while it continues to manage the finances and production of a competitive manufacturing entity.

SwitchboardSystem-wide support. As the numbers of MPE-savvy pros decline, outsourcing for expertise becomes essential for any customer homesteading long-term, or even through a migration project. Pivital Solutions, and companies like Allegro and Beechglen, ensure older HP iron and the static, classic MPE/iX 7.5 behave as planned. There's even a resource in Applied Technologies that can integrate open source software, ready for MPE and part of any larger project.

That's a lot to unwrap and admire for a 40-year-old computer, all still open at a time of year when presents are present. We're delighted to keep telling stories like million-dollar virtualization configurations, shiny benefits of data cleansing, or the new players taking over icons like PowerHouse. We're taking the remainder of this holiday week off, celebrating a birthday, the end of Hannukah and Christmas with the family. We'll be back with reports on Monday, December 29.

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

December 22, 2014

A Quiet December Week's MPE Ripples

The week of Christmas is a quiet one for business and enterprise IT. Sales calls and installations are at a minimum, companies work with skeleton crews, and announcements of news are rare. But nine years ago the week of Christmas was hot with a 3000 development, one that has ripples even today.

HolidayrippleIn the Christmas week of 2005 — back when HP still worked full shifts over the holidays — the 3000 division released news that HP's support lifespan for MPE would be extended. What had been called a firm and solid date of HP's departure got moved another 24 months into the future. The news was the first unmistakable evidence that the migration forecast from HP was more wishful than accurate.

As it said it would offer basic reactive support services for 3000 systems through at least December of 2008, the vendor confirmed that it would license MPE source code to several third parties. The former put a chill on migration business in the market, sending vendors -- services and software suppliers alike -- looking for non-3000 markets to service. The latter gave the support community a shot of fresh competition over the afterlife beyond the Hewlett-Packard exit.

In one of the more mixed messages to the community, HP said customers should work with the vendor to arrange support until migrations could be finished. The 3000 division also said its license for MPE source was going to "help partners meet the basic support needs of the remaining e3000 customers and partners." It would take another three years, beyond the closing of the MPE lab, for that source code to emerge.

Read "A Quiet December Week's MPE Ripples" in full

Posted by Ron Seybold at 07:45 PM in History, Homesteading, News Outta HP | Permalink | Comments (0)

December 19, 2014

Making a New Case Against Old Hardware

Try to Order PartsIt won't make the resellers of HP's 3000 hardware happy, but Stromasys has started to make a strong argument against preserving the life of Hewlett-Packard's MPE hardware. In a link inside a video that was attached to a 2015 happy holidays message, we've spotted a 96-second summary that shakes the bones of the assurance there's plenty of parts in the world to support aging 3000 systems.

Maintaining the original MPE-based systems from Hewlett-Packard is risky and difficult, the commercial that's hosted on the Vimeo website says. The software is worth preserving, it continues, and it notes more than 5,000 companies have used the Stromasys Charon technology to enable hardware emulation. The majority of these Stromasys clients have emulated Digital's server hardware to preserve VMS applications.

Lower than full migrationOf course, there's a mention of emulation's savings versus a full migation. For the customers who are leaving the HP 3000 because the hardware's old, this point might have some traction. The level of support from the original hardware vendor, as well as the end of HP's 3000 manufacturing, drove a significant number of migrations in the past. The Stromasys argument states that with new hardware, an application suite can be preserved. Customers who remain on their homesteaded systems often say they'd be happier if their futures didn't include the expenses and risks of migrating.

There's a short reference to cloud-based Charon installations amid the message, too. In that level of solution, investment in the powerful Intel-based hardware is exchanged for a typical cloud-rental fee. In some cases, the investment in the hardware required to emulate HP-branded 3000 servers can be substantial.

Most interesting, Stromasys now has offered MPE support among the services it sells. It's right there alongside VMS and Solaris software support. The company hasn't issued a press release and there aren't details immediately available on the levels of operating system support, or the staff which will be supplying it.

Read "Making a New Case Against Old Hardware" in full

Posted by Ron Seybold at 07:14 AM in Homesteading | Permalink | Comments (0)

December 17, 2014

MB Foster extends Ability Commerce's retail

Screen Shot 2014-12-17 at 6.19.47 PMAbility Commerce, a direct commerce software and provider of JDA Direct Commerce Professional Services, has announced their partnership with MB Foster. The two companies offer services to enterprises that use the JDA products including Escalate Retail, the latest generation of the Ecometry ecommerce software suite.

Ability, in calling MB Foster "a software programming and consulting firm specializing in highly scalable data access and delivery solutions for the  JDA Direct Commerce (Ecometry) software platform," plans to use its new partner to transform and migrate the surround code popular in Escalate installations.

“MB Foster’s addition to our strong partnership solutions dedicated to the JDA Direct Commerce software platform will allow us to provide an even higher level of service to that user base, "said Shawn Ellen, Director of Sales and Marketing for Ability Commerce. "MB Foster is committed to the Ecometry user base and will be joining us as a sponsor at our Ability Commerce User Summit this coming March 11-13 in Delray Beach, Florida."

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

December 16, 2014

How OpenCOBOL Helped Porting COBOL II

Editor's note: A little while ago the 3000 newsgroup was discussing the merits of OpenCOBOL compared to the heartland compiler of MPE, COBOL II. Roy Brown offered his story of how he made the open source COBOL step in to do the work that COBOL did during a 3000 migration. A port, if you will.

By Roy Brown

I used OpenCOBOL to port two HP 3000 COBOL programs — only two, but one of them was the big and critical engine at the heart of a system otherwise written completely in PowerHouse.

Key_to_replacementI first used the portability checker on COBOL II to make a few amendments to bring the program in line with the standards — and was able to roll that version back into the production HP3000 code at the time.

The thing that remained non-standard, but which OpenCOBOL supported, IIRC, was entry points. I could have got round the limitation of not having them, but I was pleased not to have to.

The one remaining issue after that was not having IMAGE on the new platform, but having to use Oracle instead. So I rewrote the IMAGE calls as Oracle PRO*COBOL calls. And I was quite surprised that this made the program shorter, or would have if I hadn't left the IMAGE calls in, but commented out, so I could refer back to them if there were issues.

So, armed with a readable program, I slotted it through the PRO*COBOL precompiler, which spits out unreadable COBOL, put that through the OpenCOBOL compiler, which spits out C (or did then, at any rate — does it still?) and then compiled that with the GNU C compiler.

Read "How OpenCOBOL Helped Porting COBOL II" in full

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

December 15, 2014

2015 migrations creep on, in virtual mode

HocusPocusIn the concept of virtualization, a server is replaced by another which pretends to be just like the original. There's no new HP 3000 in emulation, for example. Just the idea of one. The essence of the HP 3000, its PA-RISC architecture, is replaced using the Charon product: software that mimics the HP hardware. Virtualization engines use software to eliminate hardware.

Some MPE migrations which have been underway for years look like they may be using up virtual man-months, so the IT group won't have to adopt a new application. The plan and lengthy project time eliminates the need to go live with changes.

In a virtual migration, the organization knows its intention. Get onto another environment with mission-critical apps. But the work never gets completed, something like a "forthcoming" novel that's expected but unfinished. Virtualized migrating can very well be the reason any 3000 project still has a 2017 target date.

"These days with the tools that are available," said Alan Yeo of ScreenJet, "no migration should take more than 12 months." He added that he believes that engaging a migration services company of any reasonable size would get most of of an organization's code running in test-mode in about six weeks.

Read "2015 migrations creep on, in virtual mode" in full

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

December 12, 2014

Essential Skills: Using Password Vaults

Editor's note: HP 3000 managers do many jobs, work that often extends outside the MPE realm. In Essential Skills, we cover the non-3000 skillset for these multi-talented MPE experts.

By Steve Hardwick, CISSP

Passwords are always a challenge for security professionals. Why is creating a secure password so difficult? More importantly, how can a user tell if their password has been stolen? Typically, when all the damage has been done and the password has been used by someone else. At this point in time it is too late. One way to resolve this is to have a password vault such as KeepPass or 1Password.

VaultA vault is a good investment of your time. A security breach that might result from having no vault might be difficult to even detect. It might be that the time the breach is discovered may not be the first time the hacked credentials were used. This might be how many times a stolen credit card is used before the owner gets the bill. Second, the hacker could have hacked the password and is just keeping it for later use or sale. One of the preventative measures for this is to require users to periodically change passwords. 

This changing strategy can stem the use of stolen passwords and also prevent the future use of any that have not yet been exploited. From a user's perspective, though, generating multiple passwords every 60-90 days just compounds the passwords nightmare.

As a security professional I have seen several solutions that users concoct to try and get around this issue. One common one is to write them all down and hide the resulting list. It turns out there are not that many good hiding places. Under keyboards, behind pictures, inside speakers, taped to the underside of a drawer or chair, back of a bookcase do not qualify as good locations. Also, many users forget to update the sheet with new passwords. Another approach is to create a text file, e.g. shopping_list.txt, and put everything in there. A quick search of the most frequently used files normally finds those. Plus if the hard drive crashes, and the file is not backed up, new ones have to be set up all over again. 

A variation of the last theme is to use a password vault. This is a method where the password information is stored on a file, but the file is encrypted. In this case only one password is needed, to decrypt the vault, and access is granted to all of the other passwords. The most ubiquitous form of encryption is AES - Advance Encryption Standard. AES256 encryption is adequate for most users.

However, one word of caution. If the password used to encrypt the vault is easy to guess, then the contents are at risk. 

Read "Essential Skills: Using Password Vaults " in full

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

December 11, 2014

Big, unreported computing in MPE's realm

When members gather from the 3000 community, they don't often surprise each other these days with news. The charm and challenge of the computer's status is its steady, static nature. We've written before about how no news is the usual news for a 40-year-old system.

Pegged gaugesBut at a recent outing with 3000 friends I heard two pieces of information that qualify as news. The source of this story would rather not have his name used, but he told me, "This year we actually sold new software to 3000 sites." Any sort of sale would be notable. This one was in excess of $10,000. "They just told us they needed it," my source reported, "and we didn't need to know anything else." A support contract came along with the sale, of course.

The other news item seemed to prove we don't know everything about the potential of MPE and the attraction of the 3000 system. A company was reaching out for an estimate on making a transition to the Charon emulator. They decided not to go forward when they figured it would require $1 million in Intel-based hardware to match the performance of their HP 3000.

"How's that even possible?" I asked. This is Intel-caliber gear being speficied, and even a pricey 3000 configuration shouldn't cost more than a quarter-million dollars to replace. It didn't add up.

"Well, you know they need multiple cores to replace a 3000 CPU," my source explained. Sure, we know that. "And they had a 16-way HP 3000 they were trying to move out."

Somewhere out there in the world there's an HP 3000, installed by Hewlett-Packard, that supports 16 CPUs. Still running an application suite. The value is attractive enough that it's performing at a level twice as powerful as anything HP would admit to, even privately. 

A 4-way N-Class was as big as HP would ever quote. Four 500-MHz or 750-MHz PA-8700 CPUs, with 2.25 MB on-chip cache per CPU, topped the official lineup.

Unix got higher horsepower out of the same HP servers. An 8-way version of the same N-Class box was supported on HP-UX; HP would admit such a thing was possible in the labs, and not supported in the field. But a 16-way? HP won't admit it exists today, and the customer wouldn't want to talk about it either. Sometimes things go unreported because they're too big to admit. It made me wonder how much business HP might've sustained if they'd allowed MPE to run as fast and as far as HP-UX ran, when both of those environments were hosted on the same iron.

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

December 10, 2014

Getting Macro Help With COBOL II

GnuCOBOL An experienced 3000 developer and manager asked his cohorts about the COBOL II macro preprocessor. There's an alternative to this very-MPE feature: "COPY...REPLACING and REPLACE statements. Which would you choose and why?"

Scott Gates: COPY...REPLACING because I understand it better.  But the Macro preprocessor has its supporters. Personally, I prefer the older "cut and paste" method using a decent programmer's editor to replace the text I need. Makes things more readable.

Donna Hofmeister: I'm not sure I'm qualified to comment on this any longer, but it seems to me that macros were very efficient (and as I recall) very flexible (depending on how they were written, of course). It also seems to me that the "power of macros" made porting challenging. So if your hidden agenda involves porting, then I think you'd want to do the copy thing.

There was even porting advice from a developer who no longer works with a 3000, post-migration.

Read "Getting Macro Help With COBOL II" in full

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

December 08, 2014

IMAGE data schemas get visualized

Is there any program that will show the network of a TurboIMAGE database? I want to output the relationships among sets and items.

CFAWireframeIn 2011, Connie Sellitto researched the above question, while aiding new programmers who were charged with moving a pet organization's operations to a non-MPE system. Understanding the design of the database was important to this team. Sellitto mentioned a popular tool for PCs, but one not as essential as an IT pro's explanations.

You might try Microsoft's Visio, and you may need to have an ODBC connection to your IMAGE database as well. This produces a graphical view with search paths shown, and so on. However, there is still nothing like a detailed verbal description provided by someone who actually knows the interaction between datasets.

To sum up, we can refer to ScreenJet founder's Alan Yeo's testing of that Visio-IMAGE interplay

Taking a reasonably well-formed database into Visio and reverse engineering, you do get the tables and items. It will show you what the indexes in the tables are, but as far as I can see it doesn't show that a detail is linked to a particular master. Automasters are missing anyway, as they are really only for IMAGE.

My conclusion: if you have done all the work to load the databases in the SQL/DBE and done all the data type mappings, then importing in Visio might be a reasonable start to documenting the databases, as all you would have to do is add the linkages between the sets.

If you don't have everything in the SQL/DBE, then I would say we are back where we started.

Read "IMAGE data schemas get visualized" in full

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

December 05, 2014

A Forced Migration, One That's Unfortunate

ImagesThis month in the US includes more than the usual ration of Christmas carols and holiday office parties. This is the first month when we US citizens are renewing our healthcare, all of us at once. It's Open Enrollment! According to my insurance agent, everybody's got to be insured by the end of the month. I'm one of the people who's having an experience like 3000 users got in 2001. Blue Cross is migrating me away from a product that it no longer wants to sell.

The parallels, so far, are pretty close. There was nothing that stopped working with my health plan. Like HP, Blue Cross simply stopped selling it because it wasn't making the vendor enough profit. The plan was not removed because of the Affordable Care Act (commonly known as Obamacare). But then, the HP 3000 was not removed because of the HP merger with Compaq. These were simply business decisions, by HP and by Blue Cross of Texas.

Business decisions are taken as a result of events that create situations. Insurers must protect profits, in the same way that HP had to protect its ability to grow after it absorbed $25 billion of Compaq. Customers don't get consulted about discontinuing products.

Much like the experience of the 3000 community with the 2001 migration march, my journey to a new plan will trigger more expense, and let Blue Cross earn more by doing less. I'll see about a 20 percent increase in recurring costs -- which might look cheap compared to how much the 3000 migration has cost the companies being forced to move.

There's a difference that's important, though. The active event that's changed the sale of insurance in America comes with federal rules. It now costs at least $395 a year to homestead, as it were, with no insurance at all. That's a fine that can rise as high as 2 percent of your gross income. A similar bill for a company making $5 million yearly in profit would be $100,000. That would be money spent just to stay on a system which the vendor stopped making or supporting.

Thankfully, there's no such fine for homesteading. There's a bill if a site simply stops support of all kind, however. Every computer system breaks down sooner or later, because nothing is built to never break. A company's insurance on its computer operations is support. The 3000 community got an advantage over those of us who've seen their products discontinued. System support got less costly.

Read "A Forced Migration, One That's Unfortunate" in full

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

December 04, 2014

TBT: When Poetry Sang the 3000's Story

Our extended report on the occasion of Fred White's death let a memory of a poem float to the foreground of collective consciousness. The HP 3000's fans and fanatics have dreamed up verse to go along with the acres of prose written about the computer. One of the youngest fans of all time owns the copyright to three such poems. There has been other verse in song, as well.

SashaComputer poetry -- that is, poems written about a computer -- goes back to the tradition of IBM's company songbooks. Orly Larson of Hewlett-Packard was the chief bandleader for such music about White's creation, IMAGE. A rousing medley of Larson's compositions became part of HP conferences during the mid-1990s. But on another end of the age range, Alexander "Sasha" Volokh (at left, at an HP conference of the day) penned a poem celebrating the Boston Tea Party protest led by White in 1990.

Sasha's The Unbundling of IMAGE (full text at the Adager website) was an account of the SIGIMAGE meeting during that show, "In the style of The Man From Snowy River by A.B 'Banjo' Paterson"

Now Fred White had written IMAGE and was sad, as you can guess.
He said the word "unbundling" was a lie.
IMAGE isn't like a product, but is part of FOS
And that's why you get it when HPs you buy.
But IMAGE, it has always been mistreated by HP
And I wouldn't like to think the end is near.
And I'm working with Alfredo, but in this, I speak for me,
'Cause if not for me, you wouldn't all be here.

There was more, plenty more to protest about at that meeting of 24 years ago. Some of the poem included a reference to an open letter, this one written by a 3000 legend also deceased. That letter of Wirt Atmar's was another means to dispute the vendor's plans for the 3000's future. MPE systems have retained their value to homesteading users, in large measure because the unbundled database scheme was shouted down.

Read "TBT: When Poetry Sang the 3000's Story" in full

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

December 03, 2014

Cyber-shop for networked storage this week

AmazonAs Cyber-Week -- the extension of Cyber Monday shopping -- continues to unfold this week, the holiday sale might provide new resources for your old 3000. Network Attached Storage (NAS) is a powerful enterprise resource, full of value now that disk prices have plummeted. Everything is even lower this week. Alan Yeo of ScreenJet has shared his secrets for making NAS an HP 3000 tool.

"Like most HP 3000 shops we were looking for a cheap way to [store many gigabytes of data] — and there was no way we could afford a DLT," he said. Digital Linear Tape boasts massive capacities, but most storage these days is going straight to another disk.

LinkstationYeo said that fundamentally, the method to include NAS as an option involves creating STORE to Disk files, "and then you FTP those STORE files up to your NAS device. A simple half-terabyte (500 GB) RAID-1 NAS device is the equivalent of 40 12-GB DDS tape drives." 

It's a little unsettling to hear how many HP 3000 backups still go onto DDS tapes. Even the DLT tapes are a pain to handle, Yeo added.

Read "Cyber-shop for networked storage this week" in full

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

December 02, 2014

Data leads way to migrations, via support

Migration patternThe heart of a 3000 homestead operation is its collection of IMAGE/SQL databases. Almost 20 years ago, IBM was mounting an effort to turn 3000 customers into AS/400 sites. I commented on the effort for Computerworld, "They'll have to do something about converting IMAGE/SQL data, if they expect to have any success." IBM had little luck in that effort, and not a great deal more nine years later, after HP announced an exit date for its 3000 operations.

From a reader and system manager on the US East Coast, we've heard more about data leading the way to the future. At this long-time 3000 site, the systems are getting a new support provider to keep them online and reliable. Not many sites are changing this sort of arrangement these days. It's been almost four years since HP closed its 3000 and MPE support operations in 2010.

A new company will be supporting that A-Class server on the East Coast before long. The new support is going to open the door to a revamped future, however. 

Our purchasers are still in the process of signing up our new vendor for HP 3000 support. What is sad is that part of the deal includes migration of some TurboIMAGE databases to MS Access or something like that, which will lead to the eventual demise of the HP3000.

There is still the chance the new support might extend the 3000's utility, though. Self-maintainers who don't use support run risks that the 3000 doesn't really have to bear. A stable server is just one short-term reward for signing up with a support provider specializing in 3000s, like Pivital Solutions or The Support Group.

Read "Data leads way to migrations, via support" in full

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

December 01, 2014

HP Q4, FY static; 3000 replacement sales fall

Enterprise Group totals Q4 2014Despite all of the challenges Hewlett-Packard faced over the past fiscal year, the company has reported sales and earnings that didn't fall much from FY 2013 levels. Falling sales of HP 3000 replacement systems remain on the balance sheet, however. Nothing has changed but the depth of the plunge.

Both the 2014 fiscal year and the Q4 numbers (click on graphics for details) reflected an ability to keep some declines off the HP financial report. The latest quarter improved on Q2 and Q3 results overall. HP reported a profit of $2.62 per share for 2014. That's nearly $5 billion in earnings company-wide.

If the company sticks to its plan, its total of $115 billion in 2014 sales, only down 1 percent from last year, covers the penultimate period HP reports as a full company. By the end of FY 2015, the corporation will separate its businesses and spin off HP, Inc. for consumer and PC products. Hewlett-Packard will remain to sell servers and enterprise computing products and services. Analysts expect the companies to be of equal size.

Revenue shares Enterprise Group Q4 2014The total of HP's Business Critical Systems revenues took another hit in the fourth quarter, dropping almost 30 percent from Q4 of 2013. Double-digit percentage drops in BCS sales are commonplace by now. The unit produces the HP-UX systems HP once designated as replacements for the HP 3000. Intel-based systems, contained in the Industry Standard Servers operations, also saw their sales decline slightly. Networking revenues were slightly higher for the quarter.

The company's CEO was thrilled about the overall picture for the full company, calling it a sustained turnaround.

"I'm excited to say that HP's turnaround continues on track," said Meg Whitman. "In FY14, we stabilized our revenue trajectory, strengthened our operations, showed strong financial discipline, and once again made innovation the cornerstone of our company. Our product roadmaps are the best they've been in years and our partners and customers believe in us. There's still a lot left to do, but our efforts to date, combined with the separation we announced in October, sets the stage for accelerated progress in FY15 and beyond." 

Read "HP Q4, FY static; 3000 replacement sales fall" in full

Posted by Ron Seybold at 07:58 PM in Migration, News Outta HP | Permalink | Comments (1)

November 26, 2014

Something to give thanks for, and envy, too

On the eve of a holiday invented to promote thanks as well as outsized eating, Thanksgiving reminds us of what a 3000 user can thank the gods for -- and something to envy, too.

OpenVMS-HPProlific commenter Tim O'Neill asked, "Can you write about the current futures of other no-longer-supported systems such as HP 1000, Alpha, and old HP 9000s such as Series 300/400/700?" We can write that the HP 1000, a product line which HP turned off just after Y2K, still has third parties who will maintain and support RTE operating system applications. The HP 1000 got a proper emulator from Strobe Data, engineered in time to capture the business of companies who couldn't part with RTE apps.

A similar story is true of the AlphaServer line from HP. Killed off in the last decade, Alpha is a third-party supported product. No other Alpha computers were built after HP shunted its users to the Integrity line, a migration path of dubious future by now. Alpha has a good emulator in the AXP version of Charon from Stromasys, the company providing a future for long-serving MPE/iX apps, too. The presence of Charon prompts thanks from companies who can't support the concept of decade-old HP hardware running MPE/iX.

But while the Alpha and the 3000 will live on in the virtualization of Stromasys, they can be envious of the deal another retiring environment received this year. OpenVMS will live on in an exclusive license to VMS Software Inc. (VSI). The company got the arrangement to carry OpenVMS forward with new versions using the HP source code for the operating system.

The details released haven't yielded much more than a third-party road map for the OS, up to now. But that's a future with some tantalizing what-if's, both for the OS and for the 3000 user who wanted more MPE/iX future back in 2002. OpenMPE campaigned for use of HP's source code for MPE and got an arrangement that was announced six years ago this week. That source was limited to a technical support resource, however.

If, as happened with OpenVMS, that source had been promised to a single third party, six years before HP would drop support, there could be more to be thankful for this week. Extended third party applications. Support for newer technologies. A replacement vendor, blessed by HP, to mention in boardroom meetings about the 3000's future.

Perhaps OpenVMS customers should be thankful for something else, too: The lessons HP faced about ending the life of a business operating environment, an OS that brought HP to the computing game. Third parties that love and care for a legacy computer were on hand for the 3000. They fell short of convincing Hewlett-Packard to turn over a marketplace. Maybe HP learned that leaving customers with no better choice than replacing a system with Windows wasn't great business.

We'll give thanks for a few days off to celebrate this holiday with family in the Great Lakes -- regardless of frigid weather. We'll be back on Monday.

Posted by Ron Seybold at 10:07 AM in News Outta HP | Permalink | Comments (0)

November 25, 2014

Open source SED manages 3000 streams

Open source resources make it possible to use SED, a stream editor built in the open source community. Since 2001 SED has worked on the HP 3000, thanks to Lars Appel, a former HP support engineer who ported Samba to the platform in the 1990s.

SED's main MPE page is on a page of Appel's. SED is an at your own risk download, but support is available through the 3000 community.

Dan Barnes, working on a problem he had to solve in his 3000 environment, asked:

The issue is incoming data from another platform that is being fed into MM 3000. This data occasionally has some unprintable characters, which of  course wrecks havoc on the MM application when it is encountered. To address this, the user, using a cygwin (Unix-like) environment on their Windows PC, developed a SED script. When they test the script in the cgywin environment it works just fine. But when done on the target HP 3000 it gets an undesirable result.

Barnes added that "The user thought that because MPE/iX is Posix-compliant, that this should work." He explained his user created the expression

sed -e 's/[\x7F-\xFE]/*/g' < COMSHD > COMSHD1

But Appel noted that hex 7F thru hex FE portion of the expression isn't supported on the MPE/iX version of SED. It's a limitation of MPE/iX, but there's a workaround.

Not sure if the regular expression usage here matches Posix or GNU specs, but my guess is the "\xNN" format, that seems to indicate a char by hex code, doesn't work.

How about something like using the command sed -e 's/[^ -~]/*/g' instead, i.e. map the characters outside the range space through tilde?

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

November 24, 2014

Building a Portfolio Away From Retirement

ClutteredclosetUsing analogies of moving out of a house and filling out scorecards, an hour of last week unreeled off a Webinar that showed how portfolios offer a plan for migrating and sustaining applications. Birket Foster and his crew at MB Foster showed how continuous and thorough software management helps available budget meet the most crucial needs.

A classic four-quadrant chart outlined the scoring of applications. One axis showed a business fit, the other a technical fit. Like all of the four-box charts, nobody wanted software in the bottom left, low in both aspects. But it's a business decision that drives most of the changes in IT these days. Scorecard the business fit of applications in a portfolio first, Foster said. If it scores well in that fit, go on to the technical fit.

The portfolio is the tool of governance, he added. Governing is a classic process to ensure the most needy get resources as required. Application Portfolio Management has been a favorite topic at MB Foster. It's only possible if a company knows its applications very well — and very well means with documentation that can be shared over time. The assets in a portfolio can be judged to be worthy of migration based on their risk-benefit-value. What helps a company most, and what could you least afford to let fall into that dreaded lower-left box?

QuadrantOnly about 5 percent of the community's applications can fall off that chart completely, ready for retirement. The largest group are suited for a same-capability migration, when they creep down. That 70 percent of the apps can get a lift-and-shift of their functionality, usually through replacement. It takes hundreds of hours per application.

What makes it less painful and swifter is cleaning in advance. As Foster said, "It's like moving out of a house. If you go through your closets regularly, you'll be moving less that you don't need." In this analogy, the closets are your data, which "has to be made available to the new app. It's not automatic."

Read "Building a Portfolio Away From Retirement" in full

Posted by Ron Seybold at 09:40 AM in Migration | Permalink | Comments (0)

November 20, 2014

TBT: When Joy of Tech Was Necessary

SuperGroup Fred White


The cover above of the SuperGroup Association magazine from January, 1985 came to mind here on ThrowBack Thursday. Fred White passed away this week, and it's been a delightful trek down the lane of memories to recall his gusto about the art of technology.

The cover above shows some of that gusto which is not easy to describe. SuperGroup understood the MPE and IMAGE technology of the '80s as well or better than any magazine of the day. But that 3000 publication edited by D. David Brown had a sense of humor and whimsy about it no other publication has been able to eclipse. (Even on my best day as HP Chronicle editor I was only cooking up editorial cartoons about PA-RISC that somebody else would illustrate, and there have been those Ken-Do strips from the NewsWire. But nothing as savvy as what was staged above.)

The players in the little romp were, from left, White, Adager's Alfredo Rego, and Robelle's Bob Green. The photo was a teaser into a great technical paper about a perceived need to acknowledge that databases needed "uncomfortable Procrustean designs... [using] methodologies associated wth normalizing and relating."

Procrustean creditsLike the paper that Eugene Volokh wrote in the following year, the technical report put relational databases in their place -- capable of permitting multiple views of data, but with a steep performance price to pay compared to IMAGE/3000. The article was on the vanguard of unmasking the shortcomings of relational databases of that era, as I read it. Also clever and playful, two words not often associated with technical writing. The paper was authored by more than the three in the picture; Allegro's Stan Sieler and Steve Cooper got credits, as did Leslie Keffer de Rego for editing.

Read "TBT: When Joy of Tech Was Necessary" in full

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

November 19, 2014

Fred White, 1924-2014

FredWhiteCourtesy of his long-time collaborator and partner Alfredo Rego, this picture of Fred White was taken in 2004, when Fred was 80 and several years into retirement. The legendary co-creator of IMAGE and the SPL expert in Adager's Labs, White was a Marine Corps veteran. Rego said while offering this portrait, "I took this photo with my Olympus E-1 on October 26, 2004 (just a bit over 10 years ago!) in Cedar City, Utah, where he and Judy lived for a while. Fred invited Judy and me to lunch, and I snapped this image across the table. I loved everything there: The warm light, the delicious food, the stimulating conversation, the young college students rushing about..."

The creator of the heartbeat of the HP 3000, Fred White, passed away on November 18, 2014 at the age of 90. White died peacefully in the presence of his wife Judy and family members, of natural causes. He had relocated to Arizona after retiring from Adager in the year after Y2K. His work in building the essential database for MPE, alongside Jon Bale, was the keystone of the 3000 experience. Rego took note of a key identifier inside the IMAGE internals, one that signified a database was sound and accurate. The flag was FW, or as Rego said in a short tribute to his partner, "%043127, the octal representation of “FW” — the flag for a normal IMAGE/3000 database (and TurboIMAGE, and IMAGE/SQL)."

White's work for the 3000 community came in two stages. The first was his innovations while working for HP, building a network database which won awards until HP stopped selling IMAGE and included it with the HP 3000. (Bundled software would not be considered for prizes like the Datamation award bestowed on IMAGE in 1976.) IMAGE, integrated at a foolproof level with the MPE intrinsics and filesystem, delivered a ready field for a small army of developers to plant applications and tools. Without White's work, the 3000 would have been just a footnote in HP's attempts to enter the computer business.

The second stage of White's gifts to the community began when HP had infuriated him for the last time. Never a fan of large organizations, he left Hewlett-Packard when it became clear the vendor had no interest in enhancing IMAGE. But before he departed HP, White met with Rego when the latter was visiting HP in an effort to learn more about IMAGE from the vendor, in preparation for a forthcoming database manager he'd create. As the legend is told, White decided he'd try to help Rego just to ensure that the creation to be called Adager could emerge a little easier.

"He hoped we would answer his questions," White said in a post-retirement interview. His partner Jon Bale "said that kind of help would be contrary to HP company policy. I said to him, 'Jon, this guy’s going to get this done whether we help him or not. All we’re doing is helping a fellow human. Whatever it takes, Alfredo’s going to do it anyway.' "

"At that point, Jon said it was up to me, but he couldn’t do it because it wasn’t HP company policy. He wished Alfredo the best of luck and left. So I answered his questions, and even told him things he couldn’t possibly have thought of, such as privileged mode intrinsic calling and negative DBOPEN modes, things peculiar to the software rather than the database. We chatted for an hour and a half or so."

The exchange in 1977 pointed toward the door to the Adager segment of White's career. The years between 1980 and 2001 allowed Fred to make up for his reticence inside corporations by becoming the conscience of accuracy and fairness. Innovations for IMAGE finally arrived in the middle 1990s. But White's most saucy moment of advocacy came in Boston when HP was trying to make IMAGE a separate product once again.

Read "Fred White, 1924-2014" in full

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

November 18, 2014

Replacing rises as migrator's primary choice

Key_to_replacementIt's the end of 2014, just about. Plenty of IT shops have closed down changes for the calendar year. Many 2015 development budgets have been wrapped up, too. Among those HP 3000 operations which are still considering a strategy for transition, there's only one assured choice for most of who's left. They'll need to replace their application. Not many can rehost it.

We've heard this advice from both migration services partners as well as the providers of tools for making a migration. An HP 3000 is pretty likely to be running an application with extensive customization by this year. We've just now edged into the 14th year since HP announced a wrap-up of its interest in all things MPE/iX. Year One began in mid-November of 2011. After completing 13 years on watch during the Transition Era, there's a lot of migration best practices to report. More success has been posted, at a better price and on schedule, when a replacement app can be integrated along with a new server and computing environment.

Of course, massive applications have been moved. One of the largest was in the IT operations of the State of Washington Community College Computing Consortium. It was a project so large it was begun twice, over enough elapsed time that the organization changed its name. The second attempt better understood the nuances of VPlus user interface behaviors. There were 40 staffers and at least four vendor services groups working on the task.

One of the issues that's emerged for rehosting organizations is a reduction in MPE expertise. Companies can still engage some of the world's best developers, project managers, and rewriting wizards for MPE/iX. It's harder to assign enough expert human resources who know your company's business processes. That's why a top-down study of what your apps are doing is the sort of job that's been going out-of-house. By this year, it would be better to engage an outside company to replace what's been reliable. This hired expertise ensures a company doesn't lose any computing capability while it makes a transition.

You'll need the use of tools to manage data in a replacement, though. Everything else is likely to change, even in a replacement, except for the data. "Replacement requires reorganizing data," Birket Foster of MB Foster told us this summer. "You could start cleaning your data now." Foster is presenting a Webinar on the subject of the Three Rs -- Rehosting, Replacing, or Retiring -- tomorrow (Wednesday) at 2PM Eastern Time. 

Read "Replacing rises as migrator's primary choice" in full

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

November 17, 2014

HP's 3000 power supply persists in failure

Amid a migration project, Michael Anderson was facing a failure. Not of his project, but a failure of his HP 3000 to start up on a bad morning. HP's original hardware is in line for replacement at customers using the 3000 for a server. Some of these computers are more than 15 years old. But the HP grade of components and engineering is still exemplary.

"I was working with a HP 3000 Series 969, and one morning it was down," he reported. "All power was on, but the system was not running; I got no response from the console. So I power-cycled it, and the display panel (above the key switch) reported the following."

Proceeding to turn DC on

On the console it displayed garbage when the power was turned on, but the message on the display remained. I wasn’t sure what to replace. I was thinking the power supply — but all of the power was on. As it turned out, even in the middle of a power supply failure the 3000 was working to get out a message. The back side, the core I/O, FW SCSI, and so on, all appeared to have power. That is why I found it hard to believe that the power supply was the problem.

Read "HP's 3000 power supply persists in failure" in full

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

November 14, 2014

Our World's Greatest Cartoon, Ever

101 MigrationsBecause it's so crucial, and because Alan Yeo was brilliant in commissioning it. Mark your calendars. (Click it for detail)

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

November 13, 2014

Thursday Throwback: IMAGE vs. Relational

As a precocious 18-year-old, Eugene Volokh wrote deep technical papers for HP 3000 users who were two or three times his age. While we pointed to the distinctions between IMAGE master and automatic datasets recently, Eugene's dad Vladimir reminded us about a Eugene paper. It was published in the fall of 1986, a time when debate was raging over the genuine value of relational databases.

While the relational database is as certain in our current firmament as the position of any planet, the concept was pushing aside proven technology 28 years ago. IMAGE, created by Fred White and Jon Bale at HP, was not relational. Or was it? Eugene offered the paper below to explore what all the relative fuss was about. Vladimir pointed us to the page on the fine Adager website where the paper lives in its original formatting.

COBO HallThe relationships between master and automatic and detail datasets pointed the way to how IMAGE would remain viable even during the onslaught of relational databases. Soon enough, even Structured Query Language would enter the toolbox of IMAGE. But even in the year this paper emerged, while the 3000 still didn't have a PA-RISC model or MPE/XL to drive it, there was a correlation between relational DBs and IMAGE. Relational databases rely on indexes, "which is what most relational systems use in the same way that IMAGE uses automatic masters," Eugene wrote in his paper presented at COBO Hall in Detroit (above). QUERY/3000 was a relational query language, he added, albeit one less easy to use.

Vladimir admits that very few IT professionals are building IMAGE/SQL databases anymore. "But they do look at them, and they should know what they're looking at," he explained.

Relational Databases Vs. IMAGE:
What The Fuss Is All About

By Eugene Volokh, VESOFT

What are "relational databases" anyway? Are they more powerful than IMAGE? Less powerful? Faster? Slower? Slogans abound, but facts are hard to come by. It seems like HP will finally have its own relational system out for Spectrum (or whatever they call it these days). I hope that this paper will clear up some of the confusion that surrounds relational databases, and will point out the substantive advantages and disadvantages that relational databases have over network systems like IMAGE.

What is a relational database? Let's think for a while about a database design problem.

We want to build a parts requisition system. We have many possible suppliers, and many different parts. Each supplier can sell us several kinds of parts, and each part can be bought from one of several suppliers.

Easy, right? We just have a supplier master, a parts master, and a supplier/parts cross-reference detail:

Relational-IMAGE Fig 1Every supplier has a record in the SUPPLIERS master, every part has a record in the PARTS master, and each (supplier, part-supplied) pair has a record in the SUPPLIER-XREF dataset.

Now, why did we set things up this way? We could have, for instance, made the SUPPLIER-XREF dataset a master, with a key of SUPPLIERS#+PART#.  Or,  we  could have made all three datasets stand-alone details, with no masters at all. The point is that the proof of a database is in the using. The design we showed -- two masters and a detail -- allows us to very efficiently do the following things:

  • Look up supplier information by the unique supplier #.
  • Look up parts information by the unique part #.
  • For each part, look up all its suppliers (by using the cross-reference detail dataset).
  • For each supplier, look up all the parts it sells (by using the cross-reference detail dataset).

This is what IMAGE is good at -- allowing quick retrieval from a master using the master's unique key and allowing quick retrieval from a detail chain using one of the detail's search items. 

Read "Thursday Throwback: IMAGE vs. Relational" in full

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

November 12, 2014

Public server with a mission: CHARON cloud

About a month ago, Stromasys announced that the CHARON HP 3000 emulator was going to be finding a home in the cloud. The company says it's talking to prospective partners to put such a 3000 capability onto a standard cloud provider, such as Amazon Web Services. That would establish a working environment where the 3000 has already performed a mission. More than a decade ago, Hewlett-Packard believed that a 3000 for public use would help the 3000 community.

The server was dubbed Invent3K, because its mission was to further the 3000's lifespan through the invention of software. HP stocked it with subsystems, offered accounts for free, and let development commence. Some useful products came out of Invent3K. The first that comes to mind is a version of perl ready for MPE/iX. That's a version that continues to work.

Now CHARON might do similar work to help extend the MPE/iX lifespan. Plenty of people want to experience the emulator's powers. Tapping a free server, including free accounts where homesteaders' applications and test databases could reside, would offer the world a useful test bed for transition onto Intel hardware and away from HP-branded boxes.

Last fall the MPE expertise inside Stromasys suggested if there would be interest, from a volunteer, in putting a public-access CHARON-fueled machine on the Internet." It's the sort of mission OpenMPE might have done in its heyday. A lot has changed since HP's labs shut down and OpenMPE was left without much mission. A public access server for the world's only HP 3000 emulator would get ample traffic. It could also be a vital proof of concept for using a 3000 based in the cloud.

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

November 11, 2014

Veterans get volunteered for transition's day

1stCavHere on Veteran's Day — I'm a vet of the '70's-era military — I'm remembering there are IT pros with another kind of veteran status. They are people who count more than a couple of decades of experience with the HP 3000, managing their servers since before the time that Windows was the default computing strategy. They've been through a different kind of conflict.

I've learned that the most embattled managers employ a surprising tool. It's a sense of humor, reflected in the tone of their descriptions of mothballing the likes of 25-year-old independent apps during migrations. They have to laugh and get to do so, because their attempts to advance their positions might seem like folly at first look, or even in a second attempt.

Really, an assignment like putting Transact code into an HP-UX environment? Or take the case of working around a financial app software from Bi-Tech -- an indie vendor that "really stopped developing it for the 3000 years ago," according to City of Sparks, Nevada Operations & Systems Administrator Steve Davidek. There's been some really old stuff doing everyday duty in HP 3000 shops. The age of the applications was often in line with the tenure of the project's management.

These pros typify the definition of veterans, a term we'll use liberally in the US today to celebrate their sacrifices and courage. Facing battle and bullets is not on par with understanding aged code and logic. But two groups of people do have something similar at heart. Both kinds of veterans have been tested and know how to improve the odds of success in a conflict. Youthful passion is important to bring fresh energy to any engagement, military or technological. What earns the peace is experience, however grey-haired it looks next to Windows warriors.

With each mission accomplished -- from what looks like the Y2K effort of 14 years ago to embracing a roll-your-own Unix that replaced MPE's integrated toolset -- these veterans moved forward in their careers. "Our knowledge base is renewed with this work," one said after migrating apps that served 34 Washington state colleges. "We're on the latest products."

Recruiting IT talent into small towns — and the 3000 runs in many small cities where manufacturing labor is less costly — meant hiring for Windows experience. Adopting Windows into an organization means leaving proprietary environments even more popular than MPE/iX. Like HP-UX.

Read "Veterans get volunteered for transition's day" in full

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

November 10, 2014

Sharing the Source of SLEEPER for MPE

Sleepy penguin,jpgSLEEPER is one of the best-known Contributed Software Library (CSL) programs in the history of the HP user group Interex. For years after the user group shut down, the CSL tapes -- created once a year and refreshed with new programs after every annual user meeting -- were the most significant Interex asset left to the community. But making the CSL a public asset, after the Interex shutdown, encountered a snag. How could those useful programs like SLEEPER get shared, if they didn't have clearance from the contributing companies?

SLEEPER and BOUNCER were the programs most often cited in the snags, since they were shared by way of the 3000 shop at Boeing. It was heard a lot, this caution, while people were searching for CSL collections after the Interex meltdown. "Oh, we can't go and release that swap tape," people like the Interex curators would say. "There's BOUNCER on there, and we'd have to get permission from Boeing." Well, that's not exactly true.

Maybe one email would've gotten the process of permission started. It's different times by now. The SPL source for SLEEP, a progeny of SLEEPER, was shared up on the 3000-L mailing list last week. (That's a link to the 3000-L archive message, containing the code in the message body.) Ray Legault offered the code when John Korb, a 3000 consultant, was asking around for it.

Korb thinks so highly of SLEEPER that wants to port the program to PHP, for use on a Linux system. "My goal is to create a PHP version of SLEEPER," he said, "something that can run on Linux desktops and servers and Windows 8.1 desktops -- so I can avoid cron on the Linux box, and avoid the Windows task scheduler."

Read "Sharing the Source of SLEEPER for MPE" in full

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

November 07, 2014

Manual and Automatic Masters, Detailed

A few days ago we included a Hidden Value question about how manual and automatic masters work in TurboIMAGE. Our ally and friend Vladimir Volokh called to note that in part of the question, the system manager had found "one detail data set that has thousands of entries which do not appear to be connected to any master.

It wasn't exactly a question, but in a reply on the 3000-L mailing list and newsgroup, Roy Brown gave a fine tutorial on how these features do their jobs for MPE and the 3000 -- as well as how a detail dataset might have zero key fields.

Manual masters can contain data which you define, like Detail sets can, along with a single Key field. Automatic masters contain only the Key field.

In both cases, there can be only one record for a given key value in a Master dataset.

A Detail dataset contains data fields plus zero, one, or many key fields. There can be as many records as you like for a given key value, and these form a chain accessible from the Master record key value. This chain may be sorted, or it may just be in chronological order of adding the records.

Zero key fields in a Detail dataset would be unusual, but is permissible.

Read "Manual and Automatic Masters, Detailed" in full

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

November 06, 2014

Throwback: Today's Empire of Invent3K

Five years ago today we watched for notice about a fresh 3000 resource on the Web. Invent3K, a public access development server created by HP in 2001, was searching out a new home in November 2009. The vendor shut off Invent3K in November 2008, along with the Jazz website that hosted shareware utilities created by HP and the user community.

Invent3K was an OpenMPE adoption project five years ago. The community probably didn't need a public access development web server by the end of 2009. But replacing HP's withdrawn assets seemed important. Invent3K harkened back to a more hopeful time. 3000 developers were first offered access to MPE accounts on that HP server only about six months before the vendor announced it would end its 3000 programs.

Invent3K was unique in the 3000's history. The server was the first and only place that hosted free, development-use-only subsystem software from HP. Working from an Invent3K account, a developers employed COBOL II, TurboStore, and other HP-branded products while building apps or utilities.

InventFor a time, OpenMPE wanted to sell $99 yearly development accounts on its replacement Invent3K. The community was not accustomed to paying for public access, so sales were slow. OpenMPE was trying to generate revenues for operating things like a Jazz replacement host where contributed tools could be accessed. By that time, much of Jazz had been re-hosted at servers owned by Client Systems and Speedware. Things were not hosted quite the same as on Jazz, though. HP insisted that those two vendors make users click through an End User License Agreement before using the contributed tools re-hosted from Jazz.

Last month, two of the replacement servers for delivering Jazz and Invent3K had online glitches. Speedware's server went offline for a weekend, so its hpmigrations.com website that hosts Jazz delivered only an error. The HP 3000 where Invent3K was headed in 2009 had a small hiccup, too: the 3000-based Empire 3.9 game server lost use of its domain name for awhile in October. Tracy Johnson is the caretaker for the Empire server and its parent -- Invent3K, whose domain name is invent3k.openmpe.com.

But Invent3K is operating today, at least for anyone who had an account established before OpenMPE curtailed its operations. Access is through any terminal emulator with Telnet or VT/Mgr protocol. Once you've configured your terminal emulator, connect to the address invent3k.empire.openmpe.com.

Read "Throwback: Today's Empire of Invent3K" in full

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

November 05, 2014

Migration plans: Rehost, Replace, or Retire

CircleRMigration begins with an inventory. Application by application, an IT manager does triage on every program on their 3000. The goal is to come up with a disposition for each app. Some ccan be rehosted. Apps built with PowerHouse might be moved to other servers, for example. For other apps, they can be replaced. Ecometry sites could adopt the CommercialWare application, in some cases. Or in other instances, an in-house program suite can be replaced by a Commercial Off The Shelf app. Migration services company MB Foster likes to call those replacements COTS. The company has a Wednesday webinar scheduled on Nov. 19 to explore planning to replace COTS and more.

Foster calls the strategy the Three R's of Migration: Rehost, Replace, Retire. At 2 PM Eastern Time in a couple of weeks (register here), Birket Foster will lead a slide talk with time for questions about what to do if you're migrating away from any one of the above types of applications. The word Retire is already on the minds of MPE-savvy managers, since most of them are older than 50. It turns out that applications can find the end of a career even before their caretakers do.

It's not always this way. At the San Bernadino County schools, the apps to run the California district will have a retirement date from the 3000 that falls after the district's 3000 expert. Sometimes, though, a migration can become easier when older programs that have fallen into disuse are simply erased. There's no need to migrate such an app.

However, there's only one sure way to discover these retirees: inventory and analysis. MB Foster's summary for the Nov. 19 webinar breaks that triage process into inventory of app environments; rating the functionality vs. business suitability of each app; then organizing and prioritizing with a study of interfaces and grouping used that applies to each app. COTS carries a different set of requirements to study during migration planning, the company says, than in-house apps.

Read "Migration plans: Rehost, Replace, or Retire" in full

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

November 04, 2014

Tips for Listing SCHEMAs, and FTP Listings

From my existing TurboIMAGE database, I want to generate a listing of data sets, data item names, and their relationships (master, detail). One detail data set has thousands of entries which do not appear to be connected to any master. 

Oh, and I cannot remember the difference between manual and automatic masters.

Francois Desrochers first replies, "Use Query's FORM command."

RUN QUERY.PUB.SYS
B=dbname
PASSWORD = >> password
MODE = >> 5
FORM

Manual masters: programs have to explicitly add entries before you can add related entries in detail sets. Programs have to explicitly delete entries when there are no related detail entries left. In other words, you have to do master dataset maintenance.

Automatic masters: entries are automatically created when a related detail set entry is created. Entries in the master are automatically removed when the last related detail entry is deleted. IMAGE takes care of the maintenance.

Consultant Ron Horner adds, "If you have a tool like Adager or DBGeneral, it can create a file of the database schema. The other way is by using QUERY to get a listing."

Read "Tips for Listing SCHEMAs, and FTP Listings" in full

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

November 03, 2014

10 years ago, was the 3000 halfway gone?

I revisited a set of user conference slides from 2004 recently, and I found a scheduling milestone. A presentation at that final Interex show in Chicago included a schedule warning. In that year, it was about halfway through the period HP gave the community to get away from their HP 3000s. The deadline for the end of HP support was December 31, 2006, as of the week the presentation rolled out in Chicago.

Go 95%"Put your plan into the budget during this summer of 2004," one slide suggested. Using that timeline, an IT manager could commence migrating by the summer of '05 and complete a migration by the end of 2006. To be sure, 18 months is a swift migration schedule, but it's possible -- if a company can budget for some outside expertise for project management and coding. The tests will usually be handled in-house. That's up to one third of a migration project's timeline, according to migration services experts like MB Foster.

By the next fall, HP was pulling the carpet out from under such companies. That deadline for HP support got extended by 24 months. With that change, that halfway-gone point was still at the moment of HP's rescheduling. But now there were more than 36 months left. People had not migrated in enough numbers. A greater factor: HP made a business decision to keep support business alive and earning revenues for another two years. It was high-profit revenue. High enough that the deadline got moved again, out by another 24 months.

Since those days, we've seen many customers use the same sort of rolling-forward deadline for their migrations. They plan for the end of 2013, for example, then push out to the end of 2015. Just like HP, customers in places like California school districts and manufacturers in the Southwest are taking more time because they like the return on investment. They can afford to reset the halfway mark.

But what if 2004 was the start of 95 percent of migrations, and the decade since then represents halfway-gone? What's left by now in the user community still includes companies of serious size.

Read "10 years ago, was the 3000 halfway gone?" in full

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

October 30, 2014

ITMGR3K + YOLO = CHARON COSTINFO?

The formula above translates into an appeal for budget reporting. IT managers of HP 3000s can complete this formula. YOLO is the ubiquitous You Only Live Once, sometimes broadcast in a tattoo. When added to 3000 IT managers' experiences, the formula may yield some of the most crucial costs of the CHARON virtualization engine for emulation.

Elder-tattoosThe daring of YOLO is required because there's plenty at stake, even at MPE's advanced age. 3000 owners are often working with reduced budgets. Cost-effective computing is one good reason why the MPE/iX apps survive in a company. But some managers could acknowlege you'll only live once through homesteading your MPE/iX applications. It's not the hardware you're saving with Charon. The operating environment, your TurboIMAGE/SQL data, and the apps with their software helpers -- those are the orphans being rescued from any failing HP-branded computer.

So it figures that managers with nothing to lose can help other homesteaders get better information on the costs to virtualize. Costs can be fatal to a project. Many managers know they have something significant at stake: their relations with the software vendors who supply the help for HP 3000 operations. Surround code, it's been called. Some vendors are everywhere, like Robelle, Adager, Vesoft, PowerHouse, and so on. Add in the suppliers of key data transfer tools such as MB Foster. Everybody's got virtualization licensing practices in mind, if not executed yet.

The above list of vendors can include a show-stopper, by some customer reports. PowerHouse products, even something as fundamental as Quiz reports, have still been quoted at rates that can shelve a virtualization project. We recently heard about one at a 3000 manufacturer. The COSTINFO specifics were not forwarded. But in a budget-conscious community like the 3000's, even such prices in the low five figures can cause a HALT.

Then there's the manager whose operational best practices include lowering a profile with vendors. "I'm not old enough to retire," we often hear -- meaning that high visibility on vendors' radars could invite higher costs. Not good for any career built on economic prowess. No, not every vendor operates by watching for such an extra-fee opportunity. But enough do; some can be hungry for back-support revenues when they bring a customer back onto vendor support. Then there are the applications. Update fees for virtualizing an Ecometry installation, or something from the Infor stable of manufacturing apps, are not common-enough knowledge. Not for HP users.

Read "ITMGR3K + YOLO = CHARON COSTINFO?" in full

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

October 29, 2014

Security experts try to rein in POODLE

PoodlelocksSometimes names can be disarming ways of identifying high-risk exploits. That's the case with POODLE, a new SSL-based security threat that comes after the IT community's efforts to contain Heartbleed, and then the Shellshock vulnerability of the bash shell program. HP 3000s are capable of deploying SSL security protocols in Web services. Few do, in the field; most companies assign this kind of service to a Linux server, or sometimes to Windows.

The acronym stands for Padding Oracle on Downgraded Legacy Encryption. This oracle has nothing to do with the database giant. A Wikipedia article reports that such an attack "is performed on the padding of a cryptographic message. The plain text message often has to be padded (expanded) to be compatible with the underlying cryptographic primitive. Leakage of information about the padding may occur mainly during decryption of the ciphertext."

The attack can also be performed on HP's Next Generation Firewall (NGFW), a security appliance that is in place protecting thousands of networks around the world. Other firewalls are at risk. Just this week HP released a security patch to help the NGFW appliances withstand the attack. External firewalls are a typical element in modern web service architectures.

A POODLE attack takes a bite out of SSL protections by fooling a server into falling back to an older SSLv3 protocol. HP reported that its Local Security Manager (LSM) software on the NGFW is at risk. But a software update is available at the HP TippingPoint website, the home of the TippingPoint software that HP acquired when it bought 3Com in 2010. TippingPoint rolled out the first HP NGFW firewalls last year.

Read "Security experts try to rein in POODLE" in full

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

October 28, 2014

Strategies for Redirecting App Spoolfiles

An HP 3000 manager wrote that a 24x7 application at his shop is stable and never goes offline unless it's required. But the everyday management had to include aborting the app once a week.

We take that application offline to close out the spoolfile that the application generates. Is there a way to keep the application running, and just redirect the output to a new spoolfile? We're using an N-Class server.

Robert Schlosser of Global Business Systems replied: Short of closing and reopening the application after n number of pages, you could have the application read (without wait and checking status codes) a message file. It could then close and open the output file on demand, and possibly even close down the application gracefully (no abort).

Our Homesteading Editor Gilles Schipper replied: I think the only way you could do that would be to actually modify the application program to periodically (say, for example, every 10 pages or every 100 pages) close then re-open the print file.

Olav Kappert of IOMIT International added:

If the program can be slightly modified, then I would suggest creating a message file as a conduit to the application. The program would do a read of the message file with the nowait option every once and awhile.  If the application encounters a keyword indicating a new spoolfile, then the program would close the spoolfile and reopen it.

An alternate method would involve the application being modified to close and open the file at a particular day and time during the week.

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

October 27, 2014

Early 3000 Flights: A New Embattled History

Bill FosterThe world is still full of computer aces who flew in the earliest skies of minicomputers. The HP 3000 has history to share about the dogfights to bring interactive computing to businesses and organizations. The new voice of a pilot of that early age, Bill Foster, tells a fresh story about historic 3000 events. (A tip of the hat here to former OpenMPE director and Allegro support engineer Donna Hofmeister, who spotted Foster's blog.)

Bill Foster was in charge of engineering for the first HP 3000 that became a production-grade computer, the Series II. Foster went on to co-found Stratus Computer. In a blog he's called TeamFoster he tells his compelling story I Remember HP, complete with characters memorable and regrettable, about the earliest times in the Data Systems Division labs in California. Up to now, most of the stories about the 3000's birth have had a more abbreviated telling, or they're summarized in less vivid accounts.

Foster's written 15,000 words on his blog to tell his Hewlett-Packard story, which begins in 1971. In that year the HP 3000 is still more than a year away from its ill-fated debut, so he can chronicle the inner workings of a lab where "The engineers were mostly out of control, particularly the programmers."

HP Journal 1973Foster's story about the earliest days of the 3000 includes accounts of important players such as Barney Oliver, Paul Ely and Ed McCracken. There's even a note about Jim Hewlett, son of HP co-founder Bill Hewlett. A golfer and a nature lover, Hewlett's son got Foster in trouble. As part of the system's revival there was even a face-saving video interview, designed to revive the ruinous reputation of the 3000.

Read "Early 3000 Flights: A New Embattled History" in full

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

October 24, 2014

Legacy Management: More than Rehosting

LooksoftwareSpeedware became Freshe Legacy several years ago, and in 2012 the company's business crossed the watershed from Hewlett-Packard sites to those running IBM's AS/400 servers. The latter is now called IBM i, and in one interview Fresche CEO Andy Kulakowski said the company's customers are now 85 percent IBM users.

The world of IBM i is still populated with product releases, vendor support, and the challenges of keeping a legacy line of computing looking current. Last month Fresche purchased the assets, intellectual property and customer base of looksoftware (yes, all lowercase and all one word.) Next week the newest tool in the Fresche belt goes on display in one of the oldest of enterprise venues: a $949 user conference, COMMON.

COMMON has served IBM users since before there was an Interex. The first meetings of the group surrounded the IBM Series 1800, a data acquisition and control system which was similar to the 3000 in that it used a Multi Programming Executive (MPX) operating system. COMMON meetings began in the 1960s, and the 1800 was used in product for more than 50 years. Even though COMMON attendance has dropped and the gatherings have gotten shorter, the group still assembles the experts and the faithful once a year for a classic expo and education event. This year's is in Indianapolis, following the model that Interex used for HP 3000 customers: a moveable feast taking place in cities both great and, well, common. One forgettable year the Interex show was held in Detroit. In the Midwest, however, a great number of manufacturers and distributors have always used business systems like the 3000 and the i.

ModernizationDrill into the looksoftware website and you'll find mention of the HP 3000 in the Modernization Solutions section. Along with methodologies such as cloud enablement, database modernization and automated code conversion, MPE/iX customers can find a relevant line, "Re-hosting (HP e3000)." COMMON attendees could very easily hear about rehosting at the conference. After decades of serving just the AS/400 family, it's now an expo that embraces Unix and Linux computing from IBM, too.

Read "Legacy Management: More than Rehosting" in full

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

Search