« May 2018 | Main

June 13, 2018

New DL325 serves fresh emulation muscle

DL385-Whiteboard
Hewlett-Packard Enterprise has reintroduced its ProLiant workhorse, talking up the server in connection with next week's HP Discover conference in Las Vegas. The DL325, when it ships in July, will be a newer and more powerful model of the DL380 server — one suitable for powering a virtualized HP 3000 driven by the Stromasys Charon HPA system. The DL325 is a single socket system, a design that's disrupting the server marketplace.

HP has posted one of its whiteboard walk-throughs on YouTube to cover some of the DL325 advantages. There's also a performance comparison for the system, ranked against a Lenovo alternative as well as an energy efficiency measure against a server from Dell. 3000s never got such industry benchmarks for performance.

But HP 3000s once got this kind of spec treatment from Hewlett-Packard. The 3000 division's product manager Dave Snow gave such product talks, holding a microphone with a long cord that he would coil and uncoil as he spoke. With his pleasant Texas drawl, Snow sounded like he was corralling the future of the hardware. He spoke in that era when "feeds and speeds" sometimes could lure an audience "into the weeds." Breakdowns like the one below once lauded the new PCI-based 3000 hardware.

DL385-Chassis-Overview
The ProLiant line has long had the capability to put Linux into the datacenter. Linux is the cradle that holds the Charon software to put MPE/iX into hardware like the 325. The DL325 (click above for a larger view) is a single-processor model in the company's Gen10 line, adding horsepower for an application that's always hungry for more CPU: virtualization. The DL325 gets its zip from the EPYC chip, AMD's processor built to the x86 standards. EPYC designs mean the chip only needs to run at 2.3 GHz, because the system's got 32 cores per processor.

"This server should deliver great price performance for virtualized infrastructure while driving down costs," wrote analyst Matt Kimball in Forbes.

Even way back in 2014, the DL380 ProLiant server was driving virtualized 3000 systems, fired by a 3.44 GHz chip. That was plenty fast enough to handle the combo of Linux, VMWare and the Stromasys Charon 3000 emulator. The DL385 was 17 inches x 29 by 3.5, just 2U in size. HPE's shrunk the power down to a 1U chassis for the DL325.

During the era when the DL380 was first being matched to virtualization work, Stromasys tech experts said that CPUs of more than 3 GHz were the best fit for VMWare and Charon. Putting MPE/iX onto such a compact AMD EPYC-based machine is a long way from the earliest year of the OS. In 1974, MPE would only fit on a 12,000 BTU server, the HP3000 System CX

The newest Generation 10 box retails for one-tenth of the cost of that CX server. The plodding CX was all that ASK Computer Systems had to work with 44 years ago when it built MANMAN. HP needed to assist ASK just to bring MPE into reliable service on the CX. "It didn’t work worth shit, it’s true," said Marty Browne of ASK at a software symposium in 2008. "But we got free HP computer time."

In the current IT architecture, the feeds and speeds of individual systems are usually in the weeds. A vendor like Stromasys though, working as it does to implement Charon in every customer site, cares about the speeds.

Employing hardware that's newer, like the DL325, brings support to block cutting-edge attacks on the datacenter. HP said this server is not exposed to this year's Masterkey CPU vulnerability, because it uses the HPE Silicon Root of Trust functionality. Root of Trust, HPE says, is "a unique link between the HPE Integrated Light Out (iLO) silicon and the iLO firmware to ensure servers do not execute compromised firmware code. The Root of Trust is connected to the AMD Secure Processor in AMD's EPYC System on a Chip so that the AMD Secure Processor can validate the HPE firmware before the server is allowed to boot."

With exploits like Masterkey on the march this year, HPE has released a patch to update the system ROM with a patch for Linux anyway to mitigate the vulnerability. Current hardware gets that kind of attention from a vendor.

06:13 PM in History, Homesteading, News Outta HP | Permalink | Comments (0)

June 11, 2018

Making a 3000 Reunion a Personal Affair

With the Duke of Edinburgh pub set aside for June 23d's 3000 reunion, this year's event has now become even more personal. Orly Larson, the affable creator of Hewlett-Packard songs about the 3000, is holding a garden party at his home near the old HP campus on Friday the 22d.

HP 50th Anniversary Song

Lyrics to Orly's 50th Anniversary HP song

Reunion kingpin Dave Wiseman sent out a notice to the community, asking "can you join us the previous day, Friday, June 22nd for a visit to Valhalla for a social get together late afternoon/evening?"

For those of you who don’t know, Valhalla in Norse mythology is a majestic, enormous hall where Viking heroes slain in battle are received (also known as Viking Heaven). Located in Asgard, ruled over by the god Odin, and is used for partying. Or, to put it another way, Orly Larson’s back yard.

