HP has posted this neat video. Look for Acision under Telecommunications,
I’ve upgraded the blog to WordPress 2.3.1. It was almost painless!
Soon, Quayle Consulting will be 15 years old. Funny how VMS has been around exactly twice as long…
My first job was working at Fairfield Engineering. They mostly built conveyors for coal-fired power plants. The DEC PDP-11 was used as a controller for many of those systems. We had a VAX 11/780, running VMS V3.2, but it was too expensive to consider using as an “embedded” controller. Also, the VAX was huge compared to the single-board PDP-11’s.
I moved to a company making welding robots based on PDP-11’s. After a month, it went under due to poor management. It disappeared so completely that the US government couldn’t find a trace of it some years later when processing a security clearance for me.
I spent six years away from DEC stuff, working at Battelle Memorial Institute. Three Mile Island was good to me — there was a flood of government bucks to model nuclear reactor accidents (in Fortran, on CDC mainframes). When that dried up, I moved into an experimental group (and got to learn Unix on a Masscomp computer). But, just when it seemed like I’d be there forever, I got laid off. That’s when I realized that I was responsible for own life.
I eventually landed a job at CRISP Automation, doing Motorola 68000 programming. The embedded system talked over Ethernet with a VAX system. I remember VMS 4.7, and the transition to VMS 5.0. Those were fun days, working with a group of people who loved VMS and were razor-sharp developers.
CRISP Automation got bought by Square D Company. All of a sudden, we were the automation group of a company that everyone’s heard of. Of course, it couldn’t last. Square D got bought in a hostile takeover by Schneider. They made it very clear — they had their own automation group back in France, and they didn’t need one in the USA.
Before the takeover, Square D had put in a severance package of one month’s pay for every year of service (called a “poison pill” or “tin parachute”). So, when the VP’s came to explain the “future”, I jumped up and volunteered to be the first one to go.
With 5 months of pay in the bank, I started Quayle Consulting on September 16, 1992. I remember that date because I was able to be at my son’s first birthday photo shoot at Olan Mills on September 18th. Ordinarily, I wouldn’t have been able to go because I’d be at work.
Quayle Consulting became a corporation in 2001 — the bigger the business, the more they insist on only working with other corporations. Silly, I know, but the paperwork was cheap and easy.
Things have been up and down. For me, “consultant” doesn’t mean “between jobs”. I wouldn’t trade this “job” for any other!
There’s a legend about a company accidentally walling-off a VAX server, and it continued to hum along.
It’s no longer a legend — I have found an eyewitness!
Keating Floyd (Keating_floyd-at-onebox-dot-com) is a consultant. He was visiting B&W Tobacco in Macon, Georgia in 1998 or so. The client was ripping out drywall, and discovered a VAX that no one knew about. It was still running and serving clients.
Sorry — no pictures available. And he didn’t know what application was running. But, hey, it was running VMS, for sure!
In May, HP built two data centers and blew one up to demonstrate disaster tolerance. VMS recovered first, in less than 14 seconds. The associated document said that it could have been adjusted to be less than 5 seconds.
Neat movie: www.hp.com/go/DisasterProof
Document: http://h71028.www7.hp.com/ERC/downloads/4AA1-3405ENW.pdf (PDF)
At a high-tech ballistics center managed by National Technical Systems
in Camden, Arkansas, HP simulated a gas leak using real explosives that
resulted in a very real explosion and datacenter destruction.
What was blown up? Products from the entire spectrum of HP products,
including HP servers, HP StorageWorks products, HP Software and HP
Procurve networking products running in five operating
environments-HP-UX, HP OpenVMS, HP NonStop, Red Hat Enterprise Linux and Microsoft(r) Windows Server 2003.
Who said that computer geeks don’t have a sense of humor?
Some religious organizations use VMS. But that’s not what I’m talking about.
Some people in the VMS community believe that VMS is the only operating system that’s worth using. And that any Microsoft product needs to be avoided like the plague.
Windows deserves its reputation. The VMS community sees it clearly, because many of Microsoft’s problems are the same ones that we solved 20+ years ago. A definition of insanity is doing the same thing over and over and expecting different results. It also takes the highest level of cognitive development to learn from other people’s mistakes.
The world has lots of platforms: Windows, Linux, Macintosh, Unix (HP-UX, Solaris, Tru64, etc.). And this list is by no means exhaustive — there are embedded systems and mainframes, DOS and CP/M. And, of course, VMS.
Right here at home, I’m using two flavors of Windows, 3 different distributions of Linux, and 3 different VMS platforms (VAX, Alpha, and Itanium).
My clients expect that I know something about the platforms they use, so I’m not only HP certified on VMS, but also Tru64 UNIX. And Red Hat certified. And CompTIA Server+ certified. My IBM mainframe experience is old (very old), but I did live on MVS for a few years.
I recommend against working with anyone who says that there is only One True Operating System. Someday he’ll be a dinosaur. And look how they turned out.
Each year, at the OpenVMS Advanced Technical Bootcamp, there’s an awards night. Members of the VMS community are recognized for their contribution to advancement of VMS.
Ian Miller was given the John Wisniewski Spirit Award. John was a person who loved and lived VMS. The award is given each year for the person who shows the most spirit, passion, integrity and excitement about OpenVMS. Congratulations, Ian!
There were quite a few other winners. See the OpenVMS.org story for all the details.
Frequently, when I post things to comp.os.vms or the HP ITRC site, I add a disclaimer.
It’s not that I have no shame (got plenty already, thanks), but I want people to know that one avenue to solving their problem is by buying CHARON-VAX or CHARON-AXP and migrating their application to it.
Give a 2-year-old a hammer, and everything needs pounding. I have more tools than that. I only recommend it if it makes sense.