OpenVMS 7.2-1H1 (codenamed Penguin)
A fairly anonymous hardware release (designated by the H), but was it.
Angus Durie

A fairly anonymous hardware release (designated by the H), but was it. Compaq announced the Wildfire family of servers in 2000, supporting both Tru64 and OpenVMS. The key innovative technology of this hardware were the Quad Building Blocks (QBBs), 4 closely couple processors designed to improve speed for multi-processor applications; and they did perform well for applications that needed no more than 4 processors. The problem came when QBBs needed to communicate with each other, because communications between QBBs was nowhere near as fast as that inside the QBB. The net result was that applications using more than 4 processors slowed down, and that was a problem for some of the larger OpenVMS users.
Cut a long story short, Rich Marcello, who was VP of the OpenVMS group at the time, realised the problem early on and put an internal team together to fix the problem. So essentially the software guys had to fix the hardware’s short comings, and fix it they did. They made changes to the OS on a daily basis, testing each one overnight. At that time the OpenVMS team were renowned for the quality testing and control however this was quite a lengthy process for a new version of the OS, so to get round that obstacle the team designated the release as a hardware release, which meant a shorter testing cycle and therefore it could be released to customers in a timelier manner. The fixes worked and OpenVMS survived until the Marvel family of servers were released in 2003 (Mesh architecture, more dynamic than QBBs).
Little know fact. T4 (Tom’s Terrific Timeline Tool) was developed by Tom Cafarella for use by the team to test the performance of the new versions of 7.2-1H1.
More articles
View all
The Rdb Conundrum and Ways to Solve It
Oracle's decision to end Rdb support on OpenVMS X86 has been on the cards for years. With the Malmö Bootcamp 2026 bringing the conversation into the open, we look at the options available to Rdb customers who want to plan their next move.

Monitoring OpenVMS Servers with Modern Tools
OpenVMS has long been a cornerstone of mission-critical computing. But as the pool of skilled engineers shrinks, visibility into how these systems are performing has never been more important.

Note from an old DEC-hand
Ken Olsen once called VMS the best operating system for business. Technically, he had a point. The case for OpenVMS is rarely lost on engineering - only on marketing.
Comments are reviewed before they appear publicly.
Comments (0)
No comments yet. Be the first to add one.