Complete with swimming pool, hot tub, dart boards, table tennis, bean bag toss and a sound stage (not really). This yard is the same place Orly had a pre-San Francisco INTEREX ’89 Conference dinner party for some of the 75-plus HP 3000 users who helped him sing HP and Interex songs together at local, regional and international conferences.

The plan is to chip in for some beers and pizza and chill out.

Orly at Reunion
Orly Larson

Pizza and beers, chilling out in an colleague's backyard and catching up on what's happened to everyone since we last worked together. It's a very personal aspect to a reunion that may seem like a memorial to some. To register an RSVP and a pizza preference, contact Wiseman at davebwiseman@googlemail.com.

To RSVP for the afternoon at the Duke, head over to the webpage of the event's Jot signup form. You might have chip in for the pizza, but the drinks at the Duke are on CAMUS, the MANMAN user group, for at least the first few rounds.

By the late 1989, when the songs were being crooned by customers at user group meetings, the greatest champion of that edgy IMAGE database was Larson, who wrote and led the music a cappella. An SQL interface had been added to IMAGE. Paul Edwards reports that "that we, employees and customers who called ourselves The Sequals, used the HP song book all over the world to sing with Orly." Singing about the HP 3000 became a tradition. HP marketeer George Stachnik extended the singing with a guitar and eventually a band at user group events. Larson led his choruses a capella—complete with ensemble kicks at the close of the song New Wave.

10:09 PM in History, Homesteading | Permalink | Comments (0)

June 08, 2018

Fine-Tune: Making the 3000's ports report

I have a port in an HP 3000 and I want to know the application that is currently using that port. Is there any command that can show me the applications accessing a particular port?

Kevin Miller replied:

:sockinfo.net.sys

Enter ‘c’ for ‘call sockets.’ Listeners are shown in port order.

The port for telnet on our 3000 is set to a different value then 23, but it is set to 23 on our HP Unix server. When I try to telnet from the 3000 to HP-UX I get the following message: Trying... telnet: Unable to connect to remote host. If I switch the port for telnet to 23 on the 3000, it works great.

My question is: Can I run telnet on two different ports on either box so that I can maintain my non-standard port on the 3000, but still allow telnet to run between the two boxes? If not, is there another way to make this work?

Jeff Kell replied:

Just ‘telnet your.3000.name nnn’ where ‘nnn’ is your ‘nonstandard’ port.

How do I point network printer configurations to specific ports on (external) multi-port JetDirect (or equivalent) boxes?

Gilles Schipper replied:

You need to add the tcp_port_number option, in NPCONFIG, as follows:

(network_address = 128.250.232.40 tcp_port_number = 9100) # for port 1
(network_address = 128.250.232.40 tcp_port_number = 9101) # for port 2
(network_address = 128.250.232.40 tcp_port_number = 9102) # for port 3

