HP OpenVMS Systems Documentation

Content starts here

OpenVMS Version 7.3 Release Notes

Previous Contents Index

5.14.4 Remote Access of Recovery Unit Journaled Files in an OSI Environment


OSI nodes that host recovery unit journaled files that are to be accessed remotely from other nodes in the network must define SYS$NODE to be a Phase IV-style node name. The node name specified by SYS$NODE must be known to any remote node attempting to access the recovery unit journaled files on the host node. It must also be sufficiently unique for the remote node to use this node name to establish a DECnet connection to the host node. This restriction applies only to recovery unit journaled files accessed across the network in an OSI or mixed OSI and non-OSI environment.

5.14.5 VFC Format Sequential Files

VAX V5.0
Alpha V1.0

You cannot update variable fixed-length control (VFC) sequential files when using before-image or recovery unit journaling. The VFC sequential file format is indicated by the symbolic value FAB$C_VFC in the FAB$B_RFM field of the FAB.

5.15 Security---DIRECTORY Command Now Summarizes Suppressed PATHWORKS ACEs


In OpenVMS Version 7.1 and later, if you execute the DCL command DIRECTORY/SECURITY or DIRECTORY/FULL for files that contain PATHWORKS access control entries (ACEs), the hexadecimal representation for each PATHWORKS ACE is no longer displayed. Instead, the total number of PATHWORKS ACEs encountered for each file is summarized in this message: "Suppressed n PATHWORKS ACE." To display the suppressed PATHWORKS ACEs, use the DUMP/HEADER command.

5.16 System Parameters

The release notes in this section pertain to OpenVMS system parameters.

5.16.1 MAXBOBMEM System Parameter Not Obsolete


When you are using the AUTOGEN utility, the following warning may occur in the AGEN$PARAMS.REPORT:

** WARNING - Parameter MAXBOBMEM is Obsolete .

The MAXBOBMEM system parameter is not obsolete.

5.16.2 VCC_MAXSIZE System Parameter Definition Corrected


The system parameter VCC_MAXSIZE is incorrectly described in online help and in the OpenVMS System Management Utilities Reference Manual: M--Z as follows:

"This special parameter is used by Compaq and is subject to change. Do not change this parameter unless Compaq recommends that you do so."

Please ignore the quoted paragraph; VCC_MAXSIZE is not a special parameter, and you can change it. Also, its maximum value is now correctly set at 3700000.

If you want to adjust the XFC size, use the system parameter VCC_MAX_CACHE to do so.

5.16.3 NISCS_MAX_PKTSZ System Parameter Definition Corrected


PEDRIVER uses NISCS_MAX_PKTSZ to compute the maximum amount of data to transmit in any LAN packet:

LAN packet size <= LAN header (padded Ethernet format)
                   + NISCS_MAX_PKTSZ
                   + NISCS checksum (only if data checking is enabled)
                   + LAN CRC or FCS

The following table shows the minimum NISCS_MAX_PKTSZ value required to use the maximum packet size supported by specified LAN types. These values are corrections of the values shown in online help and in the System Parameters appendix of the OpenVMS System Management Utilities Reference Manual: M--Z.

Type of LAN Minimum Value for NISCS_MAX_PKTSZ
Ethernet 1498
FDDI 4468
Gigabit Ethernet 7532
ATM 7606

5.16.4 Parameter Description Changes


Descriptions of the following system parameters have been changed or corrected since the last release:

  • DEVICE_NAMING (Alpha only)
  • FAST_PATH (Alpha only)
  • IO_PREFER_CPUS (Alpha only)
  • LAN_FLAGS (Alpha only)
  • MAXBOBMEM (Alpha only)
  • MPDEV_REMOTE (Alpha only)
  • NPAGERAD (Alpha only)
  • S2_SIZE (Alpha only)
  • VCC_FLAGS (Alpha only)
  • VCC_MAX_CACHE (Alpha only)
  • VCC_MAX_LOCKS (Alpha only)
  • VCC_WRITEBEHIND (Alpha only)
  • VCC_WRITE_DELAY (Alpha only)

You can read the new descriptions of these system parameters in online help. For example:


5.16.5 Obsolete System Parameters


Starting with OpenVMS Version 7.3, the following system parameters are obsolete:



Initially, the MAXBOBS0S1 and MAXBOBS2 parameters were intended to ensure that users could not adversely affect the system by creating huge buffer objects. However, as users began to use buffer objects more widely, managing the combination of these parameters proved to be too complex.

Users who want to create buffer objects must either hold the VMS$BUFFER_OBJECT_USER identifier or execute in executive or kernel mode. Therefore, these users are considered privileged applications, and the additional safeguard that these parameters provided is unnecessary.

To determine current usage of system memory resources, enter the following command:


5.17 Terminal Fallback Facility (TFF) (Alpha Only)

On OpenVMS Alpha systems, the Terminal Fallback Facility (TFF) includes a fallback driver (SYS$FBDRIVER.EXE), a shareable image (TFFSHR.EXE), a terminal fallback utility (TFU.EXE), and a fallback table library (TFF$MASTER.DAT).


TFFSHR has been removed from IMAGELIB because it is not a documented, user-callable interface. The image is still available in the SYS$LIBRARY: directory.

To start TFF, invoke the TFF startup command procedure located in SYS$MANAGER, as follows:


To enable fallback or to change fallback characteristics, invoke the Terminal Fallback Utility (TFU), as follows:


To enable default fallback to the terminal, enter the following DCL command:


OpenVMS Alpha TFF differs from OpenVMS VAX TFF in the following ways:

  • On Alpha systems, the TFF fallback driver is named SYS$FBDRIVER.EXE. On VAX systems, the TFF fallback driver is named FBDRIVER.EXE.
  • On Alpha systems, TFF is capable of handling 16-bit character fallback. The OpenVMS Alpha fallback table library (TFF$MASTER.DAT) contains four more 16-bit character tables than the VAX library. Table 5-3 describes these additional tables.

    Table 5-3 TFF Character Fallback Tables
    Table Name Base Description
    BIG5_HANYU BIG5 BIG5 for CNS 11643 (SICGCC) terminal/printer
    HANYU_BIG5 CNS CNS 11643 (SICGCC) for BIG5 terminal/printer
    HANGUL_DS KS KS for DOOSAN 200 terminal

    These tables are used mainly by the Asian region. Also, the table format was changed due to the support of 16-bit character fallback.
  • On Alpha systems, the TFU command SHOW STATISTICS does not display the size of the fallback driver (SYS$FBDRIVER.EXE).

RT terminals are not supported by TFF.

For more information about the Terminal Fallback Facility, refer to the OpenVMS Terminal Fallback Utility Manual. The order number for this manual is AA--PS6BA--TE, and you can also access it on line from the OpenVMS Documentation CD-ROM (in the archived manuals directory).

5.18 Volume Shadowing for OpenVMS

The following release notes pertain to Volume Shadowing for OpenVMS.

5.18.1 Minicopy Version Required on All Nodes


OpenVMS Alpha Version 7.3 introduces minicopy support in Compaq Volume Shadowing for OpenVMS.

To use this new feature of volume shadowing in an OpenVMS Cluster system, OpenVMS Version 7.3, or an upgrade to OpenVMS Version 7.2--xx that will contain this support, must be installed on every node. This restriction also pertains to all storage controllers, such as the HS121, that use OpenVMS to serve disks.

The upgrade to OpenVMS Version 7.2--xx that will include minicopy support is expected to be available soon after the release of OpenVMS Version 7.3.

5.18.2 Multipath HSG/HSZ Disk Partitions and Volume Shadowing Restriction


A partition of a multipath disk on an HSG80, HSG60, HSZ80, or HSZ70 controller can be used as a member of a host-based volume shadow set (HBVS) if and only if that disk is used exclusively for that partition. Specifically, the remaining space on the partitioned disk cannot be used for another logical unit that is accessed concurrently with the partition that is an HBVS member.

Failure to adhere to this restriction can result in:

  • Problems mounting the shadow set
  • Reduced data availability due to the unexpected removal of shadow set members

Compaq expects to remove this restriction in the future.

5.18.3 Dismount of Client Using /MINICOPY; First Dismount Might Fail


In an OpenVMS Cluster configuration, when a member of a shadow set is dismounted on a client and the minicopy qualifier is specified, the first DISMOUNT command might fail.


