April 17, 2019

Wayback: HP sues insurer for MPE defeats

Logo
Fifteen years ago this month, HP was working to prove MPE was a rich asset. The vendor had already shucked off its futures for selling the 3000, saying in 2001 the server would be kaput by 2006. The 2004 lawsuit was a last resort to get money for servers that HP did not sell.

Confused? The marketplace was in the know about HP's attempt to recover $31 million from an insurance policy it took out against losing sales to system counterfeiters. In 1999 HP began its campaign to arrest, or sue out of business, a stable of companies selling 3000s outside of HP's control. The '99 lawsuits were aimed at Hardware House and several other 3000 resellers. Those companies were charged with selling 3000s whose MPE licenses had been faked.

After more than two years of those legal attacks — HP concocted a High Tech Task Force out of a few California law enforcement agencies, raiding suspect companies — the 3000 division walked away from its 3000 sales beyond 2003. As far as HP was concerned, it was still entitled to money it lost from faked sales in the years leading up to 1999. It didn't matter to the vendor that it was ending its 3000 business and putting 3000 software vendors on the ropes. It wanted to be paid for those unlicensed servers sold by third parties. MPE was the prize HP was claiming, since the hardware itself was officially useless without an MPE license. 

Los Angeles legal firm Anderson, McPharlin & Conners went to the 3000 newsgroups in 2004 to beat the community’s bushes, working to discover prices for used HP 3000s sold between 1994 and 1998. Paralegal Laurie Moss said HP wanted to levy a claim for the full software price on every server sold to Hardware House.

During the legal firm’s discovery search, Moss said many 3000 community members who were contacted wanted to help. The Brunswick, Ohio-based reseller Norco, which eventually closed its doors three years later, was eager to tell the truth about the 900 Series systems genuine value.

“You wouldn’t believe how many people said, ‘I sure do wish I could help you in this,’ “ Moss said. The law firm’s attorney Lisa Coplin deposed John Adamson, former owner of Hardware House, in the case, as well as Deborah Balon, an HP resales employee who aided Hardware House. HP settled within a week of the legal firm's discovery depositions. The vendor settled for five percent of its original $10 million claim.

“We were afraid that some of the hardware brokers wouldn’t want to come up against HP,” Coplin said. “One of them, Norco, said, ‘We’ll give you everything we have.’ "

Read "Wayback: HP sues insurer for MPE defeats" in full

Posted by Ron Seybold at 05:44 AM in History | Permalink | Comments (0)

Pivital Solutions: Your complete
HP 3000 resource

April 15, 2019

Taking a Stab at the Size of Your World

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

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

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

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

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

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

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

Read "Taking a Stab at the Size of Your World" in full

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

April 12, 2019

Fine-Tune: Creating Store to Disc from tape

NewsWire Classic

I still have some 3000 information on a tape. I’d like to create a Store to Disc file with it — how do I do that?

Jack Connor replies:

There are several solutions. The first and easiest is to simply restore the info to a system (RESTORE *T;/;SHOW;CREATE;ACCOUNT=WORKSTOR) where WORKSTOR is an account you create to pull the data in.

Then a simple FILE D=REGSFILE;DEV=DISC and STORE /WORKSTOR/;*D; with whatever else should create the disc store.

The second method is to use FCOPY. You'll have to research the STORE format, but I believe it's FILE TAPEIN;DEV=TAPE;REC=8192,,U,BINARY.

The third (also easy, but you need the software) is to use Allegro's tool TAPECOPY, which moves from tape store to disc store and back.

John Pitman adds:

Do you mean copy it off tape to a disk store file? I’m not sure if that can be done, as in my experience of tapes, there is a file mark between files, and EOT is signified by multiple file marks in a row... but anything may be possible. If you do a file equate and FCOPY as shown below, you should be able to look at the raw data, and it should show separate files, after a file list at the front.

FILE TX;DEV=TAPE;REC=32767
FCOPY
FROM=*TX;TO=;CHAR;FILES=ALL

Here is our current store command, and the message it provokes. MAXTAPEBUF speeds it up somewhat

STORE  !INSTOREX.NEW.STOCK2K;*DDS777;
FILES=100000;DIRECTORY;MAXTAPEBUF

Posted by Ron Seybold at 04:52 PM in Hidden Value, Newswire Classics | Permalink | Comments (0)

April 10, 2019

Wayback Wed: Sizable drives for 3000s

Supersize
Ten years ago this month, we celebrated the fact that Hewlett-Packard created a forward-looking feature for the HP 3000 before its lab retired. One of the biggest enhancements gave MPE/iX the ability to use drives sized up to 512GB. Getting this size of drive to work involves going outside of the 3000's foundation, both literally as well as strategically.

External disc drives supply any storage beyond the 73GB devices which were fitted inside the HP 3000 chassis. This Hewlett-Packard part, numbered A6727A, was an off-the-cuff answer from Client Systems to the "how big" question. Client Systems built HP 3000s with this part installed while the company was North America's only 3000 distributor. But nothing bigger ever came off a factory line before HP stopped building 3000s in 2003.

Outside of HP's official channel, however, a drive twice as large has been installed on a N-Class with a pair of 146GB drives inside. The Seagate ST3146855LC spins at 15,000 RPM, too, a faster rate than anything HP ever put in a 3000. These Seagates are still available; just $95 today at Amazon.

Older 3000s, however, need single-ended drives for internal use. Allegro's Donna Hofmeister says the 3000's drive size limit is controlled by two factors: internal versus external, and HP "blessed," or off-the-shelf specified.

Read "Wayback Wed: Sizable drives for 3000s" in full

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

April 08, 2019

Where to go for better 3000 census numbers

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

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

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

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

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

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

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

April 03, 2019

Wayback: Oracle embraces Sun and Solaris

Hurd-Ellison
Current Oracle CEO Mark Hurd (left) at a conference with Oracle founder Larry Ellison (far right) in 2010

Ten years ago this month, Oracle announced it was purchasing Sun Microsystems. The move led by CEO Larry Ellison ended the independence of the one company that nudged the world, including HP 3000 customers, into the realm of dot-com and fully networked servers.

HP lost the march on Internet growth to Sun, and those setbacks led to the departure of HP CEO Lew Platt, the final leader of the full Hewlett-Packard who'd grown his career from HP upward. In the late 1990s, the 3000 division moved heaven and earth to integrate the Internet services for MPE/iX that HP-UX had. But not even the HP-UX technical leg up could outrun the Sun rocket launched by its CEO Scott McNealy in 1982.

The 2009 deal dialed down the competition to HP's Unix solution. IBM was near a deal to buy Sun in March of that year, but talks fell through. Oracle said its $7.4 billion acquisition brought it the most important piece of software Oracle ever purchased: Java. But the world's biggest database supplier said the Solaris operating system, key to Sun's server solution, was an important prize, too.

There are substantial long-term strategic customer advantages to Oracle owning two key Sun software assets: Java and Solaris. Java is one of the computer industry’s best-known brands and most widely deployed technologies, and it is the most important software Oracle has ever acquired.

Oracle's statement went on to place the Solaris-Oracle combination of OS and database as the best possible for a company choosing Oracle. The future seemed to hold special features for Unix customers who chose Sun's hardware.

The Sun Solaris operating system is the leading platform for the Oracle database, Oracle’s largest business, and has been for a long time. With the acquisition of Sun, Oracle can optimize the Oracle database for some of the unique, high-end features of Solaris.

Solaris is an asset that one 3000 ally counts upon today. Oracle has given Stromasys the ability to transfer Solaris licenses as a part of installations of Charon for SPARC. HP still requires a separate transaction if a customer will be preserving the official status of an MPE license while moving to Charon for the 3000.

Read "Wayback: Oracle embraces Sun and Solaris" in full

Posted by Ron Seybold at 06:53 PM in History | Permalink | Comments (0)

April 01, 2019

Bounty brings out bonus for 900 Series

Screen Shot 2019-04-01 at 9.42.40 PM
A new electric vehicle manufacturer is seeking early-model HP 3000 servers, hoping to locate systems that were built with a now-rare alloy crucial to the latest EV propulsion needs.

Voltene, which is building the first line of solar-powered food trucks, wants the HP 3000s manufactured prior to the year 2000. The systems were built with a set of gold-plated network interface cards and cages. When in service, this old hardware was a serious drain on power resources for customers who used servers like Series 900 systems.

But the very design of physics that needed all of that electricity makes those components a superior source of storage for the wattage the food trucks need to maintain cooking capabilities. Will Ubeserius, the CEO at Voltene, says the older the server, the more it's worth to the California-based competitor to Tesla.

"They don't make them like that anymore," Ubeserius said. "We'd like to get in front of our competition to get that classic iron's materials into our production lines. We're pretty sure that the value in those 900s is going to be a good match with our HotPlayte line."

A novel combination of solar arrays and grills converted from white gas kerosene, the HotPlayte trucks have been through hardware tests in Roseville, Calif. The testing field, a roundup corral with a dozen trucks, was built less than a mile from the last working HP 3000 manufacturing line in Roseville.

"We found a warehouse in the area with thousands of these servers, tucked away by what we're told was the HP FRD division when it took 3000s in for remarketing ploys," the CEO said. "It's a gold mine for what we need. But it's still a fraction of what we'd like to have."

The company is also researching the potential for the 7944 disk drives to contribute to the Voltene line. "Those drives moved on their own without wheels," said Stan Derddisc, chief engineer at the Roseville test site. "There's something in them that stores energy and releases it as kinetic propulsion. Those HP engineers were decades ahead of their time in making bytes move."

Companies with Series 900 servers are invited to send the systems FOB to the Voltene Energy Renewal Center at 8000 Foothills Blvd, Roseville, CA 95747. Freight On Board shipping ensures the systems will become property of Voltene once they leave the docks of the 3000 owners' companies. 

Posted by Ron Seybold at 09:54 PM in Newsmakers | Permalink | Comments (0)

March 25, 2019

Making Directories Do Up To Date Duty

Last week we covered the details of making a good meal out of LDAP on an MPE system. Along the way we referred to an OpenLDAP port that made that directory service software useful to 3000 sites. The port was developed by Lars Appel, the engineer based in Germany whose work lifted many a 3000 system to new levels.

Appel is still working in 3000s, from time to time. We checked in with him to learn about the good health of LDAP under MPE/iX.

Is this port still out in the world for 3000 fans and developers to use?