(Please note that everything on each line after and including the “#” represents a comment.)

My HP 3000 is set up for full access to the Internet. The telnet connection works fine, but I also see that VT-MGR also works. I know that inetdsec is used for restricting access for ip, http, ftp and so on. Is there something in NMMGR to restrict VT-MGR access, or do you use inetdsec for that also?

Chris Bartram replied:

Just an option logon UDC that checks the CIVars set for the IP address and hostname of the originator.

We’ve got a DLT4000 tape drive I’d like to connect to a Series 957 and use them for database, incremental, and full backups. Can I simply hook a DLT4000 drive to the SE-SCSI port on the MFIO card, set its SCSI address, and add the device as an HPC1521B?

Gilles Schipper replied:

It should be no problem at all. The DLT4000 SE SCSI device can also be utilized as a boot device on the 957. You should use the device ID of DLT4000 and not HPC1521B. You should consider using the device ID of HPC1521B as a workaround to any restore problem. It would be best to use device ID DLT4000 and test to ensure good restore performance, and only resort to device ID HPC1521B if the restore speed is NOT satisfactory.

08:52 PM in Hidden Value, Homesteading | Permalink | Comments (0)

June 06, 2018

Wayback: HP's 3000 Conference Sign-off

HP's June months have been populated by nationwide conferences for more than a decade. Ten years ago in June marked the last known appearance of Hewlett-Packard's 3000 experts at the HP Technology Forum show in Las Vegas. It was an era marked by the soaring expectations from CEO Mark Hurd and the soon-to-plummet economy crashing around the American lending and banking markets. HP was emptying its tech wallet at a show that would soon be called HP Discover instead of a Technology Forum.

HP had a meeting for 3000 customers at that 2008 show, the final expression of support for the owners who launched HP's enterprise business computing prowess. Jennie Hou was in the final year of managing the 3000 group at HP. The vendor had a history of awarding one community member — people like Alfredo Rego, or Stan Sieler — with a Contributor of the Year Award. The 2008 award was renamed a Certificate of Appreciation and given to the full 3000 community. Being thanked, as HP retired the customers, was a sign of HP's final sign-off.

Appreciation certificate
The 2008 edition was the last public event where HP presented news about the platform. It was the last year when the server owners could employ the services of HP's labs. HP's Alvina Nishimoto, who'd been leading the information parade for third party tools and migration success stories, gave an outstanding contributor award of sorts at an e3000 roadmap meeting. The award shown in the slide above had a commemorative tone about it, like a fond farewell to the days when something new was part of the HP message to 3000 attendees.

In that June, the new Right to Use licenses were proving more popular than HP first imagined. The licensing product placed on the price list for 2007 let customers upgrade their license level on used systems. Of course, it only applied to the 3000s designed before 2001. It says something when servers almost a decade old could be a popular upgrade item in datacenter.

Just two HP speakers addressed the 3000 at the conference — Nishimoto and Jim Hawkins, the latter of whom spoke for five minutes at the end of the OpenMPE update. The Tech Forum had become a great place to learn about technology that HP would never put into a 3000.

I asked Hou about HP's participation in the conference and what I should expect in the years to come. The vendor would only discuss migration by 2008, after completing the final PowerPatch and delivering some whitepapers to the community.

HP was saying so long, and thanks for the fish.

The e3000 community has always been and will continue to be an interesting place.  It truly is one of a kind. This year, at Alvina's talk, HP will thank every e3000 partner and customer. HP recognizes that the e3000 community wouldn't be what it is without so many people's ongoing involvement and contributions. This also includes all your dedication in bringing the e3000 news to the user community over the past decades.

Hou was gracious in acknowledging the role we'd played up to that point a decade ago. Neither one of us knew the Newswire would still be tracking the fate and future of MPE/iX, ten years later.

07:49 PM in History, Homesteading, News Outta HP | Permalink | Comments (0)

June 04, 2018

Being first is about serving customer needs

During the 1990s the 3000 managers at HP started an enterprise revolution. Instead of creating computing systems built upon marketing research and technical breakthroughs, the division devoted to MPE/iX started a movement it called Customer First. It meant that to develop something for a 3000 owner, management had to be listening to the customer first, instead deferring to the business development mavens at the vendor.

HP got in close enough touch with its customers that it sent employees from the factory, as it called its system development labs, out to customer sites to interview the customers. HP's Unix division took note and started to follow suit.

Customer First doesn't sound that revolutionary today, but it put the 3000 leadership in the spotlight at HP's enterprise operations. In the 1990s HP was more of a computing company than anything else. Printers were important but computing was still earning the highest profits and paying for everything else. HP understood that while proprietary computer environments differ, they've got one thing in common: the customers who know what they need better than the vendors themselves.

Stromasys is picking up the concept with every quarter it sells products to support legacy environments like MPE/iX and VMS. Sustaining legacy investments makes sense when the system delivers what's needed. Customers needs come first.

Sue_Skonetski"I do think that customers know what they want and need," said Stromasys' Sue Skonetski, "and no one else knows their mind as well. One of the things I am looking forward to at Stromasys is working with customers from so many different areas. Hopefully I will be able to help when questions come up, as well as post information as I see it."

Harry-sterling-realtorHarry Sterling, who was the general manager at the 3000 group in those revolutionary time, passed praise on to Skonetski. "Taking care of customers based on their needs, and not the sole ideals of engineers, is key—and from your remarks, I know you believe that." Key concepts can get a revival just as surely as a good Broadway play gets another production after enough time has passed.

Customer First got its first mission in 1991. After 3000 customers expressed their displeasure at HP's waning emphasis on IMAGE, CSY had to respond with improvements. Jim Sartain of the R&D lab was directly responsible for HP’s offering of an SQL interface for IMAGE, the first advance to signal the division's commitment to a Customer First strategy. Sartain worked with a revived IMAGE special-interest group to revitalize the database.

Gathering voices from differing platform bases was once important to HP. The vendor embraced the idea so much it published a Customer First Times, a PDF document that carried information about HP 3000s, along with HP 9000, OpenVMS and Itanium-based market products. It was the first assembly of the legacy ecosystem of HP.

In 2004 HP closed up Customer First Times. That was the first full year HP didn't sell a new HP 3000. The OpenVMS community was by then fully assimilated into HP's product plans, receiving the technology shift it needed to get the OS onto the Itanium computers.

Customer First was a mantra that the CSY division promoted to the rest of HP's server businesses. The legacy systems of VMS, MPE/iX, and even Sun are still in production mode at companies that know what they need. Assembling them to hear their voices is what Customer First is all about—as well as posting information about what they all need.

09:56 PM in History, Homesteading, Newsmakers | Permalink | Comments (0)

June 01, 2018

Recovering a 3000 password: some ideas

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

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

If your operator can log onto operator.sys:

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

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

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

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

09:57 PM in Hidden Value, Migration | Permalink | Comments (0)