June 16, 2020

This blog turns 15, logs a half-million views

Screen Shot 2020-06-16 at 2.16.21 PM
Earlier today, this blog served up pageview number 500,000. That's a half-million times that some business computer expert needed to learn about, repair, or plan for using MPE/iX or the HP 3000. Content at this web address still serves a community.

The straight-up math tells us that the total amounts to 33,333 page views a year on average. These days, the pageviews are closer to 16,000 per year. None of those pageviews are included among those off the website at the original 3000newswire.com. It's the repository for the 1996-2005 Newswire, the Online Extra newsletters, plus a record of 122 monthly FlashPaper supplements. That site goes back 24 years.

A half-million blog page views, all since the year before HP's original support shutdown, shows remarkable devotion. Not even necessarily to the NewsWire; that half-million illustrates how long a server can remain vital and useful. We've been telling the 3000's stories for more than 18 years since HP started to quit on it. We reported for six years while the product was still a part of HP's futures.

Although the news from that 2005 monthly roundup might seem like history, it reinforces the choices 3000 managers face today. Solutions not tied to a single vendor continue to face a steep decline. Going independent of a system vendor is the default move.

The 2005 news reports showed an HP trying to find relevance in a changing IT landscape. June was the summertime after CEO Carly Fiorina left HP. She departed after throwing the vendor's weight behind high growth, low-margin computing. PCs, laptops, and printers were ascendant in the HP of 2005. HP was finding new enterprise business elusive, unless the new systems ran Windows. Unix served some 3000 sites that migrated from MPE/iX. Many more of the departed had migrated to Windows. Some were taking a chance on Linux.

The 2005 customers were moving away quickly from the OS at the heart of their companies. By mid-year, only 43 months had ticked away since HP's exit announcement. There were not a lot of customers already exited by the month the blog opened for business. We surveyed customers to discover that a close to half were replacing a 3000 with Windows 2003 Server.

That was not HP's plan at all, figuring enterprise features of HP-UX were going to snare the ex-3000 sites.

This blog gave us the avenue to report survey updates immediately. One of the first five blog articles that kicked off the page view deluge updated our migration target survey with fresher results.

Customers expressed reluctance to put mission-critical computing onto Windows. But Windows’ familiarity won it many converts. This made HP's exclusive tech advantages less popular. “We are moving to a Windows 2003 Server environment," said programmer supervisor E. Martin Gilliam of the Wise County, Va. data processing department, "because it is the easiest to manage compared to Unix or Linux.” 

Hewlett-Packard was casting about for a plan to keep growing. In 2005 HP announced it would separate its printer units from PC segments. HP's 1990s management assumed everything was supposed to thrive on the business model that drove its laser printer success. A smaller direct sales channel, with less room for different and superior engineering, was the result of chasing commodity computing sales. HP was reorganizing, back toward a business plan that acknowledged not all products can use the same strategy.

Printers and PCs got their own leadership. At the time I looked into the future and saw that the HP 3000 customers were forced to leave might see another spinoff. A separate enterprise computing business. "An HP with non-Windows servers running HP-UX and OpenVMS could be just around the corner."

Nine years later, HP decided to break up the brand. Enterprise servers split off from the low-margin products. It didn't make HP more relevant to business IT. By 2014 even OpenVMS was flagging — and it remains the product line with the biggest number of customers not using Windows or Linux.

Our first month of blog reports included more tactical advisories. Some remain useful today. Keven Miller, who still supports 3000s and gathers MPE resources for the community, updated his 3000 firmware without the aid of HP's support engineers. It's the unusual site which doesn't need outside support help. After all, Miller's 3K Ranger firm serves 3000 customers. But the how-to about changing Processor Dependent Code is still on this blog's site, ready to serve its goodness through another page view. You will need patches, where the independent support firms can make them available.

We said at the time that "Miller's experience represents the level of admin skill a 3000 owner is going to have to call upon once HP's support leaves the field. If you're uncomfortable with this kind of admin, but need to keep your 3000s in service, there's a good lineup of 3000 service providers who can help you, all in the third-party market." There is still a healthy group of service companies working 15 years later.

Onward to the next half-million page views. It ought to happen around 2051, if we can keep up the current pace. I'll only be 94, while the 3000 will be 77. I hope to age as well as MPE.

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

Follow the 3000 NewsWire on Twitter
for immediate feeds of our latest news
and more twitter.com/3000newswire.

May 06, 2020

Interex director Chuck Piercey dies at 85

Chuck Piercey
Chuck Piercey, executive director of the user group Interex during its greatest era of the 1990s, died last week peacefully in his sleep. He is survived by his wife of 64 years, Charlene, as well as children, grandchildren, and great-grandchildren. His memorial last weekend during our viral times was held over Zoom. That kind of essential innovation would have been in step with his vision for Interex.

He held his Interex post more than a decade, longer than any director in the 31-year group's history. Piercey helmed the organization that gathered thousands of Hewlett-Packard community experts under one roof after another, in city after city, for each year's biggest exchange of 3000 technology and commerce.

Piercey would be quick to point to his staff as the reason for those successes. He came to his post from executive work in Silicon Valley at Perkin-Elmer, a semiconductor firm with roots nearly as deep into HP's. Piercey grew a multimillion-dollar user organization that launched new conferences and established a digital footprint into the Web. New publications emerged during an era when paper was still the dominant means of information exchange. But thick volumes of tech papers made their way onto CDs, too. Panels of HP's top executives sat for tough questions from 3000 customers during a time of uncertain futures. 

Screen Shot 2020-05-06 at 9.23.24 AM
By the close of Piercey's era, Interex had moved firmly into the promise of development over the Web. HP created an MPE/iX Shared Source project, which Interex hosted for the 3000 division. HP started in a very timid way with Editor, Query, and the TurboIMAGE class libraries. Members of HP's labs collaborated with users to check source code modules out and check them back in after revisions. It was akin to the Github repository, mapped onto MPE's essentials.

The growth took place while HP was sacrificing its 3000 vision to the promises of Unix. That strategy was driving a stake into the hearts of Interex volunteer members. Those actions made Piercey's work complicated in a way that reflected the industry's era of change. Terminals were the predominant access to 3000s when he arrived at Interex. By the time he left the group in 2000, the dot-com boom was reshaping the way 3000 users shared expertise. Windows was the driving force as Interex's work opened windows to an HP future that relied less on vendor-specific environments like MPE.

Piercey managed Interex with a series of volunteer board members voted in on three-year terms. In a continual change of Interex leadership, Piercey was the constant for that decade. Boards often better steeped in technology than business presented challenges to the needed changes, evolution that Interex accomplished nevertheless.

He came to the position with no direct experience in managing an association, but Interex pursued him relentlessly in 1989. With a mechanical engineer’s degree and an MBA from Stanford, Piercey worked at Silicon Valley firm Ultek during the first 20 years of his career. As he described it, the middle section of his career was being the founding partner of three startups, doing turnaround management at the bidding of venture capitalists. He was doing his own business consulting when Interex won him to its mission in March of 1990.

Piercey took the wheel at an association facing as much of a transition as HP itself in the 1990s. The group’s roots and its volunteer strength lay in the 3000 community, but HP’s attention was being focused on the world of Unix. Platform-specific user groups were under siege in the middle of the decade. He pointed out that even the 32,000-strong Unix group Uniforum eventually withered away. But Interex persevered, forming a tighter coupling with the changing HP and broadening the group's focus. The Interex user show and news publication were both rebranded as HP World to tighten the HP relationship. The conference was ranked as one of the best in a Computerworld survey.

His retirement from Interex was supposed to bring him into full-time grandfatherhood, but a educational startup devoted to molecular biology carried into his final career post. When he announced his resignation, board member Linda Roatch said, "He is largely responsible for bringing Interex forward to what it is — the most successful vendor-centric independent user group in existence."

Before he left his work at the user group, Piercey reflected on the future of single-vendor organizations like Interex. He had enough vision to see that a multivendor IT world could render well-established user groups obsolete. In board meetings and in public, Piercey would ask, "What is the role of a vendor-specific group in a multivendor world?" Asking hard questions was one of Piercey's talents that kept Interex on its feet during a trying time for user groups.

In a NewsWire Q&A from 2000, Piercey's final year with Interex and the final year HP proposed 3000 growth, he summed up the changes that challenged the user group. "Customers don’t have the luxury of focusing on the HP 3000 like they did 10 years ago," he said. "We have less mindshare, and we have to be more effective with the mindshare we do have. It squeezes the value proposition: you have to deliver more value cheaper and faster. What they really want is wise filtering of information."

The transfer of that information grew as a result of his work. Last weekend's celebration of Piercey's life was transcribed, including photos. It's hosted on the Web as a Google Doc, an eventuality of sharing that he would have foreseen.

Posted by Ron Seybold at 11:44 AM in History, Homesteading, Migration, Newsmakers | Permalink | Comments (0)

May 04, 2020

Infor cuts off MANMAN support by mid-year

Cut rope
More than four decades after its launch in 1970s, MANMAN marks a milestone at the end of this month. On June 30, 2020, the app's vendor will terminate all remaining support contracts. Other will be available on a time and materials basis, either.

In a world where legacy datacenters continue to contribute thrive, losing support is not a crushing blow. MPE/iX and OpenVMS are the two environments where MANMAN dug in. Tim Peer at Envy Systems supplies good independent support for MANMAN on OpenVMS. Terry Floyd at The Support Group, along with his son David, bolsters HP 3000 MANMAN users. Terri Glendon Lanza of ASK Terri is another good resource for MANMAN on MPE. By all accounts, support from the MANMAN lab is minimal today.

When June 30 arrives, Infor will end its journey with MANMAN. The application has had at least five vendors own it. Created by ASK Computer Solutions in 1977, the suite moved item data from untold billions of products and materials across many midrange systems. 

Infor has thrown in its official towel. "Finally, upgrading MANMAN to newer hardware would require a complete rewrite of the MANMAN software," an Infor release stated in 2018. "Unfortunately, after analysis, that is not an economically viable option."

One interesting element of the support shutdown is how Infor wants customers to consider sticking with the vendor. Infor has a cloud ERP solution. CloudSuite Industrial would be a good alternative, according to the marketing department at Infor.

"If your organization has not considered cloud, now is the time to start," Infor's end of support notice suggests. "We plan to offer an attractive and affordable program for MANMAN customers that want to move to one of our cloud products. For example, we recommend that you explore Infor CloudSuite Industrial."

Infor goes on to tell its customers that legacy computing is the problem. "MANMAN is based on legacy technology using hardware platforms that are no longer supported by their vendors," Infor's notice states. "As such, Infor believes there is a real risk in using the MANMAN software to manage your enterprise."

Yes, it's always the risk that a vendor is watchful about, especially when it cancels an enterprise-grade product. Minimizing risk can maximize a vendor's opportunity to replace an app that continues to work

MANMAN is supported by knowledge and code from the CAMUS user group at camus.org. Infor's internal requirements are getting in the way of continued support. Make no mistake: the HP 3000s without vendor support from HP have been that way since 2011. All through those last nine years, Infor has collected support revenue from MPE/iX customers.

Everything grows old, sometimes too old to turn a profit. CAMUS has resources to help MANMAN feel younger.

Photo by Douglas Bagg on Unsplash

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

April 06, 2020

SSD devices head for certain failures

Western Digital SanDisk
A solid-state storage device is not usually a component of HP 3000 configurations. However, with the onset of virtualizing MPE servers, those drives that do not move, but still store? They are heading for absolute failures. HP is warning customers.

The problem is surfacing in HP storage units. It's not limited to HP-brand gear, though. SanDisk devices cause these failures. One fix lies in HP Enterprise firmware updates.

HP Enterprise disk drives face a failure date of October 2020, unless administrators apply a crucial firmware patch. Notices from HP Enterprise warn the owners of some disks about failures not earlier than October. Other Solid State Drive (SSD) disks are already in danger of dying.

Some SanDisk SSD drives have already rolled past a failure date of last fall, for those that have operated constantly since late 2015. The failure of the drives is being called a data death bug.

For some, HPD7 firmware is a critical fix. HPE says that Western Digital told the vendor about failures in certain Serial Attached Storage (SAS) models inside HPE server and storage products. Some SAS SSD drives can use external connections to HPE's VMS Itanium servers.

The drives can be inside HPE's ProLiant, Synergy, and Apollo 4200 servers. Some of these units could serve as hardware hosts for virtualized 3000 systems. The SSD problem also exists in HP's Synergy Storage Modules, D3000 Storage Enclosure, and StoreEasy 1000 Storage. If the disks have a firmware version prior to HPD7, they will fail at 40,000 hours of operation (i.e., 4 years, 206 days, 16 hours). Another, even larger group of HP devices will fail at 3 years, 270 days 8 hours after power-on, a total of 32,768 hours.

The numbers mean that the failures might have started as early as September of last year. The first affected drives shipped in late 2015. HP estimates the earliest date of failure based on when it first shipped the drives. Another batch of HP drives shipped in 2017. They are also at risk. These are the drives looking at an October 2020 failure date without a firmware update.

Beyond HP gear

The devices are Western Digital's SanDisk units, according to a report on the website The Register. Dell has a similar support warning for its enterprise customers. Dell lists the SanDisk model numbers:

LT0200MO
LT0400MO
LT0800MO
LT1600MO
LT0200WM
LT0400WM
LT0800WM
LT0800RO
LT1600RO

RAID failures will occur if there is no fault tolerance, such as RAID 0. Drives will fail even in a fault tolerance RAID mode "if more SSDs fail than are supported by the fault tolerance of the RAID mode on the logical drive. Example: RAID 5 logical drive with two failed SSDs."

Adding to the complexity of the SSD failures, firmware to fix the issue has two different numbers. HPD7 repairs the 40,000-hour drives. HPD8 repairs a bigger list of devices. Leaving the HPD7 firmware inside drives among the larger list of disks — which have a death date that may arrive very soon this year — will ensure the failures.

Full details from HP's bulletins for the 40,000-hour and for the 32,768-hour drives are at the HPE website. There are also instructions on how to use HP's Smart Storage Administrator to discover uptime, plus a script for VMware, Unix, and Linux. These scripts "perform an SSD drive firmware check for the 32,768 power-on-hours failure issue on certain HPE SAS SSD drives."

A list of 20 HPE disk units falls under the 32,768-hour deadline. Four other HPE devices are in the separate 40,000-hour support bulletin.

Posted by Ron Seybold at 11:51 AM in Homesteading, Migration, News Outta HP, Newsmakers | Permalink | Comments (1)

March 31, 2020

MPE file equations and Unix equivalents

Blackboard equation
HP 3000s, as well as MPE, employ a unique tool to define the attributes of a file. That tool is file equations, a 3000 speciality. Robelle calls these "commands that redefine the attributes of a file, including perhaps the actual filename."

In any migration away from HP 3000s (an ill-advised move at the moment, considering the COVID-19 Crisis) managers must ensure they don't lose functionality. Unix doesn't have file equations. Customers need to learn how to make Unix's symbolic links report the information that 3000s deliver from a LISTEQ command.

3000 managers are used to checking file equations when something mysterious happens with an MPE file. Dave Oksner of 3000 application vendor Computer And Software Enterprises (CASE) offered the Unix find command as a substitute for file equations. You need to tell find to only process files of type "symbolic link."

Oksner's example of substituting find for LISTEQ:

find /tmp/ -type l -exec ls -l {} \;

which would start from the /tmp directory, look for symbolic links, and execute “ls -l” on the filenames it finds. You could, of course, eliminate the last part if you only wanted to know what the filenames were and get

find /tmp/ -type l

(I believe it’s the same as using ‘-print’ instead of ‘-exec [command]’)

Beware of output to stderr (if you don’t have permission to read a directory, you’ll get errors) getting interspersed.

Jeff Vance added that the command interpreter in MPE also can deliver file information through a listfile command:

Don't forget the CI where you can do:

:listfile @,2;seleq=[object=symlink]

:help listfile all shows other options.

Our former Inside COBOL columnist and product reviewer Shawn Gordon offers his own MPE vs. Unix paper, and Robelle's experts wrote a NewsWire column contrasting Unix shell scripts with MPE tools.

Image by Gerd Altmann from Pixabay

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

March 28, 2020

TE turnoff date for 3000s could be 2021

Light switch
For a long time, TE Connectivity has been one of the biggest users of MANMAN software running on HP 3000s. That might be on the way to a permanent quieting — sometime next year.

Terry Simpkins at the firm was patching a Series 918 not long ago. It gave him a chance to check in with the remaining 371 subscribers to the 3000 mailing list, once he got the know-how he needed to patch.

"The force is once again calm," he said. Simpkins found a converter that allowed him to replace his old single-ended 2 Gb disk drives with the newer 36 Gb LVD drives. "I now have more disk space than my little 918 will ever need, plus a few spare drives to ensure I’ll never have a disk fail. Now to dust off the old CSL tapes and see what I want to restore."

TE measures its 3000 footprint by the number of databases online. "We’re down to four active MANMAN databases, from a high of 22. Three will convert to SAP at the end of June, so the last five-plus months will be a single MANMAN DB in Germany. I suspect we are going to be extremely bored at that point."

As to the shutdown date of 3000 operations, Simpkins said, "Right now that looks like somewhere between November 2020 and March 2021." 

Photo by twinsfisch on Unsplash

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

March 16, 2020

Deep pockets? Maybe not for MPE positions