Well, I don't recall if anyone ever used it (and I must admit that I don't recall of the top of my head, what drove me to build it for MPE/iX at that time... maybe just curiosity). However, the old 1.1 and 2.0.7 versions at still available at the website maintained by Michael Gueterman, who is still hosting my old pages there.

The versions are — of course — outdated compared to the current 2.4.x versions at openldap.org. But anyone with too much spare time on their hands could probably update the port.

But it's still useful?

Funny coincidence, though. Just yesterday, I had to use a few ldapsearch, ldapadd, and ldapmodify commands against our Linux mail server. If I had seen your mail two days ago, I could probably have looked up examples in my own help web pages, instead of digging up syntax in some old notes and man pages.

And you're still working in MPE?

I am still involved with Marxmeier and Eloquence, so it is more with former HP 3000 users that with current ones.

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

March 22, 2019

Making LDAP Do Directory Duty

DAP
Explore a 3000 feature to see how a little LDAP’ll do ya

NewsWire Classic

By Curtis Larsen

When you think of LDAP, what do you think of? You’ve probably heard about it — something to do with directories, right? — but you’re not quite sure. You’ve heard some industry buzz about it here and there, read a paper or two, but perhaps you still don’t quite know what it can do for you, or how it could work with an HP 3000. Hopefully this article will de-mystify it a bit for you, and spark some ways you could use it in your own organization.

MPE currently has limited support for LDAP, but the support is growing. Aside from the OpenLDAP source ported by Lars Appel, HP offers an LDAP “C” Software Development Kit for writing MPE/iX code to access directories, er, directly.

LDAP stands for “Lightweight Directory Access Protocol.” In a nutshell, it allows you to create directories of information similar to what you would see in a telephone book. Any information you want to store for later quick retrieval: names, telephone numbers, conference room capacities, addresses, directions — even picture or sound files. Using directories such as these is an incredible time-saver (can’t you think of company applications for one already?), but LDAP can do so much more. The directories you create are wholly up to you, so the sky’s the limit.

At this point you might be saying “Great, but why not use a database for this stuff?” That’s an excellent question, and in truth, there is some overlap in what you might want stored in a database versus being stored in a directory. The first and foremost difference between them is that a directory is designed for high-speed reading (and searching) — not writing.

The idea is that, generally speaking, a directory doesn’t change much, but quickly reading its information is a must. Understand that this doesn’t mean that directory writes are at all bad — they’re just not structurally designed to be as fast as reads are.

Databases also require more in the way of overhead: high-powered servers and disks, (usually) high-priced Database Management Systems — which one will be best for you? — and highly-skilled, highly-paid DBAs to keep it all happy. (Our DBA said I had to mention that part.)

LDAP directories are generally simpler and faster to set up and manage. LDAP is (also) a common client-server access standard across many different systems. You don’t have to deal with the outrageous slings of one DBMS, or the delightful syntax variations in SQL or ODBC implementations. LDAP directories can even be replicated. Copies of directories, or just sections of larger directories, can be stored on different servers and updated (or cross-updated) periodically. This can be done for security (“mirrored directories” — one here, one elsewhere), performance (all queries against local entries on a local server), or both.

Read "Making LDAP Do Directory Duty" in full

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

March 20, 2019

Celebrating a Software Salvation

Winston Kriger
The 3000 community in Austin laid an icon to rest last weekend, and Winston Kriger was well-remembered. The chapel at Cook-Walden on Lamar Boulevard, deep in the center of a busy city, was full of friends from as far back as his childhood, his family including his wife Ruth of 52 years, and more than a few colleagues from a 3000 company once called Tymlabs.

Beyond the 35 minutes of tender memories from Winston's best boyhood friend — they flew wire-controlled model airplanes together, experimented with making nitro, and worked as teenagers at the TV and radio stations of Baton Rouge — someone spoke about salvation. Morgan Jones wasn't talking about the grace that Winston had earned after a full life full of curiousity. Jones talked about the time that Winston saved Tymlabs.

It was a splashy company in the 1980s of Austin. I came to know it as a lynchpin of a software vendor down on Seventh Street, full of incredibly bright people and building stout and innovative products. Tymlabs was the first and only place I ever saw an Apple Lisa, the Mac's predecessor. Tymlabs employed Marion Winik, who was wearing purple hair when I first saw her, developing marketing copy before she became a celebrated memoirist with eight books. Tymlabs employed Denise Girard, a woman of endless cheer who had a Patsy Cline impression she sang at user group meetings. The punch line on Denise's performance once included pulling a golf putter out of her dress at the end of a song.

Gifted, unique people worked there. Winston Kriger kept those doors open, said Jones, by saving the future for the software that butressed the company. Backpack was invented by Jeorg Groessler at Tymlabs, and the backup software saved untold companies' data. Then Groessler left Tymlabs and there was no one to keep Backpack in good health. When things got dire at Tymlabs in 1985, only "one really smart guy at Houston Instruments" could save the company. "He was supremely confident he could find and fix the problems" with Backpack, Jones said. 

Jones and Tymlabs needed Winston. It took some coaxing to get someone that brilliant to come to a software company with less than five years of existence on the books. Tymlabs started out like a lot of MPE software companies, built around the work to create custom software, then developing products for sale in the 3000 market. The products made the company a keystone advertiser for the HP Chronicle where I was editor in the 1980s. They built a 3000 emulator that ran on the Macintosh just a few years after Apple launched the Mac. 

Jones said he began to hire Winston's colleagues to work at Tymlabs, hoping it would convince him the vendor was real. Winston was 45 when he joined the company, a man already ensconced in a successful career for Houston Instruments. "He basically saved our company," Jones said at the ceremony last weekend. "He was a force of nature, and I don't mean like a tsunami or fusion. He was like gravity. When we'd be running around frantic, he kept us all grounded."

People in the room at Cook-Walden were nodding. This was the Winston they all knew, steady and with a dry wit. Jones said that Winston was "an intellectual giant and a gentleman who was always at his best — and who had a slight, wry smile at parties." Jones' co-founder Teresa Norman sent regards that said she gave thanks "for having the confidence to join us. We've always respected the courage that took."

In these waning years of the Teens, it can be hard to imagine a time when MPE and the 3000 were a calculated business risk. Backup software made the servers a bona fide choice for what the industry called data processing in the 80s. When it came to saving an innovative company making bedrock software, a fellow who was "genetically inclined to always tell the truth and do the right thing" was the right person for the job.

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

March 18, 2019

Curating a Collective of MPE Advice

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

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

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

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

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

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

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

March 15, 2019

Samba, and making it dance on MPE/iX

Screen Shot 2019-03-24 at 5.11.14 PM
HP 3000 sites have the Samba file sharing system, a universal utility you find on nearly every computer.

Samba arrived because of two community coding kings: Lars Appel, who ported the Samba open source package to the 3000, and Mark Klein, who ported the bootstrap toolbox to make such ports possible. As John Burke said in the sunnier year of 1999:

Without Mark Klein’s initial porting of and continued attention to the Gnu C++ compiler and utilities on the HP 3000, there would be no Apache/iX, syslog/iX, sendmail/iX, bind/iX, etc. from Mark Bixby, and no Samba/iX from Lars Appel. And the HP 3000 would still be trying to hang on for dear life, rather than being a player in the new e-commerce arena.

So Samba is there on your HP 3000, so long as you've got an MPE version minted during the current century. Getting started with it might perplex a few managers, like one who asked how to get Samba up on its feet on his 3000. One superb addition is SWAT, the Samba administration tool. Yup, the 3000's got that, too.

Read "Samba, and making it dance on MPE/iX" in full

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

March 13, 2019

Finding the Drumbeat to Differ, Decades Ago

Drummer
LinkedIn likes to remind you about work anniversaries of the people in your network of contacts. Sometimes the reminders can be unfortunate, celebrating entry dates for jobs people no longer hold. That's not the case for my own anniversary this month. Twenty-four years ago in March, the first seeds of the NewsWire were being planted in the heart and soul of my family.

HP has been at hand for most of my fatherhood. I grew up as a dad editing the HP Chronicle for PCI, an Austin company specializing in trade monthlies. One tradition at PCI was a video produced by the staff of editors and ad reps. The movie always appeared at the Christmas party. One year my son Nicky, who was all of four years old, sat in my London Fog trenchcoat and wore my reporter's hat in a bit where my chair spun around and there he was, in place of me. I'm short enough that the joke was on me.

Years later I'd gone out on my own to freelance, still keeping a hand in writing HP news for one publisher or another. Nobody was covering the HP 3000 much, though. The action was all with Unix, either HP's or the systems from Sun, or in the swelling majority of Windows. Digital and IBM had big swaths they were carving, too.

My wife and I had plenty of publication experience from our days in Texas publishing companies. I looked at the growing lines of posts on the 3000-L mailing list, right alongside the precarious nature of marketing and freelance writing. Dreams of a publication about the 3000 were soon on our lips at my house. Nicky was 12, and the NewsWire was on its way to delivery.

We had our realism bridles on for awhile. There was a reason the 3000 news appeared infrequently in the likes of Computerworld. The pages of Open Systems Today where I was freelancing made a little room for MPE, but nobody really wanted to acknowledge future growth for HP's original business server. Not anymore, not with the drumbeat of Unix so loud and HP's ardor for the 3000 so withered.

Then Abby said what many others who wanted to fly in the face of business trends say: "Hey, people made money in the Depression." I had maiden aunts who did just that, mostly on the strength of shrewd stock trades and a little high society retail commerce. I only worried how we'd find out enough to fill a newsletter month after month. Even if we filled it, more than a few key advisors thought the NewsWire would be worth less than a dollar a month. This month a few kind LinkedIn followers called me a legend, or maybe they meant the NewsWire, when that 24th anniversary notice popped up. I know there would be no legend without Abby.

We flew in the face of a trend. We saw plenty of companies doing just that in stories nobody was telling. Change must overcome inertia. Those of you who own 3000s know about staying stalwart about unneeded changes. We could only celebrate this anniversary because of you—plus the companies that made your 3000s reliable. Those advisors of ours were wrong about the one dollar a month. But Abby and I were wrong about what would drive the NewsWire. Sponsors came through when the top end of the subscription pricing was just $99 a year.

Read "Finding the Drumbeat to Differ, Decades Ago" in full

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

March 11, 2019

Hardware magician Winston Kriger dies at 77

Winston-Krieger
Kriger, shown here next to his amateur radio set in Austin, used this call sign since he was 13 years old.

