CHARON Guest Utilities for OpenVMS
Table of Contents
General Description
The "CHARON Guest Utilities for OpenVMS" (CHARONCP) package contains several utilities for managing virtual tapes, changing the emulator speed and creating useful definitions for that operations.
This set of utilities is located in the "charoncp013.vdisk" disk file in the "C:\Program Files\CHARON\Virtual Disk Images\Tape utilities package".
Supported OpenVMS versions: OpenVMS 6.1 and above.
In case of OpenVMS upgrade, CHARONCP will have to be re-installed.
Installation
Specify this image in the CHARON configuration file, boot from the system disk and mount the disk with the following OpenVMS command:
|
Issue the following commands to install the package:
|
Select all the components included to the package:
|
Proceed with installation using all the default options.
Once the installation is completed, add the following line to the "SYS$STARTUP:SYSTARTUP_VMS.COM" file for the package to be loaded automatically at system startup::
|
After that the package will be loaded automatically on startup.
Performance optimization
CHARON takes 100% of host CPU even in case of idle state of guest OpenVMS operating system. To get rid of such resources consumption there is a specific option provided by CHARON Guest Utilities - "idle" mode.
To load the OpenVMS idle loop detection software, use:
|
This allows CHARON to detect when the emulated CPU(s) are idle and use the host power saving instructions to reduce power usage.
To unload the OpenVMS idle loop detection software, use:
|
Adjusting emulator's speed
CHARON speed can be adjusted using these commands.
To increase the emulator speed by the specified number of steps, use:
|
© Stromasys, 1999-2025 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.
Need fast, reliable migration? We have done it countless times. Talk to an expert
Hello @Bruno Miretti (Deactivated). Frank Mueller (because he for some reason used the AXP/VAX Baremetal documenation for this) asked me to update the documentation to state that there is a problem with the full path name in the configuration. He wrote:
Quote: In the config file, the container name must be ".vtape" without the path.
set PKA container[600] = ".vtape" removable[600] = true (Works fine)
set PKA container[600] = "D:\vtapes\mka600.vtape" removable[600] = true (fails with badfilename errors)
I don’t know if this is a bug or a special situation he had. But since he mentioned he worked with you, I thought, I add this comment here….