VMS and Virtual Systems
Whether you call it OpenVMS, VAX/VMS, or just "VMS", this operating system is still being developed by Hewlett-Packard (HP). The latest version is V8.4. HP promised that there would be an equivalent release for Alpha some time after a release for the Integrity server. VAX development stopped at V7.3.
These facts mean that your investment in software and licenses needs to be protected! All hardware will fail, it's just a question of when. By creating a virtual system, you can keep moving forward to the latest hardware and not have to change a thing. And that new hardware means that your virtual system will keep getting faster as the newest hardware keeps getting faster.
The CHARON-VAX and CHARON-AXP products run VMS, creating the virtual system you need.
Both of these products pass the hardware test suites to verify that they're a real VAX or Alpha. Some other things you need:
- DEC/Compaq/HP software licenses can be transferred to the emulated system -- your license investment is protected.
- HP OpenVMS software support is available when running on HP hardware.
- Oracle RDB licenses can be transferred to the emulated system. Oracle does all its VAX development with CHARON-VAX! (PowerPoint)
- Q-bus hardware can be directly supported, or completely replaced.
- Many licenses from companies that are no longer in existence can be migrated with QCI's System Identification Change product.
- Oracle RDB
- System 1032
- Ross System's UserBase
- All DEC compilers (C, Fortran, Macro, etc.)
To simplify migration, Quayle Consulting has a set of DCL scripts to run BACKUP on each disk and push the savesets across the network using TCP/IP or DECnet. The documentation of the full set of scripts are at stanq.com/Migration-Tools