Veteran MPE wizard Winston Kriger, whose work powered 3000 software products from Tymlabs, OPin Systems, and ROC Software, and connected hardware the world over, died this week at his home in Austin, Texas. Kriger made his mark on the MPE community with an advanced understanding of component, bit, and file-level activities that are essential to the 3000's dominance. Anything to do with tapes, software and hardware was his heartland of know-how, one colleague said.

His passing—after several months of a rare, untreatable, and debilitating brain disease impairing muscle control, balance and speech, and finally basic life sustaining functions—was being mourned by colleagues and friends in the 3000's highest technical community.

"Interfacing hardware was his special magic," said Terry Floyd, founder of the Support Group and a 3000 expert from the 1970s onward. With a dry, rapier wit and a massive storehouse of knowledge on subjects as diverse as tesla coils and garden railroading, Kriger left a mark with signature brilliance that reminded Floyd of two other 3000 legends, Fred White and Bruce Toback.

"Winston was up there with Fred and Bruce as far as I’m concerned," Floyd said. As a fellow Austinite, Floyd and worked with Kriger closely, going back to 1978. "I think he somehow tied three HP 3000 Series III’s together, way back there in that timeframe." The magic of such a combination didn't daunt Kriger.

His work on Backpack for Tymlabs and on Reveal/3000 from Opin Systems stood out among countless projects, creativity and precision that was often behind important scenes. His time in the marketplace ran from the 1960s to the current decade. In one of his many bemused signatures online, he said he'd been "specializing in 'obsolete' technology since the mid 20th Century." Kriger was a resource who vendors turned to when answers could be found nowhere else.

A Celebration of Life service for Kriger is set for 2 PM on March 16 at the Cook-Walden chapel in Austin. An online memory book for Kriger is at the Cook-Walden website. His is survived by his wife Ruth, son Carey, brother Brett, and brother-in-law Larry Miller.

Kriger was a Vietnam Era veteran who gathered some initial career experience from the Army Signal Corps. Memorial gifts may be sent to Austin Area Salvation Army, or to the National WW II Museum in New Orleans.

Posted by Ron Seybold at 08:58 PM in Newsmakers | Permalink | Comments (0)

March 08, 2019

It may be later than you think, by Monday

Clock-face
Daylight Saving Time kicks off early on Sunday. By the time you're at work on Monday it might seem late for the amount of light coming in your window. If you're working at home and next to the window, it will amount to the same thing. We lose an hour this weekend.

This reset of our circadian rhythms isn't as automatic as in later-model devices. Like my new Chevy, which is so connected it changes its own clocks, based on its contact with the outer world. HP 3000s and MPE systems like those from Stromasys don't reach out like that on their own. The twice-a-year event demands that HP 3000 owners adjust their system clocks.

Programs can slowly change the 3000's clocks in March and November. You can get a good start with this article by John Burke from our net.digest archives.

The longer that MPE servers stay in on the job, the more their important date manipulations will be to its users. The server already hosts a lot of the longest-lived data in the industry. Not every platform in the business world is so well-tooled to accept changes in time. The AS/400s running older versions of OS400 struggled with this task.

You also need to be sure your 3000's timezone is set correctly. Shawn Gordon explained how his scheduled job takes care of that:

"You only have to change TIMEZONE. For SUNDAY in my job scheduler I have the following set up to automatically handle it:

