May 03, 2017

More than ever, old sticks trigger backups

Memory-cageRegular and frequent backups still hold their spot as keystones in a stable HP 3000 datacenter. The backups are even more essential this year. 2017 is the 14th year and counting since any HP 3000 components have been manufactured. Excepting some third party disk solutions, the average age of Hewlett-Packard's MPE/iX servers has more than doubled since HP stopped building the boxes in 2003.

In 2003 a manager might be daring enough to run a shop with a server built in 1991, the first year the 9x7 servers were manufactured. Systems in the first wave of PA-RISC design were still in service, but a Series 950 was a rare box by the time HP stopped building them. That oldest 3000 server at the time was still only 15 years old. That made the average age of a 3000 about 8-10 years.

Add 14 years to that lifespan and it's easy to locate a 3000 and its components which are more than 16 years old. The Series 9x8 systems turn 25 this year. The numbers came up in a recent emergency repair discussion out in public. A Series 918 at Harte & Lyne ground to a halt with a bad memory component, and even a pair of replacement sticks were duds on this 23-year-old system. The 918-928 servers are still among the most frequently used servers in the community.

The manager at Harte & Lyne keeps this hardware high-wire act going because of Powerhouse licensing problems. The repairs of his 918 coincided with very recent backups, but it could have been up to 30 days behind. Loss of company data was well within reach at this logistics company. The backups prevented the calamity that's now started to hit spare parts, too.

Read "More than ever, old sticks trigger backups" in full

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

Pivital Solutions: Your complete
HP 3000 resource

May 01, 2017

No obit for your OS, but not so for hardware

ObitThere's a new documentary in theaters about writing obituaries. The film Obit covers the work of obituary writers at the New York Times. No matter how you feel about mainstream media, the Times is one of just a handful of media outlets still telling stories about the lives of people who've just died. Obits were part of my reporting tasks when I broke into journalism, but I never wrote anything about someone famous while I worked at the Williamson County Sun. My very next job was Editor of the HP Chronicle, where people were famous within a modest community. I didn't write an obit at the Chronicle. I was eight years into the work at the Newswire when Danny Compton, a co-founder of ROC Software, died so very young at 40.

Compton and his wife Wendy were fun and important to reviving the Maestro user community. Why care about them now, you might ask, or even a legend like Fred White, whose life story I wrote up when he died in 2014? An obit is written for a death of something material, a person with a body, or an object which can be scrapped or destroyed. Something of value which made a mark on the world. The years continue to pull out HP's 3000's hardware from service. No one's making new gear with PA-RISC chips. Someday nearly everything that's an HP 3000 will go to dust.

The same cannot be said about MPE/iX. An obituary of the OS might be hard to prepare. The demise of HP's hardware could be written in advance. Advance obits, sitting up on the cloud by now, are a practice of those obit journalists. Obit writing tells about a life, not a death. Even as a celebrity continues to celebrate birthdays, their clock is ticking. Maybe that MPE/iX demise is in 2028. It's easier to see an obit arriving earlier for HP's hardware, though. It might read HP 3000, durable business server, dies at 51.

Hewlett-Packard's HP 3000, the first minicomputer which included a database wired into a file system, passed away on November 14, 2023 when the last CPU board failed to boot the server's operating system. The hardware, whose design was revised from the heyday of mainframes through the boom of the Web economy, carried commerce and data among entities as varied as aerospace makers and police departments. It is survived by the software written for the MPE/iX operating system as well as the database IMAGE/SQL.

HP's 3000 gear grew from a system that demanded raised flooring and specialized cooling to systems that could be carried under an arm. The hardware once read data from paper tapes and gained its ultimate IO abilities processing Internet data from standardized networks.

The obit for MPE/iX will be harder to write in advance. The OS is still going places.

Read "No obit for your OS, but not so for hardware" in full

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

April 28, 2017

Friday Fine-tune: directories and tombstones

ByetombstoneA 3000 manager wanted to know about adjusting privileges on their server. When the community's veterans started to respond, extra information rose up. Some of was about the management of files in MPE/iX, the kind of legacy recorded on what's known as a tombstone.

Tombstones are data used to solve 3000 problems and establish file access. HP says in its manual for programming in MPE/iX that "It's frequently necessary to obtain status information on a file to determine the cause of an error." A File Information Display is frequently called a tombstone, providing:

  • Actual physical and operational file characteristics.
  • Current file information, pertaining to end of file, record pointer, and logical and physical transfer count. Information on the last error for the file and the last HPFOPEN or FOPEN error.
  • When a file is opened, the final characteristics may be different from those originally requested because of defaults, overrides, :FILE commands, and the file label.

You can use the PRINTFILEINFO intrinsic to print a tombstone. It requires that you specify the file number returned when the file is opened by HPFOPEN or FOPEN. The tombstone can display either a full or short format.  If the file is open, it provides a full display. Otherwise, it provides a short display. Calling this intrinsic does not automatically abort the program.

You can call the PRINTFILEINFO intrinsic from programs written in COBOL II/XL and HP FORTRAN 77/iX. When calling from COBOL II/XL, use the FD filename. You can call the name PRINTFILEINFO directly from HP FORTRAN 77/iX programs. You can obtain the required file number by using the FNUM intrinsic.

Tombstones came up after one list member resurrected an answer about privileges from a 11-year-old post. Ray Shahan, still managing archival systems for Republic Title of Texas, heard his name in discussion about TD and RD privileges and how to control them. He quipped about not being heard from in ages.

Read "Friday Fine-tune: directories and tombstones" in full

Posted by Ron Seybold at 11:37 AM in Hidden Value, History, Homesteading | Permalink | Comments (0)

April 26, 2017

Wayback Wed: Doing the Beta patch Samba

Samba dancerIn April of HP's 2006, the company was exhorting its customers to use the 3000 improvements built by the vendor. Near the top of that list was the latest Samba, the printer and file sharing open source software that made it easy for 3000s to connect to Windows servers and resources. The latest version was 3.0.22, delivered to the world in the same year as the Samba community began to use it. The snag for a 3000 user: the official patch was only available to customers that year with an HP support contract.

The issue remained a troubling one that HP settled by the end of its 3000 business. Beta patches with improvements like SCSI Pass Thru and Samba eventually got unfettered distribution, even through they never passed the tests needed for General Release status. Today, the best way to get any HP 3000 patch is to use the guidance of an independent support company. We never tire of reminding readers that Pivital Solutions is an all-3000 provider, an official reseller of 3000s until HP closed that business, and one of seven holders of an MPE/iX source code license. It's a unique combination.

HP improved the 3000 and repaired bugs with a patch process that included alpha and beta testing before going into general release to customers. General Release status was important, because until HP's code was GR'd no one could get it but HP support customers. That was a wide gap in coverage. By 2006 the majority of the 3000 world was getting support from the independent companies which serve the community today. Alpha testing happened inside HP, and beta happened in the customer shops where a test machine was available. As the 3000's futures dwindled inside HP, though, the beta testers became harder to recruit. Customers usually took on patches in a PowerPatch collection. One was being prepared for the ultimate MPE/iX 7.5 release during April, 2006.

The announcement of a PowerPatch deadline was a routine message from HP's 3000 lab. The messages asked customers to pick up what they'd ordered though the Systems Improvement Ballot. "There are more than 30 beta-test patches still not qualified to be included in the PowerPatch. Tests of PowerPatches must be completed by customers on HP support. The 7.5 patches can only be tested on a subset of the 3000 installed base: any server released before the 9x8 systems won't be able to test anything created for 7.5."

HP lab liaison Jeff Vance told the user community, "If you voted for one of the many SIB items which are stuck in beta-test, waiting to become GR patches, and have not requested any of these patches, please do so ASAP. It really doesn’t do the user community much good to have a bunch of MPE enhancements stuck in beta-test, maybe never to see the light of day."

Customers' devotion to stability kept the beta test improvements in the dark. Changes to a 3000 became harder to justify on a stable, version-frozen server. Samba 3.0.22 was ported by HP for all three supported OS versions of that year, from 6.5 through 7.5. It was the final Samba version developed through HP's labs, a significant one since Samba gained the ability to join Active Directory as a member, though not as a domain controller. Samba was one of the first advances for 3000s resulting from Posix standards for MPE -- developments that earned the OS its /iX name.

As HP closed down the MPE/iX labs, concerns rose about beta-test enhancements like a current Samba disappearing for customer use. A beta patch that never made it to General Release might be unavailable once HP's support contracts ended. The vendor came through with a plan to make the beta patches available to the world: ask HP support for what you'd like by name. Samba 3.0.22 was dubbed SMBMXY6F, for example.

The patched MPE/iX code itself remains inside HP Enterprise, but HP 3000 customers enjoy a unique place in HP's support world. A current HP support contract isn't required to get the code. It's a dance, to be sure, that a customer must do with HP support—but at least now that HP's been divided into Enterprise and Printer companies, the 3000 questions don't get confused with HP printers using the same number.

Read "Wayback Wed: Doing the Beta patch Samba" in full

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

April 24, 2017

On the Surprises Of Six Decades

.Kaypro Man

I never expected to be doing this on the day that I turned 60. That's today. I joined the world of the HP 3000 when I was 27. I worked out my earliest articles about MPE (there was no iX) on a Kaypro II like the one depicted at right. Yes, that phone there was state of the art, too. I came hungry to write about PCs and Macs and figured the minicomputer beat would be a starting spot. This has become the destination, the world we love together.

In my late 20s I gave little thought to what my job would be by the time I got old enough to buy Senior tickets at the movies. I'm a journalist, so I think about the future more than some fellows, though. I had no vision about reporting about a minicomputer when I turned 60. Like you, I never believed I'd be doing this for so long. More than half my life, I've typed the letters MPE together. My life has been blessed, both with the rich array of people whose stories I get to tell, as well as the sponsors who support this life's work. I am thankful for both.

But here we all are, faithful to work that is rich and comforting, steeped in the knowledge that the 3000 is nearly 45 years old. Just at midlife, perhaps, at least in the measurement of a man. I'm entering my third act, I like to say. Friends are close at hand in my life and I continue to  create with words and ideas. My dreams are realized and something I'll never retire from. Perhaps that's true for you as well. The 3000 was supposed to be rubbish by now. Instead, people still want to buy HP's software for it

I'm here for the surprises like that. Survival is success earned across years and through uncertainty and crisis. Your support of that survival is a point of pride. We all earned our latest act. Enjoy the role you are playing, making way for the future.