Pants pocket
Even in the earliest days of 2020, consultants and programmers are hunting down chances to earn money servicing the 3000. When Doug Hagy looked into joining the LinkedIn HP 3000 Community, he wanted to see if the group was a source of related work opportunities. "I developed on the HP 3000 continuously from 1981 to 1999," he said. "At its peak of popularity, it was a pretty solid platform. Companies who chose HP 3000 usually had deep pockets."

Hagy isn't wrong altogether. An HP 3000 investment can be traced to Fortune 100 corporations like Boeing, or a part of the L'Oreal beauty empire. It's far more likely to see an MPE/iX server running as a place like a Texas title insurance company, or a manufacturer of saw blades.

We had to reply that we didn't know of new work opportunities for 3000 experts. Certainly, his 18 years of development experience qualifies Hagy as one of those. From time to time, opportunities surface in places like the 3000-L mailing list. Fresche Legacy has a stable of 3000 people who help in migrations as well as perform some system maintenance for 3000s.

FM Global was looking to hire a Powerhouse developer on a contract basis in January. Pay was $50 an hour for the job in Rhode Island, on a six-month set of contracts "extended for years to come." The company even advised applicants of a $62 a night rate it had for contractors' lodging at Extended Stay America. It didn't look like the lodging was fully compensated, but there was a $23 a day per diem.

Just this week we heard from Birket Foster, whose MB Foster firm is still assisting in migrations of data from 3000s. Some of those are contract-driven, while others can be sometimes project-specific engagements.

LinkedIn has a 3000 Community with 674 members, which makes it twice the size of today's 3000-L membership list. LinkedIn's groups used to have an attached Jobs feature, but by now the Jobs are spread across all of the site's resources. With that said, a post for Programmer/Analyst for the City of Lawton, Oklahoma was listed in November. MPE/iX was among the requirements.

Hagy was enthusiastic. "If I found someone wishing to migrate an app from a 3000, that could be interesting. IMAGE, V3000, COBOL could be an interesting project. Lots was developed for this platform."

The deep pockets are mostly gone from 3000 enterprises. Migrating Image, VPlus, and COBOL II was a project for the previous decade. Companies are migrating data for use with cloud computing and alternatives involving Linux. Archival 3000 systems are running, and some others are managing production on a timeframe to allow companies to migrate.

Hagy, who operates Twin Lakes Consulting, "a nimble micro business" based in Greensburg PA, says he last touched MPE around 1999 or so. "I was doing Y2K prep and providing backfill support for businesses moving to new platforms," he said. I wasn't thinking there'd be any HP 3000 action out there now, until I saw the group you moderate. I'd make time to assist if someone wanted to port a novel app from MPE and needed someone to dissect its inner workings. Before MPE I did RTE work on HP 1000s."

Some companies will need a programmer or consultant whose experience goes back to the days of real-time systems with HP badges on the front of the server. They emerge from the shadows of an era where reliable service, on an unhackable server, that simply worked, could be enough.

Image by ds_30 from Pixabay

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

February 10, 2020

3000 market maven Charles Finley dies at 70

CharlesFinley_8_2_2013
Charles Finley, whose career in the HP 3000 community spanned eras from powerful regional user group conferences to trusted HP reseller status, then led to new success as a migration maven, has died at age 70.

Finley built a reputation with the community from his first steps in the Southern California 3000 market. Buoyed by the remarkable manufacturing community in the area, by the middle 1980s he was operating the ConAm reseller and worked to establish the Southern California Regional User Group. SCRUG hosted conferences successful enough to rival those from Interex in scope.

Finley also played an essential part in founding an invitation-only MPE developer conference, using a novel format called the un-conference. It delivered information that otherwise would not be presented if only one person were in charge of the agenda. In the early times for groundbreaking tech, the 3000 community had a forum to explore new choices. "Things that could be overlooked like NT, Linux, VMware are noticed, because one person in the group happened to notice it and think it was important," he once said. "The rest of us benefitted by it."

Once HP curtailed its 3000 futures, Finley evolved the ConAm reseller business into Transformix, owned and operated with his wife Deborah. She assumes the post of president of the firm that has created and deploys a migration suite for carrying legacy applications from MPE/iX and other environments applications onto new platforms, especially Linux.

Finley was a Vietnam-era Marine Corps veteran. His widow said the CEO of Transformix delivered his skill and innovation with a duty to the work and the customer.

"Charles was unsurpassed in his passion for the business, his drive for perfection and professionalism, and his commitment to the integrity of customer relationships," Mrs. Finley said. “I saw that every day in the way he spoke about his work."

"This is both a personal and professional loss for many of the people who have known and loved him. Everyone who knew Charles regarded him as a man devoted to his family, his employees, his customers, and his friends."

Condolences may be sent to Deborah via email. The family requests that donations in lieu of flowers can be made to the charity Charles held close: Copley-Price Family YMCA 619.280.9622. Deborah asks to please designate that your donation is in memory of Charles H. Finley, Jr.

The company he leaves in her management is an integration, reseller, and consulting organization specializing in migration of legacy systems to current hardware and software. Transformix is headquartered in San Diego.

Mrs. Finley said the passing was unexpected. Charles Finley is listed as a speaker at next month's SCALE 18X technology conference. His seminar, Transforming Legacy Applications to an Open Source Modern Technology Stack, was the latest in a line of talks at the Southern California Linux Expo.

This year's seminar would "provide attendees with an understanding of the steps involved to transform legacy applications by retargeting them to an Open Source Java Framework. The seminar shows how the CUBA-Platform framework—which was designed for development of modern web application—is also well suited to enhance and extend legacy applications."

Finley was a significant voice in the migration community. While outlining differences between legacy migration, modernization, and transformation,
his experience smoothed the way for legacy applications to use modern technology stacks, including Java.

His SCALE seminar for this year was "a hands-on workshop transforming a legacy application for those who want to know more."

"If you have a PostgreSQL database already, you can generate a working Java web application in minutes using the CUBA-Platform. Moreover, you can do this without knowing any Java! Also of interest is the fact that professional developers and 'citizen developers' can use the platform for development."

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

January 30, 2020

Calendar date issues are already surfacing

Hurdles
The 2028 date hurdle for MPE/iX has been well documented and thoroughly discussed. Although the January 1, 2028 deadline — when MPE/iX CALENDAR processes will start to report dates as January 1, 1970, and so on — seems like it's years away, it's much closer. Calendar issues emerge as programs call for dates.

Programs that call for dates in the future are already facing the hurdle. Systems that use Unix, Linux, or other operating systems this month have triggered these involuntary date rollbacks already.

In one recent case, a top 100 pension fund had a nightly batch job that computed the required contributions, made from projections 20 years into the future. It crashed on January 19, 2018 — 20 years before Y2038.

HP 3000s have been key tools in many financial and resource planning operations. While dates are usually used to track transactions as a matter of history, some ERP users look forward to forecast their resource needs.

MPE/iX has a Y2028. Unix and Linux have a Y2038. This is important to know for a legacy system manager's planning and tactics. There's no good reason to tear down a legacy system if its only show-stopping flaw is date handling. A solution for the 3000 community is already at hand in several spots. 

Stromasys reports it has been working with an independent developer for a 2028 fix, something available to its Charon emulator sites. That update was shared with us in July of last year. It's not public yet, but that indie developer confirms the work is in progress. Beechglen has a 2028 solution it is selling as a service.

There are additional developers and consultants who say they're ready to repair 2028 issues with MPE/iX systems. It's important to know that the HP 3000, as one of the older legacy systems still working in businesses, is in no worse shape than systems driven by Linux or Unix. It's only a matter of when, not if, a date handling process will need to be addressed.

The legacy of an operating system is a condition defined very broadly. Legacy systems have been successful for a long time, and the vendor's focus has usually slipped away from these legacies. It can remind us of that term "proprietary" that was hurled at the 3000 for a decade before HP quit on its futures. Nearly all technology has a proprietary aspect, even if it only amounts to a support clause that makes one knowledge resource crucial to the OS health. 

Photo by Interactive Sports on Unsplash

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

January 02, 2020

Even in apps retirement, 3000 data survives

Aging hands on keyboard
A notable manufacturing datacenter in the 3000 community is making changes to its application lineup over the coming year. Although the profile of the apps and their status is changing, there's no talk of removing MPE from the datacenter yet.

Al Nizzardi is part of the IT command at TE Connectivity, the company that has more MANMAN instances running than any other in that ERP ecosystem. There's been a devotion to the 3000 that's extraordinary. Terry Simpkins has been the face of using 3000s in manufacturing since the 1990s. The IT director at TE even appeared once in a magazine ad promoting the 3000.

At TE, plans for the future of ERP applications have been aimed at SAP for several years. It's a migration, but one with echoes. SAP shares a customization practice with MANMAN: both apps are better choices when they're tuned to individual business practices.

After a few decades of use, the data repository for a MANMAN site becomes an asset that deserves its own curation. Data from a 3000 goes back to the late 1970s. The final cutover to SAP is likely to take place in late 2020 or sometime in 2021, by Nizzardini's reckoning.

"Databases are slowly migrating to SAP," he said. "I believe the final cut over will be 12 to 24 months out from today. That does not mean the end of the HP 3000. Historical data will reside on a HP 3000 of some sort."

TE runs a production N-Class, a test N-Class, an N-Class disaster box, and an A-Class. The datacenter does some Netbase shadowing, Nizzardini added. "We are still formulating a plan on our options, whether it's using an emulator or the N-Class we have" for archival MPE computing. "Either one of those options will be moved to a co-lo."
 
Experts on managing MPE/iX computing never stray too far from a place of helping. "We will be ready for when the Phoenix arises," Nizzardini quipped. "I've often said they will have to yank that HP 3000 out of my cold dead hands."
 
Image by Steve Buissinne from Pixabay

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

December 24, 2019

Gift wishes heading into the future

Christmas tree
Today's the day when generous people tuck presents underneath a holiday tree. Not so long ago, the only museum devoted fully to HP's computers was looking for gifts of classic hardware to flesh out its collection.

The HP Computer Museum is based in Melbourne, Australia. Its founder Jon Johnston passed away but left behind gift requests. The museum is downsizing now, like a lot of the owners and managers of HP 3000s. It's worth noting, though, that HP's breakthrough 3000 designs were among the most desired of museum gifts.

A table provides a listing of major hardware products the museum was seeking. This matrix lists the items by rarity and product category. Near the top quadrant: HP 3000s first released 45 years ago.

HP Computer museum needs
The white boxes represent the most needed items. The museum has no samples of these items. Pink boxes are most rare.

An HP-built 3000 server is old by definition now. The freshest pieces of hardware were manufactured more than 16 years ago. The craft and design of the HP iron, of any vintage, was legendary as well as being a gift of legacy. Even if MPE/iX is the only thing in use at some sites in 2020, because Stromasys emulation has taken over there as the hardware platform, HP's hard goods made that environment a classic.

Several resellers still trade in HP's MPE/iX iron. Cypress Technology's Jesse Dougherty continues to leave reminders about his 3000 system stock. Ebay is another reliable source, a place where the systems are often being sold by a reseller like Cypress. A Series 969 220 was for sale this week at $1,450.

Happy holidays. We're taking a break until just beyond the new year, when we mark the start of the 47th calendar year of MPE and 3000 service.

Posted by Ron Seybold at 12:21 PM in History, Migration, Web Resources | Permalink | Comments (0)

November 14, 2019

Welcome to Year 19 of the Afterlife

Cheated Death on printer
You remember where you were, perhaps, on the day you learned Hewlett-Packard was done with MPE/iX. You might have been in a meeting, or checked your email before heading home. You might have been installing something a 3000 needed to keep serving your company, or even ready to order a new server to replace the old 9x8 box. Some unlucky vendors were holding orders for new systems.

People did all of that and more on the day HP revealed its 3000 era was on its way to a finish. By 2003 the community was calling the new era The Afterlife. The lifespan of building new HP 3000 hardware was ended when a box rolled off the line at the Roseville plant in early November that year.

Afterlife shirt

And so, on November 14 of 2001, the afterlife of Hewlett-Packard's lifetime started with dismay, anger, and then resignation. The five stages of death proceeded through discussions in a lively 3000 newsgroup. Taking a cue from the horrors of 9/11 in that season, programmers and vendors howled about the relatively unimportant death in their lives.

Doug Greenup was leading Minisoft in that November week. The CEO of a software company whose products were on thousands of systems, he became aware of the HP pullout with just one day's notice.

Alvina Nishimoto from HP called me. She was in charge of third parties with HP at the time. She asked me to sign a non-disclosure which she'd just faxed me. She said she had important news. I signed it and faxed it right back. She called to tell me HP was announcing they were discontinuing the HP e3000, and that HP-UX was their future direction.

HP might have been worried the story was going to get into the world without its influence. The news had been roiling through the 3000 community for more than a week before I learned about it. Wirt Atmar, the founder of AICS and a 3000 stalwart, threw off the lid about the pullout by posting on a developers' mailing list.

I spoke to two of our oldest, most trusted customers yesterday, one a ten-year customer and the other 15 years, about this upcoming announcement. Their first reactions were that it simply sucked their breath away. When I told them about HP's proposed plans of migrating their applications to HP-UX — which as an option has all of the practicality to them of trying to establish a penguin colony in Death Valley — their second reaction was "the hell with HP. If we move, it will be to anything but HP." I think that that's going to be the general reaction.

HP learned a great deal about ending a product line with the lessons that began 18 years ago. Earlier this year the company made a graceful transfer of responsibility for OpenVMS, sending the software as well as support opportunities to an independent firm, VMS Software Inc. HP won't sell any more OpenVMS licenses, although it continues to build Itanium servers that will run the apps created for that OS.

This was a vision that the HP 3000 community took to heart during the first of the 18 years that followed. A similar group of OS experts, organized and led by Adager, wanted HP to transfer the future of MPE/iX to new, independent stewards. HP didn't know how to do this in 2001 or in 2002. The offer took another form in the OpenMPE advocate organization, but eight more years had to slip past before HP's source code made its way into independent software labs.

A new history began 18 years ago, a record of a group of computer customers who kept their own counsel about walking away from a corporate computing asset. The next two years or so will show HP Enterprise customers what might have been possible had MPE/iX found a third party home. VSI is predicting that it will have production-grade OpenVMS ready for a late 2021 release on Intel hardware.

This is more than a shift away from the HP Enterprise resources. VSI is carrying OpenVMS to a new chipset, a commodity home. In 2001, Atmar told HP's business manager for 3000 operations, Winston Prather, such a move was what the 3000 customers deserved.

Opening MPE up and migrating it to an Intel platform offers at least some real hope for a continued and bright future for MPE. More than that, it keeps a promise that most customers believe HP has made to them, and that is very much the nub of the moral and ethical question
that faces you now, Winston.

Migrating MPE to Intel hardware would have permitted MPE to run on inexpensive but high-quality servers. Earlier this month, VSI announced a timeline for such a thing to happen with OpenVMS. A different HP paved the way, perhaps chastened by the past, than the corporation that launched the afterlife. In the beginning, the launch of the server took place in this month. The slogan in 1972 was "November is a Happening." Nothing can change what happened nearly 30 years later, but the decisions over what to do with a loyal enterprise customer base have changed in the years since 2001's happenings.

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

October 31, 2019

Wayback Wed: Leaving a Wake on an exit

Chris Gauthier  Jackie at Wake
Simpkins  Nizzardini  Johnson Wake redux
Above, a 2019 commemorative lunch today at Tide Mill Café in Hampton, VA with Terry Simpkins, Al Nizzardini and Tracy Johnson, all 3000 experts and veterans of MPE. 3000s are in use at their company, TE Connectivity. At top, a 2003 World Wide Wake picture with Chris Gauthier and his co-worker Jackie Mitchell, both supporting 3000 customers as contractors to Terix.

Today we're marking the 16th anniversary of the World Wide Wake. The event was a marker of the end of HP’s 3000 manufacturing on Oct. 31, 2003. Alan Yeo, who passed away recently, organized the Wake and posted photos contributed from attendees onto what we were still calling the World Wide Web. A Web gallery for 3000 people was groundbreaking at the time.

Yeo said back in 2004, a few months after the event that drew more than 400 devotees to meetings in 15 countries, “We have created a simple single Web page that by country just lists the venues and who attended, and also has a link to any pictures for that venue," Yeo said. “The information will be condensed into a single Web page, linked to a directory of about 75 images. We have had several offers to host the information, so rather than try and pick a single host, we thought that allowing any interested attendee to host it would be best.”

Thanks to good Web hunting from Keven Miller, the Wayback Machine link to the original Web page tells the tale of who attended, and where, along with some of the photos.

Our own archive of the photos, sans captions, is here on the blog.

The photos from that day look like party pictures, even though nobody in them was celebrating anything except Halloween. The memories were on the minds of everyone in the frame, though. The future without any more new 3000s didn't seem to scare anyone on that day, at least not for the cameras. It was a coincidence that the building of new computers, as well as the licenses for the MPE/iX that made the boxes genuine 3000s, stopped on the spooky holiday. HP's fiscal year ends every year on October 31.

The Wake gatherings were all across the globe. New Zealand was the furthest away from the Epicenter of Grief, as the 3000 faithful had dubbed Lori's Little Shack in Roseville, the town where HP's 3000 factory was ending its birth of the servers. 

Loree's Epicenter Grief

Hundreds of HP 3000 users, managers, vendors and devotees gathered in pubs, cafes, back yards and offices to celebrate the end of something: HP's finale to creating new HP 3000 servers.