If the first DISMOUNT command fails, repeat the command, as shown in the following example:

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
DSA5555:                Mounted              0  $80$DKA107:    7994646     1  18
$80$DKA107:    (WILD3)  ShadowSetMember      0  (member of DSA5555:)
$80$DKA302:    (WILD3)  ShadowSetMember      0  (member of DSA5555:)
$80$DKA303:    (WILD3)  ShadowSetMember      0  (member of DSA5555:)
%DISM-W-CANNOTDMT, $80$DKA302: cannot be dismounted
%DISM-F-SRCMEM, only source member of shadow set cannot be dismounted

This problem will be corrected in a future release.

5.18.4 SHADOW_MAX_UNIT Settings


OpenVMS Alpha Version 7.3 introduces minicopy support in Volume Shadowing for OpenVMS.

As part of the minicopy functionality, a new volume shadowing system parameter, SHADOW_MAX_UNIT, is provided for specifying the maximum number of shadow sets that can exist on a node. The default value on OpenVMS Alpha systems is 500; on OpenVMS VAX systems, the default is 100. This system parameter is not dynamic; a reboot is required to make the change take effect.


Review carefully the default settings of SHADOW_MAX_UNIT for your configuration. Dismounted shadow sets, unused shadow sets, and shadow sets with no write bitmaps allocated to them are included in this total. The setting must be equal to or greater than the number of shadow sets you plan to have on a system. Any MOUNT command that attempts to create more than the maximum specified by SHADOW_MAX_UNIT fails.

Note that this parameter does not affect the naming of shadow sets. For example, with the default value of 100, a device name such as DSA999 is still valid.

5.18.5 SHADOW_MAX_COPY VAX Setting for Using Minicopy in Mixed-Architecture Cluster


OpenVMS Version 7.3 supports minicopy on standalone Alpha systems, in an OpenVMS Cluster system consisting entirely of Alpha systems, and in a mixed-architecture OpenVMS Cluster system consisting of Alpha and VAX systems. It is possible, although highly unlikely, in a mixed-architecture cluster that a VAX system could be assigned the task of adding a member to a shadow set. Because a VAX system cannot perform a minicopy, it would perform a full copy.

To prevent this from happening, Compaq advises you to set the SHADOW_MAX_COPY system parameter to 0 on any VAX systems in the cluster if you intend to use this new minicopy feature.

5.18.6 HSD10 Virtual Disks


The HSD10 controller supports a virtual disk capability by partitioning physical disks. To prevent data corruption, do not use OpenVMS Volume Shadowing to create shadow sets using HSD10 virtual disks.

Chapter 6
Programming Release Notes

This chapter provides release notes about both application and system programming on OpenVMS systems.

For information about new programming features included in OpenVMS Version 7.3, refer to the OpenVMS Version 7.3 New Features and Documentation Overview.

6.1 Backup API

This section contains release notes pertaining to the Backup application programming interface (API).

6.1.1 Unexpected Informational Message


The Backup API may return an incorrect exit status, BACKUP-I-INCONQUALS, and display an informational message after the backup completes. The backup will, however, proceed as normal.

The following BCK_OPT_K_BEFORE_TYPE and BCK_OPT_K_SINCE_TYPE flags have been removed. If one or more of these flags is used, the informational message may be displayed.


6.1.2 Journaling Callback Events Restriction


If an application registers a callback routine for any of the journaling events, it must register a callback routine for all the journaling callback events. The following is a list of the journaling callback events:


This is a permanent restriction.

See the Backup API chapter in the OpenVMS Utility Routines Manual for more information on registering callback routines.

6.1.3 Repetitive Calls to BACKUP$START Can Cause an Error


Repetitive calls to BACKUP$START can cause the following error:

%BACKUP-F-INSBUFSPACE, insufficient buffer space

The number of repetitive calls completed before receiving this error varies, depending on the previous backup operations performed.

The workaround for an application that receives this error is to exit the operation and restart.

6.2 Batch and Print Queues---Terminating Executing Batch Jobs


Under the following conditions, the DELETE/ENTRY command may fail to stop an executing batch job:

  • The batch job is a DCL command procedure.
  • There is an ON ERROR CONTINUE command (or SET NOON command) within the command procedure.

