January 02, 2017
Where's your backup media in the new year?
Here in the opening days of the New Year it's time to resolve your way to a cleaner 2017. People in the US and the UK voted for changes starting this year and they'll get some, including unexpected ones. You don't want unexpected change on your homesteading HP 3000 system, though. One of the simplest means to forestall a crisis is getting fresh media for your backups. MPE/iX system backups are no better than the media they employ.
Not long ago, a 3000 manager was looking for fresh DLT tape for his backups. Tape remains a part of the backup regimen at some shops, never more true than at a site still using HP's 3000 hardware. DDS drive verification should be among your new year's examinations.
New tape media is available for purchase. New tape all the way back to DDS-1 is on the Data Tech Store website. As a minimum 2017 homestead resolution, write a fresh backup onto new tape.
Disk backup will pull your homestead practices out of the 1990s. As DLT technology fades, cheap high capacity Serial ATA discs took their turn as the method of choice for large backups. Store to disk should be the next generation of MPE/iX backup. Using an SCSI to SATA converter, newer drives can capture backups from 3000s. HP's SCSI storage devices for 3000s are at least a decade old by now. SATA disks work well for smaller systems where Model 20 HP backup units are overkill.
The age of media can be offset by more recent design. Although it's slower and has lower capacity, tape is a seasoned technology. On the other hand, disk has the advantage of being engineered more recently. Pencils versus rollerball pens is a similar consideration. You know exactly how long a pencil can be used. Pens are more indelible but expire unexpectedly.
MPE/iX servers created using the Charon emulator from Stromasys can even employ SSD disks for backups. Verifying any media, new or old, should be on a manager's to-do list for 2017. It's even better to craft a regimen that rotates fresh media, whether you're relying on tape or storing to disk.
Pivital Solutions: Your complete
HP 3000 resource
December 28, 2016
HPE losing weight for 2017: in servers, too?
Hewlett-Packard Enterprise made itself smaller during 2016, the natural progression of a slim-down that started in the fiscal 2016 period for the company. Annual results for the first full year of the dual-HP venture—one devoted to business computing, the other to all else—showed a continued decline in sales. HP cut its software group loose this quarter, selling off assets like Autonomy to Micro Focus. Becoming smaller has not helped HPE's overall numbers quite yet.
Sales at the Enterprise group, home to 3000 replacements like ProLiant servers, fell by 9 percent from 2015's Q4. The full HPE sales tally for the quarter dropped by $900 million in year-over-year measures. Were it not for favorable currency shifts, the company would have had to bear the full range of these losses. Until HP could offset its results with divestitures and currency benefits, the Enterprise Group ran $403 million in the red. A total of $50.1 billion in HPE sales was booked in 2016. More than $3 billion in profits were left after expenses were met and taxes were paid.
A report from Patrick Moorhead at Forbes noted that the sell-off of HPE software to Micro Focus was a marriage to a company with a solid history of preserving acquired products. Whitman "bragged on Micro Focus a bit," Moorhead wrote, "saying that the company has never shut down a product that they acquired and merged with, and that their growing assets will be important moving forward." He added that the statement looked like it was crafted to keep the former HPE software customers satisfied with becoming Micro Focus clients.
HPE keeps slimming itself down to ensure its expenses will drop. Since revenues are on a decline year over year, the ploy to sell off businesses with dim short-term prospects seems destined to continue. On the website The Street a story has reported that according to Credit Suisse analyst Kulbinder Garcha, Hewlett Packard Enterprise could part with its servers, storage, IT support and consulting. One potential buyer might be the Chinese multinational networking and telecommunications equipment and services company Huawei.
Hewlett Packard Enterprise's server business, which Garcha values at $8.9 billion, could interest Huawei. The unit has $15.4 billion in projected fiscal year 2017 sales and $1 billion in Ebitda, Credit Suisse estimates.
December 26, 2016
Did you get what you wished for?
Nine years ago we ran an article that suggested 10 things a 3000 owner could put on their Christmas list. Most of them were directed Hewlett (Santa) Packard, since the vendor's toy factory was so full. After this weekend of Christmas, it's instructive to take a look at what was delivered from the 2007 list and why—or why not. In summary, the HP 3000 hardware remained frozen in time. The software did advance, though. Here's the wishes.
1. Unleashing the full horsepower of A-Class and N-Class 3000s
You got this only if you poked around for a third party consultant who knows how to do this. HP had three more years of support and one more year of full MPE/iX lab when we wrote that wish in 2007. All those years made no dent in the vendor's resolve. It's okay, there's Charon HPA from Stromasys to introduce speedy futures.
2. Or just unleashing the power of the A-Class 3000s (since the A-Class operates at no more than one quarter of its possible speed)
Didn't get this, either. We're always surprised to see how many A-Class systems still show up for work every day. The A-Class amounted to the Series 9x8 caliber of PA-RISC for MPE/iX.
3. Well, then just unleash the N-Class systems' full clock speeds
Like a broken record here: this didn't appear under any tree, either Christmas, phone support, or other kinds. There is a way to employ eight CPUs on 3000-class PA-RISC servers. Don't ask HP about it. Your independent support provider will probably have a story to tell you.
4. HP's requirements to license a company for MPE/iX source code use
The market got this a couple of Christmases later. Source didn't matter much to the future of the system. It improved some workaround options, though. This became more important as more workarounds edged into the 3000's support practices from independent providers.
December 23, 2016
The True Meaning of A 3000 Christmas
Charlie Brown shouts to the stars in the 1966 TV classic, "Isn't there anybody here who knows the true meaning of Christmas?" Linus leads him to the story that started the season which we're now ending. I like to think of that character's voice delivering an answer to the question, "Doesn't anybody remember the true meaning of MPE/iX?" Linus might say, "Its value, Charlie Brown, and its promises kept."
Like the commercial holiday that Charlie despised, there was always the phrase "you could just tell them to migrate" while discussing what HP's 3000 iron cannot do.
Feelings can affect choices and confirm faith. There was a design to extend the 3000's memory from 8GB to 32. But HP explained it couldn't justify doing that kind of work any longer. Adding "So migrate" might have sent people looking for systems with better memory, like a Christmas tree all shiny and new.
There are people who have known MPE/iX just as long as HP's lab experts, and some more deeply. A team of third party experts wrote the book Beyond RISC. HP bought thousands of copies. These two sides, first inside HP and now out in the expert community have wooed and rued that MPE gal, all while she has gained weight (years) and lost her tone (customers, demanding updates) and shown more grey (elderly versions of Ethernet, SCSI, all the tendrils of open source).
Yes, they've both had a relationship with her, but the outside experts still love her. HP's experts took her out, bought her dinner, even gave some gifts to show they knew her. The true meaning of MPE/iX and protecting a promise now resides in the wise Linus of our world, the independent software and support providers.
December 21, 2016
Wayback Wed: A Dark Day for Emulation
The future looked dim for hosting MPE/iX on virtual hardware in December of 2009. Your market had little news about the forthcoming Charon HPA 3000 emulator. That software was only in alpha testing. This was the month that Strobe Data announced it was curtailing development of its 3000 emulator. Your community headed into 2010 with the hope of a Stromasys success and HP's promise to announce the new independent holders of MPE/iX source licenses.
Licensing source for an OS that only runs on aging HP hardware has value, indeed. Support customers benefit from outside licenses. It's well worth asking if your support vendor has such a license. But as a model to extend the lifespan of MPE/iX in production, source won't do the work that an emulator does: create new boxes.
Strobe hoped to do that using new hardware. The company started as a venture to emulate Digital computers as well as the HP 1000 real time machines. Many roadblocks stood in the way of a successful 3000 emulator launch in 2009. Strobe's founder Willard West intended to sweep away some obstacles by obtaining new PA-RISC processors. The chips were to be integrated on cards that would go into high-end Windows servers.
But development takes money. The resources for non-Digital development at Strobe did not materialize. It would take two more years for the ultimate winner in 3000 emulation, Stromasys, to bring out a product that needed no special HP hardware—just a special OS to run, MPE/iX.
An economic lull at the end of 2009--HP was reporting declines in all of its businesses except services --set the 3000/PA-RISC emulation work onto Strobe's back burner. The rate of hardware aging made a profound difference to Strobe, a small concern compared to Stromasys.
"We are just trying to survive the lull in government orders right now," the company's Alan Tibbetts said during the dark of that December. "The trouble is that the sales of our [Digital] PDP-11 line are down. The PDP-11s became unreliable more quickly and we have sold a bunch of them in the past, but the easy ones have already been captured." The month was a moment like the epic one in The Empire Strikes Back. Yoda watches Luke fly off Degobah, his training unfinished. "That boy was our last hope," he said. "Now matters are worse."
"No," Obi Wan replies. "There is another."
December 19, 2016
University completes its course with regrets
After decades of use in a wide array of business and educational functions, the Idaho State University of has shut down its HP 3000s. The institution worked with Powerhouse tools from the earliest days of the 3000, a period that included some years using MPE V. Idaho State University turned off our HP 3000s. "We have the one N-Class server, plus two A-400s, for sale or for parts if there is interest."
John MacLerran reported to the 3000 mailing list, "with fond memories", the accomplishments and lifespan of MPE/iX at the university based in Pocatello.
The HP 3000 had been in use at ISU since the early 1980s, running everything from Procurement and Payroll to Student Registration and Grading. When I started work at ISU as a programmer in 1984, we had two Series 68s (later upgraded to Series 70s). Over the years, we upgraded as budget allowed. We installed the current boxes in Summer of 2001. Our production box was an N4000 4-way 440 mHZ box, and our development box was an A400 110 mHZ box. In 2004 we added a VA7100 array to our N4000 box, and it was this configuration that we turned off in October.
We went live with Banner, an ERP for universities, in 2009— but some applications on the HP 3000s hung on much longer because there was no suitable replacement in the ERP system.
Since we are a State of Idaho agency, there is a somewhat convoluted process for us to sell the boxes, but if there is any interest, you can contact our Customer Services manager Tony Lovgren at email@example.com for more information.
Idaho State worked, tested, and managed its migration over more than 11 years. Since the choice to migrate was replacing in-house Powerhouse with the Banner application, its exit from the 4GL was simplified. Batch processing was harder to replace.
December 16, 2016
Friday Fine-Tune: Login recovery strategies
We have changed passwords on MANAGER.SYS—and now we cannot locate the changed passwords, thanks to some staff reductions that made the new passwords unavailable. Any ideas on how to recover them?
John Stevens says
If you're logged on as OPERATOR.SYS, do LISTACCT on all the accounts that may have SM capability, then logon as the MGR/MANAGER of those accounts: TELESUP, and SUPPORT, and there are others; LISTACCT will find them. Login as those users (unless you don't have those passwords either) and LISTUSER MANAGER.SYS. Vesoft's MPEX might help ease some of this as well.
Duane Percox of QSS adds a simpler approach:
Using your favorite editor or other utility search for the string: "ALTUSER MANAGER SYS"
You will notice: PAS=<the pwd> which is your clue.
Steve Ritenour suggests that a logon to the TELSUP account will unlock the passwords.
Some 3000 managers believe the subject itself should be filed in a place not easily found. "These responses are all well and good," said Bruce Collins of Softvoyage, "but shouldn't we be thinking twice about posting this kind of information (i.e. how to hack an HP 3000) to the 3000 newsgroup?"
December 14, 2016
HP: Still a font of talent after all these years
It's Wayback Wednesday, but the 3000's history recall has fresh entries from the current day. A lot of HP 3000 sites turned away from Hewlett-Packard's offerings over the last 15 years. But more than a few have not, even after three CEO ousters and a split up of the company into consumer and enterprise parts. There's still something in the split-off parts to admire. A new book chronicles lasting HP lessons to the industry players who are lapping HP today.
Among the former: thousands of HP employees who've spent decades serving the HP customer. From engineering desk to conference presentation room, too many people to count or name have lifted the level of service. We heard from one today, Guy Paul, who once managed HP 3000s for the vendor and now is working on network storage for HP Enterprise. When asked what's remained stellar about the company where he's worked for 32 years, Paul pointed at people.
December 12, 2016
Security in cloud IT expands to fit ERP
HP 3000 sites that make a migration bring a broad array of technology into their planning rooms. In the world of MPE/iX, the server and infrastructure was almost always on the premises of the company or in a subsidiary's offices. Once a company begins to migrate to commodity environments, this structure starts to evaporate. In a meeting about what to do next after something like MANMAN, clouds and the ground they float above get equal valuation.
Security is a challenge in the process of floating clouds for enterprise IT. As Terry Floyd from The Support Group is leading Disston Tools through its migration, he's seen that security is no sacrifice to the gods of change who live in the clouds.
Kenandy is making its way into the command center of Disston. "We are seven months away, on schedule, and on budget," Floyd said when he checked in last week. "There is a lot to do here. MANMAN is very robust, and Disston has a lot of customizations, as well as serious use of EDI."
By its nature EDI passes sensitive information across networks. Kenandy works by riding the Salesforce cloud and its networking. Disston won't have to settle for something less secure.
"We are just getting into setting up user security settings," Floyd said. "Kenandy is as robust as MANMAN is. It can be tightened down as much as you want."
December 09, 2016
Friday Fine-Tune: Driving Filesystem Checks
In the middle of a full backup, the HP 3000 at James Byrne's shop came to a system halt at 3 AM. It was the kind of halt that puts up those puzzling abort messages not even HP has fully documented. For example, about SA 1458, Robelle's Neil Armstrong said, "My experience with SA 1458 is that it is a catch-all abort. You need to look at the subsystem information and the only way to truly know the root cause would be to get a dump and analyze it." He referenced a webpage that breaks down the process of doing 3000 system failure analysis, too.
When a halt occurs during a backup, there's always the chance the 3000's filesystem has been injured. "I'd say run FSCHECK.MPEXL.TELESUP and check your filesystem," said Keven Miller of 3k Ranger. He added that a former HP support expert, Lars Appel, "instructed me that System Abort messages are in subsystem 98. From the MPE Error Messages Volume 2, Chapter 4, System Aborts, 1458 MESSAGE means A critical process is being terminated due to a trap."
Sure enough, power interruptions at Byrne's shop introduced damage to an Image database.
We reached the point last summer were we were toying with going off-grid simply to avoid the repeated power interruptions. If this sort of thing is causing damage then we will have to consider it. And it seems to; we now have a broken backward chain in one of our Image databases. A thing that I cannot ever recall. Coincidence? We are doing a backup, and then I will be using Adager to go in and take a look.
FSCHECK is an included tool on the 3000. It's simply there to validate extents and scan the table cache for missing files. Better tools include not only the legendary Adager, but independent support suppliers for the 3000 owner. People who know the fast commands of tools like CSTM. "What does your support provider say?" asked one support vendor. Self-support can be backed up by 3000-L questions. Some of the advice about the halt even ran to looking at memory issues. A provider can help eliminate these possibilities.
December 07, 2016
Taking Steps into Open Source with a Plan
A significant number of HP 3000 shops have employed Linux as a replacement over the last 15 years. (Yes, it's been that long that the MPE/iX community has been migrating or homesteading their systems). Over that time, open source software has become so mainstream that an architecture meeting often includes a line like, "Well, what can open source do for us here?"
If open sourcing a commercial datacenter sounds enticing—think of the size of the community you join, for example—it's wise to remember a commercial open source is the way to success. Downloading and testing is always essential, but adding open source has its best prospects when there's a commercial, paid support aspect to the choice.
This week we reported on one HP 3000 site where the system is making a slow exit. Harte & Lyne is still using a Series 918 with MPE/iX 7.5. The operations are being supplanted by what manager James Byrne calls FOSS: Free and Open Source Software. He's got his reservations about doing much more in that direction, though. Byrne said a more commercial—though not vendor-specific—approach to new architecture is in order.
HP was advising this to its enterprise computing customers as far back as 2006. Linux in the datacenter was a lot more exotic in that year, a time when HP was still selling support for the 3000. That vendor-based support is all gone by now, right down to the demise of docs.hp.com webpages where advice and training materials once lived. If you need 3000 support, third parties like Pivital Solutions are the best way to go forward, even if you're going away slowly.
An HP exec of 2006 said it only made sense to look for a supported FOSS design. David Claypool said
The rational thing to do is to choose something from a commercial company, whether implementations available and supported by a Linux distribution or non-affiliated Xen implementations like those from XenSource, Virtual Iron, and now Oracle.
Working together in such alliances was part of what FOSS was all about at the beginning. It would be another four years before Oracle would hire the departing CEO of HP, Mark Hurd, to run Oracle's software business. In 2006 all was pretty collegial between Oracle and HP.
December 05, 2016
COBOL's Continuing Value for 3000s
The venerable workhorse of COBOL is often maligned during IT strategy meetings. The language usually has to make do with a lot less educational opportunity these days in universities, too. It is verbose and legacy and not ever going to captivate a ping pong table discussion about which platform development platform is best. There are perhaps only 1 million people in the world still trained in using it.
However, COBOL brings a single, enduring asset to the 3000s and other mainframe-caliber servers where it runs. COBOL is a standard, one that's exploited and extended and supported by many vendors, not to mention carried through decades of use. This is no one-man show.
You cannot say that about Powerhouse, or any other fourth generation language. If there's a standard out there for C-Sharp, or the wonders of Visual Basic, it is controlled by a single vendor. Powerhouse users are in a pickle. A single company, Unicom, controls the fate of all users employing the 4GL, and the vendor is jerking its leash on users. When Unicom said it was canceling the license of one customer, James Byrne at Harte & Lyne, then Byrne had a response.
"I am ignoring that," he said. "One cannot cancel a contract without cause."
He went on to point at what sets COBOL apart while he's choosing foundational software. "Not that we use it," Byrne said, "but there is a reason that COBOL is still around. The people who do not understand why are at the root of many of the problems with FOSS." That's open source software he's referencing, something that a vendor cannot cancel, but drifting toward commercial prejudices anyway.
December 02, 2016
Friday Fine-Tune: Print classes, STORE, FTP
I need to add classes to a printer on my HP 3000. I keep getting a message that the LDEV doesn't exist from SYSGEN's I/O section when I issue the ACLASS command. I can see the device exists, so what's the problem?
Devices on your system that are configured through NMMGR must have their classes changed through NMMGR, which is probably why you're getting the error message. Run NMMGR and go to the PROFILE for the device. You should be able to add classes to the device at that point. After making changes in NMMGR, remember to VALIDATE these changes to NMCONFIG, and then cross-validate using the RDCC command from SYSGEN's SYSFILE section.
NMMGR changes take effect after the system has been reSTARTed and the power has been cycled on the DTCs. You should cut a System Load Tape (SLT) making these changes so you'll have them on tape for your next UPDATE.
If your device was configured through SYSGEN, the device should have its classes modified through SYSGEN. You're right, you do use the ACLASS command in the IO section. Changes to the IO section require a START to make them take effect.
In HP's MPE/iX manuals I am are directed to backup the system as follows:
What is the practical benefit over
People trot out the reason from the distant past: if you have to do a re-install it is good to have PUB.SYS (and maybe the TELESUP account) on the front of the tape so you can restore quicker.
Gilles Schipper woke us up with his response. “The reason one would perform the former over the latter is to ensure that all of the files residing in the SYS account be placed at the beginning of the backup. Whether that is a good thing is, in my opinion, dubious."
November 30, 2016
This just in: Generalissimo Cobol is not dead
A favorite running gag on the most antique Saturday Night Live shows was Chevy Chase reading the fake news. With each broadcast he'd repeat this joke: "Generalissimo Franciso Franco is still dead." Same result, week after week. A situation with a lot in common with COBOL's current fortunes. Despite what people think they know about it, the Common Business Oriented Language still props up a vast swath of the business data across the world.
Nothing has changed with COBOL's fortunes since we last visited this topic with a podcast in 2014. During that year's spring, the NPR Planet Money radio team posted a show that blamed COBOL for the slow pace of money-changing in clearinghouse transfers. The mistaken report was like fingering English for the outcome of the Presidential election. Yes, the COBOL code in banks turns the IT cranks. The result is not the fault of the tool, but how it has been used. Yes, English was used in the 2016 campaign. [Insert joke about Twittering here.]
Our COBOL correspondent Bruce Hobbs pulled this story back into the light this week. He pointed to an article on the HackerRank blog, examining COBOL's not-dead-yet status once again. If you like numbers, the article included these above. Its still a language that supports 80 percent of all point of sale transactions and routes health care to 60 million patients a day.
To be fair, one of the sources of that graphic is the company still selling COBOL, Microfocus. But Gartner is also cited, an impartial consulting giant. In the NPR show the reporters interviewed an exec from Fiserv, a vendor who might have known better; they made some of their fortunes selling Spectrum/3000 for credit unions.
In the HackerRank piece, the author quotes an article from 20 years ago that surveyed why COBOL has held on so long.
November 28, 2016
3000 customers ponder what they're leaving
This month's relicense quotes that Unicom delivered to Powerhouse customers could spark some migrations. Although these 3000s have held on by using out-of-support software, the five and six-figure prices to return to MPE/iX support "are difficult to imagine as a sustainable model," said Charles Finley of Xformix. "The price makes it worthwhile to move away from Powerhouse entirely."
Finley, who's been assisting 3000 shops in migrations and conversions for 15 years and more, isn't the only vendor who's skeptical of the Unicom pricing scheme. "That strategy will not last long," he said of the sky-high quotes. "We can move the Powerhouse to a Java-based non-proprietary alternative for something in that [$300,000] ballpark. Pricing like that [from a vendor] only provides incentive for people to leave the product."
The full scope of what a customer is leaving is worth some consideration, however. Finley offered the scope of a typical 3000-using Powerhouse customer's datacenter lineup.
Focusing on the base language is misleading at best. The background processing/shell scripting is usually more difficult to migrate than the base application. I suspect that there could be more to a relicensing story than simply the Powerhouse license. For example, if the customer has some dependent 3GL code such as COBOL, a few third-party products such as Suprtool and MPEX, along with JCL, UDCs, and Command Files—the cost to migrate all of that, and the database and other file types, could well exceed the price of only the Powerhouse license.
Hearing such please-go-away pricing can be hard to comprehend. A decade or two of using a foundational tool like Powerhouse shouldn't end with a six-figure quote, but sometimes such a lengthy relationship drifts to a bottom-line-only state. "Don't they normally look at the financials before determining price?" asked consultant Craig Lalley. We've heard about that same software update strategy from another support consultant.
November 25, 2016
Friday Fine-tune: Adding disks and IP blocks
Is it possible to add a disk drive "on the fly" without doing a reload?
Jeff Kell replied:
You generally have to shut the system down to install and cable the disk to avoid electrical/interface problems. The usual approach is to use SYSGEN to configure the new device on the path where it will reside, keep the new configuration, shutdown the system, install the disk and do a START NORECOVERY.
Once the disk is recognized by the system, you can add it to your running configuration as follows (assuming the new drive will be LDEV 5 in the system volume set):
> newvol mpexl_system_volume_set:member5 5 90 90 (DISC,SPOOL)
[For details, see "Volume Management", HP Part No. 32650-90045 or "Performing System Management Tasks" HP Part No. 32650-90004.]
This will add the volume to the system volume set, but it also has some side effects. Since the new volume is "empty" and the disk space allocation routines attempt to "balance" loads across drives, all of your new files and transient space will be allocated on the new drive until it's capacity approaches that of the other volumes. This will create an I/O bottleneck on that drive, at least initially.
You could selectively :RESTORE certain accounts (or the whole system) to try and balance the allocation. You could also perform an INSTALL and a :RESTORE for better efficiency, but at the cost of a great deal of time. There are also certain third-party utilities that will balance disk utilization across members of a volume set. These utilities work online on a running system and don't require any downtime.
The network configuration of our HP 3000 was originally set up with one block of IP addresses. Now I need to add another block of addresses. Where do I add these in NMMGR?
You can add an IP address using NMMGR the following way:
- After typing NMMGR, select "Open Directory" .
- Then select "Update Dir."
- Now select the "Add" option (F5.)
- You are placed in a screen where you can enter the IP Address of the machine. The type is generally set to 1( IP).
- Now press the "Save Data" (F6) option, back out of NMMGR, and you are done.
November 23, 2016
Mailing news from the HP 3000: an old skill
Internal mail hosts remain a crucial tool in datacenters, even some running MPE/iX. "You still host your own email?" is not a question you'd only pose to a crazy manager. An organization's security standards can be so high that no outside mail server will be trusted. In the earliest days of email, 3k Associates built and sold a beautiful native MPE mailing system, Netmail/3000. It's a smart mailserver, meaning it doesn't require that an organization's e-mail be piped through an Internet provider's mail server for final delivery. Then in the late 1990s, HP's lab started the long process of porting sendmail to MPE/iX.
Now some 3000 sites are looking at how to replace their 3000-based mailing software as they migrate. One of them contacted us this week to ask about an alternative to sendmail. Linux is their migration target, after a history using the 3000 that goes back to the days of HP Deskmanager. Tim O'Neill shared a story while asking about an alternative to sendmail.
I saw that FreeBSD Unix has its version of sendmail. Seeing reference to FreeBSD made me recall a story about FreeBSD running on an old HP 3000, maybe a Series 70 or an early Spectrum system. I think I have read that FreeBSD is at some sites still running in production mode, as MPE and MPE/iX are. It also made me wonder what the installed base of FreeBSD might be — and how that compares to the installed base of MPE and MPE/iX on old hardware and on Charon hardware.
FreeBSD, like MPE/iX, has some surprisingly large companies using it. You might have heard about one of them called Netflix. Of course the Charon HPA emulator from Stromasys makes every remaining product and archival 3000 a candidate for the kind of longevity we see in FreeBSD.
Sendmail has a colorful history. The Unix Hater's Handbook devoted a full chapter to the software's vulnerabilities; sendmail comes from the Unix heritage, after all. By 2003, HP was still patching sendmail to shut down security breaches, although the breaching wasn't nearly as serious on MPE/iX as on Unix variants including Linux. Sendmail's open source capabilities are now under the banner of ProofPoint, the company that purchased the sendmail resources in 2013.
Sendmail's worldwide release was last updated in 2014. HP announced it was testing sendmail to place in the Fundamental Operating System in November, 2001—a month that's famous in the 3000's history for other reasons. But the software moved along to an 8.13.1 release in FOS. It's only one major release behind the worldwide open source version, now advanced to an 8.14 release. Sendmail also includes encryption.
November 21, 2016
Middleware rescues a Quiz captive, again
Old friends can help with new challenges to homesteading. Minisoft's ODBC software stepped in again to get a 3000 customer away from the pricing schemes of Powerhouse and its Quiz reporting software. That ODBC link between MPE/iX and Windows databases and tools turned out to be the essential component in pulling a client away from Powerhouse, according to the Support Group's Sue Kiezel.
Kiezel said her support client got an eye-popping quote to move Quiz from a 9x9 to an A-500 server: $27,000. Like some sites who are learning about the new regime of pricing from Unicom, this Support Group customer was returning to Quiz support after years of no improvements to the former Cognos product. Quiz made its way onto many MANMAN installations in the during the 1980s on the ERP suite. Getting out from under that legacy required a reasonable tool to connect the data with more modern reporting.
Enter the Minisoft ODBC software. The middleware connected with SQL Server to build a reporting database, data that was used to create the Excel spreadsheets everyone wants to use. As we've seen before, Windows-based reporting solutions like Crystal Reports can carry the 3000's data into departments better than Quiz did.
"SQL Server has turned into a beautiful database," Kiezel says. "You don't need a database administrator for it. Because of this kind of connection, my users no longer need paper for their reports. The middleware opens it up for MANMAN uses, and Excel can make joined tables for reports. Instead of just sending out a paper report, I'm sending out a spreadsheet, with the first three sheets of them working like a visual dashboard."
Visual Basic does analytics in this kind of report solution, too. "We are now in the modern world," Kiezel says. The bonus? Finding an expert to tune up these reports is a $50-75 hourly charge, instead of the $200 hourly that a Powerhouse consultant will charge to beautify and enhance Quiz. There are features and solutions that are worth the extra cost you'll sometimes encounter in MPE/iX. But reporting doesn't turn out to be worth the extra expense in licenses and expertise — not when there's middleware to open up reporting options.
November 18, 2016
Friday Fine-Tune: Tricks with command files
I'm working on a command file on my HP 3000. Is there any way to have it copy part of itself into a separate (temporary) file?
Jeff Vance replies:
MPE does not support the Unix concept of ‘here’ files, where input data for the command can reside in the same file as the command, except in the case of jobs. But even in a job, you may not include inline data for a script or UDC invoked by that job.
The SPOOKHELP script may be of some use. This single script contains the help text for all of the SPOOK commands plus the code to search for and display that text once HELP xyzzy is entered.
How can we execute a command after a user enters the :bye command in MPE?
Olav Kappert replies:
It is possible to execute many commands after the bye has been entered. Simply create a UDC (maybe a cmd file) called bye.
The contents of the UDC for the command bye is up to you. This would be useful if you want to do statistics before the session terminates.
John Pittman adds:
Don’t let them do a bye. We don’t allow any users access to OP system prompt at all. They get a logon no break UDC that runs a menu, and when they end the menu, they get logged off.
Inside that UDC at exit time, we build a string giving user, connection point (LDEV or IP of their PC) connect time, CPU date etc and append it to a log file. Then we know when anybody last used the system, how many users are using different connections, or when different user names are using the same connection point.
November 16, 2016
Noteworthy dates drive views of the future
This week on the 3000 newsgroup, Alan Yeo of ScreenJet picked up the remembrance torch to note the anniversary of 2001's 3000 business shut-off at HP. About your resilient computer he added, "In some ways it seems to have survived in some places in better shape than the HP that announced they were killing it!"
We agree and noted as much in the Nov. 14 NewsWire article. I promised to make not such a big deal about the history of the event; instead I tied it to recent advice about a hybrid of local and cloud-based ERP alternatives.
That event brought some benefit along with all of its carnage. Canceling the HP business operations for the 3000 (never an end-of-life; vendors don't get to define that) also sparked the completion of the first PA-RISC hardware emulator from Stromasys. The software continues to assure us all that the aging HP hardware won't be our only option over the next 11 years or so. Remember, on Jan. 1 2028, at 0000 hours, the dates stop working. Not MPE altogether, however.
A fix for that date issue might become a project for some remaining support company which has an MPE/iX source license. As you might infer from a date in this month's political events, stranger things have already happened.
November 14, 2016
The best wishes for your long life: a Plan B
Congratulations to us all. This is the 15th anniversary of the "we're killing off the 3000" announcement from HP. The end-game hasn't played out like HP expected. In 2001 the company's management didn't see three CEO resignations coming over those 15 years, or the company being forced to split itself to stay relevant to enterprise IT. Those two events are related. Yes, the 3000 got its pink-slip notice at the HP of 2001. So did the overstuffed, unwieldy Hewlett-Packard. The company that lurched toward every business while stepping back from others. It took 14 years almost to the day, but HP is half the size it was: HP Enterprise is the severed sibling from 2001's family.
Inside the 3000's division during that year, no one was talking about emulating the 3000 PA-RISC hardware that the company would stop building in 2003. That's now a reality, a new development since the 10-year anniversary of this sobering date. Hewlett-Packard was going to lead four customers out of every five away from MPE/iX, delivering them to the Unix alternative of HP-UX. Windows was going to get new customers out of the upheaval, too. No one figured three of every four departing companies would choose a non-HP environment.
Here on this date in 2016, the idea of an environment as a crucial strategy is feeling outdated. IT directors always cared about applications. Now they're told they don't have to worry about environments. The cloud computing providers will do that for them. Except when they cannot provide the cloud. Behold (above) the map of Internet outage from last month on an ugly day.
The Support Group's Terry Floyd offered a Plan B strategy to the manufacturing customers of CAMUS last week. More than 30 companies using HP 3000s and MANMAN are in the CAMUS user group. Floyd's company is delivering a fresh alternative to help MANMAN sites move on from the 3000. But he also supports homesteading sites. With a foot in both worlds, he recommends staying safe by having a Plan B, even while you employ cloud computing for your future.
November 11, 2016
Friday FineTune: Internal disk plus VA array
FiberChannel Storage Area Networks and shared tape libraries became popular in the years after HP stopped making its MPE/iX hardware. The HP 3000 supports SAN from the XP series of RAID devices to the VA7100 disk arrays. But how much should you rely on a RAID or SAN device? Internal storage devices might seem to be yesterday's tools, but the modest drive inside an HP 3000 can still be very useful — even if a company has invested in the FiberChannel storage solution of the VA7100.
Moving to the VA solution has great benefits, as reported in a story about using a VA7100 array with the 3000s. But booting directly from a VA array — well, you'll need an N-Class server (native FiberChannel installed) or a very expensive HP A5814A-003 Fiber/SCSI router (if you can find such a thing) to employ VA in the 9x9s.
The Crossroads SA-40 Fiber/SCSI switch will link a VA array to 9xx 3000s. It just won't let you boot your MPE/iX system from any of its drives. Craig Lalley of EchoTech recommends the affordable Mod 20 arrays for boot capability.
Internal drives remain as important as the VA arrays for a Series 9xx HP 3000, or even to the XP line of HP arrays. Even important enough to even duplicate them.
November 09, 2016
A Response to Being Stunned: No Tribute
Citizens of the US woke up this morning to a turn of political events described everywhere as stunning. There's nothing anyone can do to change that today, but in the event of a stunning relicense quote for Powerhouse products, you can respond with software that preserves your reporting administration. Some customers using HP 3000s can stun right back by leaving Powerhouse, using software from Minisoft to pave their data's way.
Steve Suraci of Pivital Solutions told us that one of the HP 3000 GrowthPower clients he supports has opened up one of those stunning relicense bids. In trying to get their software back onto support with the vendor, the customer received only an offer to relicense the full version of Powerhouse. "The most current product doesn’t even run on the 3000," Suraci said, explaining the folly of the return to support tribute being demanded by Unicom this year.
It's easy to think of back-support fees, levied in a market the size of the 3000's, as tribute: money demanded for nothing in return except a promise of help. A small promise indeed for software like a Powerhouse suite that hasn't had one MPE bit improved in more than 7 years.
The demand made even less sense considering what the customer was using. Quiz, the reporting end of the GrowthPower application, was the only Powerhouse software running on the 3000. "They originally acquired the product embedded in their ERP application," Suraci said. "They ended up purchasing the Minisoft ODBC and recreating the necessary reports using SQL tools like Crystal Reports, SQL Server, and Access."
Minisoft's products have never had an acquiring entity like Unicom take over and then demand such tributes from 3000 sites. Returning to support is a noble practice, something a manager with integrity does. However, this is a good deed that can be punished by ignoble companies. Support returns are a tradition that can trigger back-support fees. You don't have to pay them, but then your data has to live software else to get its support. The situation mirrors the dilemma of more than half of those who voted in the US yesterday. They don't want their President-elect, but they want to be citizens, too. It'll be awhile to see how much tribute the new President will demand. HP 3000 data is in a luckier situation.
November 07, 2016
Work of 3000s Helps Preserve Democracy
Tomorrow is a very special day in America. In a land called the United States we're going to elect a President to unite us. The kind of future we work toward will be chosen on that day. I'd like it to be the same kind of future the HP 3000 community has always worked toward.
This computer is called a business server because it works to meet the needs of business. A business relationship is at the heart of manufacturing concerns, insurance organizations, e-commerce companies and more. Business is at the heart of good relations with others in our world. MPE/iX software has always been a part of good relations. Much it serves the processes of business like invoicing. Going Forward Together might as well be a way to say Make Relations Through Documents. Business documents are the bedrock of your community.
In the earliest part of our 21st Century, Wirt Atmar was holding a seat as the conscience of this community. The founder of vendor AICS Research railed at HP's plunder of loyal customers, then proposed a Plan B to resist needless change. It was a time of high passions. The most crass and base expressions of the IT pros in our world were on display in the 3000-L listserver in that era. But since this is a republic with freedom of expression, although that trolling was revolting, it was tolerated. Much of that era's tone seems gentle compared to what's assaulted our ears and our spirits since this year began.
Back in 2004, Atmar was teaching his community how affordable Web-based lecture software could give minds a common ground. His QCShow product followed QCTerm, and both of those sprang from the makers of QueryCalc. In an HP World demo and lecture, Atmar explained his belief about how an HP 3000 was an alternative to war and atomic armageddon. These are real prospects for an American future. It feels like a disturbing misfit that anyone devoted to MPE, and having built a life's work from it, should vote for anything but a diplomatic leader.
Atmar had a fascinating background, including a stretch of his life when he worked to estimate and calculate the effects of annihilation. Nuclear throw weights -- the number of tons of atomic bomb to destroy various numbers of people and structures -- were his everyday work as a scientist in a government defense contract. He said he hated every day of his life that he had to wake and perform that work.
In contrast, when he created business tools that delivered invoices and orders, he felt his work spoke to the very root of human decency. Invoices, he said, were the everyday diplomacy of enterprises and organizations. I agree to purchase these goods and services, each would say. I agree to make and deliver them as you ordered, replied each sales receipt. A world still sending invoices, he said, ensured that war and revolt was a poor choice. Invoices were an expression of peace and a shining light for democracy and capitalism.
Something approaching half of America has already voted in this year's Presidential election. For those who have not, asking if a leader should respect business partners, find allies, and preserve relationships with respect— these all are a guide for anyone who's ever programmed or managed an HP 3000. Nobody is perfect. Anyone who wants to lead us should respect invoices, contracts and agreements. Tearing up a legacy is a poor start toward the future. Every HP 3000 community member should agree on that, and agreement is a good start toward where we need to go. We don't need to migrate away from working together and moving forward. Rather than looking back, we should take a hand in making history. Vote tomorrow and make some.
November 04, 2016
Reporting software takes over for pricey 4GL
By some estimates the 4GL software from Cognos sat on 7,000 HP 3000s at the 4GL's high water mark. A very serious share of that installed base was using only the reporting tool associated with Powerhouse, Quiz. Manufacturing sites such as those employing MANMAN, plus other applications, relied on Quiz to produce reports for managers and C-level executives. In many instances, these Quiz licenses came without restrictions or separate support agreements.
These are the sites that never had much of a business relationship with Cognos, and none at all by the time IBM bought the 4GL suite in 2007. Some of these sites eventually felt they needed to buy support, though, and some believed maintaining a license was important -- even though they'd become Quiz users when they implemented their application. The majority of Quiz sites stopped paying for support long ago. Like many bits of MPE/iX software, Quiz was frozen in time, a day when a reporting tool could cost thousands to support.
It was a bolt-on module, something that customers could be taught to un-bolt when pricing got outrageous, though. Cognos used to try to tamp down the outrage during the 1990s about license costs. Renegotiations were common, because the default pricing maintained strategies of an era when Windows was not a lower-cost enterprise option.
Steve Suraci of Pivital Solutions supports HP 3000 sites as an exclusive business model. It's an all-3000 vendor. He checked in about the latest shock over Powerhouse re-license prices. In the era of of ownership by Unicom, the licenses have soared agin. But there's another option to letting Powerhouse lock up a company to a 3000 license.
Back in the day, Cognos was always out of their minds regarding pricing. When they were bought by IBM, they got much more realistic and started offering a seat-based licensing model. Then Unicom entered the picture and they lost their minds!
We have a customer that owned the reporting-only version of the product, but was no longer on support. The only option available from Unicom was to re-purchase the full-blown development product in order to upgrade. The most current product doesn’t even run on the HP 3000. Needless to say, we replaced Quiz with something more robust and much less costly.
November 02, 2016
Legacy 4GL sites call foul on license ploys
Life is hard enough for any company that's been homesteading with their legacy-grade development applications working over the last 15 years. Some of these 4GLs haven't seen upgrades since before the Obama administration. Now the users of the Powerhouse products are crying foul over transfer or crossover license fees that have become up to 10 times more expensive.
Once tech experts and consultants on a Powerhouse mailing list got the news about a Canadian HP 3000 site facing a $300,000 quote to move Powerhouse onto Linux, stories emerged about the boosted prices for Powerhouse. At Boeing, the Powerhouse applications were a part of a move to the Stromasys Charon emulator. Ray Legault at the IT shop in Boeing said the transfer to an emulated 3000 was a six-figure purchase, and support fees have increased by 35 percent.
"When we went to the Stromasys virtual MPE/iX server, we found that a lot of the Cognos products were supported by Unicom," he noted.
Instead of our legacy HP 3000s where we paid support of $22,000, we now get to pay $30,000 a year. And it expires every year. We also had to pay over $100,000 to move Powerhouse to our HP ProLiant servers that host Charon. Unicom considers the product to be running on a RedHat Linux server and not the HP 3000 emulator, which raises the price.
Legault added that he's got a 10 percent yearly discount on the $30,000, but he's got to call a Unicom VP to receive that discount.
The initial report of this price spike came from James Byrne of Harte & Lyne, a logistics firm. Even though some migration experts think the $300,000 must include services, that $300K quote only covers licenses for Powerhouse and the related, Cognos-built tools like Quiz and QTP. The company dropped Powerhouse support right after HP pulled out of its business model for the 3000. Cognos, owner of Powerhouse at the time, wasn't getting any further support payments from Harte & Lyne.
"There seemed to be no point in paying our money for something that quite evidently was going to receive no more upgrades," Byrne said. "And we were right. The version sold by Unicom today for the HP3000 is 8.39, which happens to be the same version we have been running since late 2001."
The shop has been moving to open source software, although Byrne says the Free Open Source Software (FOSS) strategy has got its issues, too. In the meantime, Powerhouse prices are hitting the six-figure range to move away from HP's 3000 iron. An all-in migration is coming at Harte & Lyne, but the quote will freeze Powerhouse in place. Byrne said Unicom told him they were canceling his license, too.
October 31, 2016
A Scary Kind of October Surprise
James Byrne, a systems manager at Canadian logistics management firm Harte & Lyne, has reported a hair-raising development at his 3000 shop. A straightforward request to relicense Powerhouse from the MPE/iX version of the software to Linux resulted in an eye-popping quote.
The supplier of the software, Byrne said, has told him they want $300,000 to move the 20-seat license. Byrne noted dryly, "I recently had my decision to move our company away entirely from proprietary software validated in a most dramatic way."
It's always possible, when numbers like this surface on a Powerhouse relicense bid, that the wrong person in the Powerhouse business line has responded to a request for a quote. Byrne reported this exchange on the 3000-L mailing list, but didn't want to name the software vendor of Powerhouse. It used to be Cognos, but that stopped being true many years ago.
In a message of nine years ago, the debut of Powerhouse for Linux seemed tied to the fortunes of Powerhouse for HP-UX.
Cognos continues its ongoing commitment to its PowerHouse customers with the upcoming release of PowerHouse 4GL and PowerHouse Web for Linux. This is a direct port of the industry-leading application development tool that is so successful on other UNIX platforms as well as MPE/iX, OpenVMS, and Windows. User-based pricing for PowerHouse 4GL and PowerHouse Web for Linux is the same as for other UNIX versions. Please contact your Cognos Account Representative for availability.
Byrne said the exchange with the current supplier of Powerhouse licenses ended with a termination of the Harte & Lyne license for the software -- just after he was told the annual support fee for the relicensed copy was going to be $60,000 a year.
October 28, 2016
A Scheduler Built for You
A job scheduler is a good bedrock for keeping an enterprise humming. But leaving the HP 3000 means leaving a very good scheduler behind. Good news: a Windows-based solution that manages non-3000 hosts is on the market. MBF Scheduler was built with the needs and power of the 3000 in mind, too.
On November 9 a webinar shows the details of this product. A note from the company's vendor, MB Foster:
A Windows Scheduled Task may have worked well in the past. Today, your company has grown, and you've acquired more infrastructure. Do you know what jobs have being scheduled, on which server and at what times?
One of the many achievements of MBF Scheduler is its ability to manage complex batches through queues and a fence, ensuring everything runs in the right order and notifies someone if a job stalls or aborts. With the right solution, automating your processes is both practical and beneficial.
Sign up at the MB Foster website to participate and ask questions. Lots of schedulers for migration platforms offer features. Few of them know what a 3000 shop has grown accustomed to reply upon.
October 26, 2016
MPE/iX to private licensees: A new HP way?
Fifteen years ago HP was cutting its 3000 business loose and software vendors scrambled. A few of the bigger ones, like Adager, were looking for a way to buy the MPE/iX assets from Hewlett-Packard. Nothing could be arranged. However, HP recently started posting notices about its patented technology it's trying to license.
The IAM Market (free registration required) has started to hawk the intellectual property of both sides of the HP, a company about to mark the first anniversary of its split-up. Hewlett-Packard Enterprise is offering a range of patents, all designed to let a company use HP technology to serve business users.
HPE Patent Sale – Mission Critical Computing Portfolio
46 issued patents (41 US, 2 JP, 2 GB, and 1 FR) relating to servers and storage products for Mission Critical Computing (MCC). Key applicable areas include High Availability, High Reliability, Replication/Failover, SSD/HDD, System Management.
Except for that SSD element, everything in the portfolio could fall into the realm of HP 3000 and MPE technology. If only such a marketplace existed 15 years ago. More importantly, if only HP was actively licensing its IP back then. Something could have been worked out. Today, at least there's a mechanism for listing patents for sale and finding interested buyers.
October 19, 2016
Come together to conference with CAMUS
Admit it. It's been a long time since you talked person to person about your HP 3000 with somebody outside your company. User conferences and one-day meetings for 3000 folk used to be as common as leaf piles in October. That's what happens when you live a long time. You can outlive your community and lose touch.
CAMUS, the Computer Aided Manufacturing User Society, has a way to reconnect. At 11 AM Central Time on Thursday, Nov. 10, the Annual User Group meeting of the organization will form around a conference call. Terri Glendon Lanza of CAMUS is organizing the call. It's free.
The agenda, shared by CAMUS member Ed Stein of MagicAire, is 10 minutes of CAMUS announcements, followed by general discussion with the Board of Directors and everyone on the call. It's manufacturing managers who make up CAMUS, but you might have questions about a certain emulator that earned its stripes in the Digital market before arriving to emulate HP's 3000 systems. Both Digital and MPE managers will be at this conference.
Or you may be interested in the new ERP replacement for MANMAN, Kenandy. Experts from the Support Group -- which is installing Kenandy at Disston Tools this year -- will be on the call. You might just want to know something about MPE management that could take only a minute to answer.
Send an email to Terri at firstname.lastname@example.org, or call her at 630.212.4314, to get your conference call-in phone number. The call runs until 12:30 Central Time. You might learn something, or get to show what you know.
October 17, 2016
Rebuilding Systems Faster and Better
I'm looking at how to save as much time as possible in rebuilding an HP 3000's software and directories. My options seem to be using STORE, versus the sysgen tape command "tape store=@.@.@". What's the best way to go here?
Donna Hofmeister of Allegro replies
Unless your system is small (like a 918 with 8-12GB of disc), you don't want to try to do a full backup via sysgen. If you really do a full backup then I prefer this syntax “store /;...” as it is self-documenting and you know that the Posix files will be backed up as well. (On older releases of MPE, @.@.@ did not back up Posix files <eek>)
You want to make sure that you run 'buldacct' periodically (and routinely). You also want to make sure that you are somehow backing up your directory (store /;*t;directory, for example). Between the two, you have belts and suspenders (for recovering your accounting structure).
On older releases of MPE, you want to make sure that the network is shut down prior to making your SLT tape. And it's still a good idea to have the system quiesced when making an SLT, since everything in the sys account (and .pub.sys in particular) will be locked while the tape is being made. Nothing quite like grumpy users to make your day.
October 12, 2016
Wayback Wed: HP's Oracle-MPE discounts for 3000s hoped to spark new applications
Go back 20 years this week in the history of the 3000 and you'll find cheaper Oracle as a lure for application growth on MPE. Hewlett-Packard sank human resources and money into making Oracle a more attractive and affordable option for 3000 owners. By October, 1996 the pursuit of new applications was at its most ardent peak. HP would bring down the cost per seat of Oracle 7 by 25 percent just to get a company to install it on a new HP 3000. What the deal was seeking was places where Oracle might sell into a community that grew strong on IMAGE/SQL.
The deal, plus Oracle's applications, was trying to overcome three barriers to implementing Oracle. First, sites had data in IMAGE databases with no straightforward way in 1996 to move that information to Oracle's format. Second, site managers experienced higher management demands while using Oracle on other platforms. Finally, the price barrier for purchasing a second HP 3000 database (since IMAGE was bundled, even in 1996 after HP's efforts to split it off) kept sites from adding Oracle to their database mix.
HP's offer reduced one portion of the last hurdle. It offered Oracle's 7.2.3 version to 3000 sites at prices starting at under $1,200 per seat with an eight-seat minimum. Purchasing Oracle for an HP 3000 for under $10,000 hadn't been possible before. The price per seat increased based on HP's CPU tiers—the $9,600 price was available only for the lowest HP 3000 tier.
Oracle was always at arm's length from the 3000 user base, though. During the 1990s when HP was promoting HP-UX as a complete enterprise solution, the many Unix-based apps relied on Oracle foremost. In the middle 1980s, when Oracle was just rising up, a VP of market development asked me, "Why would I want to offer a database to a market where they already have a free, bundled database?" The question was a good one that never got a good enough answer for existing customers. HP and its Oracle allies had a good answer, but it was one that didn't matter much to the installed 3000 base.
We summed up HP's motivation on behalf of all customers with two words.
October 10, 2016
Duke diners deliver some wayback news
It's always a great event—since it's so rare now — to see 3000 folk gather in person. Last week an invite over 3000-L and other channels requested the pleasure of the company of anyone in the Bay Area who remembers — or works with — MPE and HP 3000s. The number of lunchtime diners at The Duke of Edinburgh pub was at the intimate level, which is not a surprise. What was interesting was how informed some attendees were.
"Some were finding out about the [Stromasys] emulator," Stan Sieler reported. He was among the few who were still working on MPE tasks. I was surprised that the news of the emulator was just arriving in October 2016, five years after the product's debut in the Bay Area.
In the fall of 2011, about 80 HP 3000 folk gathered at the last HP3000 Reunion. (I won't say final, because reunions tend to hold on until organizers and the ardent alumni lose the ability to travel, drive, and have meals together. We're not young, us 3000 folk, but we're spry.) The story of the Charon HPA product has orbited the MPE solar system for many months. Not everybody looks up at the sky to see the stars, of course.
Those getting wayback news about Charon included one who needed a free hobbyist license. That kind of license went off the market at the end of 2014, when Stromasys transitioned to an all-proof of concept licensing and sales plan. The PoC strategy has yielded a string of green-lit transitions to the non-3000 hardware. Hobbyist/freeware licenses got abused; free software was caught running in commercial settings. Other people might have failed at their no-cost DIY approach. You don't always get news of failures when you never knew about the attempts.
News travels slowly, especially for managers who are not in everyday contact with MPE and 3000s anymore. Sometimes 3000 news has traveled slowly for reasons other than simple oversight, or becoming busy with non-3000 computing.
October 07, 2016
How to Make a Windows to 3000 FTP Move
I need to move a file to our 3000 from a Windows server with FTP and Windows doing the put. The Windows file has longish variable length records, but I would like them converted to fixed length on the 3000. When I tried, this was the result:
PUT C:\Dev\MViewFTP\transdata\AP_HEADER_GW.CSV LMAPGW.IVD;rec=-1024,1,f,ascii,disc=1000;move
200 PORT command ok.
550 The FILE EQUATION STRING option (item# 52) is not in a valid file equation form. (FILE OPEN ERROR -449)
Keven Miller replies
Item #52 refers to HPFOPEN. From the intrinsic manual
52 File equation string:
Passes a character string that matches the file equation specification syntax exactly. (Refer to the FILE command in the MPE/iX Command Reference Manual.) This option allows the specification of options available in the FILE command.
I don't like the trailing ";move" in your command string. I'd remove that. Also, you have comma after "ascii" and it should be a semicolon, like this
October 05, 2016
How to fail at mission-critical IT with 3000s
We recently tried to be helpful for a 3000 manager who was desperate to get an MPE/iX server back online in steady, reliable service. Our role was just to feed questions to the volunteer force of experts on 3000-L and then pass back answers to the manager. The experience led us to think about what any company should do to fail at using a 3000 for mission-critical service.
Be assured, following these helpful hints will ensure your 3000 cannot do its work.
- Do your support with someone who'll just help out from time to time. Save your support budget for your other servers that are mission-critical. Let the 3000 fend off errors with volunteer help.
- Let your inventory of spares of the 3000's moving parts take care of themselves. A power supply or a hot-spare CPU board takes up a lot of room; set aside space for more modern computer components. Someone will be able to find something soon enough when trouble comes up.
- When a software or network problem starts to occur, give the situation awhile to work itself out for a few months. Save your support budget for the time when things are crashing because they've gotten serious.
- When your support vendor bills you on your 3000, let that expense take the same place as less-critical services. This isn't a vaccine, after all. It's just support for mission-critical servers.
- Make it clear to your management you're saving money by using the 3000 in a mission-critical role. Reinforce the cost-effective nature of the use of MPE/iX by keeping the software on 15-year-old HP hardware.
- If No. 6 might raise attention you're using MPE/iX, keep the age and support matters internal to datacenter planning. A 9x9 with no support provider is a fine way to ensure the future.
October 03, 2016
Emulation customers got all they wanted
Five years ago this week Stromasys was doing a full technical detail demonstration of its PA-RISC emulation software. Since then, such virtualization has become an everyday choice for interim homesteading (just a few years of use needed) or long-term plans, too.
The software got its debut in front of a sophisticated crowd: HP 3000 veterans at that year's HP 3000 Reunion. In 2011 skeptics were schooled and devotees bowled over.
The rap on emulator choices from out of the past was performance. That's gone away by now, because moving an environment to a quick-growing OS like Ubuntu Linux -- the foundation for the emulator -- gives MPE an accelerating train of processor improvements to leap onto. Itanium won't leap like Intel's Xeon chips will over the year to come with Skylake. Here's a surprise nobody saw coming: the ultimate Itanium chip, Kittson, began development in 2011, and it's still not running in HP's servers. To think, MPE/iX could've had that fate if HP had chosen to port the OS to that chipset.
HP 3000 hardware and MPE experts at the Reunion believed in Charon's emulation future. In 2011 there were more in attendance at the Reunion than could fit in a single-family home. What's still in the years to come is making a home for MANMAN on one Ubuntu-Charon partition of a big Skylake Intel server, and MANMAN's replacement Kenandy on another.
September 30, 2016
Earliest birds to eye Charon stick with 3000s
One week ago the 3000 Simulator Project rolled out a new version of software to simulate an MPE V Classic 3000. That news led to a look at the modern emulation product Charon HPA and what has helped make it a success. Diligent engineering and testing of the Stromasys product across the community started just about five years ago. One of the earliest vendors to green-light their software for emulation was a company who's still selling new customers on MPE software: Minisoft.
Founder Doug Greenup called last month to report on some new sales into your market, the one which established his company. He mentioned Minisoft's connection to See's Candies' HP 3000s. See's is using Minisoft's middleware, and the connection between emulation and Minisoft popped up when I found Greenup's earliest report on testing against Charon. Minisoft was the first third party company to announce their products were Charon-ready, including ODBC, JDBC, and OLE DB products. These were the days when PA-RISC emulation was as new as Clarence Birdseye's frozen food was in the 1940s. Greenup's report was so early in the Charon HPA lifespan that the Stromasys software was being helped into the market by independent consultants like Craig Lalley.
Craig [Lalley] gave us access to the Stromasys emulator to test some of our legacy MPE products. The HP 3000 terminal emulators under Windows and Macintosh worked fine connecting up via Telnet. We ran some VPLUS screens with no problems. Connections were reliable and fast. We also tested our middleware drivers, connecting and running queries.
The bottom line is our products worked like they were interacting with an HP 3000. So if any of our customers deploy Stromasys, we are confident our MPE products will work.
Charon HPA needed software vendors who were familiar to the 3000 community to step up and certify. It's satisfying to see that one of the earliest adopters of your market's emulator is still selling software to MPE/iX sites. We'd call those sites 3000 customers, but its possible the HP hardware has been replaced by Charon HPA. Which is precisely why it was good business to step up and demonstrate that the emulator worked just like an HP 3000. Works better, now that HPA is not five years older like those boxes with "HP" on the front.
There's your report. MPE/iX still running at high-profile candy manufacturer. New 3000 software still being sold in a few places. Stromasys now moving toward five years of support from the MPE third party vendors, support that started with Minisoft.
September 28, 2016
Meeting at Building D: the rarest 3000 link-up
Notices were posted this week on the 3000-L mailing list about a rare meeting next Monday, Oct. 3. At opening time 11:30, people who know and remember the 3000 will gather at The Duke of Edinburgh pub. It's a site popular enough with the MPE crowd that it's still called Building D by some seasoned community members. The Duke is on Wolfe Road, just to the west of where the 3000 grew up. As the 3000 group intends to arrive at opening time, it might be able to commandeer the snug (above).
In-person meetings for the 3000 community happen in bars and pubs by now. The last one we heard about this public was SIG-BAR's meeting in London in 2014. Dave Wiseman, a vendor and software maven whose history includes a software project called Millware for 3000s, set up SIG-BAR. The 2014 meeting was announced so far in advance that people were able to plan their summer vacations around a gathering at Dirty Dick's. There's something about English pubs that attracts the 3000 crowd.
The Duke of Edinburgh is within walking distance of a mecca of the 3000 world, now departed: The HP Cupertino campus. Building 48 has been replaced by the rising concrete and steel of the new Apple world headquarters building. There's no word yet if the 3000 friends who meet Monday at Building D will bring their drones to take their tour of the Apple-ized HP campus.
A walk through the HP parking lot and across a cozy margin of poplars used to bring you to the Duke. "It's right across the street from where MPE lived," said Stan Sieler of Allegro while announcing the meeting. As of Monday, MPE's heart will be among the taps and chips of The Duke. Two years ago, Robelle's Bob Green said this about the last in-person meeting at that London pub:
We exchanged notes on the current state of the machine—especially the new emulator—- and discovered what each of us was doing. An amazing number of people are still doing the same thing: helping customers with their IT concerns. But in reality, most of the time was spent swapping war stories from the past, which was great fun.
As for that emulator, Charon HPA is in full swing by now, a certainty of life going forward with MPE/iX systems. For one additional lunchtime, a pub will be emulating the home of the system, even as it continues to move into a virtual existence.
September 26, 2016
3000-L connects again after a silence
As if on cue after our report about its silence, the 3000-L mailing list and newsgroup sprang back to life over the weekend. One problem solved by the 415 readers was how to identify if a store to disk backup is a LZW compressed backup file. A Tracy Johnson report also confirmed that a LISTF,2 can report the time of each LISTF, by writing a specialized job.
Meanwhile, a 15-year-old HP 3000 with network connection troubles got advice from the newsgroup's readers. A Series 969 running MPE/iX 6.0 would not be the first thing you'd choose for interfacing to an internal website. But when a 3000 has data that a user needs over the Web, the server is the place to go.
Trouble started to surface when clients access a webpage which then opens a telnet session with the 3000, grabs the info, and then returns the data to the webpage.
We’ve been getting more and more errors over the last year, culminating in non-stop Could not initialize data in path with TCP, which then blocked anyone accessing us through our webserver. We’ve tried many changes but cannot seem to get past this.
When it locks up, the HP 3000 keeps running but won’t accept any new sessions. Which means our clients can’t run searches. Which is very bad for us. Sometimes we can stopnet and startnet and it will work for a while, but then the errors start again. Eventually, we have to coolstart to be able to have clients log in.
September 23, 2016
Simulator for Classic 3000 gets third release
A third release of an HP 3000 Series III simulator is now available from the Computer History Simulation Project website. J. David Bryan of the project reports the software which simulates the old MPE V HP 3000 Series III now has a cold dump facility.
Entering the DUMP command simulates pressing the ENABLE and DUMP front panel buttons. The contents of main memory are written to an attached magnetic tape in a format suitable for analyzing with the DPAN4 program provided with MPE. The new SET CPU DUMPDEV and SET CPU DUMPCTL options specify the default device number and control byte for the dump.
Known as the SIMH project, the software is aimed at hobbyists who are using MPE V programs and utilities. Even though a power failure is not a desired event, the simulator has a capability of creating one. This is in addition to yanking the plug out of the laptop or PC running the simulator software.
September 21, 2016
Power outage, or no problems? It's been quiet on the 3000-L. "Yeah, too quiet."
In the classic war movies, or a good western with Indian battles, there's the moment when someone notices the silence on the field. "It's quiet out there, Sarge," says the more innocent hero. "Yeah, too quiet," the non-com replies. That kind of quiet might be the sound we're hearing from the 3000-L mailing list today.
It's been five weeks without a new message on the mailing list and newsgroup devoted to MPE and its servers. Advice and solutions has flowed for two decades and more off a mailing list that still has 498 members subscribed. The number of subscribers has remained steady over the last three years. Like the number of migrations in the market, the exit from the list has slowed to a trickle. So has new traffic, of late.
The silence may not be ominous. In 2016 the 3000-L is used almost exclusively to resolve MPE/iX problems. The hardware posts are limited to the rare announcement of used server prices, messages that the members still howl at if they don't include <PLUG> in the subject. The server hasn't been sold by HP in more than a decade, but its owners still don't like to be bugged by sales messages. They solve problems in a grassroots manner. As a notable ballplayer once said, you can look it up. There might be no problems to solve.
However, no messages at all over 35 days sets a new record for the 3000-L quiet. This 3000 resource was much more lively a decade ago. And 20 years back? Well, HP was still selling enough 3000s in the fall of 1996 to be sending its new marketing manager Kathy Fitzgerald to speak at an Indiana RUG meeting about the new servers. There was also advice on storage compression, because compression-enabled DDS drives were becoming more common.
Good advice: If you can find a DDS tape drive from 1996, you should take it out of service. Your MPE server, no. And evergreen advice from the L is still available online. Jeff Kell, the deceased 3000 guru who started the server on a University of Tennessee at Chattanooga server, built it to last.
September 19, 2016
Re-SUSAN services: off-label, or standard
As the 3000 servers age, their components are failing. It may not be a common event yet, but when it happens, getting an HPSUSAN number transferred to new iron has some options. One of the alternatives is a mighty fan to forestall the re-SUSAN processes.
Pivital Solutions' Steve Suraci reports that HP's still servicing 3000 owners who need an older HPSUSAN moved to replacement hardware after a failure. "In our area HP still provides the service to officially update the SUSAN. That's how we'd deal with it, but I'm sure other providers would differ."
When a 3000 manager has no provider anymore, they're likely to look for an off-label solution. In the drug industry, off-label is a use of a drug for which it was not intended. HP never intended to give independent companies the ability to change an HPSUSAN. That's why its tools were protected with a lockword. Then again, HP intended to move MPE/iX to Itanium, and to serve 3000 owners with no end date for support. Everybody knows about intentions can turn out.
Enter Immediate Recovery Solutions. The Bay Area company's history is using software that gives one key HP support capability to owners of 3000s. The Immediate in the company's name refers to intent: To get a 3000 back online, if HPSUSAN is standing in your way, as soon as they can get access to your console,
If that seems rather intimate for a first encounter—saying here's my console on the Internet, and now do your best — then the value of a relationship with an ongoing support provider becomes plain to you. So on the first day a 3000 needs to be replaced, but keep its original HPSUSAN to preserve booting up old vendor software, the choices are three. Call your support company for standard service. Call Immediate Recovery and go all the way on your first date. Or look around for a hefty fan, if you're lucky.
September 14, 2016
Dancing the Samba services tune, MPE/iX-style
Ten years ago this week we were promoting instructions on how to use Samba better on HP 3000s. Samba is "a group of programs that allows a Unix host to act as a fileserver for Windows platforms," according the MPE/iX documentation rolled out in 1999. The file-sharing and printer sharing software which has been a part of MPE/iX since the 6.0 release "allows Unix-like machines to be integrated into a Windows network without installing any additional software on the Windows machines. Many different platforms run Samba successfully; and there are nearly 40 different operating systems which support Samba." And many more now, a decade later.
HP brought features of Samba to the 3000 in a port called Samba/iX. "It is a solution for those wishing to access HP 3000 disk storage and printers (both networked and spooled from MPE/iX) from common PC client operating systems like Windows." Samba/iX allows access to disk and printer resources of MPE/iX by providing standard SMB file and printer services that are accessible from PC clients and their applications. An administration tool called SWAT makes Samba so much easier to use.
Samba 3.0.22 is distributed by the following MPE/iX base patches. Your independent support provider should be able to help you round one of these up. They've got the latest functionality.
- SMBMXY6D (BT) for MPE/iX 6.5
- SMBMXY6E (BT) for MPE/iX 7.0
- SMBMXY6F (BT) for MPE/iX 7.5
The (BT) stands for Beta Test. HP never cut the 3.0.22 version loose as a general release (GR) version. For reference, the following are GR versions with less functionality.
- SMBMXG3A (GR) for MPE/iX 6.5
- SMBMXG3B (GR) for MPE/iX 7.0
- SMBMXG3C (GR) for MPE/iX 7.5
Even a total 3000 network newbie can get Samba up and running. Samba must be running before you can run SWAT. Here's some useful info when getting SWAT going.
In SERVICES.NET you'll want a line that reads:
swat 901/tcp # Samba/iX Web Admin Tool
In INETDCNF.NET you'll want:
swat stream tcp nowait MANAGER.SYS /usr/local/samba/SWAT swat
(adjust the path to your SWAT NMPRG)
September 12, 2016
HP sells software business to boring buyer
Micro Focus, which has already bought Attachmate (nee WRQ) and Acucorp (maker of a COBOL that was once fine-tuned for the 3000) is now sitting on what HP was selling that Hewlett-Packard Enterprise calls software. Like Autonomy, for example. The latter is probably valued at one-tenth what the-CEO Leo Apotheker's HP board paid for it five years ago. Admiral Grace Hopper's invention has ultimately provided a harbor for HP's exit from the software sector. The buyer builds COBOL.
The entire transaction only costs Micro Focus -- makers of boring software that drives thousands of businesses -- $8.8 billion on paper. HP's is cashing out of software for application delivery management, big data, enterprise security, information management and governance, and IT operations management. With Autonomy in the deal, the company HP purchased for $11 billion in 2011, HPE gets an albatross off its back.
Here's one shakeout: Minisoft is now the only vendor selling 3000-ready terminal emulation that remains under the same vendor brand. WRQ has been absorbed, and HP's out of the terminal business they started with AdvanceLink in the 1980s. (Minisoft's still selling connectivity software to MPE/iX users, too — as in active sales, this year.) HP sells almost zero 3000 software today.
A Reuters report says the HPE move tilts its business mix hard towards hardware, with two-thirds of what's left at HP Enterprise now devoted to a sector with slim margins. HP has stopped much of its operating system development over the last 15 years, casting off OpenVMS and MPE/iX, then stalling HP-UX short of a transformation to Intel-ready software. Instead, MPE/iX got its Intel introduction post-HP, when Stromasys made its Charon HPA the gateway to x86.
NonStop remains a part of to HP's enterprise group and enjoys development, but it's tied to Itanium chips. Nothing left in the Business Critical Systems group -- HP-UX, VMS, NonStop -- gets any love anymore during HP's analyst briefings.
HP software, aside from operating systems, could provide a frustrating experience for 3000 customers. Transact and Allbase were strategic, until they were not. IMAGE got removed from the 3000-bundled status it enjoyed. HP had to farm out its ODBC lab work to keep up during the 1990s.
The deal between HP and Micro Focus gets more unusual when you see that HPE has to pay Micro Focus $2.5 billion in cash. In exchange, HPE shareholders will own 50.1 percent of Micro Focus. HPE wanted to get its software out of its enterprise business and into the hands of a company with business success in software. Micro Focus built its rep on embracing backbone technology like mainframe connectivity and COBOL.
September 07, 2016
HP remains in HPSUSAN update business
Close to 15 years has elapsed since HP chose to step away from the 3000 business. However, the vendor is still serving the needs of any customers who require an HPSUSAN ID to be refreshed onto replacement 3000 hardware.
We looked at this situation several weeks ago. For a customer who's looking over a move away from HP's 3000 hardware — but wants to remain on MPE/iX — Charon HPA from Stromasys is the logical choice. Going with a virtualized PA-RISC box can help sidestep a complication while staying with MPE. Replacement hardware will need either a refresh from a software vendor to accommodate the change in HPSUSAN. Or, in an extreme case, the HPSUSAN of record from the retired hardware would need to be flashed onto the permanent storage of the 3000.
Steve Suraci of Pivital Solutions, a comprehensive 3000 support practice focusing on MPE/iX, gave us an update on the ways to move an HPSUSAN. "In our area, HP will still provide the service to "officially" update the HPSUSAN," he said. "That's how we would deal with it, but I'm sure some other providers would differ."
September 05, 2016
Labor of homesteading lifted by advice
Today in the US we celebrate Labor Day, a tribute to the respect that workers earned during the labor movement of the 20th Century. Many offices are closed including most states' offices. Here in Texas organized labor works in the shadows cast by a business-sotted political engine. Nobody needed a labor movement and its human rights back when the 20th Century started, according to the politicians controlling those times. Mother Jones and other heroes who were radicals got the 11-year-olds out of the coal mines of West Virginia, as a start. Machine guns were employed by the powers in charge to oppose that movement. You can look it up.
Homesteading customers face labors too, and they have long struggled for respect. Their work is no less important than the heavy lifting of migration was. Migrations have tapered way back. It's easy to say there are now more companies working to keep 3000s in production than companies working to get off the platform.
If you are lucky enough to have a holiday today, thank your precursors in the labor unions. For a good look at what labors a homesteader should work on, here's Paul Edwards' homesteading primer from 2004. Homesteading tasks are little-changed by this year, with one exception. All customers have moved the labor of their 3000 support to third parties. The Web resources listed in Edwards' primer are much-changed, however, with a few exceptions.
September 02, 2016
Open launch has become a workaround tool
Fifteen years ago this week I put the finishing touches on a Q&A with Jon Backus. He might be best known to one group of 3000 managers who flagged down his taxi-like service of MPE education — his Tech University had independent experts whocarried people from one point in their MPE careers to the next, better trained. An MPECert program was part of the venture that went into business just before HP changed its mind about continuing with 3000s. Tech University offered an alternative to Hewlett-Packard training classes, vendor-led education that was on the decline in 2001.
However, there's another milestone in his career just as well known. He launched OpenMPE as 2002 began, starting with a conversation with then-lab manager Dave Wilde. On the strength of that talk, the advocacy movement ultimately delivered MPE source code to third parties. It did take another eight years, but hopes were high at the start. HP named a key lab engineer to a board of directors. Minisoft donated middleware and MPE software from some of its licensed 3000s.
Backus began it all when he launched a discussion group on the Internet to explore the ways MPE might be preserved by its customers after HP steps away from it in a few years: a homesteading option. The group moved quickly to a consensus that open source methods didn’t fit MPE very well.
“The feeling and desire is very much not open source,” Backus said at the time. “The vast majority feeling is a migration of support and control of the entire MPE environment, including IMAGE, to a new entity. The source would continue to be closely controlled, similar to the way it is today.”
Starting a education group for HP server customers was a bold move. We interviewed him as one of the last 3000 experts to sit for a Q&A before HP's November 2001 exit announcement. August 2001's HP World was the last show to offer any HP hope for the server. Without OpenMPE and its work to capture that source code, however, to independent support companies such as Pivital Solutions, the trade secrets of MPE/iX would be lost. Instead that source acts as workaround and custom patch bedrock to help homesteaders.
Source for MPE/iX was not the initial goal Backus proposed for OpenMPE, though. The whole of the 3000 business would pass to a third party in his opening gambit. HP took months to even respond to that, saying the computer's infrastructure was decaying. Tech University was already addressing the brain drain before OpenMPE was born.
August 31, 2016
What To Do To Succeed In Migrations
In the 3000 community a major manufacturer is making its way off its ERP system. It will take years. We've been told not to say who, but the more important element of this story is the what. As in, what not to do to make a clean move away from applications that drive finances and manufacturing.
It's been a struggle, but mostly due to poor project planning and project management. Migration partners who've served the 3000 community pride themselves on the planning deliverable. Without such good planning, "it's taken significantly longer than they thought it would, primarily because they chose to ignore warnings."
The top IT management refused to perform any business process analysis before beginning the project. Business processes have been traced by MPE/iX applications since the 1980s. The software has been lauded for bending to the needs of processes, instead of the other way around. "They knew what they were doing, and didn't think we understood what it would take to implement new systems in our businesses."
Planning comes at a discount as well as with a price. You get the discount when you plan. You pay the price when you don't. Especially in migrating from a legacy system ERP, where the P stands for Planning.
August 29, 2016
How Good Things Are Slow to Change
Five years ago this week I was debating Apple's place in the future of tablets. The iPad was roaring along with more than 60 percent of the share of tablets shipped at the time. I bought one for my wife a few months later, to help her convalesce following a hip surgery. It was an iPad 2, and it's turned out to be the equivalent of a 9x9 HP 3000. It might run forever.
My debating point in late August of 2011 was Apple would not be chased off its leadership of market share anytime soon. In 2011 nobody offered a tablet featured with apps and an infrastructure like Apple's. I heard the word "slab" to describe tablets for the first time. That label predicted that a tablet could become nothing more special than a PC. White box, commodity, biggest market share will eliminate any out-sold competitors.
The trouble with that thinking is that it's the same thing that drives the accepted wisdom about the future for datacenters still using MPE/iX and the HP 3000. Last Friday I attended a 20th work anniversary lobster boil at The Support Group for Sue Kiezel. She left her datacenter career on MANMAN systems to become a part of Terry Floyd's consulting and support company. All through those years, HP 3000 experience has remained important to her work. There's years ahead, too, years with 3000 replacements -- in their own time. Slowly, usually.
Those 20 years also track with the Newswire's lifespan. It's always a chipper afternoon when I visit the company's HQ out in the Texas oaks near Lake Travis. In addition to things like barbecue and cake -- and last Friday, lobsters large enough to crowd a deep pot--reminders of the success of the 3000 are often laying about. Last week I noticed flyers and documents outlining software from Minisoft. Not all of that software is MPE-centric products, but it is all designed for any company that still makes and ships products using a 3000-driven datacenter. Even if that datacenter is hooking up iMacs to MPE/iX, a specialty Minisoft has come to own completely. The 3000 users who remain in the market believe they have a good thing. Change comes slowly to good things, behavior which mirrors human nature.
August 26, 2016
Expecting the Best, Even During A Disaster
This week marked the onset of cheaper air fares. August 23 was the official day for lower fares to be posted by airlines. A fare between Austin and Bejing -- the country where a dozen HP 3000s are driving a manufacturing corporation's operations — is down to $863.
So the impact of airline companies' failed disaster recoveries will recede. There are fewer people to strand when a system goes dark like the one did at Delta Airlines. The disaster was centered around a single building in the Atlanta power grid. It led to people tweeting “I’ll never fly your airline again.” This is just life in 2016. Get used to it: instant reviews, dashed off in the heat of anger and dismay. Tweets motivate spending millions to do good DR.
But the assumptions are that legacy systems are to blame. "Legacy systems stay on way too long," said one blogger who's had some software experience as well as work at Boeing. "Vendor agreements, support and maintenance — and the pain of switching and upgrading a system that’s by and large pretty reliable and so deeply integrated—are things few CTOs want to touch."
Southwest Airlines had no legacy systems at work during its high-season meltdown. The 3000s had been turned off. The plan was to save money by getting more modern. The disaster recovery was not high on the budget list. Customers don't care about IT budgets. They expect the best, even during a disaster. Plenty of 3000s have come through hell and high water.
That reliability doesn’t come out of thin air. The track record the server built during the advent of ticketless flight operations is one reason it still drives manufacturing in places like China and airports serving See's Candies. Celebrating the days of MPE glory won't return it to those places where DR has failed, though. Turning back only happens when a system fails upon installation. Once you're in, it's hard to turn something away at the gate.