On our separate photo gallery page, we've collected some images of that day. The people in those pictures were holding a wake for Hewlett-Packard's 3000s (and a few who believed it was the beginning of the end for MPE/iX). Even today, it's hard to make a case that the server actually died on Halloween of 2003. What ended was the belief that HP would build any more 3000s.

TSG wake
The gatherings ranged from "The Ship" in Wokingham in the UK, to Vernazza, Italy, to Texada Island off British Columbia, to Melbourne, to the Carribbean's Anguilla, and to a backyard BBQ in Austin -- where a decommissioned 3000 system printer and put-aside tape drives sat beside our grill. At a typically warm end of October, the offices of The Support Group gave us a way to gather and mourn a death -- the official passing of any hope of ever seeing a new HP 3000 for sale from Hewlett-Packard.

Company employees chatted with several MANMAN customers under those Austin oaks, along with a few visitors from the local 3000 community. Winston Krieger, who passed away this year and whose experience with the 3000 goes back to the system’s roots and even further, into its HP 2100 predecessor, brought several thick notebook binders with vintage brochures, documentation, technical papers and news clippings.

RadE4A95HP, as well as the full complement of those October customers, continued to use the server during November. And while the creator of the Wake concept Yeo said, "the date does sort of mark a point of no return, and it will be sad," Birket Foster had his own view of what just happened.

“The patient’s not dead yet," he said at the time, "but we did pass a milestone.”

One software vendor even announced new products at the gathering. Steve Quinn of eXegySys said that "We will not be mourning the death of the HP 3000 as much as celebrating the birth of two new products." Both ran on Windows but had deep roots in MPE. Almost 40 people signed in at the company's HQ in Salt Lake City.

The Wake drew the interest of mainstream media in the US and the UK, including some of the first notice from the business press in several years. But no outlets devoted mainline coverage to the impressive array of parties and commemorations; instead, Web-based reports of the Wake appeared from print publishers and ABC News. The Wall Street Journal, Computerworld and the website The Register also reported on HP’s end of sales. 

On the website where Yeo first hosted the photos, Gary Stead of the UK reported in a note he was "looking for a job 1st Nov!" 

But Duane Percox, Doug Perry, Steve Cooper, Rick Ehrhart, Ric Goldman, Mark Slater, John Korondy, Tom McNeal, and Stan Sieler joined HP’s Cathlene Mcrae, Mike Paivinen, Peggy Ruse, Jeff Vance and Dave Wilde to raise glasses in salute at the pub The Duke of Edinburgh, just down the street from HP’s MPE labs. Everybody went back to work on 3000s the next day.

Quinn of eXegySys said his company's new products, while running on non-3000 servers, "both extend far beyond the capabilities of their forefathers." The same can be said of everyone who attended a wake for an HP Way business and an ideal.

Moving onward is natural in a lifecycle. The Chinese philosopher Lau Tzu said "New beginnings are often disguised as painful endings." There was pain in the end of the manufacture of 3000s, the beginning of HP's MPE end. Beginnings happened nine years later, when Stromasys introduced the PA-RISC HP 3000 emulator Charon.

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

October 22, 2019

HP's kids: Children who can't say yes, or no

Merry-go-round amusement parkPhoto by Marjorie Bertrand on Unsplash

Editor's note: Developer, vendor, and advocate Alan Yeo has passed away at age 65 after a lifetime of work for the 3000 community. His essay below was written in 2005 amid the early years of the computer's Transition Era. He wrote about the damage done after migrations were first triggered by HP's 2001 pullout, then postponed on a fuzzy timeline from the entity the community was calling the virtual HP division for the server, vCSY.

Vendors like Yeo who weathered HP's stormy strategy took on a lot of water because of HP's revision of its end of service deadline. Yeo's use of metaphor and allegory here are a fine tribute to his wit and intelligence that the world has lost. ScreenJet, his company, followed his insight to survive the turmoil.

By Alan Yeo

That's it, children, just give the merry-go-round another shove, just when passengers thought it was stopping and they could get off it and get on with planning the rest of their lives. Oh yes, some of the children will be happy; the period before they have to decide which ride to take next has been extended. But for the adults either already behind schedule, or struggling to get attention-deficit children to concentrate on important decisions, it's just another frustrating delay.

Now it wouldn't be too bad if the very Careless Stupid Youngsters ("vCSY") nudging the merry-go-round on weren't the same vCSY who had planned its retirement, and had then encouraged its customers and partners to seek out new more exciting future-proof rides. But no, to compound the disappointment they caused their passengers when they announced the ride was ending, they now have to say, “We lied, we didn't mean it, the ride's not ending yet!”

Is this because they think their passengers are still having the best ride in the fair? Perhaps they think they can just keep it spinning under their control for a while longer, that there are another 3000 pieces of silver to be extracted for their parents, the only Happy Party ("HP") in this.

And what of vCSY partners, and the encouragement they received to help transport the passengers to other rides when the Merry-go-round stopped. Or even those they encouraged to build an organisation to help those passengers that wanted to stay on the Merry-go-round and even maintain it after the ride had stopped.

For yes, there was an organisation of such Open Minded Passengers Established ("OpenMPE") that hoped to provide counseling and support for those who chose to stay, and even to build a work shop to repair the Merry-go-round Physical Environment ("MPE") for them. What of OpenMPE's chances now? Why would anyone invest in them when they need it, if the HP and vCSY are going to keep the ride spinning and the MPE supported?

And what of those who vCSY encouraged to build the transport for the passengers to other rides — their parents (the HP) had no transport of their own. Those vendors built the busses the planes and the trains, and even migrated some of the passengers to new rides. What are they to do now, just sit there with the engines running for a couple more years whilst the merry-go-round spins on?

And what of those partners vCSY encouraged to build infrastructures to keep old merry-go-round's functioning and provide support for the MPE? For them, the ride has been delayed for two more years, and it has reduced the number of potential passengers to the point where it may not be economic to hang around and wait.

And what of those passengers who vCSY forced to flee early to other rides, with threats of a failing ecosystem and that the ride would become unsafe unless they left before the cock crowed at the dawn of 2007? Was their journey unnecessary, in pointless haste, and to an earlier or higher cost than needed? If some of them felt pricked when vCSY announced the ride was to stop, some of them will surely feel stabbed in the back by the HP who lied.

So what can one say about these children, those who can't say Yes, can't say No, and for whom Maybe is a mantra. Would you trust the support of your merry-go-round to them now? Would you trust them to help enable an ecosystem to maintain the MPE after they finally tire of it? Would you believe them if they told you Y2K came after 1999?

As for me, I would no longer give them the time of day, far less ask it of them, for fear they would get it wrong. What's so unfortunate is that it would be much easier if one could believe that there was some great conspiracy within HP and with vCSY to completely jerk both their customers and partners around. But as someone else has said today, “plain stupid" beats “malevolent" most of the time.

And what do vCSY think they have done for the passengers on the Merry-go-round by keeping it spinning for another two years? If they actually had the ability to support the MPE it would be fine, but the average third party ISV now retains more expertise than the whole of vCSY. A third party will also know what a merry-go-round is if you call them, and will probably charge far less than the HP if you need spares or repairs for your merry-go-round.

This statement is subject to limitations and exclusions based on exact merry-go-round configurations, geographic location, ride transition timelines, and other considerations. All characters are fictional and not intended to portray any person or organisation living, dying or dead.

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

October 17, 2019

Alan Yeo, 1954-2019

Yeo at Reunion

Alan Yeo, a software vendor and developer whose business ultimately led to success as a nexus for the 3000 community in its Transition Era, has died at age 65 after a battle with a small cell cancer. He is survived by his wife Helen, a lifetime of creations he designed with partners, and a gripping voice that gathered and rallied MPE customers after HP quit on their marketplace.

Yeo’s company Affirm, Ltd. rose up in the 1980s as a resource for manufacturers who used the HP 3000 to manage their enterprises. He served a group of customers across the UK and began to move in wider circles with the advent of ScreenJet, his software to modernize the 3000’s bedrock VPlus application interfaces.

ScreenJet arose in the years just before Hewlett-Packard scrapped its business developing 3000s and MPE. While the HP decision left Yeo undaunted in his business aspirations, it also led him to a new role as a leader for a 3000 community that was dissolving after the implosion of the Interex user group in 2005.

His first effort surrounded the final date of HP’s manufacture of the system. On Oct. 31, 2003, he organized and led the HP 3000 World Wide Wake, a collective of gatherings to celebrate the server and the people who’d made it their life’s work. Across North America and Europe, customers and managers held parties and met at pubs, bars, and restaurants. Photos from the events poured into a web server that Yeo hosted. Earlier in the year, Yeo asked out loud where else the HP 3000 community might gather in a user conference — a question he posed in a meeting at the Atlanta HP World, where few 3000 customers had appeared.

In the year that followed, he shared his strategy of being a master of one. It was built around the nugat of collaboration that led to his ability to connect.

"We’re starting to see more collaboration between migration tools providers and migration service partners," he said in a NewsWire Q&A. "To get some of this stuff right, you really, really need to know it. I think it’s too big for any one person to do anything right. If you want good fish you go to a fishmonger. If you want good meat, go to a butcher. If you just want food, go to Wal-Mart, and if you just want to eat, you go to McDonalds."

Community meets and reunions

Many of the stranded customers using the HP 3000 got an introduction to Yeo’s voice in those first years of the 3000’s Transition Era. He commissioned an editorial cartoon during 2002 that became a mainstay in his company’s ads, one built around the HP move to end its MPE plans and sever relations with the thousands of companies that grew up using the 3000’s extraordinary solution. The CEO of the company at the time, as well as the 3000 division’s GM Winston Prather, caught the brunt of the brilliance in a cartoon that compared killing off HP's 3000 futures to the evil in a Disney movie.

WinstonDalmations
A few years later, after the user group Interex folded its operations overnight and stranded users’ plans to meet at the now-canceled annual conference, the first of a series of Community Meets sprang up for 3000 owners. After an impromptu gathering in the Bay Area for community members already stuck with nonrefundable hotel reservations and air tickets, a single-afternoon lunch gathered several dozen managers, developers, and owners.

The first Bay Area meet was replicated and expanded twice more with single-day meetings in 2007 and 2009, organized and underwritten by Yeo and his business partner Michael Marxmeier of the database and language vendor Marxmeier Software. Other companies contributed to cover expenses, but the largest share of the organizing always went to Yeo.

In 2011, he and Marxmeier teamed up with some help from the NewsWire to mount the HP3000 Reunion, a multiple-day event with a meeting at the Computer History Museum. In addition to seminars and a group tour of the exhibits, a catered dinner, a briefing on the upcoming 3000 emulator, and a meeting of enterprise resource planning software users made for a busy weekend with dozens of community members.

Alan_Yeo_at_Reunion
Yeo was pragmatic while keeping his lights on for every software customer who’d invested in his products. Marxmeier Software has taken over support and services for ScreenJet Ltd. in the wake of Yeo’s death. ScreenJet and Marxmeier Software have had close ties for a long time. Yeo was a valued board member for Marxmeier Software and Michael Marxmeier is a director at ScreenJet.

To ensure the continuation of ScreenJet products and services, as of June 2019 support, license renewals and upgrades have been administered by Marxmeier Software. "This will not affect any ScreenJet customer product licenses or agreements which will remain with ScreenJet Ltd," said Marxmeier. "The teams at ScreenJet and Marxmeier will combine their long time experience and resources to guarantee efficient and reliable ongoing support and services."

Alan Yeo with dogsWith his beloved dogs at his Gloucester home

Ever-prepared, Yeo worked out the details of a smooth transfer over the months when his cancer recovery had failed. He'd rallied after treatments and recovered enough to race vintage cars on rural road rallies in 2018. In his last months the disease progressed to cut off motor functions of one arm. He resolutely typed long messages one-handed.

Failures were always a topic he could approach with candor as well as compassion. “Most software on the HP 3000 was too expensive, compared with other platforms,” he said in a 2004 interview examining the collapse of HP’s ecosystem. “However, because people could reliably write applications for the system, many of these were developed far too cheaply. Many customers got far too much for the money they actually spent.”

A reach for personal connections

The ScreenJet product was a recovery from a valiant effort to make the 3000 a vital part of the dot-com PC world. Millware was to deliver software that gave 3000 customers a way to make their VPlus interfaces behave like modern graphical interfaces. The software was to be free in exchange for giving over some of the screen real estate to messages from vendors. Before that user base could be established, dot-com computing staggered, a blow to the vendor element of the formula.

Yeo also picked up the pieces from the effort to market ScreenJet, developed as a connectivity product and sold by Millware.com until that marketing company went bust during the dot-com implosion. ScreenJet earned an award for migration solutions from Acucorp. But for all of his effort toward helping migration customers, Yeo was clear-eyed about 3000 transitions. ScreenJet achieved its best technical release just one month before HP announced its withdrawal from the 3000 market — and the product’s development up to that point was not driven by any need to move companies away from the platform.

Yeo also took a role as producer in a new feature for 3000 customers long abandoned by HP: Transact users. The advanced development language was kicked to HP’s curb in the middle 1990s, but sites continued to run extensive Transact applications, long after the “strategic” badge fell off the language. The TransAction software from his team give Transact sites service and tools to move programs to COBOL, a way to prepare for the journey away from the HP 3000.

Marxmeier, who reached out to break the news about Yeo's death, said he would miss his ally's organizational gifts, but even more so, Yeo's ability to write and speak with, well, eloquence. After drafting a heartfelt letter to inform the ScreenJet customers about the founders' demise, Marxmeier said he already felt a gap in the story. "It's something I would have liked Alan to read, before I released it," he said.

Yeo said he wanted no florid speeches of eulogy at his passing. Months before he died, he said if there was any afterlife at all, "I could be a little sprite, one who could occassionally make it rain on somebody who was being pompous, that would do me quite nicely." It's fair to say his narrative for the 3000's transition era was rich with the words that rained on misfortune and miscalculation.

Carly_cartoon_dalmations

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

October 14, 2019

How to make databases live past shutdown

Index card file drawer
Photo by Maksym Kaharlytskyi on Unsplash

In 2011, a systems manager for the power utility at the City of Anchorage was looking toward a shutdown of the municipal HP 3000. It's a situation that surfaces from time to time even now. Back in 2011, the manager could see another 10 years of useful service for the 3000. His management had other ideas. This might sound familiar.

Wayne Johnson said, "We have an HP 3000 that we are going to decommission, sadly. I have powers that be who want it turned off sometime next year, although I think it will be longer than that. Is there a service that will read DLT IV tapes or convert them to some other usable format on a Windows platform or some Unix server?"

He went on to say that most of his data files were TurboImage database files. They were for archival purposes only. "Of course, the simple solution is to run the HP 3000 N-Class, probably for the next 10 years. It never goes down. But that call is not mine to make. They want to unplug it."

Alan Yeo of ScreenJet supplied a database tape migration solution that still works today.

"One very simple but elegant solution is to get a copy of Marxmeier's Eloquence database which is very inexpensive for your choice of Windows, Linux, or HP-UX and just load the databases in. Then either with the Query3K tool or with ODBC, you can just access the data as and when required.

"You could copy the volume sets to Network Attached Storage. I'll make a bet that the smallest NAS device you can buy for less than $400 will comfortably store more data than you managed to create on the HP 3000 in its lifetime.

"Allegro has a product, Rosetta Store, that will directly load Eloquence from databases in STORE format on tape, if you want to skip the step of restoring from the 3000 tapes and then unloading for import into Eloquence. I think the Allegro product will also do flat file conversion."

Beyond the Marxmeier and Allegro software, there was another suggestion offered in 2011 about a product that has come to change the way MPE databases live on beyond hardware shutdown. HP's iron, after all, isn't the final resting place for 3000 applications and data.

"Before you scrap the N-Class," said Tracy Johnson, "you may want to take note about its details. It may qualify for a license transfer to the up and coming 3000 hardware emulator by Stromasys." 

"Thus in theory, you could keep your IMAGE data running on some Intel platform, as is."

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

April 15, 2019

Taking a Stab at the Size of Your World

10 000th
In 1982, 10,000 servers shipped was a milestone at HP

This month our friends at Stromasys are building a roadmap of the best prospects for their emulator. HP customers have been showing up for years. The software there will soon include a Unix PA-RISC edition of the Charon emulator, too. It's designed to bring the same kind of longer future to companies running Unix on the classic RISC systems that HP released alongside HP's 3000 iron.

Just as a note: The HP 3000 customer who's not on the final generation of Hewlett-Packard hardware can use Charon to replace Series 900 servers. We're always suprised and a little pleased when we see a Series 928 holding its own in a world where more and more servers aren't even on-premise. Cloud-based emulation is an option for replacing old 3000s, too.

Analysts might be surprised at the use of hardware a decade and more in age. The 3000 was never the biggest share of HP's computing, in terms of numbers of systems. Where the 3000 has always had the edge has been in hardware durability. That longevity has been underscored by sound design of the OS. The HP iron is expiring, leaving the operating environment as the durable asset for businesses still using it.

Again: Do not think only small companies are using MPE/iX in 2019. Stromays knows about the size of prospective emulator customers. The nature of the product's pricing suggests that significant companies have emulated the HP 3000 iron. Now an HP-UX market could mean hundreds of thousands of more systems they might emulate. Unlike a 3000, a single 9000 installation could run to dozens of servers.

Why care, as a 3000 customer? Well, the fact is that any extra connection to HP business servers, no matter what the OS, will be good for the future of Charon — and by extension, the lifespan of MPE/iX. That's PA-RISC being emulated there, regardless of the 3000 or 9000 designation.