IF HPMONTH = 3 AND HPDATE > [this year's DST] THEN
   ECHO We are going back to Standard Time
   SETCLOCK TIMEZONE = W8:00
ENDIF
IF HPMONTH = 11 AND HPDATE < [this year's ST] THEN
   ECHO Setting clock for Daylight Savings Time
   SETCLOCK TIMEZONE = W7:00
ENDIF

3000 customers say that HP's help text for SETCLOCK can be confusing:

SETCLOCK  {DATE= date spec; TIME= time spec [;GRADUAL | ;NOW]}
   {CORRECTION= correction spec [;GRADUAL | ;NOW]}
   {TIMEZONE= time zone spec}
   {;CANCEL}

Orbit Software's pocket guide for MPE/iX explains shows the correct syntax. In this case, ;GRADUAL and ;NOW may only be applied as modifiers to the DATE=; TIME= keywords, not to ;CORRECTION=.

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

March 04, 2019

Playing ball for keeps with MPE

Pete-Rose-ball
In a regular conversation with MPE software vendors, surprising news surfaces. As I was calling into Hillary Software to catch up, I said hello to Carrie in support and sales. We hadn't met but she felt like an old comrade. Some of that has to do with tending to the needs and desires of people who won't let go of their legacy. In this case, the historic need was a sports company.

If you've ever purchased — or been gifted — a major league baseball, there's a good chance the case was made with the help of a 3000. Carrie said the country's largest manufacturer of sports memorabilia cases uses the Hillary Software, byRequest, to move its information into reports. The reports operate in a more modern era than MPE, of course. Excel is just 11 years younger than the HP 3000 and MPE.

At the manufacturer, the focus is on a much older pastime. There's something poetic about the HP 3000, a legacy giant, serving the needs of a company that preserves historic items. The value of a baseball lies in the heart of its collector. Sometimes the value of a legacy system lies in the heart of its manager. Preserving what's meaningful and productive isn't the same thing as protecting a signed baseball.

But they are the same in one special way. Decades from now, these balls will retain their memories of happiness. To be fair, it's MPE that will retain that happiness. Microsoft Excel began its life as Multiplan, a spreadsheet created in the days of CP/M. DOS overtook CP/M, just like Windows overtook DOS. The essence of what's great about Excel remains from those early days.

It's a joyful moment to see something of a legacy era doing everyday work. I found particular pleasure in seeing a software product, built to connect newer tools to an older OS and apps, help to create a preservation tool. Simple boxes. A simple solution.

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

March 01, 2019

There's more of this all the time, so dust

Vacuum-cleaner
Newswire Classic

By John Burke

As equipment gets older and as we neglect the maintenance habits we learned, we will see more messages like this.

Upon arrival this morning the console had locked up. I re-started the unit, but the SCSI drives do not seem to be powering up. The green lights flash on for a second after the power is applied, but that is it. The cooling fan does not turn either. I am able to boot, but get the following messages: LDEVS 5, 8, 4, 3, 2 are not available and FILE SYSTEM ERROR READING $STDIN (CIERR 1807).

When I try to log on as manager.sys, I must do so HIPRI, and get the following: Couldn’t open UDC directory file, COMMAND.PUB.SYS. (CIERR 1910) If I had to guess, I would say the SCSI drives are not working. Is there a quick fix, or are all the files lost? I should add that I just inherited this system. It has been neglected, but running, for close to two years. Is it time to pull the plug?

Tom Emerson responded

This sounds very familiar. I’d say the power supply on the drive cabinet is either going or gone [does the fan ‘not spin’ due to being gunked up with dust and grease, or just ‘no power’?] I’m thinking that the power supply is detecting a problem and shutting down moments after powering up [hence why you see a ‘momentary flicker’].

Tim Atwood added

"I concur. The power supply on the drive cabinet has probably gone bad. If this is an HP6000 series SCSI disc enclosure for two and four GB SCSI drives, move very quickly. Third-party hardware suppliers are having trouble getting these power supplies. I know the 4GB drives are near impossible to find. So, if it is an HP6000 series you may want to stock up on power supplies if you find them. Or take this opportunity to convert to another drive type that is supported.”

The person posting the original question replied, “Your post gave me the courage to open the box and the design is pretty straight forward. It appears to be the power supply. As I recall now, the cooling fan that is built into the supply was making noise last week. I will shop around for a replacement. I can’t believe the amount of dust inside!”

Which prompted Denys Beauchemin to respond

The dust inside the power supply probably contributed to its early demise. It is a good idea to get a couple of cans of compressed air and clean out the fans and power supplies every once in a while. That goes for PCs, desktops, servers, and other electronic equipment. The electrical current is a magnet for dust bunnies and other such putrid creatures.

Wayne Boyer of Cal-Logic had this to say; useful because supplies may be hard to locate

Fixing these power supplies should run around $75 to $100. Any modular power supply like these is relatively easy to service. I never understand reports of common and fairly recent equipment being in short supply. It is good advice to stock up on spares for older equipment. Just because it’s available somewhere and not too expensive doesn’t mean that you can afford to be down while fussing around with getting a spare shipped in.

The compressed air cans work, but to really do a good job on blowing out computer equipment, you need to use an air compressor and strip the covers off of the equipment. We run our air compressor at 100 PSI. Note that you want to do this blasting outside! Otherwise you will get the dust all over whereever you are working. This is especially important with printers, as you get paper dust, excess toner, etc. building up inside the equipment. I try and give our office equipment a blow out once a year or so. Good to do that if a system is powered down for some other reason.

Bob J. of Ideal Computer Services added

The truth sucks. There are support companies that don’t stock spare parts. The convenient excuse when a part is needed is to claim that ‘parts are tough to get.’ Next they start looking for a source for that part. One of my former employers always pulled that crap.

Unfortunately, quality companies get grouped with the bad apples. I always suggest system managers ask to visit the support supplier's local parts warehouse. The parts in their warehouse should resemble the units on support. No reason to assume the OEM has the most complete local stock either. Remember HP's snow job suggesting that 9x7 parts would become scarce and expensive? Different motive, but still nonsense.

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

February 27, 2019

Wayback: MPE joins the land of the Internet

Whole-Internet-Catalog
In a February of 23 years ago, HP brought MPE/iX into the Internet era. During that year, Sun was already running roughshod over the computer industry by selling servers built for use on the networks that were exploding around the World Wide Web. The 3000 community knew how to call the Internet the WWW, thanks to early guides like the Whole Internet User's Guide and Catalog. Modeled after the Whole Earth catalog of the 1970s, the early O'Reilly & Associates book covered basic Internet utilities like telnet and FTP, rudimentary search tools like Gopher, plus a quick reference card to remember essentials like the commands for Archie, an FTP utility. The book boasted nine pages of Internet Service Provider listings.

Five years after those ISP listings were printed, they remained in the pages of the Catalog, unaltered. Putting books onto the Internet was still out in the future, some five years away. That's not the Amazon start date, because that distributor was selling only paper books until 2004.

The O'Reilly guide was recommended to 3000 managers by David Greer of Robelle. In the pages of that February's NewsWire, Greer shared the basics of being a 3000 manager who used the WWW to "get you online and finding information that helps you manage your HP 3000." The finding was taking place via Unix or PC systems, not HP 3000s. HP had a set of CD-ROMs it sold with the electronic versions of its documentation.

In that same issue, the 3000 market learned that HP would be releasing a Web server that would run under MPE/iX. Delivery of the OpenMarket Web Server was supposed to start in July. HP had to port the third party product, working with code from an OpenMarket product already released for HP-UX systems. HP was selling such a wonder at prices starting at $1,650. While the rest of the world was working with open source Apache for Web services, HP was tier-pricing a Web server. Hopes were high among Web experts, who said "even the smallest HP 3000 can be used to handle lots of Web requests, especially since the Open Market product is about five times more efficient than freeware alternatives."

A stutter step was the best that HP could do for the Open Market introduction. By summertime the server's porting was called off, making the 3000 look even further away from Internet-ready. In a couple of years HP was using a port of open source Apache to make a secure Web server for MPE/iX. HP would be so confident of the 3000's Internet suitability that it renamed the server the e3000. That e was for e-commerce, we were told.

In the same month as the Web server news, HP announced it was putting its MPE/iX patches online. Delivering OS patches for a computer whose roots were in the minicomputer era felt splashy, even if 14K modems were doing the work.

Read "Wayback: MPE joins the land of the Internet" in full

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

February 25, 2019

Itanium, we hardly knew ye, aside from HP

Titanic
Earlier this month, the computer community learned how late in life Itanium was living. The chip architecture was going to rule the world when HP and Intel first announced it in 1994 as a project called Tahoe. Intel ruled the world with x86 architecture then in the lion's share of PCs. Literally, as in the true definition of lion's share: all of it. 

It's taken 25 years, but Intel has called Time's Up for its design it co-created with HP. Intel told its customers that the final order date for Itanium 9700 series processors is January 20 of next year. The final Itanium processor shipments end on July 21, 2021.

Itanium was essential to the HP decision to stop manufacturing HP 3000s. Itanium was going to be the future of all enterprise computing, the company figured right after Y2K. There was not enough money in the R&D budget at HP to fund the redesign of MPE/iX for a new processor. VMS, sure, HP would do that for a market that was four times the size of MPE/iX.

By now HP has split in two and Itanium is nowhere but in the HP Enterprise servers, the ones running VMS and NonStop. HPE says it will support its Itanium-based Integrity servers until 2025. A superior article in the the EE Journal includes this summary.

Itanium’s developers sought a path to much faster processing. Unfortunately, the theory behind Itanium’s development was just plain wrong. While VLIW architectures do appear to work well for specialty processors running well-behaved code, particularly DSPs, they’re just not appropriate for general-purpose applications thrown willy-nilly at server processors.

And so, we remember the fallen.

It's taken awhile to understand the inertia that occupies the energy of the computer industry. HP seems to have a side of itself that learned such lessons more slowly than most enterprises. HP was late to Windows (who needed GUIs?) and got well behind the pack on the Internet (Sun crowed over HP's sluggish pace by the late 1990s.) After creating its own RISC chip in PA-RISC, HP figured that another chip developed along with the creator of the x86 was a slam dunk. 

There was a time for dictating the way forward in computing with a new architecture for chips. That time passed well before Y2K. HP hung on for more than a decade in full denial, even as it revved up the ProLiant enterprise servers using x86.

It's not easy to see a clean future in the years beyond 2025 for the companies which are invested in Integrity systems. But no one could see how the PA-RISC servers of the 3000 were going to be anything but a write-off for their users, either. The strength of the operating environment, as well as a long history of efficient computing, gave the 3000 a longer lease on life. Now's the time to see if the HP-UX and NonStop environments are going to make the jump to x86. We're also watching how well they leap and what the HP of the 2020's will say. 

Read "Itanium, we hardly knew ye, aside from HP" in full

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

February 22, 2019

Cautions of a SM broadsword for every user

Broadsword
NewsWire Classic

By Bob Green

Vladimir Volkh was doing MPE system and security consulting at a site. One of his regular steps is to run VESOFT’s Veaudit tool on the system. From this he learned that every user in the production account had System Manager (SM) capability.

Giving a regular user SM capability is a really bad thing. It means that the users can purge the entire system, look at any data on the system, insert nasty code into the system, etc. And this site had just passed their Sarbanes-Oxley audit.

Vladimir removed SM capability from the users and sat back to see what would happen. The first problem to occur was a job stream failure. The reason it failed was because the user did not have Read access to the STUSE group, which contained the Suprtool "Use" scripts. So, Suprtool aborted. 

Background Info

For those whose MPE security knowledge is a little rusty, or non-existent, we offer a a helpful excerpt from Vladimir’s son Eugene, from his article Burn Before Reading - HP3000 Security And You – available at www.adager.com/VeSoft/SecurityAndYou.html

<beginarticlequote>

When a user tries to open a file, MPE checks the account security matrix, the group security matrix, and the file security matrix to see if the user is allowed to access the file. If he is allowed by all three, the file is opened; if at least one security matrix forbids access by this user, the open fails.

For instance, if we try to open TESTFILE.JOHN.DEV when logged on to an account other than DEV and the security matrix of the group JOHN.DEV forbids access by users of other accounts, the open will fail (even though both TESTFILE’s and DEV’s security matrices permit access by users of other accounts).

Read "Cautions of a SM broadsword for every user" in full

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

February 20, 2019

Security advice for MPE appears flameproof

Burn-before-reading

Long ago, about 30 years or so, I got a contract to create an HP 3000 software manual. There was a big component of the job that involved making something called a desktop publishing file (quite novel in 1987). There was also the task of explaining the EnGarde/3000 security software to potential users. Yow, a technical writer without MPE hands-on experience, documenting MPE V software. 

Yes, it was so long ago that MPE/XL wasn't even in widespread use. Never mind MPE/iX, the 3.0 release of MPE/XL. All that didn't matter, because HP preserved the goodness of 3000 security from MPE V through XL and iX. My work was to make sense of this security as it related to privileges.

I'll admit it took yeoman help from Vicky Shoemaker at Taurus Software to get that manual correct. Afterward I found myself with an inherent understanding, however superficial, about security privileges on the HP 3000. I was far from the first to acquire this knowledge. Given another 17 years, security privileges popped up again in a NewsWire article. The article by Bob Green of Robelle chronicled the use of SM capability, pointed out by Vladimir Volokh of VEsoft.

Security is one of those things that MPE managers didn't take for granted at first, then became a little smug about once the Internet cracked open lots of business servers. Volokh's son Eugene wrote a blisteringly brilliant paper called Burn Before Reading that outlines the many ways a 3000 can be secured. For the company which is managing MPE/iX applications — even on a virtualized Charon server — this stuff is still important.

I give a hat-tip to our friends at Adager for hosting this wisdom on their website. Here's a recap of a portion of that paper's good security practices for MPE/iX look like.

Volokh’s technical advisory begins with a warning. “The user is the weakest link in the logon security system -- discourage a user from revealing passwords. Use techniques such as personal profile security or even reprimanding people who reveal passwords. Such mistakes seem innocent, but they can lose you millions."

Read "Security advice for MPE appears flameproof" in full

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

February 18, 2019

Driving a Discontinued Model with Joy

Volt
When a chariot has stopped rolling off the line, it might well be the time to buy one. That's what happened to me, unexpectedly, this weekend. I felt a kinship with HP 3000 owners of the previous decade as I weighed my purchase of a new car.

Like the HP 3000, my 2019 Chevy Volt was the ultimate model of a superior design and build. The Volt was Chevy's foundational electric vehicle when the vehicle made its debut in 2011. Back in that year it was costly (true of the 3000, even through most of the 1990s) unproven (MPE/XL 1.0 was called a career move, and not a safe one) and unfamiliar — plugging in a car inside your garage might have been as unique as shopping for applications knowing every one would work with your built-in IMAGE database.

The Volt grew up, improved (like the final generation of 3000 hardware, A-Class and N) and gained a following I've only seen in the best of designs. People love this car. There's a Facebook group for Volt owners, many of whom crow and swagger as they point out things like the intelligence of the car's computer systems or the way that an owner can train a Volt to extend its electric-only range. The latter is a matter of how often the car is charged plus a combination of a paddle on the steering wheel, a gear range, and the right driving mode. H is better sometimes.

Yes, it's as complex as any intrinsic set tuned for a bundled database. The Volt's efficiency rivals the best aspects of a 3000 at the start of the millennium. GM, much like HP, decided the future of the car would not include manufacturing it. Just as I was poised to purchase, after healthy research, I learned its sales had been ended. 

The Facebook group mourned, and one owner said the car would be a collector's item someday. That's when I thought of my 3000 bretheren and signed up for six years of Volt car payments. I had the full faith of two governments behind me, however. Both the US and Texas wanted to reward me for buying something so efficient. That's how this story diverges from the HP decision about the 3000. It was the resellers, as a private group, that made those last 3000s such a great deal.

I remember when the HP cancelation was announced, Pivital Solutions was still in its first 24 months of reselling the 3000. The company remained in the business of shipping new hardware as long as HP would build new systems. Ever since that day in 2003, Pivital has supported the hardware and backstopped the software. Pivital is one of the Source Code Seven, those companies which have licenses to carry MPE/iX into the future.

Pivital and a few others in the community sealed the deal on 3000 ownership in the post-manufacturing era of the computer. No matter how long you decided to own a 3000, you could get a support contract on hardware and software. GM is promising the same to me, for the next 10 years. After that, I'm in the wilds of great fandom and aftermarket service. Your community showed great confidence in that kind of era from 2004 onward.

Read "Driving a Discontinued Model with Joy" in full

Posted by Ron Seybold at 07:40 PM in Homesteading, News Outta HP | Permalink | Comments (0)

February 15, 2019

Scripting a Better UPS link to MPE/iX

In another article we talked about how HP dropped the ball on getting better communication between UPS units and the HP 3000. It was a promise that arrived at about the same time as HP's step-away from the 3000. The software upgrade to MPE/iX didn't make it out of the labs.
 
That didn’t stop Donna Hofmeister. About that time she was en route to a director's spot on OpenMPE. Later on she joined Allegro. We checked in to see if better links between Uninterrupted Power Supplies via MPE/iX was possible. Oh yes, provided you were adept at scripting and job stream creation. She was.
 
"I wrote a series of jobs and scripts that interrogate an APC UPS that is fully-connected to the network — meaning it has an IP address and can respond to  SNMP," she said. "These are the more expensive devices, for what it's worth."
 
"It worked beautifully when a hurricane hit Hawaii and my 3000 nicely shut itself down when power got low on the UPS. Sadly, the HP-UX systems went belly-up and were rather a pain to get running again."

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

February 13, 2019

Why a UPS FAIL let down a 3000's shield

Fail
Previously, when a pair of HP 3000s were felled in the aftermath of a windstorm which clipped out the power at Alan Yeo's shop, his Uninterrupted Power Supply in the mix failed as well. After a couple of glasses of merlot, our intrepid developer and founder of ScreenJet continued to reach for answers to his HP 3000 datacenter dilemma. Why did that UPS that was supposed to be protecting his 3000s and Windows servers FAIL once the power died? 

By Alan Yeo
Second in a series

Feeling mellower and with nothing I really wanted to watch on the TV, I decided to take a prod at the servers and see what the problems are. I decided I'd need input to diagnose the Windows Server problem, so that could wait until the morning. Power-cycled the 917 to watched the self-test cycle and got the error, did it again. (Well sometimes these things fix themselves, don't they?) Nope, it was dead! 