The DELETE/ENTRY command causes the job to terminate in phases. A delete_process AST routine is given in user mode, supervisor mode, and then executive mode. Because there is a small delay between each mode, it is possible that, in a batch job, a user-mode image may terminate, and the command procedure may continue to execute until the supervisor-mode delete_process AST routine is executed.

The return status of the SYNCHRONIZE command is assumed to contain the termination status of the target batch job. In addition, command procedures would normally execute a command such as $ON ERROR THEN CONTINUE or $SET NOON before issuing the SYNCHRONIZE command. If a DELETE/ENTRY command is issued to the job executing the SYNCHRONIZE command, the JBC$_JOBABORT is interpreted as being the termination status of the target batch job rather than a return status of the SYNCHRONIZE command. The command procedure then continues to execute for a short period with this incorrect assumption and performs an operation such as requeuing the target batch job or incorrectly reporting a failure of the target batch job.

This problem has been corrected for the SYNCHRONIZE command by detecting this situation and waiting in an exit handler for longer than the delay between the user-mode and supervisor-mode termination delay.

Any other images that would report the job completion status obtained by the SJC$_SYNCHRONIZE_JOB function code of the $SNDJBC system service as the return status of the program should implement logic similar to the following:

  1. Declare an exit handler.
  2. In the exit handler, implement the following logic:

    IF (exit status is JBC$_JOBABORT)
        Wait 10 seconds

6.3 COM for OpenVMS (Alpha Only)


For release notes about COM for OpenVMS, see the OpenVMS Connectivity Developer Guide, which is installed as part of the COM for OpenVMS installation process. That document is available in PostScript, HTML, and PDF formats.

The OpenVMS Connectivity Developer Guide is also available from the OpenVMS website at the following location:


6.4 Compaq Ada Run-Time Library

This section contains release notes pertaining to the Compaq Ada Run-Time Library.

6.4.1 OpenVMS Text Libraries Containing Ada Declarations


The following OpenVMS text libraries are optional Ada bindings for STARLET:


These bindings are not supplied in the Compaq Ada V3.5A Predefined Library (which was last updated for OpenVMS V7.1).

These bindings are not supported by Compaq Ada.

6.4.2 Unexpected Storage Errors (Alpha Only)


In OpenVMS Alpha Version 7.0 and later, binary compatibility fails for some Compaq Ada programs that make incorrect assumptions about the amount of task space used by Compaq Ada tasks. If a task receives a storage error that it did not previously receive, you may need to add a length clause specifying the storage size for the task. If you already use a length clause, you may need to increase the amount of storage specified. This is necessary only in cases where the specified size (or default size) is not large enough for the task's execution.

6.4.3 AST Procedures No Longer Receive Access Violations


Compaq Ada written AST procedures used to receive access violations if the AST that invoked them occurred when the null thread or a non-Compaq Ada thread was running.

The workaround (rewrite the program to use a task entry point that has pragma AST_ENTRY on it) is no longer necessary.

6.5 Compaq C Run-Time Library

The following sections contain release notes pertaining to the Compaq C Run-Time Library (RTL).

6.5.1 The strptime Function Is Now XPG5 Compliant


The strptime function has been modified to be compliant with X/Open CAE Specification System Interfaces and Headers Issue 5 (commonly known as XPG5). The change for XPG5 is in how the strptime function processes the "%y" directive for a two-digit year within the century if no century is specified.

When a century is not specified, XPG5 requires that values for the "%y" directive in the range of 69 through 99 refer to years in the twentieth century (1969 through 1999), while values in the range of 00 through 68 refer to years in the twenty-first century (2000 through 2068). Essentially, for the "%y" directive, strptime became a "pivoting" function, with 69 being a pivoting year.

Before this change, the strptime function interpreted a two-digit year with no century specified as a year in the twentieth century.

With OpenVMS Version 7.3, XPG5-compliant strptime becomes a default strptime function in the Compaq C RTL. However, the previous nonpivoting XPG4-compliant strptime function is retained for compatibility.

The pivoting is controlled by the DECC$XPG4_STRPTIME logical name. To use the nonpivoting version of strptime , do either of the following:

  • Define DECC$XPG4_STRPTIME to any value before invoking the application.
  • Call the nonpivoting strptime directly as the function decc$strptime_xpg4 .

Previous Next Contents Index