How many PA-RISC boxes are out there to emulate? It's all educated guesses. Once upon a time, HP cared about the number enough to assemble employees outside the Roseville manufacturing facility to celebrate the first 10,000 in the photo above.

Nobody knows those numbers for certain, in truth. The size of the 3000 world has been an exercise in estimation as long as there's been MPE servers for sale. There are Gartner estimates to estimate the total HP systems sold — and of course there’s no Gartner numbers for the 3000 in those reports.

It’s been encouraging to see the effort to quantify a market like ours. The MPE market has been losing customers for two-thirds of the time we’ve been writing about it. We’re all guessing about legacy lifespans. But they can surprise us.

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

April 08, 2019

Where to go for better 3000 census numbers

10 000Cover
Thirty-seven years, ago, HP celebrated 10,000 servers sold. PA-RISC was still five years away on the day everybody stood outside the 3000 HQ at HP.

Outsider estimates on the size of the 3000 market are going to be flawed. By outsider, I mean the ones that come from analyst companies, such as the ones that IDC prepared in the 1990s and early 2000s. Nobody can really be sure where that data came from. You can only hope they've talked to firms who were actively selling HP 3000s.

Those companies didn't have an HP address. Most of the 3000s were sold through resellers and distributors. This was a small business solution, in so many cases. Not that there aren't servers running in places the size of Boeing. But for every Bullard — makers of the iconic hardhats with three ridges — there were three or more companies like Peerless Pumps, or even a good-sized but not giant company like Disston Tools.

For the 3000, though, it was never about the numbers of servers. The tally of companies was more impressive. A Unix shop could have a few dozen HP systems, because the nature of the Unix world was to dedicate a server to each application. A single 3000 could host many apps.

In searching for better data on how big the 3000 market might be, I reached out to Steve Suraci of Pivital Solutions. A 3000-focused company, Pivital sold 3000s and is among one of the freshest resellers of servers. Suraci said HP had a number which they used while describing the size of the market.

"I recall HP telling us there were 20,000 to 25,000 units in service at the end of [HP's] 3000 life," Suraci said. "That was the last time I recall hearing anything close to official."
 
Considering how hard HP sold its Unix servers against the 3000 base, it's remarkable that anything that big could show up on HP's hardware tally. HP's "end of life" could be calculated from the end of manufacturing, or even the end of support for MPE/iX. No matter where the line is drawn, that's a lot of worldwide systems to be shut down over the last nine years. Even an 80 percent shutdown rate would leave the census at 5,000 servers.

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

March 18, 2019

Curating a Collective of MPE Advice

70and930
LinkedIn is the Facebook of business professionals. The service operates as a de facto resume repository; business people who search for jobs are often invited to use their LinkedIn profiles to provide a CV.

The service is also a collection of groups. Several are online as HP 3000 meeting spots. One is a private group that has served 3000 needs from inside HP. Nineteen members make up a group devoted to the Empire role playing game that runs on MPE and MPE/iX systems. A Connect HPE User Group Community is at LinkedIn; lots of members in there have HP experience that includes no MPE expertise.

Then there's the 677 members of the HP 3000 Community. I started it 11 years ago when LinkedIn was popular but not so essential that it was serving up resumes. We had 80 members in a few months and several hundred a few years later. The group is still growing. It's not growing as fast as some applicants to it would like, however.

LinkedIn still gives group moderators the choice to curate members of a group. The HP 3000 Community has always been a curated group. I remember a complaint a few years ago from an applicant. "He only approves people with have HP 3000 experience in their work histories." Indeed. There are a smattering of recruiters among those members, but nearly everyone on the group has worked on or with MPE.

LinkedIn gives groups a platform for publishing content, as well as forums for open discussions. There's a nice link at the top of the current feed about a Stromasys white paper, one that explains hidden costs of operating HP's MPE hardware. These are not the main feature for the HP 3000 Community, though. The 3000-L mailing list and this blog serve those needs better, but we're always glad for new content anywhere in the community. LinkedIn's group is the biggest collection of curated MPE professionals by now. If you're looking for someone who knows your environment, it's a good place to begin

And if you're not yet a member, stop by and apply. The door is always open to pros who can count upon MPE knowledge as a way in.

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

January 28, 2019

MPE vendors walk wooded path into futures

Forest-931706_1280
The HP 3000 world has been active long enough to see death visit the floors of its forests. Death is the great leveler in a crowded forest. Trees that go down provide rich soil for their survivors to flourish in. Software, the trees in the ecosystem of MPE/iX, has been growing and declining for decades now.

The community still ripples with products for development, for management of data, and even some off the shelf applications. There's less rippling today, of course. It's the result of the operating environment's abandonment by its creators. When you tell the world as HP did more than 17 years ago, "We're leaving this market," then products begin to retreat. So does newer and younger talent.

Such a retreat was also a natural event while HP still plied its 3000 trade. A company would shift focus away from the 3000 market, like Aldon Computing did when it embraced the AS/400. In some cases, a vendor would be acquired and the products stripped out of the new owner's list. Infor has retired many a software suite for ERP, although MANMAN has survived that fate that other Infor products have endured. In one case from the earliest days of the NewsWire's sponsors, the owner died and his widow had no succession plan in place. Cosmosoft was a casualty.

A more current event will be the retirements of small and focused companies, operated by a bare handful of experts. It's good work to be serving customers of many years. At some point, though, some of the majordomo managers of software vendors will earn their retirements. A report in Bloomberg News today says that 24 percent of all people 65 and older in the US will continue to work in 2019. Some of them will be software vendors and programmers. A lot fewer, though, than the food service or retail workers in that age group. Check the age of the experts at Home Depot if you disagree.

When a software vendor retires, without much prospect for selling its products to another software company, something's got to be done for the customers using the products. In the past this has been managed with a donation of some kind to a vendor who's friendly enough to keep answering the phones or emails on support issues. Sometimes a product can move into a free status — it's happened in the job scheduling segment, for example.

Expect to see more of this as the market matures. Make a plan, if you're one of the Double Digit MPE managers headed beyond 2027, to see what your software providers have in place. Lots of the software vendors who know MPE/iX are using a workforce in their 60s. A retirement of a key technical resource can trigger new plans for the product's future. Stay in front of this development. These engineers of enterprise are aging. Some can afford to park their products.

This aging of the 3000 marketplace has been the genuine current carrying companies toward migrations. Nothing was permanently wrong with MPE tech when HP pulled out of its futures. The years that have elapsed since then have done nothing to turn back the hands of time. Everything ages. The wetware of the wizards is not replicated easily.

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

January 14, 2019

How far behind is MPE/iX, really? One look...

Start-finish-banners
Ten years ago a system admin who used a 3000 explained why emulation seemed to be a bad idea. In the era of 2009 there was no software to emulate PA-RISC processing on an Intel system. The problem really didn't need repairing, said James Byrne of Harte & Lyne, because "The world has moved on considerably, since 2001, while MPE/iX has not."

At the time his firm was still using two 918LX systems, a primary and a hot spare at an off-site location. Many a 3000's life has been extended because one key application was working with no need to invest in it. There were other things to be said about the suitability of MPE/iX now, as well as 10 years ago. There are things to be said in reply, too, because in life and IT, few things are as straightforward as they seem.

One expert who's supported HP 3000s and MPE is Donna Hofmeister. In 2009 as well as now she supports companies at Allegro. Byrne's problems with MPE/iX in 2009 as well as today didn't seem quite as serious when she examined them. Caution is required while using an operating system that was last patched a decade ago. As in traffic signals, caution does not mean stop.

Even in the year 2009, when I pointed out that seven-plus years of no emulator didn't mean "no emulator, ever," Byrne kept to his course. "It does seem to me the prudent way to bet nonetheless," he wrote me. Whether you believe in an emulator's promise or not, MPE/iX is the deal-breaker here in 2019. It doesn't have as many fundamental shortcomings as it seemed a decade ago. I asked Donna about it, saying "Here we are in 2019, still caring about the 3000 and its OS. You could’ve won a good bet about that one."

Nobody is doubting that the world has moved on since the end of 2001, but "there are still plenty of companies running MPE." Hofmeister adds that "MPE is not as up-to-date as other OSes. There are ways, however, of dealing with that."

In 2009 Byrne said that "Basic FTP and Telnet are inherently insecure and increasingly discarded methods of data transfer. SSL with SHA2 or SHA512 encryption is a de facto, and in many instances a de jure, requirement for business data communication between hosts and even for inter-process communication on unsealed servers."

As far as Hofmeister knows, there is no solution for the Telnet issue. "But for FTP there is SFTP -- freely available from Allegro's website. Yes, it's old but it works and addresses the 'no plain text' issue."

Languages for development looked like a problem 10 years ago.

Compiler-driven languages are all but completely replaced in new business application development by interpretive, and processor intensive, virtual machines (IVM) such as Java, PHP, Python, Ruby and so forth.
"There's absolutely no reason that an MPE system can't fit into the above pardigm (oooo, I just used that word!). Rather than depend on a human or batch, applications can be 'revised' to respond to external request. Yes, it takes work but "good hard work never hurt anyone", right?
 
Mombi
"Mombi is one of our MPE systems. The list on the right is all the things that our Nagios server is monitoring on Mombi. Yeah, the 'Industry Standard In IT Infrastructure Monitoring' is happily watching the 'health' of an MPE system. Did it take rocket science to make this work? No...just a wee bit of coding, some design specs and a lot of testing.

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

December 31, 2018

Date upgrade deadline: now in single digits

Countdown-9
When MPE/iX systems, both virtual and physical, see their clocks tick over tonight at midnight, it will be a significant date. The end of Dec. 31 puts MPE/iX, as crafted by its creators — into single digits for years remaining. Nine is tomorrow's number.

Whether that's nine years until end of life depends on your IT plans. If like more than a few managers you're retiring clean -- with configurations in place to survive into 2028 — the nine years will show you're prepared. You've made your changes to work around the loss of accurate MPE/iX date keeping. At least one vendor is taking orders for this service.

Others, meanwhile, are doing the work and leaving the credit to others. Stromasys has a lot at stake in the 3000 market to make 2028 a year of smooth pavement. We've gotten word they're ready with a software solution to carry MPE/iX beyond HP's wildest visions.

For the IT manager who's retiring without a 2028 plan — and leaving Dec. 31, 2027 as a shutdown date — tomorrow is the start of the final nine years for that HP 3000. It goes without saying these managers have no current interest in the Charon virtualizer for HP's MPE/iX iron.

Everything ends sometime. 2018 wraps up this evening. Lau Tao wrote in another century, "New beginnings are often disguised as painful endings." May your year to come be a new beginning without such pain. We'll see you in a future where options are still emerging for a suprising decade-plus to come. Some 3000 managers will be joining the march toward a Double-Digit Future for MPE/iX.

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

December 17, 2018

What to say back to "Your system sucks."

Rolling-stones
There are still moments out there waiting for the homesteading 3000 manager. The ones where someone in IT who's pretty sure they know better about systems says something like "MPE sucks." Or anything equally glib, dressed up little to hide the ignorance.
 
"MPE sucks" is something like "the Stones were hacks." It’s a matter of taste and what you know. There’s too much legacy software out there doing production work to dismiss anything out of hand. I find that the more technical the IT administrator, the more they seem to like the clean choices, those with shorter pedigrees and clearer parentage. MPE/iX, being in its late 40's of existence, feels like it's just too out of date.
 
If that were true, then a company like Stromasys would have failed at selling an emulator into the MPE/iX marketplace. Charon is working and moving data where it needs to go.
 
I’ve talked for thousands of hours to people who cut code and build application suites. The dance between developer, administrator-CIO, and end user is interesting and frustrating. Using something older is not an ignorant move. What sucks, if anything, is a tunnel vision about the best tool to preserve a company's investment.
 
I've read the following in the last 24 hours, shared by a vendor who really needs you to see that cloud IT is your next best future.
The person in charge of the software isn’t generally involved in the day to day. The only thing they know is that the job is getting done, and “If it ain’t broke, don’t ax it.” They’re too removed to realize that it is broken, and there’s no one questioning them about whether something could be done 20 percent faster or 10 times easier.

Neither of these stakeholders is in a position where they can see the problems. What
they need is a different perspective.

When a different perspective can respect the investment in MPE/iX, and acknowlege how much less faster or easier an alternative is once you factor in the cost of change — then it might be time to talk futures and alternatives
 
People like the tools that they like. I don’t try to win the PC vs Mac debates anymore. It does annoy me to see a tech expert dismiss something. I have a friend who loves Android and slams iOS, who uses Linux and hoots at Windows. For him, the ability to flip a million software switches and manage his own filesystem is the smartest way to go. The 3000 marketplace started to see this when SAP crept in to try to replace MPE/iX. That's why Kenandy has been able to stand in at a few 3000 sites. Its switches are already set in positions that let work get done.
 
Advocates of the more complex choices usually don’t understand how smart they are in relation to everybody else. I encountered this in our editorial business just a few days ago.
A colleague who's a website developer belted out that "Wordpress sucks" stink bomb. To veer into the weeds on editorial and author websites, I'm one of the many who use Wordpress to manage content — blog entries, pages for books or services, and more. Wordpress is classic and yet evolving, and it's everywhere. Some might think of it like a legacy choice. The alternatives for content management are harder to customize. Joomla is that's colleague's favorite. For me, it was the bad, beautiful girlfriend who never felt safe.
 
I tried to make Joomla work for more than three years, but it was impenetrable. Some of that was probably my build-out of its theme, some my unfamiliarity with Joomla (I know WordPress dashboards and plug-ins much better.) I didn’t cut code. I made content and thought up business practices.
 
Keeping a website in clean enough shape to remain useful is not automatic, not in 2018. 
 
It didn’t get better once the Joomla site for the Writer's Workshop got injected with malware scripts. Twice. I changed hosting and got an intermediate firewall company (SiteLock, $60 monthly) to make the security problems go away. 
 
Like an MPE/iX customer who's finding problems with hardware, I had to get my resource chain in order. My new host auto-updates my WordPress (and believe me, I know people are trying to hack into WordPress. It’s everywhere, like Windows) and my new webmaster wants to secure my site as much as I do.
 
Insisting on control and customization — like the MPE/iX customers must, because they're supporting decades of data — makes things stickier. My challenge with website user experience is I learned publishing in the paper era. We controlled every user experience because the medium was the same everywhere. Losing control, and giving myself over the the dynamic nature of web, still annoys me. Three different sizes of smartphones, and two mobile operating systems, plus the vagueries of browsers, alters everyone's the experience.
 
Don't let anybody tell you your legacy choices suck. IT can sing from more than one set of chords.
 

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

December 05, 2018

One Alternative to $1 Million of 3000 Costs

Charon Portfolio
In a webinar this week, Stromasys made its case for how shutting down HP's 3000 hardware can reduce an IT budget. Using data from Gartner analysts and other sources, the company estimates that downtime costs companies $1 million per year on average. Any alternative to 15- to 25-year-old servers is a good shot at making the future more stable.

There still hasn't been a computer system built that will never fail. Hot-swap backups with automatic server failovers were never a big part of the 3000 datacenter experience. If you had to handicap which server was a likely failure candidate, HP's MPE/iX hardware would give you short odds of failure. In this case, short is not a good measure.

One million per year in losses is a big enough number to get the attention of a corporation's C-level. It's the same number, coincidentally, that Stromasys used this week to describe the costs of migrating MPE/iX apps. The text circled in the slide above "implies investments of $1 million+" for migrations.

These millions, lost through downtime or surrendered in datacenter budget, are averages. Smaller 3000 customers may not approach the $1 million in yearly lost revenues. Migration costs track closer to that number, but they're a one-time hit. The alternative is Charon, of course. During the webinar we learned that an additional HP market is coming online to use Charon. HP's Unix PA-RISC servers will be the latest Stromasys virtualization segment, according to Dave Campbell.

There's no specific release date for Charon's HPA-9000 version yet. Such a product has been hinted at for a long time and rumored to be in development more recently. Stromasys needs the cooperation of the system manufacturers — HP and Oracle, to be exact — to bring out a virtualization of the old vendor hardware.

The news of a new virtualization marketplace tells us that replacing aging hardware with virtualized systems running on modern iron is a growing business. It may not even be growing as fast as it could. One customer on the webinar asked about IBM AS400 (Series i) virtualization. Campbell noted that the vendor's participation is essential to making another edition of Charon.

IBM may not be ready to help AS400 users for some time. Their POWER-based iron is still being built and sold. The only hardware still being built to support MPE/iX today is Intel x86-based, the platform for the Linux+Charon solutions. There can be millions of reasons why newer hardware plus the cost of Charon software would leave a customer miles away from failures. Charon isn't inexpensive, but when compared to $1 million for an MPE/iX user, it may feel like a better choice for a legacy budget.

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

December 03, 2018

HP 3000 dream tracks close to virtualization

Railroad switches
An HP 9000 HP-UX virtualization product is in development. In that kind of design, a single Intel server with enough computing power (concurrent threads) could host both HP 3000 and HP 9000 virtualizations. HP had the same objective almost 20 years ago for its largest enterprise platforms.

Early in 1999 HP's Harry Sterling spoke at an all-day user meeting in the UK hosted by Riva Systems. Sterling, who'd retire before the end of that year, said a multi-OS server was within HP's vision for the 3000 and 9000 customers.

Sterling’s mentioned the possibility of running MPE, NT and Unix concurrently on the HP 3000 "sometime in the future." There was even the possibility of a “hot-swap” version of MPE alongside the production system. John Dunlop reported for us at the time.