Google turned up nothing on the error. Nothing on the 3000-L newsgroup archives, either. I'd tell you the 3000 error code, but I've thrown away the piece of paper I had with all the scribbles from that weekend.

Where's a guru
when you want one?

I really wanted to get my 917 back up and running over the weekend, as it had all our Transact test software on it. Dave Dummer (the original author of Transact) was doing some enhancements to TransAction (our any-platform replacement for Transact) and we had planned to get some testing done for early the following week, to help a major customer.  

So it's 11:30 PM UK time, but it's only 3:30 PM PDT. I wonder who's still around at Allegro? A quick Skype gets hold of Steve Cooper, who with the other Allegroids diagnose within five minutes that the 3000 has got a memory error. The last digit of the error indicates which memory bank slot has the problem.

Okay, I'm not going to start climbing around the back of the rack at this time of night. I leave it until the morning, but at least I know what the problem is.

Read "Why a UPS FAIL let down a 3000's shield" in full

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

February 11, 2019

Making a UPS Light Up a 3000

Lightning_bolt_power_stripEditor's note: A recent message thread on the 3000-L mailing list and newsgroup reported on attaching an Uninterruptible Power Supply (UPS) to a 3000. The question came up when an MPE/iX manager asked about hooking up a UPS to an emulated 3000. While that is proof enough that the Charon emulator is working in the field, the question still covered HP's MPE hardware. More than five years ago Alan Yeo covered this ground for us in a lively and informative two-part feature.