On Saturday my bride and publisher Abby cooked up a party for me, a total surprise. It was the first surprise party of my life. Sometimes the universe gives us surprises. When we're lucky, the surprises are enduring and continue to reward our faith and hope. The love, ah, that flows on its own, propelled by our lives together.

Posted by Ron Seybold at 10:27 AM in History, Homesteading, Newsmakers | Permalink | Comments (2)

April 21, 2017

Federal program re-trains HP 3000 pros

US LaborHP 3000 IT pros have a challenge to overcome in their careers: how to add modern skills to the classic toolset they learned managing 3000s. Those between jobs must handle the costs to train, too. Craig Proctor has been spending time to learn the likes of C#, Java and Visual Studio. After one year of study, he didn't have to spend his own money.

"I took a dozen different classes," Proctor said. "The Trade Act paid for it all. It's possible to take one class at TLG Learning, or work with them to design a series of classes."

Proctor worked with a 3000 for more than 20 years at Boeing, as a Configuration Management Analyst and Business Systems Programmer Analyst. He left Boeing and began a period he calls Updating IT Skills in his resume at LinkedIn. TLG, based in Seattle, gave him training that he will blend with the business analysis that's so common in 3000 careers. He understands that by drawing on his recent education he'd accept at an entry level IT position. "You get the merger of an experienced analyst, using new tools," he said of his proposal to any new employer."

An extension of the Trade Act signed into US law by President Obama was one of the few bills to escaped the partisan logjam. A federal website describes it as a way for foreign-trade-affected workers to "obtain the skills, resources, and support they need to become re-employed." $975 billion in federal funds have been sent to states like Proctor's in Washington, adminstered by each state. Furloughed workers file a petition for training, job search and relocation allowances. These pros have an average age of 46, which is the younger side of the HP 3000 workforce.

Read "Federal program re-trains HP 3000 pros" in full

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

April 19, 2017

Where will HP even take 3000 money today?

CashboxCompanies want to do the right thing, even while they're keeping their budgets in order. When a customer of the 3000-only support shop Pivital Solutions needed to add Netbase/iX to their server, it was time to find the correct way of doing that. The customer didn't have a license for the HP software needed to power Netbase.

HP once sold such a thing. More accurately, HP's distributors sold licenses for this subsystem software. The most common purchase was TurboStore, but items like a COBOL II compiler and odd ducks like Business Report Writer and Allbase 4GL were on HP's price list. Now it looks like there's no longer a list, and scarcely anyone left to take a check.

Pivital's Steve Suraci was resolute about serving his customer with integrity. It might've been a lot easier for a 3000 vendor to just load a subsystem onto a server that HP stopped supporting more than six years ago. Some customers need to satisfy license requirements on everything, though. Getting a license meant finding a reseller or someplace inside HP Enterprise to send the check. Media for subsystem software on the 3000 doesn't ship from HPE by now. This would be a license-only transaction. But where was the cash box?

After Suraci reached out to me, I touched base with people in the 3000 world who might still need a contact to purchase MPE/iX software from HPE. The first wave of requests came back stumped to identify who'd be running the 3000 store anymore. A trip to the website for Client Systems, the final 3000 distributor in North America, draws a couple of parking pages for domains. The OpenMPE advocates planned for many things in the eight years they worked with HP. A missing HP pay station was not among those plans.

Read "Where will HP even take 3000 money today?" in full

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

April 17, 2017

3000 Community Meets Up on LinkedIn

LinkedIn 3000 CommunityMore than 660 HP 3000 veterans, pros, and wizards emeritus are members of the only 3000 group on LinkedIn. Last week a message from 3000 vendor and group organizer Dave Wiseman invited them all to meet in the Bay Area in the first week of June.

Wiseman organized a couple of well-run meetings in the UK over the last few years. The latest one he's working to mount is a users group meeting without the work, as he said in a brief LinkedIn discussion message. The message provides a chance to point out one of the best-vetted gatherings of 3000 talent and management, the HP 3000 Community.

I created the 3000 group nine years ago and have screened every applicant for membership. You need to have HP 3000 work history in your resume to capture a spot in this group. As the years have worn down the mailing list for 3000 users on 3000-L, this LinkedIn group now has a greater membership in numbers.

LinkedIn is now a part of the Microsoft empire, a $26 billion acquisition. That's good news for Microsoft customers whether you use Windows or something as explicit as the lightweight ECTL tool for SQL Server, SSIS. The latter is being used by The Support Group on a migration of a MANMAN site to the new Kenandy ERP package.

Reid Hoffman, the founder of LinkedIn who ran a social networking site while Mark Zuckerberg was still in middle school, is now on the LinkedIn board of directors. The pedigree of LinkedIn flows toward services as well. The highly regarded training site Lynda.com is now a part of LinkedIn. There's a Premium membership to LinkedIn, priced as low at $29.99 a month, that includes access to every course on Lynda. You'll be staggered to see how much business, design, development, and technical training is available through the same network that hosts the only HP 3000 online community.

Job searches are complex and a trying experience for many HP 3000 tech pros. LinkedIn makes it easier. If nothing else, a good-looking resume complete with video, audio and work portfolio examples is part of being a LinkedIn member. Applying for a job is easier in many places by pointing to your LinkedIn resume.

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

April 14, 2017

The way to San Jose offers 6-figure 3000 job

Developer posts in the HP 3000 world don't come up often, but companies and organizations need talent. On GovernmentJobs.com, a position is open that has a starting salary of $108,802. For the right professional, the pay could go as high as $132,254.

Seeking a COBOL/HP3000 developer who will be responsible for maintaining the AIMS application which runs on a HP3000 system and support the HP3000 system administration work with other team members. The AIMS application is the main appraisal and assessment application for the Assessor's Office. In addition, the selected candidate will help in the AIMS replacement project, which entails rewriting the legacy AIMS application to run in modern platform.

AIM3000The software is probably the venerable AIM/3000, a financials package that was shiny and new in 1983. The job is at the County of Santa Clara, a shop where just two years ago the organization was looking for help to rewrite AIMS into an application "running on a modern platform." The listing for this year's job reiterates that movement off MPE/iX systems. This time out, the position is being listed as Information Systems Manager I.

The successful candidate should have experience with program development work in COBOL on HP3000 as well as HP3000 system administration experience. The candidate must have the knowledge and experience performing duties listed below.

  • Maintaining the software application running on HP 3000 system.
  • Supporting the HP 3000 system administration work with other team members
  • Program development work in COBOL on HP 3000
  • HP 3000 system administration work such as batch job scheduling, system backup and restore, printer and output management among other system management tasks.

The 2015 listing was seeking an Information Systems Analyst II at a lower pay scale. The new job could well be the manager for the 2015 staffer. The position closes in two weeks, on April 27.

 

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

April 12, 2017

Oracle serves a profitable slice of cloud

IaaS revenue sharesAmazon Web Services and Microsoft's Azure receive the established reputation for cloud resources. Oracle is the new player in the Infrastructure as a Service (IaaS) game. Within a month after Oracle announced sustained profitability on its cloud operations, Stromasys rolled out its plans for offering HP 3000 virtualization through Oracle Cloud.

Oracle's spring numbers showed the third straight quarter of increasing revenues overall, even while its business in application software declined throughout those months starting in mid-2016. Cloud growth, primarily in platform and software services, is making up the difference at Oracle. Oracle means to get its slice of the cloud's pie. Oracle is not on the chart from 2016. But neither is Salesforce, a company with 4 million subscribers. Revenues are not the only meaningful measure of the clout in cloud computing.

Rodney Nelson, an analyst at Morningstar, said the results show "new cloud revenues are more than offsetting the declines in software license sales." Oracle's CEO Larry Ellison said that Oracle Cloud will eventually be the vendor's largest business, outpacing revenues from the application suites that built the $40 billion a year giant.

The coincidence of a new platform for HP 3000s arriving on the cloud hosts of HP's most ardent competitor is profound. Hewlett-Packard's Enterprise business has cast off the futures of MPE/iX and OpenVMS, exiting markets that were still growing, albeit at low rates. The trends away from legacy infrastructures like proprietary OS on vendor-built hardware are mirrored in Oracle's shifts.

New software licenses, a measure tied to Oracle’s on-premise software business, declined in the latest quarter by 16 percent. The decline was smaller than the drop of 20 percent posted in Oracle's fiscal second quarter. This is the pattern HP's own Mission Critical Business operations followed. Ultimately, trends like that led to dividing HP into two companies. When profitable business shrinks, the computing model must be changed. Those changes track with the concept of eliminating the need for on-premise hardware to host MPE/iX operations.

Read "Oracle serves a profitable slice of cloud" in full

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

April 10, 2017

3000 backup strategy for closing Sundays

ClosedOnSundayEaster Sunday is on this week's horizon. While it's a rare day of closure at our local HEB grocery chain, Sundays are another sort of closure for 3000 managers. Nearly all of them want their partial backups of the weekdays to wrap up before the backup begins that will serve the work week. If you do full backups every night and want to make the new strategy to do partials during the week and a full on Sunday, there's a way to make that work. Donna Hofmeister, one of the former OpenMPE directors, explained the strategy in a message to 3000 managers.

First you need to decide what kind of partial you want to do.  On Tuesday, do you want to backup all files changed since Sunday's full backup or do you want to backup all files changed since Monday's backup?  (and so on....)

There are some things to think about here. If your "line in the sand" is always Sunday, then you have to deal with knowing that by Friday/Saturday your "partial" backup is likely going to be sizeable and will take longer to run. On the other hand, if you ever have to do a big restore, your restore plan is plan is pretty simple -- you'll need your last partial and your last full backup.

If your "line in the sand" is always yesterday, then your "partial" backups will be relatively small and quick. The flip-side is your big restore could be very complicated, since you'll need every partial backup through Monday plus your full backup. I think most people set the backup date as "Sunday" and do partials from there. But there's a technical bit that's also important.

Read "3000 backup strategy for closing Sundays" in full

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

April 07, 2017

Friday Fine-Tune: Creating the perfect CSLT

Editor's note: A classic technique, detailed here by the NewsWire's Hidden Value editor emeritus John Burke.

PerfectTapeA question about creating a CSLT for a Disaster Recovery test turned into a general discussion about what the perfect CSLT should look like. A system manager wanted to use the STORE option on the SYSGEN TAPE command to store additional files onto the CSLT he was creating for his DR test but was running into trouble trying to specify STORE options as part of the SYSGEN TAPE command. In particular, he wanted to simply add ;SHOW to get a listing of all files stored.

The answer to his original question is to use an indirect file, as in

sysgen>TAPE MODE=VERBOSE DEST=OFFLINE STORE=
^CSLT.INDIRECT.SYS