The passing mention indicated that separate processors in one box would be able to run different operating systems. Sterling did suggest that a hot-swap version of MPE might be a valid use, so that there would be some redundancy with the live operating system.

This seemed to lead to the subject of more uptime. From these comments, it’s possible that HP is looking at allowing online changes to a hot-swap system and then just switching it over to achieve the so-called “magic weekend.” This is a system upgrade that occurs seamlessly and transparently to both the users and management.

That would be a dream not realized. Hot-swap didn't make it any further into the customer base than architect discussions. Sterling noted that in 1997 customers expressed concern about the future of the 3000. To counter that feeling and give the customers more confidence, he outlined in 1999 a five-year roadmap for the 3000.

Marketing was on board as well in that year that led to Y2K. It would take another 13 years before a multiple OS host for MPE/iX would emerge.

Marketing Manager Christine Martino told that crowd about HP’s commitment to the 3000 by hiring more MPE engineers and setting up of new centers of expertise. There was also to be a higher investment in training and education. Finally, she stated that HP was running over 650 HP 3000s to power core Hewlett-Packard corporation business applications.

By now it's going to be 20 years on to the promised land of one host for Unix and MPE. A big enough Intel server — and it might well be one that will evoke enterprise iron costs — could do what Sterling proposed before he retired. All it took was the cooperation of HP's engineers to release internals to emulate PA-RISC systems for Unix and MPE/iX. Those are legacy systems by today, but at least there's an independent software vendor to make the twin-OS dream a possibility.

Posted by Ron Seybold at 01:28 PM in History, Migration, News Outta HP | Permalink | Comments (0)

October 05, 2018

Shifting Data Off the 3000, Easily

NewsWire Classic

By Roy Brown

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

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

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

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

Extraction

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

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

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

Formatting in WinWord, Part 1

Then I use WinWord to open the .txt file that Reflection has built for me on the PC, and Edit/Replace to change ###^p to one space throughout. Bingo! One long line per returned entry.

How does this work? Well, ^p (caret p) is WinWord’s code for a paragraph mark, which is how each line in the data is terminated. So I’m saying “Find each line ending in ###, and chop off not just these characters, but also the line ending itself. And then put a space in, to make sure that doesn’t cause two fields to run together.”

If you open Edit/Replace, choose the More tab and then the Special tab, you will be able to see the list of formatting characters you can search for and replace. Paragraph Mark is at the top, and right below it is Tab Character; click this, and you’ll see caret-t appear in the ‘Find what:’ window. There are 20 options there in all, but ^p and ^t cover pretty much 99% of what I need to do.

I top and tail my output file to remove the original query lines, and the >end at the end. Sometimes, I might then sort it, with Table/Sort and the default options there, to get the detail records in order. But generally, WinWord’s sort runs out of steam with a file that is more than a few megabytes, so I wait until I’m in Excel.

So I Save As on the WinWord file, taking care to keep it as a .txt file, and ignoring WinWord’s warnings about ‘losing formatting’ if I do. WinWord’s formatting is exactly what I don’t need; .txt is the most versatile format for use here.

This excursion into WinWord has really just been to de-block the detail lines, a task which is straightforward here, but nigh-on impossible in Excel. But we’ll find, in turn, that there are things which Excel can easily do for us, while in WinWord they would be nigh-on impossible.

Formatting in Excel

Next, I open up Excel, and File/Open my .txt file, setting ‘Files of type’ to All Files so I can see it. Excel comes up with its Text Import Wizard, a most powerful tool that lets me break my file up into individual fields.

The option to use here is Fixed Width, and Excel guesses where the field breaks are. It usually does this very well, providing the fields have spaces between them. But if not, I can add, remove or move the suggested breaks.

Moving on with Next, I can set the format for each field. Again it usually guesses these right, except for those CCYYMMDD dates. But for those, I just choose Date format, and the YMD option, and it will convert them to Excel dates. On completing the Wizard, I have my data, field by field, neatly arranged in Excel columns.

By the way, I could have just Copied from my WinWord file, and Pasted into Column A of the Excel sheet, and then split that. The wizard is available under Data/Text to Columns, for just that purpose.

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

October 01, 2018

Where have all the migrations gone?

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

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

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

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

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

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

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

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

September 28, 2018

The Migration Dilemma

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

Newswire Classic

By Curtis Stordahl

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

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

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

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

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

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

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

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

Packaged app migration

Many organizations will be lured by the promises of packaged software vendors. A package reduces migration risk. But this isn’t like just plugging in a new e-mail package.

The biggest risk factor is going to be implementation. Instead of building an application to conform to your business, you must make now make your business conform to the application. Managers outside the IT organization must buy into this and revise policy and procedures accordingly. So much is needed outside the IT organization to make it work that it must be managed from the executive level. If there is insufficient commitment at the executive level, then the project is destined to fail.

Training users is another risk factor. If you train too early you risk losing them through attrition before you implement. If you train too late, they may not be able to retain and understand what is expected of them.

 

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

September 26, 2018

Why and When to Leave Platform-Land

Goodbye Tin Man
Life in the 3000 community revolved around platforms. We used to think about these as operating systems. Long ago it was time to change that thinking and call the combo of servers and the OS a platform. You could think of that era as the Land of Oz, instead of OS. It might be time for 3000 owners to change their thinking about computers as platforms. It depends on what else is doing service in your datacenter.

For a small percentage of 3000 owners, the servers built by HP are all that runs in what we once called the computer room. They live in what one storage vendor, one who knows the 3000 well, calls platform-land. Everything in platform-land is connected to a 3000, so the homogenous benefits of multi-server storage just aren't needed.

Companies that live fully in platform-land are using HP-branded devices built exclusively for the 3000. That's the way HP used to qualify its peripherals: tested for MPE/iX. For a while during the years after HP's "we're outta here" announcement, the vendor asserted that any other storage device was risky business. We covered those debates. The results showed the risks were not substantial.

HP's outta-here movement caused movement in the 3000 community, of course. Some of the movement was inbound instead of an exodus. Companies have turned to using Linux servers, more Windows Servers (2008 and later) and even some Unix boxes from HP, Sun, or IBM. That's the moment when a company starts to leave platform-land. You should leave it once you've got multiple OS servers and need to leverage networks and peripherals across all servers. That's the When.

The Why is a little more complicated. 3000s and the Stromasys servers that have replaced the MPE/iX hosts are cradles for the applications that companies don't want to drop. The companies shouldn't drop an application just because it's on the wrong platform. Applications need to exit when they don't serve the business logic anymore. Leaving platform-land supports the continued service from MPE/iX apps. Like I said, it's complicated.

What we know about managing IT in the year 2018 is that it's complex in a way we couldn't imagine in the 1980s and 1990s. The diversity of devices is what's changed the community for good. Even HP began to understand that a multiple-platform storage device was a better value to anyone who didn't live in platform-land.

For almost all of the HP 3000 customers left today, their server isn't the only box in the shop. They have added Windows, Linux and Unix, yes. More often, those operating systems aren't part of the decision loop. We always said that it was the applications, stupid, when deciding what computer was going to get the assignment. The 3000 survives because of its apps, but its survival is beset by more than the calendar pages slipping away. The differences in connected devices chip away at the 3000's rightful place. 

Oh. Not only do we have to try to retain MPE/iX expertise, we also have to keep that Jamaica disk set running. A set that does nothing else for everything else in the datacenter. When it fails, we have to find a replacement for that device with moving components. An old replacement, at that. If we'd made the 3000 ready for a platform-agnostic environment, so it could use modern storage like the later-generation XP arrays, we could justify a replacement and get something newer.

Now the 3000 goes onto the bubble again. The most-quoted reason for companies to scrap their MPE environments, their platform, is because of aging hardware and the worry over replacing it. Peripherals like storage and tape now have their own worry points, according to support companies serving 3000s. Tape is a crapshoot. People have been warning about old disks for a long time.

The Why to leave platform-land is all about the future. When a datacenter is no longer thinking about 3000-only hardware -- when that hardware can be commodity high-class Intel servers or an array that's beyond the reach of platform-land -- the apps can stay off the bubble. The need to migrate recedes, so long as there's expertise about MPE/iX somewhere.

MPE know-how isn't automatic anymore, but there are support companies that specialize in it. The future of self-maintaining that know-how isn't bright. Indie companies can help, and at least the devices need to be useful to all hardware. Until that's done, being stuck in platform-land is just one more way to hurry to an exit from everything still working from the 3000 world, built and configured in the era when platforms were like the heroes from Oz. We'll miss you most, Tin Man.

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

September 24, 2018

Data migration integrity can be in the garage

RulesoftheGarage
In the world of book publishing, a customer with a legacy of using HP 3000s is pushing users through a migration. The Nielsen name has long been associated with TV ratings, but that former HP 3000 customer tracks so much more. This month the book sales service BookScan is getting a migration to a new system. The old system was called Nielsen and the new one is NPD's Decison Key. The transfer is expected to have its bumps. Some might have impact who's on this year's bestseller lists.

Publisher's Marketplace reports, "BookScan will complete its transition from the old Nielsen platform to the NPD system and at outset, the biggest adjustment for users may be getting accustomed to system updates on a different day of the week. "

As the story unfolds there's more changes expected. NPD Books president Jonathan Stolper is predicting high integrity. "We're going to get it right," he said in a Publisher's Marketplace article. The Marketplace resells Nielsen data to authors, publishers and booksellers—so the forecast would of course be bright. Many data migrations have had this forecast.

But the data on this Nielsen system, some of which goes back to the HP 3000 era there, has deep roots. From the Marketplace report:

We're talking about millions of titles, a system that goes back to 2004 in detail. There is a ton of data within this system. So it's only natural that there's probably going to be some – I don't want to call them hiccups, but some variances. Whenever you switch systems, there's some slight variance. People are going to have to realize that it's not an absolute match."

Then comes the upshot of the migration. Some books are going to "sell" better than others, depending on the data integrity for this year's sales.

The switchover will increase sales because the newer data collection system reaches into more points of sale. Gift shops and museum stores, for example, are in the new mix.

Those variances mean that some titles will see increased sales for 2018 in the new platform versus legacy BookScan, due to the broader information enabled by NPD, which collects retail point-of-sale data in broad fashion across many industries.

Data migration has been the heartland at MB Foster for the last three decades. Last week the company that made database interfaces for HP 3000s in ODBC/SE hosted a webinar on a concept called the Migration Garage. "A garage can be set up to deal with the end-to-end requirement, the staffing required to make the garage a success, and where the savings come from when a garage process is defined."

It took two years for the BookScan tracking system to migrate to the NPD platform. The NPD system, called Decision Key, will become the data of record for BookScan. The number of titles that have been printed with the word "Bestseller" on the cover probably hasn't been tracked. It's a powerful marketing term, though.

MB Foster's concept of a Migration Garage "is useful when there are a number of applications with the same requirements or that have a common set of data that is changing and similar changes have to be made to each application as it is transformed to its new environment."

Publishing is an industry that often clings to legacy practices, like paying published authors their royalties just twice a year. (Something about needing to count the returned books before the checks for the writers go to the agents, who send the money to the authors.) Nielsen is moving its data to a new vehicle this fall. Just as in every migration, the numbers will speak for themselves.

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

September 17, 2018

Planning to migrate has been the easy mile

Postman3000 owners have made plans for many years to leave the platform. The strategies do take a considerable while to evolve into tactics, though. The planning stage is easy to get stopped at, like an elevator jammed up at a floor. 

For example, take a company like the one in the deep South, using HP 3000s and manufacturing copper wire and cable. The manager would rather not name his employer and so we won't, but we can say the 3000 is dug in and has been difficult to mothball.

In fact, the only immediate replacement at this corporation might be its storage devices. The datacenter employs a VA7410 array.

We do have to replace a drive now and then, but there hasn't been any problem getting used replacements, and we haven't suffered any data loss. I think if we were planning to stay with MPE for the long term, we might look for something newer, but we are planning to migrate. In fact we planned to be on a new platform by now, but you know how that goes.

More companies than you'd imagine know how that goes in 2018. We're nearing the end of the second decade of what we once called the Transition Era. The final mile of that journey can be the slowest, like the path of the postman who must carry the mail on foot through urban neighborthoods.

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

August 27, 2018

Where to go when the app vendor is gone

Nature-2806211_1920
The cozy corner of your world that's the HP 3000 Community on LinkedIn has many reports about where users are working. One story that's slid onto our desk from that community illustrates the work a 3000 owner faces when a software vendor leaves them behind. For many sites with few resources, this is the situation that triggers a migration.

This is a story of what happens when the Hewlett-Packard hardware outlasts vendor applications. It's not that the app has stopped working, not at all. But the manager of the 3000 knows his employer has limited time to plan for a future while using software that can't be modified, because there's no source code — and not much documentation, even though the software's been customized.

3000s stay in service long enough to get to the point where the most durable piece of the solution is MPE/iX. Hardware can die off and be replaced by Charon from Stromasys. Expertise can be hired on contract for administration and operations. Development, though, is the hardest asset to maintain. When expertise dwindles for a third party piece of software — in this case, the IBS/3000 (Integrated Business System) financials package from DeCarlo, Paternite and Associates — a migration is usually in order.

The 3000 manager said he came on board at the company and learned about IBS being a key business component. "I Googled it to see if there was a user forum, vendor site, or any information. All I found was Irritable Bowel Syndrome."

Even if there was still vendor support available, it would be of limited use because there are so many in-house modifications and enhancements. The app has served us well, but is not sustainable for the long term.

He reports that the migration project will have to survive bad decisions, woefully inadequate management support, bad consultants, and a lack of expertise. "New leadership is in place with more realistic expectations. I hope we can hit a 2019 target." This manager of an A500 system is counting down to an end of 2018 retirement — and doing his best to ensure the system can outlast him.

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

August 13, 2018

Licensed MPE source solves OS mysteries

Rathbone-holmesIn early 2028 I’ll be 70, and some MPE/iX apps could be 40 years old. I can hope retirement is in my rangefinder by then, but at the moment it looks like I’ll be writing until I can’t make sentences anymore. (Gotta remember, first noun, then verb.)

Well before that year, though, the roadblock of 3000-MPE date handling will be cleared. The companies most likely to have a comprehensive workaround are the ones which have licensed MPE/iX source. Or, the companies which are allied with the source licensees. Fixing the use of the CALENDAR intrinsic doesn't need to be a source-level repair. Having source access, though, only makes the fix more robust.

The 3000 owners and managers are all about robust. That's why they're still making use of a computer the vendor hasn't sold since 2003. Many of the companies who don't self-maintain are relying on support services now working more than seven years since HP left that support business, too.

The established independent support companies will be glad to collect money for building a 2028 solution, customer-by-customer. They should be paid. There are some IT managers out there in the 3000 world who see leaving their existing systems in a future-proof state, software-wise, as part of their job whenever they get to retire. Those are the real Boy Scouts, I’d say. On the other hand, you will hear arguments they’re not doing their jobs by leaving their companies running MPE/iX, even today.

The heart wants what it wants, though. If a company hasn't got heart for a migration right now, then the adminstrative work to be done is preparing for a forever journey for MPE/iX. Or at least until I'm 80, when the Unix 2038 roadblock appears.

Nobody should be building a 2028 fix unless they’re going to be paid. This issue is important to the Stromasys customer base. Not all: some Charon 3000 emulator installations are holding a place for a migration that's underway.

The community's elders care about the future. So long as the old managers can get a new expenditure approved, the game's afoot, as Sherlock Holmes would say.

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

August 08, 2018

Wayback: Linux re-enters the 3000's world

Penguin-shorelineThe Newswire's articles can sometimes be evergreen, even in the hottest months of the year. This week we got an email about a 2001 article that introduced Linux to our readers. A companion to the article from 17 years ago, A Beginners Guide to Linux, includes one outdated link, along with timeless advice.

Linux was already a juggernaut on corporate IT whiteboards and it had a strong following in the field, too. Shawn Gordon wrote a pair of columns about Linux as a 101 course for 3000 experts. The first article was published in the first weeks after HP's exit announcement about the 3000 business. Gordon, who founded a software company built around Linux applications, connected the dots.

To be honest, you can go another seven years quite easily with your existing 3000 system, which is a long time for a system these days. But if you were looking for a change anyway, now is the time. So what does this all have to do with Linux?

Linux seems to be the great equalizer. It runs on watches, set-top boxes, PDAs, Intel chips, PowerPC chips in Macs and IBM systems, Itanium chips, IBM mainframes — the list goes on and on. IBM and HP both are moving their customers towards it, and IBM has done some fantastic work helping Linux on scalability.

In our HP 3000 space we mostly know the players and we are comfortable where we are. Jumping over to Linux required that I learn a lot about things I never cared about before — like the GPL, GNU, Linux, RMS, ESR, and other things that I will explain in a bit. One of the bits that has been floating around a lot on the various 3000 discussion lists is Linux.

The update for the two-part article comes from a company that has a free Linux education website. Alex Nordeen, Editor of Guru99.com, hopes to get your web visits.

The tutorial is for an "absolute beginner's guide to Linux. You don't even have to buy a new PC to learn Linux. You can run Linux, right within your existing Windows or Mac OS systems! (Detailed steps are given in tutorials)."

Nordeen says of the second part of the article series, "In one article, you mentioned and linked to www.tuxedo.org/~esr. However, that site has been pulled out. And it's unclear that the page is going to be available again."

We recently created tutorials on Linux that took 190+ hours to create with beautifully annotated screenshots and videos. They are very comprehensive.