Intrepid veteran developer Yeo of ScreenJet in the UK had a pair of HP 3000s felled, despite his sound strategy of using an Uninterrupted Power Supply in his IT mix (or "kit," as it's called in England). Here is Yeo's first installment of the rescue of the 3000s which logic said were UPS-protected. As Yeo said in offering the article, "We're pretty experienced here, and even we learned things through this about UPS." We hope you will as well.

New UPS, sir! or "Would you like fries with that?"

By Alan Yeo
First of a two parts

"Smart UPS" now has a new meaning to me. "You're going to smart, if you're dumb enough to buy one" I guess this is one of those stories where if you don't laugh you'd cry, so on with the laughs.

By the end of this tale, you should know why your UPS may be a pile of junk that should be thrown in the trash. And what you should replace it with.

A Friday in early June and it was incredibly windy. Apparently we were getting the fag end of a large storm that had traversed the Atlantic after hitting the US the week before. Sort of reverse of the saying "America sneezes, and Europe catches a cold." This time we were getting the last snorts of the storm.

Anyway, with our offices being rurally located, strong winds normally mean that we are going to get a few power problems. The odd power blip and the very occasional outage as trees gently tap the overhead power lines. Always worst in the summer, as the trees are heavily laden with leaf and drooping closer to the lines than they are in the winter, when they come round and check them.

So this situation is not normally something we worry about. We are fairly well-protected (or so we thought) with a number of APC UPS units to keep our servers and comms kit safe from the blips and surges. The UPS units are big enough so that if the power does go out, we can keep running long enough for either the power to come back -- or if we find out from the power company that its likely to be a while, for us to shut down the servers.

We keep all the comms kit, routers, switches, firewalls and so forth on a separate UPS. This UPS will keep them running nearly all day, so that way we still have Internet access, Web, email and more, so can keep functioning, as long as the laptop batteries hold out.

Read "Making a UPS Light Up a 3000" in full

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

February 08, 2019

What can a 3000 do to talk to a modern UPS?

SmartUPS
Michel Adam asks, "How can I install and configure a reasonably modern UPS with a 3000? I'd like to use something like an APC SmartUPS or BackUPS, for example. What type of signaling connection would be the easiest, network or serial?"

Jim Maher says

First you need to find out what model 3000. Listed on the back will be the power rating. Some of the older ones use 220V. Then you can match that with a proper UPS.

Michel Adam explains in reply

This HP 3000 is an emulator, i.e. a 9x8 equivalent or A-Class. I guess a regular "emulated" RS-232, or actual ethernet port would be the most likely type of connection. In that sense, the actual voltage is of no consequence; I only need to understand the means of communicating from the UPS to the virtual 3000.

Tracy Johnson reports

While we have three "modern" APC units each with battery racks four high, they also serve the rest of the racks in our computer room. Our HP 3000 is just a bigger server in one of those racks. Each APC services only one of the three power outlets on that N-Class. Their purpose is not to keep the servers "up" for extended periods, but to cover for the few seconds lapse before our building generator kicks in in case of a complete power loss.

As far as the UPS talking to our HP 3000 serial port, we didn't bother. Our APC units are on the network so they have more important things to do, like send emails to some triage guy in Mumbai should they kick in.

Enhanced, or not?

In the history department, Hewlett-Packard had its labbie heart in the right place just weeks before the vendor canceled its 3000 plans. We reported the following in October of 2001

HP 3000s will say more to UPS units

HP's 3000 labs will be enhancing the platform to better communicate with Uninterrupted Power Supply systems in the coming months. HP's Jeff Vance reports that the system will gain the ability to know the remaining time on the UPS, so system managers can know that the UPS will last long enough to shut down my applications and databases and let the system crash. Vance said that HP has scheduled to begin its work on this improvement—voted Number 8 on the last System Improvement Ballot—in late fall.

Late fall of 2001 was not a great time to be managing future enhancements for the 3000 and MPE/iX. The shortfall of hardware improvements and availability has been bridged by Charon. Adjustments to MPE/iX for UPS communication have not been confirmed.

Posted by Ron Seybold at 05:53 PM in Hidden Value, User Reports | Permalink | Comments (0)

February 06, 2019

Wayback: MPE's Computer Scientist Expires

Kick Butt Poster

Wirt Atmar conceived and lead The World's Largest Poster Project (shown above) with the help of hundreds of volunteers on a Southern California football field.

Ten years ago this week the 3000 community was reminded of its mortality. Wirt Atmar, founder of AICS Research and the greatest scientist to practice MPE development, died in his New Mexico home. Wirt was only 63 and demonstrated enough experience in the 3000's life to seem like he'd been alive much longer.

Atmar died of a heart attack in his hometown in Las Cruces, NM. It was a place where he invited everyone to enjoy a free enchilada dinner when they visited him there. He once quipped that it was interesting to live in a state where the omnipresent question was about sauce: "Green or red?" He gravitated to new ideas and concepts and products quickly. Less than a month after Apple introduced the iPhone, he bought and tested one, praising its promise even as he exposed its failures from the unripened state of its software to the cell signal unavailability.

If I go outside and stand under one specific tree, I can talk to anyone I want. In only one week, I have felt on multiple occasions like just heaving the phone as far as I could throw it -- if it weren’t so damnably expensive. The iPhone currently resembles the most beautiful cruise liner you’ve ever seen. It’s only that they haven’t yet installed the bed or the toilet in your stateroom, and you have to go outside to use the “facilities” — and that’s irritating even if the rest of the ship is beautiful. But you can certainly see the promise of what it could become.

He was not alone in predicting how the iPhone would change things, but being a scientist, he was also waiting on proof. The postings on the 3000-L mailing list were funny and insightful, cut sharp with honesty, and complete in needed details. A cruise through his postings on the 3000 newsgroup stands as an extraordinary epitaph of his passions, from space exploration to environmental science to politics to evolution and so much more. He was a mensch and a brilliant polymath, an extraordinary combination in any human.

Less than 24 hours before he died, Wirt posted an lively report on migration performance gains he recorded after moving an MPE/iX program to faster hardware running Linux. It was an factual observation only he could have presented so well, an example of the scientific practice the community loses with his passing.

One of the 3000 founders who was best known by his first name, Wirt was respected in the community for his honest and pragmatic vision of the 3000's history and potential, expressed in his countless e-mails and postings to the 3000 newsgroup. But alongside that calculating drive he carried an ardor for the platform.

Wirt was essential in sparking HP's inclusion of SQL in IMAGE, a feature so integrated that HP renamed the database IMAGE/SQL. In 1996 he led an inspired publicity effort that brimmed with a passion for possibility, conceiving and leading The World's Largest Poster Project (shown above) with the help of hundreds of volunteers on a Southern California football field. He quipped that after printing the hundreds of four-foot rolls of paper needed for the poster, loading them into a van for the trip to California represented "the summer corporate fitness program for AICS Research."

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

February 04, 2019

Long-time MPE licensees leave dates in dust

Date book
I went to a birthday celebration for Terry Floyd yesterday as part of a Super Bowl party. You may begrudge them the kudos, but congrats to the Pats, who once again executed like the MPE applications still running this week in businesses around the world. Not flashy, like MPE, but every day brings no surprises. That's a very good thing for enterprise computing, and always has been.

Floyd's turned 70 -- he’s the guy who started The Support Group here in Austin to serve MANMAN 3000 customers. One of those customers was in town to celebrate. Ed Stein spent years managing MANMAN at MagicAire, a Carrier subsidiary.

That corporation is still using MPE, even after Ed has gone. He’s moved into the interesting fields of independent support and consulting on MPE. He mentioned he's available to the community's 3000 owners looking for MPE talent. Along the way he's developed his experience on the prospects for keeping dates nine years from now in MPE.

It was Stein's intentions for prepare for the 2027 date keeping changes that led several companies to spin up services and strategies for date-keeping in 2028 and beyond. What was mumbled about in private became more public offerings and strategies. During a conference call among MANMAN managers late in 2017, Floyd and others talked about how much work it will be to keep dates straight in an era HP never planned for.

Stein says that in his travels though the community he’s still running into many a 3000 user who’s got no idea their OS will stop making accurate dates in less than nine years. He also made reference to Beechglen and its 2028 patch service. Like everyone else who's using HP's MPE source code licenses, Beechglen cannot sell a product to patch MPE/iX. HP was never going to sell permission to create patched versions of MPE/iX.

Seven companies paid HP $10,000 each to become the source code licensees about nine years ago. At the time, the 3000's operating environment felt like a long shot to feel its age and forget its date-keeping skills. The server was 18 years away from a date that no working MPE server would ever see, right?

Don't look now, but 2027 is gaining on the community. Floyd was one of several developers who identified the scope of the work to make an app like MANMAN ready for the year 2028.

Some customers will get readiness for 2028 by becoming 3000 support customers. Any support company using the MPE source must package the repairs and improvements they develop as support offerings. There are a half-dozen more companies with source capabilities for MPE/iX. Getting a relationship in place with them will be on some to-do lists for 2019. Even the companies without a clue about date keeping will eventually catch on to where the correct tomorrows are going to come from: solutions off the support bench.

Posted by Ron Seybold at 09:45 AM in Homesteading, News Outta HP | Permalink | Comments (0)

January 28, 2019

MPE vendors walk wooded path into futures

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

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

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

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

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

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

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

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

January 23, 2019

The State of the 3000's Union, 2019

Us-capitol-477987_1280
The world is still open for business, even if parts of the US Government are not this week. Shutdown has become an ugly word by now. And to think, it was a different kind of ugly word in the world of 1999. 3000 managers would say to support, "What do mean I have to do a SHUTDOWN?" The 3000 was always online, in the minds of many of its customers. When we started the Newswire in 1995, I dubbed our website Always Online.

Those were tender young days for the Internet, but that year was a part of the mature adult life of MPE/iX. In this first month of 2019, it's worthwhile to be plainspoken about what an operating system that's more than 31 years old can still do. I'm counting from the summer of 1987, when the PA-RISC-ready MPE XL emerged. Of course, MPE goes back an extra 13 years before that. Who's counting?

You can be counting forward in 2019. There's technology and support consulting to take the 3000 into the year 2028. For a long time the computer was not supposed to keep dates accurately in that year or beyond. I recall Vladimir Volokh telling me that that the end of 2027 barrier was just something else that would be overcome. He also liked to say that the horizon is an elusive thing, because it's always in front of you. The horizon for MPE/iX is ever-forward.

In a couple of examples, Donna Hofmeister — who was once a director of an advocacy group called OpenMPE — sent me her thoughts about how ready MPE/iX still is in 2019. The state of the operating system's union is sound enough to let it be used by a surprising number of companies.

I pointed out to her that the hardware which drives MPE/iX is not in the greatest state.

There’s more obvious stuff, like the failure of tape media and tape devices, or the age of power supplies and HP gear. Seems that Charon takes care of those things. How about the security, file transfer, and compilers?
"Charon nicely deals with the hardware issues, of course," she said.
Disk drives are 'sorta' a problem. There's issues with dependable, small (4Gb) drives -- but that's rather a 'duh'. There are clear issues, imo, regarding tape drives and media. I've been encouraging our customers to seriously consider doing backups to disc. Even better, take that backup and move it to 'the cloud'. Here's what we're doing:
Image
 
This picture shows how Allegro is using 'BackBlaze' to hold all of our systems' backups. And yes, I tested this! And no, it's not a replacement for making and testing CSLTs.
Hofmeister added, "I'll suggest that some of MPE's problems are not with the machines, rather with the people running them."

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

January 14, 2019

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

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

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

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

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

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

Read "How far behind is MPE/iX, really? One look..." in full

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

January 11, 2019

Fine-tune: how to reinstate config files

Reinstate logo
I’m replacing my old Model 10 with a Model 20 on MPEXL_SYSTEM_VOLUME_SET. This will of course require a re-INSTALL. What’s the best way to reinstate my network config files? Just restore NMCONFIG and NPCONFIG? Can I use my old CSLT to re-add all my old non-Nike drives and mod the product IDs in Sysgen, or do I have to add them manually after using the Factory SLT?


Gilles Schipper replies:

Do the following steps:
- using your CSLT to install onto LDEV 1
- modify your i/o to reflect new/changed config.
- reboot
- use volutil to add non-LDEV1 volumes appropriately
- restore directory or directories from backup
- preform system reload from full backup - using the keep, create, olddate, partdb,show=offline options in the restore command
- reboot again
No need for separate restores of specific files.

We had another hard drive fail this weekend. It was in an enclosure of old 2GB drives that we really did not need, so I just unplugged them and rebuilt my volumes without them. However, when I boot up I get error messages that path 10/4/0.20-26 can’t be mounted. How do I get rid of these messages?

Gilles Schipper replies:
You can safely ignore the messages, but if you want them not to reappear, simply remove those devices from your IO configuration via SYSGEN, keep the new configuration to config.sys and reboot with a start norecovery. When you’re back up again, you should create a new slt tape.

Paul Edwards adds:
Use SYSGEN with DOIONOW or IOCONFIG to delete them. No reboot is required.

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

January 09, 2019

Wayback: 2009's emulator hopes, proven

PA-RISC-clock

In 2009 in this month we made a case for why the time was ripe for a product to emulate HP's aging hardware for MPE/iX. Time has only reinforced those talking points. It's worthwhile to review them while figuring what your plan is going forward. If you're among the managers in the double-digit futures club -- those planning for 10 years and more of MPE -- consider what was true then, and just as true now.

Early in the transition era the homesteading advocates in the community pumped up the ideal of an emulator, hardware that would make up for the 3000s which HP would be stripping out of its product lineup. The market learned that the final generation of 3000s was better connected and faster, but few in number. HP's late delivery of N-Class and A-Class systems hampered production. If you needed a faster 3000 than the top-end 900 Series, you hunted for N-Class servers that the customers were returning once they migrated.

• Staying with MPE/iX solutions means a customer needs to keep planning for more connectivity and speed. An emulator can leverage the latest Intel chip designs, rather than stay native on the familiar PA-RISC architectures of HP.

• There's nothing built upon PA-RISC that can network and integrate like an Intel-based server. The irony of that reality is not lost on the 3000 customer, who saw the Intel+MPE generation first promised, then denied to the community.

• Emulator vendors need MPE/iX expertise to make a product of any use to the 3000 market. There's exactly one that's got it, and they've had it now for at least eight years. We've seen more hopes become realities since then.

Read "Wayback: 2009's emulator hopes, proven" in full

Posted by Ron Seybold at 08:41 PM in History | Permalink | Comments (0)

January 07, 2019

Virtualization: only as good as its legacy lore

MPE:iX Search Priority
(Hat-tip to 3kRanger's website)

Getting rid of HP's hardware will be a more popular choice during this year. For some companies that might mean shedding MPE/iX. The Hewlett-Packard iron worries some 3000 sites. But not enough to drop MPE/iX, for other customers.

So they adopt a virtualization plan and put their 3000 onto Intel hardware. Charon is the way forward for their MPE/iX applications. There's a lot to be said for the magic of an emulator when it made its debut. The greater miracle is running a legacy OS in a world of modern options. Linux as the bedrock, SSD as storage, cloud servers waiting for any MPE/iX customer brave enough to need them. (Using a cloud with Charon? We'd like to hear from you.)

There's always a legacy chord running through the virtualized sonata. It's been important, since 2012, to have someone in the mix who's got a foot planted in both worlds: virtualized datacenter guru as well as the world of running STORE and RESTORE on MPE/iX. A person who's got background in how IMAGE/SQL datasets are accessed by applications, as well as the MPE/iX practices for jobstreams to keep workflows running smoothly.

Doug Smith has been that person with a foot in both worlds for Stromasys. He arrived with MANMAN experience, using ERP know-how to smooth Charon into companies. Before him it was Paul Taffel, taking his experience from Orbit Software and using it to plant the emulator into fresh fields.

By today the exposure to the virtualized 3000 has become more commonplace. Support experts with decades of MPE/iX background are getting used to working on PA-RISC 3000s that no longer use HP's hardware. A virtualized system is no better than the expertise about its legacy, though. It's the lore like the illustration above that companies must preserve to keep using MPE/iX here in its fourth decade.

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

January 04, 2019

Fine-tune: Validating interleaved backups

DLT cartridge

Experts on 3000 practices are advising customers to get away from using tape devices. You may have no other choice while tending to an achival system, though. An interleaved backup requires special handling.

Backup errors on STORE tapes can occur when you try to restore on the exact same drive the backup tape was made on. There's a tape restore issue to manage with interleaved DLT tapes. For example, a DLT7000 must be on a different device adapter if tapes are to be used at the same time when backing up in interleave option. Interleaving provides a higher disk data rate. It is accomplished by reading from several disk drives (files) simultaneously. The file data is blocked together and then stored to the specified devices. The effect is to accelerate the STORE process.

The workarounds are to not use tapes on same device adapter for interleave restores, or put the DLT7000 devices on different device adapters.

It's not recommended to validate any tape after writing a backup onto it. "You always want to validate on a different different tape drive,” says Allegro's Stan Sieler. For example, on Intuit’s HP 3000s, “they happily validated the tapes for months. Then the tape drive was replaced, and no backups would validate on the new drive—or on any other drive.”

Finally, verifying a backup with validation can be done automatically right after the backup overnight, if you put the tape drive back online with the ONLINE utility. You can download ONLINE from Allegro’s website. 

Posted by Ron Seybold at 10:55 PM | Permalink | Comments (1)

January 02, 2019

New year gives MPE a ride on a Raspberry

Raspberry Pi
Robert Mills has a plan to put an HP 3000 in his pocket. The UK programmer reported this week that he's got the MPE V version of an HP 3000, the Series III Simulator, running on a Dell Inspiron desktop. The Simulator gives Intel-based servers the ability to mimic HP's Classic 3000 hardware -- in the same style as the Stromasys Charon virtualizing software lets HP's PA-RISC processing be hosted on Intel systems.

Mills says he's working his way backwards in time for 3000 computing. Once his simulated HP disk drives can be replicated, he'll have a 3000 circa 1983 running on his Dell system.

The simulator on my main computer (Dell Inspiron 3668 running Linux Mint 18.3 with Cinnamon Desktop) has two HP7925 (120Mb) disc drives, two HP7970E tape drives, and 1024K words of memory. The simulator reports that it is executing machine instructions approx 95 times faster than a real Series III. With a little bit of work I could increase the number of HP7925s to eight. This would give me a system that equals, except for the processing speed, a system I worked on during 1981-83.

It's fun to note that the simulated Classic 3000 runs 95 times faster than the original HP hardware. This echoes the upgrade potential of a system virtualizer like Charon. Host the emulated 3000 on faster Intel hardware and see performance increase. The size of the 3000 itself is decreasing for Mills in his plans.

"The next thing I plan to do is try and install the simulator on my Raspberry PI 2B, which has a 2Tb Seagate Expansion Drive," Mills said. "If it works, I'll have an HP 3000 that I can carry in my pocket." The Raspberry is the hardware that helped drive the Rover on the surface of Mars. It's a wonderful story of how a community has lifted a processor into such demanding jobs.

Read "New year gives MPE a ride on a Raspberry" in full

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

December 31, 2018

Date upgrade deadline: now in single digits

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

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

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

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

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

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

December 28, 2018

Fine Tune: Optimized Disaster Recovery

Disasters
By Gilles Schipper

While working with a customer on the design and implementation of disaster recovery (DR) plan for a large HP 3000 system, it became apparent the implementation had room for improvement.

In this specific example, the customer had a production N-Class HP 3000 and a backup HP 3000 Series 969 system in a location several hundred miles from the primary.

The process of implementing the DR was completed entirely from a remote location — thanks to VPNs and an HP Secure Web Console on the 969. One of the most labor-intensive aspects of the DR exercise was to rebuild the IO configuration of the DR machine (the 969) from the full backup tape of the production N-Class machine, which included an integrated system load tape (SLT) as part of the backup.

The ability to integrate the SLT on the same tape as the full backup is very convenient. It results in a simplified recovery procedure as well as the assurance that the SLT to be used will be as current as possible.

When rebuilding a system from scratch from a SLT/Backup tape, if the target system differs in architecture from the source system, it is usually necessary to modify all the device paths and device configuration specifications with SYSGEN and then rebooting the system in order to even be able to utilize the tape drive of the target system to restore any files at all.

(This would be apart from the files restored during the INSTALL process — which does not require proper configuration of any IO component at all).

Some would argue that this system re-configuration needs to be completed only once, since any future system rebuilds would require only a “data refresh” rather than a complete system re-INSTALL.

I say that this would be true only in very stable system environments where IO configurations — including network printer configurations — are static and where TurboIMAGE transaction logging is not utilized. Otherwise there could be unpleasant results and complications from using stale configurations in a real disaster recovery situation. In any case, there really is no reason to take any chances,

Read "Fine Tune: Optimized Disaster Recovery" in full

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

December 26, 2018

3000 security status: obscure and secure

Bank vault
Earlier this year Jeff Kubler of Kubler Consulting was trying to label the status of MPE/iX security. The distinction between hardware and software is noteworthy. Whatever security the 3000s had confers onto the virtualized 3000s running under the Charon emulator from Stromasys.

Kubler built a list of the known conditions and advantages

  • Unknown operating system
  • Password protected
  • Must know how to address it with HELLO
  • Must know or guess the user
  • Could have additional security like VEsoft strenghtening the additional login string
  • Security on the account, user and group level could keep those who even know a login from getting anything important 
  • No visiting websites while using an HP 3000 application

When Alan Yeo of ScreenJet said the 3000 security is weak ("if you have locked the doors, then it will stop someone who just tries the door handle"), Pro 3K's Mark Ranft wanted to disagree.

The correct description is Security through Obscurity. If your HP 3000 has VESOFT's Security 3000 installed, and it is properly configured with two factor authentication, I don't know if anyone, without physical access to the machine, or access to unencrypted backups media, that could break in.

Where the HP 3000 falls short is in encryption of data that is in transit between the user and the system.  For this, I recommend you turn to MiniSoft Secure 92 for terminal access.

And unfortunately, if you host a website on the HP 3000, I have to admit the HP WebWise MPE/iX Secure Web Server is not TLS 1.2 capable. This would be a showstopper for PCI certification. But this is only a big deal if you accept credit card or other protected information via the website.

Finally, depending on your location or customer base, you may also need to worry about GDPR.

That two-factor feature might not be fully available under MPE/iX, depending on your definition of 2FA.

Read "3000 security status: obscure and secure" in full

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

December 24, 2018

Gifts given, 11 years after a Christmas

Gifts-under-tree
Eleven years ago we wished for nine things that would help 3000 users in the years to come. At the close of 2007 there was no virtual HP 3000 product like Charon. We didn't even allow ourselves to wish for such a thing.

But here on the last office day before Christmas, it's fun to review our holiday wish list. Let's see what we got and what HP withheld until it was too late for the vendor to supply what the community requested.

We've heard these desires from HP 3000 customers, consultants and vendors. Some of the wishes might be like the Red Ryder BB-Gun that's at the center of the holiday epic A Christmas Story. As in, "You don't want that, you'll put your eye out." If you're unfamiliar with the movie, the line means "I don't want you to have that, because I worry what you will hurt once you get it."

1. Unleashing the full horsepower of A-Class and N-Class 3000 hardware
2. Just unleashing the power of the A-Class 3000s (since every one of the models operates at a quarter of its possible speed)
3. Well, then at least unleash the N-Class systems' full clock speeds
4. HP's requirements to license a company for MPE/iX source code use
5. A way to use more than 16GB of memory on a 3000
6. A 3000 network link just one-tenth as fast as the new 10Gbit Ethernet
7. A water-cooled HP 3000 cluster, just like IBM used to make
8. A guaranteed ending date of HP's 3000 support for MPE/iX
9. Freedom to re-license your own copy of MPE/iX during a sale of an 3000

HP finally supplied Numbers 4 and 8. The first created the Source Code Seven, vendors who hold licenses that let them create workarounds and custom patches for MPE/iX issues. Number 8 arrived during the following year. It can be argued HP didn't end all of its MPE/iX support for several years beyond that official Dec. 31, 2010 date.

Some of the more inventive indie support companies have devised ways to use 32 GB of memory for 3000s, too. Ask yours about Number 5.

The last two items seem like real BB-Guns. But they have a chance of helping the community see the 3000 future more clearly, instead of putting its eye out.

A guaranteed ending date for HP's 3000 support is something both homesteaders and migration experts desire. By moving the finish line twice already, HP has kept customers from finishing migrations, or even starting them, according to migration partners.

What's more, the "we're not sure when support is really done" message keeps the 3000's service and support aftermarket in limbo. Customers tell us that they will be using their HP 3000 systems until their business demands they migrate away. HP plans to change its business practices someday for the HP 3000. But nobody knows for certain what day that will be.

That brings us to No. 9, the freedom to re-license your own MPE/iX. HP development on this software ends in one year. That's the end of changes to the operating environment, a genuine Freeze Line for MPE/iX. HP should be able to compete on a level field with the rest of the community. HP Services seems to need those special 3000 licenses.

Number 10? A wish for a long life and continued interest in MPE/iX from the HP 3000 gurus of the community. Someone can bring some these gifts after there's no one inside HP to cares about the 3000 community.

Posted by Ron Seybold at 07:40 AM in History, Homesteading, Newswire Classics | Permalink | Comments (0)

December 21, 2018

Fine Tune: Rebooting a 3000 Remotely

Reboot
I want to provide an option for rebooting an HP 3000 remotely using LDEV 21. How do I do it?  Can I using a modem and landline or an IP address to get to LDEV 21?

Gary Stephens replies

Yes, you can use a modem on the remote support port set to auto answer. This will definitely work. It was more about controlling access to the console remotely. I recall one site that had a modem with a remote call-back to a known inbound number that was effective. Upon answer you were prompted for a U and P that had a dial-back associated with it. Ultimately it's all down to risk and your appetite for change.

Billy Brewer adds

You could hook up a cheap laptop connected to the console port (with a USB to serial converter). Then use TeamViewer or any shared desktop utility you prefer.

Tracy Johnson reports

An older PC with one NIC (you can remote into) and a serial port will also do. These days we just have a PC as the console via a terminal emulator (Minisoft, Reflection, or QCTerm). We use two NICs and just remote into the PC and open a window from there to do our remote reboots.

Mark Ranft notes

All the newer A- and N-Class systems have IP configurable remote console. I assume yours is an older system.

The PC options are excellent. If you have a DTC, you can set up back-to-back DTC switching. You configure a host (outbound) port on the DTC and you choose it by IP and TCP port ID.

Posted by Ron Seybold at 07:27 AM | Permalink | Comments (0)

December 19, 2018

Even DTCs can spark memories for 3000s

DTC to 3000 N-Class config
The Distributed Terminal Controller was a networking device with intelligence that stood between an HP 3000 and a peripheral. We use the past tense to describe the DTC usage for many of the homesteading 3000 sites. In some places, DTCs continue to let 3000s shake hands with other devices.

At TE Connectivity in Hampton Roads, Va. the box works between an N-Class 3000 (the ultimate generation) and an impact printer (of considerably older peerage). Al Nizzardini makes the pair work for the company that employs 3000s across the globe, from North America to China.

"Our DTC 48 with 3-pin ports died on us," Nizzardini said. "We have an impact printer connected to the 48, the only thing that is hanging off that DTC." At first the solution to the blocked connection was to use an even older controller, the DTC16 with modem ports. That would've involved shorting out pins on the DTC 16.

Nizzardini asked and a few veterans answered. Francois Desrochers said Nizzardini would need pins 2, 3 and 7 (send, receive, ground). "You may have to short out 5 and 20," he added. Another combination from Gary Robillard suggested connecting 4 and 5 together and 6, 8, and 20 together. "We always had 2 and 3 crossed—2 to 3 and 3 to 2," he said.

It's been 20 years since HP last released a DTC, something that's still useful for older peripherals. The intel to keep one connected to the latest 3000s is still available in the 3000 community. Old doesn't mean dead when someone remembers the essentials. Nizzardini solved his problem without shorting out pins, just by locating another working DTC 48. MANMAN drives the workflow at TE Connectivity, but the real driver is pros like Nizzardini, helping one another remember.

 

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

December 17, 2018

What to say back to "Your system sucks."

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

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

When a different perspective can respect the investment in MPE/iX, and acknowlege how much less faster or easier an alternative is once you factor in the cost of change — then it might be time to talk futures and alternatives
 
People like the tools that they like. I don’t try to win the PC vs Mac debates anymore. It does annoy me to see a tech expert dismiss something. I have a friend who loves Android and slams iOS, who uses Linux and hoots at Windows. For him, the ability to flip a million software switches and manage his own filesystem is the smartest way to go. The 3000 marketplace started to see this when SAP crept in to try to replace MPE/iX. That's why Kenandy has been able to stand in at a few 3000 sites. Its switches are already set in positions that let work get done.
 
Advocates of the more complex choices usually don’t understand how smart they are in relation to everybody else. I encountered this in our editorial business just a few days ago.

Read "What to say back to "Your system sucks."" in full

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

December 14, 2018

Routers and switches and hubs, oh my!

Lions-and-tigers-and-bears
Editor's Note: Initial HP 3000 hardware networking can be like a trip down a Yellow Brick Road. Here's a primer for the administrator who's wondering if that HP 3000 can link to a network

By Curtis Larsen

Auntie MAU! Auntie MAU! A Twisted Pair! A Twisted Pair!

Once upon a time networks were as flat as the Kansas prairie, and computers on them were a lot like early prairie farmsteads: few and far between, pretty much speaking to each other only when they had to. (“Business looks good again this year.” “Yep.”) Most systems still used dumb terminals, and when speaking to anything outside the LAN, system-to-system modem connections were the way to do it.

A tornado named the Internet suddenly appeared in this landscape. It uprooted established standards and practices, swept aside protocols and speed limitations, and took us into a Technicolor networking landscape very different than what was there before.

Toto, I get the feeling our packets aren’t in Kansas anymore

Smaller companies were tossed before the tornado to eventually land and quickly begin growing again in the new environment. Large companies like IBM, HP, Digital, and Microsoft, who were rooted and established in their own proprietary standards (it sounds like an oxymoron, but it’s true) survived by generally ignoring the howling winds. Eventually, munchkin-like, they all came out to see what the general fuss was about, and found that a house-sized chunk of change (pun intended) had landed.

Networking, and the TCP/IP protocol had truly arrived in style, bringing strange new applications and markets. Serial connections and proprietary networking (“What do you mean we don’t need SNA to connect to the Wichita office anymore?”) gave way to a new kid on the block. And her little dog, too.

Follow the Yellow-Colored-Cable-and-Labeled-at-Both-Ends Road!

So then the HP 3000 managers found themselves sitting in a strange new networking land of strange new networking things. And for some of us, trying to understand the whole of it all — especially in relation to “legacy” system like the HP e3000 — was a little daunting. What are all these networking black boxes we plug the system into, and what do they all do? How can they make life better? (How can they make life worse?) If you’re not sure (or just plain curious) read on.

Read "Routers and switches and hubs, oh my!" in full

Posted by Ron Seybold at 07:02 PM in Hidden Value, Newswire Classics | Permalink | Comments (0)

December 12, 2018

Source code for MPE/iX: Security, by now

Blanket-Ad
Ten years ago this week the 3000 community was in a state of anticipation about MPE/iX. HP had an offer it was preparing that would give select vendors the right to use the operating system code. The vendors would have a reference-use-only license agreement for MPE/iX. No one knew whether the source would have any value, said Adager CEO Rene Woc.

Adager, the company whose 3000 products are so omnipresent they held a spot on the Hewlett-Packard corporate price list, believed there was potential for independent support and development vendors. What was far less certain was how far HP would let source go to solve problems for the 3000 community.

"Source code is important whenever these kinds of [vendors] have support from HP, which most of them do," he said in that month of 2008. But HP engineers can look at source, just as third parties will do, "and the answers won't come instantaneously. In the meantime, you have to get your business back on track, and I think that's what the customer is eventually interested in. It will be nice to have that additional [source code] resource — especially in the sense that it will not be lost to the community."

There was a chance that HP's source licensing terms would be too restrictive, "to the point where you say that you are better off not knowing, because then we're free to use all the methods we've worked with while we didn't have source." After getting a license to source, Woc added, "you might have to prove that you got your knowledge through a difference source than HP's source code. We will see."

That sort of proof has never been required. Not in a public display, at least. Source code, held by vendors such as Pivital Solutions and others, has been a useful component in workarounds and fixes. HP never gave the community the right to modify MPE/iX. This turned out to be a good thing, as it kept the 3000s stable and made support a manageable business for application vendors.

There was also the wisdom that the resource of HP's code would have to prove itself. At least it held a chance for rescue and repair.

The source code "is probably a security blanket," Woc said in 2008. "In that respect, it's good that it will be available, that they're starting to offer some things. We'll have to see what kind of conditions HP will offer in their license agreements." 

Having source access though a license did not automatically make license holders better providers of products and services, he added. "You cannot assume, even with good source code readers, that the solutions will pop up," he said. "A lot of the problems we see these days are due to interactions between products. So the benefit for the customer would be based more on the troubleshooting skills that an organization can provide."

"The basic resources [of source] won't make things better by themselves," Woc said. "It's a matter of troubleshooting." 

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

December 10, 2018

HP's 3000 boxes step closer to solid storage

SCSI2SD-V6-RevF-2T
Almost two years ago, an expert in HP's 3000 systems was working to use solid state disks (SSD) with the computer. John Zoltak was trying to link the server to microSD cards late in 2016. He checked in with us this week to report success on the project.

SSD on 3000 hardware from HP has been a dream for several decades. Imperial Computer had a solid state unit early in the 1990s that held a promise of faster IO transfer on MPE/iX. The cost was astounding compared to moving media and the capacity was a fraction of spinning disk drives'. Much later, SSD has become something of a desktop standard and is an active choice in enterprise servers, too.

The MPE/iX hardware from HP -- to us, something called an HP 3000 -- wanted to play from SSD, too. In his prior report, Zoltak was 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. Now there's a V6 edition of SCSI2SD, a combination of hardware and software that delivers SD storage to HP's 3000 iron.

The combination now works beautifully, said Zoltak, who's working at Fives North American Combustion in Cleveland, Ohio. "You want the V6 boards," he said. "The V5's are much slower. The V6 takes a full size SSD card and up to 128GB has been tested." Michael McMaster, the inventor based in Australia, has engineered the latest version of his product "as a complete redesign for the V6 boards, which use a completely different microcontroller." The device is for sale online at Intertial Computing. Today's price is $105 including 16GB of microSD.

The product employs a SCSI-2 Narrow 8-bit 50-pin connector. It does SCSI FAST10 synchronous transfers at 10MB/second. Zoltak is reaching way back into the HP 3000 hardware closet to test. He's attached the SCSI2SD to a Series 917.

"I have the board sitting on top of the system with a cable around to the back on the same SCSI as the 917's DAT and DLT drives. I did a reconfigure and a restore to the SSD. Seems to be fairly quick. While restore was running I used HP Glance and saw that the disk was doing about 65-70 IO's per second. This is not as fast as the Nike array it came off of, but then it was on a differential wide SCSI."

The bigger benefit is that the HP MPE/iX iron can rely on SSD instead of moving media. Disks are among the leading culprits in HP's 3000 failures in 2018. Tape is a close second. Storing and moving bits gets complicated while using the hardware that HP certified for storage with 3000s than a decade ago.

Newer storage reduces the risk of homesteading. This is one of the benefits of using a virtualized 3000, too.

Read "HP's 3000 boxes step closer to solid storage" in full

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

December 07, 2018

Memory and Disk Rules for Performance

Concentration
NewsWire Classic

By Jeff Kubler

You need to get management support for your efforts to keep your systems performing at their best. Memory and disk are two components of your performance picture under MPE/iX. 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.

CPU used to manage 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.

Page Faults per Second: A Page Fault occurs each time a memory object is not found in memory. The threshold for the number of Page Faults per second that can be incurred before a memory problem is indicated varies with the size and the power of the CPU. Larger machines can handle more Page Faults per second while a smaller box will encounter problems with far fewer.

An exceptional number of Page Faults should never be used as the sole indicator of memory problems but when observed should be tested with the memory manager percentage. If both agree, you have a memory shortage. There are some strange things that I have observed with Page Faults, so it does not stand alone as an indicator of memory shortage.

The number of Page Faults per second and the amount of CPU needed to manage Memory are always evaluated in conjunction with each other. That is to say the high Page Fault Rate will not be considered a problem if the Memory Manager Percentage is not above 4 percent.

Read "Memory and Disk Rules for Performance" in full

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

December 05, 2018

One Alternative to $1 Million of 3000 Costs

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

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

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

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

Read "One Alternative to $1 Million of 3000 Costs" in full

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

December 03, 2018

HP 3000 dream tracks close to virtualization

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

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

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

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

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

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

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

Read "HP 3000 dream tracks close to virtualization" in full

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

November 28, 2018

HP show offers something to Discover

HP Discover Madrid
Early this morning the new-ish HP, Hewlett Packard Enterprise, was connecting with its customers in an old-school way. The HPE Discover conference has been unreeling since Monday and today was the final day of three in Madrid. These kinds of events were once so remote it took a week or more to learn what was said. Now there's a live-streamed component the vendor mounts on browsers and over phones anywhere.

Whether there's anything worth a live stream depends on the C-level of the viewer. How to Tame Your Hybrid Cloud and The Future and Ethics of AI might be best absorbed by a CTO or some other CxO. On-the-ground solutions don't show up much in HP's livestreams. The most practical lessons usually came during sessions of the 1980s and '90s held in rooms where indie software vendors delivered chalk talks. Down on the expo floor the instruction was even more focused. A manager could get advisories on their specific situations.

That's part of what Stromasys is doing at Madrid this week. An application demo isn't a novel experience most of the time. Making commonplace hardware behave like proprietary systems can still be a revelation. Over in Hall 9 this morning, managers at Discover will see demos of a Charon solution that's got more than 7,000 installed sites, according to Stomasys.

More of those 7,000 sites are MPE/iX emulations than ever. The demos will operate on both on-premise servers as well as from the cloud. Stromasys likes to remind the world that its Charon emulates VAX, Alpha, and SPARC systems as well as the HP 3000. The vendor does this reminding in person at conferences in places like Madrid, like the Middle East, and it demonstrates its virtualization at VM World in the US, too.

Conferences like HPE Discover were once run by user organizations and funded by booth sales. It was a personal business in those days before the Web gave us everything everywhere. Today the personalization arrives at vendor booths with demonstrations for those who've traveled to ask questions. Having an expert on hand to answer them shows a committment to keeping new solutions on display.

Posted by Ron Seybold at 04:30 AM in Homesteading, News Outta HP, Newsmakers | Permalink | Comments (0)

Search