VSI Job Management for OpenVMS
Release Notes
- Operating System:
- VSI OpenVMS x86-64 Version 9.2-3
- Software Version:
- VSI Job Management V3.1 for OpenVMS
1. Introduction
VMS Software, Inc. (VSI) is pleased to introduce VSI Job Management V3.1 for OpenVMS.
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.
2. Software Requirements
Before you install VSI Job Management V3.1 for OpenVMS, make sure the following software products are installed on your system:
VSI OpenVMS x86-64 V9.2-3
VSI TCP/IP Services for OpenVMS x86-64 Version V6.0 or later
If you intend to use the DECwindows interface, you must install VSI DECWindows Motif for x86-64 V1.8-2 or later.
If you intend to use the remote functions to access other Job Managment Managers running on standalone nodes or in different VMS Clusters, you must install either DECnet Phase IV or DECnetPlus (both are included in the VSI OpenVMS V9.2-3 distribution).
3. Required OpenVMS ECO Kits
No ECO kits are required at the time of this field test.
4. Changes in This Release
This section describes the differences between VSI Job Management V3.1 for OpenVMS and the previous versions of the Job Management for OpenVMS product on the Alpha and IA-64 architectures.
4.1. Changes in Job Management Manager
4.1.1. File Naming Conventions
The names of command procedures are now prefixed with the string "JOB" instead of "UJM". For example, a script that is named UJM$MANAGER$STARTUP.COM on Alpha and IA-64 is named JOB$MANAGER$STARTUP.COM on x86-64.
Important
The legacy startup and shutdown procedures SCHEDULER$STARTUP.COM and SCHEDULER$SHUTDOWN.COM have been changed to call JOB$MANAGER$STARTUP.COM and JOB$MANAGER$SHUTDOWN.COM, respectively.
4.1.2. Logical Names
The default value for the SCHED$BATCH_NAME_PREFIX logical name has been changed from CAJM to VJM.
4.2. Changes in Job Management Agent
The names of command procedures are now prefixed with the string "JOB" instead of "UNIJM". For example, a script that is named UNIJM$MANAGER$STARTUP.COM on Alpha and IA-64 is named JOB$MANAGER$STARTUP.COM on x86-64.
5. Known Issues and Limitations
This section lists the issues and limitations that are relevant for VSI Job Management V3.1 for OpenVMS. VSI engineering is working to correct these problems.
- The SHELL interface is currently not functional. Any command entered at the
SCHEDULE>prompt will cause the interface to terminate with the following error:%RMS-F-NOMSG, Message number 00017924
- SCHEDULE commands that call the VSS$GET_HISTORY routine may display the following errors:
SUB VSS$GET_HISTORY: Error 250 at line 29 ?Not Implemented %BAS-F-NOTIMP, Not Implemented