The tutorials are created by a Google veteran and I have personally edited them. The course covers

• Linux Basics like Introduction, Linux Distributions and Installation, Commands, and File Permissions.
• Redirection, Regular Expressions, Commands, and Communication in Linux.
• We also touch on advanced topics like Environment Variables, Managing Processes, VI Editor, Shell Scripting, Virtual Terminal, and Linux Administration.

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

July 30, 2018

Ways to make SFTP serve to a 3000 system

Waiter-serviceEarlier this month a seasoned veteran of 3000 development asked how he could get SFTP service supported for his system. He's been managing a 3000 that's been ordered to employ file transfers that are more secure than FTP.

Secure FTP works well enough outbound, thanks to the OpenSSL software ported to the 3000 in WebWise. But incoming SFTP is tougher. Some say it's not possible, but that answer doesn't include any potential for a proxy server. Or a virtualized 3000.

Versions of OpenSSL that were ported to run on native MPE probably won’t satisfy an audit, nor do they have some of the current crypto capabilities that would satisfy things like PCI requirements. There are no developers signed up to continue the OpenSSL port project.

That leaves the proxy solution.

In this solution, a manager would set up a Linux SFTP server with two NICs. NIC 1 goes to the outside world. NIC 2 is a crossover to the HP 3000. From the HP 3000, SFTP to the Linux server via NIC 2.
 
In another scenario, you can FTP between the HP 3000 and a Linux virtual machine. One developer said that on the Linux VM "we have a small application that talks to the HP 3000 via FTP and forwards to and from other machines via SFTP or SSH." He added that the app on the Linux system is written in Java.
 
Migration often includes this kind of expertise. Charles Finley, a veteran of HP 3000 matters since the 1980s, recently raised his hand to offer notes on using an SSH tunnel. "It does not involve coding, the use of libraries and—although you can do it with Linux—does not necessarily involve Linux." He drew a link to an example employing a Windows host, adding that "we use Linux or Windows for this type of thing. Here's a description of how connect to an FTP/SFTP server which can be accessed via another server only, using PuTTY, "something we make use of a lot," Finley said.
 
There's also a simple way to use SFTP by employing Stromasys Charon. Other servers can SFTP to a Linux partition. Charon is hosted under Linux as it emulates the 3000 hardware. This hosted MPE server can then pick the files up internally.
Mark Klein, who bootstrapped the original GNU library for the 3000 that made all of its open source tools possible, says a requirement for the security of encryption could be satisfied with a secure link, rather than secure protocol.
See if you can negotiate with the auditors for an encrypted link instead of an encrypted protocol (tell them that the protocols on the 3000 itself can’t do what they are asking and suggest the alternative). Tell them that the SSL on the 3000 is older than 1.0.x and still won’t pass audit, even if you could make SFTP work.
 
These days, everything less than TLS1.1 is unacceptable.  The OpenSSL on the 3K can’t support that. I’m afraid you might get the SFTP requirement resolved only to then fail on the lack of TLS or the newer ciphers.  

It would be easier to leave the existing processes in place (they work) rather than exchange them for something that is unknown and then wrap that with accepted encryption. 

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

July 18, 2018

July's IA-64 news, delivered by the Sandman

IA-64 Sequel t-shirt copy
Twenty years ago this month the 3000 community got its biggest assurance of a long future. The system's lab manager said that the IA-64 architecture would be fully supported in future 3000 models. New compilers would be built for a new MPE/iX. Channel partners and resellers got the news from the labs two months earlier at a swell retreat.

The man delivering the news for that July article is a familiar name with 3000 customers. He was Winston Prather, head of R&D at the time—and three years later, the person who decided the 3000 community didn't need the computer. A weak ecosystem was supposedly the reason Prather could be the Sandman and help put HP's MPE/iX business to sleep.

Three summers earlier, all the news we could report in the NewsWire was good. 

"The 3000 customers who experienced the move from Classic to MPE/XL know exactly what they’ll be looking at as they move forward,” Prather said. “One thing that makes me feel good about it is that it’s something we’ve done before. I think we pulled it off pretty successfully, and we learned quite a bit. We’ll use some of the same learning and techniques as we move to the new architecture."

Prather said that by early in the 2000s, 3000 customers would be able to buy and use an operating system to run with both PA-RISC and IA-64 processors,  "Customers who need the additional performance of IA-64 will then be able to buy IA-64 processor boards to plug into HP 3000 processor slots on the new systems." It was an audacious design. HP bragged of the bold move.

“Prior to the IA-64 boards or chips," Prather said, "there will be complete new boxes available at the high end and the midrange, and then potentially at the low end.” The new 3000s would use new IO systems, giving customers a way to step into new hardware technology incrementally. The IO arrived, late out of those labs, in the form of new PCI bus architecture. IA-64 on MPE was put to sleep.

Watching the whiplash as HP first promised a future, pre-Y2K, then took away the hope of 3000 site, in 2001, baffled a lot of us. The system deserved a big tech investment. Then it didn't.

The 1998 IA-64 report sounded very real, much more so than the announcement from Prather's 3000 leadership in late 2001. HP's MPE futures were going dark. In 1998 there was even an admission that some "forking" of the operating system — a la MPE V and MPE XL — would have to take place.

Although CSY is working to delay it, a time will come in the next decade when there will be two versions of MPE/iX, one for the PA-RISC systems and one for the IA-64 boxes. Customers work in such an environment today if they support Classic (CISC) HP 3000s running MPE V alongside MPE/iX.

HP has already been working on bringing 64-bit features such as large memory space and large files to MPE/iX long before IA-64 is ready for the 3000. The technical discussions taking place over the last year inside CSY include methods to keep from dividing MPE/iX into two camps.

“We don’t want to fork the operating system,” Prather said. “We have had internal debates about how we could provide all of this new functionality, the 64-bitness, and in the future avoid forking the operating system. We have a strong desire to avoid that. I’m not sure we’ll be able to avoid it forever.”

The departure of HP from MPE/iX futures is a fact that changed thousands of careers. Now the future demanded costly migrations for many firms. Everyone could be forgiven for being flummoxed by the leadership flame out, considering how certain the 3000 lab leader sounded in 1998 about building for the future.

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

June 18, 2018

Still seeking expertise for 3000 work

Port of VirginiaFresche Legacy floated a request this month for 3000 experts to contact the company which was once called Speedware. Eric Mintz runs the services group there. 

Fresche Solutions (formerly Speedware) is looking for HP resources (related to MPE, HP-UX, 4GLs, COBOL, IMAGE, Eloquence, knowledge of the common third party utilities, etc.) for various engagements and start dates (some almost immediate). Mandates may include onsite, remote, short to long term. I can't be more specific than this, so please reach out to me directly and I'll work to facilitate next steps.

Some long-term HP 3000 shops have used the services at Fresche. One of them, Virginia International Terminals, has worked with the company long enough to know it as both Speedware and as Fresche. Late in 2016 the organization was doing its final push away from the 3000. The Windows version of Speedware was the target, with the organization moving off of five MPE apps.

The VIT project was moving ahead of schedule when we last checked in with Mintz. We chronicled the pace on that migration during the earliest phase of the Transition Era, once more as the work ramped up,  and again not long ago. MPE was fully dug-in at the organization, which is now part of the Port of Virginia. That's one reason why 3000 expertise was essential to a successful migration.

VIT was fully locked in over all of the last 15 years of its migration. Even still, when HP dropped Carly Fiorina in 2005, it made the IT manager at the time wonder about a twist in the 3000's fate at the time.

“The ‘change’ did make me wonder if the HP 3000 decision might be revisited,” said Dave Seale, IT Director at VIT, HP’s earliest case study on migration practices. VIT was ready to turn over its migration project to Speedware in March or 2005 after its business growth had slowed VIT’s projected timetable to leave the platform. “It would be very interesting to me if HP decides to reconsider their decision,” Seale said. “Logically, I never could understand it.” 

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

June 01, 2018

Recovering a 3000 password: some ideas

I have an administrator who decided to change passwords on MANAGER.SYS. Now what's supposed to be the new password isn't working. Maybe he mis-keyed it, or just mis-remembered it. Any suggestions, other than a blindfold and cigarette, or starting down the migration path?

The GOD program, a part of MPEX, has SM capability — so it will allow you to do a LISTUSER MANAGER.SYS;PASS=

If your operator can log onto operator.sys:

file xt=mytape;dev=disc
file syslist=$stdlist
store command.pub;*xt;directory;show

While using your favorite editor or other utility, search for the string: "ALTUSER MANAGER  SYS"

You will notice: PAS=<the pwd> which is your clue.

It's said that a logon to the MGR.TELSUP account can unlock the passwords. The Telsup account usually has SM capability, if it wasn't changed.

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

May 25, 2018

Fine-Tune: Locking databases into lookups

Editor's Note: Monday is a holiday to commemorate Memorial Day, so we're celebrating here with time away from the keyboard. We'll be back with a new report May 30.

Lock files databaseWe’re migrating from our 3000 legacy applications to an ERP system hosted on another environment. Management has decreed the HP 3000 apps must still be available for lookups, but nobody should be able to enter new data or modify existing data. Should I do the simplest thing and change all of the databases so that the write class list is empty?

Doug Werth replies:

One way to do this is to write a program in the language of your choice that does a DBOPEN followed by a DBLOCK of each database (this will require MR capability). Then the program goes into an infinite loop calling the PAUSE intrinsic. Any program that tries to update the database will fail to achieve a lock, rendering the databases read-only. Programs that call conditional locks will come back immediately with a failed lock. Unconditional locks will hang.

This has been a very successful solution I have used on systems where a duplicate copy of the databases is kept for reporting and/or shadowing using IMAGE log files.

Steve Dirickson agrees with the poster of the question:

Since very few developers write their apps to check the subsystem write flag that you can set with DBUTIL, changing the classes is your best bet. Make sure you do so by changing the current M/W classes to R/R so the existing passwords will still work for DBOPEN, and only actual put/update/delete operations will fail.

The Big Picture: If protection is required for the database, that protection should reside in the database if at all possible. As mentioned, this is easy with IMAGE.

I am putting a new disk drive into my 3000 configuration, one that doesn't have an HP label on it. It's 500GB and a great value. What patches should I be sure to have installed on MPE/iX 7.5?

MPEMXT1
Large Disk: FSCHECK SYNCACCOUNTING fix for HFS files

MPEMXT3
Large Disk: limit maximum SCSI disk size to a half-terabyte

MPEMXT4
Large Disk: SSM changes for disk space allocation and accounting

MPEMXT7
Large Disk: Discfree changes to correct sector counts

MPEMXU3
Large Disk: REPORT "FORMAT=LONG" enhancement. MPEMXU3 includes patch MPEMXT2 which is another Large Disk/Files patch. MPEMXT2 provides changes to the ALTACCT, NEWACCT, ALTGROUP, NEWGROUP commands.

MPEMXU6
Large Disk: CATALOG.PUB.SYS changes for CIERR messages

MPEMXU7
Large Disk: CICAT and CICATERR.PUB.SYS changes

The critical one is MPEMXT3, which protects from other problems.

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

May 21, 2018

Second generation of migration begins

Synergy for DummiesHP advertised the transition off of 3000s as a migration in 2002. The changes and replacements took place throughout the rest of that decade, culminating around the time HP was closing off its support operations for MPE/iX in 2011. That was generation number one for migration at 3000 shops. The second shift is underway.

Promedica is the largest employer in Toledo, Ohio, a non-profit corporation which used 3000s to manage provider operations running the Amisys software. Tom Gerken is still an analyst at the organization, after many years of managing the production HP 3000s. Now the healthcare firm is shifting off of its Unix version of Amisys, after taking its 3000 computing and migrating it to HP's Unix.

"We did continue using Amisys," he says. "We moved to HP-UX in the second half of 2006. The data transfer to the Oracle database went smoothly. It was really sad seeing the HP 3000s go away."

At Promedica the changes are leading into another generation of migration. "We most likely aren't staying with Amisys much longer," he said. "We have begun the search for a replacement system. I think Amisys is still in the running officially, but I hear it's a long shot to make it into the finals."

Out at the City of Sparks, Nevada, another longtime 3000 manager is shifting into a fresh generation of computing resource. What was once MPE/iX, and then became a virtualized Windows datacenter, is becoming even more virtual.

The 3000 migration was complete at Sparks almost six years ago, and then a virtualized Windows platform got its work assignment. Now the city is heading for a deployment of HPE Synergy. It's still using a Hewlett-Packard product, as it's always been at Sparks under the command of Steve Davidek.

In about a month he's delivering a talk at the HP Discover conference on the migration to HPE Synergy. The HP Enterprise product is a composable infrastructure, one so different that HP arranged for a Dummies guide to be written about Synergy.

Synergy uses software to discover and assemble the pools of compute and storage. A hardware frame houses appliances that run the management software, including Synergy Composer and Synergy Image Streamer. Detailed configurations for particular applications are saved as templates and deployed through Composer. 

Virtually every technology is a base to migrated away from. The changes have slowed over the last five years for 3000 owners, though. Steve Cooper of Allegro says he thinks there's been no more than a five percent decline in systems since last year.

Posted by Ron Seybold at 09:32 PM in Migration, News Outta HP | Permalink | Comments (0)

May 07, 2018

June's 3000 Reunion destination: Building D

DukeSnugThis week I made my reservations for a date that's become rare in our community. On June 23, the 3000's experts, vendors, and consultants are gathering for another 3000 Reunion. That's the name that Apple is using for the group, since the gathering will include a visit to the frontier of Apple's world HQ. The event also includes a morning's visit to the Computer History Museum, the site of the 2011 Reunion where more than 150 members gathered.
Apple Park Rooftop

The highest point of the day won't be the elevated observation deck at the Apple Park Visitor Center, overlooking the company's spaceship campus that replaced HP's legendary 3000 hub. The pinnacle seems to be the afternoon hours enjoyed in a cozy snug at the The Duke of Edinburgh pub. Lunch, beverages, and war stories will be on the bill of fare starting at 1. People who know and remember the 3000 will gather in a pub popular enough with the MPE crowd that it's still known as Building D by some community members.

The Duke is on Wolfe Road, just to the west of where the 3000 grew up. Space has been reserved for a group that's making its way beyond 20 attendees. If you join us, I will be delighted to see you and hear your stories there, as well as any update on your interests and work of today.

The close-up nature of the venue doesn't mean it's without an agenda. As of today there's informal talks about migration, Stromasys emulation, the HP Enterprise of today and homesteading in our current era. The group is eager to include a member who's running MPE/iX today, either in virtual mode using the Charon HPA software or native on HP's venerable and as-yet durable HP hardware.

Screen Shot 2018-05-07 at 6.43.07 PMThe Duke was the site of a 2016 meeting of 3000 alums. In-person meetings for the 3000 community happen in bars and pubs by now. This event has been sparked by Dave Wiseman, who organized what he calls a SIG-BAR meeting in London in 2014. The vendor and semi-retired software maven has a history that includes a software project called Millware for 3000s as well as tales about a Series III he installed in 1978. Wiseman calls these events SIG-BAR because hotel bars during the Interex conference era always included informal wisdom, swapped after hours over a glass or bottle of something refreshing.

There's something about English pubs that can attract the 3000 crowd. Some of us who are flying in for the event are staying at the Hilton Garden Inn Cupertino. (At the moment, Saturday evening rooms are under $150, which is a value at Bay Area rates.) The Inn is close enough to the Duke that no matter how much happiness is served, it's a one-block walk back from pub. There will be an evening session at the Duke after the Apple tour, too.

The Duke sits within walking distance of a now-lost mecca of the 3000 world, the HP Cupertino campus. Building 48 has been replaced by the concrete, glass and steel of the new Apple world headquarters building. Apple's organized a tour of the Visitor Center for this year's 3000 attendees. The Centre's rooftop is as close as you'll get to the HQ spaceship without a contract with Apple, or a job at the world's Number 1 market cap company.

In 1976, HP fed Apple with engineering talent, a fellow named Steve Wozniak. Legend has it that Woz was working on HP's business computer designs at the time when he left to become VP of Apple R&D. In a way, that Apple HQ has always had innovation on its acres, even before there was a company first called Apple Computer.

The land of what's now called just Apple covers the path where a walk through an HP parking lot and across a cozy margin of poplars brought you to the Duke. "It's right across the street from where MPE lived," Stan Sieler of Allegro said at the 2016 meeting. On June 23, MPE's heart will be among the taps and the chips at The Duke.

In London in 2014, Robelle's Bob Green said this about the in-person meeting at that London pub:

We exchanged notes on the current state of the machine—especially the new emulator—- and discovered what each of us was doing. An amazing number of people are still doing the same thing: helping customers with their IT concerns. But in reality, most of the time was spent swapping war stories from the past, which was great fun.

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

April 11, 2018

Wayback Wed: HP group combines, survives

Connect LogoIn the aftermath of the Interex user group bankruptcy, an HP enterprise user group survived. That group remains intact to this day. Its survival is due to an ability to combine forces with other groups, an effort that kicked off 10 years ago this week.

That week was the time when Encompass, the user group that outlasted Interex, gave members a vote on merging with three other HP-related groups. At the time of the April vote, Encompass and these partners weren't even sure what the allied group would call itself. Endeavor was being floated as a possible new name.

The vote of the Encompass members approved the merger with the International Tandem User Group; the European HP Interex group, which was operated separately from the rest of Interex; and a Pacific Rim segment of the Encompass group. The European Interex reported that it had 35,000 members at the time of the merger.

