October 12, 2018

Friday Fine-Tune: Speeding up backups

Spinning-wheels
We have a DLT tape drive. Lately it wants to take 6-7 hours to do a backup instead of its usual two or less.  But not every night,  and not on the same night every week.  I have been putting in new tapes now, but it still occurs randomly. I have cleaned it. I can restore from the tapes no problem. It doesn’t appear to be fighting some nightly process for CPU cycles. Any ideas on what gives?

Giles Schipper replies

Something that may be causing extended backup time is excessive IO retries, as the result of deteriorating tapes or tape drive.

One way to know is to add the ;STATISTICS option to your STORE command. This will show you the number of IO retries as well as the actual IO rate and actual volume of data output.

Another possibilty is that your machine is experiencing other physical problems resulting in excessive logging activity and abnormal CPU interrupt activity — which is depleting your system resources resulting in extended backup times.

Check out the following files in the following Posix directories:

/var/stm/logs/os/*
/var/stm/logs/sys/*

If they are very large, you indeed may have a hardware problem — one that is not "breaking" your machine, but simply "bending" it.

Posted by Ron Seybold at 07:25 PM in Hidden Value | Permalink | Comments (0)

Pivital Solutions: Your complete
HP 3000 resource

October 10, 2018

Wayback: Charon kicks off with freeware

Free-beer-case-computer
Six years ago this week the HP 3000 emulator Charon had its debut among the masses who wanted to kick the software's tires. 2012 was the first year when a downloadable version of the PA-RISC emulator, the first of its kind, could be pulled off an FTP server in Switzerland. Stromasys called the freeware a Demo Package.

This was an offering that illustrated the famous gratis versus libre comparison. Something that can be free, like demoware, was also restricted in its use. You paid nothing but had to abide by the rules of use.

One of the more magic portions of that demoware was HP's own software. Since Stromasys had a long HP relationship, tracking back to the days when HP bought Digital, the vendor was able to include mpe75a.dsk.gz, an MPE/iX 7.5 Ldev 1 disk image that contained the FOS and most HP subsystems.

But wait, said the offer, there's even more. The file mpe-tape.img.gz was also available via FTP, a virtual HP 3000 SLT, generated on Stromasys' A Class 400 test system. "You can configure Charon to boot from this virtual tape file," the demo's read me advised, "and perform an INSTALL from SLT."

Whoa, that was all a leap of Web-based advances. For the price of some disc space, a 3000 owner could have PA-RISC hardware (slapped onto freeware Linux, running on an Intel server) plus the 3000's OS (on a limited license) and a file which could become an SLT. HP had never made MPE/iX a downloadable up to that point. The 3000 was beginning to look like a modern server again, empowered by files from an FTP server.

The freeware propogated through the 3000's universe, with each download promising a purchase of the full Charon. It was supposed to be a demonstration of an emulator. A few bad actors in the market tried to make the A-202 model a production version.

Read "Wayback: Charon kicks off with freeware" in full

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

October 08, 2018

Leaving Something to Retire On

Vacation-home-retirement-rocker
The fate of MPE/iX shops can be a malleable thing. In the middle of the last decade every one of them was considering paths toward the future: migrate, homestead, or some blend of the two where homesteading was the prelude to a migration.

The more current situation takes the age of the professionals into account. People who were in their 50s during that decade are now closer to Social Security age. Only one person in five is going to enjoy a traditional retirement from here on out. They will continue to work and their benefits will reduce their need to tramp through the IT sector looking for a premier home. A nice chair with a great view will do.

If you're still in charge of an HP 3000, and you're not an IT pro, you're likely to be a CFO or a corporate soldier in operations. Those IT folks have retirement tattooed onto them. The MPE/iX applications, not so much.

The HP 3000s are going through a similar transformation. You don't retire an HP 3000 as much as you leave it in place and give it nothing new to do. The strategy might be called Migrating in Place. All of the other operations in the datacenter have a new and uncertain future. The MPE/iX applications now know where they're going: retirement, someday, but they all have to be made comfortable along the way. The most nimble of IT managers know there's must be reliable hardware right up to the retirement date for an application.

This thinking brings newer hardware into an organization to support older applications. The HP 3000 itself could get a replacement with a Charon virtualized server. Or it might be the storage components that are updated. Networking and switches have their makeovers. It's all justified better when the new elements are ready to work with other systems in the datacenter.

The code itself and the data remains the constant. In the retirement scenario, this might be like the retiree who's looking over active senior apartment complexes, or maybe that downsized house that's newer and needs little maintenance. The COBOL and the IMAGE datasets are the fingerprints and recognizable faces that establish who's moving into senior living.

"I am seven years past retirement age and still supporting four HP 3000s," Roy Brown said on the message board of the HP 3000 Community group on LinkedIn. "I'm trying to get it down to two now, so I can at least go part time."

One of those remaining servers looks to be a durable as a homeowner association board member. "Traditionally one of the two 3000s, called Troy, sees off anyone who tries to shut it down," Brown said. "The last three attemptees, each trying separately and some months apart, all lost their jobs shortly after commencing the exercise. So I now need to engineer the fall of Troy without instead engineering the fall of Roy." 

 

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

October 05, 2018

Shifting Data Off the 3000, Easily

NewsWire Classic

By Roy Brown

Tool-beltWhether you are migrating data, or just wanting to present it in a more portable format, be aware of how you can manipulate it using those all-pervasive Microsoft tools. When your consulting role takes you across a wide range of HP 3000 sites, you rapidly learn that not everybody has all the add-on tools you might like to see – Qedit, MPEX, Adager, Suprtool, and so on. You can rely on what’s in FOS, but there are a bunch of things you are brought up short by, that are not so easy without the armory above.

So, when I needed to extract and massage data from a bare or nearly bare HP 3000, I pretty soon learned to rely on what I could bring to bear from my laptop, equipped with Reflection and the MS Office suite.

Actually, the product I really missed isn’t one I listed above – it’s MBF-UDALink, from MB Foster. Perhaps because I’ve never quite mastered its rather quirky interface, I find it’s often easier to rewrite a query than to modify one. But they are so quick to write that it really doesn’t matter – especially for multi-set, multi-key extracts.

And as it can make your data extract, put it in the format of your choice, and transfer it to your PC via your termulator, all in one go, it lets you skip a whole bunch of what I describe below; stuff you need to do only if all you have is FOS in this area.

Extraction

Mostly, when grabbing stuff on an ad-hoc basis, I like to list it out in Query, and watch it scroll by in Reflection, with logging to a PC file turned on. I know that I could file equate the output to QSLIST with DEV=DISC, make a file and copy it that way, if I wanted. But this way, I get to see problems as it runs. And if it runs okay, it’s already on the PC for me.

I use Query because it’s always there. I figure I don’t need to do a Query tutorial here – though you can email me at [email protected] if you’d like a copy of one – but suffice to say that you can usually walk the paths you need, and pick up the data you want. I generally set LINES=0 or NOPAGE, and I pay attention to numeric field formatting with Edit masks where needed, but I only output Detail lines. Dates I leave in CCYYMMDD format, just as they come. And I don’t need to do any math – I can save that until I’m in Office.

But I do hit the 80-character line limit, which is where the first neat WinWord trick kicks in. I use multiple lines, and I mark the end of each line except the last with a string like ### - something that I know won’t ever occur naturally in the data – ending at position 80.

Read "Shifting Data Off the 3000, Easily" in full

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

October 01, 2018

Where have all the migrations gone?

Wilted rosesIs the bloom finally off the rose for migrations away from MPE/iX? I had lunch today with a support provider for third party maintenance who sees a lot of activity in the 3000 market. He said that as far as he can see — and of course nobody can see everywhere — the HP 3000 migration activity is pretty much done.

Nobody has complete visuals on the full marketplace. It can be difficult to know much about migration projects in progress. So if 3000 migration is done, maybe what that really means is that all of the migrations have been started by now. For example, I wrote about a company last month whose 3000 expert says they’ve been migrating for awhile. The project is supposed to be over by the end of the year. Then this 3000 veteran of many years added, “but you know how that goes.”

Like lots of 3000 experts, that IT pro is retiring from his company. At year's end he'll be leaving behind a 3000 app that’s working. Whoever’s got the job of getting that replacement app online will have to finish it in 2019 without as much MPE expertise on staff. I'm guessing that even retired, the expert will be able to bill for some consulting. "You know how that goes" usually means there's some unresolved issues, like there are in every migration. You never know what you've done well in a migration until you get to the testing phase. Birket Foster used to say that testing was at least 30 percent of the workload in a migration.

Once a migration team's testing gets serious, knowing the MPE app and the 3000 technical infrastructure can show off its benefits. It might even be like the way COBOL skills got valuable in the years leading up to Y2K. Getting that kind of independent expertise into the contract-procurement market can be the big hurdle for 3000 veterans. Lots of great 3000 experience has worked inside a company. Being for-hire is a different gig.

Migrations can be pretty secret. Some datacenter managers don’t want to talk about having a genuine legacy app (what, you use MPE?) still serving in production. Other 3000 managers don’t have control of the migrations their company is doing. Therefore, little knowledge they might share with 3000 friends (or writers). That migration might be done by the supplier of the new app, or the Platform as a Service (PaSS, or what they like to call cloud) such as a Salesforce reseller.

Finally, there's the IT management that's going on at the C-level by now. The guardians of the datacenter are sometimes not connected to the 3000 at all. The CFO just wants an outside company to take that putty-colored HP server box out of the shop, because nobody knows enough about it anymore. That's the circumstance where outside migration services can help. You've got to find those CFOs, though. A list of former 3000 sites might help. Someone just offered us one—but it was from 1988. There are dead people on that list.

Just because it's hard to see 3000 migrations doesn't mean they're not there. You can say the same thing about spirits and faeries and even some religious powers. If you're hoping for migrations to appear, it doesn't hurt to believe. Get your shingle out there and explore. Verradyne is a collective of experts who've done 3000 migrations.

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

September 28, 2018

The Migration Dilemma

3000-migration-penguins
This article first ran in the opening month of the 3000's migration era. For the companies still working through a migration, most of the issues remain in play. More to the point for the homesteading 3000 site: These are high-level reasons why a migration isn't on the horizon.

Newswire Classic

By Curtis Stordahl

Well, the other shoe has dropped. Hewlett-Packard has given their HP 3000 customer base just five years to migrate to another platform. This is a daunting task that is full of risk.

The biggest migration risk factor is probably that the complexity of the applications on the HP 3000 may have been severely underestimated. These applications can be over 20 years old, and some have had scores of programmers continuously evolving the original application without any supporting documentation. Consequently, it is possible that nobody knows just how big and complex these applications are. Many migration projects are also led by personnel with no experience on the HP 3000 platform, who have a perception of it being something like an old dBase application on an IBM PC.

Many organizations will be lured by the “flavor of the month” technology and want to completely redevelop their HP 3000 applications accordingly. This is also full of hidden risks.

A major redevelopment is going to essentially have three project teams. The first project team is going to be responsible for the development of the new application. This team faces multiple risks: of underestimating the complexity of the legacy application they are replacing; or of completing the development only to find it does not meet the minimum requirements and cannot be implemented without extensive rework.

At that point, the team could then find it impossible to obtain the resources needed to complete the project. The technology they choose may not meet expectations and so will not satisfy the minimum requirements. If you go outside your organization for new application development, the vendor you contract to do the work could go bust.

A second project team needs to migrate the data to the new platform. A radical change in design could make this difficult if not impossible.

A third project team needs to provide ongoing support to the legacy application. A major redevelopment could be years in the making, and you can’t stop the business from evolving during that time. This introduces additional risk into both the development and migration project teams because they must aim at a moving target.

There is an overall risk that a migration project could fail, leaving you with no additional funding or time to recover from the failure.

Read "The Migration Dilemma" in full

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

Search