where the indirect file contains whatever STORE directives you want in addition to the file list.

One contributor recommended robust efforts to get a listing: “A backup tape is of limited value without a listing. For Disaster Recovery purposes it is also a good idea to have the original HP tapes and patches with you as it is possible to create an SLT that does not install or work on a different HP 3000 system.” This same contributor also suggested creating a disk file with a listing of all the stored files.

Read "Friday Fine-Tune: Creating the perfect CSLT" in full

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

April 05, 2017

Stromasys Charon lifts off with Oracle Cloud

Charon on CloudThe makers of the only emulator for HP's 3000 hardware have announced a new service to deliver the Charon virtualized MPE/iX systems over the cloud. Stromasys eliminated the need for HP-branded hardware when it released Charon for HP 3000 users in 2012. The latest development eliminates the need for any local hosting resources by moving processing to Oracle Cloud.

“We are thrilled to offer a robust cloud solution to our customers by collaborating with Oracle,” said John Prot, Stromasys CEO in a press release. Oracle VP for ISV, OEM and Java Business Development David Hicks added, “The cloud represents a huge opportunity for our partner community."

The release notes that the Oracle Cloud is "the industry’s broadest and most integrated public cloud, offering a complete range of services across SaaS, PaaS, and IaaS. It supports new cloud environments, existing ones, and hybrid, and all workloads, developers, and data."

Cloud-based HP 3000 and MPE/iX computing is a solution Stromasys brings to the 3000 community for the first time. While remote-based HP 3000s have been an IT staple for decades, a system hosted without the need to integrate and install any host systems is a breakthrough offering.

Charon for HPA relies on a Linux-based host, making the cloud-provisioned services from Oracle a minimal transition from local-hosted Intel servers. Charon on Oracle Cloud includes a license for the Charon virtualization software along with unmetered Oracle Cloud services and support for the combined solution.

Oracle says its cloud offering is more complete than those from Amazon Web Services. “AWS is an incomplete cloud," said Vice President of Cloud Platform Ashish Mohindroo. "The main AWS  focus is IaaS, compute, and storage. If you want to store files in the cloud [or] spin out a new server, you’re good. But most customers want to run applications, and with AWS most of those capabilities come from third parties. So when it comes to integration, you’re on your own.”

Read "Stromasys Charon lifts off with Oracle Cloud" in full

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

April 01, 2017

History processor heralds new Wayback/iX

A reconfiguration of HPCALENDAR intrinsic capabilities is opening the door for date revisions, one of the last remaining roadblocks to an everlasting MPE/iX lifespan. The design and development of the project has been underway in a Sourceforge repository since 2013, with a handful of volunteers working to deliver the new intrinsic WAYBACK.

BillandDaveworkingVolunteers cited the work of the Stromasys Charon HPA system for providing the ongoing inspiration to keep the work alive. One developer, who requested anonymity for fear of having his report labeled fake news, said that the everlasting platform for MPE/iX software triggered the stealth project. "This is no fool's errand," he said. "We'll bring these apps into a future HP never dreamed about. That's the value of the HP Way, retaining value and profitability."

When successfully tested, WAYBACK will bypass the 2028 roadblock to date processing. The Sourceforge team, which calls itself the League of Joy, believes that an additional processor will have to be added for HP 3000 hardware manufactured by Hewlett-Packard. Emulated and virtualized HP 3000s are expected to need no such separate CPU, although a high number of cores will make date manipulation seamless.

The end of accurate date processing — a state that the League calls Fake Dates — was never a concern when MPE was first developed. "This is not a bug, really," said Vladimir Volokh, who is not a part of the League development team. "It's a limitation. This 'end of 2027' date was as far away as infinity when MPE was created." Adding a Wayback/iX to the package of Fundamental Operating System components is the next step in the work to add pages to the 3000's calendar.

HPCALENDAR, rolled out by Hewlett-Packard engineers in the late 1990s for the 6.0 release of MPE/iX, has been a newer tool to solve the old Fake Date problem. Since HPCALENDAR is fresher than CALENDAR, it's only callable in the 3000's Native Mode. WAYBACK intercepts the calls to CALENDAR and pipes them though HPCALENDAR, or so it's hoped once this history processor makes its way through beta testing.

In the meantime, one of the developers in the League of Joy suggested that IT pros who want their MPE/iX apps to run beyond 2028 should bone up on using intrinsics. Suggesting the Using Intrinsics whitepaper on the 3K Associates website, D. D. Browne predicted a swift end to the Fake Date roadblock.

"We've all been keeping the 3000's applications alive for longer than NPR has been broadcasting real news," Browne said. "It's going to carry us all beyond retirement," he said of any system running with WAYBACK. "Back in the days the 3000 was built, TV and radio stations once signed off the air. This operating environment is never going off the air."

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

March 30, 2017

Puts, Gets, and Serving Up Transfers Faster

Server TrayHP 3000s are exchanging files with other servers, a process that's included the FTP protocol for more than 15 years. This capability was once so magic that the arrival of Samba file exchange on MPE/iX was lauded as a breakthrough. FTP is quite a ways off the most current of transfer protocols. One manager's started a discussion about how to improve transfer speeds to and from the 3000, though. He's using DSCOPY as well, but prefers the PUTs and GETs of FTP.

