vsiftp.vmssoftware.com/[e-mail]/FREEWARE/FREEWARE40.ZIP/vde/doc/vdemsg.sdml

Text File | 1996-12-12 | 336KB | 8,327 lines

<MESSAGE_SECTION> <MESSAGE_TYPE>(textident)

<MSG>(ABKEYW\ambiguous qualifier or keyword '<EMPHASIS>(text)' - supply more
characters )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE cannot complete the command because '<EMPHASIS>(text)'
is ambiguous in the context of this command.

<MSG>(ABTBADST\VDE may be in an inconsistent internal state )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The user has typed 3 or more CTRL/Cs.  VDE normally responds
to a CTRL/C by continuing execution until a consistent
internal state is achieved and then aborts the current
command.  However, if VDE is in an infinite loop and does not
detect this "consistent" state, it will abort anyway after
the 3rd CTRL/C.
<MSG_TEXT>(User Action)
Leave and enter VDE again to make sure the internal state is
consistent.

<MSG>(ABTCNTLC\command aborted by Control-C )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current VDE command has been aborted due to a
control C issued by the user.  VDE will attempt to
gracefully recover.
<MSG_TEXT>(User Action)
Issue another command to VDE.  It has gracefully
to a consistent internal state.

<MSG>(ADATETIME\accepted.checkin.datetime: <EMPHASIS>(datetime) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AERRORS\accepted.checkin.defectsfixed: <EMPHASIS>(defects) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AGROUP\accepted.checkin.group: <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AITEM\accepted.checkin.item: <EMPHASIS>(item) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AMODULE\accepted.checkin.module: <EMPHASIS>(modname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ANOTE\accepted.checkin.note: <EMPHASIS>(topic).<EMPHASIS>(reply) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARCHADDED\architecture <EMPHASIS>(architecture) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated architecture
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the CREATE ARCHITECTURE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(ARCHDEL\architecture <EMPHASIS>(architecture) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated architecture has been deleted from the VDE
database.  This message is only issued when you use
the /LOG qualifier on the DELETE ARCHITECTURE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(ARCHEXISTS\architecture <EMPHASIS>(architecture)  already exists in database; not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated architecture name was specified on a CREATE
ARCHITECTURE command, but an entry for that architecture
is already present in the database.  Hence a new entry was
not created for that architecture.  Alternatively, the
indicated name was specified as the new name for an existing
architecture on the MODIFY ARCHITECTURE command, but another
architecture already has the requested new name.  Hence the
name of the existing architecture could not be changed to
the new name.
<MSG_TEXT>(User Action)
If you entered the wrong architecture name, reenter the
command with the correct name.  If you entered the right
architecture name, use the SHOW ARCHITECTURE command to
display the database information for that architecture.
If you are not satisfied with that information, use the
MODIFY ARCHITECTURE command to change it.

<MSG>(ARCHMOD\information for architecture <EMPHASIS>(architecture) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
architecture has been modified in the VDE database.  This
message is only issued when you use the /LOG qualifier on
the MODIFY ARCHITECTURE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(ARCHNOTDEL\architecture <EMPHASIS>(architecture) not deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to delete an architecture that
cannot be deleted.  Additional messages are normally
included with this message, and these messages
indicate why the architecture cannot be deleted.
<MSG_TEXT>(User Action)
Resolve the problem(s) flagged by the other error
messages, and reenter the DELETE ARCHITECTURE command.

<MSG>(ARCHNOTFOUND\architecture <EMPHASIS>(architecture) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated architecture name was entered on a SHOW
ARCHITECTURE command, but no such architecture was found
in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated architecture does not exist in the
database.

<MSG>(ARCHSYNTAX\invalid architecture name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the architecture name
is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the architecture name using only alphanumeric,
underscore, dollar sign and hyphen characters.

<MSG>(AREASON\accepted.checkin.reasonmask: <EMPHASIS>(reason) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AREPLID\accepted.checkin.replacementid: <EMPHASIS>(replid) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AREPLNAME\accepted.checkin.replname: <EMPHASIS>(replname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBCMSDIR\accepted.module.cmslibrary: <EMPHASIS>(cmsdir) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBCOUNT\accepted.module.count: <EMPHASIS>(count) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBGENNEW\accepted.module.newgeneration: <EMPHASIS>(newgen) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBGENOLD\accepted.module.oldgeneration: <EMPHASIS>(oldgen) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBMODFLAG\accepted.module.modflags: <EMPHASIS>(modflags) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBMODNAME\accepted.module.modname: <EMPHASIS>(modname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBREPLREMARK\accepted.module.replaceremark: <EMPHASIS>(replaceremark) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBRESREMARK\accepted.module.reserveremark: <EMPHASIS>(reserveremark) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ARMPBSTAGING\accepted.module.staging: <EMPHASIS>(staging) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.
! ========== ========== ==========

<MSG>(ASTREAM\accepted.checkin.stream: <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ATTACHED\terminal now attached to process <EMPHASIS>(process-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The SPAWN command issues this message before attaching to
the new process.

<MSG>(ATYPCOD\accepted.checkin.typecode: <EMPHASIS>(type) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(ATYPNAM\accepted.checkin.typename: <EMPHASIS>(type) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(AUSERNAME\accepted.checkin.username: <EMPHASIS>(username) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.
! ========== ========== ==========

<MSG>(BADASSUMPTION\bad assumption, <EMPHASIS>(name), <EMPHASIS>(value), <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an inconsistency in its internal memory pool.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include any
information that may be useful or relevent in duplicating the
problem.

<MSG>(BADCHAR\illegal character encountered )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An unanticipated character was found on the command line. This
character may be found to have meaning in other syntaxes;
however, it lacks  meaning in this context.
<MSG_TEXT>(User Action)
Verify the appropriate syntax of the specific command.

<MSG>(BADFILNAM\illegal file specification '<EMPHASIS>(text)' )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The provided file name does not follow standard VMS
file specification conventions.

<MSG>(BADIMAFLA\bad image flavor detected )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an inconsistent image flavor setting.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in
duplicating the problem.

<MSG>(BADMARKER\bad marker file format for generation <EMPHASIS>(generation) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The CMS element for a module should contain a marker file
that points to the actual source module, but the indicated
generation of the module does not contain a valid marker
file.  This error is also seen when /OUTPUT=NLA0: is
specified on a FETCH or RESERVE of a module that uses
a marker file.
<MSG_TEXT>(User Action)
Examine the text of the CMS generation using CMS directly
to determine what is wrong.  If the module should not use
marker files, change its marker-file attribute with the
MODIFY MODULE command.  If it should use marker files,
determine what is wrong with the CMS element and repair
it with CMS so it points to the appropriate actual source
module.  If /OUTPUT=NLA0: was specified, respecify the
command with a non-null device and directory.

<MSG>(BADQUESTAT\bad status for batch queue <EMPHASIS>(queue-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A batch queue to which you are attempting to submit a
build job is not available.  The reason why it is not
available is given by a second message following this
message.
<MSG_TEXT>(User Action)
This is an informational message only.  If you need the
displayed batch queue for your build job, stop the build
job and resubmit it later when the queue is available again.

<MSG>(BADSCRATCH\bad SYS$SCRATCH directory )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The directory specification associated with the SYS$SCRATCH
logical name is not syntactically correct.  Associated with
the VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Reenter the VDE command after redefining SYS$SCRATCH to a
valid directory specification.

<MSG>(BADSTATUS\bad status returned from <EMPHASIS>(routine-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE got an unexpected error status from a system service
or RTL routine <EMPHASIS>(routine-name) that it called.
<MSG_TEXT>(User Action)
Examine the associated error messages and determine if
the problem can be remedied through changes to process
quotas or to SYSGEN parameters, or due to a site-specific
configuration problem.  Contact VDE support for assistance.

<MSG>(BADVMSVERS\unable to interpret OpenVMS version string: <EMPHASIS>(VMS-version) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE is unable to determine OpenVMS version information
from the version string returned either from a SYS$GETSYI
service call or from a translation of the logical name
VDE$VMS_VERSION.  This may indicate you are running an
internal baselevel of the operating system.
<MSG_TEXT>(User Action)
Define the logical name VDE$VMS_VERSION to a valid
OpenVMS version string value.  This will override
the value returned by SYS$GETSYI.

<MSG>(BINSRCMOD\binary source modules cannot be displayed or differenced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have entered a SHOW or EDIT command to display a
binary (non-text) source module or the differences
between two generations of a binary source module.
These commands do not work on binary modules.
<MSG_TEXT>(User Action)
Do not use the SHOW or EDIT command on binary source modules.

<MSG>(BITRANGE\bit range out of limits )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment

<MSG>(BLDALRSTART\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) already started; build job cannot be started again )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to start a build job that cannot be
started because it has already been started.  A build job
can only be started if it is not queued for execution or if
it is suspended.  As a result, the specified build job could
not be started.
<MSG_TEXT>(User Action)
This is an informational message.  No user action is required.

<MSG>(BLDALRSTOP\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) has already stopped; build job cannot be stopped again )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to stop a build job that has already been
stopped or that has already completed.  As a result, the
build job could not be stopped.
<MSG_TEXT>(User Action)
This is an informational message.  No user action is required.

<MSG>(BLDINIFAIL\build initialization completed with errors )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The build initialization for a build job or a compile or
link operation completed with one or more errors.  The
DCL commands that failed were generated from the build
initialization script for the default development stream.
<MSG_TEXT>(User Action)
Correct the errors and resubmit the compilation or build job.

<MSG>(BLDJOBACT\build job already active for stream <EMPHASIS>(stream); new job not created )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to create a new build job with the BUILD
command when another build job for the same development
stream is already active.  A build job is <QUOTE>(active)
unless it has completed execution or has been stopped.
You cannot have more than one active build job for the
same stream at any one time since that could cause two
build jobs to write to the same result directories at the
same time.
<MSG_TEXT>(User Action)
Allow the first build job to complete before you create
the next one.  Alternatively, you can stop the previous
build job with the STOP BUILD_JOB command and then create
the new build job.

<MSG>(BLDJOBAFTER\build job to be started after <EMPHASIS>(time) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The build job you are starting will actually start executing
after the indicated date and time.
<MSG_TEXT>(User Action)
This is an informational message only.  If you do not want
the job started after the shown time, stop the job with the
STOP BUILD_JOB command and restart it with a different time
using the START BUILD_JOB command.

<MSG>(BLDJOBCRE\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) has been created )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated build job has
been created in the VDE database for the indicated
development stream.  This message is only issued when you
use the /LOG qualifier on the BUILD command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(BLDJOBDEL\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) deleted from database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated build job
has been deleted from the VDE database.  This message
is only issued when you use the /LOG qualifier on the
DELETE BUILD_JOB command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(BLDJOBENT\entry number <EMPHASIS>(entry) submitted to queue <EMPHASIS>(queue) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A process has successfully been submitted to the indicated
batch queue.  It received the queue entry number shown in
the message.
<MSG_TEXT>(User Action)
This is an informational message.  No user action is required.

<MSG>(BLDJOBERR\error queuing build job on queue <EMPHASIS>(queue); process not queued )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when attempting to queue a process on
the indicated batch queue on behalf of a build job you are
starting.  The message that follows gives more information
on the reason for the error.  In this case, no more processes
are submitted to the indicated queue.  Your build job will
thus run with fewer processes than your requested.
<MSG_TEXT>(User Action)
This is an informational message only.  If you need the
displayed batch queue for your build job, stop the build
job, correct the error, and resubmit the build job later
when the queue is available again.

<MSG>(BLDJOBMOD\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
build job has been modified in the VDE database.  This
message is only issued when you use the /LOG qualifier on
the MODIFY BUILD_JOB command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(BLDJOBSIZ\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) consists of <EMPHASIS>(steps) steps )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message tells you how many build steps there are in
the indicated build job.  This message is only issued when
you use the /LOG qualifier on the BUILD or START BUILD_JOB
command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(BLDJOBSTARTED\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) started with <EMPHASIS>(processes) processes )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The build job with the shown build-job identification number
for the indicated development stream has successfully been
started.  The message shows the actual number of parallel
processes that will execute the build job.
<MSG_TEXT>(User Action)
This is an informational message.  No user action is required.

<MSG>(BLDJOBSTARTING\starting build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The build job with the shown build-job identification number
for the indicated development stream is about to be started.
This message comes out before the processes that will run
the build job are submitted to batch queues.  Its purpose
is to let you know which build job is being started.
<MSG_TEXT>(User Action)
This is an informational message.  No user action is required.

<MSG>(BLDJOBSTOP\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) stopped )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated build job has been stopped.  This message is
only issued when you use the /LOG qualifier on the STOP
BUILD_JOB command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(BLDJOBSUSP\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) suspended )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated build job has been suspended.  A suspended
build job can be restarted with the START BUILD_JOB command.
This message is only issued when you use the /LOG qualifier
on the SUSPEND BUILD_JOB command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(BLDNOTRUN\build job <EMPHASIS>(job) for stream <EMPHASIS>(stream) is not queued or running; build job cannot be suspended )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to suspend a build job that is not
currently queued for execution or running.  As a result,
the build job could not be suspended.
<MSG_TEXT>(User Action)
This is an informational message.  No user action is required.

<MSG>(BLDSTEPNEED\build step needed to make inputs up-to-date:      <EMPHASIS>(step) <EMPHASIS>(step) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated build step needs to be performed to make all
input modules up-to-date for the compile or link operation
you have requested.  This situation can occur if, for example,
you have modified a source module without compiling it (so
that the corresponding object module is no longer up-to-date)
and you then request a link that includes the old, non-current
object module.  This is an informational message to alert
you that your compile or link will not produce fully
up-to-date outputs, but the requested compile or link will
still be performed as you requested.
<MSG_TEXT>(User Action)
If the outputs of the compile or link do not need to be
up-to-date, no action is necessary.  Otherwise, you can
use COMPILE, LINK, or BUILD commands to perform the build
steps needed to make all inputs to the original compile or
link operation up-to-date with respect to all source changes.
You can then repeat that original operation.

<MSG>(BLDSTEPNOTSHO\<EMPHASIS>(steps) additional needed build steps not shown )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
If more than 30 build steps are needed to make the inputs
to a requested compile or link up-to-date, BLDSTEPNEED
messages are only printed for the first 30 such build steps.
Then the BLDSTEPNOTSHO message is printed to indicate how
many additional build steps are needed, but those build
steps are not listed individually.
<MSG_TEXT>(User Action)
If the outputs of the compile or link do not need to be
up-to-date, no action is necessary.  Otherwise, you can
use COMPILE, LINK, or BUILD commands to perform the build
steps needed to make all inputs to the original compile or
link operation up-to-date with respect to all source changes.
You can then repeat that original operation.

<MSG>(CMSBADGEN\bad CMS generation <EMPHASIS>(generation) found for module <EMPHASIS>(module)      possible CMS error )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated bad CMS generation expression was found in
an existing CMS library; the cause is probably an error
in CMS.  The affected generation is not recorded in the
VDE database.
<MSG_TEXT>(User Action)
Examine the CMS library and consult a CMS expert.

<MSG>(CMSCLASSEXIST\CMS class <EMPHASIS>(class) already exists for CMS facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated CMS class was found to already exist in the
indicated CMS facility, so we do not attempt to create it.
<MSG_TEXT>(User Action)
None.

<MSG>(CMSCRECLASS\CMS error when creating CMS class <EMPHASIS>(class) in facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when creating a CMS class in the indicated
facility.  The subsequent print line shows what
specific error status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSCREELEM\CMS error when creating CMS element for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when creating the CMS element (the delta-file)
for the indicated module.  The subsequent print line
shows what specific error status CMS returned.  This
error should not occur unless you have insufficient
privileges to access the VDE library or the file to
be added to that library, or unless you have run out
of some resource such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSCRELIB\CMS error when creating CMS library for facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when creating the CMS library for the indicated
facility.  The subsequent print line shows what specific
error status CMS returned.  This error should not occur
unless you have insufficient privileges to access the
VDE library or unless you have run out of some resource
such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSDELELEM\CMS error when deleting element <EMPHASIS>(element) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when deleting the indicated module's CMS
element.
The subsequent print line shows what specific error
status CMS returned.  This error should not occur
unless you have insufficient privileges to access the
VDE library or unless you have run out of some resource.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSDELGEN\CMS error when deleting generation <EMPHASIS>(generation) (<EMPHASIS>(generation)) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when deleting the indicated module generation.
The subsequent print line shows what specific error
status CMS returned.  This error should not occur
unless you have insufficient privileges to access the
VDE library or unless you have run out of some resource
such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSDUPGEN\duplicate CMS generation <EMPHASIS>(generation) found for module <EMPHASIS>(module)      possible CMS error )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated CMS generation was found more than once
for the same CMS element; the cause is probably an error
in CMS.  The affected generation is not recorded in the
VDE database.
<MSG_TEXT>(User Action)
Examine the CMS library and consult a CMS expert.

<MSG>(CMSFETCH\CMS error when fetching CMS element for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when fetching the CMS element for the indicated
module.  The subsequent print line shows what specific
error status CMS returned.  This error should not occur
unless you have insufficient privileges to access the
VDE library or unless you have run out of some resource
such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSINSGEN\CMS error inserting generation <EMPHASIS>(generation) of element <EMPHASIS>(element) into class <EMPHASIS>(class) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error status
when inserting a CMS element generation into the indicated
class.  The subsequent print line shows what specific error
status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSLIBEMPTY\the CMS library <EMPHASIS>(library) contains no elements )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Since the CMS library specified with the /CMS_LIBRARY
qualifier is empty, no modules are created.
<MSG_TEXT>(User Action)
None.

<MSG>(CMSMODCLASS\CMS error modifying the class name <EMPHASIS>(class) to <EMPHASIS>(class) in facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error status
when modifying a CMS class name in the indicated facility.
The subsequent print line shows what specific error status
CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSNOCLASS\CMS class <EMPHASIS>(class) does not exist for facility <EMPHASIS>(facility) Unable to modify CMS class name )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated CMS class does not exist in the indicated
facility, so we are not able to modify its name.
<MSG_TEXT>(User Action)
None.

<MSG>(CMSREMGEN\CMS error removing element <EMPHASIS>(element) from class <EMPHASIS>(class) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error status
when removing a CMS element generation from the indicated
class.  The subsequent print line shows what specific error
status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSREPLACE\CMS error when replacing CMS element for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when replacing the CMS element for the indicated
module.  The subsequent print line shows what specific
error status CMS returned.  This error should not occur
unless you have insufficient privileges to access the
VDE library or unless you have run out of some resource
such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSRESERVE\CMS error when reserving CMS element for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when reserving the CMS element for the indicated
module.  The subsequent print line shows what specific
error status CMS returned.  This error should not occur
unless you have insufficient privileges to access the
VDE library or unless you have run out of some resource
such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(CMSSETLIB\CMS error when setting CMS library for facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when making the CMS library for the indicated
facility the current CMS library.  The subsequent print
line shows what specific error status CMS returned.
This error should not occur unless you have insufficient
privileges to access the VDE library.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges to perform the action, you must correct the
deficiency.  Then try the command again.  If the problem
appears to be due to an internal VDE error, submit a
problem report.

<MSG>(CMSSHOWCLASS\CMS error when retrieving CMS class information in library <EMPHASIS>(library) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when retrieving CMS class information for
the indicated CMS library.  The subsequent print line
shows what specific error status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSSHOWDESGEN\CMS error when retrieving CMS generation of element <EMPHASIS>(element) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when retrieving CMS generation information for
the indicated CMS element.  The subsequent print line
shows what specific error status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSSHOWELEM\CMS error when retrieving CMS element in library <EMPHASIS>(library) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when retrieving CMS element information for
the indicated CMS library.  The subsequent print line
shows what specific error status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSSHOWHIST\CMS error when retrieving CMS history in library <EMPHASIS>(library) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when retrieving CMS history information for
the indicated CMS library.  The subsequent print line
shows what specific error status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSSHOWRES\CMS error when retrieving CMS reservations in library <EMPHASIS>(library) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when retrieving CMS reservation information for
the indicated CMS library.  The subsequent print line
shows what specific error status CMS returned.
<MSG_TEXT>(User Action)
If the problem appears to be due to an internal VDE
error, submit a problem report.

<MSG>(CMSSTART\starting retrieval of CMS information for facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE is starting to retrieve module, generation, and
reservation information from the exiting CMS library
for the indicated facility.  After this information is
retrieved, it will be included in the VDE database.
<MSG_TEXT>(User Action)
None.

<MSG>(CMSVARLET\all CMS variant letters in use; none left for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
All CMS variant letters up to "Z" are already in use for
the indicated module.  Hence the current REPLACE operation
cannot be performed.
<MSG_TEXT>(User Action)
Submit a problem report.  This is a very unlikely situation,
but there is no known workaround.  Additional VDE code is
needed to handle this situation.

<MSG>(CMSVERGEN\CMS error reading class membership list when verifying generation <EMPHASIS>(generation) (<EMPHASIS>(spec)) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
CMS (Code Management System) has returned an error
status when reading the class membership list for
the indicated module generation. The subsequent print
line shows what specific error status CMS returned.
This error should not occur unless you have insufficient
privileges to access the VDE library or unless you have
run out of some resource such as disk space.
<MSG_TEXT>(User Action)
If the error is caused by not having sufficient
privileges or resources to perform the action, you
must correct the deficiency.  Then try the command
again.  If the problem appears to be due to an
internal VDE error, submit a problem report.

<MSG>(COMMAND\command <EMPHASIS>(command) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you of the particular command that
was (or was not) executed.  This message is normally
associated with other messages or errors of some sort.
<MSG_TEXT>(User Action)
If unable to resolve the basic error, please contact VDE
support for assistance.  Please include any information that
may be useful or relevent in duplicating the problem.

<MSG>(COMMIT\database transaction has successfully committed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The database transaction associated with the current
command has successfully committed, thus ensuring that
all changes have been written to the VDE database.
<MSG_TEXT>(User Action)
Feel relieved.

<MSG>(COMNOTDEF\command "<EMPHASIS>(command-text)" not defined )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
DELETE/COMMAND issues this message when the command you request
to delete was not defined.
<MSG_TEXT>(User Action)
Use SHOW SYMBOL/DEFINED to display all defined commands.

<MSG>(COMPFAIL\compilation of <EMPHASIS>(module) completed with errors )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The compile step for the indicated module completed with
one or more errors.  The compiler's output (on your
terminal or in the step's log file) gives more detail on
the errors it detected.
<MSG_TEXT>(User Action)
Correct the errors and resubmit the compilation or build job.

<MSG>(COMPSUCC\compilation of <EMPHASIS>(module) completed successfully )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The compilation of the indicated module completed successfully.
<MSG_TEXT>(User Action)
None.

<MSG>(COMSTEPADDED\compile step for <EMPHASIS>(module) added to database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated compile step
has been added to the VDE database.  This message is only
issued when you use the /LOG qualifier on the CREATE STEP
command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(COMSTEPDEL\compile step for module <EMPHASIS>(module) deleted from database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the compile step for the
indicated module has been deleted from the VDE database.
This means that all build dependency information for that
build step has been deleted.  This message is only issued
when you use the /LOG qualifier on the DELETE STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(COMSTEPMOD\compile step for module <EMPHASIS>(module) modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that build dependency information
for the indicated compile step has been modified in the
VDE database.  This message is only issued when you use
the /LOG qualifier on the MODIFY STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(COMTERMEOF\command terminated by CTRL/Z or end-of-file on input )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current command has been terminated because the
user entered a CTRL/Z in response to a query for
additional information needed to execute the command.
Alternatively, an end-of-file may have been encountered
in the current input file in response to such a query.
This error can also appear if an attempt is made to
use DCL command procedure with a VDE kept subprocess.
<MSG_TEXT>(User Action)
Not an error since a user may intentionally terminate
commands in this way.  To execute the original command,
reenter the command and supply all required information.
If using a DCL command procedure to issue VDE commands,
disable the use of the VDE kept subprocess, or switch
to a VDE command procedure.

<MSG>(CONCURRES\concurrent reservation <EMPHASIS>(reservation) of <EMPHASIS>(module) by user <EMPHASIS>(user) already present )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are reserving a module which is already reserved by
another user (possibly yourself).  That reservation allows
concurrent reservations.
<MSG_TEXT>(User Action)
This is an informational message which appears when you
are creating a concurrent reservation.  This message
informs you of each already existing reservation for the
same module that covers at least one common stream.

<MSG>(CONFACC\unable to access notes conference )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Check the notes conference for general accessability,
and -- if conference membership is needed -- determine
if you  are a member of the conference from the node on
which you are running VDE.
<MSG_TEXT>(User Action)
See the accompanying message(s).

<MSG>(CONFLICT\conflicting qualifers and/or keywords specified )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is issued when VDE detects conflicting
qualifiers and/or keywords within the same command.
<MSG_TEXT>(User Action)
Verify the intention of your command and see if the use of
a specific qualifier or keyword may exclude the use of one
of the other qualifiers and/or keywords.
See <reference>(VDE_MANUAL_NAME) for assistance with the
command syntax.

<MSG>(CONFMEM\check conference file accessability and membership )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Check the notes conference for general accessability,
and -- if conference membership is needed -- determine
if you are a member of the conference from the node on
which you are running VDE.
<MSG_TEXT>(User Action)
See the accompanying message(s).

<MSG>(CONFNAM\conference file name <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This is the name of the notes conference.
<MSG_TEXT>(User Action)
See the accompanying message(s).

<MSG>(CONKEYATR\conflicting key attributes <EMPHASIS>(key-attribute) and <EMPHASIS>(key-attribute) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The recently
issued DEFINE KEY command has conflicting qualifiers such as
/NOSTATE and /LOCK_STATE.
<MSG_TEXT>(User Action)
Determine correct applicability and reissue the command.

<MSG>(CONQUAL\conflicting qualifiers /<EMPHASIS>(qualifier) and /<EMPHASIS>(qualifier) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The above mentioned qualifiers are mutually exclusive.
<MSG_TEXT>(User Action)
Verify the intention of your command and see if the use of
a specific qualifier may mutually exclude the use of other
qualifiers.

<MSG>(CONRESDEL\concurrent reservation <EMPHASIS>(reservation) of <EMPHASIS>(module) for user <EMPHASIS>(user) has been deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated concurrent
reservation has been deleted from the VDE database because
you replaced the same module.
<MSG_TEXT>(User Action)
None.  The affected users will be informed that their
reservations are deleted.  They should reserve the module
again and merge in their changes.

<MSG>(CONTINUE\attempting to continue )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
One or more quotas are below the recommended
values for VDE.  VDE will attempt to continue.
<MSG_TEXT>(User Action)
Contact system management and request that the
quotas associated with the current process be
compared to the values recommended for use
with VDE.

<MSG>(COPSTEPADDED\copy step for <EMPHASIS>(step) added to database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated copy step
has been added to the VDE database.  This message is only
issued when you use the /LOG qualifier on the CREATE STEP
command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(COPSTEPDEL\copy step for module <EMPHASIS>(module) deleted from database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the copy step for the
indicated module has been deleted from the VDE database.
This means that all build dependency information for that
build step has been deleted.  This message is only issued
when you use the /LOG qualifier on the DELETE STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(COPSTEPMOD\copy step for module <EMPHASIS>(module) modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that build dependency information
for the indicated copy step has been modified in the VDE
database.  This message is only issued when you use the
/LOG qualifier on the MODIFY STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(COPYFAIL\copy of <EMPHASIS>(module) completed with errors )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The copy step for the indicated module completed with
one or more errors.  The step's output (on your terminal
or in the step's log file) gives more detail on the errors
it detected.
<MSG_TEXT>(User Action)
Correct the errors and resubmit the copy step or build job.

<MSG>(COPYSUCC\copy of <EMPHASIS>(module) completed successfully )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The copy step for the indicated module completed successfully.
<MSG_TEXT>(User Action)
None.

<MSG>(CREDIRFAI\create directory failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A directory specification on a VDE command is not
syntactically correct.  This message is also printed
if a logical name (such as VDE$LIBRARY) that is supposed
to be bound to a directory specification is not bound to
a syntactically correct directory specification.
<MSG_TEXT>(User Action)
Reenter the VDE command with a valid directory specification
or define the logical name to be bound to a valid directory
specification.

<MSG>(CRELNMFAI\failed to define logical name <EMPHASIS>(lnmdsc) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you of the particular logical name
creation that failed.  This message is normally associated
with other messages or errors of some sort.
<MSG_TEXT>(User Action)
If unable to resolve the basic error, please contact VDE
support for assistance.  Please include any information that
may be useful or relevent in duplicating the problem.

<MSG>(CTXADDED\context <EMPHASIS>(context) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated context
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the CREATE CONTEXT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(CTXDEL\context <EMPHASIS>(context) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated context has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE CONTEXT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(CTXDELARCH\context <EMPHASIS>(##) contains deleted architecture <EMPHASIS>(architecture) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to set the indicated context, but the
default architecture specified by the context has been
deleted.  As a result, the context cannot be set.
<MSG_TEXT>(User Action)
Redefine the context to reference an architecture that
has not been deleted.  Then reissue the command.

<MSG>(CTXDELFAC\context <EMPHASIS>(context) contains deleted facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to set the indicated context, but the
default facility specified by the context has been deleted.
As a result, the context cannot be set.
<MSG_TEXT>(User Action)
Redefine the context to reference a facility that has not
been deleted.  Then reissue the command.

<MSG>(CTXDELSTRM\context <EMPHASIS>(context) contains deleted stream <EMPHASIS>(context) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to set the indicated context, but the
default stream specified by the context has been deleted.
As a result, the context cannot be set.
<MSG_TEXT>(User Action)
Redefine the context to reference a stream that has not
been deleted.  Then reissue the command.

<MSG>(CTXEXISTS\context <EMPHASIS>(context) already exists in database; context not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated context name was specified on a CREATE CONTEXT
command, but an entry for that context is already present
in the database.  Hence a new entry was not created for that
context.  Alternatively, the indicated name was specified as
the new name for an existing context on the MODIFY CONTEXT
command, but another context already has the requested new
name.  Hence the name of the existing context could not be
changed to the new name.
<MSG_TEXT>(User Action)
If you entered the wrong context name, reenter the command
with the correct name.  If you entered the right context
name, use the SHOW CONTEXT command to display the database
information for that context.  If you are not satisfied
with that information, use the MODIFY CONTEXT command to
change it.

<MSG>(CTXMOD\information for context <EMPHASIS>(context) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
context has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
CONTEXT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(CTXNOTFOUND\context <EMPHASIS>(context) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated context name was entered on a SHOW CONTEXT
command, but no such context was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated context does not exist in the database.

<MSG>(CTXSYNTAX\invalid context name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the context name
is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the context name using only alphanumeric,
underscore, dollar sign and hyphen characters.

<MSG>(CULPRIT\reserved by user <EMPHASIS>(user) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
the module is reserved by the specified user.  The
reservation was requested in the current stream, or
in an ancestor of the current stream.
<MSG_TEXT>(User Action)
This message is informational, and should accompany one
or more other error messages.

<MSG>(DATETOOLONG\date-time value is too long; maximum length is 24: <EMPHASIS>(date)... )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A date-time value entered as a command parameter is too
long because it exceeds the maximum length indicated in
the message.
<MSG_TEXT>(User Action)
Reissue the command with a shorter date-time value.

<MSG>(DBCNV\converting database format from <EMPHASIS>(oldver) to <EMPHASIS>(newver) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to display the status of a database
conversion operation.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(DBCREATED\database <EMPHASIS>(db) has been created )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that a new library database, and
associated database files, directories, and CMS libraries
has been created.
<MSG_TEXT>(User Action)
None required.

<MSG>(DBFMT\database format is <EMPHASIS>(ver) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to display the current version of a
database, or the status of a database conversion operation.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(DBGCMSGEN\at <EMPHASIS>(codept), letflg <EMPHASIS>(bool), item1 <EMPHASIS>(itm1), item2 <EMPHASIS>(did) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays various internal process-related
values used within VDE.  This message should appear only
during VDE testing, and should be displayed only by debugging
versions of VDE.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(DBGCMSTXT\at <EMPHASIS>(codept), expected <EMPHASIS>(gen) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays various internal process-related
values used within VDE.  This message should appear only
during VDE testing, and should be displayed only by debugging
versions of VDE.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(DBGDB\debugging database: <EMPHASIS>(param1), <EMPHASIS>(param2) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used during development and displays
where the behaviour of a debugging or prototype VDE
image database operation differs from that of a
production VDE image.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(DBGLNMBAT\debug logical name VDE$BATCH_MODE: <EMPHASIS>(mode) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates the batch mode setting of VDE,
and should appear only during VDE testing.  This message
is displayed only by debug versions of VDE, and this
logical name is translated only by debug versions.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(DBGLNMDAT\debug logical name VDE$DATE_TIME: <EMPHASIS>(mode) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates the date-time setting of VDE,
and should appear only during VDE testing.  This message
is displayed only by debug versions of VDE, and this
logical name is translated only by debug versions.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(DBGLNMUSR\debug logical name VDE$USERNAME: <EMPHASIS>(mode) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates the username setting of VDE,
and should appear only during VDE testing.  This message
is displayed only by debug versions of VDE, and this
logical name is translated only by debug versions.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(DBGNOLNM\unable to translate <EMPHASIS>(logicalname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to translate a mandatory logical name.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE running contains debug-only images.  Correct the
error in the date-time logical name value and reissue
the command.

<MSG>(DBGQUALMSK\qualifier mask <EMPHASIS>(qualmsk1) <EMPHASIS>(qualmsk2) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays the contents of an internal
bitmask during program execution.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(DBGWAYPT\debug waypoint <EMPHASIS>(waypoint) reached )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays a waypoint, and the associated
waypoint value, encountered during program execution.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(DBGXLAC\debug <EMPHASIS>(waypoint) reached; text: <EMPHASIS>(text) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays a waypoint, and the associated
waypoint value, encountered during program execution.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(DBGXLXL\debug <EMPHASIS>(waypoint) reached; value: <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays a waypoint, and the associated
waypoint value, encountered during program execution.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(DCLBUFOVFL\DCL command line being generated is too long for buffer )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Some command which generates a DCL command file to perform
part of its actions generated a DCL command line that is
too long for its buffer; this normally means that the line
is excessively long since the buffer size is ample for
normal use.
<MSG_TEXT>(User Action)
Change the command line specification in the script for it.

<MSG>(DCLERROR\error status returned by spawned DCL <EMPHASIS>(DCL) command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has run a DCL command in a spawned subprocess and that
command has returned an error status.  The command's status
is displayed by the following status line.
<MSG_TEXT>(User Action)
Determine the cause of the problem, correct it, and retry
the VDE command.

<MSG>(DCLTRUNC\DCL command line from script truncated; line too long )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A script has generated a DCL command line that is too long
and has been truncated.  Since the editing buffer is of
ample size for normal use, the script tried to generate an
excessively long DCL command line.
<MSG_TEXT>(User Action)
Correct the script to generate a shorter DCL command line.

<MSG>(DEFARCH\architecture <EMPHASIS>(architecture) not deleted; you cannot delete default architecture )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated architecture,
namely the current default architecture, has not been
deleted from the database.  You are not allowed to delete
the default architecture.  This prohibition prevents you
from accidentally deleting all architectures, especially
when using a wildcarded architecture name specification.
There is thus no way to delete all architectures from the
database.  (If you could delete all architectures, the
library would become useless since it could not contain
any modules.)
<MSG_TEXT>(User Action)
If you want to delete a given architecture from the database,
set your default architecture to another architecture that you
want to keep.  Then issue the DELETE ARCHITECTURE command.

<MSG>(DEFKEY\<EMPHASIS>(state-name) key <EMPHASIS>(key-name) has been defined )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Issued by DEFINE/KEY to inform the user that the specific
key definition has been bound.
<MSG_TEXT>(User Action)
If you did not wish to see this message, issue /NOLOG with your
DEFINE command.

<MSG>(DEFKEYERR\error defining <EMPHASIS>(state-name) key <EMPHASIS>(key-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE uses the SMG screen management facilities for the
purpose of  managing key bindings. In this instance, the
call to SMG$ADD_KEY_DEF returned a bad status.
<MSG_TEXT>(User Action)
First, try to interpret the reason for the SMG error. If it
can be understood, then try to see if you may fix it locally.
Otherwise, please contact VDE support for assistance.

<MSG>(DELKEY\<EMPHASIS>(state-name) key <EMPHASIS>(key-name) has been deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Issued by DELETE/KEY to inform the user that the specific
key definition has been deleted.
<MSG_TEXT>(User Action)
If you do not wish to see this message, issue /NOLOG with your
DELETE command.

<MSG>(DELKEYERR\error in processing DELETE/KEY command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE uses the screen management
facilities, SMG, for the purpose of managing key
bindings. In this instance, a call to either
SMG$LIST_KEY_DEFS or SMG$DELETE_KEY_DEF has returned a
bad status.
<MSG_TEXT>(User Action)
First, try to interpret the reason for the SMG error. If it
can be understood, then try to see if you may fix it locally.
Otherwise, please contact VDE support for assistance.

<MSG>(DEPNOTUPDATE\dependency information not updated for build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The dependency information for the most recent build step
has not been updated in the VDE database because the
build step did not automatically collect dependency
information.  Hence the existing dependency information
is kept without change in the database.
<MSG_TEXT>(User Action)
None.

<MSG>(DEPUPDATE\dependency information updated for build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The dependency information for the most recent build step
has been updated in the VDE database based on dependency
data collected during the execution of the build step.
<MSG_TEXT>(User Action)
None.

<MSG>(DEVOSYNCH\executing synch command: <EMPHASIS>(dclcmd) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays the synchronization command being
spawned by VDE.  This message should appear only during
VDE testing, and should be displayed only by debugging
versions of VDE.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(DIRADDED\directory specification <EMPHASIS>(spec) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated directory
specification has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the SET DIRECTORY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(DIRCREATED\directory <EMPHASIS>(directory) has been created )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated directory has just
been created as your VDE scratch directory.
<MSG_TEXT>(User Action)
Check the newly created directory specification and delete the
directory if you do not wish to keep it.  To change the default
VDE scratch directory specification, define VDE$SCRATCH.

<MSG>(DIRDEL\directory specification <EMPHASIS>(spec) deleted from database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated stream root
or facility root directory specification has been deleted
from the VDE database.  This message is only issued when
you use the /LOG qualifier on the CANCEL DIRECTORY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(DIREXPBAD\directory filename expansion bad )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
internal state information for VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Correct the cause of the VDE$_INVDIRSPEC error.

<MSG>(DIREXPFAI\directory filename expansion failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
internal state information for VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Correct the cause of the VDE$_INVDIRSPEC error.

<MSG>(DIRFILFAI\directory filename conversion failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
internal state information for VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Correct the cause of the VDE$_INVDIRSPEC error.

<MSG>(DIRFILNOTDEL\unable to delete directory file <EMPHASIS>(directory) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated directory
file was not deleted for some reason, such as insufficient
privileges.
<MSG_TEXT>(User Action)
Use DCL commands to check the security on the directory file,
and take the appropriate action to delete it if possible.

<MSG>(DIRNOTFOUDCL\directory location not found for script's DCL command file )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The subdirectory in the VDE library that should be used
for the DCL command file that the current script generates
is not found in the database.  This message indicates that
some required subdirectory is not present in the directory
tree for the current development stream.
<MSG_TEXT>(User Action)
Create the directory tree or correct the directory structure
for the current stream or stream and facility.  Then
reissue the command that invokes the script.

<MSG>(DIRNOTFOULOG\directory location not found for build-step log file )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The subdirectory in the VDE library that should be used
for the log file for the current build step is not found
in the database.  This message indicates that some required
subdirectory is not present in the directory tree for the
current development stream.
<MSG_TEXT>(User Action)
Create the directory tree or correct the directory structure
for the current stream or stream and facility.  Then
reissue the command that executes the build step.

<MSG>(DIRNOTFOUND\directory specification to cancel not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the directory specification
you are trying to cancel with the CANCEL DIRECTORY command
does not exist in the VDE database.  This message is only
issued when you use the /LOG qualifier on the CANCEL
DIRECTORY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(DIRNOTFOUSCRP\directory location not found by script function <EMPHASIS>(function) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current script has invoked the indicated script
function (such as $DIR or $FACROOT), but the directory
location specified with that function invocation is not
found in the VDE database.  This may mean that the
directory tree for the specified stream or facility
has not been created, or that the function invocation
specifies a directory symbol that is not used for that
stream and facility.
<MSG_TEXT>(User Action)
Create the directory tree for the facility or stream, or
correct the directory symbol name in the function call.
Then reissue the command that invokes the script.

<MSG>(DIRSPECREQ\directory specification required for stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A root directory specification for the indicated stream
is required on the CREATE STREAM command but was not
specified.  You need to use the /DIRECTORY qualifier to
specify the root directory for the stream, or you need
to enter that directory specification when prompted for
it.  This message is only given if an earlier
SET DIRECTORY/PROMPT command has specified that the
CREATE STREAM command should prompt for the directory
specification if the /DIRECTORY qualifier is missing.
<MSG_TEXT>(User Action)
Enter a directory specification for the stream root
directory when prompted for it or reissue the CREATE
STREAM command with the /DIRECTORY qualifier.

<MSG>(DIRTOOLONG\directory specification is too long; maximum length is 255 )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A directory specification entered as a command parameter
is too long because it exceeds the maximum length indicated
in the message.
<MSG_TEXT>(User Action)
Reissue the command with a shorter directory specification.

<MSG>(DIRTREFAI\directory tree conversion failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
internal state information for VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Correct the cause of the VDE$_INVDIRSPEC error.

<MSG>(DIRTRENOTDEL\not all files deleted in directory tree <EMPHASIS>(tree) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that not all files in the indicated
directory tree were deleted for some reason, such as
insufficient privileges.
<MSG_TEXT>(User Action)
Use DCL commands to check the security on the remaining files
in the directory tree, and take the appropriate action to
delete them if possible.

<MSG>(DUPLNAME\duplicate name in list not allowed: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have entered the same name twice in a comma list where
such duplicates are not allowed.  Possibly, you may have
mistyped one of the names.
<MSG_TEXT>(User Action)
Correct the error and reissue the command without any
duplicates.

<MSG>(EDITUNDEF\your editor is undefined; editor cannot be invoked )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The command you have entered is attempting to invoke an
editor to read or edit a file, but you have not specified
what editor to invoke.  You must specify the editor you
want VDE to use by entering the SET EDITOR command.
<MSG_TEXT>(User Action)
Use the SET EDITOR command to define the editor you want
VDE to invoke for all commands to put you in an editor.

<MSG>(EDITUPDATE\default editor definition updated in the VDE database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Your default editor has been updated in the VDE database.
The default editor is the editor that is initially defined
each time you start a VDE session.
<MSG_TEXT>(User Action)
None.  This is an informational message only.

<MSG>(ELENOTFOUNDCMS\element <EMPHASIS>(element) not found in CMS library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module
generation does not have an element in the CMS library.
<MSG_TEXT>(User Action)
Use the VERIFY GENERATION/RECOVER command to attempt
recovery of the missing generation or locate missing
element from a backup and manually insert the
element and generations in the database.

<MSG>(ERRASSIGN\the attempt to acquire an I/O channel for VDE failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A bad status was returned from a SYS$ASSIGN service call.
VDE needs to acquire I/O channels to do I/O.
In this case, VDE failed to acquire such a channel.
<MSG_TEXT>(User Action)
Check your process's quotas. If this problem cannot be
resolved locally, please contact VDE support for
assistance.

<MSG>(ERRCRELNM\unable to create a logical name )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE creates logical names for input and output redirection.
<MSG_TEXT>(User Action)
Check your process's quotas.  If this problem cannot be
resolved locally, please contact VDE support for assistance.

<MSG>(ERRDEASSIGN\attempt to deassign an I/O channel acquired by VDE failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE wanted to deassign an I/O channel that was acquired.
This error notes the failure of the SYS$DASSGN system
service, probably due to an invalid channel.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.

<MSG>(ERRDIRSPEC\error in directory or file specification <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
There is a syntax error or other error in the indicated
directory or file specification.  The RMS message that
follows explains the error in more detail.
<MSG_TEXT>(User Action)
Correct the error in the directory or file specification
and reissue the command.

<MSG>(ERRFAO\unable to format output string )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error was returned from a call to SYS$FAO.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.

<MSG>(ERRQIOW\error from SYS$QIOW )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A bad status was returned from a call to SYS$QIOW.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.

<MSG>(ERRSMG\error returned from a call to the Screen Management Facility (SMG) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A bad status was returned from a call to a SMG routine.
This could be a result of any number of things which may or
may not be a VDE problem.
<MSG_TEXT>(User Action)
Check the setup of the terminal which might cause
SMG some problem.  If the error still cannot be explained
or resolved, please contact VDE support for assistance.

<MSG>(ERRWRIFIL\error writing file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The output could not be written to the appropriate file.
<MSG_TEXT>(User Action)
Determine if there is any external interference with RMS
writing to the specified file.  If no interference can
be found, please contact VDE support for assistance.

<MSG>(EXARANGE\hexadecimal number not valid; valid range is <EMPHASIS>(number) to <EMPHASIS>(number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Illegal hexadecimal range provided as input.
<MSG_TEXT>(User Action)
Verify that the provided hexadecimal range is in an accepted
format.

<MSG>(EXPGENDIFF\expected generation expression <EMPHASIS>(expression) differs from actual <EMPHASIS>(expression) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
When you reserved the module you are replacing, the
RESERVE command displayed the expected replace-time CMS
generation expression of the new module generation.
However, the actual CMS generation expression that VDE
assigned during the current replacement differs from that
expected generation expression.  This situation is normal
because VDE cannot predict the actual replace-time CMS
generation expression when you reserve the module; it
can only tell you the most likely generation expression.
By the time you replace the module, various circumstances
can change the appropriate generation expression to use.
<MSG_TEXT>(User Action)
None.  This message is informational only.  However, if
you used the expected CMS generation expression in code
comments, you may have to change those comments.

<MSG>(EXPGENEXPR\expected generation expression at replacement is <EMPHASIS>(generation) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
When you replace the module you just reserved, the new
generation of the module is expected to have the indicated
CMS generation expression.  You may use this generation
expression as an <QUOTE>(audit trail identifier) in the
comments in your code if your project uses that convention.
The indicated generation expression may differ from the
one that VDE actually assigns when you replace the module,
but only in certain unusual circumstances.
<MSG_TEXT>(User Action)
None.  This message is informational only.

<MSG>(EXPGENLONG\expected CMS generation expression is too long )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The expected replace-time CMS generation expression for
the module you are reserving will be longer than 16
characters, which is longer than CMS allows.  As a result,
you cannot reserve the module.
<MSG_TEXT>(User Action)
This error indicates that you have reserved and replaced
modules on too many nested non-main streams.  You should
create new streams off the main development stream and
place the offending generations there so that they have
CMS generation expressions of modest size.  Even though
you cannot reserve the generation in question, you can
still fetch it out and replace it into the new streams.

<MSG>(FACADDED\facility <EMPHASIS>(facility) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated facility
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the CREATE FACILITY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(FACDEL\facility <EMPHASIS>(facility) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated facility has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE FACILITY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(FACEXISTS\facility <EMPHASIS>(facility) already exists in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated facility name was specified on a CREATE
FACILITY command, but an entry for that facility is already
present in the database.  Alternatively, the indicated name
was specified as the new name for an existing facility using
the MODIFY FACILITY command, but another facility already
has the requested new name.  In either case, the command
fails and the facility is not created or modified.
<MSG_TEXT>(User Action)
If you entered the wrong facility name, reenter the command
with the correct name.  If you entered the right facility
name, use the SHOW FACILITY command to display the database
information for that facility.  If you are not satisfied
with that information, use the MODIFY FACILITY command to
change it.

<MSG>(FACMOD\information for facility <EMPHASIS>(facility) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
facility has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
FACILITY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(FACNOTDEL\facility <EMPHASIS>(facility) not deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to delete a facility that
cannot be deleted.  Additional messages are normally
included with this message, and these messages
indicate why the facility cannot be deleted.
<MSG_TEXT>(User Action)
Resolve the problem(s) flagged by the other error
messages, and reenter the DELETE FACILITY command.

<MSG>(FACNOTFOUND\facility <EMPHASIS>(facility) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated facility name was entered on a SHOW FACILITY
command, but no such facility was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated facility does not exist in the database.

<MSG>(FACNOTMT\facility contains modules )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The specified facility contains modules.
<MSG_TEXT>(User Action)
The requested operation is prohibited due to the presence
of modules in the facility.

<MSG>(FACSYNTAX\invalid facility name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the facility name
is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the facility name using only alphanumeric,
underscore, dollar sign and hyphen characters.

<MSG>(FAMILY\unable to deallocate: siblings or children present )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Something deep within VDE has attempted to deallocate
a data structure that has siblings or children.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include any
information that may be useful or relevent in duplicating the
problem.

<MSG>(FCBERR\internal VDE FCB error in <EMPHASIS>(VDE-internal-identifier) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an internal inconsistency.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(FCBWRONG\internal error; <EMPHASIS>(access) access failed in <EMPHASIS>(VDE-internal-identifier) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an internal inconsistency.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(FETCHED\generation <EMPHASIS>(generation) fetched from library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module and
generation has been fetched from the current library.
This message is only issued when you use the /LOG
qualifier on the FETCH command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(FILCOPLIB\file <EMPHASIS>(file) copied to library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated file has
been copied into the VDE library by the REPLACE command.
When this is done, the file has been included in the
appropriate CMS element, but has not yet been recorded
in the VDE database.  This message is only issued when
you use the /LOG qualifier on the REPLACE command for
an immediate replacement.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(FILCOPSTAG\file <EMPHASIS>(file) copied to staging area )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated file has
been copied into a VDE staging area by the REPLACE
command.  This message is only issued when you use the
/LOG qualifier on the REPLACE command for a queued
replacement.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(FILENOTFOUND\file not found: <EMPHASIS>(file) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated file was requested through a VDE command,
but could not be found.  Hence the current command cannot
perform the requested action.
<MSG_TEXT>(User Action)
Do without the file or determine why the file is missing
and correct the problem.

<MSG>(FILQUE\print file queued to <EMPHASIS>(queue-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This this message informs the user where the file
was queued for printing.
<MSG_TEXT>(User Action)
Ensure that the file is placed on the appropriate queue.

<MSG>(FILREADERR\unable to read file <EMPHASIS>(file) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to read a line of text from
an input file.  A more specific error message follows
this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(FILWRITERR\unable to write file <EMPHASIS>(file) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to write a line of text to
an output file.  A more specific error message follows
this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(FIRGENNODEL\generation <EMPHASIS>(generation) is first generation of module; cannot be deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to delete the first generation of a module
with the DELETE GENERATION command, which VDE does not
allow.  If you want to delete all generations of a module,
you must delete the entire module with the DELETE MODULE
command.
<MSG_TEXT>(User Action)
If you mistyped the generation number, reenter it correctly.
If you want to delete all generations of the module, use
the DELETE MODULE command.

<MSG>(FIRNUMMAY\first number of a range may not be less than <EMPHASIS>(number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Some integers provided in the command line must be greater
than a given "n".
<MSG_TEXT>(User Action)
Verify that the appropriate "n" was given in the command line.

<MSG>(FIRNUMRAN\first number of a range must be less than the second )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
When providing a
range in the format n[:m], "n" must be less than "m".
<MSG_TEXT>(User Action)
Correct the range description and reissue the command.

<MSG>(FLAVORPIDS\flavor <EMPHASIS>(flavor), pid <EMPHASIS>(pid), master <EMPHASIS>(mpid), parent <EMPHASIS>(ppid) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays various internal process-related
values used within VDE.  This message should appear only
during VDE testing, and should be displayed only by debugging
versions of VDE.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(FOLDADDED\fold record <EMPHASIS>(record) for module <EMPHASIS>(module) added to database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
had a fold record created in the current VDE database.
This message is only issued when you use the /LOG
qualifier on the CREATE FOLD command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(FOLDDEL\fold record <EMPHASIS>(record) for module <EMPHASIS>(module) has been deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
had a fold record deleted from the current VDE database.
This message is only issued when you use the /LOG
qualifier on the DELETE FOLD command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(FOLDEXP\fold record for <EMPHASIS>(fold) expected for stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE expects to generate a fold
record for the indicated stream.  The fold record will be
generated when this module change is approved and performed
by the project leader -- when the queued replacement is
performed.  Because there may be a delay before the
replacement is performed by the project leader and
because the project leader may reject the replacement, the
fold record will not immediately appear via commands such
as SHOW REPLACEMENT.  The fold will be generated when VDE
sends you the notification that the replacement has been
performed.  This message is only issued when you use the
/LOG qualifier on the REPLACE command, and only for a queued
replacement from which VDE expects to generate a fold record.
<MSG_TEXT>(User Action)
You may/will need to resolve the fold record that will
(eventually) be generated by this replacement.  Use the
/NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(FOLDIDREQ\fold identifier required for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have multiple fold records for the indicated module.
You must therefore specify a fold identifier with the
/IDENTIFICATION or /FOLD qualifier (depending on the
command) to uniquely indicate to which fold record you
want the command to apply.
<MSG_TEXT>(User Action)
Reissue the command with the /IDENTIFICATION or /FOLD
qualifier to indicate the specific fold record to which
you want the command to apply.

<MSG>(FOLDIDUSED\fold identifier <EMPHASIS>(identifier) already used for module <EMPHASIS>(module)      attempt to create fold record has failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to create a fold record for a module using
the same fold identifier as you have used on a previous
fold record for the same module in the same development
stream.  This is not allowed, since fold identifiers must
be unique.
<MSG_TEXT>(User Action)
Reissue the CREATE FOLD command with a different fold
identifier specified on the /IDENTIFICATION qualifier.
Alternatively, you can omit the /IDENTIFICATION qualifier,
in which case VDE will assign a unique identifier for you.

<MSG>(FOLDINSTRM\generation <EMPHASIS>(generation) must be folded into stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that you must manually fold the
indicated module generation into the indicated development
stream in order to propagate the changes in that generation
into the stream.  VDE cannot propagate the changes
automatically because the module has already diverged
between that stream and its predecessor.  This message
is only issued when you use the /LOG qualifier on the
REPLACE or PERFORM REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(FOLDMOD\fold record <EMPHASIS>(record) for module <EMPHASIS>(module) modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that fold record for the indicated
module has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the
MODIFY FOLD command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(FOLDNOTFOUND\fold record <EMPHASIS>(record) not found for module <EMPHASIS>(module) and stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to reference a fold record for the indicated
module in the indicated development stream, but there is no
such fold record.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated module has no fold records in the
indicated stream.

<MSG>(FROMDIREMPTY\the directory <EMPHASIS>(directory) specified with /FROM_DIRECTORY is empty )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Since the directory specified with the /FROM_DIRECTORY
qualifier is empty, no modules are created.
<MSG_TEXT>(User Action)
None.

<MSG>(GBLSECNAM\communications global section name: <EMPHASIS>(gblsecnam) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you of the name of the communications
section used within VDE.  This message is associated with a
more serious error of some sort.  Resolve the basic error first.
<MSG_TEXT>(User Action)
If unable to resolve the basic error, please contact VDE
support for assistance.  Please include any information that
may be useful or relevent in duplicating the problem.

<MSG>(GENDEL\generation <EMPHASIS>(generation) deleted from stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated generation
has been deleted from the indicated development stream.
This message is only issued when you use the /LOG qualifier
on the DELETE GENERATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(GENDELLIB\generation <EMPHASIS>(generation) deleted from library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated generation
has been deleted from the library.  This message is only
issued when you use the /LOG qualifier on the DELETE
GENERATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(GENINSERT\generation <EMPHASIS>(generation) inserted into stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated generation
has been inserted into the indicated development stream.
This message is only issued when you use the /LOG qualifier
on the CREATE MODULE or INSERT GENERATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(GENMOD\information for generation <EMPHASIS>(generation) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
generation of the indicated module has been modified in the
VDE database.  This message is only issued when you use the
/LOG qualifier on the MODIFY GENERATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(GENNODEL\generation <EMPHASIS>(generation) cannot be deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to delete a generation of a module which is
still reachable by at least one stream and/or is not a leaf
generation (some other generation points to it as its previous
generation).  VDE does not allow a generation to be deleted
in either of these cases.
<MSG_TEXT>(User Action)
Check that you have specified the correct generation for
deletion.

<MSG>(GENNOPRED\generation <EMPHASIS>(generation) of <EMPHASIS>(module) has no predecessor )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The generation of the indicated module with the shown
CMS generation expression does not have a predecessor
generation.  As a result, the current operation cannot
be performed.  For example, the DIFFERENCES command
cannot compare generation 1 with its predecessor because
it has no predecessor.
<MSG_TEXT>(User Action)
Specify a generation that has a predecessor (normally any
generation except generation 1) and rerun the command.

<MSG>(GENNOTCLASSMEM\generation <EMPHASIS>(generation) is not a member of CMS class <EMPHASIS>(class) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated generation
is not a member of the indicated CMS class. This message
is output when a VDE stream is maintaining CMS class
membership, but the indicated generation is not a member
of that CMS class.
<MSG_TEXT>(User Action)
Use the VERIFY GENERATION/RECOVER to attempt recovery of
the class memebership for this stream.

<MSG>(GENNOTFOUNDCMS\generation <EMPHASIS>(generation) not found in CMS library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module
generation does not have a generation in the CMS library.
<MSG_TEXT>(User Action)
Use the VERIFY GENERATION/RECOVER command to attempt
recovery of the missing generation or locate missing
generation from a backup and manually insert the
generation.

<MSG>(GENNOTINSTAGE\generation not found in staging area <EMPHASIS>(area) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the module
generation is not in the library staging area
<MSG_TEXT>(User Action)
Try to locate a previous module generation by
checking with users that last had the module
reserved.

<MSG>(GENNOTQUEREPL\replacement was not queued; no staging area exists )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the module generation
has not been queued for replacement and therefore
a generation cannot be located for recovery.
<MSG_TEXT>(User Action)
Try to locate a previous module generation by
checking with users that last had the module
reserved.

<MSG>(GENNOTRECOVERED\generation <EMPHASIS>(generation) not recovered )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the module generation
has not been recovered. The message that follows will
provide more detail as to why the recovery failed.
<MSG_TEXT>(User Action)
Review the cause of the recovery failure. Try to locate
a previous module generation.

<MSG>(GENRECCLASSMEM\generation <EMPHASIS>(generation) successfully recovered into CMS class <EMPHASIS>(class) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the module generation
has been successfully recovered into the indicated
CMS class.
<MSG_TEXT>(User Action)
None required.

<MSG>(GENRECOVERED\generation <EMPHASIS>(generation) successfully recovered from <EMPHASIS>(source) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the module generation
has been successfully recovered.
<MSG_TEXT>(User Action)
None required.

<MSG>(GENREM\generation <EMPHASIS>(generation) removed from stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated generation
has been removed from the indicated development stream.
This message is only issued when you use the /LOG qualifier
on the REMOVE GENERATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(GENREPLDNF\staging directory <EMPHASIS>(directory) not found )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that reported staging directory
does not exist. Perhaps the directory was deleted as part
of a cleanup operation.
<MSG_TEXT>(User Action)
Try to locate a previous module generation by
checking with users that last had the module
reserved.

<MSG>(GENRETAINED\generation <EMPHASIS>(generation) retained in library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated generation has
been retained in the library because it is still reachable
by at least one stream.  This message is only issued when
you use the /LOG qualifier on the DELETE GENERATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(GENSUCVERIFY\generation <EMPHASIS>(generation) successfully verified )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module
generation has a corresponding generation in the CMS library
and it is a member of all the CMS classes that are being
maintained for the corresponding VDE streams.
<MSG_TEXT>(User Action)
None required.

<MSG>(GETJPI\SYS$GETJPI system service failed, unable to attach )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The ATTACH command could not continue because a failed
service call to SYS$GETJPI occurred.
<MSG_TEXT>(User Action)
Determine if there is any external interference.
If no interference can be found, then please submit a
problem report.

<MSG>(GETQUIERR\get queue information system service error for queue <EMPHASIS>(queue) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to start a build job and the VMS get
queue information ($GETQUI) system service returned an error
status.  The message that follows gives more information to
explain the error.
<MSG_TEXT>(User Action)
The action to take to correct the error depends on the
nature of the error.  You or your system manager should
correct the error and restart the build job.

<MSG>(GRPADD\module <EMPHASIS>(module) is added to group <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
been added as a member of the indicated group .  This
message is only issued when you use the /LOG qualifier
on the CREATE GROUP or MODIFY GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPADDED\group <EMPHASIS>(group) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated group
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the CREATE GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPALRMEM\module <EMPHASIS>(module) is already a member of group <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that you have attempted to add
the indicated module as a member of the indicated group,
but the module is already a member of that group.  This
message is only issued when you use the /LOG qualifier on
the MODIFY GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPDEL\group <EMPHASIS>(group) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated group has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPEXISTS\group <EMPHASIS>(group) already exists in database; group not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated group name was specified on a CREATE
GROUP command, but an entry for that group is already
present in the database.  Hence a new entry was not created
for that facility.  Alternatively, the indicated name was
specified as the new name for an existing group on the
MODIFY GROUP command, but another group already has
the requested new name.  Hence the name of the existing
group could not be changed to the new name.
<MSG_TEXT>(User Action)
If you entered the wrong group name, reenter the command
with the correct name.  If you entered the right group
name, use the SHOW GROUP command to display the database
information for that group.  If you are not satisfied
with that information, use the MODIFY GROUP command to
change it.

<MSG>(GRPMOD\information for group <EMPHASIS>(group) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
group has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPNOTFOUND\group <EMPHASIS>(group) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated group name was entered on a SHOW GROUP
command, but no such group was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated group does not exist in the
database.

<MSG>(GRPNOTMEM\module <EMPHASIS>(module) is not a member of group <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that you have tried to remove
the indicated module from the indicated group, but
the module is not a member of that group.  This
message is only issued when you use the /LOG qualifier
on the MODIFY GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPREM\module <EMPHASIS>(module) is removed from group <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
been removed from being a member of the indicated build
set.  This message is only issued when you use the /LOG
qualifier on the MODIFY GROUP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(GRPSYNTAX\invalid group name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the group name
is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the group name using only alphanumeric,
underscore, dollar sign and hyphen characters.

<MSG>(HELLO\Motif <EMPHASIS>(vdeversion) starting up )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message displays the version identification of the
VDE Motif interface in use.  This message is displayed
automatically during the VDE Motif startup.
<MSG_TEXT>(User Action)
None.

<MSG>(ICIBOGUS\intermediate conference information invalid )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed in conjunction with other
error messages, and indicates the particular failure
that occurred.
<MSG_TEXT>(User Action)
Resolve the basic error.  If unable to resolve the
error, please contact VDE support for assistance.

<MSG>(ICIGONE\intermediate conference information not found )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed in conjunction with other
error messages, and indicates the particular failure
that occurred.
<MSG_TEXT>(User Action)
Resolve the basic error.  If unable to resolve the
error, please contact VDE support for assistance.

<MSG>(ICIPARSE\parse of intermediate conference information failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed in conjunction with other
error messages, and indicates the particular failure
that occurred.
<MSG_TEXT>(User Action)
Resolve the basic error.  If unable to resolve the
error, please contact VDE support for assistance.

<MSG>(ILLDEPFUN\Illegal dependency function passed to module VDE$REC_DEPENDENCY. The illegal dependency function value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An illegal dependency function was passed to the dependency
recording module VDE$REC_DEPENDENCY. Valid dependency recording
functions are defined in the module VDELIB.REQ.
<MSG_TEXT>(User Action)
Check the dependency recording function that was passed on the
call to VDE$REC_DEPENDENCY. If that is ok, check the values
assigned to the VDE$K_DEPEND_xxxx dependency recording
literals in VDELIB.REQ. Someone may have assigned them
incorrect values.

<MSG>(ILLFORUSE\ill-formed user defined name )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
In the DEFINE/COMMAND command, the provided user-defined name
is illegal.
<MSG_TEXT>(User Action)
Reissue the command with the correct user defined name.

<MSG>(INCNOTVAL\INPUT not valid on streams marked for queued replacement )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The specified or default stream is marked for queued
replacements, and the CREATE MODULE /INPUT command
cannot be processed as it attempts to directly create
the module(s) without regard to the review and replacement
policy associated with the stream.
<MSG_TEXT>(User Action)
Perform a CREATE MODULE sans the /INPUT qualifier,
and then use a REPLACE command.  [This restriction may
be relaxed in a future release of VDE.]

<MSG>(INMODNOTFOU\input module <EMPHASIS>(module) of build step not found in database; ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The automatically collected dependency information for the
current build step specifies that the indicated module is
an input to the step.  However, the module is not found in
the VDE database; it is neither specified as a source module
nor as an output of any previous step.  This indicates that
the VDE database is not consistent with the actual contents
of the facility subdirectory in which the compiler or other
processor found the module.
<MSG_TEXT>(User Action)
Determine whether the module should be in the VDE library.
If it should be there, create the module with the CREATE
MODULE command.  If it should not be there, delete it from
the facility subdirectory in which the compiler or other
processor found it.

<MSG>(INPNOTNAME\input string <EMPHASIS>(text) is not syntactically valid )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An input string entered in response to an interactive
query for the name of some entity (such as a library,
module, or group) does not have the correct syntactic
form for that kind of entity name.
<MSG_TEXT>(User Action)
Reenter a correctly specified name in response to the query.

<MSG>(INPTOOLONG\input string too long; maximum length is <EMPHASIS>(number) characters )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An input string entered in response to an interactive
query for information is too long because it exceeds
the maximum length indicated in the message.
<MSG_TEXT>(User Action)
Reenter a shorter input string in response to the query.

<MSG>(INPTOOSHORT\input string too short; minimum length is <EMPHASIS>(number) characters )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An input string entered in response to an interactive
query for information is too short because it does not
reach the minimum length indicated in the message.
<MSG_TEXT>(User Action)
Reenter a longer input string in response to the query.

<MSG>(INTERR\internal VDE error in <EMPHASIS>(VDE-internal-identifier) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an internal inconsistency.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(INTERR_AZ\internal VDE error in <EMPHASIS>(VDE-internal-identifier) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an internal inconsistency.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(INTFUNCERR\internal script function error )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The script function encountered an error during the
parsing, and cannot be processed.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(INTMEMERR\internal memory-pool error at <EMPHASIS>(hex-virtual-address)
<EMPHASIS>(VDE-internal-identifier) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an inconsistency in its internal memory pool.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include any
information that may be useful or relevent in duplicating the
problem.

<MSG>(INTTOOBIG\integer too large )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Integer values
entered from the command line must  fit into a longword.
<MSG_TEXT>(User Action)
Determine if it is necessary to provide such a large number.
If it is necessary, then this is a restriction of VDE.

<MSG>(INVALANS\<EMPHASIS>(answer) is an invalid answer )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The response to a confirmation message is invalid; only
the word YES or the word NO or an abbreviation of one
of those two words is allowed as a response.  Confirmation
messages only appear when you use the /CONFIRM qualifier
on a command that accepts this qualifier.
<MSG_TEXT>(User Action)
Reenter either YES or NO (or Y or N) in response to the
confirmation message.

<MSG>(INVDATLNM\invalid VDE$DATE_TIME; use DD-MMM-YYYY:HH:MM:SS.CC format: <EMPHASIS>(time) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The format of a date-time value entered as a logical
name is invalid.  This message should appear only during
VDE testing, and is only displayed by debug versions of
VDE, and the logical name is only translated by debug
versions.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.  If the logical
name is being specified, correct the error in the
date-time logical name value and reissue the command.

<MSG>(INVDATTIM\invalid date-time; use DD-MMM-YYYY:HH:MM:SS.CC format: <EMPHASIS>(time) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The format of a date-time value entered as a command
parameter is invalid.
<MSG_TEXT>(User Action)
Correct the error in the date-time value and reissue
the command.

<MSG>(INVDBFORM\invalid database format; VDE is unable to access library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE database does not have the proper format.  The
database header record could be read successfully, but
that record does not contain the proper sentinel value
or its database version value indicates an out-of-date
or invalid database format.  This error could indicate
that the database has been corrupted in some way or
that VDE has generated it incorrectly.
<MSG_TEXT>(User Action)
Try to connect to the database again using the SET LIBRARY
command.  If that does not work, you may have to recreate
the library (and thus the database) from scratch with the
CREATE LIBRARY command.  If that still does not work,
please contact VDE support for assistance.

<MSG>(INVDIGDEC\invalid decimal number: <EMPHASIS>(number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A decimal digit is
often expected in many contexts such as a parameter.  If
the provided input is not a digit, this error message will
be generated.
<MSG_TEXT>(User Action)
Reissue the command with the appropriate number.

<MSG>(INVDIRSPEC\invalid directory specification: <EMPHASIS>(text) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A directory specification on a VDE command is not
syntactically correct.  This message is also printed
if a logical name (such as VDE$LIBRARY) that is supposed
to be bound to a directory specification is not bound to
a syntactically correct directory specification.
<MSG_TEXT>(User Action)
Reenter the VDE command with a valid directory specification
or define the logical name to be bound to a valid directory
specification.

<MSG>(INVGENEXPR\invalid CMS generation expression:  <EMPHASIS>(expression) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A CMS generation expression on a VDE command is not
syntactically correct.
<MSG_TEXT>(User Action)
Reenter the VDE command with a valid CMS generation
expression.

<MSG>(INVHISCHAR\invalid history or notes character following poundsigninvalid string is: <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A history or notes string was specified which contains an
invalid character after the poundsign character.  Valid
characters for a history string are:  H, h, B, or b.  Valid
characters for a notes string are:  G or g.  A poundsign
character may be included in the string by quoting it with
another poundsign character.
<MSG_TEXT>(User Action)
Reenter the VDE command with a valid history or notes string.

<MSG>(INVINPUT\invalid interactive command input; command aborted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current command has queried the user for input and has
gotten invalid input several times in a row.  This can be
caused by specifying insufficient parameter or qualifier
information on a command in a command file, which may cause
subsequent commands to be read as responses to interactive
queries.  Due to the invalid input, the current command is
aborted.
<MSG_TEXT>(User Action)
Reissue the command with correct qualifiers and parameters
or with correct input to interactive queries for command
information.

<MSG>(INVINTVAL\invalid integer value on command line: <EMPHASIS>(integer) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated integer value was entered on the current
command line but its value is not in the valid range for
that kind of value.  For example, if the number of
seconds in a delta-time interval is exceeds 59, you will
get this error message.
<MSG_TEXT>(User Action)
Reissue the command with a valid integer value.

<MSG>(INVIPMTNAM\invalid IPMT/CLD number syntax )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The format for the CLD number is not valid.
<MSG_TEXT>(User Action)
Respecify the CLD number in the format ABC-12345,
ABC-123456, ABC.12345 or ABC.123456.  If the IPMT/CLD
number is not in this format, or if this format is
not accepted by VDE, please contact VDE support for
assistance.

<MSG>(INVKEYNAM\invalid or missing key name )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name of a key on
the keyboard was expected in this command.
<MSG_TEXT>(User Action)
Reissue the command with an acceptable name of a key.

<MSG>(INVNUMRNG\number not valid; number is <EMPHASIS>(number), valid range is <EMPHASIS>(number) to <EMPHASIS>(number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A numeric input value is not within its valid range.  The
valid range is indicated in the message.
<MSG_TEXT>(User Action)
Reenter the number with a value within the valid range.

<MSG>(INVNUMSTG\invalid numeric string: <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A numeric input value is not syntactically valid.
<MSG_TEXT>(User Action)
Reenter the number with correct syntax.

<MSG>(INVPAGE\invalid screen height, value must be between <EMPHASIS>(minimum_height) and <EMPHASIS>(maximum_height) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
For the SET TERMINAL command, the /PAGE qualifier must
provide a page length between 11 and 100, inclusively.
<MSG_TEXT>(User Action)
Reissue the SET TERMINAL command with an acceptable page size.

<MSG>(INVPARAM\invalid parameter passed to <EMPHASIS>(routine-name-plus-info) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected in internal inconsistency, namely
that an illegal value has been passed as a parameter
to an internal routine.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please
include any information that may be useful or relevent
in duplicating the problem.

<MSG>(INVQARDB\invalid QAR database name syntax )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The format for the QAR database name is not valid.
<MSG_TEXT>(User Action)
Respecify the QAR database name using only alphanumeric,
underscore, dollar sign or hyphen characters.

<MSG>(INVQARNO\invalid QAR entry number syntax )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The format of the QAR entry number is not valid.
<MSG_TEXT>(User Action)
Respecify the QAR entry number using only numeric characters.

<MSG>(INVRANGE\no values in inverted range <EMPHASIS>(number) to <EMPHASIS>(number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The values specified for the /IDENTIFICATION qualifier on
the DELETE, MODIFY or SHOW REPLACEMENT command are in reverse
order and, therefore, do not represent any value.  For this
reason, no replacement entries are found matching this criteria.
<MSG_TEXT>(User Action)
Reenter the command specifying a valid range of replacement id
numbers in ascending order.

<MSG>(INVSOURCE\Invalid source of information specified: <EMPHASIS>(code) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The source of information -- typically the SCT, FOLD
or OTHER -- is not valid.
<MSG_TEXT>(User Action)
Reenter a valid source of information on this change.

<MSG>(INVWIDTH\invalid screen width, value must be between <EMPHASIS>(minimum_width) and <EMPHASIS>(maximum_width) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
For the SET TERMINAL command, the /WIDTH qualifier can
provide a page length between 40 and 255, inclusively.
<MSG_TEXT>(User Action)
Reissue the SET TERMINAL command with an acceptable width.

<MSG>(INVWILDSPEC\invalid wildcard specification in script selector: <EMPHASIS>(selector) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated module name or facility name is wildcarded
in a way that is not valid in a module-name or facility
specification used to select scripts.  The only form of
wildcarding that is allowed in this context is a single
asterisk <PARENDCHAR>(*); other, more general forms of
wildcarding are not allowed in script selectors.  Also,
the components of a full module (such as [FAC]MOD.TYP)
may all be wildcarded individually, but only in certain
combinations.  Invalid combinations yield this error
message.
<MSG_TEXT>(User Action)
Reissue the command with an acceptable wildcard specification.

<MSG>(IPMTAGAIN\please re-enter the IPMT or CLD number )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
There is a problem with the IPMT or CLD name, and you are
being prompted to re-enter the IPMT or CLD number.  This
message should be paired with other error messages, and
these other messages should provide insight into the
particular problem VDE is (currently) griping about.
<MSG_TEXT>(User Action)
The the IPMT or CLD name should be specified using three
leading alphabetic characters, a hyphen or period, and five
or six trailing numeric characters.  ABC-12345, ABC.12345,
ABC.123456, and ABC-123456 are all examples of valid IPMT
(or CLD) name syntax.

<MSG>(IPMTFMT\use ABC.12345, ABC-12345, ABC.123456 or ABC-123456 )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
These are valid formats for the IPMT/CLD number.
<MSG_TEXT>(User Action)
The IPMT/CLD number must be specified in the format
ABC-12345, ABC-123456, ABC.12345 or ABC.123456.  If
the IPMT/CLD number is not in this format, or if this
format is not accepted by VDE, please contact VDE
support for assistance.

<MSG>(IPMTSYNTAX\invalid IPMT/CLD name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the IPMT/CLD name
is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the IPMT/CLD name using three leading alphabetic
characters, a hyphen or period, and five or six trailing
numeric characters.  ABC-12345, ABC.12345, ABC.123456, and
ABC-123456 are all examples of valid IPMT/CLD name syntax.

<MSG>(ITEMLIST\unable to parse itemlist list entry at offset <EMPHASIS>(offset) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected a size, type code or buffer address error
at the specified entry offset in the itemlist.
<MSG_TEXT>(User Action)
Please evaluate the specified entry offset in the itemlist,
and rework it as appropriate.

<MSG>(IVQLOC\invalid qualifier location - place after each dependency file parameter )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The /INPUT and /OUTPUT qualifiers are allowed as a qualifier
for each file specification that is to be recorded as a
dependency.  These qualifiers are only meaningful for the
build dependency parameter of the VDEDEPEND command.
<MSG_TEXT>(User Action)
Reissue the command with the proper syntax.

<MSG>(IVQUAL\unrecognized qualifier '<EMPHASIS>(qualifier)' - check validity,
spelling, and placement )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An undefined qualifier was found.
<MSG_TEXT>(User Action)
Verify the syntax for the command and reissue it with only the
allowed qualifiers.

<MSG>(JOURDISA\database journalling disabled for VDE library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that after-image journalling
has been disabled (turned off) for the VDE library.
When journalling is disabled, it can be very hard to
recover from a damaged or corrupted VDE database.
<MSG_TEXT>(User Action)
None.

<MSG>(JOURENA\database journalling enabled for VDE library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that after-image journalling
has been enabled (turned on) for the VDE library.
Journalling makes it possible to recover the database
contents if the database is damaged or corrupted.
<MSG_TEXT>(User Action)
None.

<MSG>(KEYADDED\keyword <EMPHASIS>(keyname) added to note <EMPHASIS>(noteID) in conference <EMPHASIS>(conference) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has successfully added
the indicated keyword to a note in the indicated notes
conference.
<MSG_TEXT>(User Action)
None

<MSG>(LIBCONV\library format converted for new version of VDE )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The format of the current VDE library, including its
database schema, has been converted to the format
required by the present version of VDE.  If automatic
library conversion is enabled for the current VDE
library, this action takes place the first time someone
accesses the VDE database with a new version of VDE.
If automatic library conversion is disabled, you must
enter the CONVERT LIBRARY command to convert the library.
<MSG_TEXT>(User Action)
None.  This is an informational message only.

<MSG>(LIBINDRAN\Library index value of <EMPHASIS>(value) out of range for library dependency or module dependency. )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A library dependency or module dependency with an illegal
library index value was passed to the module VDE$REC_DEPENDENCY
for dependency recording. The value was equal to 0, or
greater than the currently largest assigned library index value
for the dependency recording session.
<MSG_TEXT>(User Action)
Check the call to LIB$REC_DEPENDENCY for recording this
library dependency or module dependency for a correct
library index value. If the library index value appears
correct please submit a problem report.

<MSG>(LIBLABEL\library (<EMPHASIS>(mnemonic)) contents: <EMPHASIS>(label) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This is an informational message, and indicates
the label associated with a particular library
that is available.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(LIBMOD\library attributes modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that attributes for the current
library have been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
LIBRARY command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(LIBNOTSET\library not set; no VDE database found in directory <EMPHASIS>(directory) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to set a VDE library by specifying a
directory specification or library mnemonic specification
on the SET LIBRARY command, but the directory or mnemonic
either does not exist or does not reference a valid VDE
library database.  If you are using a mnemonic for the
library, check to make sure you have entered a valid
mnemonic, then check to see that the VDE$LIBRARY_DEFAULTS*
logical names all include the appropriate and matching
numbers of translations.  (If you are uncertain how to
check  the VDE$LIBRARY_DEFAULTS* logical names, consult
the VDE user's guide.)
<MSG_TEXT>(User Action)
Reenter the command with a directory specification that
specifies a valid root directory for a VDE library, or
enter a correct mnemonic.  If the directory or mnemonic
is correct, contact the local system management staff and
ask that the translations of the VDE$LIBRARY_DEFAULTS*
logical name(s) be corrected.

<MSG>(LIBREQ\specification of library mnemonic required )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE/LOCATIONS is unable to locate the target for the
location translation operation.
<MSG_TEXT>(User Action)
Specify the target via VDE/LOCATIONS/MNEMONIC=mnemonic.

<MSG>(LIBRESET\library reset )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have reset the VDE library.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(LINKFAIL\link of <EMPHASIS>(module) completed with errors )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The link step for the indicated module completed with
one or more errors.  The linker's output (on your
terminal or in the step's log file) gives more detail on
the errors it detected.
<MSG_TEXT>(User Action)
Correct the errors and resubmit the link or build job.

<MSG>(LINKSUCC\link of <EMPHASIS>(module) completed successfully )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The link of the indicated module completed successfully.
<MSG_TEXT>(User Action)
None.

<MSG>(LNKSTEPADDED\link step for <EMPHASIS>(module) added to database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated link step
has been added to the VDE database.  This message is only
issued when you use the /LOG qualifier on the CREATE STEP
command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(LNKSTEPDEL\link step for module <EMPHASIS>(module) deleted from database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the link step for the
indicated module has been deleted from the VDE database.
This means that all build dependency information for that
build step has been deleted.  This message is only issued
when you use the /LOG qualifier on the DELETE STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(LNKSTEPMOD\link step for module <EMPHASIS>(module) modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that build dependency information
for the indicated link step has been modified in the VDE
database.  This message is only issued when you use the
/LOG qualifier on the MODIFY STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(LOASTLM\recommended free ASTLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the ASTLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOBIOLM\recommended free BIOLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the BIOLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOBYTLM\recommended free BYTLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the BYTLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOCKED\library write access is disabled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed when an attempt is made
to write -- RESERVE, REPLACE or PERFORM REPLACE a
module, etc -- into to a locked library.
<MSG_TEXT>(User Action)
Contact the staff responsible for the library to
determine why access to the library is currently
locked out.  The library may be currently undergoing
maintenance operations, or the library may be a
read-only shadow copy of a library.  Only a user
with the MODLIB privilege can unlock the library.

<MSG>(LODIOLM\recommended free DIOLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the DIOLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOENQLM\recommended free ENQLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the ENQLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOFILLM\recommended free FILLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the FILLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOGNAMUNDEF\logical name <EMPHASIS>(logical) undefined; operation cannot complete )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current VDE operation requires the indicated logical
name to be defined, but it is not defined.  As a result,
VDE cannot perform the operation.
<MSG_TEXT>(User Action)
Exit the VDE kept process with the EXIT/KEPT_PROCESS
command, define the required logical name, restart VDE,
and retry the operation.

<MSG>(LOJTQUOTA\recommended free JTQUOTA is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the JTQUOTA currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOPGFLQUOTA\recommended free PGFLQUOTA value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the PGFLQUOTA quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOPRCLM\recommended free PRCLM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the PRCLM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(LOQUOTA\one or more process quotas is too low )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The currently-free value of one or more quotas
is below the recommended values for VDE.  VDE
will attempt to continue.
<MSG_TEXT>(User Action)
The determination of a low quota is based on the
currently-free value of the quota.  Contact your
system management staff and request that the
process quotas associated with the current
username be reset to provide the recommended value
with VDE.  One or more messages are output with
this message listing the particular quota found
to be low, and the recommended minimum free value
for the quota.  VDE will attempt to continue from
this error.

<MSG>(LOTQELM\recommended free TQELM value is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The amount of the TQELM quota currently available
is below the recommended value for VDE.  VDE will
attempt to continue.
<MSG_TEXT>(User Action)
Contact your system management staff and request
that the process quotas associated with the current
username be reset to the values recommended for use
with VDE.  This message includes the recommended
minimum free value for the quota.

<MSG>(MAILERR\error from MAIL routine <EMPHASIS>(routine-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has encountered an error while using the VMS MAIL
callable interface.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one and contact VDE support
for assistance.

<MSG>(MAILSENT\mail message sent to user <EMPHASIS>(user) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has sent a mail message
to the indicated user notifying that user of your action.
This message is issued when you use the /LOG qualifier
on a command that sends mail notifications.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(MATQUOMIS\matching quote is missing )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
All quoted strings must be delimited by either two
single or two double quotes.
<MSG_TEXT>(User Action)
Reenter the command with appropriately quoted string.

<MSG>(MAXIDVAL\maximum allowed Id value in database exceeded: <EMPHASIS>(ID) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Each entity in the VDE database, such as each module, each
stream, and each build job, has an integer Id value that
uniquely identifies it.  This Id value may not assume a
value larger than 2,000,000,000, but the operation you have
attempted to perform has tried to create an entity with an
Id value larger than this maximum.  The indicated name tells
which Id value is affected.  This error should never occur
unless the database is extremely large.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Most likely the
VDE database has been damaged by an internal error.

<MSG>(MAXPARM\too many parameters - reenter command with fewer parameters )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
In both the SHOW KEY and DELETE KEY commands, the user
cannot provide both /ALL as a qualifier and a key name as
a parameter.
<MSG_TEXT>(User Action)
Choose between /ALL or just one key in either the SHOW KEY
or DELETE KEY commands.

<MSG>(MERGEGEN\merging generation <EMPHASIS>(generation)(<EMPHASIS>(this)) into <EMPHASIS>(that) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the current FETCH or RESERVE
command will merge the indicated <QUOTE>(merge) generation
into the generation being fetched or reserved to produce
the output file.  This message is only issued when you use
the /MERGE and /LOG qualifiers on the command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(MISCONTSCRP\missing continuation line in script )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current script specified that the last line should
be continued but no such continuation line exists.  A
hyphen <PARENDCHAR>(-) at the end of a line indicates
that the line should be continued.
<MSG_TEXT>(User Action)
Either remove the hyphen at the end of the last line or
supply a continuation line, whichever is appropriate.

<MSG>(MISHISPARM\missing history parameter in string "<EMPHASIS>(string)" )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A history string was specified which does not contain
a history parameter.  A history parameter is required
as part of the history string.
<MSG_TEXT>(User Action)
Reenter the VDE command with a valid history string.

<MSG>(MISTYPNAM\missing type name for module <EMPHASIS>(string); type name required )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A module name has been specified without a module type in
a context where the module type is required.  For example,
the command CREATE MODULE M1 is incorrect because a module
type, as in CREATE MODULE M1.FOR (where FOR is the module
type), is required for this command.  The type name must
be separated from the module name by a dot (.) as shown in
the example.

<MSG>(MNEMONIC\library (<EMPHASIS>(mnemonic)) <EMPHASIS>(library) available )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This is an informational message, and indicates
a particular library is available, as well as the
mnemomic name associated with the library.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(MNETOOLONG\library mnemonic too long; maximium length: <EMPHASIS>(length) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
One (or more) of the VDE$LIBRARY_DEFAULTS_MNEMONICS
library mnemonic name translations are too long.
<MSG_TEXT>(User Action)
Contact the maintainer of the definitions of the
VDE$LIBRARY_DEFAULTS_MNEMONICS logical name in use,
and ask that the mnemonics be shortened.

<MSG>(MODADDED\module <EMPHASIS>(module) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the CREATE MODULE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(MODALRINSTEP\module <EMPHASIS>(module) is already an input to build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
already an input to the build step.  This message is
only issued when you use the /LOG qualifier on the
MODIFY STEP command and specify a new input module
which is already an input to the step.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODALROUTSTEP\module <EMPHASIS>(module) is already an output from build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
already an output from the build step.  This message
is only issued when you use the /LOG qualifier on the
MODIFY STEP command and specify a new output module
which is already an output from the step.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODALRQUEREP\module <EMPHASIS>(module) already queued for replacement <EMPHASIS>(replacement) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to replace or unreserve a module that already
belongs to the indicated queued replacement.  A reservation
that already belongs to a queued replacement cannot be
unreserved or queued for another replacement; the reservation
remains until the original replacement is performed or
cancelled.  As a result, your attempt to replace or unreserve
the module has failed.
<MSG_TEXT>(User Action)
If you want to remove the module reservation from its current
queued replacement, you must cancel that replacement with the
CANCEL REPLACEMENT command.  You can then unreserve the
module or replace it as part of another replacement.

<MSG>(MODALRRES\module <EMPHASIS>(module) already reserved; reservation has failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to reserve a module that is already reserved
by another user (possibly yourself).  That reservation does
not allow concurrent reservations, or you have not requested
a concurrent reservation.  The reservation may be in the
current default stream, or in an ancestor stream.  As a
result of this prior reservation, your attempt to
reserve the module has failed.
<MSG_TEXT>(User Action)
Wait until the user who has reserved the module replaces it
in the library.  Then reserve it yourself.  You can use the
SHOW RESERVATION/FULL command to see who currently has the
module reserved, and in what stream the module was originally
reserved.  Alternatively, you can use the /OVERRIDE=CONCURRENT
qualifier to concurrently reserve the module, or the /QUEUE
qualifier to queue a request for notification when the
module becomes available.

<MSG>(MODDEL\module <EMPHASIS>(module) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated module has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE MODULE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(MODEXISTS\module <EMPHASIS>(module) already exists in database; module not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated module name was specified on a CREATE MODULE
command, but an entry for that module is already present in
the database.  Hence a new entry was not created for that
module.  Alternatively, the indicated name was specified as
the new name for an existing module on the MODIFY MODULE
command, but another module in the same facility already has
the requested new name.  Hence the name of the existing
module could not be changed to the new name.
<MSG_TEXT>(User Action)
If you entered the wrong module name, reenter the command
with the correct name.  If you entered the right module
name, use the SHOW MODULE command to display the database
information for that module.  If you are not satisfied
with that information, use the MODIFY MODULE command to
change it.

<MSG>(MODINSTEP\module <EMPHASIS>(module) is an input to the build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
recorded as an input to the build step being defined.
This message is only issued when you use the /LOG
qualifier on the CREATE STEP or MODIFY STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODLOCKED\module <EMPHASIS>(module) locked for replacement by another user )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The module you are trying to replace is currently being
replaced by another user who is updating the same generation
as you want to update.  As a result, your replacement attempt
failed.
<MSG_TEXT>(User Action)
Wait a minute or two and then try the operation again.
If the other user deleted your concurrent reservation
through his or her replacement, your second attempt will
fail with a message to that effect.  If the other user's
replacement failed or did not conflict with yours, your
new replacement attempt can succeed.

<MSG>(MODMODIF\information for module <EMPHASIS>(module) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
module has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
MODULE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(MODNOTDEL\module <EMPHASIS>(module) not deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to delete a module that
cannot be deleted.  Additional messages are normally
included with this message, and these messages
indicate why the module cannot be deleted.
<MSG_TEXT>(User Action)
Resolve the problem(s) flagged by the other error
messages, and reenter the DELETE MODULE command.

<MSG>(MODNOTFOUND\module <EMPHASIS>(module) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated module name was entered on a SHOW MODULE
command, but no such module was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated module does not exist in the database.

<MSG>(MODNOTINSTEP\module <EMPHASIS>(module) is not now an input to build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
not now recorded as an input to the build step whose
definition you are modifying.  Removing it from the
build step is thus redundant.  This message is only
issued when you use the /LOG qualifier on the MODIFY
STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODNOTINSTRM\generation <EMPHASIS>(generation) not in stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that an attempt was made to update
the specified stream with a new generation of the specified
module, but the specified module is not part of the specified
development stream.
<MSG_TEXT>(User Action)
Use the /NOPROPAGATE qualifier for the command or populate the
specified stream with the specified generation and try the
command again.

<MSG>(MODNOTOUTSTEP\module <EMPHASIS>(module) is not now an output from build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
not now recorded as an output from the build step whose
definition you are modifying.  Removing it from the
build step is thus redundant.  This message is only
issued when you use the /LOG qualifier on the MODIFY
STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODNOTRES\module <EMPHASIS>(module) is not currently reserved )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to replace the indicated module but that
module is not currently reserved in the current stream
development stream.
<MSG_TEXT>(User Action)
Reserve the module before trying to replace it.

<MSG>(MODNOTREV\module <EMPHASIS>(module) not found in review list )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a module that does not exist in the
current review list.  As a result, you cannot select the
module with the name you specified.
<MSG_TEXT>(User Action)
Reenter the SELECT command specifying a module that is
present in the review list for the current REVIEW command.
Use the DIRECTORY subcommand to determine what modules are
present in the list.

<MSG>(MODOBS\module <EMPHASIS>(module-name) superceded or marked obsolete )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The latest generation of the specified module indicates
the module was superceded by a more recent module or was
marked obsolete.
<MSG_TEXT>(User Action)
Determine if the current operation should proceed with a
module that has been superceded or is marked as obsolete.
If the operation should proceed, determine if any modifications
are needed to any module(s) that may have superceded or replaced
this module.

<MSG>(MODOUTSTEP\module <EMPHASIS>(module) is an output from the build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
recorded as an output from the build step being defined.
This message is only issued when you use the /LOG
qualifier on the CREATE STEP or MODIFY STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODREMINSTEP\module <EMPHASIS>(module) removed as an input to build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
no longer recorded as an input to the build step whose
definition you are modifying.  This message is only
issued when you use the /LOG qualifier on the MODIFY
STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MODREMOUTSTEP\module <EMPHASIS>(module) removed as an output from build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module is
no longer recorded as an output from the build step whose
definition you are modifying.  This message is only
issued when you use the /LOG qualifier on the MODIFY
STEP command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(MUSTREPL\you must replace the new module to create its first generation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed when you create a new module
with the CREATE MODULE command and the command marks
the module as reserved.  It reminds you that you must
replace the module with a REPLACE command to create
the first generation of the module.  This message is
only issued when you use the /LOG qualifier on the
CREATE MODULE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(NAMTOOLONG\name is too long: <EMPHASIS>(text); maximum length is <EMPHASIS>(number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A name entered as a command parameter is too long because
it exceeds the maximum length indicated in the message.
<MSG_TEXT>(User Action)
Reissue the command with a shorter name.

<MSG>(NEEDFACILITY\this request requires a facility )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to perform the specified request as
a facility was not selected nor otherwise specified.
<MSG_TEXT>(User Action)
Select or specify a facility, and retry the request.

<MSG>(NEEDLIBRARY\this request requires a library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to perform the specified request as
a library was not selected nor otherwise specified.
<MSG_TEXT>(User Action)
Select or specify a library, and retry the request.

<MSG>(NEEDMOD\module must be specified on command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have failed to specify a module name on a command that
requires it.
<MSG_TEXT>(User Action)
Enter the module name you want on the command.

<MSG>(NEEDMODULE\this request requires a module )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to perform the specified request as
a module was not selected nor otherwise specified.
<MSG_TEXT>(User Action)
Select or specify a module, and retry the request.

<MSG>(NEEDMORE\unexpected end of command line )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Many commands require the presence of additional parameters or
qualifiers.
<MSG_TEXT>(User Action)
Review the correct syntax of the respective command and enter
it with the appropriate parameters.

<MSG>(NEEDSTEP\build step must be specified on command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have failed to specify a build step on a command that
requires it.
<MSG_TEXT>(User Action)
Enter a module name on the command to select the build step
you want.

<MSG>(NEEDSTREAM\this request requires a stream )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to perform the specified request as
a stream was not selected nor otherwise specified.
<MSG_TEXT>(User Action)
Select or specify a stream, and retry the request.

<MSG>(NETERROR\network error; component: <EMPHASIS>(id), code: <EMPHASIS>(errcod) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Something deep within the bowels of the VDE network
layer has returned an error.
<MSG_TEXT>(User Action)
Please check the status of the local network, and
then contact VDE support for further assistance.

<MSG>(NEWDBGMSK\debug mask switching from <EMPHASIS>(oldmask) to <EMPHASIS>(newmask) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that the value loaded in the VDE
debugging bitmask is being changed.  This message should
appear only during VDE testing.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug-only images.

<MSG>(NOACCLIB\no access to library allowed for user <EMPHASIS>(username) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are not authorized to access the VDE library that
logical name VDE$LIBRARY points to or that you are
trying to establish with a SET LIBRARY command.
<MSG_TEXT>(User Action)
Correct the definition of logical name VDE$LIBRARY,
specify the name of a library you are authorized to
access on the SET LIBRARY command, or request that
the administrator for the desired VDE library give
you the right to access that library.

<MSG>(NOARCHSPEC\no architecture specified for operation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have entered a command that requires a default
architecture to exist, but you have not established a
default architecture.  Usually, this means that the
command you have entered contains a module name with an
omitted architecture name and the architecture cannot be
defaulted.  As a result, the module cannot be looked up
in any architecture.
<MSG_TEXT>(User Action)
Either establish a default archtecture with the SET
ARCHITECTURE command and reenter the command, or reenter
the command with an explicitly specified architecture
name, as in ARCHNAM:[FACNAM]MOD.TYP.

<MSG>(NOATTACH\failed to attach to process PID !XL )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The ATTACH command has failed to attach to the requested
process.
<MSG_TEXT>(User Action)
Verify that the requested process exists.  Check spelling
of the process name.

<MSG>(NOAUTOCONV\automatic conversion to current database format disabled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE database does not have the proper format, and
the automatic conversion of the database has been disabled.
<MSG_TEXT>(User Action)
If use of the new version of VDE is intended, perform a
full library backup using the database-provided backup
tools, and then use the VDE CONVERT command to update the
database format.

<MSG>(NOBASENOTE\no base note found for replacement <EMPHASIS>(replacement_id) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed in conjunction with other
error messages, and indicates the particular failure
that occurred.  VDE has attempted to find a base note
with either a keyword or a title containing the
specified replacement ID and has failed.
<MSG_TEXT>(User Action)
Resolve the basic error.  If unable to resolve the
error, please contact the project leader or VDE support
for assistance.

<MSG>(NOBLDJOB\no build jobs found for stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
No build job is present in the database that belongs to
the indicated stream and matches the selection criteria
you specified on the SHOW BUILD_JOB or other BUILD_JOB
command.  The selection criteria you have specified may
include the build-job identification number, the build-job
status, or bounds on the build-job creation date and time.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the no build job exists for the stream and
selection criteria you specified.

<MSG>(NOBLDSTEPS\build job contains no build steps; build job is not created )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You tried to create a build job with the BUILD command,
but the build job turns out to contain no build steps.
As a result, the build job is not created in the database.
The usual cause of this error is that you specified a
minimal build of modules that are already up-to-date with
respect to their source modules.
<MSG_TEXT>(User Action)
If you intended to perform a minimal build, the build job
is unnecessary.  If you intended to perform a full build,
specify the /FULL qualifier on the BUILD command.

<MSG>(NOBUILD\no BUILD privilege; cannot create build jobs in this library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCANRES\cannot cancel reservation to create first generation of <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have entered an UNRESERVE command to cancel the
reservation that will create the initial generation of the
indicated module.  The reservation was created by a CREATE
MODULE command and VDE does not allow you to cancel such a
reservation.
<MSG_TEXT>(User Action)
If you no longer want the reservation that will create the
first generation of the module, you must delete the module
with the DELETE MODULE command.  If you just want to change
the attributes of the reservation, you must do so with the
MODIFY RESERVATION command.

<MSG>(NOCAUSE\replacement cause not known; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was not provided with the cause of the replacement
being performed.  The cause of a replacement -- usually
a Source Code Tracking (SCT) entry or a source code
Fold -- is tracked.
<MSG_TEXT>(User Action)
Select the appropriate replacement cause -- Source Code
Tracking (SCT), Fold, or Other -- using the toggle buttons
on the module replacement dialog box.

<MSG>(NOCLOSEQ\no closing quotation mark for a quoted string )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
For the DEFINE/COMMAND command, the parameter that describes
the command must be enclosed with either single or double
quotes.
<MSG_TEXT>(User Action)
Reenter the DEFINE/COMMAND command  with the appropriate
quotes.

<MSG>(NOCONFNAM\no notes conference name specified in call to <EMPHASIS>(routine-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an inconsistency within an internal
routine which uses the notes callable interface.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(NOCREARCH\no CREARCH privilege; cannot create or modify architectures )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCRECTX\no CRECTX privilege; cannot create or delete contexts )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCREFAC\no CREFAC privilege; cannot create or modify facilities )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCREGRP\no CREGRP privilege; cannot create or delete groups )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCREMOD\no CREMOD privilege; cannot create or modify modules )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCRESCRP\no CRESCRP privilege; cannot create or delete scripts )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCRESTEP\no CRESTEP privilege; cannot create or delete steps )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCRESTRM\no CRESTRM privilege; cannot create or modify streams )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOCREUSR\no CREUSER privilege; cannot create or delete users )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NODELARCH\no DELARCH privilege; cannot delete architectures )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NODELDEF\Attempt to delete default prohibited )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to delete a object (architecture,
stream, facility, etc.) that is a default.
<MSG_TEXT>(User Action)
To make the architecture deleteable use the MODIFY
ARCHITECTURE command with the /DELETE qualifier. Then
reenter the DELETE ARCHITECTURE command.

<MSG>(NODELFAC\no DELFAC privilege; cannot delete facilities from library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NODELMOD\no DELMOD privilege; cannot delete modules from library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NODELREP\no DELREP privilege; cannot delete replacements )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NODELSET\marked /NODELETE )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to delete an object (architecture,
stream, facility, etc.) that has been marked not-deletable
by default or by use of the /NODELETE qualifier.
<MSG_TEXT>(User Action)
To allow the object to be deleted, specify the appropriate
MODIFY command with the /DELETE qualifier.  Then reenter
the failing DELETE command.

<MSG>(NODELSTRM\no DELSTRM privilege; cannot delete streams from library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NODELTAROOT\no delta-file root directory exists for library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to create a directory tree for a specific
facility's delta files, but no delta-file root directory
exists for the library.  Hence VDE cannot create any disk
directories for the indicated facility.
<MSG_TEXT>(User Action)
Use the CREATE DIRECTORY_TREE/DELTA_FILES command to create
a directory tree for the library's delta files.  That will
automatically create the delta-file root directory for the
library and the delta-file subdirectories for all facilities.

<MSG>(NODIRDELTA\no delta-file directory found for facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE tried to access the delta-file directory for the
indicated facility, but no such directory is recorded
in the database.  This normally means that you have
not yet created the disk directories for the facility.
<MSG_TEXT>(User Action)
To create the facility's delta-file directory, use the
CREATE DIRECTORY_TREE command with the /DELTA_FILES and
possibly /FACILITY qualifiers.  Use the SHOW LOCATION
command to see what disk directories are recorded in
the VDE database.

<MSG>(NODIRMARKER\no marker-file directory found for facility <EMPHASIS>(facility) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE tried to access the marker-file directory for the
indicated facility, but no such directory is recorded
in the database.  This normally means that you have
failed to create a delta-file subdirectory with directory
symbol VDE$MARKER for the indicated facility.  Such a
directory must exist for you to create modules that use
marker files.
<MSG_TEXT>(User Action)
To create the needed subdirectory, use the SET DIRECTORY
command with the /DELTA_FILES and /SYMBOL=VDE$MARKER
qualifiers.  Then create the facility's delta-file
directory tree with the CREATE DIRECTORY_TREE command,
using the /DELTA_FILES and possibly /FACILITY qualifiers.
Use the SHOW LOCATION command to see what disk directories
are recorded in the VDE database.

<MSG>(NOFACSPEC\no facility specified for operation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have entered a command that requires a default facility
to exist, but you have not established a default facility.
Usually, this means that the command you have entered
contains a module name with an omitted facility name and
the facility cannot be defaulted.  As a result, the module
cannot be looked up in any facility.
<MSG_TEXT>(User Action)
Either establish a default facility with the SET FACILITY
command and reenter the command, or reenter the command
with an explicitly specified facility name, as in
[FACNAM]MOD.TYP.

<MSG>(NOFREE\no free storage available )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has run out of virtual memory.
<MSG_TEXT>(User Action)
Use less complex commands, raise the virtual-address quota,
or submit a problem report.

<MSG>(NOFROZEN\no FROZEN privilege; cannot replace modules into frozen streams )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOGENSTRM\generation <EMPHASIS>(generation) not found in stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated module generation was entered on a command,
but no such generation was found in the specified stream.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated generation does not exist in the
specified stream.  First, verify that you have either specified
the correct stream on the command or that your context is set
to the correct stream.  If the stream name was correct and
you had expected such a generation of a module to exist in
that stream, you may use the SHOW GENERATION/STREAM=stream-name
command to see what module generations are found in that stream.

<MSG>(NOKEYPAD\unable to set up keypad definitions )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to setup keypad definitions because
an error was returned from SMG$DELETE_VIRTUAL_KEYBOAD.
VDE uses the SMG facility to perform keypad management.
<MSG_TEXT>(User Action)
Check the setup of the terminal which might cause
SMG some problem.  If the error still cannot be explained,
please contact VDE support for assistance.

<MSG>(NOKEYW\qualifier name is missing - append the name to the slash )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A qualifier is
composed of both a "/" and keyword.  If only a "/" appears,
then this error message is displayed.
<MSG_TEXT>(User Action)
Ensure that there are no dangling "/" in the command.

<MSG>(NOLIBDEF\no VDE library defined )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE is unable to perform the specified operation as
the target VDE library -- the library on which the
operation will be performed -- has not been established.
<MSG_TEXT>(User Action)
Specify the target VDE library.  To determine the
available libraries, issue the "SET LIBRARY" command
with no parameters.  As part of the error message, this
command will display the names of the predefined VDE
libraries, the Rdb root directory for each, and the
mnemonic name for each.  Once the mnemnonic name or the
Rdb root directory name for the target library is known,
one can: A) use the mnemnonic name or the Rdb root directory
name as the libname parameter on a "SET LIBRARY libname"
VDE command.  B) Use use the mnemnonic name or the Rdb root
directory name as the parameter on the VDE /LIBRARY=libname.
C) Define the logical name VDE$LIBRARY to translate to
the VDE mnemnonic name or to the Rdb root directory name.

<MSG>(NOLIBROOM\too many libraries in default file )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected too many libraries declared in the VDE.DAT Motif
application defaults file, and is unable to display all of the
specified libraries in the system library cascading pulldown.
<MSG_TEXT>(User Action)
If you are unable to reduce the number of libraries in the
default file, please contact VDE support for assistance.

<MSG>(NOMAIL\no message sent;  MAIL messages are disabled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to indicate that the version of
VDE in use contains debug or prototype code, and as
a result, no mail message is being sent.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug or prototype images.

<MSG>(NOMAILSENT\failure to send mail message to user <EMPHASIS>(user) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has failed in an attempt to send a mail message to
the indicated user notifying that user of your action.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one, and contact VDE support
for assistance.

<MSG>(NOMATCHARCH\no architecture name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded architecture name specification
on a command, but that specification did not match any
architecture names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no architectures matching your specification exist
in the database.  If you had expected such architectures
to exist, you can use the SHOW ARCHITECTURE command to see
what architectures are present in the database and you can
ask your project administator to add any missing architectures.

<MSG>(NOMATCHCTX\no context name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded context name specification on
a command, but that specification did not match any
context names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no contexts matching your specification exist in
the database.  If you had expected such contexts to exist,
you can use the SHOW CONTEXT command to see what contexts
are present in the database and you can ask your project
administator to add any missing contexts.

<MSG>(NOMATCHFAC\no facility name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded facility name specification on
a command, but that specification did not match any
facility names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no facilities matching your specification exist in
the database.  If you had expected such facilities to exist,
you can use the SHOW FACILITY command to see what facilities
are present in the database and you can ask your project
administator to add any missing facilities.

<MSG>(NOMATCHGEN\no generation matches wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded generation specification on a
command, but that specification did not match any module
generations in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no module generations matching your specification
exist in the database.  If you had expected such generations
to exist, you can use the SHOW GENERATION command to see
what generations are present in the database.

<MSG>(NOMATCHGENS\no generation matches wildcarded string <EMPHASIS>(string) in stream <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded generation specification on a
command, but that specification did not match any module
generations in the specified stream.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no module generations matching your specification
exist in the specified stream.  First, verify that you have
either specified the correct stream on the command or that
your context is set to the correct stream.  If the stream
name was correct and you had expected such generations to
exist, you can use the SHOW GENERATION/STREAM=stream-name
command to see what generations are present in that stream.

<MSG>(NOMATCHGRP\no group name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded group name specification on
a command, but that specification did not match any
group names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no groups matching your specification exist in
the database.  If you had expected such groups to exist,
you can use the SHOW GROUP command to see what groups
are present in the database and you can use the CREATE
GROUP command to add any new groups you want.

<MSG>(NOMATCHMOD\no module name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded module name specification on a
command, but that specification did not match any module
names in the VDE database in the indicated (or in the
default) facility.  This message can be generated when
double-clicking on an empty facility from within the
Motif display.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no modules matching your specification exist in
the VDE database.  If you had expected such modules to
exist, you can use the SHOW MODULE command to see what
modules are present in the database and you can use the
CREATE MODULE command to add any missing modules.

<MSG>(NOMATCHREP\no replacement name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded replacement name specification on
a command, but that specification did not match any
replacement names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no replacements matching your specification exist in
the database.  If you had expected such replacements to exist,
you can use the SHOW REPLACEMENT command to see what
replacements are present in the database and you can ask your
project administator to add any missing replacements.

<MSG>(NOMATCHSCRP\no scripts match the specification )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You requested a display of all scripts of a certains type,
possibly matching a wildcarded module-name or facility-name
specification, but there are no scripts in the database that
match that specification.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no scripts exist in the database that match
your specification.

<MSG>(NOMATCHSES\no session name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded session name specification on
a command, but that specification did not match any
session names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no sessions matching your specification exist in
the database.  If you had expected such sessions to exist,
you can use the SHOW SESSION command to see what
sessions are present in the database and you can ask your
project administator to add any missing sessions.

<MSG>(NOMATCHSTEP\no build steps for modules matching <EMPHASIS>(string) found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded module-name specification to
specify build steps, but there are no build steps in the
database for modules that match that name specification.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no build steps exist in the database for modules
matching your module-name specification.  If you had
expected such build steps to exist, you can use the SHOW
STEP command to see what build steps are represented in
the database.

<MSG>(NOMATCHSTRM\no stream name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded stream name specification on
a command, but that specification did not match any
stream names in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no streams matching your specification exist in
the database.  If you had expected such streams to exist,
you can use the SHOW STREAM * command to see what streams
are present in the database and you can ask your project
administator to add any missing streams.

<MSG>(NOMATCHUSER\no user name matches the wildcarded string <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered a wildcarded username specification on a
command, but that specification did not match any
usernames in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that no users matching your specification exist in
the database.  If you had expected such users to exist,
you can use the SHOW USER * command to see what usernames
are present in the database and you can ask your project
administator to add any missing users.

<MSG>(NOMEMGRP\no members specified for group <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to create a group without specifying
any members for that group.  A group must have at
least one member.  (The members of a group are the
modules to be built when the group name is specified
on a GROUP command.)
<MSG_TEXT>(User Action)
Reenter the CREATE GROUP command, specifying the
names of the modules that you want to be the members
of the new group.

<MSG>(NOMODLIB\no MODLIB privilege; cannot modify attributes of this library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOMODMEMGRP\no modules are members of group <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You entered the indicated group name on a command to apply
the command to the modules that are members of that group,
but the group has no members.  Hence the command is not
applied to any modules due to that group specification.
<MSG_TEXT>(User Action)
Use the CREATE GROUP or MODIFY GROUP command to specify
the members of a group.  Use the SHOW GROUP/MEMBER command
to determine the membership of a group.

<MSG>(NOMODSTRM\no MODSTRM privilege; cannot modify most stream attributes )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOMOREMOD\no more modules in review list )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to review the next module in the
current review list, but there are no more such modules.
You also get this message if you attempt to review the
previous module when you are positioned at the first
module in the list.
<MSG_TEXT>(User Action)
Review build steps in the other direction or exit from
the REVIEW REPLACEMENT subsystem.

<MSG>(NOMORESTEP\no more build steps in review list )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to review the next build step in the
current review list, but there are no more such steps.
You also get this message if you attempt to review the
previous build step when you are positioned at the first
step in the list.
<MSG_TEXT>(User Action)
Review build steps in the other direction or exit from
the REVIEW BUILD_JOB subsystem.

<MSG>(NONNULLARG\argument specfied MBZ has non-zero value in routine <EMPHASIS>(VDE-routine) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected a non-fatal internal inconsitency.  A non-zero
value has been passed as an argument to an internal routine that
is specified to have a zero value.  This message should only
be seen in internal or prototype baselevels of VDE.
<MSG_TEXT>(User Action)
Please notify VDE support.  Please include any information
that may be useful or relevent in duplicating the problem.

<MSG>(NONOTE\no note topic entered; note entry is disabled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to indicate that the version of
VDE in use contains debug or prototype code, and as
a result, that a notes topic was not entered.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug or prototype images.

<MSG>(NONOTESENT\note NOT posted to conference <EMPHASIS>(conference) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has failed in an attempt to post a note to the indicated
notes conference.  Check the conference for general accessability,
and - if conference membership is needed, determine if you
are a member of the conference from the node on which you
are running VDE.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one, check the documentation
for information on setting up the notes conferences, and
contact VDE support for assistance.

<MSG>(NOPARSTRM\no parent stream specified for new stream )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are creating a new development stream, but you did not
specify the parent of the new stream.  You must specify the
parent stream by using the /PARENT qualifier with the CREATE
STREAM command or by establishing a default stream for the
VDE session with the SET STREAM command before entering the
CREATE STREAM command.
<MSG_TEXT>(User Action)
Establish a default stream with SET STREAM and reenter the
CREATE STREAM command or specify the /PARENT qualifier with
the CREATE STREAM command.

<MSG>(NOPERFREP\no PREFREP privilege; cannot perform replacements )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOPNAM\unknown project name specified for the stream )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The specified project name does not match the project
names associated with the specified development stream.
<MSG_TEXT>(User Action)
This is a warning message,  If you believe that this
project should be associated with the stream, please
contact the project leader, the system manager(s), or
VDE support for assistance.

<MSG>(NOPNAMS\no projects defined for the stream )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
There are no projects associated with the specified
development stream.
<MSG_TEXT>(User Action)
This is an informational message,  If you believe that
there should be one or more projects associated with the
stream, please contact the project leader, the system
manager(s), or VDE support for assistance.

<MSG>(NOPRIVQUAL\insufficient privilege to use <EMPHASIS>(qualifer) qualifier )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command qualifier that requires a
privilege, and you did not have that privilege set.
<MSG_TEXT>(User Action)
If you are authorized to use the qualifier, use the
SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOPRIVS\insufficient VDE privilege(s) for attempted operation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOPROMPT\no prompt specified; using default prompt )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This is an informational message, and indicates
that no prompt was specified on the SET PROMPT
command.  As no prompt was specified, VDE will
revert to the default VDE prompt.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(NORESFORMOD\no reservations exist for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to reference reservations for the indicated
module or modules (the name may be wildcarded), but there
are no reservations in the VDE database for that module or
those modules.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated module or modules are not reserved.

<MSG>(NORESREP\no RESREP privilege; cannot reserve and replace modules )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOSCRATCH\no SYS$SCRATCH translation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The translation of the SYS$SCRATCH logical name is not valid.
<MSG_TEXT>(User Action)
Reenter the VDE command after redefining SYS$SCRATCH to a
valid directory specification.

<MSG>(NOSCRIPTYP\no script type specified on command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The current SCRIPT command (such as CREATE SCRIPT) does not
include any qualifier to specify the type of script that the
command should apply to.  As a result, the command cannot be
performed.
<MSG_TEXT>(User Action)
Reenter the command with a qualifier to specify the script
type of the script.

<MSG>(NOSCT\replacement cause not known; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was not provided with the cause of the replacement
being performed.  The cause of a replacement -- usually
a Source Code Tracking (SCT) entry or a source code
Fold -- is tracked.
<MSG_TEXT>(User Action)
Specify the SCT note via the /SCT or /NOTE qualifiers
on the REPLACE command, or by providing answers to teh
replacement prompts within VDE.

<MSG>(NOSCTSRC\source file <EMPHASIS>(record) for SCT note not found )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE is not able to locate the source file for the SCT
note.
<MSG_TEXT>(User Action)
Respecify the command, using a file that exists.

<MSG>(NOSETLIB\the SET LIBRARY command is locked out )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The SET LIBRARY command is disabled when executing a
beta version of VDE.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains beta-only images.

<MSG>(NOSETTERM\the SET TERMINAL command is not supported on this terminal )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
SET TERMINAL is only supported on VT52, VT100-series,
VT200-series, VT300-series, VT400-series, VT500-series,
and DECterm terminals.

<MSG>(NOSPAWN\spawn command failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A process cannot be spawned by VDE.
<MSG_TEXT>(User Action)
Check your process's quotas.

<MSG>(NOSTAGROOT\no staging area root directory exists for library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to create queued replacement for some module,
but no staging area root directory exists for the library.
Hence VDE cannot create a disk directory for saving (or
<QUOTE>(staging)) the files to be replaced.
<MSG_TEXT>(User Action)
Use the CREATE DIRECTORY_TREE/STAGING command to create
the root directory for the library's staging areas.  Then
reenter the REPLACE command.  Alternatively, replace the
module with an immediate (as opposed to queued) replacement.
An immediate replacement does not use a staging area.

<MSG>(NOSTRMROOT\no stream root directory exists for stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to create a directory tree for a specific
facility within the current stream, but no root directory
exists for the stream.  Hence VDE cannot create any disk
directories for the indicated facility.
<MSG_TEXT>(User Action)
Use the CREATE DIRECTORY_TREE command to create a
directory tree for the current stream.  That will
automatically create both the stream root directory
and the subdirectories for all facilities.

<MSG>(NOSTRMSPEC\no stream specified for operation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The command you have entered requires that you specify
the name of a development stream, either with the /STREAM
qualifier or as a command parameter, but the stream name
is missing on the entered command.
<MSG_TEXT>(User Action)
Renter the command, specifying the stream name as required.

<MSG>(NOSUCHARCH\architecture <EMPHASIS>(architecture) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated architecture name was entered on a command,
but no such architecture was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated architecture does not exist in the
database.  However, if you had expected such an architecture
to exist, you may use the SHOW ARCHITECTURE command to see
what architectures are found in the database.  If the
desired architecture is not there, ask your project
administator to add it to the database.  Then reenter your
command with a valid architecture name.

<MSG>(NOSUCHCTX\context <EMPHASIS>(context) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated context name was entered on a command, but
no such context was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated context does not exist in the database.
However, if you had expected such a context to exist, you may
use the SHOW CONTEXT command to see what contexts are found
in the database.

<MSG>(NOSUCHDIRSYM\directory symbol <EMPHASIS>(symbol) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated directory symbol was referenced by a script
but no such directory symbol was found in the VDE database.
VDE tried to use the directory symbol either to look up the
directory location for the script's DCL command file or to
evaluate a script function such as $DIR or $STRMDIR.  The
most likely reason for the error is that you used a script
function that takes a directory symbol as a parameter, and
you misspelled the symbol name or specified a symbol you
have not yet defined.  Directory symbols are defined with
the /SYMBOL qualifier of the SET DIRECTORY command.
<MSG_TEXT>(User Action)
Correct the script function call to have a correct directory
symbol that is already defined.  Then reenter the script in
the database with the CREATE SCRIPT command and reenter the
command that got the error message.

<MSG>(NOSUCHFAC\facility <EMPHASIS>(facility) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated facility name was entered on a command, but
no such facility was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated facility does not exist in the database.
However, if you had expected such a facility to exist, you may
use the SHOW FACILITY command to see what facilities are
found in the database.  If the desired facility is not there,
ask your project administator to add it to the database.
Then reenter your command with a valid facility name.

<MSG>(NOSUCHFOLD\fold record <EMPHASIS>(record) not found for module <EMPHASIS>(module) and stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to reference a fold record with the indicated
fold identifier for the indicated module and stream, but
there is no such fold record in the VDE database.  As a
result, VDE has aborted the current command and rolled
back the current transaction.
<MSG_TEXT>(User Action)
Specify a valid fold record and reenter the command.

<MSG>(NOSUCHFUNC\no such script function exists: <EMPHASIS>(function) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated script function was specified in a VDE
script, but no such function exists.  The most likely
cause for this error is that you misspelled the function
name.  VDE recognizes a script function by the fact that
all script function names begin with a dollar sign.
Directory symbol names, which can appear in the same
places as functions in scripts, should not begin with
dollar signs.
<MSG_TEXT>(User Action)
Correct the spelling of the function name or select a
directory symbol name that does not begin with a dollar
sign.

<MSG>(NOSUCHGEN\generation <EMPHASIS>(generation) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated module generation was entered on a command,
but no such generation was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated generation does not exist in the
database.  However, if you had expected such a generation
of a module to exist, you may use the SHOW GENERATION
command to see what module generations are found in the
database.

<MSG>(NOSUCHGRP\group <EMPHASIS>(group) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated group name was entered on a command, but
no such group was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated group does not exist in the
database. However, if you had expected such a group
to exist, you may use the SHOW GROUP command to see
what groups are found in the database.  If the desired
group is not there, use the CREATE GROUP command
to add it to the database.  Then reenter your command with
a valid group name.

<MSG>(NOSUCHMOD\module <EMPHASIS>(module) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated module name was entered on a command, but
no such module was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated module does not exist in the database.
However, if you had expected such a module to exist, you may
use the SHOW MODULE command to see what modules are found
in the database.  If the desired module is not there, you
can use the CREATE MODULE command to add it to the database.
Then reenter your command with a valid module name.

<MSG>(NOSUCHPRIV\no such privilege name exists: <EMPHASIS>(priv-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An invalid privilege name was specified on a VDE command.
<MSG_TEXT>(User Action)
Check the spelling of the privilege name and reenter the
command with a correct privilege name.

<MSG>(NOSUCHQUE\batch queue <EMPHASIS>(queue) does not exist; check spelling )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a batch queue on a BUILD command or a
related command, but that queue does not exist on the
system.  Possibly you have misspelled the queue name.
Hence build jobs cannot be submitted to that batch queue.
<MSG_TEXT>(User Action)
Specify a valid queue name and restart the build job.

<MSG>(NOSUCHREP\replacement <EMPHASIS>(replacement) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated replacement name was entered on a command, but
no such replacement was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated replacemen does not exist in the database.
However, if you had expected such a replacemen to exist, you may
use the SHOW REPLACMENT command to see what replacements are
found in the database.  If the desired replacement is not there,
ask your project administator to add it to the database.
Then reenter your command with a valid replacement name.

<MSG>(NOSUCHRES\reservation <EMPHASIS>(reservation) for module <EMPHASIS>(module) not found )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a reservation identifier for a module
reservation, but no reservation with that identifier exists.
Hence the current command has not been performed for that
reservation.
<MSG_TEXT>(User Action)
Specify the correct reservation identifier and reissue the
command.

<MSG>(NOSUCHSCRP\script <EMPHASIS>(script) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated script was specified on a command, but no such
script is found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated script does not exist in the database.
However, if you had expected such a script to exist, you may
use the SHOW SCRIPT command to see what scripts are present
in the database.

<MSG>(NOSUCHSES\session <EMPHASIS>(session) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated session name was entered on a command, but
no such session was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated session does not exist in the database.
However, if you had expected such a session to exist, you may
use the SHOW SESSION command to see what session are
found in the database.  If the desired session is not there,
ask your project administator to add it to the database.
Then reenter your command with a valid session name.

<MSG>(NOSUCHSTEP\no build step for module <EMPHASIS>(module) found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
No compile or link build step is recorded in the database
for the indicated module.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated build step is not represented in
the database.  However, if you had expected such a build
step to exist, you may use the SHOW STEP command to see
what build steps are found in the database.

<MSG>(NOSUCHSTRM\stream <EMPHASIS>(stream) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated stream name was entered on a command, but
no such stream was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated stream does not exist in the database.
However, if you had expected such a stream to exist, you may
use the SHOW STREAM * command to see what streams are
found in the database.  If the desired stream is not there,
ask your project administator to add it to the database.
Then reenter your command with a valid stream name.

<MSG>(NOSUCHSYM\no such symbol '<EMPHASIS>(text)' exists )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
No symbols matching the given symbol specification have been
found.
<MSG_TEXT>(User Action)
Check the spelling of the symbol specification in question.
The SHOW SYMBOL * command can also be used to display all the
symbol names.

<MSG>(NOSUCHUSER\user <EMPHASIS>(user) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated username was entered on a command, but no
such user was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated user does not exist in the database.
However, if you had expected such a user to exist, you may
use the SHOW USER * command to see what usernames are found
in the database.  If the desired user is not there, ask
your project administator to add that user to the database.
Then reenter your command with a valid username.

<MSG>(NOTCONNLIB\you are not connected to a VDE library; command not performed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to perform a command that requires you to
be connected to an existing VDE library, but you are not
connected to such a library.  This normally means that you
have not defined logical name VDE$LIBRARY to point to the
root directory of a properly formed VDE library that you
are authorized to use.  This problem can also occur after
you have encountered an error when trying to set or create
a new library; you are then disconnected from the formerly
set library without successfully connecting to the new one,
leaving you unconnected to any library.
<MSG_TEXT>(User Action)
Define logical name VDE$LIBRARY to point to the root
directory for the VDE library you wish to access.  Then
try the command again.

<MSG>(NOTEID\topic <EMPHASIS>(major).<EMPHASIS>(minor) entered in conference )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that VDE has entered a note
into a notes conference on behalf of the user.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(NOTESCONF\accessing notes conference <EMPHASIS>(conference) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has successfully
opened the indicated notes conference for notes access.
<MSG_TEXT>(User Action)
None

<MSG>(NOTESENT\note posted in conference <EMPHASIS>(conference) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has successfully
posted a note in the indicated notes conference.  This message
is issued when you use the /LOG qualifier on a command that
sends notifications to notes conferences.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(NOTESENTID\note <EMPHASIS>(noteID) posted in conference <EMPHASIS>(conference) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has successfully
posted a note in the indicated notes conference.  This message
is issued when you use the /LOG qualifier on a command that
sends notifications to notes conferences.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(NOTESERR\error from DEC Notes at <EMPHASIS>(routine-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has encountered an error while using the notes callable
interface.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one, check the documentation
for information on setting up the notes conferences, and
contact VDE support for assistance.

<MSG>(NOTESID\unable to parse DEC Notes topic <EMPHASIS>(note-number) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has encountered an error while using the notes callable
interface.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one, check the documentation
for information on setting up the notes conferences, and
contact VDE support for assistance.

<MSG>(NOTEXTSTR\text string argument missing in call to <EMPHASIS>(routine-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an inconsistency within an internal
routine which uses the notes callable interface.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(NOTIMPL\this feature is not currently implemented )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated feature
or callback is not currently implemented.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.

<MSG>(NOTINRANGE\integer value <EMPHASIS>(number) not in valid range of <EMPHASIS>(low-bound) to <EMPHASIS>(high-bound) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated integer value is not within the valid range
for the qualifier or parameter on which it is specified.
<MSG_TEXT>(User Action)
Reenter the command with the integer value within the
proper range.

<MSG>(NOTPROP\generation <EMPHASIS>(generation) not propagated past stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Because the /PROPAGATE or /NOPROPAGATE qualifier was
specified on the REPLACE command, the indicated module
generation is not propagated past the indicated development
stream.
<MSG_TEXT>(User Action)
None.  This is an informational message that merely confirms
that VDE performed change propagation as requested.

<MSG>(NOTRESINSTRM\module <EMPHASIS>(module) not reserved in stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to unreserve or replace a module in the
indicated stream, but the module is not reserved in that
stream.
<MSG_TEXT>(User Action)
Use the SHOW RESERVATION/FULL command to see what stream the
reservation was made in.  Then use the SET STREAM command
to set the current stream to the appropriate stream and
re-enter the command, or (when available) you can append
the /STREAM qualifier on the failing command and reissue
the command.  If you are performing a REPLACEMENT, a
replacement performed in the ancestor stream propogated
forward into any and successors of the target stream.

<MSG>(NOTREVREP\you are not a reviewer for replacement <EMPHASIS>(replacement) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to mark a replacement as accepted or
rejected, but you are not a reviewer for the replacement.
As a result, your attempt to mark the replacement as
accepted or rejected has failed.
<MSG_TEXT>(User Action)
Specify the name of a replacement for which you are a
reviewer or have yourself added as a reviewer by someone
authorized to add you.

<MSG>(NOUNCLOSE\no UNCLOSE privilege; cannot unclose a closed stream )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOUSERNAME\no USERNAME privilege; cannot reserve and replace for other users )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NOVDEDEVO\no VDEDEVO privilege; access to dungeon restricted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You attempted to use a command or qualifier that
requires one or more VDE privileges, and you did not
have sufficient privileges enabled.  This message is
normally displayed in conjunction with other error
messages, usually a no-privilege error.
<MSG_TEXT>(User Action)
If you are authorized to use the privilege, use the
VDE SET PRIVILEGES command to give yourself the necessary
privilege.  Then try the original operation again.  If
you are not authorized to use the qualifier, you should
either request the necessary privilege from your project
administrator or you should not use the qualifier.

<MSG>(NULSTRNOT\a null string is not allowed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This qualifier requires that a string with a minimum length
of 1 character be provided if any string is specified at all.
The null string is not allowed.
<MSG_TEXT>(User Action)
Reenter the command providing a string with this qualifier,
or no value at all.

<MSG>(NYI\feature not yet implemented )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected a request for a feature that has not
yet been implemented.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include any
information that may be useful or relevent in duplicating the
problem.

<MSG>(OFFLINE\source code control system offline, try again later )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE system is offline for maintenance or upgrade,
please try your request again later.
<MSG_TEXT>(User Action)
The VDE system is offline fopr maintenance or upgrade,
please try again later.  If you have questions, please
contact VDE support or the system management staff for
assistance.

<MSG>(OUTFILE\output file is <EMPHASIS>(file) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Indicates the output file of the current command.  The
FETCH and RESERVE commands display this message to show
the location of the output file containing the fetched
module generation.
<MSG_TEXT>(User Action)
None.  This is an informational message.

<MSG>(OUTMODSRC\output module <EMPHASIS>(module) of build step is a source module; ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The automatically collected dependency information for the
current build step specifies that the indicated module is
an output from the step.  However, the module is marked as
a source module in the VDE database, and a source module
cannot be an output of a build step.  Hence this dependency
information is ignored and is not recorded in the database.
<MSG_TEXT>(User Action)
If the module is erroneously marked as a source module in
the VDE database, you should delete the module and rerun
the build step.  If the module actually is a source module,
you should investigate why the compiler or other processor
specifies it as an output from the build step.

<MSG>(OUTNLA0\if /OUTPUT=NLA0: was used, respecify with non-null output )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message suggests a workaround for a failure to fetch
a module -- this situation occurs only when fetching or
reserving a module that uses a marker file, and when
/OUTPUT=NLA0: was specified on the command.  The underlying
problem will be fixed in a future release of VDE.
<MSG_TEXT>(User Action)
If fetching or reserving a module that uses a marker file,
respecify the command with a non-null output device and
directory.

<MSG>(OVERRIDE\VDE library controls overridden via OpenVMS privileges )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An attempt has been made to perform an operation that
VDE would normally prohibit, but VDE has allowed
the operation because of OpenVMS privileges possessed
by the caller.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(OVFLOWBUF\overflow of the input buffer, command ignored. )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A VDE command line may only consist of records that are less
than 1024 characters long.
<MSG_TEXT>(User Action)
If you want more than 1024 characters for input, divide each
line into records that are less than 1024 characters and use
the continuation character "-" at the point of each break.  If
the sum of these records are greater than 32,768 characters,
then the complete command line cannot be processed.

<MSG>(PREFIXNOTALL\prefix VDE$ not allowed in facility or stream names )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to create or rename a facility or stream
with a name that begins with the prefix <QUOTE>(VDE$)
but VDE does not allow facilities or streams to have
such names.  VDE uses facility and stream names as disk
directory names, but VDE also creates directories reserved
for its own use whose names always begin with the VDE$
prefix.  To prevent name conflicts between facility or
stream directories and these reserved directories, VDE
does not allow facility or stream names to begin with
the VDE$ prefix.
<MSG_TEXT>(User Action)
Reenter the command with a facility or stream name that
does not begin with VDE$.

<MSG>(PROTOLIB\using prototype library <EMPHASIS>(library) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to indicate that the version of
VDE in use contains debug or prototype code, and as
a result, that a particular library is being used.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug or prototype images.

<MSG>(PROTOTYPE\this is a prototype version of VDE )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to indicate that the version of
VDE in use contains debug or prototype code.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debug or prototype images.

<MSG>(QARDBSYNTAX\invalid QAR database name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the QAR database
name is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the QAR database name using only
alphanumeric, underscore, dollar sign and hyphen
characters.

<MSG>(QCHECKCOUNT\queued.checkin.count: <EMPHASIS>(count) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QDATETIME\queued.checkin.datetime: <EMPHASIS>(datetime) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QERRORS\queued.checkin.defectsfixed: <EMPHASIS>(defects) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QGROUP\queued.checkin.group: <EMPHASIS>(group) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QITEM\queued.checkin.item: <EMPHASIS>(item) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QLIBMNE\queued.library.mnemonic: <EMPHASIS>(libmnemonic) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QMODULE\queued.checkin.module: <EMPHASIS>(modname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QNOTE\queued.checkin.note: <EMPHASIS>(topic).<EMPHASIS>(reply) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QPROJECT\queued.project.name: <EMPHASIS>(project) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QREASON\queued.checkin.reasonmask: <EMPHASIS>(reason) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QREPLID\queued.checkin.replacementid: <EMPHASIS>(replid) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QREPLNAME\queued.checkin.replname: <EMPHASIS>(replname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QRMPBCOUNT\queued.module.count: <EMPHASIS>(count) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QRMPBMODFLAG\queued.module.modflags: <EMPHASIS>(modflags) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QRMPBMODNAME\queued.module.modname: <EMPHASIS>(modname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QRMPBREPLREMARK\queued.module.replaceremark: <EMPHASIS>(replaceremark) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QRMPBRESREMARK\queued.module.reserveremark: <EMPHASIS>(reserveremark) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QRMPBSTAGING\queued.module.staging: <EMPHASIS>(staging) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QSTREAM\queued.checkin.stream: <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QTYPCOD\queued.checkin.typecode: <EMPHASIS>(type) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QTYPNAM\queued.checkin.typename: <EMPHASIS>(type) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(QUALDISALL\qualifier <EMPHASIS>(qualifier) is disallowed for the <EMPHASIS>(command) command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a command qualifier that is not
allowed with the specified command.  Because the
qualifier is not allowed, the command is not executed.
In certain cases, the qualifier is disallowed by your
VDE library due to a library attribute, and the
qualifier would be allowed if the library attribute
that disallows it were changed.
<MSG_TEXT>(User Action)
Reenter the command without the offending qualifier or
change the library attribute that disallows it, if
applicable.

<MSG>(QUALNOTALL\qualifier <EMPHASIS>(qualifier) is not allowed when a parameter is specified )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified both the indicated qualifier and a command
parameter on a command that does not allow both to be
specified.  The command is not executed for this reason.
<MSG_TEXT>(User Action)
Reenter the command with either the indicated qualifier or
with command parameters, but not both.

<MSG>(QUALTOOMANY\qualifier <EMPHASIS>(qualifier) has been specified too many times )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified the indicated qualifier too many times for
a parameter on this command line.  The command is not executed
for this reason.
<MSG_TEXT>(User Action)
Reenter the command with the indicated qualifier specified no
more than once for each parameter.

<MSG>(QUECLOSED\batch queue <EMPHASIS>(queue) is closed and cannot accept jobs )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated batch queue is closed and cannot accept
batch jobs.  It thus cannot be used to run the build
job you are starting.
<MSG_TEXT>(User Action)
You can either run the build job on the remaining batch
queues you have specified, or you can restart the build
job and specify a different set of batch queues for it.

<MSG>(QUEPAUSED\batch queue <EMPHASIS>(queue) is paused or pausing; job execution is halted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated batch queue is paused or in the process of
pausing.  You can still submit batch jobs to the queue, but
the jobs will not execute until the pause condition ends.
<MSG_TEXT>(User Action)
You can either let the build job be queued to the paused
batch queue and wait for the pause condition to end, or you
can restart the build job and specify a different set of
batch queues for it.

<MSG>(QUESTOPPED\batch queue <EMPHASIS>(queue) is stopped or stopping; job execution is halted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated batch queue is stopped or in the process of
stopping.  You can still submit batch jobs to the queue,
but the jobs will not execute until the queue is started
by a system manager or operator.
<MSG_TEXT>(User Action)
You can either let the build job be queued to the stopped
batch queue and wait for the queue to be started, or you
can restart the build job and specify a different set of
batch queues for it.

<MSG>(QUOCHECK\performing a quota check operation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that the VDE/READ_UAF image
is checking process quotas in the SYSUAF, and that
it will NOT update quota settings in the SYSUAF.
<MSG_TEXT>(User Action)
Informational, no action is necessary

<MSG>(QUOLOW\quota <EMPHASIS>(quota) set to: <EMPHASIS>(old), recommended: <EMPHASIS>(new) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that the VDE/READ_UAF image
has detected a username with a quota value that is
below the recommended settings.
<MSG_TEXT>(User Action)
Contact your local system manager, and ask that
the quotas on the specified user be checked against
the VDE minimum values, and raised where necessary.
The system manager or VDE database administrator
can use the VDE command VDE/READ_UAF/WRITE_UAF to
raise the process quotas to the required minimum
values on all VDE users.  (Process quota values
above the required minimums will not be altered.)

<MSG>(QUORESET\performing a quota check and update operation )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that the VDE/READ_UAF image
is checking process quotas in the SYSUAF, and that
it WILL update quota settings in the SYSUAF.
<MSG_TEXT>(User Action)
Informational, no action is necessary

<MSG>(QUOSTREXP\quoted string expected )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
A quoted string was expected.  This quoted
string must be delimited by either single or double quotes.

<MSG>(QUOUSER\user <EMPHASIS>(user) below recommended quota setting(s) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that the VDE/READ_UAF image
has detected a username with a quota value that is
below the recommended settings.
<MSG_TEXT>(User Action)
Contact your local system manager, and ask that
the quotas on the specified user be checked against
the VDE minimum values, and raised where necessary.
The system manager or VDE database administrator
can use the VDE command VDE/READ_UAF/WRITE_UAF to
raise the process quotas to the required minimum
values on all VDE users.  (Process quota values
above the required minimums will not be altered.)

<MSG>(QUSERNAME\queued.checkin.username: <EMPHASIS>(username) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.
! ========== ========== ==========

<MSG>(READERR\VDE input read error, forced to exit )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error was found in reading an input line.
<MSG_TEXT>(User Action)
All command line information is read from the logical
VDE$INPUT.  Something is interfering with the reading from
the file or device that is specified by this logical name.
Determine where VDE$INPUT is pointing. If you cannot
determine what is causing the interference, please submit
a problem report.

<MSG>(REGRESSION\operating in mode suitable for regression tests )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message indicates that the VDE image has detected
a request to switch into a mode suitable for operations
within a VDE regression test suite.  This request can
be initiated only by a user with OpenVMS privileges,
or by a VDE image linked with this mode enabled.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as this message
should not be displayed under normal operations.

<MSG>(REPACCEPT\replacement <EMPHASIS>(replacement) marked as accepted in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the VDE database now records
that you have accepted the indicated replacement.  This
message is only issued when you use the /LOG qualifier on
the ACCEPT REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(REPADDED\replacement <EMPHASIS>(replacement) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated replacement
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the REPLACE  command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(REPBELUSER\replacement <EMPHASIS>(replacement) belongs to another user )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to modify or cancel a queued replacement
that belongs to another user, and you do not have the
PERFREP privilege that would allow you to cancel or modify
another user's replacements.  As a result, the replacement
is not cancelled or modified.
<MSG_TEXT>(User Action)
Reenter the command specifying your own queued replacement
to cancel or modify, or else have someone with the necessary
privilege perform the operation.

<MSG>(REPCAN\replacement <EMPHASIS>(replacement) cancelled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated replacement
has been cancelled. This message is only issued when you
use the /LOG qualifier on the CANCEL REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(REPDEL\replacement <EMPHASIS>(replacement) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated replacement has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(REPEXISTS\replacement <EMPHASIS>(replacement) already exists; replacement not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated replacement name was specified on a
REPLACE command, but an entry for that replacement is already
present in the database.  Hence a new entry was not created
for that replacement.  Alternatively, the indicated name was
specified as the new name for an existing replacement on the
MODIFY REPLACEMENT command, but another replacement already has
the requested new name.  Hence the name of the existing
replacement could not be changed to the new name.
<MSG_TEXT>(User Action)
If you entered the wrong replacement name, reenter the command
with the correct name.  If you entered the right replacement
name, use the SHOW REPLACEMENT command to display the database
information for that replacement. If you are not satisfied
with that information, use the MODIFY REPLACEMENT command to
change it.

<MSG>(REPLACED\generation <EMPHASIS>(generation) replaced into stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
been replaced into the indicated development stream in
the current VDE library.  It has also been assigned the
indicated generation number.  This message is only issued
when you use the /LOG qualifier with the REPLACE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(REPLQUE\module <EMPHASIS>(module) queued for replacement <EMPHASIS>(replacement) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
been queued for replacement as a member of the named
replacement.  This message is only issued when you use
the /LOG qualifier on the REPLACE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(REPMOD\information for replacement <EMPHASIS>(replacement) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
replacement has been modified in the VDE database.  This
message is only issued when you use the /LOG qualifier on the
MODIFY REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(REPNOTFOUND\replacement <EMPHASIS>(replacement) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated repalcement name was entered on a SHOW
REPLACEMENT command, but no such replacement was found in
the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated replacement does not exist in the
database.

<MSG>(REPNOTPERF\replacement <EMPHASIS>(replacement) for stream <EMPHASIS>(stream) not performed; does not match stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated replacement
has not been performed because it belongs to a stream
that does not match the stream name you specified with
the /STREAM qualifier to the PERFORM REPLACEMENT command
(or your default stream).  This message is only issued
when you use the /LOG qualifier on the PERFORM REPLACEMENT
command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(REPPERF\replacement <EMPHASIS>(replacement) performed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated replacement
has been performed.  This message is only issued when you
use the /LOG qualifier on the PERFORM REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(REPREJECT\replacement <EMPHASIS>(replacement) marked as rejected in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the VDE database now records
that you have rejected the indicated replacement.  This
message is only issued when you use the /LOG qualifier on
the REJECT REPLACEMENT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(REPSYNTAX\invalid replacement name syntax: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The name or format specified for the replacement name
is not using valid syntax.
<MSG_TEXT>(User Action)
Respecify the replacement name using only alphanumeric,
underscore, dollar sign and hyphen characters.

<MSG>(REQQUAMIS\required command qualifier missing )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Both the DEFINE and DELETE commands must have a qualifier to
specify the type of definition or deletion.  You must use
either /KEY or /COMMAND.

<MSG>(RESDEL\reservation <EMPHASIS>(reservation) of <EMPHASIS>(module) for user <EMPHASIS>(user) has been deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated reservation
has been deleted from the VDE database because you
performed an operation that changed what generation is
the latest generation of the module for some stream.
Such operations include the DELETE, INSERT, and REMOVE
GENERATION commands.  After such an operation, the
reservation is based on the wrong generation and can
no longer be replaced into the stream.
<MSG_TEXT>(User Action)
None.  The affected users will be informed that their
reservations are deleted.  They should reserve the module
again and redo their changes.

<MSG>(RESERVED\generation <EMPHASIS>(generation) reserved from stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module and
generation has been reserved from the current library.
This message is only issued when you use the /LOG
qualifier on the RESERVE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(RESERVSES\generation <EMPHASIS>(generation) reserved from stream <EMPHASIS>(stream) for session <EMPHASIS>(session) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module and
generation has been reserved from the VDE library and
is part of the indicated reservation session.  This
message is only issued when you use the /LOG qualifier
on the RESERVE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(RESIDREQ\reservation identifier required for module <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have multiple reservations for the indicated module.
You must therefore specify a reservation identifier with
the /IDENTIFICATION qualifier to uniquely indicate to which
reservation you want the command to apply.
<MSG_TEXT>(User Action)
Reissue the command with the /IDENTIFICATION qualifier to
indicate the specific reservation to which you want the
command to apply.

<MSG>(RESIDUSED\reservation Id <EMPHASIS>(ID) already used for module <EMPHASIS>(module)      attempt to reserve module has failed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to reserve a module concurrently using the
same reservation identification as you have used on a previous
reservation of the same module in the same stream
development stream.  This is not allowed, since reservation
identifications must be unique.
<MSG_TEXT>(User Action)
Reissue the RESERVE command with a different reservation
identification specified on the /IDENTIFICATION qualifier.
Alternatively, you can omit the /IDENTIFICATION qualifier,
in which case VDE will assign a unique identification for you.

<MSG>(RESMOD\reservation <EMPHASIS>(reservation) for module <EMPHASIS>(module) modified in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated reservation
record for the indicated module has been modified in the
VDE database.  This message is only issued when you use
the /LOG qualifier on the MODIFY RESERVATION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(RESQUEUED\reservation request for <EMPHASIS>(module) queued for stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has queued a reservation
request for the indicated module and development stream.
This message is only issued when you use the /LOG
qualifier on the RESERVE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(RETURNED\control returned to process <EMPHASIS>(process-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
After performing either a SPAWN or ATTACH operation, this
message will be generated to inform you when you have
returned to VDE's process.

<MSG>(RIGIDNOTFOU\required rights identifier <EMPHASIS>(ID) not found in rights database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have not yet been added to the VDE database, and to
be added you must hold the indicated VMS rights identifier.
However, that rights identifier is not present in the
system rights database.  As a result, you are not allowed
access to the VDE library.
<MSG_TEXT>(User Action)
Have your system manager add the rights identifier to the
system rights database and assign it to the users who
should have access to the VDE library, or have the VDE
library maintainer use the MODIFY LIBRARY command specify
the correct rights identifier in the VDE database.

<MSG>(RIGIDNOTHELD\you do not hold required rights identifier <EMPHASIS>(ID) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have not yet been added to the VDE database, and to
be added you must hold the indicated VMS rights identifier.
However, you do not hold that rights identifier in the
system rights database.  As a result, you are not allowed
access to the VDE library.
<MSG_TEXT>(User Action)
If you should have access to the VDE library, have your
system manager assign you the indicated rights identifier.
Then try accessing the VDE library again.

<MSG>(ROLLBACK\database transaction has been rolled back )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The database transaction associated with the current
command has been rolled back because an error occurred
while processing the command.  This means that all changes
the command would have made to the database if successful
have in fact been removed from the database.
<MSG_TEXT>(User Action)
Correct the error and retry the command.

<MSG>(SCRDONE\completed wait for script )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has completed a wait
for a script.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(SCRIPTONLY\VDE/STATUS is invoked only within scripts )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is indicates the user has attempted to
invoke the VDE/STATUS command at the DCL prompt; this
command is for script processing within VDE and is not
intended to directly accessed by users.
<MSG_TEXT>(User Action)
Don't do this.

<MSG>(SCRLOAD\loading script into subprocess )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE has loaded a script into
a subprocess for execution.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(SCRPADDED\script from file <EMPHASIS>(file) added to the database      script <EMPHASIS>(script) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated script has
been added to the VDE database from the indicated file.
The script only applies to the current stream.  This
message is only issued when you use the /LOG qualifier
on the CREATE SCRIPT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SCRPCMDTOOLONG\script command is too long; it exceeds <EMPHASIS>(count) characters )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have entered a script command that is too long for
VDE's internal script command buffer.  The message
indicates the maximum size of this buffer.  The total
length of the script command includes the initial line
for the command and all continuation lines.
<MSG_TEXT>(User Action)
Change the script command so that it is not so long.

<MSG>(SCRPDEL\script deleted from the database      script <EMPHASIS>(script) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated script for the
current stream has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE SCRIPT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SCRPEXTR\script extracted to file <EMPHASIS>(file)      script <EMPHASIS>(script) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated script has
been extracted from the VDE database into the indicated
file.  This message is only issued when you use the /LOG
qualifier on the EXTRACT SCRIPT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SCRPFACFAIL\script for facility <EMPHASIS>(facility) terminated with errors )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The script for the indicated facility terminated with
errors when executed for the current command.  The type
of the script depends on the command.  For the CREATE
STREAM command, for example, the new-stream script
is invoked to perform part of the stream creation.
<MSG_TEXT>(User Action)
Correct the error in the script and reenter the command.

<MSG>(SCRPFILE\script produced DCL command file <EMPHASIS>(file)      script <EMPHASIS>(script) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated script has
been invoked to produce the DCL command file whose name
is given in the message.  This message is only issued when
you use the /LOG qualifier on the INVOKE SCRIPT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SCRPFUNCUNDEF\script function <EMPHASIS>(function) is undefined in the current script )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated script function is used in the currently
executing script, but is undefined for this type of
script.  This means that the function is not allowed
to be used in this type of script.  The module-name
functions, for example, are undefined in scripts invoked
at stream creation because these scripts are not applied
to individual modules.
<MSG_TEXT>(User Action)
Do not use the indicated function in the script.

<MSG>(SCRPMOD\script information modified in the database      script <EMPHASIS>(script) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
script has been modified in the VDE database.  The modified
attributes only apply to the current stream.  This message
is only issued when you use the /LOG qualifier on the MODIFY
SCRIPT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SCRPMODFAIL\<EMPHASIS>(script) script for module <EMPHASIS>(module) terminated with errors )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The script for the indicated module terminated with
errors when executed for the current command.  The
type of the script is specified in the message.
<MSG_TEXT>(User Action)
Correct the error in the script and reenter the command.

<MSG>(SCRPUSED\script <EMPHASIS>(stript) was used )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated script was used
to generate one segment of the current DCL command file.
This message is only issued when you use the /LOG qualifier
on the INVOKE SCRIPT command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SCRQUOERR\no closing quotation mark in script command:!/<EMPHASIS>(cmd) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected a missing quote in the specified
command for the script.  The script command must be
respecified using correct syntax.
<MSG_TEXT>(User Action)
The script command must be respecified using
correct syntax.

<MSG>(SCRWAIT\commencing wait for script )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that VDE is commencing a wait
operation for a script.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use contains debugging images.

<MSG>(SCTCONF\SCT note conference null; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The required SCT notes conference name field was found
empty on a replacement operation.
<MSG_TEXT>(User Action)
Please reenter the SCT notes conference name using
correct syntax, and retry the replacement operation.

<MSG>(SCTCONFSYN\SCT note conference syntax error; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE detected a syntax error in the SCT notes conference
name field.
<MSG_TEXT>(User Action)
Please reenter the SCT notes conference name using
correct syntax, and retry the replacement operation.

<MSG>(SCTFCMT\SCT fold comment required; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The required SCT fold comment field was found empty
on a replacement operation.
<MSG_TEXT>(User Action)
Enter an SCT fold comment and retry the replacement
operation.

<MSG>(SCTFNF\unable to locate notes conference <EMPHASIS>(confname) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE was unable to open the specified SCT notes
conference
<MSG_TEXT>(User Action)
Please reenter the SCT notes conference name using the
correct name and syntax, and retry the operation.  If the
conference is missing, contact the project leader, the
system manager(s), or VDE support for assistance.

<MSG>(SCTNOTE\SCT note number null; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The required SCT note number field was found empty
on a replacement operation.
<MSG_TEXT>(User Action)
Enter the number of the associated SCT note using
correct syntax, and retry the replacement operation.

<MSG>(SCTNOTESYN\SCT note number syntax error; module not replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE detected a syntax error in the SCT note number
field.
<MSG_TEXT>(User Action)
Please reenter the SCT note number using correct
syntax, and retry the replacement operation.

<MSG>(SECMERFAI\secondary merge failure )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
internal state information for VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Correct the cause of the VDE$_INVDIRSPEC error.

<MSG>(SEECONLIB\see the VDE CONVERT LIBRARY command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE database does not have the proper format, and the
automatic conversion of the database has been disabled.
The VDE CONVERT LIBRARY command can be used to force the
conversion of the database format.
<MSG_TEXT>(User Action)
If use of the new version of VDE is intended, perform a
full library backup using the database-provided backup
tools, and then use the VDE CONVERT LIBRARY command to
update the database format.

<MSG>(SESADDED\session <EMPHASIS>(session) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated session
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the REPLACE  command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(SESBELUSER\session <EMPHASIS>(session) belongs to another user )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to modify or cancel a reservation session
that belongs to another user, and you do not have the
PERFREP privilege that would allow you to cancel or modify
another user's session.  As a result, the session is not
cancelled or modified.
<MSG_TEXT>(User Action)
Reenter the command specifying your own reservation session
to cancel or modify, or else have someone with the necessary
privilege perform the operation.

<MSG>(SESCAN\session <EMPHASIS>(session) cancelled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated session
has been cancelled. This message is only issued when you
use the /LOG qualifier on the CANCEL SESSION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(SESEXISTS\session <EMPHASIS>(session) already exists in database; session not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated session name was specified on a
REPLACE command, but an entry for that session is already
present in the database.  Hence a new entry was not created
for that session.  Alternatively, the indicated name was
specified as the new name for an existing session on the
MODIFY SESSION command, but another session already has
the requested new name.  Hence the name of the existing
session could not be changed to the new name.
<MSG_TEXT>(User Action)
If you entered the wrong session name, reenter the command
with the correct name.  If you entered the right session
name, use the SHOW SESSION command to display the database
information for that session. If you are not satisfied
with that information, use the MODIFY SESSION command to
change it.

<MSG>(SESMOD\information for session <EMPHASIS>(session) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
session has been modified in the VDE database.  This
message is only issued when you use the /LOG qualifier on the
MODIFY SESSION command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(SESNOMODS\session <EMPHASIS>(session) contains no module reservations )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the reservation session
you are replacing or unreserving contains no module
reservations.  The command deleted the session from the
VDE database, but did not replace or unreserve any modules.
<MSG_TEXT>(User Action)
If you meant to replace modules you have already reserved,
replace them individually.  Alternatively, use the RESERVE
command to create a new session that contains reservations
for the desired modules.  Then change the modules and
replace the session.

<MSG>(SESNOTFOUND\session <EMPHASIS>(session) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated session name was entered on a SHOW
SESSION command, but no such session was found in
the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated session does not exist in the
database.

<MSG>(SESTERM\session <EMPHASIS>(session) terminated )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated session has
been terminated.  This message is only issued when you
use the /SESSION and /LOG qualifiers on the REPLACE or
UNRESERVE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(SETKEY\keypad state has been set to <EMPHASIS>(state-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
For the SET KEY operation, this informs the user that the
key was set.
<MSG_TEXT>(User Action)
If you do wish to see this information, use the /NOLOG
qualifier on the SET KEY command.

<MSG>(SETKEYERR\error in processing SET KEY command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The screen management
facility is used to maintain screen bindings.
In this instance, SMG$SET_DEFAULT_STATE has returned an error.
<MSG_TEXT>(User Action)
See SMG documentation to determine the problem.  If your
answer cannot be found, please contact VDE support for
assistance.

<MSG>(SETLIB\use SET LIBRARY, VDE$LIBRARY, or /LIBRARY )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE is unable to perform the specified operation as
the target VDE library -- the library on which the
operation will be performed -- has not been established.
<MSG_TEXT>(User Action)
Specify the target VDE library.  To determine the
available libraries, issue the "SET LIBRARY" command
with no parameters.  As part of the error message, this
command will display the names of the predefined VDE
libraries, the Rdb root directory for each, and the
mnemonic name for each.  Once the mnemnonic name or the
Rdb root directory name for the target library is known,
one can: A) use the mnemnonic name or the Rdb root directory
name as the libname parameter on a "SET LIBRARY libname"
VDE command.  B) Use use the mnemnonic name or the Rdb root
directory name as the parameter on the VDE /LIBRARY=libname.
C) Define the logical name VDE$LIBRARY to translate to
the VDE mnemnonic name or to the Rdb root directory name.

<MSG>(SETUNAUTH\attempt to set unauthorized privileges; privileges not set )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to use the SET PRIVILEGES command to
grant yourself one or more privileges that you are not
authorized to set according to the VDE database.
<MSG_TEXT>(User Action)
Use the SHOW PRIVILEGES/FULL command to see what privileges
you are authorized to set.  Then reenter the SET PRIVILEGES
command to set only authorized privileges.  Alternatively,
ask the project administrator to grant you authorization to
set the privileges you want.  Then exit from VDE, start a
new VDE session, and set the privileges you want.

<MSG>(SHOKEYERR\error in processing SHOW KEY command )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The screen management
facility is used to maintain screen bindings.
In this instance, SMG$LIST_KEY_DEFS has returned an error.
<MSG_TEXT>(User Action)
See SMG documentation to determine the problem.  If your
answer cannot be found, please contact VDE support for
assistance.

<MSG>(SHORESFUL\use SHOW RESERVATION/FULL to check reservation stream )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The SHOW RESERVATION/FULL command is used to display
outstanding reservations, and can be used to locate
the particular stream in which the reservation was
originally requested.  Certain operations require the
specification of a stream via an explicit /STREAM
qualifier, or via an implicit SET STREAM default
stream value.
<MSG_TEXT>(User Action)
This message is informational, and should accompany one or
more other error messages.

<MSG>(SNDJBCERR\job controller error status for queue <EMPHASIS>(queue) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have attempted to start a build job and the VMS job
controller (the $SNDJBCW system service) returned an error
status when VDE submitted a build process to a system batch
queue.  The message that follows gives more information to
explain the error.
<MSG_TEXT>(User Action)
The action to take to correct the error depends on the
nature of the error.  You or your system manager should
correct the error and restart the build job.

<MSG>(SPARE_1\placeholder for VDE$_MODEXISTS (<EMPHASIS>(module)) message )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE$_MODEXISTS message was reclassified from an
informational message to a warning message.  This
entry is a placeholder that prevents the condition
values of subsequent errors from changing.
<MSG_TEXT>(User Action)
See VDE$_MODEXISTS.  Also contact VDE support for assistance,
as VDE should no longer be reporting this error message.

<MSG>(SPARE_2\placeholder for VDE$_INVALANS (<EMPHASIS>(answer)) message )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE$_INVALANS message was reclassified from an
informational message to a warning message.  This
entry is a placeholder that prevents the condition
values of subsequent errors from changing.
<MSG_TEXT>(User Action)
See VDE$_INVALANS.  Also contact VDE support for assistance,
as VDE should no longer be reporting this error message.

<MSG>(SPARE_3\was FACNOTDEL; replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message (was FACNOTDEL) has been superceded.
<MSG_TEXT>(User Action)
Contact VDE support for assistance.

<MSG>(SPARE_4\was STRMNOTDEL )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
message superceded (was STRMNOTDEL)
<MSG_TEXT>(User Action)
Contact VDE support for assistance

<MSG>(SPARE_5\was FOLDNOTFOUND )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
filler for error message elevated to a warning.
<MSG_TEXT>(User Action)
This message should not appear.

<MSG>(SPARE_6\was BADSTATUS; replaced )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message (was BADSTATUS) has been superceded; the
BADSTATUS message now returns an error severity.
<MSG_TEXT>(User Action)
The version of message file in use does not match the
version of the images running.  Check for a bad or old
message file, and contact VDE support for assistance.

<MSG>(SPARE_8\was FOLDNOTFOUND )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
filler for error message elevated to a warning.
<MSG_TEXT>(User Action)
This message should not appear.

<MSG>(SPAWNED\subprocess spawned )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Issued when the /NOWAIT qualifier is used.
<MSG_TEXT>(User Action)
None; this is an informational message only.

<MSG>(SPEMERFAI\specification merge failure )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
internal state information for VDE$_INVDIRSPEC error.
<MSG_TEXT>(User Action)
Correct the cause of the VDE$_INVDIRSPEC error.

<MSG>(SRCNOTOUT\source module <EMPHASIS>(module) cannot be an output from build step )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified that a source module is an output from
a build step.  A source module can be an input to a build
step, but it can by definition not be an output.  The
build step definition is not added to the database.
<MSG_TEXT>(User Action)
If this error occurs on a CREATE STEP or MODIFY STEP
command, correct the error and reenter the command with
valid output modules.

<MSG>(STATNOTSPEC\the kind of statistics to display was not specified )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This qualifier requires a keyword specifying what kind of
statistics to display.
<MSG_TEXT>(User Action)
Reenter the command providing a keyword specifying what kind
of statistics to display.

<MSG>(STEPNOTCRE\build step not created; module <EMPHASIS>(module) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a module that does not exist in the
VDE database as the primary input to a compile step.  As a
result, the CREATE STEP command does not add the compile
step or its dependency information to the database.
<MSG_TEXT>(User Action)
Correct the module name to be the name of an existing
module or create the module with the CREATE MODULE command
before reentering the CREATE STEP command.

<MSG>(STEPNOTFOUND\build step for module <EMPHASIS>(module) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a build step that does not exist in the
VDE database.  As a result, the current MODIFY STEP command
cannot modify any information in the database.
<MSG_TEXT>(User Action)
Reenter the command specifying an existing build step or
create the desired build step with the CREATE STEP command.

<MSG>(STEPNOTMOD\build step not modified; module <EMPHASIS>(module) not found in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a module that does not exist in the
VDE database as the primary input or output module for a
build step.  As a result, the MODIFY STEP command cannot
modify database information.
<MSG_TEXT>(User Action)
Correct the module name to be the name of an existing
module before reentering the MODIFY STEP command, or
create the module with the CREATE MODULE command and
enter the step information with the CREATE STEP command.

<MSG>(STEPNOTREV\build step for module <EMPHASIS>(module) not found in review list )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a build step that does not exist in the
current build-step review list.  As a result, you cannot
select the build step with the module name you specified.
<MSG_TEXT>(User Action)
Reenter the SELECT command specifying a build step that
is present in the build-step review list for the current
REVIEW BUILD_JOB command.  Use the DIRECTORY subcommand
to determine what build steps are present in the list.

<MSG>(STGTRUNC\string truncated )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has attempted to output a string which is longer than
its internal buffer.
<MSG_TEXT>(User Action)
If it can be determined that it is not caused by a user
error, please contact VDE support for assistance.

<MSG>(STKOVF\command procedures too deeply nested; limit is 16 levels )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE allows only 16 levels of nesting of command
procedures.
<MSG_TEXT>(User Action)
Embed some of the command procedures within others to decrease
the level of nesting to fewer than 16.

<MSG>(STRMADDED\stream <EMPHASIS>(stream) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated stream
definition has been added to the VDE database.  This
message is only issued when you use the /LOG qualifier
on the CREATE STREAM command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(STRMCLOSED\stream <EMPHASIS>(stream) is permanently closed; state not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have tried to change the state of a stream development
stream with the /OPEN or /FROZEN qualifier on the MODIFY
STREAM command when the stream is already in the
permanently closed state.  The rest of the command still
takes effect, but the stream state is not changed; the
stream remains closed.
<MSG_TEXT>(User Action)
No user action is necessary; the state cannot be changed
and the command did not change it.

<MSG>(STRMDEL\stream <EMPHASIS>(stream) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the definition for the
indicated stream has been deleted from the VDE database.
This message is only issued when you use the /LOG qualifier
on the DELETE STREAM command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(STRMEXISTS\stream <EMPHASIS>(stream) already exists in database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated stream name was specified on a CREATE
STREAM command, but an entry for that stream is already
present in the database.  Hence a new entry was not created
for that stream.  Alternatively, the indicated name was
specified as the new name for an existing stream on the
MODIFY STREAM command, but another stream already has
the requested new name.  Hence the name of the existing
stream could not be changed to the new name.
<MSG_TEXT>(User Action)
If you entered the wrong stream name, reenter the command
with the correct name.  If you entered the right stream
name, use the SHOW STREAM command to display the database
information for that stream.  If you are not satisfied
with that information, use the MODIFY STREAM command to
change it.

<MSG>(STRMMOD\information for stream <EMPHASIS>(stream) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
stream has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
STREAM command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(STRMNOTCLOSED\stream <EMPHASIS>(stream) can not be deleted because it is not closed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to delete a stream which is in an open or
frozen state.  Only streams in a closed state may be deleted.
<MSG_TEXT>(User Action)
If appropriate, change the state of the stream to closed
and repeat the delete stream command.

<MSG>(STRMNOTDEL\stream <EMPHASIS>(stream) not deleted )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to delete a stream that
cannot be deleted.  Additional messages are normally
included with this message, and these messages
indicate why the strean cannot be deleted.
<MSG_TEXT>(User Action)
Resolve the problem(s) flagged by the other error
messages, and reenter the DELETE STREAM command.

<MSG>(STRMNOTFOUND\stream <EMPHASIS>(stream) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated stream name was entered on a SHOW STREAM
command, but no such stream was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated stream does not exist in the database.

<MSG>(STRMNOTOPEN\stream <EMPHASIS>(stream) is not open; operation not allowed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are trying to reserve or replace a module, but the
currently active stream (whose name is given in the
message) is either frozen or closed.  It is thus not open
for the reservation or replacement of modules.
<MSG_TEXT>(User Action)
You can use the SHOW STREAM/FULL command to see the status
of the current stream.  If the stream is closed, it is
permanently protected against being changed, and you should
not be trying to reserve or replace modules in it.  If the
stream is frozen, it is currently protected against being
changed, but changes may be allowed later when the library
administrator sets the state back to open.  You must then
wait until the stream becomes open.  (You may reserve
modules from a frozen stream, but not replace them.)
Finally, if you meant to reserve or replace modules in
another stream, you should use the SET STREAM command
to switch your context to that stream and then reserve
or replace the desired modules.

<MSG>(STRMNOTPOP\stream <EMPHASIS>(stream) is not allowed to be populated )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You are attempting to populate the indicated stream with
the POPULATE STREAM command but a stream attribute disallows
use of this command for the stream.   Hence the stream has
not been populated.
<MSG_TEXT>(User Action)
Either you should not be trying to populate the stream or
else you must set the stream attribute that allows you to
populate the stream before retrying the operation.  To set
that attribute, use the /POPULATE qualifier to the MODIFY
STREAM command.

<MSG>(STRMPOP\stream <EMPHASIS>(stream) populated from stream <EMPHASIS>(stream) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated stream has
been populated with all generations from the second
indicated stream.  This message is only issued when you
use the /LOG qualifier on the POPULATE STREAM command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(STRMPOPCOUNT\populate module counts: update <EMPHASIS>(count), insert <EMPHASIS>(count), remove <EMPHASIS>(count) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message tells you how many modules were updated in,
inserted into, and removed from the target stream by the
current POPULATE STREAM command.  This message is only
issued when you use the /LOG qualifier on the POPULATE
STREAM command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not
wish to see the message.

<MSG>(STRTOOLONG\quoted string too long; must be shortened )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The maximum length of the quoted string is determined
by the nature of the string.  For the DEFINE command,
the string is limited to 255 characters.  For remark
strings, it is limited to 132 characters.
<MSG_TEXT>(User Action)
Try to shorten the size of the string.

<MSG>(SUCGENEXIST\successor generation for <EMPHASIS>(module) already exists in library )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The new generation of the indicated module created by the
current REPLACE or PERFORM REPLACEMENT command should get
a whole-number CMS generation expression but the reserved
generation already has a successor generation in the VDE
library with that whole-number CMS generation expression.
This situation can arise if you have placed the reserved
generation into a stream using the INSERT GENERATION
command or if you have changed the stream that <QUOTE>(owns)
the whole-number successor generation with the /MAIN_STREAM
qualifier to the MODIFY GENERATION command.
<MSG_TEXT>(User Action)
If the existing whole-number successor generation should
not be in the VDE library, delete it and its successors
with the DELETE GENERATION command.  Then repeat the failed
replacement.  Otherwise, use the /MAIN_STREAM qualifier to
the MODIFY GENERATION command to allocate ownership of the
whole-number successor generation to the stream that already
owns that generation, but not to any stream into which you
are trying to replace the module.  This will force the
replacement to use a CMS variant letter.  Then repeat the
replacement.

<MSG>(SUCLNKADD\successor link from stream <EMPHASIS>(stream) to stream <EMPHASIS>(stream) added )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The successor stream relationship, from the first stream
specified to the second stream specified, has been added.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SUCLNKREM\successor link from stream <EMPHASIS>(stream) to stream <EMPHASIS>(stream) removed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The successor stream relationship, from the first stream
specified to the second stream specified, has been removed.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(SYNTAX\command syntax error at or near: '<EMPHASIS>(text)' )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
All commands  have a
specific syntax that must be followed. Failure to do so
will result in this error.
<MSG_TEXT>(User Action)
See <reference>(VDE_MANUAL_NAME) for assistance with
the command syntax.

<MSG>(TOOMANPARM\too many poundsign parameters in history or notes stringinvalid string is: <EMPHASIS>(string) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The history or notes string specified contains more than
one history or notes parameter.  This is not allowed.
<MSG_TEXT>(User Action)
Reenter the command with a valid history or notes string.

<MSG>(TRANTOODEEP\translation of logical name <EMPHASIS>(logical) more than 7 deep )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated logical name is either too deeply nested,
or is defined incorrectly to point back to itself causing
an infinite translation loop.
<MSG_TEXT>(User Action)
Reenter the command without using the logical name.

<MSG>(UIDSKEW\possible UID skew detected; check for correct UID file. )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an internal inconsistency with the UID file.
<MSG_TEXT>(User Action)
Please determine if the UID file associated with the VDE
distribution is the version in use.  If the UID file is
the one associated with the distribution, please contact
contact VDE support for assistance.  Please include any
information that may be useful or relevent in duplicating
the problem.  If there is a skew code associated with
this error, please include it in the error report.

<MSG>(UIDSKEWCODE\UID skew code <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This is the code for the particular internal inconsistency
detected within the UID file.
<MSG_TEXT>(User Action)
Please determine if the UID file associated with the VDE
distribution is the version in use.  If the UID file is
the one associated with the distribution, please contact
contact VDE support for assistance.

<MSG>(UNACLOFIL\unable to close file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to close the indicated text
file.  A more specific error message follows this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(UNACLOLOG\unable to close log file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The SYS$CLOSE system service was not performed successfully
in closing the log file.
<MSG_TEXT>(User Action)
Determine what could be preventing RMS from closing the file
successfully.  If the reason cannot be determined,
please contact VDE support for assistance.

<MSG>(UNACONLOG\unable to connect log file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The SYS$CONNECT system service was not performed successfully
in connecting the log file's RAB and FAB.
<MSG_TEXT>(User Action)
Determine what could be preventing RMS from connecting the
file's FAB and RAB successfully.  If this cannot be done,
please contact VDE support for assistance.

<MSG>(UNACONVDBFORM\unable to convert database format due to access conflict with another user )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The VDE database does not have the format required by the
current version of VDE and VDE has attempted to convert
the database to the required format.  This operation has
failed because of an access conflict with another user
attempting to convert the database at the same time.  That
other user has probably succeeded in converting the database
format, which is why you cannot do so.
<MSG_TEXT>(User Action)
Retry the CONVERT LIBRARY command and try accessing the
database again.  You should find that you are now able to
convert the database format or that the format has already
been converted.  Either way, you should be able to use VDE
with that database.

<MSG>(UNACREFIL\unable to create file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to create or open a new
text file.  A more specific error message follows this
message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(UNACRELOG\unable to create log file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The SYS$CREATE system service was not performed successfully
in creating the output file.
<MSG_TEXT>(User Action)
Determine what could be preventing RMS from creating the file
successfully.  If the reason cannot be determined,
please contact VDE support for assistance.

<MSG>(UNACREMBX\unable to create temporary mailbox )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to create a mailbox for
sending text between processes.  A more specific error
message follows this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(UNADELFIL\unable to delete file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to delete the indicated file.
A more specific error message follows this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(UNAOPEFIL\unable to open file <EMPHASIS>(file-name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to open an existing text
file for reading.  A more specific error message follows
this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(UNAOPEINP\unable to open input stream '<EMPHASIS>(text)' )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE could not read the command line correctly.
<MSG_TEXT>(User Action)
The logical name VDE$INPUT is probably not defined
correctly.  Correct the VDE$INPUT reference.

<MSG>(UNAPARFIL\unable to parse file name <EMPHASIS>(name) with default string <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An error occurred when trying to parse the indicated file
specification with the indicated default name string.  A
more specific error message follows this message.
<MSG_TEXT>(User Action)
Examine the error message that follows to diagnose the
reason for the error.  Then correct the problem accordingly.

<MSG>(UNAREPNOTECONF\unable to reply to note in notes conference <EMPHASIS>(conference) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE attempted to record a PERFORM REPLACEMENT operation
by replying to a previous note for the REPLACE command
in the indicated notes conference, but was unable to find
the notes conference or the note to reply to.  As a result,
the PERFORM REPLACEMENT operation was not recorded in the
notes conference.
<MSG_TEXT>(User Action)
Make sure that the notes conference has been established
and that the notes created by the REPLACE command are not
being deleted.

<MSG>(UNDKEY\<EMPHASIS>(state-name) key <EMPHASIS>(key-name) is undefined )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs the user that the key was undefined by
either the DELETE/KEY or UNDEFINE/KEY commands.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(UNKCOMSTA\unknown completion status value <EMPHASIS>(status) passed to VDESTATUS )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the image VDESTATUS, was
passed a status value it did not understand. VDESTATUS
is expecting the character string "SUCCESS" or the character
string "FAILURE" to be passed to it for its parameter. Any
other character string results in this error message being
output.
<MSG_TEXT>(User Action)
Check the invocation of the VDESTATUS image. Typically,
VDESTATUS is invoked from a command file that is built by
the program VDEDOBUILD for running buildsteps. Check the
command file associated with the buildstep that resulted
in this message.

<MSG>(UNKEPT\unable to <EMPHASIS>(opnam) to kept subprocess section )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has encountered an error while attempting to create
or connect to the global section used to communicate
with the kept subprocess.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one, check the documentation
for information on setting up process and system quotas,
and contact VDE support for assistance.

<MSG>(UNKEYW\unrecognized keyword '<EMPHASIS>(text)' - check validity and spelling )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The keyword provided in the command was unrecognized in this
context.
<MSG_TEXT>(User Action)
See <reference>(VDE_MANUAL_NAME) for assistance with
the command syntax.

<MSG>(UNKFILEXT\Unknown file extension in analysis file; the complete filespecification found was <EMPHASIS>(spec) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The program VDEDEPEND encountered a file specification
that has a file extension it does not support.  This error
occurred while VDEDEPEND was processing an analysis (.ANA)
file recording compiler or assembler dependency information.
<MSG_TEXT>(User Action)
Determine if the analysis file is corrupted.  If the
analysis file is not corrupted and the file extension
corresponds to a file type that should be recorded as
dependency information, please contact VDE support for assistance.

<MSG>(UNKPNAM\unable to locate project <EMPHASIS>(projnam) in stream <EMPHASIS>(streamnam) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has unable to locate the specified project name
associated with the specified stream.
<MSG_TEXT>(User Action)
Specify a valid and correctly-spelled project name
from the available list of projects assocated with
the stream.  If you believe that there should be one
or more additional projects associated with the stream,
please contact the project leader, the system manager(s),
or VDE support for assistance.

<MSG>(UNKPROJ\unable to locate a project name )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has encountered an error while using the notes callable
interface.
<MSG_TEXT>(User Action)
Attempt to resolve the problem based on any other error
messages included with this one, check the documentation
for information on setting up the notes conferences, and
contact VDE support for assistance.

<MSG>(UNKQARCLD\internal VDE coding error )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an internal inconsistency.
<MSG_TEXT>(User Action)
Please contact VDE support for assistance.  Please include
any information that may be useful or relevent in duplicating
the problem.

<MSG>(UNLOCKED\overriding library lockout )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is displayed when user with MODLIB
privilege replaces a module in a locked library.
<MSG_TEXT>(User Action)
Evaluate if the replacement is necessary in the
locked library; unlock the library if appropriate.

<MSG>(UNMATQUO\unmatched quote or missing quote at end of string )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
Any token that is to be delimited by quotes must have
quotes on both sides of the token. These quotes
may be either single or double; however, the delimiters
must be the same characters.
<MSG_TEXT>(User Action)
Reenter the command with the appropriate quotes balanced.

<MSG>(UNRESERVED\reservation for module <EMPHASIS>(module) cancelled )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated module has
been unreserved in the current library and is therefore
no longer reserved.  This message is only issued when you
use the /LOG qualifier on the UNRESERVE command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish
to see the message.

<MSG>(USEDELMOD\to unreserve a CREATE MODULE reservation, use DELETE MODULE )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An erroneous attempt was made to UNRESERVE a just-created module.
To cancel the module reservation and the module creation caused
by a CREATE MODULE command, use the DELETE MODULE command.  After
the DELETE MODULE command is accepted, the module will not be
created, the outstanding module reservation will be canceled,
and no further user action is required.
<MSG_TEXT>(User Action)
If you wish to cancel this reservation, use the DELETE MODULE
command.  This message is informational, and should accompany
one or more other error messages.

<MSG>(USERADDED\user <EMPHASIS>(user) added to the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated user has been
added to the VDE database.  This message is only issued when
you use the /LOG qualifier on the CREATE USER command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(USERDEL\user <EMPHASIS>(user) deleted from the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated user has been
deleted from the VDE database.  This message is only issued
when you use the /LOG qualifier on the DELETE USER command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(USEREXISTS\user <EMPHASIS>(user) already exists in database; user not changed )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated username was specified on a CREATE USER
command, but an entry for that user is already present
in the database.  Hence a new entry was not created for
that user.  Alternatively, the indicated username was
specified as the new username for an existing user on the
MODIFY USER command, but another user already has the
requested new username.  Hence the username of the existing
user could not be changed to the new username.
<MSG_TEXT>(User Action)
If you entered the wrong username, reenter the command
with the correct username.  If you entered the right
username, use the SHOW USER command to display the database
information for that user.  If you are not satisfied with
that information, use the MODIFY USER command to change it.

<MSG>(USERMOD\information for user <EMPHASIS>(user) modified in the database )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that information for the indicated
user has been modified in the VDE database.  This message
is only issued when you use the /LOG qualifier on the MODIFY
USER command.
<MSG_TEXT>(User Action)
Use the /NOLOG qualifier for the command if you do not wish to
see the message.

<MSG>(USERNOTDEL\user <EMPHASIS>(user) not deleted; you cannot delete yourself )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message informs you that the indicated user, namely
you yourself, has not been deleted from the database.
You are not allowed to delete yourself from the database.
This prohibition prevents you from accidentally deleting
yourself from the database, especially when using a
wildcarded username specification.  There is thus no way
to delete all users from the database.
<MSG_TEXT>(User Action)
If you want to delete yourself from the database, someone
else with the required privilege must do it for you.

<MSG>(USERNOTFOUND\user <EMPHASIS>(user) not found in database; parameter ignored )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated username was entered on a SHOW USER
command, but no such user was found in the VDE database.
<MSG_TEXT>(User Action)
This is not necessarily an error; the message simply tells
you that the indicated user does not exist in the database.

<MSG>(USERNOTUAF\user <EMPHASIS>(user) not found in system User Authorization File )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
The indicated username is your username, but it was
not found in the system User Authorization File.
<MSG_TEXT>(User Action)
This error should not happen except to VDE developers
who redefine the current user during testing.  Submit
a problem report.

<MSG>(USEVERSLNM\use logical name VDE$VMS_VERSION to override OpenVMS version )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE is unable to determine OpenVMS version information
from the version string returned from a SYS$GETSYI
service call.  This message recommends that you use
the VDE$VMS_VERSION logical name to override the system
value.
<MSG_TEXT>(User Action)
Define the logical name VDE$VMS_VERSION to a valid
OpenVMS version string value.

<MSG>(VALREQ\missing qualifier or keyword value - supply all required values '<EMPHASIS>(text)' )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
In many commands, specific keywords or qualifiers are
expected.
<MSG_TEXT>(User Action)
See <reference>(VDE_MANUAL_NAME) for assistance with
the command syntax.

<MSG>(VDECLUSTER\vde.cluster: <EMPHASIS>(cluster) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDECONTACT\vde.contact: please contact VDE support for assistance )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDEDATETIME\vde.datetime: <EMPHASIS>(datetime) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDEFORMAT\vde.format: the format of this file is subject to change )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDENAME\vde.product: <EMPHASIS>(vdename) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDENODE\vde.node: <EMPHASIS>(node) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDEPROJECT\vde.project: <EMPHASIS>(project) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDERDBBKP\VDE$DATABASE$<EMPHASIS>(db)_BCKP_<EMPHASIS>(type) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDERDBBKP_FULL\FULL )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDERDBBKP_INCR\INCR )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VDEVERSION\vde.version: <EMPHASIS>(version) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to format text strings within VDE,
and should not be visible to users as an error message.
<MSG_TEXT>(User Action)
Contact VDE support for assistance, as the version of
VDE in use should not be displaying this as an error
message.

<MSG>(VERBOTEN\direct ATTACH to a VDE kept subprocess is forbidden )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
An attempt has been made to directly ATTACH to a VDE kept
subprocess via a DCL command, and this is not permitted.
<MSG_TEXT>(User Action)
Use of the DCL ATTACH command to attach to a VDE kept
subprocess is not permitted.  If this message arises from
a condition other than an attempt by a user to ATTACH to
a VDE kept subprocess, please contact VDE support for
assistance.   Please include any information that may be
useful or relevent in duplicating the problem.

<MSG>(WHEREIS\component <EMPHASIS>(comp) is <EMPHASIS>(value) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is used to display information about parts
of the local VDE environment and VDE configuration.
<MSG_TEXT>(User Action)
No action is required.

<MSG>(WHYOFF\reason: !AD )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
This message is usually paired with VDE$_OFFLINE.
The VDE environment has been taken offline, and this
message indicates why.
<MSG_TEXT>(User Action)
If the problem persists, please contact VDE support
for assistance.

<MSG>(WILDGENNUM\wildcarded generation number not allowed in <EMPHASIS>(module) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a wildcarded generation number on
a module name for a command which does not allow the
generation number to be wildcarded.
<MSG_TEXT>(User Action)
Decide what generation of the module you want to apply
the command to.  Then reissue the command, specifying
that generation number.  Alternatively, you may omit
the generation number, in which case the command is
applied to the last (most recent) generation of the
module.

<MSG>(WILDNOTALL\wildcard characters not allowed in name: <EMPHASIS>(name) )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
You have specified a wildcard character (asterisk or
percent sign) in a name that is not allowed to have
wildcard characters.  The message displays the name
up to and including the wildcard character.
<MSG_TEXT>(User Action)
Specify the name without a wildcard character and
resubmit the command.

<MSG>(XMERROR\Motif interface error detected )
<MSG_TEXT>(Facility)
VDE, OpenVMS Development Environment
<MSG_TEXT>(Explanation)
VDE has detected an error in the Motif interface.
<MSG_TEXT>(User Action)
A problem has occurred accessing the X Windows display,
during the fetch of a widget from a UID file, or another
similar error.  Additional error messages should have
been displayed prior to this particular error and the
other messages should detail the particular failure
detected.  If unable to determine the case of the
error, please contact VDE support for assistance.
Please include any information that may be useful
or relevent in duplicating the problem.

<ENDMESSAGE_SECTION>