VSI Console Management for OpenVMS
Release Notes
- Operating System:
- VSI OpenVMS x86-64 Version 9.2-2 or higher
- Software Version:
- VSI Console Management for OpenVMS Version 3.1
1. Preface
1.1. About VSI
VMS Software, Inc. (VSI) is an independent software company licensed by Hewlett Packard Enterprise to develop and support the OpenVMS operating system.
1.2. OpenVMS Documentation
The full VSI OpenVMS documentation set can be found on the VMS Software Documentation webpage at https://docs.vmssoftware.com.
1.3. VSI Encourages Your Comments
You may send comments or suggestions regarding this manual or any VSI document by sending electronic mail to the following Internet address: <docinfo@vmssoftware.com>. Users who have VSI OpenVMS support contracts through VSI can contact <support@vmssoftware.com> for help with this product.
2. Release 3.1 Features
This section contains the following topics:
2.1. Operating System Support
VSI Console Management for OpenVMS V3.1 supports VSI OpenVMS x86-64 V9.2-2 or higher.
2.2. System Requirements
The following requirements must be met or exceeded for VSI Console Management for OpenVMS V3.1 to install and run correctly:
TCP/IP Stack Requirements
Console Manager Requirements
2.2.1. TCP/IP Stack Requirements
The supported TCP/IP stack version is VSI TCP/IP Services for OpenVMS x86-64 Version V6.0.
2.2.2. Console Manager Requirements
The OpenVMS disk space requirements are as follows:
To install Console Manager, a minimum of 100,000 blocks of free disk space is required.
To run Console Manager, a minimum of 90,000 blocks of free disk space is required.
Disk space refers to the space required for the product base files and does not take into account the requirements for log and archive data collected by VSI Console Management.
3. Migration Considerations
You can migrate an existing Console Manager configuration from an existing VAX, Alpha, or Itanium system. You will use the Export/Import function of the Console Manager configuration editor to migrate the basic configuration, but you should be aware of the following:
Custom action routines written in a high-level language. Make sure that there is a compiler available for that language on OpenVMS x86-64.
Logical names and DCL symbols that need to be defined on the new system.
If you have created SYS$MANAGER:CONSOLE$PRIVATE_SETUP.COM, be sure to examine it and make any modifications necessary for it to work correctly in your migrated environment.
Physical device names hard-coded into DCL procedures and DCL-based action routines as those device names may not exist on the x86-64 system.
If you utilize any of the Console Manager DECWindows-based graphical user interfaces or action routines, you will need an Xwindows compatible display station in your migrated environment.
Third-party software that may not be available on OpenVMS x86-64.
4. Management Processor Access Procedures are Included in the Kit
Users of the Alpha and Itanium architecture releases of Console Management could simplify access to the operating system console of systems that utilize a management processor front-end, such as the HP Integrity Server series, by installing a set of example command procedures. These procedures were provided in a downloadable patch kit and had to be installed after Console Management.
The x86-64 release of Console Management now includes all of those procedures in the software installation kit. The x86-64 release kit will place the following files in SYS$MANAGER during the installation. Instructions for using these procedures are included at the top of each of the files:
CONSOLE$MP_ACCESS.COM CONSOLE$MP_CO.COM CONSOLE$MP_DIALOG.COM CONSOLE$MP_ACCESS_SECURE.COM CONSOLE$MP_DIALOG_SECURE.COM CONSOLE$MP_MANAGEMENT_SECURE.COM