The advice that's current about FTP/iX says that hard-coding the 3000's ports (100mb full duplex, or 10mb half) is one way to speed things up. Ensuring your traffic is not running through a proxy (called "being proxied) is another idea. Measuring the speed of a PUT against a GET is one step in discovering why the 3000's FTP might seem slow.

In 2008, MPE/iX gained a secure version of FTP—at least part of one. This SFTP functionality arrived at the end of the Hewlett-Packard lab era for 3000s, a period when new tools were not being placed into wide use. Sites were locking down their 3000 scope of operations to ensure stability. The port of this then-current functionality fell short of complete: only an FTP secured client got created. PUTs could be secured, as well as GETs. But only from Windows, Unix, or Linux hosts to the 3000. The 3000 wasn't going to dish out files using secured FTP. There are notes in place to carry the work forward, though.

MPE/iX tools and components are also out there to complete this securing of file transfers. OpenSSH is the best-known protocol. A quick-start bundle can be downloaded from the MPE-OpenSource website run by Applied Technologies. There are SFTP installation instructions at Applied, too. Someone who's got a need for securing FTP transfers will need to do the server side of the porting, which was completed on the client side by Ken Hirsh, Mark Bixby, and Mark Klein. Requests to speed up FTP are a sign this porting would be more than just an open source hobby project.

Read "Puts, Gets, and Serving Up Transfers Faster" in full

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

March 27, 2017

HP's storage devices trigger extra 3000 care

TractionWhere can an IT professional ask a question about bringing a 3000 peripheral back to life? The best place to ask is a support company, one that can even supply a replacement device if the aging 3000 iron has gone offlline. The next best place is the 3000 newsgroup and mailing list. The free advice has covered warnings as well as solutions on how to rescue the process of recovery.

The 3000 console shows an ABORTIO detected on device 9. A backup stops at Wesleyan Assurance Society and Jill Turner asks what causes the abort. "The backup logs off. No one has typed a command to do that. What would cause that message to appear?"

Tracy Johnson manages 3000s at TE Connectivity. "Sometimes an error with the mechanism shows up as an abortio. It doesn't have to be a typed command. Hitting the eject button in the middle of an operation would do it.  I have forced the issue myself sometimes: 'Damn, wrong tape! Press eject.' It then shows up as abortio detected."

Hmmm, mechanism error. That amounts to a troubled piece of hardware. Al Nizzardini suggests that the troublesome tape drive get a thorough cleaning, "and have a spare on hand to do a replacement." Good advice, although a manager has to ensure the backup tapes written by one elderly HP drive can be read by another. It's not automatic.

Disk drives have 3000 managers on watch, too. Companies have options beyond device replacement here in 2017.

Read "HP's storage devices trigger extra 3000 care" in full

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

March 24, 2017

A Few Stops on the 3000 Maintenance Line

ToolkitAfter inviting our readership to share their HP hardware service providers, we're got some early entries to share. The list of 3000 support teams is not the same as the companies who continue to service hardware. Much of the time these are different companies. While a manager can find some help on MPE/iX administration from a hardware outlet, this account-level support is more thorough and fine-tuned coming from a company like Pivital Solutions, or from The Support Group for MANMAN and ERP-focused engineering.

Even HP recognized this when the company was the primary support vendor for 3000 sites. A Customer Engineer was the equivalent of that hardware guru, working in the days before what Hewlett-Packard called Phone In Consulting Service. Close to 30 years later, onsite hardware maintenance is still the linchpin of keeping HP's aging hardware alive. Customers don't perform much of this while working with a vendor. "There's a liability issue when you have the customer do the component replacements," said one rep who's been working 3000 accounts for several decades.

A Software Engineeer was something very different than an HP CE. Not only did they know IMAGE at a depth that could outpace a CE, they often knew a customer's applications. Not just the HP-branded apps, either. In time, the top-tier utility vendors offered a kind of SE service. Adager was well-known for saving a site from calamity that wasn't yet a customer.

Without further preface, here's a few notes on some hardware resources who've volunteered information or been verified by their customers.

Saratoga Computers: "We are a group of ex-HP CE's," says Jim Maher. "All of us are experts servicing HP3000, 9000 and yes even 1000's. our average experience working on HP equipment is over 30 years." Hardware support providers usually branch out to other systems, such as Dell and HP's ProLiant systems. even Cisco switches, workstations and printers. Maher says that's the case at Saratoga.

Blueline Services: Bill Towe founded this provider that backs up the internal needs at The Support Group, among many other 3000 customers. In some cases the best way to bring up a downed 3000 is to ship a replacement system; that's what happened once, according to the Support Group's Terry Floyd. Component-level service is available as well.

Read "A Few Stops on the 3000 Maintenance Line" in full

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

March 22, 2017

Webinar explores data migration roadblocks

MB Foster is broadcasting a webinar on Thursday at 11 AM Pacific Daylight Time, a briefing that covers tools and strategies to move data. The program promises to cover components of data migration projects. As is often the case, the webinar also will highlight the potential roadblocks to migrating data. Explanation of methods, project planning, and data governance are also a part of the one-hour show. Registration for access is at the MB Foster website.

PotpourriIt can take months to move data from one platform to another. Just ask Bradley Rish, who as part of the Potpourri Group managed a two-step process to migrate away from Ecometry software on an N-Class HP 3000. Potpourri first went to Ecometry on HP-UX, then a few years later moved away from HP's proprietary environment to Windows. Same application, with each move aimed at a more commodity platform.

But there was nothing commodity about the company's data. Data migration required eight months, more than the IT pros at the company estimated. Rish said that two full-time staffers, working the equivalent of one year each, were need to complete the ultimate migration to Windows.

Migrations of data don't automatically mean there's an exit from the HP 3000. At Potpourri, after a couple of years of research by IT, the exit from the 3000 was based on HP's plans for the computer, not any inability to serve more than 200-plus in-house users, plus process Web transactions. It's a holding company that serves 11 other web and catalog brands. More than half its transactions occur in the final 90 days of each year. Holiday gift season is the freeze-out time for retailer IT changes.

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

March 20, 2017

Data migration practices support cloud IT

Crm-data-migration-steps-cloudCompanies moving from HP 3000s to cloud-based IT are reaching deeper into data migration. In some cases, the records that have never left a datacenter are becoming an asset managed in cloud computing. The process prompts lessons on tools and practices that can be new to IT administrators and ERP developers in 3000 shops.

Work at The Support Group is helping to lead manufacturer Disston Tools onto the Force.com cloud services, leaving the classic MANMAN ERP application behind. Disston is adopting the Kenandy cloud ERP solution as a MANMAN replacement.The tools to migrate Disston's data cover a wide scope of functionality, from the Minisoft IMAGE-savvy ODBC utility to the commonplace Microsoft SQL Server Information Services (SSIS).

The latter tool can be priced more effectively for a smaller enterprise if it can be licensed as a developer version for a one-time data move, said the Support Group's David Floyd. "I'm not running a production database with SSIS," Floyd said. He added that it took four days of training to become fluent in using SSIS. At the Force.com cloud service, a proprietary database takes the place of IMAGE to store company information that has sometimes never left the world of MPE/iX and the 3000.

Read "Data migration practices support cloud IT" in full

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

March 17, 2017

Friday Fine-Tune: Moving all disks at once

I want to take all my disks, system volume set, and the user volumes, and move them to another machine that has no disks. How can I best do this?

Lars Appel replies

You might use SYSGEN to create two different config groups in the SYS account, one for the old system (e.g. CONFOLD), and one for the new system (e.g. CONFNEW). To create the new config you might start with one of the existing config templates, e.g. CONF9x8.SYS for 3000/9x8 systems. Use BASEGROUP to open it, adjust IO to your needs and KEEP it as CONFNEW.

7935Just make sure that every disk gets an LDEV in the new config. Paths and LDEVs (except for LDEV 1) do not need to be the same on the new system. MPE/iX will notice (and "collect") all available volumes during bootup (as long as they are "visible" by a configured LDEV number).

Shutdown the system, plug disks into the new box, power it on, boot from the primary path (or enter the appropriate path for LDEV 1) and at the ISL prompt do a START NORECOVERY [NOSYSSTART] GROUP=CONFNEW.

You might also need to adjust NMCONFIG with NMMGR as a different system will probably have the LAN cards at a different physical path. In case you make a copy of NMCONFIG, make sure it stays on LDEV 1 (FILE;DEV=1).

We replaced LDEV1 on our HP 3000, did an INSTALL. Then we did
RESTORE *T;/;DIRECTORY;SHOW;KEEP;OLDDATE
The MPE-filespace was restored normally, but the HFS filespace was not. RESTORE told me to use CREATE=PATH which I then did. The DIRECTORY is on my STORE tape - so what went wrong?

Wolfgang Kinscher, and Gilles Schipper reply:

If you are planning an install keep this in mind: Do not specify the option "DIRECTORY" with a partial (DATE>=) backup. STORE will not put the HFS directory structure on tape. Do the following instead: STORE ;*T;DIRECTORY stores all of your MPE/HFS directories on tape. Then do your partial backup without DIRECTORY option

After the install, first restore your DIRECTORY with RESTORE *T;;DIRECTORY and then restore your partial and your latest full backup respectively.

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

March 15, 2017

3000 job fills at mainframe's speed

Ursinus_College_sealPublic listings of HP 3000 positions can be tricky to track. A Web search I run with Google tagged an opening in Pennsylvania last week. Google will track a search term and email results to you. Although "HP3000" returns a lot of pages about 3000-horsepower motors, it sometimes unearths news.

The position looked like a classic one and didn't seem to be related to migration work, although it's hard to verify the latter. The immediate opportunity, posted by David Mortham of staffing firm The Fountain Group was for an "HP 3000 Mainframe Engineer."

We are seeking a HP 3000 Mainframe Engineer for a prominent client of ours. This position is located in Collegeville, PA. Details for the position are as follows:

  • Good knowledge in HP3K Mainframe.
  • Good Experience with COBOL, Suprtool, Cognos Quiz, QTP and MPEX.
  • Able to work on enhancements as per the business requirements.
  • Able to troubleshoot issues within HP Mainframe Environment.
  • Able to handle the technical production support issues
  • Prepare technical documentation for various processes flow applications.
  • Able to manage business requirements, writing business requirement documents / technical design documents.
  • Excellent design and technical query writing skills.

It's all there: Powerhouse 4GL, aided by top tools MPEX and Suprtool, with the applications in COBOL. It wasn't available less than a week after the March 6 posting. 3000s can not only be as fast as any mainframe, the remaining openings in 2017 move off the market at similar speeds.

There's not much of a clue about where this 3000 job, a full time one at that, was open. But the listing floated up on the Higher Education job board. Ursinus College, an institution nearly 150 years old, is in Collegeville. Universities earn higher regard when they're older. Some business computer systems do as well.

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

March 13, 2017

3000 friends: Meet in the Valley, or seaside?

Dream InnAn HP 3000 user group meeting has become so rare by 2017 as to be legend. After Interex closed up shop suddenly in 2005, Alan Yeo organized a late-binding gathering in 2005, then another in 2007 and another in 2009, all in Silicon Valley. By 2011, Yeo was working along with me and Marxmeier Software's Michael Marxmeier to put on the HP3000 Reunion at the Computer History Museum. The Reunion provided the debut spot for the only HP 3000 emulator, the Charon HPA from Stromasys.

Then the meetings began to evolve to reconnect us without needing a formal program. The most enjoyable part of the formal meets, after all, was the SIG-BAR gatherings in the hotel lounges. Gossip and speculation were always a key part of SIG-BAR. Lately the meetings have moved exclusively to this Special Interest Group. Last year there was a lunch meeting at the Duke of Edinburgh pub, set up by Birket Foster.

There's something about these leaders that can rouse people to return. The Bay Area in summertime has drawn a rich collective of 3000 veterans and experts. In 2008 the Computer History Museum hosted a seminar on 3000 software history. Another fellow with user group meeting experience is leading this year's charge to the Valley.

Dave Wiseman notified us about a 2017 gathering he's setting up for the Bay Area.

So we used to all be good friends in the community and its about time we met up again for a beer or three. We had a couple of very pleasant meetings in the UK and I am in California early June so I thought that I might organize one in the valley around June 5/6/7th. I am happy to organize a meeting while I'm in San Francisco. Could you tell me if you would be interested in coming? We’d love to see all of our old friends again

Dates: Any preference for Monday June 5th, or Tuesday June 6th?
Location: San Francisco/ SFO airport hotel/ Cupertino, or Santa Cruz (I’d see if we could book the Dream Inn for a Santa Cruz location)
Time: Lunch, afternoon or evening

Please email me, davebwiseman@googlemail.com, so we can see if there are enough people interested to make it worth everyone's while.

I'd put a vote up for the Dream Inn (above, seaside) since it was a stop on my cross-California 20th wedding anniversary trip with Abby. They're even got a Dream Floor at the top.

Read "3000 friends: Meet in the Valley, or seaside?" in full

Posted by Ron Seybold at 08:18 PM in History, Homesteading, Newsmakers | Permalink | Comments (1)

March 10, 2017

Friday Fine-Tune: Going Beyond JBOD

By Gilles Schipper

Mod 20sOne of the most cost-effective ways of advancing the reliability of your legacy system may be to replace your existing “JBOD” disk system with a much more reliable disk system. MOD20 units, still a better deal than individual disks, can provide a good starting point to implement RAID. JBOD is an acronym meaning “just a bunch of disks” — which would characterize the majority of HP 3000 systems as they were initially sold. JBOD disk systems comprise a set of independent — typically SCSI-connected — disks, which are each seen by the HP 3000 as a single logical device number or LDEV. Each disk LDEV is associated with a “volume set” and the failure of a single disk renders the “volume set” to which it belongs inoperable and un-accessible.

Traditionally, most 3000 systems have comprised a single volume set (specifically, the required SYSTEM volume set, with the brevity-challenged label “MPEXL_SYSTEM_VOLUME_SET”).

Systems comprising a large number of “JBOD” LDEVs increased the likelihood of system downtime, since the failure of a single, old disk effectively resulted in a “down” system — requiring a time-consuming disk replacement and system reload before the system could properly function once again.

To mitigate such delicate exposure to a single disk failure, many installations implemented the “User Volume Set” feature built in to MPE/iX, then constructed multiple volume sets so that the failure of a single disk affected only the volume set to which it belonged.

For practical purposes, the only real benefit to this approach was to reduce the amount of time required to replace the disk and reload only the data residing on the affected volume set. (In reality, it was usually quite unusual for a system to continue normal, or even minimal operation with even a single unavailable volume set).

Read "Friday Fine-Tune: Going Beyond JBOD" in full

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

March 08, 2017

ERP ecosystems now being fed by analysis

EcosystemThere's a rule that Sue Kiezel of the Support Group follows for her ERP clientele. Try not to let the IT department establish architecture for a replacement system. Consultants who have experience with business rules and structure are the best choice to arrange the parts and plan the new flow.

"IT is for infrastructure, and for development," she said while leading me on a tour of the new denizens inside the Kenandy ERP ecosystem. "Put your business experts on the team. You'll find someone to code it inside IT."

The issue to face while relying on the current generation of IT pros is that they no longer have broad views of how companies organize business processes. In the era when the 3000 was growing, the most dynamic beasts of the ecosystem were programmer analysts. The PAs were usually people who knew the business first and learned to program as a way to solve business problems. These days the development skills seem to wag the dog.

The IT department is essential to the success of any ERP ecosystem because that's the source of support. An ecosystem was the aspect of 3000 ownership in the biggest trouble. However, that diagnosis came from the days when outside vendors who sold apps and databases were considered the ecosystem. In some ways, the new ERP that the Support Group implements delivers a new generation of ecosystem: Kenandy's tools and modules, built with the Salesforce software that underpins it all. One surprise is that even the database has become a built-in, specialized choice. Dare we say it, proprietary, even.

Read "ERP ecosystems now being fed by analysis" in full

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

March 06, 2017

Add-on applications pour down from clouds

Acrylic-finish-paint-250x250Forecasting software has been a $2 million addition to enterprise resource planning systems. The P in ERP signifies a mission to search for a view of the future. Add-ons like McConnell Chase's FD7, purchased for an additional $2-$4 million on top of software investments in monolithic apps like MANMAN, generate a strong business for vendors. In-house systems are a good match for that kind of app. Today's IT options can bring this kind of forecasting power onto the pallettes of many more companies.

The analyst and software experts at The Support Group have been implementing the Kenandy ERP solution at an HP 3000 MANMAN site. Kenandy runs on the internal architecture of Salesforce, the cloud IT supplier to millions of sites. In a cloud IT solution a company buys a subscription to an application. Kenandy, for example, is an application choice in the world of Salesforce. Rather than hoping for a third party to create a tool that can access Kenandy, the new cloud model delivers forecasting as an option on the bill of fare.

Forecasting was never a built-in MANMAN module, Terry Floyd of TSG reminded us last week. David Floyd of the company recently returned from data integration work at Disston Tools in Chicopee, Massachusetts. Together the two men explained how cloud ERP can bring essentials like forecasting within reach. They're in the the second generation of software expertise at TSG. Terry Floyd wrote archiving software for MANMAN during the 1980s, for example, a product that was sold and added to MANMAN sites. This sort of software can be added to a cloud ERP solution like Kenandy's. Today, however, it's a subscription option, as quick to integrate as adding a tier of TV channels to a cable subscription.

Changes that spring from the migrations forced by HP have been costly. Not every new look triggered by HP's drop of the 3000 is negative, though. Adding planning power has been a multi-million dollar bet in the old 3000-era strategy. There are, however, a few aspects of cloud computing which the old-era model continues to beat.

Read "Add-on applications pour down from clouds" in full

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

March 03, 2017

When and how to back up 3000 directories

Editor's Note: Homesteading Editor Gilles Schipper weighs in on  using the 3000's store directory option, rather than invoking the buldacct program, to make clean backups.

By Gilles Schipper
Homesteading Editor 

CityDirectoriesIt's common to see confusion surrounding the use of the ;directory store option versus the buldacct directory creation program. In order to benefit from the store ;directory option, one has to utilize the option almost perfectly in both the store and the restore following a system INSTALL. Consequently, it becomes much easier to fall back on the buldjob options to re-create the directory -- although that option is inferior.

In order to be able to effectively utilize the directory option, the first thing that must be done properly is to ensure that the appropriate ;onvs= option is also used in the case where user volumesets are utilized. Otherwise, the non-system volumeset directories do not get restored after the INSTALL since they are not on the tape.

But even if the store part is done correctly, the other opportunity to go wrong presents itself during the reload process.

The proper procedure during reload is as follows:

1. perform INSTALL
2. restore ;directory from tape
3. re-create disk and volumeset environment via VOLUTIL

Then -- and this where many go wrong,

4. Again restore ;directory from tape (this re-creates the volumset directory environment on the master volumes for all user volumesets for those utilizing it)
and then
5. restore files
6. reboot with start norecovery (to enable network functionality)

Of course, for those that do not utilize user volumesets, the directory option becomes much less error-prone. And, for those that utilize third-party backup utilities, the ;directory option -- as utilized in the MPE store command -- is generally replaced with a similar option in the various backup utilities.

Read "When and how to back up 3000 directories" in full

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

March 01, 2017

Wayback Wed: Customers' Proposition 3000

Computerworld April 22


During the month of March 21 years ago, the 3000 community tried to raise a ruckus. The object of Proposition 3000 was to prod HP into making the 3000 a full citizen of the future of business computing. After only a couple of years of introduction, the new processor HP was developing with Intel looked like it would pass by the world of MPE/iX. HP and Intel dubbed the IA-64 technology the future of computing. HP had backed away from plans to make the 3000's OS run on the new chip it was calling "Tahoe."

"The company appears to be making a fundamental but flawed assumption that MPE migrations will be channeled directly into HP-UX or NT-on-HP hardware." This was enough of a crisis that application vendors were standing up at an Interex Programmer's Forum to report HP asked them to rewrite their apps for HP-UX. We launched the NewsWire with a fanfare of it promoting the HP 3000 Renaissance. Not so fast, HP's top management was saying. We set down the challenge to HP and its customers in our FlashPaper (which you can read here to recall the outrage of the moment.) In this era, NT was the name of what would become Windows Server.

Customers want these systems, and vendors believe in their superiority. But those kinds of business blessings apparently clash with HP's profit motives; that's the only reason we can fathom for threatening to force an entire installed base to migrate to HP-UX or NT. You can decide for yourself how that kind of a productivity hit will impact your company's profits.

FlashPaper headline Mar 1996This was the canary in the mine shaft, the HP debate about whether to include MPE/iX in the future of business computing systems. In 1996 the IT world was allowing HP and Intel to call Tahoe the future, because the joint project was only a couple of years old. Tahoe had not yet become Merced, and then Itanium, all the while slipping release dates and getting lapped Intel's own by x86 generation enhancements. In 1996 the future looked to be slipping away. The most alarming development was HP asking vendors to rewrite for Unix. Soon enough, a few of them did, most notably the software company that put the 3000 into the world of the Web: Ecometry.

At the meeting we learned the problem wasn't really profit at HP. At the time of the Proposition, HP was earning $600 million a year in profit on sales of $1.2 billion. The 3000 division needed more engineering hands to move MPE/iX forward, resources the company would not provide.

The protest was staged at a Bay Area Interex meeting, a setting similar to the ruckus 3000 users raised in Boston at an Interex show six years earlier. But IPROF was not the annual show attended by thousands. The Proposition 3000 name and the movement were so-named because it was the new era of California's state propositions. HP's Tony Engberg replied that he would work to get the 3000 advocates an audience with top HP officials. The hearing felt desperately needed after Ecometry's Alan Gardner laid out the future HP presented him.

Read "Wayback Wed: Customers' Proposition 3000" in full

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

February 27, 2017

HP quarter invites a peek at a smaller profile

Dorian GreyQuarterly results from the latest report on Hewlett-Packard Enterprise didn't impress investors. On the news of its revenues falling short of estimates—what's called a "miss" in today's markets—the stock got sold down 7 percent a share. Stock prices come and go, and HPE has made a better restart than the HPQ end of the split-up HP. The future, though, is certain to be getting slimmer for HPE. The question is whether something smaller can ever grow like the monolithic HP which carried 3000 customers across more than three decades.

It's easy to dismiss the fortunes of a split-off part of a vendor which doesn't make 3000s anymore. When the plans wrap up on a pair of  "spin-mergers" of two of the company's bigger business units, what's left over might have lost any further ability to change the enterprise computing game. Migrating 3000 customers will still have to take their computing someplace. Looking at the HPE prospects for 2017 is a part of that decision.

Analyst Bert Hochfeld has just written a 4,000-word report on the company on the Seeking Alpha website. That's a huge piece of business reporting that deserves a close read if you're buying stock or working for HPE. IT managers can find some insights as well. Cherry-picking some sections, to look at HPE's business futures, is useful for planning. HP's selling off its Enterprise Services and Software businesses to CSC and Micro Focus, respectively. The deals will wrap up by September. Hochfeld says what remains at HPE is unlikely to grow. A lack of growth is what drove down HP's stock last week.

"I do not think anyone imagines that what will remain of HPE in the wake of its divestitures is a growth business," Hochfeld said. "There are some growth components in otherwise stagnant spaces. The company has yet to demonstrate that it can execute at the speed necessary to exploit the opportunities it has—and to make the right choices in terms of allocating its resources in what are difficult markets."

In a report titled Has the company done a u-turn on a trip to nowhere? Hochfeld notes that what's left over at HPE this year might be viewed like the picture of Dorian Grey. But that would only be true, he adds, in a world where datacenters will only be run by cloud providers. Companies will run their own datacenters, a fact HP will need to stress to stay relevant when it displays a smaller profile.

Read "HP quarter invites a peek at a smaller profile" in full

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

February 24, 2017

Friday Fine-Tune: Opening Up MPE's Shell

Way back in the middle 1990s HP added the Posix shell to the HP 3000. The improvement meant customers who had Unix and MPE running in the same shop could train operators and managers with a single set of commands. Posix was a plus, making the 3000 appear more Unix-like (which seemed important at the time).

Over the years, however, Posix has been a feature waiting be discovered for most 3000 managers and operators. The computer's operating system was renamed from MPE/XL to MPE/iX just for this added Posix feature. But enough history; Posix is still on the 3000 and remains a powerful interface tool, an alternative to the CI interface that HP created for the system. You can even call Posix commands from the CI, a nifty piece of engineering when it can be done.

That's not always possible, though. A customer wanted to know how to "expand wildcard shells" using Posix. He tried from the CI and had this story to relate.

:LL /BACKUPS/HARTLYNE/S*
ls: File or directory is not found

So how do I do this? I need to be able to tell tar to archive all of the reels of a STD STORE set via a regexp. It does not work in tar, and it apparently does not in ls—so I speculate that there is something special about the innovation of Posix utilities from the CI that I am not aware of. What is it?

Jeff Vance, the 3000 CI guru at while at HP, replied "Wildcards on most (all) Unix systems, including Posix implementations, are done by the shell, not the individual programs or in-lined shell commands, like ls in your example. A solution is to run the shell and execute ll from within.

Read "Friday Fine-Tune: Opening Up MPE's Shell" in full

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

February 22, 2017

Simulator knows what day it is, or was

Feb22The SIMH project has created a software release that mimics the HP 3000 Classic CISC hardware. The software makes it possible to emulate HP 3000 servers that go back to the 1970s—the same systems HP mothballed in the middle 1980s even before the PA-RISC products of the past two decades.

So while SIMH won't give anyone an emulated HP 3000 that can run MPE/iX, the package somehow seems to know its way around the calendar. Even after MPE V has long since gone obsolete, the SIMH combo using MPE V from trailing-edge.com adjusts the year to match the current layout. As it turns out, the year 1989 has the same days of the week falling on the same calendar dates as 2017. It offers some hope of getting MPE/iX rewired so its CALENDAR intrinsic works beyond the end of 2027.

An emulator that virtualizes the ultimate generation HP 3000s is the domain of Stromays Charon HPA. SIMH is more of a hobbyist's dreamland, or as one serious veteran called it, "my version of toy trains."

Glen Cole fired up SIMH and reported that "the only user input below was 'hp3000 mpe-auto' ... Neat how it auto-magically knew that 1989 had the same calendar layout as 2017." He did a SHOWTIME to verify the date.

$ hp3000 mpe-auto

HP 3000 simulator V4.0-0 Beta        git commit id: f9cfae0c
Logging to file "mpe-auto.log"
Listening on port 1054
LP: creating new file

Cold load complete, P: 177664 (PSHR Q)
Press <CR> to start MPE.

HP32002E.01.00
WHICH OPTION <WARMSTART/COOLSTART>? COOLSTART
ANY CHANGES? NO

DATE (M/D/Y)?02/20/89
TIME (H:M)?22:35
MON, FEB 20, 1989, 10:35 PM? (Y/N)Y
LOG FILE NUMBER 5 ON
*WELCOME*
:HELLO OPERATOR.SYS;HIPRI

Read "Simulator knows what day it is, or was" in full

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

February 20, 2017

Harris School Solutions buys K-12 ISV QSS

HSS LogoHarris School Solutions (HSS) has announced its acquisition of Quintessential School Systems (QSS). The latter is an HP 3000 vendor whose products have been running California K-12 schools since 1990. The purchase for an undisclosed amount includes a transfer of QSS Chief Operating Officer Duane Percox to the post of Product Owner. The company's QSS/OASIS is capable of going beyond single school districts; it supports multi-district agencies, such as County Offices of Education, and also community colleges.

Scott Schollenberger, EVP of HSS' Financial Solutions unit said of QSS/OASIS, "We see this product as a way to bolster what we offer now, while opening even more doors for HSS in the future.”

Similarly, QSS expressed its excitement over joining with HSS. “Harris School Solutions is an outstanding organization," Percox said in a press release, "not just because of its products and services, but also because of the people who offer them. The people within the company are the real deal, so I’m thrilled to be working with them. Together, we’re going to offer our same great products and services, but to many, many more schools across North America.”

A company press release  says QSS OASIS will now be available more widely. QSS has always had a very large share of its customers in California school systems. Selling into a school system in California demands a familiarity of some very unique requirements. Harris brings the QSS software into the rest of the US.

The QSS saga includes a long-term migration campaign on behalf of its HP3000 users. When HP cut its 3000 plans short in 2001, finding a replacement platform with no such trap door was paramount to QSS. Well before the solution was established as a commercial choice, QSS was sent down a path toward Linux. The company calls this Version L, with the migrations coming away from Version H. This past year, the majority of QSS sites crossed over from the 3000 to Linux use.

QSS launched the Linux version of its application suite at Lodi Unified School District in 2008, accessing MS SQL. According to the QSS website, various other customers are scheduled to make the transition from the HP 3000 to Linux during 2017.

Read "Harris School Solutions buys K-12 ISV QSS" in full

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

February 17, 2017

K-12 vendor still migrates schools to Linux

Editor's Note: We learned today that Quintessential School Systems (QSS) has been acquired by another school software ISV, Harris School Solutions. QSS has been notable for leading customers from its MPE/iX application suite onto Linux—and QSS was one of the very first to do this in the 3000 world. Here's a replay of our report about the how and why of this migration campaign's roots. It's an effort that began in the earliest days of the Transition Era, according to this report from 2002. In the article below, just swap in Linux for any mention of HP-UX. There's not a measurable benefit to leading anyone to HP's Unix anymore.

QSS outlines pilot move of K-12 apps to Open Source

By John Burke

Rolling deskQuintessential School Systems (QSS), founded in 1990, is an HP 3000 ISV providing software and consulting services to K-12 school districts and community college systems. While developing, supporting and providing administrative and student records management computing solutions for these public school districts, QSS created a set of tools for HP 3000 developers. QSDK was a subroutine library toolkit to network applications. QWEBS was a Web server running on the HP 3000. When QSS talks about migrating HP 3000 applications to Open Source, we all need to pay attention to what they are doing and how they are going about it.

Public school systems are understandably very cost-conscious, so for competitive reasons QSS had already started investigating migrating its software to an Open Source solution before HP even announced on November 14, 2001 its intentions about the 3000. This put QSS ahead of most ISVs and non-ISVs in determining how to migrate traditional HP 3000 COBOL and IMAGE applications. At HP World 2002, QSS COO Duane Percox gave a talk titled “Migrating COBOL and IMAGE/SQL to Linux with Open Source.” Percox hoped to share QSS’s pilot project experience for migration approaches.

QSS customers tend to be very cost sensitive, and so an Open Source approach has a lot of appeal for any ISV providing a complete packaged solution. Non-ISVs looking to migrate homegrown applications to other platforms might want to stay with commercial operating systems, databases and compilers for the vendor support. But there are migration choices here that are useful for anyone moving MPE/iX applications.

Read "K-12 vendor still migrates schools to Linux" in full

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

February 15, 2017

Wayback Wed: An Emulator's Partners Enter

Javelin-004Four years ago this month, the software that will continue to propel MPE/iX into the next decade earned its first partner. The support for the Stromasys Charon emulator first showed up from Minisoft, the vendor who announced an iPad-ready version of Javelin when Apple's tablet empire was new. Charon got a version of Javelin while the Stromasys product was just making its way into production status.

The promise of an emulator slowed down migrations in 2012. Freeware was showing up during that year that was tuned to Charon's HPA model. Keven Miller created a free utility to transfer Store to Disk files to the virtualized 3000 in the HPA. Minisoft broke the commercial software company ice with a product license created especially for the emulator. For $49, managers could now buy a Javelin to work inside the freeware version's 1-2 user license.

It was a small and initial development to show a marketplace was emerging for the sustaining aspect of the 3000. Freeware Charon (the A-202) was replaced by professional installation and proof of concept within a year. That change elevated the success rate for deployments. Software licensing became the only serious issue to resolve for a Charon site. For nearly all vendors, even though they didn't rework software itself, the licensing became an easy transfer. Software from one 4GL vendor remains an exception, but that company has vexed 3000 sites throughout three different ownerships.

Read "Wayback Wed: An Emulator's Partners Enter" in full

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

February 13, 2017

ODBC treasure might be in your system

Treasure ChestSolving HP 3000 challenges can sometimes be as simple as tracking the tools in your hand. Tim O'Neill, a 3000 manager never shy about asking for help, checked in on the 3000 mailing list needing help for his databases.

We would like to export all the data in a format that could be imported by Microsoft Access.  Data relationships would be redefined after import.  It would be nice to export, with relationships defined, that would run on Windows.

Minisoft's Doug Greenup peered over O'Neill's shoulder, as it were, sitting at his console. 

Actually you own our ODBC driver which could be used for the requirement you outline. You were on support until 2009, so you have a version that handles this.The website  support.minisoft.com has extensive documentation on our ODBC tool. You could also renew your support and get the most current ODBC version, along with access to our technical team to assist you.

The HP 3000 community is full of databases that need access to the world of Windows. Sometimes those 3000 servers have lightly-used tools to make the connections. As is customary for a budget-sensitive group, O'Neill's collegues on the mailing list had ideas on how to do that export without buying anything.

Read "ODBC treasure might be in your system" in full

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

February 10, 2017

3000 support branches into multiple types

Tree-branchHardware support for HP 3000 sites comes in differing levels this year. At the top is the system administration and MPE support that production machines demand. It's crucial, but many 3000 sites try to self-maintain their MPE/iX. The next level down comes in application and utility support. One step below is support of the hardware hosting the system. Finally there's peripheral support for anything that's not inside HP's servers.

Comprehensive support is a collaborative effort in many cases. Physical hardware support is often a regional affair. For example, Essential.com is located in Pennsylvania. Its website says "We’re central to several major East Coast cities including Washington DC, Baltimore, Philadelphia, and New York City." That seems like a clue that the middle or western parts of the US aren't covered as completely. Whether that's true depends on what you need. Peripheral support for larger storage devices is available at more providers.

For example, Ray Legault at Boeing says his organization on the West Coast has used Essential. "They were okay," he said. "They mainly replaced DLT8000 and SCSI drives for our HVD10." There are no more HP hardware hosts for MPE/iX at Legault's branch of Boeing. The Stromasys Charon emulator drives the production computing at Boeing. It uses standard Intel hardware, boxes with ubiquitous options for support.

Legault employs a different support provider for its software and MPE administration. This is a common combo in the 2017 world of 3000 management. For example, the Pivital Solutions arrangement to care for 3000s combines long-term software experience -- they've been providing support since 1995 -- with hardware partners. A manager needs a provider who vets partners and keeps up with expertise.

"A reliable network is an everyday battle," said Pivital's Steve Suraci. "It used to be one primary and one secondary company to cover the entire continental US and they did it well. Not so much anymore. Almost every contract takes an effort to vet out a reliable resource and a backup." If a 3000 manager's plans don't include a backup to their hardware support providers, that can be a problem during a downtime crisis.

Read "3000 support branches into multiple types" in full

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

February 08, 2017

3000 hardware support resources requested

Computer-hardware-supportWe're developing a listing of companies and consultants who do HP 3000 hardware support here in 2017. Recently some customers have been searching for resources to help keep HP's 3000 hardware lively and healthy. It's sometimes surprising to learn where HP's 3000s remain active and productive. Archival systems are at one level, and production boxes at another. Everything that's a working machine needs an expert to call upon.

Self-maintainers are abundant in the market by now, but spots like the Ecometry web and catalog shops and manufacturers the world over still need HP's iron to boot up and run as expected. Even if you self-maintain you need a resource for parts. It won't impress your top management to learn your parts resource is eBay.

Obviously the hardware support arm of Pivital Solutions is our first recommendation for North American HP 3000s. Steve Suraci says that hardware service in 2017 demands a network of providers, coordinated and managed by a go-to, first-call company.

"We continue to support both MPE and the underlying HP 3000 hardware as one of the select few remaining support companies with access to HP's original MPE/iX source code," Suraci said. "We maintain 7x24x365 phone support for those requiring a total Service Level Agreement. In New England, we support our hardware agreements with our own local technicians.  Outside of New England, we support our customers through a network of contracted technicians that have agreed in writing with us to support our customers SLA.  In many cases, we will maintain parts on site to help facilitate quicker times to recovery."

That network of technicians covers regional areas. A physical visit is often essential to getting a hardware problem resolved. There are YouTube video services that might be used, or even a FaceTime call or Skype connection that might be a how-to experience. That's a rare solution in your market. The problem with offsite hardware support is liability. Once anybody other than a technician contracted — in writing — troubleshoots and replaces components, the liability lies with the person handling the physical hardware.

We want to build a thorough list of resources, even while the Stromasys Charon emulator continues to replace HP's iron for MPE/iX. Vendors, send an email to us if you've got current clients. Be sure to provide an email and web address, plus a phone number, so we can contact you to follow up. Customers, if you use a hardware support company, tell us who it is. We'd all be happy to hear how it's worked out for you, too. To be fair to everybody, we'll want to use your company name in any references. Share your wealth.

Posted by Ron Seybold at 11:10 PM in Homesteading, Web Resources | Permalink | Comments (0)

February 06, 2017

German A-Class sells for $162 per CPU

HP-3000-A400-and-A500Yesterday afternoon the seller of the A-Class twin-processor model A500 closed his auction of the server. After seven days the bidding rose from an opening bid of $1.07 to $323.59, not including shipping. Some lucky bidder who's been using eBay for stocking up on computers, terminals and servers now owns a system that sold for $37,000 new: A greater than 99 percent discount.

One way to sum this up is to watch nearly all of the hardware value of an A-Class—a device that represented the ultimate line of HP's MPE/iX hardware design—evaporate over 15 years. However, the computer sells in today's US market for at least $1,300. That preserves almost 4 percent of original pricing.

However, another way to calculate this turn of events relies on return on investment. These servers are clearly in their 15th year of service. Dividing that original price by its incredible term of service gives you a cost of about $200 a month for hardware which will run a business and doesn't require replacement. The enduring benefit of MPE/iX was its astounding value. This discouraged hardware replacements, a problem HP could not solve.

Half-empty or half-full? HP's 3000 iron keeps dropping in cost. The components are aging, of course. Finding a handful of systems to part-out for spares could keep such a 15-year-old server running. Intel hardware, of much newer vintage, provides an unlimited lifespan if you're using the PA-RISC emulator from Stromasys.

eBay can be a resource for HP's MPE/iX hardware, but my, a manager must be cautious. A hardware resource that's a company rather than an individual seller—or better yet, a coordinated hardware-software support enterprise partnership—is more prudent. At $162 per processor, eBay might be worth a gamble. But getting money for a server returned may not be as simple as for a disappointing collection of sports cards: one of the other purchases the new owner of the German A-Class made last week.

Posted by Ron Seybold at 02:36 PM in Homesteading, User Reports, Web Resources | Permalink | Comments (0)

February 03, 2017

Fine-tune Friday: Care and feeding of UDCs

Screen Shot 2017-02-06 at 1.53.00 PMMercury Insurance is a long-time HP 3000 shop still running a server in production. Last week Reggie Monroe reached out for a refresher on administration of HP 3000 User Defined Commands (UDCs). These are the HP3000's equivalent of scripting in Unix environments. UDCs are a better version of Command Files, according to Jon Diercks and his MPE/iX System Administration Handbook. UDCs are catalogued, Diercks says, so they can be loaded for individual user accounts.

UDC definition
Click for details

There's a superior PowerPoint slide deck online at the 3K Associates website that covers how to create and use UDCs. But the Diercks book (no longer in print, but available online) is more concise on the use of UDCs. It's also only available as an $80 book today on the used market; put yours in a safe place. Monroe's question asked about "a command to list all users, and the logon UDC associated with them, if one is set."

The initial answer was the command HELP SHOWCATALOG,ALL. This brings an administrator to

SHOWCATALOG [listfile][;USER=username[.accountname]]

But Alan Yeo pointed out that the MPE/iX command only locates system-level UDCs. 

You don't actually get what you think you asked for, so whilst :showcatalog ;user=@.@ sounds very hopeful, in fact it only shows the system level UDCs not account ones. As far as I'm aware the only place you can find them all is in the BULDJOB2 file in PUB.SYS. You do have a BULDJOB2 file don't you? And it's up to date?

And here's where Vesoft's utility does a job the 3000's OS cannot. VEAUDIT LISTUDC @.@ finds UDCs of all kinds.

Read "Fine-tune Friday: Care and feeding of UDCs " in full

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

February 01, 2017

Wayback Wednesday: The 3000's e-Moment

SnowWithBezelIn the waning days before the Year 2000, the HP 3000 was running behind popular labels. The position was nothing new to the server and its fans. Hardly anyone outside of the MPE community knew about the computer and its legacy across the final 25 years of the 20th Century. For many years it didn't matter that the computer ran in the shadows of IBM big iron, Unix dot-com servers, and Windows PCs. The 3000 performed without problems and delivered impressive returns on investments in the HP iron.

But as far as the world outside the community could tell, the HP 3000 had little to do with the Internet. Once Y2K's survival mission was in the industry's rear-view mirror, HP decided to do something about the shadows around MPE/iX. In the prior decade MPE became MPE/iX to show the world the 3000 knew a bit about Unix. In February of 2000 HP rebranded the computer as the HPe3000, dropping that lowercase vowel in the middle of a name that hadn't changed in 27 years.

E3000Label-0002A vowel is an easy thing to add to a product. The Internet, not so. Engineers across the community, eventually those inside HP, worked between 1996 and 1999 to bolt on elements like a Web server, DNS software, Unix mainstays like bind, and more. The server was already working on the Web in spots like the e-commerce shops of Hickory Farms and Brookstone retailers. Despite the larger profile of well-known customers like M&M Mars, using the 3000 on the Internet was a secret weapon.

A new name was proposed to change that. HP Product Planning Manager for 3000s Doug Snow brought the idea to division GM Harry Sterling in 1999. By early the next year the entire server lineup had been re-branded. The new server bezels, both those for the standard cabinets as well as racked 3000s, wore a new badge. The name change story extended to our offices as well. The publisher of the NewsWire became known by a new name. Dottie Lentz became Abby Lentz to the world after I spread the news about a name as nascent as the 3000's Internet abilities.

Read "Wayback Wednesday: The 3000's e-Moment" in full

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

January 30, 2017

German A-Class for sale at $1.07 + shipping

Snow with A-ClassManagers running MPE/iX in Europe can get a backup HP 3000 server today on auction at $1.07 plus shipping costs. Considering this is a two-CPU server which you can essentially tuck under your arm, (as HP product manager Dave Snow does at left, when the server was unveiled in 2001) the shipping costs might permit even North American 3000 managers to bid.

Dennis Grevenstein posted his notice of the sale last night on the HP3000 mailing list. The eBay auction starts at a minimum of 1 Euro, or about $1.07 at today's exchange rate. As of this evening there were no starting bids posted. The listing starts in German, but not too far down the page Grevenstein has English translations on the details.

Other than servers which have been given away for the cost of shipping, this is the lowest price we've ever seen for an HP 3000—especially for a model that's nearly portable and was built after 2001. Many 9x7-9x9 servers have been offered for outrageous discounts, especially considering their original pricing. This is an ultimate-generation HP 3000. Earlier this month, a single-processor A500 was being offered for $1,200 in North America.

The description notes that the German server is an rp2740 "with a slightly different firmware. It will also run HP-UX or Linux without problems. There is one hard disk with MPE/iX 7.5 on it and a spare disk." The note reminded one 3000 veteran about the performance drag HP that saddled the RISC processor with as a result of that firmware. The eBay listing is straightforward about how much the HP of 15 years ago hobbled the A-Class.

Read "German A-Class for sale at $1.07 + shipping" in full

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

January 27, 2017

Friday Fine-Tune: Memory and disk behavior

By Jeff Kubler
Kubler Consulting

Hard-disk-headAlong with the relationship between your CPU measurements and overall performance, memory and disk make up the other two components of your HP 3000 performance picture. Main memory is the scratch pad for all the work that the CPU performs. Every item of data that the CPU needs to perform calculations on or updating to must be brought into main memory.

The CPU must manage memory. It must cycle through the memory pages, marking some as Overlay Candidates (this means that new data from disk may be placed here), noting that some are in continued use, and swapping others out to virtual or what is called transient storage. Swapping to disk occurs when data is in continued use but a higher priority process needs room for its data.

To accommodate this higher priority process and its need for memory space, the Memory Manager will swap the memory for the lower priority process out to disk. The more activity the Memory Manager performs, the more CPU it takes to do this. Therefore it is the percentage of CPU used to manage memory that we use as a measurement.

Read "Friday Fine-Tune: Memory and disk behavior" in full

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

January 25, 2017

Migrate, emulate: Wednesday show's for you

Screen Shot 2017-01-26 at 11.40.52 AMThursday, at 2 PM EST (11 PST, 8 PM CET) there's an MB Foster webinar show covering emulation options. For the 3000 owner and manager who hasn't yet moved off HP's 3000 iron, no what matter where you're headed, there's something in this 60 minutes for you.

Last summer's version of the webinar walked its viewers through Foster's eZ-MPE, Ordat's TI2/SQL, Marxmeier's Eloquence database suite, and the Stromasys 3000 hardware emulator Charon. Only the last product delivers no changes to software and frees you from HP's aging boxes. But the other three offer ways to mimic parts of the 3000's heart and soul.

eZ-MPE is the newest of the emulate-to-migrate products. Introduced in 2013, it's a suite of software to accommodate the data infrastructure and scripting needs of today's HP 3000 sites. The Thursday show includes a demonstration of the MB Foster product.

TI2/SQL gives TurboIMAGE users (pretty much everybody who's still running a 3000) an avenue into SQL databases like SQLServer. And Eloquence replaces the IMAGE database wholesale, using an SQL-based data platform with deep work-alikes for IMAGE intrinsics and features.

It should be an interesting show. The distinctions between the first three products and Charon will be obvious by the end of the presentation, so stick around to the finale. That wrap-up is also the portion of the webinar for free-form questions. It's getting rare to have a place to ask those in a semi-public setting. I hope to hear from you during the webinar. MB Foster's got a means to listen and watch these shows after their airing. But the Q&A part is live-only.

Read "Migrate, emulate: Wednesday show's for you" in full

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

January 23, 2017

SD cards take a hand in 3000 storage

One of the most unpredictable hardware devices in HP's 3000 iron is its SCSI drives. Out in the user community one enterprising manager is trying to link the server to microSD cards. John Zoltak checked in with other users last week about the project.

SCSI2SDZoltak was simply trying to copy one 917LX disk to a new disk on the server's SCSI bus. A 4GB drive is standard on a 917, so just about any microSD card would match that storage. A bit of open source wizardry props up SCSI2SD, a combination of hardware and software. You can purchase an SCSI2SD card on eBay and in other Web outposts.

Zoltak didn't begin there, however. He was searching for an offline diagnostic tool to do the disk copying. "I want to copy the system volume sets, so using VOLUTIL is not an option. And at this point just how does anyone get the diagnostics passwords? My other choice is to attach the 3000 disks to a PC and copy there."

That other choice leads the way to SCSI2SD. Using PC-based disks, of course, is one of the serious advantages to using a Stromasys Charon emulator for 3000 work. The 9x7s are so old they don't have a Charon equivalent, but the strategy is the same. 

As for ODE, once you locate a diagnostics password (an exercise left to the 3000 customers who have a support provider) you must be prepared to wait on DISCCOPY. "There is a DISCCOPY in the ODE," Craig Lalley reports. "Hook up both drives and you should be able to copy the drive if it is copyable. I must warn you, it is slow, like all night all day sort of slow. But it is free."

Read "SD cards take a hand in 3000 storage" in full

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

January 20, 2017

RAIDing Your Storage to Homestead

By Gilles Schipper
Homesteading Editor

Model12HOne straightforward way to improve the value of an HP 3000 is replacement. That is, finding a better disk storage hardware component—replacing what shipped with your 3000 with a corresponding disk subsystem, one that offers the superb protection of hardware RAID (Redundant Array of Inexpensive Disks).

I would also recommend this replacement for those who utilize HP 3000 Mirror/iX software—since Mirror/iX does not protect the MPEXL_SYSTEM_VOLUME_SET volume set . It also forces one to utilize user volume sets even if the situation does not otherwise warrant it. I believe there is a place for user volume sets, but only in very specific and limited circumstances.

The main advantage of hardware RAID is that it offers excellent protection from disk failures and resulting data loss and time lost due to data recovery requirements. Chances are good that you are if you are a candidate to benefit from hardware RAID, your existing disk technology is relatively old and prone to failure as a result of years of use.

Let's face it, unlike a good wine, older HP 3000 hardware and its associated peripherals do not get better with age. Quite the contrary.

However, even if you choose a RAID technology that is also relatively old or obsolete, the nature of the technology itself affords you a great measure of protection from disk failures and corresponding data loss and downtime.

The inexpensive choices include the Nike Mod10 or Mod20 and the HP Autoraid 12H. A higher-end RAID solution is in HP’s VA7000 family of products.

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

January 18, 2017

Recruiter opens book on college opportunity

MRG SearchYou don't see many requests for HP 3000 expertise by now, at least not in a public setting. But a boutique placement agency posted a request for COBOL experience on the 3000 mailing list this week. The notice doesn't deliver many details, but it stands out in a job market where opportunities have been few.

Under the covers, where consultants and developers serve 3000 shops both on the move as well as homesteading, gigs lurk. One veteran knows another and they'll contract for a period together. Most of these engagements involve finding someone familiar with a piece of 3000 software.

MRG Search and Placement has a website but there's no public listing of available positions. It's just as classic old-school as a lot of the talent that could fill those jobs. The message in public was simply "HP3000 skills needed in an University setting," and went on to mention COBOL was involved. The language usually is, considering the vast percentage of in-house apps written in the language.

Jon Culotta runs MRG, which is upfront about keeping 3000 customers and talent connected.  "Established in 1976, MRG started its niche recruiting in the HP 3000 arena. That core market is still served today." The company's heartland is Amisys healthcare software talent, but a university might only be involved if it was a health organization operated by a school.

The job is on-site and contract. Culotta's email is jculotta@mrgsearch.com.

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

January 16, 2017

Older hardware, current support, new prices

TapeMaster LTOHP's 3000 hardware is still being offered for sale. Hewlett-Packard Enterprise wants none of this 2017 action. Independent hardware brokers sell HP 3000s today, and by the looks of the pricing the transactions might be simply for parts. How could anyone operate a company while they rely on a $975 server?

The price is one data point on a wide spectrum of a sweeping array of servers, all offered on the 3000 mailing list this week. At the tip-top of the spectrum was a $3,175 system, first introduced early in the 1990s. At the very bottom was the faithful Series 918LX, priced at $675 including a DDS-3 tape drive. The newest computers came in at that $975 price.

The range of power ran from the 918 to the Series 989KS/650. It was a $290,000 system sold new in the late 1990s. The one on offer this week from the broker carried a price tag that was discounted $288,625.

Antiques? Some, perhaps, but not all. Series 918 and 928 servers from HP—both on the list—are running production systems today. Roy Brown, a consultant and developer in the UK and a member of the 3000 list, is running two Series 918s. One much newer server is holding archives at a migrated shop in Texas. While using the old, or very old HP iron one smart customer keeps support current for such boxes. Even when they're not on the critical path for computing.

Read "Older hardware, current support, new prices" in full

Posted by Ron Seybold at 07:27 PM in Homesteading, User Reports | Permalink | Comments (0)

January 13, 2017

Emulation review will air out all options

January 26On January 26 MB Foster is airing the 2017 edition of its emulation webinar. The 40-minute show will walk 3000 managers through four emulation options. Last year's show had four very different products. Three will address the MPE/iX environment: how to get your applications onto the Windows OS. One will give you emulated hardware. In the first edition of the webinar, Birket Foster called the Charon emulator for 3000 hardware emulation "flawless."

The other three solutions — unless the lineup changes from last year's show — are all based in software methods to replicate databases and surrounding code. They are

The MB Foster environment emulation solution has been working for at least one customer. We introduced it in 2013. Here's our story from that year for reference. We'll all look forward to the update at 11 AM PST.

eZ-MPE opens new Windows for 3000 sites

MB Foster is announcing a hybrid of solutions aimed at making migrations off the 3000 easier. The company is calling its offering MBF eZ-MPE, and it’s aiming customers at the native benefits of working in Windows once they make their transition. MBF eZ-MPE is a solution for HP 3000 sites that have a keen interest in transitioning to a Windows environment, while they preserve their company’s competitive advantage and legacy applications.

Read "Emulation review will air out all options" in full

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

January 11, 2017

Finding the knowledge HP once shared free

HP3000-resourcesIn 2008 was the debate, and I don't mean between our now-outgoing President and his rival. The debate was in your community about future knowledge. Where could you expect to find HP 3000 and MPE/iX manuals in the coming years? It didn't turn out to be where it was planned and proposed, but a manager of a homestead 3000 does have options today.

For many years, MMM Support hosted the full range of HP's manuals for hardware and software. As of this morning the website is offline, but it's probably a configuration error and not a sign of a company's demise. You'll find plenty of links on our blog to the hpmmmsupport.com site. The manuals are in PDF format and you don't experience any pop-up or page-takeover ads like you see in YouTube.

The newer player in the hosted HP manual arena is TeamNA Consulting. While it's a newer site, the venture is led by one of the older (in history) resources. Neil Armstrong, one of the tech wizards at Robelle, is the NA in TeamNA. Armstrong started with the HP 3000 more than 34 years ago—an era where MPE IV was still a common OS for the servers. Plenty of experience there, and plenty of manuals available too. More manuals than HP will share with the world today. The extra information is hardware documentation.

This wasn't the future the 3000 community expected in the days when official 3000 support from HP was nearly gone. Today that support is well-filled by companies like Pivital, a bedrock upon which homesteading and 3000 emulation rests.

Read "Finding the knowledge HP once shared free" in full

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

January 09, 2017

3000 experience floats up to the Fed

FedRichmondReid Baxter started his work in the HP 3000 world in 1981. This year he's helping to support the IT at the US Federal Reserve in Richmond, VA. There is no direct line between these two postings. Baxter has made the most of his career that started with MPE and terminals to lead to his current post where he helps maintain computers that serve the US banking bedrock, The Fed.

Baxter, one of the earliest 3000 Newswire subscribers, checked in this week to congratulate us on another anniversary as we crossed into the 22d calendar year of publishing. It's been quite a while, as Baxter says, since an HP 3000 was in his life: seven years ago he transitioned off everyday 3000 duty when his employer JP Morgan-Chase closed down its MPE/iX servers.

Baxter went into support of the 3000's successor at Chase, HP-UX, and then onward into Linux. When your skillset goes as far back as HP's Data Terminal Division, a new environment presents more opportunity than challenge. The 3000 once had a place in banking IT, which is why Chase once deployed the ABLE software suite from CASE for asset management.

After Chase did a downsize in 2015, Baxter went on a lengthy quest to land a new spot in finance computing. He's working today for HP Enterprise Services, by way of the Insight Global staffing enterprise. His mission is support of that Fed IT center, work that he can do remotely. One reason for that telecommute is that banking has often needed remote computing. Banking software on the 3000 once drove the adoption of Internet services on the business server, after all.

Read "3000 experience floats up to the Fed" in full

Posted by Ron Seybold at 09:59 AM in History, Migration, News Outta HP | Permalink | Comments (0)

January 06, 2017

Friday Fine-Tune: Logging, IP logins, SNMP

Due to a disk crash, I had to reload my HP 3000 system recently. I’ve just discovered that system logging has been suspended. How do I resume system logging?

Paul Christidis replies:

The reason for the suspension of logging was most likely due to a duplicate log file name. When the SLT was created the then-current log number was recorded, and when you restarted the system from your most recent SLT it tried to open the sequentially next log file. Said file already existed.

  • MOVE the existing log files to a hold area
  • Determine what logfile the system resumed on
  • Perform a series of SWITCHLOG commands until the logfile number advances to one more than the highest number in the hold area
  • Then move the held logfiles back to the pub.sys group — replacing the ones created by the series of ‘switchlog’ commands.

Is there a way to see the IP address associated with a particular login?

Any user with SM can do the following, for example:

:SHOWVAR HPSTDIN_NETWORK_ADDR;JOB=#S495
HPSTDIN_NETWORK_ADDR = 172.16.0.30

The command :listf ci.pub.sys,8 will list all sessions and will show their associated IP address.

I’ve got an older model HP 3000 and I'd like to start monitoring it with SNMP for things like CPU utilized, jobs running or whatever other cool stat I can SNMP-grab. The problem I have is I can’t find the MIBs for it anywhere.

Andreas Schmidt replies:

First of all, I do not recommend the use of SNMP on the 3000, for performance but also security reasons. SNMP is not the securest protocol, as you know. Nevertheless, here are some hints:

• In the group NET.SYS you will find the SNMPUDC. This should be set in any case for MANAGER.SYS or on system level.
• Having set this, a SNMPCONTROL STATUS will show you the status of the SNMP subsystem.
• SNMPCONTROL START / STOP are self-explaining.
• The MIBs specific for MPE can be found in the document HP SNMP/XL User’s Guide

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

Search