Quayle Consulting now sells CRISP!

CRISP product, with full names of CRISP/32 and CRISP/64, is factory-automation software running under the OpenVMS (“VMS”) operating system.  The “/32” version runs on VAX systems running VAX/VMS or OpenVMS.  The “/64” runs in 64-bit mode on AlphaServer and Integrity Server systems.  Quayle Consulting has been supporting the CRISP source code for several years, and migrated it from the 32-bit VAX to the 64-bit AlphaServer and Integrity servers.

Quayle Consulting Inc. has just reached an agreement with CRISP Automation to sell CRISP licenses and CRISP support contracts.  For more information, please contact Quayle Consulting at www.stanq.com or post a comment on this page.

Happy Birthday, VMS!

33 years ago today, the OpenVMS (formerly, VAX/VMS) operating system was announced.  And it’s still going strong, with version 8.4 just released for the Intel Itanium processor used in the HP Integrity server line, and the Alpha processor, used in the HP AlphaServer product line.

Think about it the next time you send a text message — chances are, it was handled by VMS!

VMS — when “legacy” means “stuff that just works”.

Hello from New Hampshire — Birthplace of VMS

Hello from Nashua NH. This week is the OpenVMS Advanced Technical Bootcamp. We started at 7:45 AM this morning, and went until 9:15 this evening.

The Bootcamp is held in Nashua because that was where VMS was originally developed. Unfortunately, Hewlett Packard canned the entire VMS development team a couple of years ago and moved development to India. *sigh*

I directed a session titled “Risk vs. Benefits of VAX/Alpha Emulation”. I’ll be doing it again Thursday afternoon. Here’s a link in case you can’t drop by and see it in person…

CHARON-VAX and CHARON-AXP supported on VMware

The CHARON product line is now supported in VMware on top of a Windows instance. Versions supported are:

  • CHARON-VAX version 3.4 build 110 and later
  • CHARON-AXP/4100/DS/ES/GS version 2.3 Build 108 and later
  • CHARON-AXP/SMA and CHARON-AXP/SMA Plus version 2.1.26 and later

There are some requirements:

  • The CHARON virtual machine should have exclusive access to the CHARON USB license dongle. It could be achieved with a third party product, for example: http://www.digi.com/products/usb/anywhereusb.jsp#overview.
  • The CHARON virtual machine should meet standard CHARON hardware requirements in terms of Windows OS version and patch level, CPU, RAM, storage, etc.
  • On any physical server hosting a CHARON virtual machine, the total number of VMware vCPUs allocated to all active Virtual Machines should not exceed the number of host physical CPU cores. The same requirement is applicable to RAM: total vRAM allocated to active VMs must not exceed total host RAM.

Some product features are not supported:

  • The Pass Through mode in CHARON-AXP/SMA and CHARON-AXP/SMA Plus
  • Direct device access

Please note that the supported CHARON-VAX version requires a HASP dongle. The older Hardlock dongle can be swapped at no charge for customers under support.

Hello from VMS Bootcamp!

A big part of the Bootcamp is “VMS Magic”. Anyone can come up and give a story about anything related to VMS. The best story wins a prize — the first-place winner this year showed how he booted VMS on a palmtop computer.

But this post is about Ron Kaledas of CareTech Solutions. He works in a typical environment — VMS, Linux, Windows. At every opportunity, he pointed out the benefits of OpenVMS. His cluster had been up for 5 years continuously without interruption.

Clustered VMS systems can be upgraded one at a time in a “rolling reboot” without affecting the cluster as a whole. Hard to believe that this technology has been available for over 20 years, and still isn’t available on any other platform.

Anyway, his part of the data center was scheduled for a complete shutdown to upgrade the un-interruptible power supply (UPS). But he wanted to keep his cluster alive through the shutdown.

So, he downloaded PersonalAlpha, a free version of the CHARON-Alpha emulator. He loaded it on a laptop, installed VMS, joined the cluster, and shut down all the other nodes.

After an hour or so, the power was restored, and he started the other systems back up. He then had his laptop exit the cluster without impacting any users.

His uptime? 5+ years and counting!