November 10, 2015
HP reaches to futures with outside labs
Hewlett Packard Enterprise, now in its second full week of business, continues to sell its proprietary OS environments: NonStop, HP-UX, and OpenVMS. MPE/iX was on that list 13 Novembers ago. A business decision ended HP's future MPE developments, and the 3000 lab closed about nine years later.
There's another HP OS lab that's powering down, but it's not the development group building fresher Unix for HPE customers. The HP OpenVMS lab is cutting its development chores loose, sending the creation of future versions of the OpenVMS operating system and layered product components to VMS Software, Inc. (VSI). The Bolton, Mass. company rolled out its first OpenVMS version early this summer.
This is the kind of future that the 3000 community wished for all those Novembers ago, once the anger and dismay had cooled. The HP of that year was a different business entity than the HP of 2014, when Hewlett-Packard first announced a collaboration on new versions of OpenVMS.
What's the difference? HP has much more invested in VMS, because of the size of the environment's installed base. Some key VMS talent that once worked for HP has landed at VSI, too. Sue Skonetski, once the Jeff Vance of the DEC world, told the customer base this summer she's delighted to be working at the indie lab. "I get to work with VMS customers, partners and engineers, so I obviously still have the best job in the world," she posted in a Facebook forum.
The 3000 and MPE probably would've gotten a nice transfer of MPE talents to independent development labs. But there was a matter of the size of the business back then. Today, HP's falling back and splitting itself up.
The Hewlett-Packard of 2001 could not imagine a time when its proprietary systems might be supported by independent tech talent. But what ensued with 3000 homesteading may have led to a lesson for HP, one that's being played out with the VSI transfer. Enterprise customers, it turns out, have longer-term business value tied up in proprietary systems. HP will be at the table to support some OpenVMS sites in the future. But they have an indie alternative to send their customers toward, too. When HP's ready to stop supporting Itanium-based VMS, an outside company will take up that business.
Pivital Solutions: Your complete
HP e3000 resource
November 09, 2015
Making 3000 Disk Faster By Virtualizing It
Age is an issue for HP 3000 homesteaders, a challenge that must be met on more than one front. Aging in-house expertise will require a replacement IT professional. That can be tricky to locate in 2015, but one way to approach the task is to train a consultant who's already a trusted resource.
At Conax Technologies, the veteran HP 3000 manager Rick Sahr was heading for retirement, an event that threw the spotlight on the suitability of MANMAN for ERP. Consultant Bob Ammerman stepped in to learn MPE/iX and the 3000's operations. That was a solution that followed an effort to replace MANMAN with another ERP software suite, running under Windows.
The trouble with the replacement application stemmed from its database. Oracle drove that app suite, and Conax and Ammerman were assured that having strong experience in Oracle wasn't a requirement of adopting the replacement app. "I'm a SQL Server guy," Ammerman said. His work to interface MANMAN with Windows helped to preserve the 3000's role. That rescue was the best way forward when the company chose to back away from the new app.
The shift in plans opened the door for the Stromasys Charon HPA emulator. As it turned out, the $100,000 of server and SAN disk purchased for the ERP replacement app was a good fit for virtualizing the 3000. Charon can just about match the CPU performance of the replaced Series 928. The bonus has been what virtualization has done for storage and disk speed. It's erased the other age barrier, the one presented by old disk drives.
November 06, 2015
MANMAN vendor wants to run datacenters
The yearly conference for Infor software customers wrapped up this week, meaning that MANMAN sites have some new dogma to process on the way to migration. Infor has lots of alternatives for these established HP 3000 sites to consider when they migrate. We've talked to one IT manager who said Infor prospective apps have made owning MANMAN and running it on a 3000 less costly.
The future for MANMAN and any legacy ERP app is up in the cloud, according to its CEO Charles Phillips. ERP for the cloud has been the mission Kenandy has pursued for more than three years, but it's good to see the concept has gained traction at a major ERP vendor like Infor.
The Infor president Stephan Scholl said this week (hat-tip to the Diginomica website)
Give us your data center. We will take your mission critical applications and run them on Infor Cloud Suite. So before you do an expensive hardware refresh, we can get you up and running in 4-6 weeks.
Getting a customized application environment working in six weeks or less sounds bold, especially to the MANMAN customer who's fine-tuned software to match business processes over the last 20 years. At Conax Technologies, that's exactly what happened. That well-fitted tuning is also what's holding Conax to MANMAN.
Infor's Phillips is not the only CEO aimed at delivering ERP via offsite hosting. (Sorry, I mean the cloud. A fellow can get confused once the development moves out of a company-run datacenter.) Kenandy's CEO was promoting wholesale ERP change earlier this year, in the weeks before Sandy Kurtzig turned over her job to a handpicked successor.
November 05, 2015
Licensing advice for hardware transitions
Today the CAMUS user group hosted a phone-in meeting, one where the main topic was how to manage licensing issues while changing hardware. Not HP to HP hardware, within the 3000 family. This migration is an aspect of homesteading: moving off the Hewlett-Packard branded 3000 hardware and onto Intel servers. The servers run Stromasys Charon HPA, which runs the applications and software built for MPE.
In-house apps need no such relicense, but everything else demands disclosure. This is a personal mission for companies that want to leave HP hardware behind, but keep their MPE software. In one story we've heard, a manager said the vendor would allow its software to run under Charon. "But you're on your own for support," the vendor told the manager. No-support licenses are the kind that satisfy auditors. In lots of cases, self-support or help from independent companies is better than the level which that sort of vendor offers.
We've talked with three managers who've done this MPE software relicensing, all reporting success. Two of these managers told their stories at today's meeting. Last year we collected the tale of re-licensing from Jeff Elmer, IT manager for Dairylea Cooperative. They left a Series 969 for a PC-based host when old drives in the 969 posed a risk.
He said licensing the software for the Charon emulator solution at Dairylea was some work, with some suppliers more willing to help in the move than others. The $1.7 billion organization covers seven states and uses at least as many third party vendors. “We have a number of third party tools, and we worked with each vendor to make the license transfers,” said Elmer.
“We won’t mention any names, but we will say that some vendors were absolutely wonderful to work with, while others were less so. It’s probably true that anyone well acquainted with the HP 3000 world could make accurate guesses about which vendors fell in which camp.”
Some vendors simply allowed a transfer at low cost or no cost; others gave a significant discount because Dairylea has been a long-time customer paying support fees. ”A couple wanted amounts of money that seemed excessive, but in most cases a little negotiation brought things back within reason,” Elmer said. The process wasn’t any different than traditional HP 3000 upgrades: hardware costs were low, but software fees were significant.
November 04, 2015
HP C-level legacy hubris perplexes women
Now that the Hewlett-Packard spin off is underway — the initial 1970s concept of selling business computing solutions has returned to the fore at Hewlett Packard Enterprise — a review of who steered the bulky HP cart into the ditch seems worth a note. HP engineering culture was targeted by COO Chris Hsu as an impediment to splitting the company up in a year's time. The HP which ran on engineering desires fell to the wayside after current Republican candidate Carly Fiorina mashed up PC business into IT's legacy at HP, including the HP 3000 heritage.
Some insight as well as bafflement is emerging. Meg Whitman, a board director of HP whose primary job is now CEO of the restored HP Enterprise, doubts that Fiorina's best start in political service will be in the White House. According to a report in the San Jose Mercury News
“I think it’s very difficult for your first role in politics to be President of the United States," she said. Whitman has expressed empathy for Fiorina over cutting HP jobs — between the two of them, they’ve slashed tens of thousands of jobs at HP. But the failed California gubernatorial candidate told CNN, “While I think business strengths are important, I also think having worked in government is an important part of the criteria.” Whitman has thrown her support behind New Jersey Gov. Chris Christie.
As a punctuation for that measure of suitability, we stumbled upon another woman with a leadership career. Gloria Steinem, the seminal sparkplug of the feminist revolution of the 1970s and ardent advocate for womens' career ceilings, spoke on The Daily Show this week. Served up a fat pitch by the host that "Carly is a big favorite of yours, right?" Steinem shook her head and smiled. "I’m talking about women who got elected because they represented a popular majority opinion. She got promoted by God-knows-who."
My publisher turned to me and asked, "Who did promote Carly? Do you know?" I wondered how many of our readers, especially those ready to vote in GOP primaries, knew the answer.
November 03, 2015
How a migration vendor planned for change
HP is telling its story of transformation this week, a tale that the vendor says was completed in 391 days. It's the amount of time between the official announcement of the HP split-up to the day when thousands of systems had to be operational with no faults. The fortunes of a pair of Fortune 50 firms were riding on the outcome of turning Hewlett-Packard into HP Inc. and Hewlett-Packard Enterprise.
It was a migration in one aspect: the largest project for internal IT HP has ever taken on. HP's in-house publication, HP Matter, interviewed its COO Chris Hsu about his practices in one of the largest IT change operations in business history. Matter has been renamed HPE Matter, and its article shares some strategic high points.
To develop the highest-level list of how to manage a large-change, high risk project, here's Hsu's items.
1: Determine what the biggest, most critical workstreams are
2. Figure out which ones act as gating items.
3. Get the best people in the company to head up the project; get them full-time, and up and running right away.
4. Make everything else secondary to items 1-3.
5. Get structure, process, governance and people in place.
It takes total management support to make item No. 3 a reality. That same kind of support, one that some HP 3000 sites have enjoyed during migrations, makes No. 4 possible. It all leads to the payoff of No. 5.
"I spent the first month working around the clock, trying to make all of that happen,” Hsu said. “At this scale and this complexity, with the number of interdependencies we were facing, there is no substitute for structure, process and governance. There just isn’t.”
November 02, 2015
HP Enterprise treads out security in opener
In the World Series and on the Sunday US news shows, HP Enterprise put its best step forward with ads. The commercials which aired on US broadcast networks touted image of the new company, rather than its products like ProLiant servers and Linux that have replaced HP 3000s at migrating sites. After the first full trading day on the NY Stock Exchange, investors had bid the HPE stock down by 2 percent. HPQ, the stock for the HP Inc. side of the split, fared better, gaining 13 percent. Together the two entities added $2.5 billion in valuation.
While one day's trading is not enough for a trend, today's investors looked like they believed the higher risk of HP Enterprise plans for next-gen datacenters and security services was a less certain bet than a high-cash, low-risk collection of HP Inc. products. HP Inc.'s sexiest product is its forthcoming 3D printers. The Twitter hashtag #newHPE includes pictures of staffers celebrating day one, including this one above of a friend of the 3000, networking guru James Hofmeister.
The HP Enterprise commercials promised that the company would be "accelerating next." The 30-second spots show a collection of motion-capture video projects, medical imaging, race car design, cargo container logistics, transit mapping, and a gripping clip of an amputee walking on a digital-assisted set of legs.
"A new flexible cloud that harmonizes all operations" refers to the cloud services that remain after the shutdown of the public HP Cloud. An investment of $3 billion in R&D gets touted, perhaps because the risks to be taken to win back business are going to be costly at first. "Because no money is better spent," the copy vows in a 3-minute "HP at 75" online ad. Things are going to be different, this Hewlett Packard says, because everything in IT is changing anyway.
The era of a vendor being essential to holistic customer success is past, however. It's nothing like the HP of 1980, says one of our readers who's still managing a 3000 for fleet vehicle parts tracking. "They thought they could defeat the world by making the world's best PCs and servers," says Tim O'Neill, "but it is a tough market. Systems have largely become unbundled in recent years, but HP seems to think they can first sell services to customers, and then the customer will buy HP hardware on which to run said services."
HP reminds the world it ships a server every six seconds. During the run-time of any of those commercials, five servers left HP shipping. By the accounting from HP's reports, however, four minutes of ads would have to run before a single Integrity server is shipped.
October 30, 2015
The New HP's Opening Day: What to Expect?
The last business day for Hewlett-Packard as we've come to know it has almost ended. By 5 PM Pacific, only the Hawaiian operations will still be able to count on a vast product and service portfolio offered by a $120 billion firm. Monday means new business for two Hewlett-Packards, HP Inc. and Hewlett Packard Enterprise. It's possible that splitting the company in half could improve things by half. Whether that's enough will take months to tell.
On the horizon is a battle with the bulked-up Dell, which will integrate EMC as well as massive share of VMware in the coming months. The Dell of the future will be a $67 billion entity, larger than HP Enterprise in sales. Dell is a private concern now, while HP is becoming two publicly traded entities. The directions could not be more different, but HP will argue that demand had better be high for a monolith selling everything.
Dell is extending its offerings to a new level of complexity, but the level of product strategy and technology to comprehend has become too great for this week's massive HP. Hewlett-Packard never controlled an operation this large until the last decade. The company that built instruments and business computers and printers added a PC empire from Compaq. But it had just spun off Agilent two years before that PC merger.
But then after loading up with billions of dollars of low-margin desktop and laptop lines, the HP of the early 21st Century blazed forward into services. Headcount rose by more than 140,000 when Carly Fiorina sold the concept of buying EDS for outsourcing and professional services. The printer business swelled into cameras and even an iPod knockoff, built by Apple. HP's TVs made their way into retail outlets. It seemed there was nothing HP could not try to sell. Some of the attempts, like the Palm OS-based tablets or smartphones, shouldn't have been attempted. Their technology advantages couldn't be lifted above entrenched competition.
HP's CEOs since lifer Lew Platt retired — Fiorina, Mark Hurd, Leo Apotheker, and now Meg Whitman — didn't have much chance understanding the nature of so many products. Three years ago, HP started in the public cloud business, yet another branch of IT commerce aimed to take market share from Amazon. Whitman said in the New York Times that outsiders like her who've tried to lead the company have had too broad a beam of corporate ship to steer.
"This is crazy — Carly, Mark, Léo, me — the learning curve is too steep, the technology is too complex for an outsider to have to learn it all," she said in a story about what's next. The most audacious of HP's enterprise efforts was The Machine, technology that was to employ the near-mythical memristor to "change the future of computing as we know it." This summer the company fell back and said it would build that product with more conventional components and assemblies. It doesn't have a target date for releasing The Machine.
October 29, 2015
Promises, and a Revolt, from 25 Years Ago
A quarter-century sounds like a long time. In the computer business it's an age, as in ages ago. In marriage it's a milestone, too. In 1990 I took my wife Abby's hand in marriage, a vow we just renewed in our backyard last month with balloons and acres of cake. In that same fall, HP was making promises for the 3000 about the way it wouldn't sell the server — as well as the equality it figured it could give it with Unix servers.
A front-page story in the HP Chronicle called the Boston Interex meeting of that year when we were married "four days that have and will shake our future." Guy Smith wrote for the paper that I edited
At the heart of most of these worries was the fate of Image, and whether HP might re-bundle it with all 3000s. The Image fervor peaked during the rebirth of the SIG-Image on the first evening of the conference. Image co-creator Fred White suggested that users could "sue HP for a couple of million bucks for possible breach of contract." De-bundling led many at the meeting to believe that the venerated network database may be heading for the software scrapyard.
It was an ugly fight that spilled onto the agenda of the HP Management Roundtable, a battle played out in front of the national tech press assembled for the year's biggest HP show. In an editorial, I promised that fights were going to be a vital part of any relationship — even the one I'd just begun with my bride. The reasons for fighting had to be more than proving you're right, though.
October 28, 2015
Compliance rule pipes MPE app to emulator
Racine Water & Wastewater, a municipal utility in Wisconsin, ran an HP 3000 and associated billing applications for decades. The organization even made the shift to final-generation HP hardware with an A-Class server. After the utility shifted IT operations to another platform in 2008, the Hewlett-Packard hardware for MPE/iX chugged along in archival mode. But the risk in running on drives more than a decade old grew serious. The organization that serves 100,000 customers in the communities around Lake Michigan reached out to an emulation platform from Stromasys to keep its archives vital.
The utility needed to maintain a legacy system in order to access archived data. After they had migrated their primary billing system to a newer system, only four years of archived data could be migrated to the new environment. More than 25 years of records remained on the HP 3000. By 2014, they knew they needed a solution to continue to access billing records stored on the HP 3000.
The State of Wisconsin mandates access to billing history records. To meet those compliance needs, the utility engaged with an independent consultant to research archival solutions. Mike York of Assertive Systems in Wisconsin began his due diligence and demo testing. Charon HPA came in for review, and while retrieving that A-Class server's HPSUSAN number, the HP hardware suffered a disk failure. Stromasys was able to help recover the system, even before the utility had adopted the Charon emulator.
October 27, 2015
Data migration taxes migration time budgets
It can take months to move data from one platform to another. Just ask Bradley Rish, who as part of the Potpourri Group managed a two-step process to migrate away from Ecometry software on an N-Class HP 3000. Potpourri first went to Ecometry on HP-UX, then a few years later moved away from HP's proprietary environment to Windows. Same application, with each move aimed at a more commodity platform.
But there was nothing commodity about the company's data. Data migration required eight months, more than the IT pros at the company estimated. Rish said that two full-time staffers, working the equivalent of one year each, were need to complete the ultimate migration to Windows.
Migrations of data don't automatically mean there's an exit from the HP 3000. At Potpourri, after a couple of years of research by IT, the exit from the 3000 was based on HP's plans for the computer, not any inability to serve more than 200-plus in-house users, plus process Web transactions. It's a holding company that serves 11 other web and catalog brands. Starting now through the end of 2015, more than half its transactions occur in the final 90 days of each year. Holiday gift season is the freeze-out time for retailer IT changes.
High-transaction installations create some of the largest collections of data. Two staffers working for one year is one approach to leaving an app. For the record, by the second migration, Ecometry still wasn't working as fast as it did on the 3000. But sometimes vendor plans for a server demand a migration. "Ecometry is IO unfriendly under Oracle," said Rish, "but Ecometry is less unfriendly under Windows than HP-UX. It's still not as fast as the 3000."
If the speed of processing takes a hit, at least there's a way to complete a migration quicker. Automation slims down the time required to move data. Some details on how this works, and reports of success in the field, will come from MB Foster on the Wednesday Webinar, starting at 2 PM Eastern Time.
October 26, 2015
Migrating licenses: an individual's mission
Hewlett-Packard's 3000 hardware is getting older, and although it's well-built, 13-year-old drives make for a good migration spark. The move to Stromasys emulators is another sort of migration, shifting MPE onto standard Intel hardware, but what of the application and software licenses? Getting them transferred is a mission for each company migrating away from HP-badged 3000s. So far, we've heard few reports of show-stopper licensing woes.
The first company that's discussed is the owners of the Powerhouse software. While that's not Cognos, or even IBM anymore, its owners are still a company that does not automatically see value in keeping a customer on support. Bob Ammerman didn't negotiate with Unicom when Conax Technologies did its test runs of Stromasys Charon HPA. Another IT group member did the bargaining, and in the end, Conax still runs its Powerhouse Quiz, QTP and even the 4GL. But its license load is lighter.
The arrangement with what people still think of as "Cognos" took a long while, so long that IBM was dragging its feet in correspondence. As a consulting contractor for the company, he said "We were bringing our software packages over one by one, and the dealing started all over when the software was bought by Unicom." In the final arrangement there was an approval issued to transfer licenses, but Conax elected to reduce its user count for its software based on these products.
"We now have a 1-user license at the developer level," Ammerman said. "We've moved away from use of the software, too," although Quiz is still important to Conax. A reduction in reporting is possible because Ammerman wrote a set of SQL stored procedures in VB Net to move data from MANMAN operational databases into SQL Server. That's where some reporting has moved, although some canned Quiz reports still operate at the company.
That mission covered the biggest software tool at the company. There was still the matter of MANMAN to transfer. The dealing with Infor, the current owners of the manufacturing app, was still to come.
October 22, 2015
Back to the Future: The HP 3000, Then
Yesterday was "Back to the Future Day" in much of the world's culture, the day on the time-traveling Delorean's clock when Marty McFly landed in 2015. Steve Cooper of Allegro posted the tribute screen capture above on a Facebook news feed. Yes, it's been more than 30 years since the legendary film's story was unveiled. The weekend of July 4th marked the premeire. Here's a few things that we knew that summer about the HP 3000.
There was a bit of fuss over SQL coming out of the 3000 community. Alfredo Rego used his keynote spot at that spring's SCRUG user conference to call out the creators of the Structured Query Language. After all, IMAGE used structured queries, too. What were keys, anyway — chopped liver? Oracle couldn't see the profit in porting its database to the HP 3000, because as one VP asked me, "You want us to port to a computer that ships with its own database?"
The HP Spectrum Project — the HP Vision Project revamp of the 3000, restarted — was more than two years away from delivering an underpowered Series 930 to launch the 3000's PA-RISC computing. That fundamental tech for MPE/XL, and then MPE/iX, wouldn't start its life on any HP server until 1986, when it would debut on HP-UX. The HP 3000 could boast of two books in 1985: The IMAGE Handbook, and Thoughts and Discourses on HP 3000 Software. Everyone carried the MPE Pocket Guide.
A 404-MB disk drive, the 7933, was a big honking storage device. It was shipping with a flaw in its head manufacture that was going to push thousands of them into a service recall by the end of the year. (In 1992, a dozen of them were put into total recall in Terminator 2, when they were destroyed in the battle with Cyberdyne Systems security forces.)
October 21, 2015
CAMUS to host homestead-migrate meeting
CAMUS, the manufacturing software society that serves ERP users, will host a meeting on November 5 to shed light on a solution to migrate off MANMAN. Or homestead on the application. The 90 minutes covers both prospects for the HP 3000 customer who continues to rely on MANMAN.
Even almost 40 years after its introduction to MPE, MANMAN is still running company operations around the world. Conax has built its business model around it while it makes temperature sensors. What's more, the MANMAN user still has resources like CAMUS and its membership. Board member Terry Floyd of The Support Group says the software is still central to his business.
"We can still say that almost all of our revenue comes from MANMAN, and that's amazing," he said. It can be expected that a support company like his, which specializes in ERP software, could dig in to serve MANMAN sites that operate with the source code as an application resource. The range of releases is wide, and not all of it is running in Native Mode of MPE/iX.
"All MANMAN users have all of the source code," Floyd said. "Most people are on NM, but I have run across a few running ancient versions before Release 6. Release 12 is current, and 8 or 9 is where some of our best customers are. Most MANMAN sites are probably on Release 11."
The ERP site managers, and anyone else running an enterprise server, can call in to the CAMUS meeting at 11 AM Central Standard Time on Thursday, November 5. The conference connection and call-in number will be emailed to anyone who registers with CAMUS board member Terri Glendon Lanza with a call to her at 630.212.4314, or via her email.
October 20, 2015
Patching an HP 3000 with Patch/iX, Stage/iX
Editor's Note: Today a system manager asked for directions on using AUTOPAT on an HP 3000. That's very old school tech even for a classic system like the 3000 (TOH to Alan Yeo for digging out that link). More than 10 years ago, our contributor John Burke detailed the use of the more-modern MPE/iX patch tools.
By John Burke
Even after HP introduced Patch/iX and Stage/iX to MPE/iX, these HP tools were poorly understood and generally under-used. Both are tremendous productivity tools when compared with previous techniques for applying patches to MPE/iX. There's a good reason for using the newer tools. Prior to the introduction of Patch/iX and Stage/iX, system managers did their patching with AUTOPAT, and you had to allow for at least a half-day of downtime. Plus, in relying on tape, you were relying on a notoriously flaky medium where all sorts of things could go wrong and create “the weekend in Hell.”
Patch/iX moves prep time out of downtime, cutting downtime in half because you create the CSLT (or staging area) during production time. Stage/iX reduces downtime to as little as 15-20 minutes by eliminating tape altogether and, furthermore, makes recovery from a bad patches as simple as a reboot.
This article is based upon the Patch Management sessions I presented at three Interex Solutions Symposiums. The complete set of 142 slides (over 100 screen shots) and 20 pages of handouts are downloadable from my website. The complete presentation takes you step-by-step through the application of a PowerPatch using Patch/iX with a CSLT and the application of a downloaded reactive patch using Patch/iX and Stage/iX. Included is an example of using Stage/iX to recover from a bad patch.
Why should you care about Patch Management? Keeping a system running smoothly includes knowing how to efficiently and successfully apply patches to the system. HP supplyed bug fix patches to MPE/iX and its subsystems through 2008, including two PowerPatches a year through 2006. Some patches add functionality to older 3000s. Patch/iX is a tool for managing these patches.
October 19, 2015
Emulator helps DTC-printer shop into 2015
A classic manufacturer of temperature and pressure equipment needed to bring its MPE/iX environment onto current-day hardware. Even though Conax Technologies was still using DTCs like the one at left to link 3000s to terminals, as well as to line-feed printers, the Charon-HPA software helped to lift the full MANMAN solution onto a virtualized HP 3000 environment.
Like many of Charon's customers, Conax was working with aging Hewlett-Packard hardware. A Series 928 was linked to user terminals as well as printers over a DTC network. The Datacommunications and Terminal Controller was a hardware device, configured as a node on a LAN, to enable asynchronous devices to communicate to Series 900s. Terminals were directly connected to DTCs, and at Conex, printers as well.
"The printers were our biggest challenge," said Bob Ammerman, the IT consultant who oversees the MPE/iX operations at the company. "We had wires running to desks, we had DTCs. Some of the PCs were using QCTerm." About 40 users access MANMAN at peak times at the company's operations in New York State.
Those printers were a significant element in the multi-part form heritage of the company. After the implementation of Charon was completed, MANMAN "thinks it's still printing to the dot-matrix devices, but we've upgraded them to laser printers," Ammerman said. The emulator project included license transfers of Cognos PowerHouse products, the 60-user MANMAN license, as well as middleware from MB Foster and others. Conax took the responsibility for arranging each transfer.
October 16, 2015
VMS follows the journey of MPE onto Linux
Migration lies in the road that HP's enterprise platforms must follow, especially if they have no hardware future beyond Hewlett-Packard's systems. AlphaServers never were part of MPE's path. Alpha was built to power VMS, and then it was acquired along with Compaq's other enterprise products. HP cut down its AlphaSystem futures in 2008, then last year announced that the VMS operating system was going into a sunset at Hewlett-Packard.
Although an independent company has acquired the rights to sell and develop VMS, HP's announcement — like the one the vendor made about MPE — has had a chilling effect on the VMS community. The customers have started to take their systems and applications to another platform. Like MPE's migrations, the way forward leads to Linux.
A couple of MPE veteran consultant-developers have checked in to report on the VMS-to-Linux work they're doing. Moving to Linux makes good sense because it loosens the hold of operating system futures. When something like a VMS or an MPE loses the faith if its vendor, migration becomes more compelling. Linux is not tied to a single vendor, and the OS is not proprietary on the operational level like HP-UX or IBM's AIX. If a SUSE or a RedHat Linux distro has its futures dashed, other Linux providers can be swapped in. Unix promised this but rarely could deliver; its vendor implementations were just too proprietary.
MPE migrations have provided experience that the MPE consultants are using in a fresh community. Many things seem the same to consultant Denys Beauchemin.
The VMS group reminds me a lot of the MPE group," he said, "just bigger and even more vociferous, but now all old and grey. The OS is excellent, and in some respects better than MPE, but in others less so." The similarity of the OS objectives has made migrations a bit easier to execute, he added.
October 15, 2015
After 20 years, NewsWire recalls its first Fall
I was hunting for something new last week when I heard an old, familiar message. "I can't believe you guys are still in business," the 3000 systems manager said. We can't believe it either. But these 20 years have rolled along because of beliefs — ours, yours, and even HP's for a time.
The start of that time was 20 years ago today. Tomorrow we head into our 21st year, but in 1995 our Day One was the middle of October, the month that we printed on the cover of our first issue. This Fall will be the first one since the middle '90s with no printed 3000 NewsWire. We loved printing all of that paper, millions of pages of it. Ten years of it made this rich picture and story. But we said this spring we'd make a transformation to all-digital. We've kept our promise because sponsors have kept our little beacon lit. They've permitted us to continue to show the way forward, as well as look back to find lessons from our past.
Along the way we've found more than 150 companies who invested in our readers. This was always a very personal business; we operate out of a roomy ranch house in a Texas neighborhood. Although there's a very official database of every ad and sponsor payment during these two decades, this hand-written list of who joined us, along with their account number, tells the story of building a business of specialized news, instruction, and gossip. None of it would be possible without the sponsors' dollars: sometimes as advertising, sometimes as patronage. We sold subscriptions, but the sponsors kept us in business.
I'm grateful beyond words for the livelihood and career they've supported. I've even more grateful that my partner Abby Lentz, who started as publisher using her given first name Dottie, proposed this journey that enters its third decade tomorrow. There was a time when the HP 3000 changed its name to the e3000, and I wondered whether the change was like my partner's names. The old one was Dottie, the newer one was Abby. Her yoga name, she told me, and I liked the way she was looking to a new facet of her life. We're looking forward to what remains of lucky lives, teaching and writing, yoga and stories.
The 3000's creators were looking forward too, as we began the NewsWire's life. In fact, HP was a big reason that we're celebrating 20 years today.
October 14, 2015
Data links make hardware migration possible
A one-system HP 3000 shop in Buffalo, NY brought its MPE-hosting hardware into the new era using the Stromasys emulator. The migration from HP's 3000 hardware to Dell servers was made possible by the use of an ODBC connection favorite, UDALink.
Bob Ammerman works at Conax Technologies, supplying his consultant system management and development for the maker of temperature sensors and compression seal fittings. The company has replaced its Series 928 with the Charon virtualized server, but a more modern interface to the historical data was an essential piece of the new solution, too.
"It wouldn't have been possible without the MB Foster software," Ammerman said of UDALink. The newest version of what began as ODBCLink in the 1990s has been keeping the company's data available for pivot tables in spreadsheets and much more. The software vendor of UDALink is hosting an MB Foster Cares class to launch a new webinar series tomorrow at 2 PM EDT. Cloud use of the software is on the agenda, as is distributed processing.
The manufacturing data at Conax goes back to the period when UDALink was ODBCLink. Keeping it all available meant reducing the need for the classic Cognos tools, according to the manager there. But some crucial programming by Ammerman kept those ODBC hooks vital. The idea was to bring history into the present day.
October 13, 2015
Don't let your data become a Forgotten Man
"It's the most forgotten piece of the migration puzzle," said Birket Foster while he led a webinar on best experiences with 3000 transitions. "People are not always remembering that at the end of the day they want to shut off the old 3000."
What Foster meant is that even after removing data -- the most essential 3000 and company resource -- project managers need to track what data they must keep to satisfy an auditor. Many companies will still need long-term access to historic data. That's either a 3000 and its services that can be outsourced from a third party, or maybe an emulator virtualization of a 3000. Some audits demand that the original 3000 hardware be available, however -- not an Intel-based PC doing a letter-perfect hardware emulation using Charon.
After the Great War ended, the returning soldiers were not welcomed as productive citizens ready to return to work. This kind of veteran was called The Forgotten Man, from Golddiggers of 1933. Some information in aging 3000s is marching in the same kind of veteran's step.
Managers have to consider if they want to move their forgotten 3000 data after a migration, or leave it in a searchable format -- several questions to consider for an auditor's satisfaction. Many 3000 sites we've interviewed have a 3000 running for historical lookups. This is the sort of resource that would meet the needs of an audit.
October 12, 2015
Making Room for a 3000's Historic Data
One promise from migration projects is the brightening of skies through better user experiences. The futures get bright when they're reflected in new features, better interfaces and user experiences, faster performance and more complete connectivity.
However, some 3000 sites have discovered that while their futures look brighter on the way to a migration, their pasts fall in a dim light. In one example, a manufacturer in New York was on the way to replacing MANMAN with newer ERP software.
There was a problem, and it lay in the reams of history the company had amassed after two-plus decades of creating temperature sensors and sealed fittings. The new ERP target application couldn't reach into the history of MANMAN transactions. This kind of need can spring up so innocently you don't see it coming. A C-level exec, or just a VP, wants a report to include history back to 2010. The new ERP package will track everything that's current, but history is another matter.
It's the kind of requirement that's keeping HP 3000s running the world over. Rigorous analysis demands looking back, in order to project the future.
October 09, 2015
Why Good News Can Stay Under Wraps
Life is full of bad news, the kind of events we seem to capture and yet are eager to pass along. There's drama in conflict, of course. The world of MPE and 3000 users has been rife with conflicts, pitting stability and legacy against the promises of modernization: mobile abilities, redundancy, commodity pricing, efficient scalability, and ease of use.
In contrast, making a go of staying with a legacy solution like MPE and the 3000 might be a development that's not often shared. There's the judgement to endure about not responding to change with new strategy. There might also be some clever moves, all upstanding, that make keeping MPE hardware a reality. Sometimes spreading good news starts with letting the light fall on reality.
We've heard a story from an IT manager about his ERP solution, one that is living in an emulated environment. "I want to keep a low profile about this," he said in a conference call. "The less detail they hear about me, the better I like it."
What's at stake there is keeping an operating budget in good order. Move to an emulator and you'll have to talk about licenses and what they're worth in 2015. But if you emulate a Series 900 with software that's got the same horsepower, what's really the difference? Application suppliers have their ideals about what an upgrade adds up to, while utility and middleware companies are sharper dealers. By sharp we mean smart. They want to keep a customer, regardless of their MPE platform.
Managing the transfer of MPE licenses to the emulator is of great interest to the legacy application community. In the first week of November, the CAMUS user group will have a meeting designed to learn about licensing, if anybody can share their experiences. Terri Lanza wants to hear from ERP sites who've moved licenses onto Charon. The conference call takes place on Thursday, November 5.
October 08, 2015
TBT: When Spectrum's Debut Missed Its Cue
Few Interex conferences ever convened in October. When the Detroit meeting of 1986 marked its high point, September was already in the year's rear-view mirror. It was a late meeting in the 3000's calendar. Late turned out to be a theme for the meeting's tech papers, because the Spectrum project for MPE was more than a year behind schedule.
By October 1986, the HP Series 930 was supposed to be churning bits using the new PA-RISC architecture and running MPE/XL. The latter was the successor to MPE V, while the former was the first 3000 to leap past Complex Instruction Set Computing. RISC had already succeeded CISC on the HP 9000 side of the server line. But moving MPE while maintaining application compatibility, as well as acceptable performance, was providing unscheduled downtime for the newest HP 3000s. "Where's our Spectrum?" was the cry of dismay from performance-bound big shops.
Detroit's conference proceedings were dotted with accepted HP papers that couldn't be written or submitted. Guidelines on Migration Solutions for MPE/XL, Organization and Direction for MPE/XL, Migrating to the Series 900s as Variables Affect System Performance, an overall Commercial Spectrum Progress Report — all were listed in the two-volume proceedings' index, but each bore a cover page that said "We regret that this paper was not received for inclusion in these proceedings."
The customers had been looking at tomorrows for much of 1985, since Spectrum was the engineering project which replaced HP's Vision effort in 1984. CISC and its memory constraints were holding back large-scale DP, as computing was called then. But like the first version of MPE and the initial 3000s, the stability and performance of the new generation 3000s was not ready for release. Some of the challenges came from testing's optimistic reports.
October 07, 2015
Reloading, Redux: How To
It used to be the worst thing that could happen to an HP 3000 was a reload of its data. Adager gained its central place in the 3000 manager's toolbox because it would prevent the need for a reload after database restructuring. Although the worst thing to happen to today's 3000 is the loss of an expert to keep it healthy and sustained, reloads are still a significant event.
Not very long ago, a 3000 manager was looking for a refresher on how to do a system reload. Ernie Newton explained why he needed one and shared what he knew. Advice about adding the DIRECTORY parameter, and using BULDJOB1 to set up the accounting structure, followed when Ernie said
We suffered a double drive failure on our Raid 5 disk array yesterday and I'm thinking that I may have to do a reload. It's been almost 15 years since I've done one. If I recall, I do a load when bringing the system up, then do a restore @.@.@.
Our resident management expert Gilles Schipper provided detailed instruction on doing a reload. We hope it's another 15 years for Ernie until he's got to do this again.
Here are the instructions, assuming your backup includes the ;directory option, as well as the SLT:
1. Boot from alternate path and choose INSTALL (assuming alternate path is your tape drive)
2. After INSTALL completes, boot from primary path and perform START NORECOVERY.
3. Use VOLUTIL to add ldev 2 to MPEXL_SYSTEM_VOLUME_SET.
4. Restore directory from backup (:restore *t;;directory)
5. openq lp
6. Perform a full restore with the following commands
7.Perform START NORECOVERY
Read "Reloading, Redux: How To" in full
October 06, 2015
Essential Skills: Securing Wireless Printing
Editor's Note: HP 3000 managers do many jobs, work that often extends outside the MPE realm. In Essential Skills, we cover the non-3000 skillset for such multi-talented MPE experts.
By Steve Hardwick, CISSP
When you do a security scan of your site, do you consider your printers? It was enough, several years ago, to limit an audit to personal computing devices, servers and routers. But then the era of wireless printing arrived. Printers have become Internet appliances. These now need your security attention, considering some of the risks with printers. But you can protect your appliances just like you're securing your PCs and servers.
Wireless printers can be very easy to set up. They come preconfigured to connect easily, and even a novice user can have something up and running in a matter of minutes. To be able to make this connection simple, however, vendors keep the amount of wireless network configuration to a minimum. Taking the default settings, as always, significantly reduces the amount of security that is applied to the device.
Modern printers are actually computer platforms that have been designed to run printing functions. Inside are a CPU, hard drive, RAM and operating system components. Unfortunately, a system breach can permit these components to be re-purposed to do other things. And those are things you don't want to happen at your site.
October 05, 2015
Pursuing Crowd-funding for an MPE Port
Open source software once provided a turbo-boost to the renaissance of the HP 3000 and MPE/iX. For one manager, the concept still holds some promise to improve his 3000's offering.
"Does anyone have a newer port of Apache and SSL for the HP 3000?" Frank Gribbin asked last month. "If not, I know a reliable vendor who can do the port. Anyone interested in crowd-funding the effort?"
Gribbin has long been on the trailblazing path with the 3000. His company was among the first to put Java/iX to work in its production software. At the law firm Potter Anderson LLP, he's done development as a part of testing the Charon emulator, too.
"Our 3000s are still useful and humming along," he said. "I haven't done anything in Java for awhile. But I've been having a lot of success using the Apache CGI capability to communicate with BASIC programs that access IMAGE databases."
BASIC. Still working in a 3000 installation.
"My interest in Java was to build a better user interface for 3000 apps," he said. "I thought that was one reason the 3000 was losing market share. Once I figured out CGI scripting and a web interface, I put my effort into that. On our 3000, most of the time, BASIC got the job done. I've written supplemental code in FORTRAN, SPL, Java and Visual Basic, too."
October 02, 2015
3000 Masters make the most of ERP access
The MPE/iX servers which service manufacturing users still have feature-growth opportunity. That's the chance to improve usability, an opportunity often presented by third-party add-on software. A few of the 3000 masters met last month to integrate that sort of software. They were widely-known, recognized for advocating MPE computing, or sharing deep ERP background to make a 3000 work smarter and more securely.
Eugene Volokh, Terry Simpkins, and Ali Sadat came together for an afternoon in LA, hunched over laptops and connecting three MPE-savvy software programs. (Of course, Eugene's dad Vladimir couldn't help but look over his son's work.) At the heart of the equation was MANMAN, still in use at Measurement Specialties' 10 HP 3000 sites, running manufacturing and ERP in China and elsewhere. That remains Simpkins' mission. He's also stood up for homesteading, or choosing HP 3000s, ever since the middle '90s. His company was acquired last year by TE Connectivity, a process that sometimes shakes out legacy software and systems. Not this time.
Helping Simpkins was Vesoft's Eugene Volokh, co-creator of Security/3000. The servers Simpkins' company uses also use the Vesoft product first launched in the 1980s. Eugene was just a teenager when he helped his dad Vladimir build Security/3000. As you can see from the picture above, one of the most famous members of the 3000 community has gotten older — as have we all.
The summit of these masters was topped up by Ali Sadat (foreground, above), whose Visual Basic user interface runs in front of MANMAN at Simpkins' sites. The product which started in 1997 as AdvanceMan does more than just pretty up users' OMAR and MFG screens with buttons and pull-down menus. By now it's an interface to the Web and XML, and it also lets users work in more than one MANMAN module at a time, plus eliminates the typing of commands to execute MANMAN actions. It doesn't require any changes to existing MANMAN environments. For continuity the screens began as ones that were similar in form to the original MANMAN screens. The flexibility and usability is now an opportunity to use an interface for improvements. That's an improvement to an app that was first released in the late '70s. Sadat's Quantum Software calls the product XactMan by now.
October 01, 2015
Throwback: The 3000 World's Forever Era
In the final October that HP was building HP 3000s, the community was still mounting a rally point about the system's future. The Fall of 2003 was presenting the fall of HP's manufacture of MPE/iX servers, although plenty of them would be sold and re-sold in the decade to come. In the waning weeks of that October people wore pins that promised MPE Forever and IMAGE Forever, rebellious chants to shout down HP's 3000 forecast.
The pins were prized at that year's HP World conference in Atlanta. The MPE Forever pin had been re-struck the previous year. The IMAGE Forever pin was harder to locate on caps and polo shirts. Early this week, a 3000 developer and consultant offered one on the 3000-L mailing list. Joe Dolliver reported that it went to the highest bidder, Frank Kelly. "Priceless" was how Dolliver valued the metal stamped as a protest.
As 2003's conference swelled up around the community, the people who supported IMAGE as well as the customers who used MPE's keystone reached out to touch each other's faith during uncertain times. The database, after all, was gaining a consolidated code base so advances like LargeFile datasets would work on some of the oldest PA-RISC systems. It was a more stable and efficient way to handle datasets bigger than 4GB. LargeFile datasets could be dynamically expanded. They were locked up, however, in an MPE release the majority of the customers could not use.
HP was still finding its way to the proper pace for migrations. Some of HP's missing steps were trying the skip the last stands its customers were making on hardware already a decade old.
September 30, 2015
The Re-baking of an Abandoned Classic
About five years after Hewlett-Packard stopped building the 3000, another legend ended its sales. Hydrox, the original sandwich cookie and the snack that Oreo copied and knocked off in 1908, fell off the world's grocery orders in 2008. Sometime tomorrow morning, Hydrox Cookies will arrive at ardent fans' doors and mailboxes.
This resurrection of a beloved cookie has several things in common with MPE systems of the past. At the heart of each revival is a belief that a better-known product is not necessarily better. That, plus a devotion to research that any return to sales demands. Some 3000 owners believed, from 2004 up to the year Hydrox left the market, that HP would return to 3000 sales. By 2010 there were few who retained such hopes — but by that year a better 3000 was already in development.
Like MPE users, Hydrox consumers know their cookie is superior to something better-known: the Oreo. Leaf Brands made tomorrow's return possible by rescuing the Hydrox trademark from disuse by Kellog's. The cereal company was the last firm to make a Hydrox, but by the end the cookies were being baked using high fructose corn syrup instead of genuine sugar. Unlike Oreos, though, the first ingredient in a Hydrox is flour, not sugar.
Hewlett-Packard never tinkered with the composition of MPE/iX or the 3000 hardware at the end of its HP lifespan. But the company has transferred its "HP3000" trademark to a VPN server appliance series. A set of HP inkjet printers called the 3000 has also been on the product list since the last HP 3000 rolled off the line in 2003. HP has not abandoned that trademark, but the server's owners haven't dropped their devotion to the product, either. Like the Hydrox fanatics, some 3000 users look forward to a return of MPE-capable systems.
It's like making a new cookie from an original recipe: new MPE boxes have growth options. And like Hydrox, you purchase them in different ways today.
September 29, 2015
ERP migrations move classics onto clouds
The largest company that's moved its ERP onto the cloud sells pet foods. Pets are one of the fastest-growing industries, and so demand agility and scalability. When Kenandy hosted a webinar today, the $2.3 billion Big Heart Pet Brands was at the top of the company's customer list. But there's also a family-owned sewing machine manufacturer in the Kenandy lineup.
That sounds like a mirror of the 3000 manufacturer community — companies large like Big Heart, a division of the JM Smuckers. And privately-held firms that have devoted followings. Everyone would like to be leaner in the IT department. If your reaction to that statement is "Well, not me," then you might be representing a view that won't sync with company directors and owners.
Cloud ERP promises to take the IT plumbing off a to-do list, but it can't carry business intelligence to outside applications running on web-connected hosts. ERP applications are notorious for being fine-tuned program suites that have been tempered and shaped by decades of insider business practices. From the invoice to the bill of materials practices, ERP touches every aspect of work.
Kenandy's Director of Client Services Rohan Patel dove deep into the particulars of what Kenandy can do to match a migrator's business intelligence. There's a whole new level of functionality in a modern ERP system. Patel mentioned that Kenandy (the name of the product is the same as name of the company, like Adager) can optimize sales order aggregation, "to combine orders to maximize the stuffing with trucks, define transit routes so you can have distance-based decision making -- in terms of if can you fulfill that order so it will arrive on time."
A manufacturer which hopes to sell to Wal-Mart will have to work around a delivery window the retailer sets. There's a fine at America's largest retailer if you deliver late. The next generation of ERP is supposed to give its users the tools to manage this new commerce.
September 28, 2015
Cloud ERP app suite to get demo event
Kenandy will be demonstrating its Cloud ERP suite on Tuesday, September 29 at 10 AM Pacific Time (1 PM Eastern) in a webinar led by Director of Client Services Rohan Patel and Marketing VP Stewart Florsheim. It will be an opportunity to see how the creators of MANMAN have re-imagined the benefits of resource planning software, using the "single source of truth" concepts that are inherent to the cloud.
Registration for the event is at the Kenandy website.
HP 3000 sites which continue to rely on software like MANMAN often don't have a migration target app vendor who understands the nature of MPE-based ERP. Kenandy, launched in 2012 by MANMAN's founder Sandy Kurtzig, has built a comprehensive ERP suite that includes order-to-cash, planning and production, procurement, and global financials, all upon the Salesforce1 platform.
The software promises scalability and agility, which may be important for a 3000 shop that's been acquired by a larger entity. On the other hand, The Support Group's Terry Floyd has said, "We think the latest Kenandy release is capable of handling some of the smaller, simpler MANMAN sites." This seems to be a software set that fits with two ranges of IT enterprise, although its first generation of success leans more toward the smaller than the larger.
September 25, 2015
Taking the Measure of HP's Ex-Leaders
We're waiting for more information about the HP 3000s still doing service by working with Apache CGI scripting, as well as an upcoming confluence of CAMUS advice about Stromasys and Kenandy, to help ERP companies to homestead or migrate. So while we wait let's take a break for Friday Funnies. The story is funny in the way a two-headed calf wants to win a blue ribbon at the fair.
The latest news in our election cycle features the prospects of a woman who impacted lives of many of our readers, as well as the direct fortunes of any who work at or have retired from HP. Or any who will be separated from the vendor soon in the latest layoffs.
That would of course be Carly Fiorina, subject of scorn in both Donald Trump's eyes as well as derision from Yale economics professor Jeffrey Sonnenfeld. The professor wrote this week that Fiorina has learned nothing from her failures, or even admitted she's had any. And so, there's a criticism of his column afloat in the bowl of the 3000 world. Sonnenfeld's talks with former CEOs were not first-hand knowledge, the takeaway read.
Here I offer a subjective summary, and that criticism of the professor goes, "Do not measure Carly's impact on HP -- or her ability to lead -- by how other corporations fared during the same period when she was CEO. Or on the valuation of the company before and after. Measure her by how anybody would have fared, given what she took over starting in 1999. Also, understand that whatever you add up, it will be conjecture."
It's a good word. Conjecture is "an opinion or conclusion formed on the basis of incomplete information." By setting up a measurement problem so there is no constant -- to compare against, say, the veteran insider Ann Livermore, who HP passed over so Carly could get her job -- the measure will always be incomplete, clouded in imagination. In Catholic school, we were usually told at this point of our hard questions, "Well son, it's a mystery."
I believe the only way we'll ever see first-hand Carly-era information is an insider other than Carly who was an HP executive would write a book about the era. Say, Chuck House did that, didn't he? For those who don't know him, he was the leader of HP's software management, and that would include MPE. He was the only winner of what Dave Packard called HP's Medal of Defiance, for extraordinary defiance beyond the normal call of engineering duty. In 2009 House wrote "The HP Phenomenon; Innovation and Business Transformations." House has quite a bit to say about Carly's leadership (lordy, pages 403, 427, 443, 460, 471, 477, 480, 497, and 597) her Compaq decisions.
There's also a sheaf of pages indexed as "Vitriolic reaction." You probably would believe House has some first-hand experience of HP management, given that he was an executive manager throughout her HP service. House wasn't CEO, though. The only CEO who's created a book is Carly. She's so certain of her story she had to write two books.
September 24, 2015
TBT: An End to 3000 Management Verve
Sixteen years ago this month, the HP 3000 community learned it was losing an essential component of the platform: A general manager who'd stuck his neck out for the server's customers. Harry Sterling announced his retirement from Hewlett-Packard and the world of the 3000.
Sterling came into the 3000's wheelhouse from a technical role, moving through product development and into the job of R&D manager for the server. On his watch in the labs, IMAGE gained B-trees for state of the art searches, MPE gained a Posix interface and namespace, and MPE/iX got its first Internet tools and utilities. MPE/iX 4.0, 5.0 and 5.5 were developed in the labs that Sterling managed. When Olivier Helleboid moved up from his GM post in 1996, Sterling was ready to make business distinction for the 3000. He was the first 3000 GM whose roots where wholly in tech.
While Sterling led the division for four years he never lost touch with the customers and their perspective. Even though the overwhelming majority of them worked at small companies, he knew their needs were important to HP. No other leader of HP's management team believed this and acted upon it better than Sterling. Many GMs chose to work for HP, instead serving the vendor's customers. At its worst, that kind of allegiance sparks protests, lost accounts, and untold waste of budget and manpower. Business in computing is hard, but Sterling usually managed to make it look smooth while he kept it personal. He made mistakes, like all of us, but it rarely seemed like the decisions were being made at the customers' expense.
Sterling was one of the best things that ever happened to HP 3000 customers. I can be accused of a clouded assessment because he was a key ally while we established the NewsWire. We never got better access or more cooperation than when he ran the 3000 business. He also green-lit a 25th Birthday Party for the server in Germany in 1997 that made people believe the best was still yet to come. We all needed to hear that while HP made Unix the favored child.
But one proof of his positive impact is the recovery of the platform as a strategic choice for HP. One of the most interesting things that happened in the period he ran the division involved resetting beliefs about computers in the 3000's age group. HP had thought such products were the children that it needed to eat in order to keep growing and improving. After a few weeks talking with Sterling's division managers, technology marketing guru Geoffrey Moore decided his own beliefs about legacy products needed revising.
September 23, 2015
Where Do Those DBEs Go In MPE?
Where can I get help with storing and restoring an Allbase DBE?
Gilles Schipper replies
SQLUTIL.PUB.SYS should let you access the DBE. IMAGESQL is to a DBE what QUERY/DBUTIL is to TurboIMAGE.
Denys Beauchemin adds
ISQL.PUB.SYS is used to access the data in a DBE. If a TurboIMAGE database is attached to a DBE, there is a DBTC file for each Turbo database and an ATCINFO file with the DBE.
How can I find all the IMAGE databases on a system?
Michael Anderson replies:
IMAGE database root files all have a unique filecode value, -400. IMAGE datasets all have a value of -401. So if you want to find all IMAGE databases on a MPE system I would use the following command:
This will give you all the IMAGE root files and only the IMAGE root files. If you use something like “listf @01.@.@” you get the first dataset in the database, but also any file where the filename ends with “01”, and that may or may not be a database file. Also, the MPE file system allows filecode representations to be alpha (“PRIV”) and Numeric. When you see “PRIV” as a filecode it simply means that the numeric value of the filecode is negative, and again this can include non-database file types.
September 22, 2015
Meetings serve futures. Most rely on pasts.
Last week I got a note from Terri Lanza, consultant to MANMAN and ERP users, asking about any forthcoming meetings for 3000 customers. Terri was a big part of the last HP 3000 meeting, the 3000 Reunion meeting that kicked off four years ago today. Lanza also queried ScreenJet's Alan Yeo, since Alan drove the engine of that Reunion while I helped organize and publicize.
Lanza is on the board of CAMUS, the user group devoted to ERP and manufacturing tech. "CAMUS was offered a place in California to gather," she said, "so our board wondered about choosing between San Diego and LA." Alan replied in short order that nothing is being planned for a 3000 meeting, and if anybody would know, it would be him. He kickstarted the meetings in 2005, 2007 and 2011. He even tried to turn the crank on a 2013 meeting. These things need financial support.
There's a great deal less purchasing among 3000 users four years after the Reunion. Purchases drive these tech meetings, but not just the sales pursued on an expo floor. Purchases of the past prop up meetings, as people try to better use the tech they already own.
That's why it's interesting to look at the content for many meetings among seniors like those who were at the Reunion. Tech meetings serve the drive toward futures, with talks about the Internet of Things or the Etch-A-Sketch wisdom on rules for social media. Learn, erase, learn again.
Legacy technology, though, tends to pay the bills for the bright-future meetings we used to attend. CAMUS is the exception, since its futures cover the survival of datacenters and legacy servers. Those are the servers that don't seem to get airtime, because their days of futures are supposedly over. Even HP seems to think so, if you look at what it's talking about at user meetings.
September 21, 2015
Throwback: FlashPaper strikes fresh match
Twenty years ago today your community was gaining one of its best database chiefs at HP, a development we illuminated in the first FlashPaper. In September of that year only a handful of 3000 vendors were operating websites, and we were not among those — so we drafted a last-minute news report sheet to deliver the latest developments into envelopes along with the first complete issue of the NewsWire. We were so full of confidence about a wave of news for the 3000 that we'd come to give the FlashPaper a slogan of "News so hot it might ignite."
We'd made a test-run at printing HP 3000 news, but that FlashPaper of September 21 was our genuine debut into breaking stories as fast as print would permit. The flame of change had been kindled in the 3000 division. We started work to change the forum for the computer from glossy magazines to something chasing newsmakers. We've always called October our birthdate because Issue No. 1 needed a date to match print-time waiting. Nine days was the fastest that print could be written and mailed in 1995.
The IMAGE/SQL lab had a hot seat at the time, its third project lead in three months. Tien-Yu Chen took over for Reynold Schweickhardt, who'd taken over for Jim Sartain at the start of the summer. R&D manager Harry Sterling promoted Chen from advanced development projects like the Critical Item Update team. He was a choice who made changes happen like increasing the scalability of IMAGE. We reported that Chen was the kind of leader who, while meeting with database tool vendors at HP, would grab a file system engineer on the spot to help along a discussion. (Just click on the paper above for a full read.)
Choices between Windows NT and Windows 95 were on customers' minds; the latter was still just a month old, while the former would take its DEC operating system roots and become Windows Server — but the Y2K challenge would be in IT's rear-view before NT grew into enterprise-grade Windows.
September 18, 2015
Passing audits: MPE privileges can be keys
Migrated HP 3000 data can become forgotten while making provisions for an audit. Since some HP 3000s work as mission-critical servers, these active, homesteading systems must weather IT and regulatory audits. The 3000 is capable of passing these audits, even in our era of PCI, HIPAA and Sarbanes-Oxley challenges — all more strenuous than audits of the past.
However, establishing and enforcing a database update procedure is a step onto filling the gap in the security of an MPE/iX system. HP 3000 managers should take a hard look at how their users employ System Manager (SM) privileges. (Privileged Mode, PM, and System Supervisor OP should also be watched. Overall, there can be 21 capabilities to each user.) In their most strict definition, those privileges can expose a database. Hundreds of users can be created at Ecometry sites; even seasonal help gets SM users, according to one consultant's report, users which are seldom deleted after the holiday has passed. One site had a script to create new users, and each had PM capability, automatically.
Privileges are often a neglected aspect of 3000 operations, especially when the system's admin experts have moved on to non-3000 duties, or even to other companies. (Then there's the prospect that nobody knew how to use privileges in the first place.) Some SM users have disturbed the integrity of 3000 databases. It's easy to do accidentally. A creator of a database can also update a 3000 database — a capability that can foul up a manager's ability to pass some audits.
VEAudit from VEsoft, using its LISTUSER @.@ (CAP("SM")) filter, can give you a report of all of the SM users on your HP 3000. You can even ask for the SM users where password="". (Now there's a good list to find: SM users who have no passwords.) There is no MPE command that will do such things, we are reminded by VEsoft co-founder Vladimir Volokh. Even after more than three decades of his business as a 3000 software vendor, he also offers consulting on MPE operations and management, and still travels the US to deliver this.
September 17, 2015
Making a Migration Work Like a Factory
There are many things to overlook or underestimate in a migration, and having a factory to move the data resolves plenty of questions. This week MB Foster took its UDA Central software for a webinar spin as a coming-out party, of a sort: The first briefing pitched directly to other integrators, consultants, and migration experts.
Cortlandt Wilson was on the call in the webinar, discovering more about how to help the MANMAN and ERP sites he's assisting in a migration onto other solutions. "He's really been the go-to person for moving data," he said of Birket Foster, CEO of the company.
Foster explained the triage of deciding if an application should be rehosted, replaced, or retired, and the factory concept shows how those decisions can be made more easily with UDA Central. The software has built a reputation for delivering insights about data.
"A lot of the customers out there don't know enough about what they own," Foster said in explaining the mission for UDA Central, which will rent by the job in the integrator-consultant model. The pricing will be offered in small-team and large-team tiers, meaning the size of the customer's IT team. The number of data targets, and the number of databases being migrated, will determine the price of the rental.
"Our goal was always to help in migrations so they're 10 times faster than using scripts," Foster said during the webinar. Scripting is the old-school way of moving data, something that UDA Central removes from the process. The software's been growing for 15 years, Foster added.
September 16, 2015
HP's latest layoffs chop a fresh slice of jobs
A report from HP's semi-annual Analysts Day yesterday included news of an extra round of 30,000 job eliminations. The letters "HP" still appear on the front of many 3000 customer's servers, either on the original 12-year-old or more hardware, or a replacement from the ProLiant or even the Integrity lines. The fate of the enterprise vendor is of differing interest to these groups of migrators and homesteaders.
Some of those customers who've left, or are leaving, will keep an eye on the shrinking headcount. HP means to keep itself healthy by keeping its costs low as it heads into its first split-up year starting this fall.
CEO Meg Whitman told analysts things are still falling in the enterprise services group, an operation that consults, outsources, and manages co-located business servers. Enterprise Services is the unit that grew up around the EDS workforce that HP acquired in 2008. Even back then, HP needed to trim back the job count as part of the acquisition.
In an '08 HP message called Streamlining for Growth the vendor said, "HP intends to implement a restructuring program for the EDS business group that will better align the combined company’s overall structure and efficiency with the operating model that HP has successfully implemented in recent years."
Enterprise Services generates about 40 percent of HP's Enterprise revenues. But the unit hasn't grown recently. Whitman said yesterday, "A big step forward will be if enterprise services can stop shrinking." The unit has posted $4 billion in losses over the last three years.
The game plan for Enterprise Services will sound familiar to an HP 3000 customer: move professional jobs offshore, outside of North America and Europe, to reduce costs. In 1995 the 3000 division opened operations in India, sending database development and other subsystems design into Bangalore. At the time India's pay scale was one-fifth of California's. Lower costs are going to look attractive for the split-off HP Enterprise.
September 15, 2015
COBOL Tools for Comma Separated Values
"item one", "item two","","","item three"
How do I create the "," between item one and item two?
And the ","",""," would it be the same? Just put that inside double quotes?
Something tells me that there is an escape sequence, but the mind is not cooperating.
Walter Murray, who worked in HP’s Language Labs before moving on to other 3000 work, replies
The STRING statement is helpful. I don't advocate using an apostrophe to delimit nonnumeric literals, preferring to stick with standard COBOL. And yes, QUOTE is a figurative constant guaranteed to give you a quotation mark.
September 14, 2015
We keep meaning to shut it down, but...
There's always acquisitions and mergers afoot in business, and the events have triggered some HP 3000 migrations. An entity gets acquired by a larger company that doesn't want to integrate MPE. The next thing you know, Windows is getting its call-up into a batting order where the 3000 used to play. (Sorry, baseball season's heating up as it winds down to the playoffs.)
A transaction that was announced this summer continued the journey of the Open Skies application that began in 1998 in the 3000 division of HP. In that fall, CSY General Manager Harry Sterling purchased the application that had helped to drive the 3000 and MPE into the airline business. "Harry, did you have to buy the company?" HP's next-level execs reportedly asked him. He bought it to show how Software as a Service could work on 3000s. HP called it Apps on Tap at the time.
Roll forward to July and see that the Amadeus Group started the purchase of Navitaire from Accenture. Navitaire became the proud owners of a farm of HP 3000s when the company purchased Open Skies early in the previous decade. By 2008, work was underway to move off those 3000s, a farm of more than two dozen of the N-Class servers. The software tracks mileage revenues and reservations and has been used by airlines including Canada's WestJet.
We got a report last week that a final N-Class server still is in operation, but it's destined for a shutdown. If only the overseas airline customers would stop needing historical reports from MPE/iX.
September 11, 2015
Fiber and SSD discs boost 3000 speed
While getting an update an IT manager at the welded carbon steel tubing manufacturer Jackson Tube, we discovered a field report on the combination of Linux, Fiber Channel networks and large disk that's being installed by Beechglen. Early this year, Mike Hornsby briefed us on the basics of the setup, one designed to bring fast storage options using Storage Area Networks to 3000s. Dennis Walker at Jackson Tube supplied some specifics.
We are currently using Beechglen's Linux Fiber Optic SAN on solid state drives with Distributed Replicated Block Device (DRBD) replication, which gave us a giant increase in speed. It's very cool; they use a Linux server with SCST Target SCSI for Linux to act as a Fiber Channel SCSI device. It uses Qlogic Fiber Channel boards to connect to the HP 3000.
Our setup is in-house, using their hardware on a hosting contract with Beechglen. We have two of their SAN devices and two of their HP 3000s, one production and one development system. The SANs are connected over an Ethernet fiber converter in two different buildings 1,000 feet apart. They have set up Linux's DRBD, and so can cross-mirror the HP 3000 logical block devices.
Before they told me about their setup, I had already been investigating a similar solution with the same software but with a SCSI-iSCSI adapter. They offered what I wanted all set up and tested, and using Fiber Channel. Plus they said they had to patch MPE to work correctly, which I could have never have done.
September 10, 2015
TBT: The End of the HP 3000's Beginnings
HP moved toward its RISC future in small steps. The hardware was first released in 1987's fall. It took another 11 years, but in September 1998 MPE V, the OS that lifted the 3000 into the highest systems count, fell off of HP's support radar. The CISC hardware such as the Series 70 fell away from HP's care, too.
MPE V was the last of the 16-bit operating systems for Hewlett-Packard. DEC had gotten a leg up in the middle '80s by promising that Digital Has It Now, with the now being 32-bit computing. Removing MPE V from the support tree at HP didn't remove the systems from the field. Paul Edwards, the trainer, consultant, and user group director exemplar, used to note that a Series 70 MPE V system was still running in the Dallas area even after HP announced its end-game for the entire line in 2001.
Calling the products its "vintage" software and systems, HP's Customer Support organization announced end-of-support-life dates for all MPE V products running on CISC-based HP 3000s, as well support for what the community called "Classic" HP 3000 computers.
Classic HP 3000s continued to operate in companies around the world after 1998, even though HP had stopped selling them 10 years earlier. A Classic-to-RISC trade-in program was still underway in 1992. HP estimated that it had shipped more than 20,000 Classic 3000s as of 1986. The Series 37, 37XE and Micro 3000 systems left support in 1997, and Series 39 through 70 systems went off support in January, 1998. By September of that year, HP turned out the lights on the last of the Classics -- the LX, RX, GX and XE models of the Micro 3000.
September 09, 2015
Still Emulating, After All of These Years
The Dairylea Cooperative was among the first of the North American 3000 emulator users to testify about making the choice to dump its HP hardware and keep MPE/iX. We ran a detailed story about Jeff Elmer and the organization that covers seven US states with sales, distribution and marketing for dairy farmers. There's a long history of Dairylea success, as well as success with the 3000.
We decided to check in after a couple of years and see what everyday life with Linux, MPE and the Charon emulator looks like today. The IT director Jeff Elmer answered our queries straight away, as if he was ready for the questions. He's making good use of VMware, so in that he's right in step with the virtualization strategy that was celebrated at the recent VMworld.
By Jeff Elmer
We started with the emulator in December 2013 and never looked back. We always loved the HP 3000 hardware, but with the emulator we no longer have any significant concerns about hardware failure since we aren't dependent on a RAID array consisting of disk drives built when some of our web developers were small children.
Even if we did encounter a hardware issue with the Proliant server that hosts the emulator, we could just fail over to an instance of the emulator we have standing by to run under our VMware environment in our business continuity site. We can "power up" that emulator in another city without getting out of our chairs. We would then restore from our most recent full backup (we do a full every day of the week which is written to disk and copied to the business continuity site) and then tell people to use the Reflection shortcut that points them to the emulator in the business continuity site.
September 08, 2015
Emulation does not include HP's slowdown
One of the prime reasons for extending 3000 application life is investment protection. It is difficult to justify, however, if a company continues to grow while its hardware performance remains capped at 2003 levels That's the incredible hamstring that most MPE/iX applications labor under. Aside from refusing to put MPE/iX onto Itanium chips, there was a fresh generation of PA-RISC processors available to HP by the middle of the last decade. But those PA-8900s were never employed in 3000s, just 9000s. Then there's the matter of hardware down-clocking. It's a feature not included in 3000 emulation.
Owners of 3000s probably know their systems were hobbled by HP during the design of the ultimate generation of the servers. They should also know that protecting their application investments with an emulator eliminates that hurdle to modern-day performance. The recommended top end today is an Intel i7. Whatever comes next will be available to keep MPE application performance growing.
In the wake of the just-completed VMworld show, it's easy to see that virtualization -- the other name for emulation -- is mainstream technology by now. Five years ago this month, though, we interviewed the Stromasys CTO Robert Boers about the design goals for the Charon emulator for PA-RISC 3000s.
Is your emulation going to get rid of the slowdown code that has hamstrung PA-RISC processors on 3000s?
We’re not using that. They’ve clocked them down to the equivalent of 55 MHz on the low-end models. HP actually had a back-door to allow their support people to turn up the performance if they were in a hurry. We’re actually building an accelerator.
The reports of Charon use in the field do not include any notes on clipped performance. The company made good on its promises of acceleration -- an area that can be enhanced by more upgrading hosting hardware, too.
September 04, 2015
Taking on Partners for Data Migrations
We'll be taking Monday off in observance of the Labor Day holiday. Enjoy your long weekends.
Enterprise IT managers have a broad brief, as the English like to call a scope of interest. They manage development, operations, networks, planning. That last mission has included migrations for quite some time by now.
And the most crucial part of a migration is moving the data. A lot of companies have never done this before on their HP 3000s, and so finding help is their next step. But who to step toward? More partners are going to get their stripes for this migration by the end of this year. MB Foster is opening up its expertise and software toolbox to get partnerships in data migration started with integrators, consultants, and vendors.
The company's CEO Birket Foster explained in an email, one that notified us about a September 16 webinar.
MB Foster has established a partner program that will enable others to leverage this data migration solution in their projects. We are excited to tell you how you can take advantage of this partnership opportunity and grow your project margins by creating a migration factory.
Fulfilling a migration request shouldn’t be difficult or time consuming. Writing custom migration scripts is the way of the past.
You can safely make such statements if you've got a proven alternative to scripting. That's the business that Foster's been in the longest, crossing four-plus decades of 3000 service. From the 3000's explosion in the 80s, through the go-go dot.com of the 90s, across the wilds of the migration decade of the Oughts, and here into the Twenty-Teens, data has been Foster's thing.
September 03, 2015
TBT: In the Thick of Proceedings Season
Before you even left your house for a flight to an HP user conference in the Eighties, you had to leave room in your suitcase for the thick books of proceedings. So much room, by the middle of that decade when the 3000 grew fastest, that you might have leave behind the booth swag you snagged from conferences like Interex annual meetings.
30 years ago this week, I was packing for my first national HP user conference. The Interex meeting was scheduled for Washington DC, the first time a HP 3000 users conference would meet in a national capital. We learned things afterward by packing up these fat tomes in our bags for the return trip. It was an era where you advanced your skill set by reading papers, printed in monotype Courier off HP 3000s which were running HP Word, or WordStar off a PC. HP could provide WordStar on its HP-150 Touchscreen PCs. It hadn't earned good notice for the utility of its touchscreen functions, though.
The graphic design for proceedings was spartan at best. At least half of the papers were written by users, and every professional who attended a show went home and hoovered up that wisdom that was shared without regard for reader comfort. The 200 papers from the Interex '87 show required three volumes of more than 700 pages each. The papers were printed in alphabetical order of authors' names, and nary a page number is to be found.
In addition to meeting in DC for the first and only time, 3000 users in September, 1985 could hear a speech from an HP CEO. David Packard was a former CEO and current HP board member when he addressed the multitudes at the conference. While Packard's speech has been lost to the wilds, those proceedings papers remain in closets, online, or fixed in the skill sets of the 3000 managers who have moved on to other platforms. Most printed advice that did not yet have the benefits of HP's LaserJet marked milestones on those hundreds of sheets printed each year.
September 02, 2015
The Heritage of Enterprise Consumerism
The heritage of your computer marketplace is driven by many more failures than successes. HP attempted to build a multiple operating system technology (MOST) system in 1993, mostly by re-engineering MPE and Unix software for customers who needed both environments.
MOST failed in alpha tests and taught Hewlett-Packard a lesson: do not promise so much flexibility that you kill performance. MOST was too slow to do the work of a single-OS system of the early '90s. The technology for multiple-OS computing was still five more years away, in Superdome. By the time HP polished Superdome, it lost its taste for expanding its MPE business.
That story has been echoed in the market many times. Virtualization and cloud solves such challenges today. But in 1993, NeXT Computer was killing itself by shipping a version of its OS that actually ran slower than the prior release. NeXT was the brainchild of Steve Jobs, who'd been kicked off Apple's throne by a board that was steered by John Sculley. Recent news has Sculley unveiling a new Android smartphone that won't be sold in the US. Aimed at China and emerging markets, this new Obi is, and so it avoids some competition with Apple.
Sculley, the former CEO of Pepsi, had been brought in to Apple by Jobs. The insanely great wunderkind knew he needed help to reach consumers. The move cost Apple momentum that elevated Microsoft and Windows to the top tier of business computing. Jobs tried to rebound with NeXT. Like MOST, the NeXT was way ahead of its time. Consumer-grade Unix was still 12 years away, lurking in the dreams for Mac OS X.
HP 3000 owners care about this because of their computer's heritage. Another consumer whiz, Dick Hackborn, climbed onto another board, HP's, and turned the LaserJet consumer reseller model onto the rest of HP's business. Direct contact with small to midsize customers became a task HP delegated. A 3000 shop that once knew its OS supplier through an SE or a CE had to learn to use resellers. The 3000 division lost track of the majority of its customers, and when the large sites yearned for a Superdome, nobody was able to keep in touch with customers who didn't need such a beast.
Sculley might do well with the Obi, even after a pratfall at Apple. On the other hand, the results might be Obi-Wan. It takes a failure to learn something, most times. MOST taught HP about speed, benefits, and the need for enough brainpower to enable something better (MPE) to drive something popular (Unix). The 3000's heritage flowed even and steady for awhile after Hackborn bent HP to a consumer beat. The loss of focus sealed the 3000's fate at HP, though.
September 01, 2015
Finding a Virtual Replacement for MPE/iX
This week HP and other vendors are presenting new products, and new ideas about older products, at VMworld. The conference is organized by VMware and offers a stage to show how IT strategies are being changed by virtualization. The only virtualization that MPE/iX hosts can enjoy is the Stromasys Charon HPA server. It makes Intel processors a virtual choice. Stromasys is at the conference, but what HP's got to say about Hewlett-Packard solutions is informative, too.
As it turns out, heading to Intel Xeon hardware is a good idea for all of the other HP enterprise environments. It's as if Charon and the Superdome brand are aimed at the same destination. HP-UX won't get there, though. And Intel Xeon is essential to VMware.
The 3000 customers who've been the slowest to move onward to other platforms might be the ERP companies. Manufacturers customize their applications more than any other kind of app user. This week HP's touting a server at VMworld that it says is the world's fastest 16-socket ERP server. Superdome X is driven by Linux and Windows, though, not the HP-UX environment that ruled HP's enterprise roost in the late '90s — an era when Windows was taking over IT.
HP bet heavy on Unix. Back then, the product which became Windows 2003, 2008 and then 2012 was called Windows NT. Everything that NT did was folded into those subsequent Windows enterprise solutions. Since then, meetings like VM World apparent that HP's Unix lost its high ground, but not because of any lack of virtualization. HP's Unix isn't ever going to the x86 family. HP-UX slipped as an enterprise choice because it was built upon the wrong processor.
That's what HP's manager Doug Strain used as a key point in his VMworld talk about Superdome X. "The only problem was that it didn't have x86 processors," he said of the machine that now can use up to 12TB of memory. "Well, we fixed that." So it seems that the right chipset — based on Intel's Xeon, not Itanium — will make Superdome as useful and fully-featured as it should be for virtualization. It's just one more way to see that Itanium and HP-UX has dropped from HP's futures.
Linux is taking the place of HP-UX in HP's ERP futures. It's not news that VMware and HP's Unix are not a match. What seems new is the way Linux and Windows are positioned as HP's VMware solutions — with specific mention of ERP applications.
August 31, 2015
Posix file movements, using FTP and more
I'm attempting to move files in and out of Posix namespace on my HP 3000. The file I've copied becomes bytestream, and has a REC of 1. But I want to transfer that file from Posix down to my PC, I need to maintain it's structure — but what appears to be happening is it's one long record, with no separators. Is there a way (automated) that I can move files in and out of Posix, maybe FCOPY, and be able to keep the structure?
Donna Hofmeister replies
Simply copying/renaming a 'regular' MPE namespace file into HFS-namespace will not change its structural attributes.
If the MPE file was ';rec=-80,,f,ascii' to begin with, it will still be that afterwards. And it will retain those attributes (cr/lf in particular) following an FTP transfer from your 3000 to [something else less enlightened].
To have a foreign/non-MPE filed take-on MPE fixed-record length attributes during an FTP transfer, simply add something like the following on your transfer line:
[put|get] non_mpe_file_name MPEFILE;rec=-NN,,f,ascii (making all the proper substitutions)
How do I get my HP 3000 to play well with Web-based FTP clients?
HP's James Hofmeister, who led the effort to keep FTP up to date on the 3000, replies
Lots of work went into an implementation of the FTPSRVR to support web access to the 3000. The "SITE POSIX ON" command can be sent by a FTP client and the 3000 FTPSRVR will emit Posix "standard" FTP output and will react like a Posix host (including file naming conventions).