Updated: 11 December 1998 |
OpenVMS Version 7.2
New Features Manual
Previous | Contents | Index |
This chapter provides new features information for all users of the
OpenVMS operating system.
2.1 DCL Commands, Qualifiers, and Lexical Functions
This section describes new and changed DCL commands, qualifiers, and
lexical functions for OpenVMS Version 7.2.
2.1.1 New SET PATH_PREFERRED Command
OpenVMS Version 7.2 introduces the SET PATH_PREFERRED command as a command line interface to the QIO function for disk and tape drives. SET PATH_PREFERRED has the following qualifiers:
For more information about SET PATH_PREFERRED and its qualifiers, refer
to the OpenVMS DCL Dictionary.
2.1.2 Changed DCL Commands and Qualifiers
Several commands and qualifiers have been modified to support the Extended File Specifications, Hierarchical Storage Management, and clusterwide logical names. The following table contains a summary of these changes. For more information about changed commands and qualifiers, refer to the OpenVMS DCL Dictionary.
DCL Command | New Features |
---|---|
COPY |
Support added for Extended File Specifications.
|
DEBUG |
Support added for CLIENT/SERVER.
|
DELETE |
Support added for Extended File Specifications.
|
DIRECTORY |
Support added for the Hierarchical Storage Management (HSM) project.
Support added for Extended File Specifications.
|
DUMP |
Support added for Extended File Specifications.
|
EXCHANGE NETWORK |
Support added for Extended File Specifications.
|
INITIALIZE |
Support added for Extended File Specifications.
Support added for DECram allocation increase.
|
Java |
Support added for Java Development Kit (JDK).
|
MIME | Support added for the MIME utility. |
Support added for Extended File Specifications.
|
|
PURGE |
Support added for Extended File Specifications.
|
RENAME |
Support added for Extended File Specifications.
|
SEARCH |
Support added for Extended File Specifications.
|
SET DEFAULT |
Support added for Extended File Specifications.
|
SET DEVICE |
Support added for Fast Path.
Support added for multipath parallel SCSI and Fibre Channel configurations.
|
SET DIRECTORY |
Support added for Extended File Specifications.
|
SET FILE |
Support added for Extended File Specifications.
|
SET MAGTAPE |
Support added for Fast Skip.
|
SET PROCESS |
Support added for Extended File Specifications.
|
SET SECURITY |
Support added for Extended File Specifications.
Support added for Intra-Cluster Communications (ICC).
|
SET VOLUME |
Support added for Extended File Specifications.
|
SHOW CPU | Support added for Fast Path. |
SHOW DEVICES |
Support added for Multipath.
|
SHOW DEVICES/FULL |
Support added for Fast Path.
Support added for Extended File Specifications.
|
SHOW MEMORY/POOL
SHOW MEMORY/POOL/FULL |
Support added for Lock Manager.
|
SHOW SECURITY |
Support added for Intra-Cluster Communications (ICC).
|
SHOW SYSTEM |
Support added for threads.
|
SUBMIT |
Support added for Extended File Specifications.
|
TYPE |
Support added for Extended File Specifications.
|
The following table contains a summary of new and changed DCL lexical functions. Refer to the OpenVMS DCL Dictionary for more information.
Lexical Function | New Features |
---|---|
F$FILE_ATTRIBUTES |
Support added for Extended File Specifications.
|
F$GETDVI |
Support added for Extended File Specifications.
|
F$GETENV |
Support added for new lexical.
|
F$GETJPI |
Support added for Extended File Specifications.
|
F$GETSYI |
Support added for clusterwide logical names.
|
F$TRNLNM |
Support added for clusterwide logical names.
|
OpenVMS Version 7.2 includes some significant documentation on new features.
For this release, OpenVMS is shipping the following new manuals to support new and enhanced functionality:
Version 7.2 of the OpenVMS System Manager's Manual contains the following new appendixes:
In addition, selected manuals from the integrated layered products and OpenVMS archived manuals are also included with the documentation.
For Version 7.2, the OpenVMS Documentation CD-ROM supports a dual OpenVMS and Windows-based PC format. This means that you can mount and read the CD-ROM on both OpenVMS VAX and Alpha systems and a Windows 95 or Windows NT system.
Table 2-3 provides information about the files and manuals that are provided on the two partitions.
File Type | Platform | Book Type |
---|---|---|
HTML | OpenVMS/Windows | OpenVMS Manuals |
PostScript | OpenVMS |
OpenVMS Manuals
Archived Manuals Layered Product Release Notes and Install Guides |
Bookreader | OpenVMS |
Archived manuals
Selected layered product manuals |
Windows | Archived manuals | |
Text | OpenVMS/Windows | Release Notes, New Features, Install Guides |
For the first time, OpenVMS is also shipping the executable files for the following browsers and viewers:
The MIME utility allows you to read and compose MIME-encoded mail messages. The standard used to attach nontext files to mail messages is the Multipurpose Internet Mail Extension (MIME). With MIME, nontext files, such as graphics or sound files, are encoded and sent as plain text, although that text may not be readable. The MIME utility decodes MIME files to their original form and allows you to create MIME-encoded files, which can be sent as mail messages using the OpenVMS Mail utility.
Complete instructions for using the MIME utility to decode or encode files are found in the OpenVMS User's Manual.
Information about the installation and administration of the MIME utility is found in the OpenVMS System Manager's Manual.
This chapter provides information about new features, changes, and
enhancements for system managers.
3.1 BACKUP Utility
The following section discusses improvements to the BACKUP utility for
OpenVMS Version 7.2.
3.1.1 /NOINCREMENTAL Qualifier
On a save operation, you can use the new BACKUP qualifier /NOINCREMENTAL to avoid saving all the files and subdirectories under directories that have been modified. Use this qualifier only if you are sure that you want to save specific files and do not want to save all data.
Prior to OpenVMS Version 6.2, the system, by default, did not save the files and subdirectories that were under directories that had been modified. In OpenVMS Versions 7.0 and 7.1, to ensure a successful restore, the system saved all files and subdirectories under directories that had been modified. This behavior, however, sometimes resulted in saving files and subdirectories that were not needed for later restore operations. The /NOINCREMENTAL qualifier has been implemented to allow you more control over the amount of file data that is saved.
Work on the BACKUP utility for this release has resulted in the following performance improvements:
In previous versions of OpenVMS, both storage and index file bitmaps were limited to 255 blocks. This size, in turn, limited a volume to approximately one million allocation units, or clusters. Larger disks were required to have a larger cluster factor to accommodate the limit; for example, a 9 GB disk required a cluster factor of 18.
Beginning with OpenVMS Version 7.2, the limits of storage and index file bitmaps have been increased as follows:
Type of Bitmap | Limit |
---|---|
Storage bitmap | 65535 blocks |
Index file bitmap | 4095 blocks |
The increased bitmap limits have the following advantages:
The behaviors of the INITIALIZE and BACKUP commands reflect the larger bitmap sizes. On OpenVMS Version 7.1 and earlier versions, you cannot mount a volume with bitmaps larger than 255 blocks. For this reason, the default cluster factor that the INITIALIZE command chooses on Files-11 structure level 2 disks limits the storage bitmap to 255 blocks. However, now you can override the default with an explicit cluster factor to make the storage bitmap as large as you want.
In OpenVMS Version 7.2, for Files-11 structure level 5 volumes, the INITIALIZE command assigns a cluster factor of 3 to currently available disks. The default maximum number of files---and hence, the size of the index file bitmap---that the INITIALIZE command assigns increases to correspond to the size of the storage bitmap.
In OpenVMS Version 7.2, when you use the BACKUP/IMAGE command to restore or copy a volume, the BACKUP utility normally preserves the cluster factor. However, when you copy an ODS-2 volume whose storage bitmap is 255 blocks or smaller, if the output volume is larger, BACKUP will increase the cluster factor to keep the storage map 255 blocks or smaller. This behavior ensures that a volume that was usable on pre-Version 7.2 systems remains usable when copied to larger media. You can override the BACKUP behavior by setting the output volume's cluster factor to any size by initializing the output volume with the /CLUSTER qualifier and then invoking BACKUP with the /NOINITIALIZE qualifier.
You cannot mount volumes with extended bitmaps on an OpenVMS Version 7.1 or earlier system. |
Beginning with OpenVMS Version 7.2, the OpenVMS Alpha and OpenVMS VAX operating system installation menus offer the choice to install either DECnet-Plus or DECnet Phase IV networking software. Note, however, that both DECnet products cannot run concurrently on your system. You must choose to install either DECnet-Plus or DECnet Phase IV. For DECnet Phase IV software service support, you must purchase an addendum to your standard support contract. See your local Compaq support representative for more information.
For detailed information about installing or upgrading DECnet-Plus and
DECnet Phase IV, refer to the OpenVMS Alpha Version 7.2 Upgrade and Installation Manual and the OpenVMS VAX Version 7.2 Upgrade and Installation Manual.
3.4 Deferred Memory Testing on AlphaServer 4100 Computers
To speed up the time between system power-on and user login, the system manager can now defer a portion of memory testing on AlphaServer 4100 computers. When you choose this option, the console tests a minimum amount of memory and leaves the rest for the operating system to test.
To use this new feature, you need to specify a value for the MEMORY_TEST environment variable at the console before booting. The values for MEMORY_TEST are as follows:
Value | Description |
---|---|
FULL (off) | The console does all the testing. |
NONE | 32 MB of memory are tested before booting. |
PARTIAL | 256 MB of memory are tested before booting. |
If you set MEMORY_TEST to NONE or PARTIAL, OpenVMS tests any remaining untested memory on an as-needed basis at either or both of the following times:
When you change the value of MEMORY_TEST, you must issue the INIT console command before the new value takes effect. Therefore, you need to follow these steps from the console before booting:
OpenVMS also gives you more control over when memory is actually tested. Bit 2 in the system parameter MMG_CTLFLAGS controls deferred memory testing:
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6520PRO_001.HTML
|