Encompass became Connect, a name announced at HP's Discover conference later that same year. Connect still operates a user group with a large meeting (held at HP's annual event, for the in-person gatherings) as well as smaller Regional User Groups.

The group bills itself as Connect Worldwide, the Independent Hewlett Packard Enterprise Technology, a membership organization. Membership in any user group has evolved during the decade-plus since Interex expired. By now it's free to join the group that serves OpenVMS customers, companies that still employ HP's Unix computers and hardware (Integrity), and sites using the HP NonStop servers (the former Tandem systems).

Those Tandem-NonStop users make up nearly all of the in-person meetings other than the HP Discover event. Discover is devoted to everything HP Enterprise sells and supports. One of the few links remaining to the 3000 at Connect is Steve Davidek, whose management and then migration off 3000s at the City of Sparks made him a good transition leader at Connect.

There are Technical Boot Camps for both NonStop and VMS customers that Connect helps to organize. A boot camp for HP-UX never became a reality. That's one of the choices a group of allied users must face: even some support for a resource like a boot camp (some members were eager) needs to be balanced against the majority membership's desires.

Some missions have survived from the Interex model that drove that group for more than 30 years. Advocacy still has a place in the Connect membership benefits, a project that's called Community Voice by now. The old days of an HP user group with a taste for confrontation ended once Interex refused to join HP's effort to consolidate user groups and things like advocacy. The Interex board voted to stay independent—without giving its members a formal vote like the open balloting which Encompass did.

The benefits of Connect still lean heavy on networking, along with some technical resources steeped heavy in NonStop expertise. Advocacy flows through HP's Discover show, and there are 19 Special Interest Groups. SIGs like these were the hotbed of 3000 customer desires communicated to HP from Interex members.

From the Connect website, the list of membership benefits includes these resources.

  • 19 Connect Communities and SIGs (special interest groups)
     
  • Never miss a beat with Connect Now, a monthly eNewsletter
     
  • Problem solve and stay on top of your game with Connect's ITUG Library (a NonStop Download Library)
     
  • Have a say in HPE with the collective voice of Connect's advocacy programs
     
  • NonStop users receive a subscription and access to the archives of The Connection, a bi-monthly technical journal
     
  • All members receive a digital subscription to Connect Converge, our exclusive quarterly technical journal for HPE business technology users
     
  • Save hundreds of dollars per year with discounted registrations to premier events like HPE Discover, and Connect's signature tech-targeted Boot Camps
     
  • Save while you expand your knowledge base with 15% off HPE Education programs
     
  • Members and their dependents can apply for $2,500 Future Leaders in Technology scholarships

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

April 09, 2018

Aspects to Ponder in Package Replacements

By Roy Brown

Shining-gemEach kind of migration has its advocates, and each has its pros and cons. Your constraints are going to be cost, time, and risk. Probably in that order. I can’t say much about the first two; that depends on your circumstances. Last week we talked about the differences between conversions and migrations and the risks. Another option is going to a package to execute a migration off MPE/iX. It might even be a familiar package — but on a less familiar platform.

Packages

If you have a package running on your HP 3000 which you are happy with, and the vendor provides that same package, or something very similar, on other platforms, then it’s likely just a case of choosing which platform to go with.

Your vendor-supported migration path should be pretty straightforward, and your hardest problem is going to be to decide what to do with the crust of subsystems and reporting programs that have built up, and which surround the package proper. If there are some you can’t do without, and the features aren’t provided by the package anyway, on the new platform, this may be a good chance to get to grips with the tools and utilities on the new platform, and how things are done there.

But maybe you had a bespoke or home-grown application on the HP 3000, in an area now covered by one or more packages on other platforms, and it makes more sense to move onto a package now than to go bespoke again?

In that case, you have a three-way analysis to do; what does your existing system provide, what does the new package provide, and what are your users looking for?

I’ve heard the advice “don’t go for customization, go for plain vanilla” a lot. It certainly gives cost and risk reduction, though perhaps at the expense of business fit. I reckon that a shame; every company has something that is its USP – unique systems proposition – something in its IT that gives it its edge in its chosen business.

On the other hand, sometimes a company does things differently because it was easier, or “it was always done that way.” Those are things you shouldn’t lose sleep over giving up.

A couple of concrete examples; firstly, meaningful SKU numbers. Chances are your SKU numbers, or product codes, have a structure you understand. If so your homegrown systems will likely have dozens of places where a program takes a different path based on what that SKU number is. A package is unlikely to support that; each property needs an explicit flag on the Part Master, and the package has to work off those.

This doesn’t mean that you can’t keep your meaningful SKUs, where everyone in the business knows what they mean. Just that the package won’t know from the SKU, and so you will need to set those flags for each one. And carefully too, or there will be some real confusion.

That’s a case where you go with what the package does. But in the system I’ve just migrated, we had a critical financial value, set against every order, in a complex and special way that was important to the business. The old system calculated it. The new system would accept a pre-calculated value as input, sure, but it wouldn’t do the calculation.

We could, I guess, have asked for it to be customized in. In practice, we built an Excel spreadsheet as a preprocessor to the package proper, and did the calculations there.

There’s still a little bit of me that says moving stuff off the HP 3000 onto a spreadsheet is going backwards. But then there’s a bit of me that says that of moving anything off the HP 3000.

Custom replacement

This is the Rolls-Royce (or should I say Cadillac?) option. But if your application is unique, so there’s no chance of a package solution, and if rewrite/code conversion doesn’t suit, possibly because of a pent-up backlog of business change requests, or the knowledge that your business area is changing radically, it can be the only sensible way to go.

And if so, you don’t need a few thoughts and observations about compromise; you need to know how to choose from the myriad of possibilities out there. I only wish I knew myself…

Roy Brown is CEO at Kelmscott Ltd., a developer and consultant with more than 35 years’ experience on MPE and the HP 3000.

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

April 06, 2018

How to Measure Aspects of Migrations

Newswire Classic
By Roy Brown

GemSo you are going to migrate. When migrating to a different system or platform, there’s usually something the vendor needs you to lose. But is it essential business functionality, or just an implementation quirk of your old system?

Which migration are you going to have? The luxury option of a custom replacement of your old system? To a package on a new platform, maybe a version of a package you had before, or one new to you? Perhaps the rewrite option, where a team of programmers, possibly offshore, re-implement your system in a whole new environment, while keeping the existing functionality. Or will it be a conversion, where your existing system is transferred to a new platform using automated tools?

Each has its advocates, and each has its pros and cons. Chances are, your constraints are going to be cost, time, and risk. Probably in that order. I can’t say much about the first two; that depends on your circumstances.

Code Conversion

But risk comes in two timescales; immediate risk – “Can we do this? Can we get onto the new platform?” – and the longer-term risk that you are maybe painting your company into a corner by accepting some compromises now that later will turn into shackles.

Those with very long memories may recall some of the early packages being offered for the HP 3000, the apps with KSAM file structures, not IMAGE ones. You just knew they had been ported from elsewhere, not written native on the HP 3000. And if you could find what you wanted, on IMAGE, you were surely glad.

That’s the longer-term risk, then, for some conversions with low short-term risk; you’ll be on the new platform, certainly. But you may have something that plays like the modern-day equivalent of having KSAM, when the smart money is on IMAGE.

Look hard at where you are going to be after a tools-based conversion; will you be fully on the new platform with all-independent code, or will you be running in an environment provided by your conversion specialists? If the latter – and these can indeed lead to faster, cheaper, lower-risk conversions – treat your supplier as a package implementer that you are in with for the long haul, and judge them accordingly.

Likewise, what about ongoing, internal support? One of the reasons to move to new platforms and new paradigms is to tap in to the new generation of people who know their way around them. But if it’s hard to see how you are going to get ongoing support for your HP 3000 apps, how much harder will it be to find people who can support a hybrid old/new system you might wind up with?

Finally, and on the same note, how maintainable is the migrated system going to be? You need to ensure that the generated code is going to be something that a human can easily work with – and likewise the environment the code runs in – or you are going to be effectively frozen in the converted state. Fine if it’s a subsidiary app, perhaps, and this is a stopgap until it dies or you replace it more fundamentally. But not if it’s a key business app that needs to grow with your business going forward.

All this is assuming the conversion is feasible. Hopefully, in the average application suite, you are not going to have done too many unusual things that the automated conversion can’t cope with; maybe some system-y job and user status calls that are done differently on the new platform, and other corner cases, but nothing fundamental.

But sometimes the gotchas can be quite widespread. While inadvertently exploiting the specific way VPlus works, we once had an application that let you put in a partial key and a question mark, hit f2, and go to a lookup screen where you could review matching keys, and select the exact one you wanted.

This was used across quite a range of screens, and relied on VPlus not trying to validate the partial key when you went that route. But move to a screen handler that works rather differently, and you may lose that option. Nothing insurmountable; we just needed to change things so the partial key was entered in the lookup itself, with a code to say what sort of key it was. But this small inconvenience for the user was surely also a bypass of nicer techniques we could have used if we’d had the new handler from scratch.

Rewrites

If a conversion isn’t the way you want to go, then likely you’ll be offered a rewrite. This can be more flexible than a code conversion (though you can bet the conversion team will be using some internal tools for the straightforward bits). And you should wind up with an app that is fully and independently implemented on the new platform, dispensing with any helper environments. Likely, though, it will not quite be what you’d have got starting from a zero base on the new platform – it will retain a few traces of its HP 3000 origins. But hey, is that such a bad thing?

Here again, you need to make sure that you can work with the resulting code going forward, to keep on track with your business needs. But the main issue is what shape is the application you are migrating.

One way of looking at a rewrite is that it’s a full custom conversion—but the results of the business analysis, instead of being expressed as use cases in UML, or whatever, are being presented in “HP 3000 Modeling Language.”

So if you are really happy with how your HP 3000 app fits the business – and if your users are — this can be a better way to go than embarking on a needless rediscovery process. If it ain’t broke – at the business level – then fix it only at the code level.

Not to say you can’t save some money by looking hard at the 3000 app, and maybe trimming out some dead wood – old functionality that is no longer used, and that thus does not need conversion. But do try – at least in the first go-round – not to request new features. Else your rewrite starts creeping towards being a new custom implementation, thus losing you the best of both approaches.

But even with a rewrite, perhaps there will be a few things the rewrite team will balk at, or instances where you will find that the cost of keeping them in is likely to be disproportionately high. Maybe they will come up with an alternative approach, or maybe you will.

But if not, consider what you are losing. A nice-to-have, but which you use once in a blue moon? Or something integral to your business? On a rewrite, it’s less likely to be the latter that when considering packages, which I’ll come to later. And it’s likely to be something system-y again, albeit at the user level, where they interact with job streams, or print queues, or whatever.

Maybe something in the user interface? Though I’m always pleased to see how closely forms on the web follow the VPlus paradigm of fill in all the data, press Enter, get it validated, go forward if okay.

But you do need to be as flexible as possible about doing things a new way on a new platform. People often ask “How do I do x?” where x is an attempted solution they can’t get working. Invariably, the response is “Yes, but what’s the actual problem you are trying to solve?” And the answer turns out to be quite different from x.

Adopt that precept here; go right back to the problem you are trying to solve, and not how to get an envisaged solution working. You’ll get a much better answer.

Roy Brown is CEO at Kelmscott Ltd., and a developer and consultant with more than 35 years’ experience on MPE and the HP 3000

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

April 02, 2018

Options for HP 3000 Transformation

By Bruce McRitchie
VerraDyne

GearsTime — it marches on. We can measure it, bend it and try to avoid it. But in the end the clock keeps ticking. This is true for owners of the venerable HP 3000. In its day one of the top minicomputers ever manufactured, it went head-on against IBM (mainframes, AS/400, and System 36), Wang and Digital - and won many of those battles. And many HP 3000s are still running and doing the job they were designed to do. They have been upgraded, repaired and tinkered with to keep them viable. But when is it time for them to retire?

There are options. Many vendors have been working diligently to provide a transformation path to move from the HP 3000 to a modern platform and language. By making such a move these organizational risks are reduced:

  • Hardware failure.
  • Personnel failure - aging programmers.
  • Software failure.

Migration issuesSo why aren't the remaining HP 3000 owners flocking to newer technology? Is it because they know the technology so well — and it works? Have they been through large ugly development projects and never want to go through the pain again?

Whatever the reasoning, the arguments for staying with HP 3000 must be wearing thin. There are options, and to a greater or lesser extent, they all do the transformation job. Today's technology will allow companies to move their whole HP 3000 environment to a new modern environment, with or without changing language and operating system elements. Of course, with the different paths there are trade-offs that must be considered. This article briefly explores some of the options available to transform your HP 3000.

Emulation

At first glance this can appear to be the cheapest and easiest solution. A company picks the supplier of the emulation software, installs it, then puts their code on top and voila—their system is running as it always did. 

But is it? You may now have an emulator interpreting instructions from your HP 3000 and the new operating system you'll use to run the emulator. Is that interpretation always correct?

And what about the MPE commands themselves? Are they being interpreted correctly? Are you getting the results you expect? Although there are no new changes coming for MPE, you may have to learn Linux or another new OS for an emulator.

And what about the cost of emulation? Of course, there is the initial cost. But what of the ongoing costs? You now have to pay for the emulator and the native OS that drives it.

Here are some of the deficiencies we have noted over the years:

• Being an emulation of the existing system, it still requires continued use of old skill-sets. Add that to the new skill-set required to be learned for the emulation layer. Some emulation designs will also require new skill-sets for the target open systems platform and COBOL. You can now have a highly complex skill-set requirement for the IT staff and potentially a new OS to contend with.

• Some emulators only support certain parts of the current system; they do not support all the components that are currently used.

• If the application has to sit on top of the emulation layer, then access to the native operating system is restricted.

• Interoperability with other applications or services on the platform can sometimes be severely restricted.

• Emulators mimic the data structures of the legacy system. This is great for running the current system as is, but does nothing to make the data accessible outside to other systems, inquiry or reporting tools.

• Running emulation renders the customer completely dependent upon the emulation vendor for ongoing support and upgrades, which in itself is a sizable risk factor.

In other words, emulation can bring its own new set of problems.

Redevelopment

The specter of re-development haunts most people (especially those who have been large development projects and cannot forget the late nights, long days, and missed vacations). Defining the business requirements, architecting the new solution, finding business analysts, programmers and project managers. Persevering through a long and drawn out process with hundreds of meetings, thousands of decisions — and finally— testing!

Hours and hours of trying to figure out if it can work well enough for the business needs. And then the bill comes. In some cases, millions of dollars, years of effort—and believe it or not, after all the years of improving —many development projects still fail.

These considerations are even more important today, when business needs are quickly changing and the underlying technology is changing to keep up. The whole platform on which the system is developed will change during the project.

Companies have spent years injecting their business intelligence into their software. Re-developing is a sure way to erode that valuable asset.

Migration

Migration offers a lower risk, lower-cost solution than re-development—so that you can end up with the functionality you need, in a language and operating system that is modern and supported by many resources.

Maybe you are running COBOL on your HP 3000 under MPE/iX but would like to be running VB on Windows. VerraDyne can do such a migration. And we can do it at a reasonable price in a reasonable time frame.

Simply put, migration is the process of moving the current applications onto a new open system platform so that they run in 'true native' mode on that new platform. However, after migration, the application and core business logic are still the mature proven systems that they were on the old legacy platform. The old proprietary legacy components are removed and are replaced by the modern components of the new open system platform.

These are the main points when considering automated conversion with no use of proprietary middleware:

• Migration removes the old legacy skill sets but it does not affect the core business logic, so the customer's systems and existing programming staff can quickly retake ownership of the converted code and continue maintaining it with very little retraining. The converted system can be deployed on the new open system with the same screens and processes that existed on the legacy platform, so user department retraining is virtually eliminated.

• Since the converted applications operate on the new open system identically as they did on the HP 3000, determining successful migration is black and white. The converted system either runs the same or it doesn't — if it doesn't, it is fixed until it does. There is no gray area, there is no 'maybe' — obtaining successful project completion is a clear and concise process.

• By minimizing manual intervention, automated conversion provides an extremely low risk, short timeframe solution. The majority of the project cycle is devoted to the most important task of testing.

• The converted system runs as a 'true native' application on the targeted open system, so there are no roadblocks to gaining the full benefits of the new open systems platform: GUI screens, Web functionality, databases and more

• Conversion provides all the benefits a company seeks without any trade-offs. It absolutely minimizes intrusion into the company's operations. The entire project is performed at very low risk.

• After conversion, the customer has full ownership of its code. There is no dependence on the migration vendor after conversion.

VerraDyne has spent 25 years developing converters that move language and OS code from one platform to another. We have done it with hundreds of systems. At the end of a project you have a system that looks, feels and behaves like the old system, but is able to take advantage of new technologies. This is our claim to fame and our intellectual property, and we are very good at it. 

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

March 21, 2018

Tracking the Prints of 3000 Print Software

Tymlabs logoA reader of ours with a long memory has a 3000 connected to a printer. The printer is capable of printing a 8.5 x 12 sheet, so it's enterprise-grade. The 3000 is running software built by OPT, '90s-era middleware for formatting print jobs from MPE/iX.

To nobody's surprise, the PSP Plus product had problems operating in 2018. "I actually tried to use it in recent times to print to a strange brand of printers, Microplex," our reader said. "The software still ran, but formatting did not work right."

Bruce-Toback

