VSI Data Dictionary (VDD) Version X1.2-03

Release Notes


1. Introduction

The VSI Data Dictionary (VDD) X1.2-03 release introduces new functionality, usability improvements, and numerous fixes across VDD and its related utilities. This release places particular emphasis on enhancing the VDD Operator Utility (VDO), including expanded DDL compatibility, additional datatype support, and improved command processing.

This kit is provided on both x86-64 and IA-64 architectures. For information about installing VDD, refer to the VSI Data Dictionary Installation and User Guide.

Any issues regarding this release should be reported to VSI.

Licensing

Starting from this release, an evaluation license is required to use VDD on OpenVMS x86-64 and IA-64 systems.

2. What's New in Version X1.2-03

The following features and improvements have been implemented in this release of VDD:

  • Starting from this release, the VDD installation procedure automatically initializes ACMS$WORKSPACES if the Application Control and Management System (ACMS) for OpenVMS is installed on the system.

  • Added the /DDL qualifier for VDO, which starts the session with CDDL-compatible record-definition semantics enabled. The SET DDL and SET NODDL commands can be used to enable or disable this mode during a session, allowing VDO to process record definitions both with and without nested STRUCTURE keywords.

  • Improved SET DEFAULT handling. The command now works with partial paths, and a related logical-name handling bug has been corrected.

  • Improved consistency of SHOW DEFAULT by using the same anchor-resolution logic as the rest of VDO.

  • Added support for the PACKED NUMERIC datatype.

  • Added support for the VALUES ARE command.

  • Enhanced support for STRUCTURE definitions. The EXTRACT command now correctly handles STRUCTURE attributes, and STRUCTURE entities now support DATATYPE and SIZE attributes.

  • Extended VALUE IS support to accept additional data types and both IS and ARE forms. Support for the VARIANT keyword also now works inside STRUCTURE definitions.

  • Improved handling of very large buffers, preventing truncation during size and metadata-change calculations.

3. Fixed Issues

The following issues have been fixed in the VDD X1.2-03 release:

  • Fixed a parsing issue that affected VARIANTS OF definitions.

  • VDO no longer exits after encountering an error. Errors are now reported without terminating the session, and VDO only exits when the EXIT command is issued.

  • VDO now reports "unrecognized command" instead of a generic parse error when appropriate.

  • VDO now correctly distinguishes interactive terminal sessions from scripted or batch input.

  • Fixed a crash that could occur during ADU DELETE operations.

  • Corrected repository anchor resolution, preventing cases where the wrong repository anchor could be used.

  • CDD$DEFAULT is now honored during anchor resolution, improving coexistence between VDD and CDD environments.

  • Corrected deletion processing to always use the resolved object version, preventing incorrect or stale-version deletions.

  • Fixed a routing issue that could cause CDD-origin lookups to fall back to CDD instead of being processed through VDD.

4. Known Issues and Limitations

  • VDD does not automatically serialize access when multiple processes read and write the same repository at the same time. Applications that require guaranteed consistency under concurrent access should serialize writes at the application level (e.g. via CDD$LOCK_NODE) rather than relying on default behavior. This will be addressed in a future release.

  • VDD Operator Utility (VDO) does not currently support abbreviations.

  • To use VDD, you will need to implement some changes into the scripts that were used with other dictionary management tools.

  • VSI Data Management Utility (VDMU) currently lacks some verbs that may be necessary for complete integration.

  • VDD does not currently support the ACMS$MENU type of entity.

5. New In Previous Releases

The following improvements and bug fixes were made in previous releases:

  • Improved the performance of the commands DTR READY and DTR SHOW.

  • Fixed an issue that was causing an ACCVIO error when attempting to delete an ACMS task via the Application Definition Utility (ADU).

  • Improved handling of NAD elements.

  • Implemented the new /VERSION qualifier for the VMU MIGRATE command, allowing users to migrate all versions when specified.

  • Improved error reporting and default directory handling in VDO.

  • Updated $NEXT_NODE for NAD elements, preventing LCCNOTFND in DTR SHOW commands for records/fields and eliminating access violations in SHOW/EDIT on NAD elements.

  • The SHOW DICTIONARY command now correctly displays the current dictionary if it is CDD$TOP.

  • Removed a spurious "illegal record length" error report.

  • SHOW DOMAINS and related SHOW commands no longer produce empty output.

  • DTR now correctly starts at VDD$DEFAULT when defined.

  • Invalid commands now return more helpful diagnostics instead of "-CDD-E-NOMSG" errors.

  • SET DEFAULT CDD$TOP now correctly succeeds.

  • SET DEFAULT DIR now treats DIR as a directory name and sets it correctly.

  • Creation now correctly uses the next highest version when earlier versions are missing instead of forcing the version number to 1.

  • LIST CDD$TOP now lists all entity types correctly.

  • CREATE /AUDIT now accepts one or more quoted strings in addition to no value.

  • UNSTRUCTURED expression buffer data in the NAD protocol is now stored correctly.

  • Fixed file version parsing for the DTR/VDD interface, including negative version handling.

  • Resolved unexpected VDD$ANCHOR redefinition in the process table.

  • VDD$DEFAULT may reference a device via a logical name without error—commands such as the VDMU LIST command and the VDO DIRECTORY command now work correctly.

  • Fixed issues with VDD library caused by COBOL compiler and DDL definitions imported via VDO.

  • Changed RECORD type to CDD$RECORD in VDO.

  • Fixed the "%VDO-E-PERR, parse error" error that occurred when using the COBOL Edit_String keyword in VDO.

  • Fixed the "-VDD-E-CTXMISSING, context parameter is missing" error that occurred when using a dictionary reference from DECForms.

  • Fixed 16 API issues in the VDDSHR Library, resulting in a more robust call interface.

  • After entering SET DEFAULT in VDO and pressing the Enter key, the cont> prompt is now correctly displayed.

  • Prior errors are now shown when attempting to delete a non-empty directory in VDO.

  • After setting the default directory to CDD$TOP with the VDMU SET DEFAULT command, the SHOW DEFAULT command now shows the correct path.

6. VDD Tools and Library Overview

This version of VDD provides three tools (VDO, VMU, and VDMU) and one library, VDDSHR.EXE. For more information, refer to the VSI Data Dictionary Installation and User Guide or contact VSI.