and if you dont have access to the release notes...

[Bennett_2]

6.12 Reduced Reliance on CDD for Task Builds

The functionality for reducing reliance on CDD for task
builds, described in the following sections, was provided
with the ACMS Version 4.2 software and is documented in the
ACMS Version 4.3 documentation set.

6.12.1 No Longer Necessary to Store ACMS Definitions in CDD

In previous versions of ACMS, after ACMS definitions were
checked for syntax errors they were always stored in CDD.
When all the definitions were processed, the definitions
were read out of the dictionary, and a database file to
be used by the ACMS run-time software was created. With
ACMS Version 4.3, the ACMS definitions no longer have
to be stored in CDD. The ADU COMPILE command can be used
to compile ACMS definitions and store the results in an
OpenVMS file. Once all the definitions are processed, the
ADU LINK command can be used to create the runtime database
files.

CDD record definitions must continue to be stored in the
dictionary. When determining whether to store definitions
in CDD or to compile the definitions into OpenVMS files,
keep in mind the following:

o All ACMS definitions that are going to be transformed
for inclusion into a database file must be processed the
same way.

For example, if you store a task group definition in the
CDD, all task definitions referenced in the task group
must also be stored in the dictionary. If, instead, you
compile the task group definition, all referenced task
definitions must be compiled.

o File-based processing requires that the files that
are the compilation results of all referenced ACMS
definitions be in the same directory with the same file
extension. That is, the compilation results of all tasks
required by a task group must be in the same directory
with the same file extension. The same is true for all
submenus required by a menu.

For more information about the ADU COMPILE and LINK
commands, refer to the Compaq ACMS for OpenVMS ADU
Reference Manual.