"I was able to print to it with some success, but I could never get the software to do what I wanted it to do, which was to fill up a 12 x 8.5" page and make logical and physical page breaks coincide." The software was a stellar choice for its day, having been developed by the funny, wry and brilliant Bruce Toback (above). Bruce passed away during the month we started this blog, though, more than 12 years ago. His tribute was the subject of our very first blog entry.

Great software that once could manage many printers, but can't do everything, might be revived with a little support. It's a good bet that OPT support contract hasn't been renewed, but asking for help can't hurt if your expectations are reasonably low. The challenge is finding the wizard who still knows the OPT bits.

"We bought and it went from OPT to Tymlabs to Unison to Tivoli to...” These kinds of bit-hunts are the management task that is sometimes crucial to homesteading in 2018. Printing can be a keystone of an IT operation, so if the software that drives the paper won't talk to a printer, even a strange one, that failure can trigger a migration. It's like the stray thread at the bottom of the sweater that unravels the whole garment.

Maybe this product that started at OPT never made its way to Tivoli. My notes say ROC Software took on all of the Unison products. Right here in Austin—where we're breathing with relief after that bomber's been taken down—ROC still supports and sells software for companies using lots of servers. Even HP 3000s.

Tracking these footprints of this print middleware led through some history. Searches turned up a NewsWire article about Toback—many, in fact, where in Hidden Value he was teaching 3000 users on the 3000-L about one kind of software or another. Back in 1997 the discussion was about something rather new called Linux. Linux could be useful, he said, to hook up a PC to the relatively-new World Wide Web.

Searching for OPT—which was the name of Toback's company—turned up plenty of hits about another OPT/3000, the one HP sold to track 3000 performance under MPE. Before we knew it, there was an HP Configuration Guide for the Series III and Series 30 on our monitor. Circa 1979, the HP3000 Family had promise.
 
HP 3000 Series III"The expandable hardware configurations and upward software compatibility of all the models," said the guide, "allow you to choose the system that best fits your current needs, while protecting your investment for the future." HP and everyone else didn't imagine that almost 40 years later that 3000 family would still have living members.
 
HP's OPT was a dead end, since HP stopped supporting that product by 1997. As for the Series III, with its beefy 120MB disk drive (the size of a single daily newspaper edition's PDF file), it was a museum piece before Y2K arrived. One support company featured a Series III at an HP World trade show, setting it up in a booth for people to photograph themselves with. No selfies in that year—you needed somebody else to capture your moment with history.
 
ROC was in the NewsWire archives, though. A 1999 article showed us that the OPT software had become Formation after the product was sold to Tymlabs, another Austin company. ROC bought Formation along with the rest of the stable of products which Tymlabs had sold to Unison—and Unison sold that lineup including Maestro to Tivoli. There's some begat's of vendors we might have left out there. Nevertheless, things like PSP Plus were well-built and useful for more than two decades.
 
That's the lure of homesteading—its low-cost ownership—as well as the curse of staying on too long. Product expertise disappears. We've reached out to ROC to see if the offices on Northland Boulevard still contain some tribal knowledge of the artist formerly known as PSP Plus.
 
Our reader, devoted to the 3000 in more than just spirit, is hopeful about its future even while he relies on software and hardware from the past. "I was so encouraged a couple of days ago that I actually searched the Internet for HP3000 MPE system manager jobs," said Tim O'Neill.

"If I did not have to move too far, I would sure like to go back to MPE. To me, it is still an exciting world—and with Stromasys Charon hardware and massively parallel disk arrays and high-speed networking, it is an exciting NEW world!"

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

March 19, 2018

Why Support Would Suggest Exits from 3000

Way-OutThe work of a support provider for 3000 customers has had many roles over the last 40 years. These indies have been a source for better response time, more customer-focused services, a one-call resource, affordable alternatives and expertise HP no longer can offer. They've even been advisors to guide a 3000 owner to future investments.

That last category needs expertise to be useful, and sometimes it requires a dose of pragmatism, too. Steve Suraci of Pivital Solutions gave us a thoughtful answer to the question of, "How do I get my 3000 ready for post-2028 use?" His advice shows how broad-minded a 3000-focused support company can be.

By Steve Suraci

While the solution to the 2028 problem is going to be fairly trivial, it really is the entry point to a much bigger question: What logical argument could any company make at this time to continue to run an HP 3000 MPE system beyond 2028?

I understand that some companies have regulatory requirements that require data to be available on the 3000 for years beyond its original creation date. Beyond this, what logical justification could an IT manager make to their management for perpetuating the platform in production beyond 2028? 

2028 is a long way out from HP’s end of support date [2010] and even further from the original 2001 announcement by HP of their intentions to no longer support it.  It would seem to me that there was a reasonable risk/reward proposition for extending the platform initially for some period of time.  I have to believe that the justification for that decision will expire as time goes on, if not already.

The homesteading base has not in general been willing to spend to keep the platform viable.  They take bigger and bigger risks and alienate themselves from the few support providers who remain capable of providing support in the event of an actual issue. The stability of the platform has lulled them into believing that this has been a good decision.  But what happens when it’s not?

Who at Beechglen or Allegro—or here for that matter—with any in-depth MPE knowledge will still be working in 2028? MPE guys were getting long in the tooth back in 2004!

The 2028 pitch should be to finally put these systems to pasture. We are pressing our customers to move off the platform, as should any MPE support provider. I challenge any MPE system administrator to come up with a viable argument for using the platform beyond 2028.

Is the risk really still worth the reward? The HP 3000 has been a workhorse that has served us well.  Alas, all good things must come to an end!

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

March 16, 2018

Fine-tune Friday: SCSI Unleashed

Seagate 73GB driveAlthough disk technology has made sweeping improvements since HP's 3000 hardware was last built, SCSI devices are still being sold. The disk drives on the 15-year-old servers are the most likely point of hardware failure. Putting in new components such as the Seagate 73-GB U320 SCSI 10K hard drive starts with understanding the nature of the 3000's SCSI.

As our technical editor John Burke wrote, using a standard tech protocol means third parties like Seagate have products ready for use in HP's 3000 iron.

SCSI is SCSI

Extend the life of your HP 3000 with non-HP peripherals

By John Burke

This article will address two issues and examine some options that should help you run your HP 3000 for years to come. The first issue: you need to use only HP-branded storage peripherals. The second issue: because you have an old (say 9x7, 9x8 or even 9x9) system, then you are stuck using both old technology and just plain old peripherals. Both are urban legends and both are demonstrably false.

There is nothing magical about HP-branded peripherals

Back in the dark ages when many of us got our first exposure to MPE and the HP 3000, when HP actually made disk drives, there was a reason for purchasing an HP disk drive: “sector atomicity.” 9x7s and earlier HP 3000s had a battery that maintained the state of memory for a limited time after loss of power. In my experience, this was usually between 30 minutes and an hour.

These systems, however, also depended on special firmware in HP-made HP-IB and SCSI drives (sector atomicity) to ensure data integrity during a power loss. If power was restored within the life of the internal battery, the system started right back up where it left off, issuing a “Recover from Powerfail” message with no loss of data. It made for a great demo.

Ah, but you say all your disk drives have an HP label on them? Don’t be fooled by labels. Someone else, usually Seagate, made them. HP may in some cases add firmware to the drives so they work with certain HP diagnostics, but other than that, they are plain old industry standard drives. Which means that if you are willing to forego HP diagnostics, you can purchase and use plain old industry standard disk drives and other peripherals with your HP 3000 system.

Connect just about anything to anything

SCSI stands for Small Computer System Interface. It comes in a variety of flavors with a bewildering set of names attached such as SCSI-2, SCSI-3, SE-SCSI, FW-SCSI, HVD, LVD SCSI, Ultra SCSI, Ultra2 SCSI, Ultra3 SCSI, Ultra4 SCSI, Ultra-160, Ultra-320, etc. Pretty intimidating stuff.

Don’t despair though. Pretty much any kind of SCSI device can be connected to any other with the appropriate intermediary hardware. Various high quality adaptors and cables can be obtained from Paralan (www.paralan.com) or Granite Digital (www.granitedigital.com).

So, SCSI really is SCSI. It is a well-known, well-understood, evolving standard that makes it very easy to integrate and use all sorts of similar devices. MPE and the HP 3000 are rather behind the times, however, in supporting specific SCSI standards. Support for LVD SCSI was added with the A- and N-Class systems—and with MPE/iX 7.5, these same systems would support Fibre Channel (FC). 

Let’s concentrate on the SE-SCSI and FW-SCSI interfaces, both seemingly older than dirt, and disk and tape storage devices. But first, suppose you replace an old drive in your system, where should you put it? The 9x7s, 9x8s and 9x9s all have internal drive cages of varying sizes. It is tempting to fill up these bays with newer drives and, if space is at a critical premium, go ahead.

However, if you can, heed the words of Gavin Scott.

I’d recommend putting the new drives in an external case rather than inside the system, since that gives you much more flexibility and eliminates any hassles associated with installing the drive inside the cabinet. It’s the same SCSI interface that you’d be plugging into, so apart from saving the money for the case and cable, there’s no functional difference. With the external case you can control the power of the drive separately, watch the blinking lights, move the drive from system to system (especially useful if you set it up as its own volume set), etc.

At sites such as Granite Digital you can buy any number of rack mount, desktop and tower enclosures for disk systems. Here is another urban legend; LDEV 1 must be an internal drive. False. Or, the boot tape device has to be internal. False. You cannot tell by the path whether a drive is internal or external, and the path is the only thing MPE knows (or cares) about the physical location of the drive.

Okay, there are some limits

Once you come to terms with the fact that you can use almost any SCSI disk drive in your HP 3000, dealing with SE SCSI is a piece of cake and a whole world of possibilities opens up. With the right cable or adapter (see Paralan or Granite Digital) you are in business.

But just because you can connect the latest LVD drive to your SE-SCSI adaptor, should you? Probably not, because you are still limited by the speed of the SE adaptor and so are just wasting your money. Now that you know you do not need the specific HP drives you once bought, you can pick up used or surplus drives ridiculously cheap. [Ed. note: the 73 GB drive at the top of the article is $129.]

Seagate created new technology drives with the old technology 50-pin SE-SCSI interface, the 18Gb model ST318418N and the 36Gb model ST336918N.

FW-SCSI is more problematic than SE-SCSI because no one even makes FW-SCSI (HVD) disk drives any more and you need more than just a simple cable or adapter to connect newer drives to an HVD adaptor. In fact, from the Paralan site, “HVD SCSI was rendered obsolete in the SPI-3 document of SCSI-3.”

So, what is one to do? Most systems with FW-SCSI adaptors need them for the increased throughput and capacity they provide over SE-SCSI. Paralan and others make HVD-LVD converters. The Paralan MH17 is a standalone converter that allows you to connect a string of LVD disk drives to an HP FW-SCSI adaptor. Pretty cool.

If you're on a Fibre Channel (FC) SAN environment and you would like to store your HP 3000 data on the SAN, then only the PCI-Bus A- and N-Class systems (under MPE/iX 7.5) support native Fibre Channel.

A quick word about configuring your new storage peripherals: Do not get confused by the seemingly endless list of peripherals in IODFAULT.PUB.SYS. And, do not worry if your particular disk or tape drive is not listed in IODFAULT.PUB.SYS. Part of the SCSI standard allows for the interrogation of the device for such things as ID, size, etc. DSTAT ALL shows the disk ID returned by the drive, not what you entered in SYSGEN.

When configuring in a new drives, just use an ID that is close. In fact, there is really no need for any more than two entries for disk drives in IODFAULT, one for SE drives and one for HVD drives so as to automatically configure in the correct driver. The same is true for tape drives.

Summary

Disk drives and tape drives are the devices most likely to fail in your HP 3000 system. The good news is that you do not need to be stuck using old technology, nor are you limited to HP only peripherals. The bottom line is you have numerous options to satisfy your HP 3000 storage needs, both now and into the future.

Special thanks go to Denys Beauchemin, who contributed significant material to this article.

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

March 12, 2018

Momentum moves towards Museum meeting

CHM displayDave Wiseman continues to pursue a 3000 user reunion for late June, and we've chosen to help invite the friends of the 3000. One of the most common sentiments from 3000 veterans sounds like what we heard from Tom Gerken of an Ohio-based healthcare firm.

"It was really sad seeing the HP 3000s go away," he said, talking about the departure of the system from Promedica. "I really liked MPE as an operating system. It was the BEST!"

The last HP 3000 event 2011 was called a Reunion. A 2018 event might be a Retirement, considering how many of the community's members are moving to semi-retirement.

Wiseman says that he's in retirement status as he defines it. "It's working not because you have to,"he said in a call last week, "but because you want to."

Most of us will be working in some capacity until we're too old to know better. That makes the remaining community members something like the HP 3000 itself—serving until it's worn down to bits. The event this summer will be a social gathering, a chance to see colleagues and friends in person perhaps for the first time in more than a decade.

The weekend of June 23-24 is the target for the 3000 Retirement party. We're inquiring about the Computer History Museum and a spot inside to gather, plus arrangements for refreshments and appetizers. There will be a nominal cover fee, because there's no band. Yet.

If you've got a customer list or a Facebook feed you'd like to spread the word on, get in touch with me. Spread the word. Email your friends.

No matter whether you have a contact list or not, save the date: one afternoon on the fourth weekend of June. Details to come. 

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

March 02, 2018

Fine-Tune Friday: One 3000 and Two Factors

RSA SecurID fobPeople are sometimes surprised where HP 3000s continue to serve. Even in 2018, mission-critical systems are performing in some Fortune 500 companies. When the death knell sounds for their applications, the axe gets swung sometimes because of security. Two-Factor security authentication is a standard now, serving things like Google accounts, iCloud data, and corporate server access.

Eighteen years ago, one HP 3000 shop was doing two-factor. The work was being coded before smartphones existed. Two-factor was delivered using a security fob in most places. Andreas Schmidt worked for Computer Sciences Corporation, which served the needs of DuPont in Bad Homburg, Germany. CSC worked with RSA Security Dynamics to create an RSA Agent that connected a 3000 to an RSA Server.

Back in that day, authentication was done with fobs like the one above. Now it's a smart device sharing the key. Schmidt summarized the work done for what he calls "the chemical company" which CSC was serving.

Two-Factor Token Authentication is a state-of-the-art process to avoid static passwords. RSA Security Dynamics provides an MPE Agent for this purpose which worked perfectly for us with Security/3000, but also with basic MPE security. The technical approach is not simple, but manageable. The main problems may arise during the rollout because of human behavior in keeping known procedures and avoiding changes, especially for security. But to stay on HP 3000 into the future, the effort is worth it, especially for better security.

The project worked better when it relied on the Security/3000 software installed on the server hosting Order Fulfillment. Two-factor security was just gaining widespread traction when this 3000 utilized it. Schmidt acknowledged that the tech work was not simple, but was manageable. When a 3000 site is faced with the alternative of developing a replacement application away from MPE/iX, or selecting an app off the shelf like SAP, creating two-factor is within the limits of possibility. Plus, it may not be as expensive as scrapping an MPE application.

Schmidt's article covers an Agent Solution created by CSC. Even 18 years ago, remaining on the 3000 was an issue worth exploring. When many outside firms access a 3000, two factor can be key.

DuPont wanted two-factor tested on its NT systems, plus the 3000.

NT and MPE were selected as pilots: NT because of the large number of servers running that environment; and MPE because of the thinking that this platform might be different from all others and more difficult to implement. However, the company also recognized the importance of running its 3000-based Order Fulfillment Process with a lot of different outside partners.

RSA’s first attempt to develop an agent for MPE was very simple: A token had to become configured for a combination of MPE-USER-ID.MPE ACCOUNT. This combination could not be reused on another token. It was not possible to use wildcards or to add SESSION-IDs or MPE-GROUP to have a complete logon string. Because of the MPE characteristic to share logons (on all levels of capabilities) this version of the agent was not what we were looking for. (More drastically: This agent could not function for the MPE platform).

The second attempt was much better: everything was changed to the chemical company’s already-existing Security/3000 setup. Now Security/3000 invokes the RSA Agent to contact the RSA Server. It transmits either the SESSION-ID or the MPE-USER-ID as the name of the token. If the token is known and allowed to access the HP 3000, the agent asks the user for the current tokencode plus PIN.

This agent also functions without Security/3000 by adding some lines to the System’s Logon UDC. This drops some additional functions in combination with Security/3000, like verifying a user profile in any case (SESSION-ID,MPE-USER-ID.MPE-ACCOUNT is defined as allowed logon in Security/3000, all others will be refused before starting anything), but it will work.

The project report details show this could be installed even before two-factor took a wide foothold in IT. Schmidt doesn't share the code in his article because it was custom work for a dedicated customer. But the process is worth a look, even if only to prove that custom code brings a 3000 into security compliance.

"One thing is essential," Schmidt wrote. "The RSA Agent for MPE does not replace the MPE password process like it does for Unix or NT. It is activated first when the HELLO string has been entered and the MPE password hurdle has been passed (Account, User, and/or Group Password) and (as an option) the basic check within Security/3000 for profile existence is passed. Now any other logon UDC functions are invoked, and this activates the RSA Agent.

Having Security/3000 in place is a good idea to replace the session passwords (if any) by supplying the tokencode.

Not having session names in place, the RSA Agent will add an additional password. I do not recommend eliminating the MPE password — it’s still a fence around your system and is needed for batch security (depending on the streaming security you have in place).

Complete details are in the NewsWire website's archived Technical Articles. Go forth and secure, if preserving an application is a better choice than locating an app replacement.

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