[OpenVMS documentation]
[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
Updated: 12 December 1998

OpenVMS Version 7.2 Release Notes


Previous Contents Index


Chapter 3
General User Release Notes

This chapter provides information for all users of the OpenVMS operating system. It includes information about commonly used commands and utilities.

For information about new features included in this version of the software, refer to the OpenVMS Version 7.2 New Features Manual.

3.1 COM for OpenVMS (Alpha Only)

This section contains a note of interest to COM for OpenVMS field test customers.

3.1.1 Problems and Restrictions

The following note reports an incompatibility between COM for OpenVMS field test versions and OpenVMS Version 7.2.

3.1.1.1 Field Test Versions Incompatible with OpenVMS Version 7.2

V7.2

An incompatibility between field test versions of COM for OpenVMS and OpenVMS Version 7.2 prevents the COM for OpenVMS run time from starting.

If you are running a COM for OpenVMS field test version (G1.0, H1.0, or I1.0) and you upgrade to OpenVMS Version 7.2, you must install COM Version 1.0 for OpenVMS before you can start COM or run any COM applications.

For more information about installing and configuring COM for OpenVMS, see the OpenVMS Connectivity Developer's Guide, which is available from the OpenVMS website at the following location:

http://www.openvms.digital.com/openvms/products/dcom/

3.2 DCL Commands

This section contains release notes related to the DIGITAL Command Language (DCL) for this release of the OpenVMS operating system.

3.2.1 Changes and Enhancements

See Section 4.18.1.2 for a change in output displayed by the DIRECTORY/SECURITY and DIRECTORY/FULL commands.

3.2.2 Problems and Restrictions

The note in this section describes a restriction pertaining to DCL commands.

3.2.2.1 SET PROCESS/NOAUTO_UNSHELVE Command in Cluster Environment

V6.1

The DCL command SET PROCESS/NOAUTO_UNSHELVE does not support operations across the cluster. It can be issued only for a process on the same node, including as the default case, the process from which the command is issued.

The /IDENTIFICATION=pid qualifier is supported, but only when the target process is on the same node as the process where the command is issued.

3.3 DECTPU

This section contains release notes pertaining to the DEC Text Processing Utility (DECTPU).

3.3.1 Problems and Restrictions

The note in this section describes a DECTPU problem.

3.3.1.1 Motif Widget Context Help Built-In

V1.0

The following built-in, which should enter Motif context-sensitive help mode, is disabled because of a problem in the Motif toolkit:


SET (WIDGET_CONTEXT_HELP, widget_variable, {on|1|off|0}) 

The mouse pointer changes to a question mark, and DECTPU waits for you to select a widget by clicking MB1. DECTPU then executes the help callback of the selected widget (or of its parent if the selected widget has no help callback). The widget_variable is the widget within which the modal help interaction occurs, usually the top-level widget returned from the GET_INFO (SCREEN, "widget") built-in. The last parameter confines the question mark pointer to the specified widget if ON or 1, and does not confine the pointer if OFF or 0.

3.3.2 Documentation Changes and Corrections

This section contains a correction to the DECTPU documentation.

3.3.2.1 DEC Text Processing Utility Reference Manual

V7.2

For the CALL_USER procedure, the Example section does not distinguish between VAX and Alpha platforms for the link option. Under Step 3, "Create an option file...," the example contains only the VAX link option, UNIVERSAL=TPU$CALLUSER. For the Alpha platform, the correct link option is SYMBOL_VECTOR=(TPU$CALLUSER=PROCEDURE).

3.4 High-Performance Sort/Merge Utility (Alpha Only)

This section contains release notes pertaining to the command line interface and the callable interface (SOR routines) of the OpenVMS Alpha high-performance Sort/Merge utility. This information is of interest to both general users and programmers.

For more information about using the OpenVMS Alpha high-performance Sort/Merge utility, refer to the OpenVMS User's Manual and the OpenVMS Utility Routines Manual.

3.4.1 Problems and Restrictions

This section describes problems associated with using the command line interface and the SOR routines of the high-performance Sort/Merge utility.

3.4.1.1 Concurrent Sort Operations

V7.0

Memory allocation differences may limit the high-performance Sort/Merge utility's ability to perform the same number of concurrent sort operations as the Sort/Merge utility can perform in the same amount of virtual memory.

If this situation occurs, you can either increase the amount of virtual memory that is available to the process, or reduce the working set extent.

3.4.2 Corrections

This section describes problems that have been fixed in the command line interface and in the SOR routines of the high-performance Sort/Merge utility.

3.4.2.1 Error Messages Problem Fixed

V7.2

In previous versions of OpenVMS, error messages generated by the high-performance Sort/Merge utility did not include secondary error messages from RMS or other facilities.

This problem has been corrected in OpenVMS Version 7.2.

3.4.2.2 Merging Stream Files Limitation Fixed

V7.2

In previous versions of OpenVMS, when the high-performance Sort/Merge utility was used to merge stream files, the end-of-file was not written correctly for the output stream file.

This problem has been corrected in OpenVMS Version 7.2.


Previous Next Contents Index

[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
[OpenVMS documentation]

Copyright © Compaq Computer Corporation 1998. All rights reserved.

Legal
6534PRO_007.HTML