! Module VDEMSG.GNM Version V04-001 ! ! ! COPYRIGHT (C) 1988 BY ! DIGITAL EQUIPMENT CORPORATION, MAYNARD ! MASSACHUSETTS. ALL RIGHTS RESERVED. ! ! THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ! ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION ! OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER COPIES ! THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER ! PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED. ! ! THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE AND ! SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT CORPORATION. ! ! DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS ! SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY DIGITAL. ! ! ! WRITTEN BY ! Bert Beander 8-Feb-1988 (Adapted from PCA) ! ! MODULE FUNCTION ! The .GNM file is the central file for error messages. Both the .MSG ! to be compiled into the software and the .GNC to be included in the ! document are derived from this file. ! ! ! < < < < < < < + > > > > > > > > ! < < < W A R N I N G > > > > ! < < < < < < < + > > > > > > > > ! ! DO *NOT* REORDER ANY MESSAGES PRESENT IN THIS FILE. ADD MESSAGES ! ONLY AT THE ENDS OF THE SECTIONS, AND SUBSTITUTE DUMMY MESSAGES ! FOR ANY MESSAGE ENTRIES THAT ARE REMOVED. (Use the name SPARE_n ! for the dummy message, where 'n' is a unique value.) ! ! ! The file can be thought of as a series of directives: ! ! .NAME - The message symbol without the VDE$_ ! .MESSAGE - The message text, it may be wrapped ! .EXPLANATION - The description that appears in the document ! .USER_ACTION - The recovery section that appears in the document. ! .BREAK - May be used to start a new paragraph in the ! .explanation or .user_action ! .DESTINATION - Which file the following appears in, parameters are ! both, message ! .SEVERITY - informational, success, warning, error, or fatal ! ! The first 4 directives: .name, .message, .explanation, .user_action, ! occur as a group in that order for each message. .explanation and ! .user_action are optional. The FAO arguments within the .message ! are contained within <>. Within the <> there are 2 arguments, the ! first is a word which will be emphasized in that position in the ! document, the second is the FAO argument which will appear in the ! message file in that position. ! ! The .destination directive must appear between message groups and is ! in effect until another .destination directive occurs. Thus, when ! one message is to goto the message file only a .destination message ! will precede the message group and a .destination both will follow ! the group. ! ! Developers are encouraged to include explanations and user actions. ! The writer will clean things up before a release. ! ! Use spaces for the indentation of the message text and explanations. ! The utilities that process the .GNC file don't like tabs. ! ! Other rules apply to the file but these are the ones necessary for ! normal updating of the message ! ! REVISION HISTORY ! Steve Hoffman 22-Mar-1994 ! Added the `no reorder' warning (avoids various problems in ! mixed-version/mixed-architecture VMScluster environments) ! and also added the quota-related messages. ! .facility VDE,879 /SYSTEM /PREFIX=VDE$_ ! ! Success messages go here. DO NOT REORDER. ! .severity success .destination message .name AERRORS .message accepted.checkin.defectsfixed: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AGROUP .message accepted.checkin.group: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AITEM .message accepted.checkin.item: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ANOTE .message accepted.checkin.note: . .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AMODULE .message accepted.checkin.module: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AREASON .message accepted.checkin.reasonmask: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AREPLID .message accepted.checkin.replacementid: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AREPLNAME .message accepted.checkin.replname: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ASTREAM .message accepted.checkin.stream: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ATYPCOD .message accepted.checkin.typecode: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ATYPNAM .message accepted.checkin.typename: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name AUSERNAME .message accepted.checkin.username: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. ! ========== ========== ========== .name QERRORS .message queued.checkin.defectsfixed: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QGROUP .message queued.checkin.group: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QITEM .message queued.checkin.item: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QNOTE .message queued.checkin.note: . .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QMODULE .message queued.checkin.module: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QREASON .message queued.checkin.reasonmask: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QREPLID .message queued.checkin.replacementid: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QREPLNAME .message queued.checkin.replname: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QSTREAM .message queued.checkin.stream: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QTYPCOD .message queued.checkin.typecode: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QTYPNAM .message queued.checkin.typename: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QUSERNAME .message queued.checkin.username: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. ! ========== ========== ========== .name QRMPBMODFLAG .message queued.module.modflags: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QRMPBMODNAME .message queued.module.modname: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QRMPBREPLREMARK .message queued.module.replaceremark: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QRMPBRESREMARK .message queued.module.reserveremark: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QRMPBSTAGING .message queued.module.staging: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBCMSDIR .message accepted.module.cmslibrary: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBGENNEW .message accepted.module.newgeneration: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBGENOLD .message accepted.module.oldgeneration: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBMODFLAG .message accepted.module.modflags: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBMODNAME .message accepted.module.modname: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBREPLREMARK .message accepted.module.replaceremark: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBRESREMARK .message accepted.module.reserveremark: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBSTAGING .message accepted.module.staging: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. ! ========== ========== ========== .name VDEDATETIME .message vde.datetime: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDENAME .message vde.product: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDEVERSION .message vde.version: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDEFORMAT .message vde.format: the format of this file is subject to change .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDECONTACT .message vde.contact: please contact VDE support for assistance .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QLIBMNE .message queued.library.mnemonic: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QRMPBCOUNT .message queued.module.count: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ARMPBCOUNT .message accepted.module.count: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QCHECKCOUNT .message queued.checkin.count: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDENODE .message vde.node: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name ADATETIME .message accepted.checkin.datetime: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDECLUSTER .message vde.cluster: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDEPROJECT .message vde.project: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QPROJECT .message queued.project.name: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name QDATETIME .message queued.checkin.datetime: .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDERDBBKP .message VDE$DATABASE$_BCKP_ .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDERDBBKP_FULL .message FULL .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name VDERDBBKP_INCR .message INCR .explanation This message is used to format text strings within VDE, and should not be visible to users as an error message. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name NOMOREITEMS .message no more items to be returned .explanation During a normal operation, there are no additional items to returned. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. ! ! ! Informational messages go here. DO NOT REORDER. ! .base 500 .severity informational .destination both .name ARCHADDED .message architecture added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name ARCHDEL .message architecture deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name ARCHEXISTS .message architecture already exists in database; not changed .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. .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. .name ARCHMOD .message information for architecture modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name DEFARCH .message architecture not deleted; you cannot delete default architecture .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.) .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. .name ARCHNOTFOUND .message architecture not found in database; parameter ignored .explanation The indicated architecture name was entered on a SHOW ARCHITECTURE command, but no such architecture was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated architecture does not exist in the database. .name ATTACHED .message terminal now attached to process .explanation The SPAWN command issues this message before attaching to the new process. .name BADQUESTAT .message bad status for batch queue .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. .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. .name BLDALRSTART .message build job for stream already started;<,!/> build job cannot be started again .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. .user_action This is an informational message. No user action is required. .name BLDALRSTOP .message build job for stream has already stopped;<,!/> build job cannot be stopped again .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. .user_action This is an informational message. No user action is required. .name BLDINIFAIL .message build initialization completed with errors .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. .user_action Correct the errors and resubmit the compilation or build job. .name BLDJOBAFTER .message build job to be started after .explanation The build job you are starting will actually start executing after the indicated date and time. .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. .name BLDJOBCRE .message build job for stream has been created .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name BLDJOBDEL .message build job for stream deleted from database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name BLDJOBENT .message entry number submitted to queue .explanation A process has successfully been submitted to the indicated batch queue. It received the queue entry number shown in the message. .user_action This is an informational message. No user action is required. .name BLDJOBERR .message error queuing build job on queue ; process not queued .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. .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. .name BLDJOBMOD .message build job for stream modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name BLDJOBSIZ .message build job for stream consists of steps .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name BLDJOBSTARTED .message build job for stream started with processes .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. .user_action This is an informational message. No user action is required. .name BLDJOBSTARTING .message starting build job for stream .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. .user_action This is an informational message. No user action is required. .name BLDJOBSTOP .message build job for stream stopped .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name BLDJOBSUSP .message build job for stream suspended .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name BLDNOTRUN .message build job for stream is not queued or running;<,!/> build job cannot be suspended .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. .user_action This is an informational message. No user action is required. .name BLDSTEPNEED .message build step needed to make inputs up-to-date:<,!/> .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. .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. .name BLDSTEPNOTSHO .message additional needed build steps not shown .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. .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. .name CMSBADGEN .message bad CMS generation found for module <,!/> possible CMS error .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. .user_action Examine the CMS library and consult a CMS expert. .name CMSCLASSEXIST .message CMS class already exists for CMS facility .explanation The indicated CMS class was found to already exist in the indicated CMS facility, so we do not attempt to create it. .user_action None. .name CMSDUPGEN .message duplicate CMS generation found for module <,!/> possible CMS error .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. .user_action Examine the CMS library and consult a CMS expert. .name CMSLIBEMPTY .message the CMS library contains no elements .explanation Since the CMS library specified with the /CMS_LIBRARY qualifier is empty, no modules are created. .user_action None. .name CMSNOCLASS .message CMS class does not exist for facility <,!/> Unable to modify CMS class name .explanation The indicated CMS class does not exist in the indicated facility, so we are not able to modify its name. .user_action None. .name CMSSTART .message starting retrieval of CMS information for facility .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. .user_action None. .name COMNOTDEF .message command "" not defined .explanation DELETE/COMMAND issues this message when the command you request to delete was not defined. .user_action Use SHOW SYMBOL/DEFINED to display all defined commands. .name COMMIT .message database transaction has successfully committed .explanation The database transaction associated with the current command has successfully committed, thus ensuring that all changes have been written to the VDE database. .user_action Feel relieved. .name COMPFAIL .message compilation of completed with errors .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. .user_action Correct the errors and resubmit the compilation or build job. .name COMPSUCC .message compilation of completed successfully .explanation The compilation of the indicated module completed successfully. .user_action None. .name COMSTEPADDED .message compile step for added to database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name COMSTEPDEL .message compile step for module deleted from database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name COMSTEPMOD .message compile step for module modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name CONCURRES .message concurrent reservation of by user already present .explanation You are reserving a module which is already reserved by another user (possibly yourself). That reservation allows concurrent reservations. .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. .name CONRESDEL .message concurrent reservation of for user has been deleted .explanation This message informs you that the indicated concurrent reservation has been deleted from the VDE database because you replaced the same module. .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. .name COPSTEPADDED .message copy step for added to database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name COPSTEPDEL .message copy step for module deleted from database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name COPSTEPMOD .message copy step for module modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name COPYFAIL .message copy of completed with errors .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. .user_action Correct the errors and resubmit the copy step or build job. .name COPYSUCC .message copy of completed successfully .explanation The copy step for the indicated module completed successfully. .user_action None. .name CTXADDED .message context added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name CTXDEL .message context deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name CTXEXISTS .message context already exists in database; context not changed .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. .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. .name CTXMOD .message information for context modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name CTXNOTFOUND .message context not found in database; parameter ignored .explanation The indicated context name was entered on a SHOW CONTEXT command, but no such context was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated context does not exist in the database. .name DCLTRUNC .message DCL command line from script truncated; line too long .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. .user_action Correct the script to generate a shorter DCL command line. .name DEFKEY .message key has been defined .explanation Issued by DEFINE/KEY to inform the user that the specific key definition has been bound. .user_action If you did not wish to see this message, issue /NOLOG with your DEFINE command. .name DELKEY .message key has been deleted .explanation Issued by DELETE/KEY to inform the user that the specific key definition has been deleted. .user_action If you do not wish to see this message, issue /NOLOG with your DELETE command. .name DEPNOTUPDATE .message dependency information not updated for build step .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. .user_action None. .name DEPUPDATE .message dependency information updated for build step .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. .user_action None. .name DIRADDED .message directory specification added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name DIRCREATED .message directory has been created .explanation This message informs you that the indicated directory has just been created as your VDE scratch directory. .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. .name DIRDEL .message directory specification deleted from database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name DIRFILNOTDEL .message unable to delete directory file .explanation This message informs you that the indicated directory file was not deleted for some reason, such as insufficient privileges. .user_action Use DCL commands to check the security on the directory file, and take the appropriate action to delete it if possible. .name DIRNOTFOUND .message directory specification to cancel not found in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name DIRSPECREQ .message directory specification required for stream .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. .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. .name DIRTRENOTDEL .message not all files deleted in directory tree .explanation This message informs you that not all files in the indicated directory tree were deleted for some reason, such as insufficient privileges. .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. .name EDITUPDATE .message default editor definition updated in the VDE database .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. .user_action None. This is an informational message only. .name ELENOTFOUNDCMS .message element not found in CMS library .explanation This message informs you that the indicated module generation does not have an element in the CMS library. .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. .name ERRASSIGN .message the attempt to acquire an I/O channel for VDE failed .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. .user_action Check your process's quotas. If this problem cannot be resolved locally, please contact VDE support for assistance. .name ERRCRELNM .message unable to create a logical name .explanation VDE creates logical names for input and output redirection. .user_action Check your process's quotas. If this problem cannot be resolved locally, please contact VDE support for assistance. .name ERRDEASSIGN .message attempt to deassign an I/O channel acquired by VDE failed .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. .user_action Please contact VDE support for assistance. .name ERRFAO .message unable to format output string .explanation An error was returned from a call to SYS$FAO. .user_action Please contact VDE support for assistance. .name ERRQIOW .message error from SYS$QIOW .explanation A bad status was returned from a call to SYS$QIOW. .user_action Please contact VDE support for assistance. .name ERRSMG .message error returned from a call to the Screen Management Facility (SMG) .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. .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. .name EXPGENDIFF .message expected generation expression differs from actual .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. .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. .name EXPGENEXPR .message expected generation expression at replacement is .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 (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. .user_action None. This message is informational only. .name FACADDED .message facility added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FACDEL .message facility deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FACMOD .message information for facility modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .destination message .name SPARE_3 .message was FACNOTDEL; replaced .explanation This message (was FACNOTDEL) has been superceded. .user_action Contact VDE support for assistance. .destination both .name FACNOTFOUND .message facility not found in database; parameter ignored .explanation The indicated facility name was entered on a SHOW FACILITY command, but no such facility was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated facility does not exist in the database. .name FETCHED .message generation fetched from library .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FILCOPLIB .message file copied to library .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FILCOPSTAG .message file copied to staging area .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FILQUE .message print file queued to .explanation This this message informs the user where the file was queued for printing. .user_action Ensure that the file is placed on the appropriate queue. .name FOLDADDED .message fold record for module added to database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FOLDDEL .message fold record for module has been deleted .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FOLDEXP .message fold record for expected for stream .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. .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. .name FOLDINSTRM .message generation must be folded into stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name FOLDMOD .message fold record for module modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .destination message .name SPARE_5 .message was FOLDNOTFOUND .explanation filler for error message elevated to a warning. .user_action This message should not appear. .destination both .name FROMDIREMPTY .message the directory specified with /FROM_DIRECTORY is empty .explanation Since the directory specified with the /FROM_DIRECTORY qualifier is empty, no modules are created. .user_action None. .name GENDEL .message generation deleted from stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GENDELLIB .message generation deleted from library .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GENINSERT .message generation inserted into stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GENMOD .message information for generation modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GENNOTCLASSMEM .message generation is not a member of CMS class .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. .user_action Use the VERIFY GENERATION/RECOVER to attempt recovery of the class memebership for this stream. .name GENNOTFOUNDCMS .message generation not found in CMS library .explanation This message informs you that the indicated module generation does not have a generation in the CMS library. .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. .name GENNOTINSTAGE .message generation not found in staging area .explanation This message informs you that the module generation is not in the library staging area .user_action Try to locate a previous module generation by checking with users that last had the module reserved. .name GENNOTQUEREPL .message replacement was not queued; no staging area exists .explanation This message informs you that the module generation has not been queued for replacement and therefore a generation cannot be located for recovery. .user_action Try to locate a previous module generation by checking with users that last had the module reserved. .name GENNOTRECOVERED .message generation not recovered .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. .user_action Review the cause of the recovery failure. Try to locate a previous module generation. .name GENRECCLASSMEM .message generation successfully recovered into CMS class .explanation This message informs you that the module generation has been successfully recovered into the indicated CMS class. .user_action None required. .name GENRECOVERED .message generation successfully recovered from .explanation This message informs you that the module generation has been successfully recovered. .user_action None required. .name GENREM .message generation removed from stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GENREPLDNF .message staging directory not found .explanation This message informs you that reported staging directory does not exist. Perhaps the directory was deleted as part of a cleanup operation. .user_action Try to locate a previous module generation by checking with users that last had the module reserved. .name GENRETAINED .message generation retained in library .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GENSUCVERIFY .message generation successfully verified .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. .user_action None required. .name GRPADD .message module is added to group .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GRPADDED .message group added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GRPALRMEM .message module is already a member of group .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GRPDEL .message group deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GRPEXISTS .message group already exists in database; group not changed .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. .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. .name GRPMOD .message information for group modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GRPNOTFOUND .message group not found in database; parameter ignored .explanation The indicated group name was entered on a SHOW GROUP command, but no such group was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated group does not exist in the database. .name GRPNOTMEM .message module is not a member of group .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name GRPREM .message module is removed from group .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name INMODNOTFOU .message input module of build step not found in database; ignored .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. .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. .name INPNOTNAME .message input string is not syntactically valid .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. .user_action Reenter a correctly specified name in response to the query. .name INPTOOLONG .message input string too long; maximum length is characters .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. .user_action Reenter a shorter input string in response to the query. .name INPTOOSHORT .message input string too short; minimum length is characters .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. .user_action Reenter a longer input string in response to the query. .destination message .name SPARE_2 .message placeholder for VDE$_INVALANS () message .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. .user_action See VDE$_INVALANS. Also contact VDE support for assistance, as VDE should no longer be reporting this error message. .destination both .name INVNUMRNG .message number not valid; number is , valid range is to .explanation A numeric input value is not within its valid range. The valid range is indicated in the message. .user_action Reenter the number with a value within the valid range. .name INVNUMSTG .message invalid numeric string: .explanation A numeric input value is not syntactically valid. .user_action Reenter the number with correct syntax. .name INVRANGE .message no values in inverted range to .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. .user_action Reenter the command specifying a valid range of replacement id numbers in ascending order. .name JOURDISA .message database journalling disabled for VDE library .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. .user_action None. .name JOURENA .message database journalling enabled for VDE library .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. .user_action None. .name LIBCONV .message library format converted for new version of VDE .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. .user_action None. This is an informational message only. .name LIBMOD .message library attributes modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name LINKFAIL .message link of completed with errors .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. .user_action Correct the errors and resubmit the link or build job. .name LINKSUCC .message link of completed successfully .explanation The link of the indicated module completed successfully. .user_action None. .name LNKSTEPADDED .message link step for added to database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name LNKSTEPDEL .message link step for module deleted from database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name LNKSTEPMOD .message link step for module modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MAILSENT .message mail message sent to user .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MERGEGEN .message merging generation () into .explanation This message informs you that the current FETCH or RESERVE command will merge the indicated (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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODADDED .message module added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODALRINSTEP .message module is already an input to build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODALROUTSTEP .message module is already an output from build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODDEL .message module deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .destination message .name SPARE_1 .message placeholder for VDE$_MODEXISTS () message .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. .user_action See VDE$_MODEXISTS. Also contact VDE support for assistance, as VDE should no longer be reporting this error message. .destination both .name MODINSTEP .message module is an input to the build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODMODIF .message information for module modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODNOTFOUND .message module not found in database; parameter ignored .explanation The indicated module name was entered on a SHOW MODULE command, but no such module was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated module does not exist in the database. .name MODNOTINSTEP .message module is not now an input to build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODNOTOUTSTEP .message module is not now an output from build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODOUTSTEP .message module is an output from the build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODREMINSTEP .message module removed as an input to build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MODREMOUTSTEP .message module removed as an output from build step .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name MUSTREPL .message you must replace the new module to create its first generation .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name NOBLDJOB .message no build jobs found for stream .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. .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. .name NOKEYPAD .message unable to set up keypad definitions .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. .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. .name NOMATCHARCH .message no architecture name matches the wildcarded string .explanation You entered a wildcarded architecture name specification on a command, but that specification did not match any architecture names in the VDE database. .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. .name NOMATCHCTX .message no context name matches the wildcarded string .explanation You entered a wildcarded context name specification on a command, but that specification did not match any context names in the VDE database. .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. .name NOMATCHFAC .message no facility name matches the wildcarded string .explanation You entered a wildcarded facility name specification on a command, but that specification did not match any facility names in the VDE database. .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. .name NOMATCHGEN .message no generation matches wildcarded string .explanation You entered a wildcarded generation specification on a command, but that specification did not match any module generations in the VDE database. .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. .name NOMATCHGENS .message no generation matches wildcarded string in stream .explanation You entered a wildcarded generation specification on a command, but that specification did not match any module generations in the specified stream. .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. .name NOMATCHGRP .message no group name matches the wildcarded string .explanation You entered a wildcarded group name specification on a command, but that specification did not match any group names in the VDE database. .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. .name NOMATCHMOD .message no module name matches the wildcarded string .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. .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. .name NOMATCHREP .message no replacement name matches the wildcarded string .explanation You entered a wildcarded replacement name specification on a command, but that specification did not match any replacement names in the VDE database. .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. .name NOMATCHSCRP .message no scripts match the specification .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. .user_action This is not necessarily an error; the message simply tells you that no scripts exist in the database that match your specification. .name NOMATCHSES .message no session name matches the wildcarded string .explanation You entered a wildcarded session name specification on a command, but that specification did not match any session names in the VDE database. .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. .name NOMATCHSTEP .message no build steps for modules matching found in database .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. .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. .name NOMATCHUSER .message no user name matches the wildcarded string .explanation You entered a wildcarded username specification on a command, but that specification did not match any usernames in the VDE database. .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. .name NOMATCHSTRM .message no stream name matches the wildcarded string .explanation You entered a wildcarded stream name specification on a command, but that specification did not match any stream names in the VDE database. .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. .name NOMODMEMGRP .message no modules are members of group .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. .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. .name NORESFORMOD .message no reservations exist for module .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. .user_action This is not necessarily an error; the message simply tells you that the indicated module or modules are not reserved. .name NOSUCHQUE .message batch queue does not exist; check spelling .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. .user_action Specify a valid queue name and restart the build job. .name NOSUCHSTEP .message no build step for module found in database .explanation No compile or link build step is recorded in the database for the indicated module. .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. .name NOSUCHSYM .message no such symbol '' exists .explanation No symbols matching the given symbol specification have been found. .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. .name NOTESENT .message note posted in conference .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name NOTPROP .message generation not propagated past stream .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. .user_action None. This is an informational message that merely confirms that VDE performed change propagation as requested. .name OUTFILE .message output file is .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. .user_action None. This is an informational message. .name OUTMODSRC .message output module of build step is a source module; ignored .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. .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. .name QUECLOSED .message batch queue is closed and cannot accept jobs .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. .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. .name QUEPAUSED .message batch queue is paused or pausing; job execution is halted .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. .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. .name QUESTOPPED .message batch queue is stopped or stopping; job execution is halted .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. .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. .name REPACCEPT .message replacement marked as accepted in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPADDED .message replacement added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPCAN .message replacement cancelled .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPDEL .message replacement deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPEXISTS .message replacement already exists; replacement not changed .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. .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. .name REPLACED .message generation replaced into stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPLQUE .message module queued for replacement .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPMOD .message information for replacement modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPNOTFOUND .message replacement not found in database; parameter ignored .explanation The indicated repalcement name was entered on a SHOW REPLACEMENT command, but no such replacement was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated replacement does not exist in the database. .name REPNOTPERF .message replacement for stream not performed; does not match stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPPERF .message replacement performed .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name REPREJECT .message replacement marked as rejected in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name RESDEL .message reservation of for user has been deleted .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. .user_action None. The affected users will be informed that their reservations are deleted. They should reserve the module again and redo their changes. .name RESERVED .message generation reserved from stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name RESERVSES .message generation reserved from stream for session .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name RESMOD .message reservation for module modified in database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name RESQUEUED .message reservation request for queued for stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name RETURNED .message control returned to process .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. .name ROLLBACK .message database transaction has been rolled back .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. .user_action Correct the error and retry the command. .name SCRPADDED .message script from file added to the database<,!/> script .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SCRPDEL .message script deleted from the database<,!/> script .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SCRPEXTR .message script extracted to file <,!/> script .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SCRPFILE .message script produced DCL command file <,!/> script .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SCRPMOD .message script information modified in the database<,!/> script .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SCRPUSED .message script was used .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SESADDED .message session added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SESCAN .message session cancelled .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SESEXISTS .message session already exists in database; session not changed .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. .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. .name SESMOD .message information for session modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SESNOMODS .message session contains no module reservations .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. .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. .name SESNOTFOUND .message session not found in database; parameter ignored .explanation The indicated session name was entered on a SHOW SESSION command, but no such session was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated session does not exist in the database. .name SESTERM .message session terminated .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SETKEY .message keypad state has been set to .explanation For the SET KEY operation, this informs the user that the key was set. .user_action If you do wish to see this information, use the /NOLOG qualifier on the SET KEY command. .name SPAWNED .message subprocess spawned .explanation Issued when the /NOWAIT qualifier is used. .user_action None; this is an informational message only. .name STGTRUNC .message string truncated .explanation VDE has attempted to output a string which is longer than its internal buffer. .user_action If it can be determined that it is not caused by a user error, please contact VDE support for assistance. .name STRMADDED .message stream added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name STRMCLOSED .message stream is permanently closed; state not changed .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. .user_action No user action is necessary; the state cannot be changed and the command did not change it. .name STRMDEL .message stream deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name STRMMOD .message information for stream modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name STRMNOTDEL .message stream not deleted .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. .user_action Resolve the problem(s) flagged by the other error messages, and reenter the DELETE STREAM command. .name STRMNOTFOUND .message stream not found in database; parameter ignored .explanation The indicated stream name was entered on a SHOW STREAM command, but no such stream was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated stream does not exist in the database. .name STRMPOP .message stream populated from stream .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name STRMPOPCOUNT .message populate module counts: update , insert , remove .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SUCLNKADD .message successor link from stream to stream added .explanation The successor stream relationship, from the first stream specified to the second stream specified, has been added. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name SUCLNKREM .message successor link from stream to stream removed .explanation The successor stream relationship, from the first stream specified to the second stream specified, has been removed. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name UNAREPNOTECONF .message unable to reply to note in notes conference .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. .user_action Make sure that the notes conference has been established and that the notes created by the REPLACE command are not being deleted. .name UNDKEY .message key is undefined .explanation This message informs the user that the key was undefined by either the DELETE/KEY or UNDEFINE/KEY commands. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name UNKCOMSTA .message unknown completion status value passed to VDESTATUS .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. .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. .name UNRESERVED .message reservation for module cancelled .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name USERADDED .message user added to the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name USERDEL .message user deleted from the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name USEREXISTS .message user already exists in database; user not changed .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. .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. .name USERMOD .message information for user modified in the database .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name USERNOTDEL .message user not deleted; you cannot delete yourself .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. .user_action If you want to delete yourself from the database, someone else with the required privilege must do it for you. .name USERNOTFOUND .message user not found in database; parameter ignored .explanation The indicated username was entered on a SHOW USER command, but no such user was found in the VDE database. .user_action This is not necessarily an error; the message simply tells you that the indicated user does not exist in the database. .name DBGLNMBAT .message debug logical name VDE$BATCH_MODE: .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name DBGLNMDAT .message debug logical name VDE$DATE_TIME: .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name DBGLNMUSR .message debug logical name VDE$USERNAME: .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name DEVOSYNCH .message executing synch command: .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name UNLOCKED .message overriding library lockout .explanation This message is displayed when user with MODLIB privilege replaces a module in a locked library. .user_action Evaluate if the replacement is necessary in the locked library; unlock the library if appropriate. .name HELLO .message Motif starting up .explanation This message displays the version identification of the VDE Motif interface in use. This message is displayed automatically during the VDE Motif startup. .user_action None. .name DBGNOLNM .message unable to translate .explanation VDE was unable to translate a mandatory logical name. .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. .name NEWDBGMSK .message debug mask switching from to .explanation This message indicates that the value loaded in the VDE debugging bitmask is being changed. This message should appear only during VDE testing. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name DBGWAYPT .message debug waypoint reached .explanation This message displays a waypoint, and the associated waypoint value, encountered during program execution. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name CULPRIT .message reserved by user .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. .user_action This message is informational, and should accompany one or more other error messages. .name SHORESFUL .message use SHOW RESERVATION/FULL to check reservation stream .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. .user_action This message is informational, and should accompany one or more other error messages. .name LIBRESET .message library reset .explanation You have reset the VDE library. .user_action No action is required. .name USEDELMOD .message to unreserve a CREATE MODULE reservation, use DELETE MODULE .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. .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. .name SCRDONE .message completed wait for script .explanation This message informs you that VDE has completed a wait for a script. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name SCRLOAD .message loading script into subprocess .explanation This message informs you that VDE has loaded a script into a subprocess for execution. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name SCRWAIT .message commencing wait for script .explanation This message informs you that VDE is commencing a wait operation for a script. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name SCRIPTONLY .message VDE/STATUS is invoked only within scripts .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. .user_action Don't do this. .name DBGQUALMSK .message qualifier mask .explanation This message displays the contents of an internal bitmask during program execution. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name NOTEID .message topic . entered in conference .explanation This message indicates that VDE has entered a note into a notes conference on behalf of the user. .user_action No action is required. .name NYI .message feature not yet implemented .explanation VDE has detected a request for a feature that has not yet been implemented. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name OUTNLA0 .message if /OUTPUT=NLA0: was used, respecify with non-null output .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. .user_action If fetching or reserving a module that uses a marker file, respecify the command with a non-null output device and directory. .name COMMAND .message command .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. .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. .name GBLSECNAM .message communications global section name: .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. .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. .name FLAVORPIDS .message flavor , pid , master , parent .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name VERBOTEN .message direct ATTACH to a VDE kept subprocess is forbidden .explanation An attempt has been made to directly ATTACH to a VDE kept subprocess via a DCL command, and this is not permitted. .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. .name OVERRIDE .message VDE library controls overridden via OpenVMS privileges .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. .user_action No action is required. .name MNEMONIC .message library () available .explanation This is an informational message, and indicates a particular library is available, as well as the mnemomic name associated with the library. .user_action No action is required. .name LIBLABEL .message library () contents: .explanation This is an informational message, and indicates the label associated with a particular library that is available. .user_action No action is required. .name NOPROMPT .message no prompt specified; using default prompt .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. .user_action No action is required. .name ICIGONE .message intermediate conference information not found .explanation This message is displayed in conjunction with other error messages, and indicates the particular failure that occurred. .user_action Resolve the basic error. If unable to resolve the error, please contact VDE support for assistance. .name ICIPARSE .message parse of intermediate conference information failed .explanation This message is displayed in conjunction with other error messages, and indicates the particular failure that occurred. .user_action Resolve the basic error. If unable to resolve the error, please contact VDE support for assistance. .name ICIBOGUS .message intermediate conference information invalid .explanation This message is displayed in conjunction with other error messages, and indicates the particular failure that occurred. .user_action Resolve the basic error. If unable to resolve the error, please contact VDE support for assistance. .name NODELARCH .message no DELARCH privilege; cannot delete architectures .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. .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. .name NOBUILD .message no BUILD privilege; cannot create build jobs in this library .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. .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. .name NOCREARCH .message no CREARCH privilege; cannot create or modify architectures .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. .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. .name NOCRECTX .message no CRECTX privilege; cannot create or delete contexts .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. .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. .name NOPERFREP .message no PREFREP privilege; cannot perform replacements .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. .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. .name NOCREFAC .message no CREFAC privilege; cannot create or modify facilities .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. .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. .name NOCREGRP .message no CREGRP privilege; cannot create or delete groups .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. .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. .name NOMODLIB .message no MODLIB privilege; cannot modify attributes of this library .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. .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. .name NOCREMOD .message no CREMOD privilege; cannot create or modify modules .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. .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. .name NOCRESTEP .message no CRESTEP privilege; cannot create or delete steps .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. .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. .name NOCREUSR .message no CREUSER privilege; cannot create or delete users .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. .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. .name NOCRESTRM .message no CRESTRM privilege; cannot create or modify streams .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. .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. .name NOFROZEN .message no FROZEN privilege; cannot replace modules into frozen streams .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. .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. .name NORESREP .message no RESREP privilege; cannot reserve and replace modules .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. .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. .name NOMODSTRM .message no MODSTRM privilege; cannot modify most stream attributes .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. .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. .name NOUSERNAME .message no USERNAME privilege; cannot reserve and replace for other users .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. .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. .name NODELSTRM .message no DELSTRM privilege; cannot delete streams from library .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. .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. .name NODELFAC .message no DELFAC privilege; cannot delete facilities from library .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. .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. .name NODELMOD .message no DELMOD privilege; cannot delete modules from library .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. .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. .name NOCRESCRP .message no CRESCRP privilege; cannot create or delete scripts .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. .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. .name NODELREP .message no DELREP privilege; cannot delete replacements .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. .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. .name NOUNCLOSE .message no UNCLOSE privilege; cannot unclose a closed stream .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. .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. .name NOVDEDEVO .message no VDEDEVO privilege; access to dungeon restricted .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. .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. .name NODELSET .message marked /NODELETE .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. .user_action To allow the object to be deleted, specify the appropriate MODIFY command with the /DELETE qualifier. Then reenter the failing DELETE command. .name NODELDEF .message Attempt to delete default prohibited .explanation You are attempting to delete a object (architecture, stream, facility, etc.) that is a default. .user_action To make the architecture deleteable use the MODIFY ARCHITECTURE command with the /DELETE qualifier. Then reenter the DELETE ARCHITECTURE command. .name WHYOFF .message reason: !AD .explanation This message is usually paired with VDE$_OFFLINE. The VDE environment has been taken offline, and this message indicates why. .user_action If the problem persists, please contact VDE support for assistance. .name PROTOTYPE .message this is a prototype version of VDE .explanation This message is used to indicate that the version of VDE in use contains debug or prototype code. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug or prototype images. .name PROTOLIB .message using prototype library .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug or prototype images. .name NOMAIL .message no message sent; MAIL messages are disabled .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug or prototype images. .name NONOTE .message no note topic entered; note entry is disabled .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug or prototype images. .name REGRESSION .message operating in mode suitable for regression tests .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. .user_action Contact VDE support for assistance, as this message should not be displayed under normal operations. .name QUOCHECK .message performing a quota check operation .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. .user_action Informational, no action is necessary .name QUORESET .message performing a quota check and update operation .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. .user_action Informational, no action is necessary .name QUOUSER .message user below recommended quota setting(s) .explanation This message indicates that the VDE/READ_UAF image has detected a username with a quota value that is below the recommended settings. .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.) .name QUOLOW .message quota set to: , recommended: .explanation This message indicates that the VDE/READ_UAF image has detected a username with a quota value that is below the recommended settings. .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.) .name IPMTFMT .message use ABC.12345, ABC-12345, ABC.123456 or ABC-123456 .explanation These are valid formats for the IPMT/CLD number. .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. .name DBGCMSGEN .message at , letflg , item1 , item2 .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name DBGCMSTXT .message at , expected .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. .user_action Contact VDE support for assistance, as the version of VDE in use contains debug-only images. .name TRYAGAIN .message please re-enter the problem code again .explanation There is a problem with the format of the problem code, and you are being prompted to re-enter the code again. 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. .user_action The the problem code name should be specified using the correct syntax for the code. .name MODOBS .message module superceded or marked obsolete .explanation The latest generation of the specified module indicates the module was superceded by a more recent module or was marked obsolete. .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. .name CONFACC .message unable to access notes conference .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. .user_action See the accompanying message(s). .name CONFMEM .message check conference file accessability and membership .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. .user_action See the accompanying message(s). .name CONFNAM .message conference file name .explanation This is the name of the notes conference. .user_action See the accompanying message(s). .name NOPNAMS .message no projects defined for the stream .explanation There are no projects associated with the specified development stream. .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. .name DBGXLAC .message debug reached; text: .explanation This message displays a waypoint, and the associated waypoint value, encountered during program execution. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name DBGXLXL .message debug reached; value: .explanation This message displays a waypoint, and the associated waypoint value, encountered during program execution. .user_action Contact VDE support for assistance, as the version of VDE in use contains debugging images. .name SETLIB .message use SET LIBRARY, VDE$LIBRARY, or /LIBRARY .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. .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. .name WHEREIS .message component is .explanation This message is used to display information about parts of the local VDE environment and VDE configuration. .user_action No action is required. .name DBCNV .message converting database format from to .explanation This message is used to display the status of a database conversion operation. .user_action No action is required. .name DBFMT .message database format is .explanation This message is used to display the current version of a database, or the status of a database conversion operation. .user_action No action is required. .name USEVERSLNM .message use logical name VDE$VMS_VERSION to override OpenVMS version .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. .user_action Define the logical name VDE$VMS_VERSION to a valid OpenVMS version string value. Only executive-mode translations in executive-mode logical name tables will be accepted. .name DBGDB .message debugging database: , .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. .user_action Contact VDE support for assistance, as the version of VDE in use should not be displaying this as an error message. .name NOTESCONF .message accessing notes conference .explanation This message informs you that VDE has successfully opened the indicated notes conference for notes access. .user_action None .name KEYADDED .message keyword added to note in conference .explanation This message informs you that VDE has successfully added the indicated keyword to a note in the indicated notes conference. .user_action None .name NOTESENTID .message note posted in conference .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. .user_action Use the /NOLOG qualifier for the command if you do not wish to see the message. .name DBCREATED .message database has been created .explanation This message indicates that a new library database, and associated database files, directories, and CMS libraries has been created. .user_action None required. .name WHOAMI .message .explanation This message displays the version identification of the particular VDE tool in use. This message is displayed automatically during the tool startup. The version of all tools should match the version main VDE image. .user_action None. .name LOGDATE .message Logfile created at .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGDB .message Accessing VDE database .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGUSER .message User () is responsible for: .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGPROC .message Processing the records for user () .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGDISUSER .message The username is disabled in SYSUAF .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGAFMTF .message Processing :[]. (Fold) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGFMTF .message Processing []. (Fold) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGAFMTR .message Processing :[]. (Reservation) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGFMTR .message Processing []. (Reservation) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGAFMTU .message Processing :[]. (Unknown Status) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGFMTU .message Processing []. (Unknown Status) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGTAFMTF .message !_:[]. (Fold) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGTFMTF .message !_[]. (Fold) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGTAFMTR .message !_:[]. (Reservation) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGTFMTR .message !_[]. (Reservation) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGTAFMTU .message !_:[]. (Unknown Status) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGTFMTU .message !_[]. (Unknown Status) .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGAGE .message !_ .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGSINCE .message displaying entries older than .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGUSRTOTAL .message has fold!%S and reservation!%S outstanding .explanation This message is used while writing to the aging logfile. .user_action None. .name LOGRUNTOTAL .message Total of fold!%S and reservation!%S outstanding .explanation This message is used while writing to the aging logfile. .user_action None. .destination message .name CGICTX .message content-type: text/html!/ .explanation This message is used while writing to the aging logfile. .user_action None. .name CGITTL .message VDE Reservation and Fold Aging .explanation This message is used while writing to the aging logfile. .user_action None. .name CGIH1 .message

Reservation and Fold Aging

.explanation This message is used while writing to the aging logfile. .user_action None. .name CGIDB .message

VDE Database: .explanation This message is used while writing to the aging logfile. .user_action None. .name CGIDT .message

Reservations and folds older than: .explanation This message is used while writing to the aging logfile. .user_action None. .name CGIBDY1 .message .explanation This message is used while writing to the aging logfile. .user_action None. .name CGIBDY2 .message .explanation This message is used while writing to the aging logfile. .user_action None. .name CGIPRE1 .message 

.explanation	This message is used while writing to the aging logfile.
.user_action	None.

.name	    CGIPRE2
.message
.explanation This message is used while writing to the aging logfile. .user_action None. .name CGIHR .message
.explanation This message is used while writing to the aging logfile. .user_action None. .name CGIP .message

.explanation This message is used while writing to the aging logfile. .user_action None. .name CRLF .message !/ .explanation This message is used while writing to the aging logfile. .user_action None. .name CGINOW .message

This page was generated at .explanation This message is used while writing to the aging logfile. .user_action None. .name CGICMTAZ .message {!!-- --} .explanation This message is used while writing to the aging logfile. .user_action None. .name CGICMTAS .message {!!-- --} .explanation This message is used while writing to the aging logfile. .user_action None. .name CGICMTAD .message {!!-- --} .explanation This message is used while writing to the aging logfile. .user_action None. .name CGICMTAC .message {!!-- --} .explanation This message is used while writing to the aging logfile. .user_action None. .destination both .name LOGNODE .message This log was created on node .explanation This message is used while writing to the aging logfile. .user_action None. .name PTRFMT .message use PTR-nnn-nnn-nnn .explanation This is the valid format for the PTR number .user_action The PTR number must be specified in the format PTR-nnn-nnn-nnn. If the PTR number is not in this format, or if this format is not accepted by VDE, please contact VDE support for assistance. .name PTRAGAIN .message please re-enter the PTR number .explanation There is a problem with the PTR number, and you are being prompted to re-enter the PTR 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. .user_action The PTR name should be specified using three leading alphabetic characters PTR, a hyphen, and three sets of numeric characters delimited by hypens. Respecify the correct PTR number using the PTR-nnn-nnn-nnnn format, where n is a numeric character. .name BUGPLUGNAM .message statistics shareable image name .explanation this is the file name of the statistics shareable image .user_action This message normally accompanies other messages. .name BUGPLUGDFN .message statistics shareable image default name .explanation this is the default name of the statistics shareable image .user_action This message normally accompanies other messages. .name BUGPLUGVERSHR .message statistics shareable image interface version .explanation this is the version of the statistics shareable image .user_action This message normally accompanies other messages. .name BUGPLUGVERVDE .message VDE statistics shareable image interface version .explanation this is the version of the statistics shareable image .user_action This message normally accompanies other messages. .name BUGINTRO .message are there any applicable problem reports? .explanation this message is part of a user query, and is not an error message. .user_action No action, beyond reading the message, is required. .destination message .name BUGID1 .message enter the code (or press if none) .explanation this message is part of a user query, and is not an error message. .user_action No action, beyond reading the message, is required. .name BUGID2 .message enter the code (or press to end list) .explanation this message is part of a user query, and is not an error message. .user_action No action, beyond reading the message, is required. .destination both ! ! Warning messages go here. DO NOT REORDER. ! .base 1000 .severity warning .destination both .name ABKEYW .message ambiguous qualifier or keyword '' - supply more characters .explanation VDE cannot complete the command because '(text)' is ambiguous in the context of this command. .name ABTBADST .message VDE may be in an inconsistent internal state .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. .user_action Leave and enter VDE again to make sure the internal state is consistent. .name ABTCNTLC .message command aborted by Control-C .explanation The current VDE command has been aborted due to a control C issued by the user. VDE will attempt to gracefully recover. .user_action Issue another command to VDE. It has gracefully to a consistent internal state. .name BADCHAR .message illegal character encountered .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. .user_action Verify the appropriate syntax of the specific command. .name BADFILNAM .message illegal file specification '' .explanation The provided file name does not follow standard VMS file specification conventions. .name CONFLICT .message conflicting qualifers and/or keywords specified .explanation This message is issued when VDE detects conflicting qualifiers and/or keywords within the same command. .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 (VDE_MANUAL_NAME) for assistance with the command syntax. .name CONKEYATR .message conflicting key attributes and .explanation The recently issued DEFINE KEY command has conflicting qualifiers such as /NOSTATE and /LOCK_STATE. .user_action Determine correct applicability and reissue the command. .name CONQUAL .message conflicting qualifiers / and / .explanation The above mentioned qualifiers are mutually exclusive. .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. .name DEFKEYERR .message error defining key .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. .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. .name DELKEYERR .message error in processing DELETE/KEY command .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. .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. .name EXARANGE .message hexadecimal number not valid; valid range is to .explanation Illegal hexadecimal range provided as input. .user_action Verify that the provided hexadecimal range is in an accepted format. .name FIRNUMMAY .message first number of a range may not be less than .explanation Some integers provided in the command line must be greater than a given "n". .user_action Verify that the appropriate "n" was given in the command line. .name FIRNUMRAN .message first number of a range must be less than the second .explanation When providing a range in the format n[:m], "n" must be less than "m". .user_action Correct the range description and reissue the command. .name ILLFORUSE .message ill-formed user defined name .explanation In the DEFINE/COMMAND command, the provided user-defined name is illegal. .user_action Reissue the command with the correct user defined name. .name ILLDEPFUN .message Illegal dependency function passed to module VDE$REC_DEPENDENCY. The illegal dependency function value is .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. .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. .name INTTOOBIG .message integer too large .explanation Integer values entered from the command line must fit into a longword. .user_action Determine if it is necessary to provide such a large number. If it is necessary, then this is a restriction of VDE. .name INVKEYNAM .message invalid or missing key name .explanation The name of a key on the keyboard was expected in this command. .user_action Reissue the command with an acceptable name of a key. .name IVQLOC .message invalid qualifier location - place after each dependency file parameter .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. .user_action Reissue the command with the proper syntax. .name IVQUAL .message unrecognized qualifier '' - check validity, spelling, and placement .explanation An undefined qualifier was found. .user_action Verify the syntax for the command and reissue it with only the allowed qualifiers. .name LIBINDRAN .message Library index value of out of range for library dependency or module dependency. .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. .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. .name MATQUOMIS .message matching quote is missing .explanation All quoted strings must be delimited by either two single or two double quotes. .user_action Reenter the command with appropriately quoted string. .name MAXPARM .message too many parameters - reenter command with fewer parameters .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. .user_action Choose between /ALL or just one key in either the SHOW KEY or DELETE KEY commands. .name NEEDMORE .message unexpected end of command line .explanation Many commands require the presence of additional parameters or qualifiers. .user_action Review the correct syntax of the respective command and enter it with the appropriate parameters. .name NOCLOSEQ .message no closing quotation mark for a quoted string .explanation For the DEFINE/COMMAND command, the parameter that describes the command must be enclosed with either single or double quotes. .user_action Reenter the DEFINE/COMMAND command with the appropriate quotes. .name NOKEYW .message qualifier name is missing - append the name to the slash .explanation A qualifier is composed of both a "/" and keyword. If only a "/" appears, then this error message is displayed. .user_action Ensure that there are no dangling "/" in the command. .name NOSETTERM .message the SET TERMINAL command is not supported on this terminal .explanation SET TERMINAL is only supported on VT52, VT100-series, VT200-series, VT300-series, VT400-series, VT500-series, and DECterm terminals. .name NOTINRANGE .message integer value not in valid range of to .explanation The indicated integer value is not within the valid range for the qualifier or parameter on which it is specified. .user_action Reenter the command with the integer value within the proper range. .name OVFLOWBUF .message overflow of the input buffer, command ignored. .explanation A VDE command line may only consist of records that are less than 1024 characters long. .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. .name QUOSTREXP .message quoted string expected .explanation A quoted string was expected. This quoted string must be delimited by either single or double quotes. .name READERR .message VDE input read error, forced to exit .explanation An error was found in reading an input line. .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. .name REQQUAMIS .message required command qualifier missing .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. .name SETKEYERR .message error in processing SET KEY command .explanation The screen management facility is used to maintain screen bindings. In this instance, SMG$SET_DEFAULT_STATE has returned an error. .user_action See SMG documentation to determine the problem. If your answer cannot be found, please contact VDE support for assistance. .name SHOKEYERR .message error in processing SHOW KEY command .explanation The screen management facility is used to maintain screen bindings. In this instance, SMG$LIST_KEY_DEFS has returned an error. .user_action See SMG documentation to determine the problem. If your answer cannot be found, please contact VDE support for assistance. .name STRTOOLONG .message quoted string too long; must be shortened .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. .user_action Try to shorten the size of the string. .name SYNTAX .message command syntax error at or near: '' .explanation All commands have a specific syntax that must be followed. Failure to do so will result in this error. .user_action See (VDE_MANUAL_NAME) for assistance with the command syntax. .name UNAOPEINP .message unable to open input stream '' .explanation VDE could not read the command line correctly. .user_action The logical name VDE$INPUT is probably not defined correctly. Correct the VDE$INPUT reference. .name UNKEYW .message unrecognized keyword '' - check validity and spelling .explanation The keyword provided in the command was unrecognized in this context. .user_action See (VDE_MANUAL_NAME) for assistance with the command syntax. .name UNMATQUO .message unmatched quote or missing quote at end of string .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. .user_action Reenter the command with the appropriate quotes balanced. .name VALREQ .message missing qualifier or keyword value - supply all required values '' .explanation In many commands, specific keywords or qualifiers are expected. .user_action See (VDE_MANUAL_NAME) for assistance with the command syntax. .name LOQUOTA .message one or more process quotas is too low .explanation The currently-free value of one or more quotas is below the recommended values for VDE. VDE will attempt to continue. .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. .name LOASTLM .message recommended free ASTLM value is .explanation The amount of the ASTLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOBIOLM .message recommended free BIOLM value is .explanation The amount of the BIOLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOBYTLM .message recommended free BYTLM value is .explanation The amount of the BYTLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LODIOLM .message recommended free DIOLM value is .explanation The amount of the DIOLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOENQLM .message recommended free ENQLM value is .explanation The amount of the ENQLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOFILLM .message recommended free FILLM value is .explanation The amount of the FILLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOPGFLQUOTA .message recommended free PGFLQUOTA value is .explanation The amount of the PGFLQUOTA quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOPRCLM .message recommended free PRCLM value is .explanation The amount of the PRCLM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name LOTQELM .message recommended free TQELM value is .explanation The amount of the TQELM quota currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name CONTINUE .message attempting to continue .explanation One or more quotas are below the recommended values for VDE. VDE will attempt to continue. .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. .name BADIMAFLA .message bad image flavor detected .explanation VDE has detected an inconsistent image flavor setting. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name XMERROR .message Motif interface error detected .explanation VDE has detected an error in the Motif interface. .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. .name NEEDMODULE .message this request requires a module .explanation VDE was unable to perform the specified request as a module was not selected nor otherwise specified. .user_action Select or specify a module, and retry the request. .name NEEDSTREAM .message this request requires a stream .explanation VDE was unable to perform the specified request as a stream was not selected nor otherwise specified. .user_action Select or specify a stream, and retry the request. .name NEEDFACILITY .message this request requires a facility .explanation VDE was unable to perform the specified request as a facility was not selected nor otherwise specified. .user_action Select or specify a facility, and retry the request. .name NEEDLIBRARY .message this request requires a library .explanation VDE was unable to perform the specified request as a library was not selected nor otherwise specified. .user_action Select or specify a library, and retry the request. .name NOCAUSE .message replacement cause not known; module not replaced .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. .user_action Select the appropriate replacement cause -- Source Code Tracking (SCT), Fold, or Other -- using the toggle buttons on the module replacement dialog box. .name SCTCONF .message SCT note conference null; module not replaced .explanation The required SCT notes conference name field was found empty on a replacement operation. .user_action Please reenter the SCT notes conference name using correct syntax, and retry the replacement operation. .name SCTCONFSYN .message SCT note conference syntax error; module not replaced .explanation VDE detected a syntax error in the SCT notes conference name field. .user_action Please reenter the SCT notes conference name using correct syntax, and retry the replacement operation. .name SCTNOTE .message SCT note number null; module not replaced .explanation The required SCT note number field was found empty on a replacement operation. .user_action Enter the number of the associated SCT note using correct syntax, and retry the replacement operation. .name SCTNOTESYN .message SCT note number syntax error; module not replaced .explanation VDE detected a syntax error in the SCT note number field. .user_action Please reenter the SCT note number using correct syntax, and retry the replacement operation. .name SCTFCMT .message SCT fold comment required; module not replaced .explanation The required SCT fold comment field was found empty on a replacement operation. .user_action Enter an SCT fold comment and retry the replacement operation. .name NOSCT .message replacement cause not known; module not replaced .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. .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. .name SCTFNF .message unable to locate notes conference .explanation VDE was unable to open the specified SCT notes conference .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. .name UNKPNAM .message unable to locate project in stream .explanation VDE has unable to locate the specified project name associated with the specified stream. .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. .destination message .name SPARE_8 .message was FOLDNOTFOUND .explanation filler for error message elevated to a warning. .user_action This message should not appear. .destination both .name NOPNAM .message unknown project name specified for the stream .explanation The specified project name does not match the project names associated with the specified development stream. .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. .name NONNULLARG .message argument specfied MBZ has non-zero value in routine .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. .user_action Please notify VDE support. Please include any information that may be useful or relevent in duplicating the problem. .name LOJTQUOTA .message recommended free JTQUOTA is .explanation The amount of the JTQUOTA currently available is below the recommended value for VDE. VDE will attempt to continue. .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. .name PUTMSGNOT .message sys$putmsg output suppressed .explanation This status is used within VDE to suppress the display of a message via a sys$putmsg system service action routine. This message should not be displayed by VDE. .user_action Please notify VDE support. Please include any information that may be useful or relevent in duplicating the problem. .name NOBUGPLUG .message no statistics shareable image found for this database .explanation This database is configured to request statistical information, and the shareable image that performs this task cannot be located. This message indicates only that the collection of statistical information has failed, and does not indicate that the replacement has failed. The replacement operation will be processed entirely seperately from this warning, and will succeed or fail seperately. .user_action Determine if this database should ask for statistical information (MODIFY LIBRARY/[NO]STATISTICS]. If statistics are to be collected, determine where the associated statistics shareable image has gone. ! ! Error messages go here. DO NOT REORDER. ! .base 1500 .severity error .destination both .name BADMARKER .message bad marker file format for generation .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. .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. .destination message .name SPARE_6 .message was BADSTATUS; replaced .explanation This message (was BADSTATUS) has been superceded; the BADSTATUS message now returns an error severity. .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. .destination both .name BINSRCMOD .message binary source modules cannot be displayed or differenced .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. .user_action Do not use the SHOW or EDIT command on binary source modules. .name BITRANGE .message bit range out of limits .name BLDJOBACT .message build job already active for stream ; new job not created .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 (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. .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. .name CMSCRECLASS .message CMS error when creating CMS class in facility .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSCREELEM .message CMS error when creating CMS element for module .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. .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. .name CMSCRELIB .message CMS error when creating CMS library for facility .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. .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. .name CMSDELELEM .message CMS error when deleting element .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. .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. .name CMSDELGEN .message CMS error when deleting generation () .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. .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. .name CMSFETCH .message CMS error when fetching CMS element for module .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. .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. .name CMSINSGEN .message CMS error inserting generation of element into class .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSMODCLASS .message CMS error modifying the class name to in facility .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSREMGEN .message CMS error removing element from class .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSREPLACE .message CMS error when replacing CMS element for module .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. .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. .name CMSRESERVE .message CMS error when reserving CMS element for module .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. .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. .name CMSSETLIB .message CMS error when setting CMS library for facility .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. .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. .name CMSSHOWCLASS .message CMS error when retrieving CMS class information in library .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSSHOWDESGEN .message CMS error when retrieving CMS generation of element .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSSHOWELEM .message CMS error when retrieving CMS element in library .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSSHOWHIST .message CMS error when retrieving CMS history in library .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSSHOWRES .message CMS error when retrieving CMS reservations in library .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. .user_action If the problem appears to be due to an internal VDE error, submit a problem report. .name CMSVARLET .message all CMS variant letters in use; none left for module .explanation All CMS variant letters up to "Z" are already in use for the indicated module. Hence the current REPLACE operation cannot be performed. .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. .name CMSVERGEN .message CMS error reading class membership list when verifying generation () .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. .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. .name COMTERMEOF .message command terminated by CTRL/Z or end-of-file on input .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. .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. .name CTXDELARCH .message context <##,!AC> contains deleted architecture .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. .user_action Redefine the context to reference an architecture that has not been deleted. Then reissue the command. .name CTXDELFAC .message context contains deleted facility .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. .user_action Redefine the context to reference a facility that has not been deleted. Then reissue the command. .name CTXDELSTRM .message context contains deleted stream .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. .user_action Redefine the context to reference a stream that has not been deleted. Then reissue the command. .name DATETOOLONG .message date-time value is too long; maximum length is 24: ... .explanation A date-time value entered as a command parameter is too long because it exceeds the maximum length indicated in the message. .user_action Reissue the command with a shorter date-time value. .name DCLBUFOVFL .message DCL command line being generated is too long for buffer .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. .user_action Change the command line specification in the script for it. .name DCLERROR .message error status returned by spawned DCL command .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. .user_action Determine the cause of the problem, correct it, and retry the VDE command. .name DIRTOOLONG .message directory specification is too long; maximum length is 255 .explanation A directory specification entered as a command parameter is too long because it exceeds the maximum length indicated in the message. .user_action Reissue the command with a shorter directory specification. .name DIRNOTFOUDCL .message directory location not found for script's DCL command file .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. .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. .name DIRNOTFOULOG .message directory location not found for build-step log file .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. .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. .name DIRNOTFOUSCRP .message directory location not found by script function .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. .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. .name DUPLNAME .message duplicate name in list not allowed: .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. .user_action Correct the error and reissue the command without any duplicates. .name EDITUNDEF .message your editor is undefined; editor cannot be invoked .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. .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. .name ERRDIRSPEC .message error in directory or file specification .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. .user_action Correct the error in the directory or file specification and reissue the command. .name ERRWRIFIL .message error writing file .explanation The output could not be written to the appropriate file. .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. .name EXPGENLONG .message expected CMS generation expression is too long .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. .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. .name FACEXISTS .message facility already exists in database .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. .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. .name FILENOTFOUND .message file not found: .explanation The indicated file was requested through a VDE command, but could not be found. Hence the current command cannot perform the requested action. .user_action Do without the file or determine why the file is missing and correct the problem. .name FILREADERR .message unable to read file .explanation An error occurred when trying to read a line of text from an input file. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name FILWRITERR .message unable to write file .explanation An error occurred when trying to write a line of text to an output file. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name FIRGENNODEL .message generation is first generation of module; cannot be deleted .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. .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. .name FOLDIDREQ .message fold identifier required for module .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. .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. .name FOLDIDUSED .message fold identifier already used for module <,!/> attempt to create fold record has failed .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. .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. .name GENNODEL .message generation cannot be deleted .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. .user_action Check that you have specified the correct generation for deletion. .name GENNOPRED .message generation of has no predecessor .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. .user_action Specify a generation that has a predecessor (normally any generation except generation 1) and rerun the command. .name GETJPI .message SYS$GETJPI system service failed, unable to attach .explanation The ATTACH command could not continue because a failed service call to SYS$GETJPI occurred. .user_action Determine if there is any external interference. If no interference can be found, then please submit a problem report. .name GETQUIERR .message get queue information system service error for queue .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. .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. .name INVGENEXPR .message invalid CMS generation expression: .explanation A CMS generation expression on a VDE command is not syntactically correct. .user_action Reenter the VDE command with a valid CMS generation expression. .name INVDATTIM .message invalid date-time; use DD-MMM-YYYY:HH:MM:SS.CC format: .explanation The format of a date-time value entered as a command parameter is invalid. .user_action Correct the error in the date-time value and reissue the command. .name INVDBFORM .message invalid database format; VDE is unable to access library .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. .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. .name INVDIGDEC .message invalid decimal number: .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. .user_action Reissue the command with the appropriate number. .name INVDIRSPEC .message invalid directory specification: .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. .user_action Reenter the VDE command with a valid directory specification or define the logical name to be bound to a valid directory specification. .name INVHISCHAR .message invalid history or notes character following poundsign<,!/>invalid string is: .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. .user_action Reenter the VDE command with a valid history or notes string. .name INVINPUT .message invalid interactive command input; command aborted .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. .user_action Reissue the command with correct qualifiers and parameters or with correct input to interactive queries for command information. .name INVINTVAL .message invalid integer value on command line: .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. .user_action Reissue the command with a valid integer value. .name INVPAGE .message invalid screen height, value must be between and .explanation For the SET TERMINAL command, the /PAGE qualifier must provide a page length between 11 and 100, inclusively. .user_action Reissue the SET TERMINAL command with an acceptable page size. .name INVWIDTH .message invalid screen width, value must be between and .explanation For the SET TERMINAL command, the /WIDTH qualifier can provide a page length between 40 and 255, inclusively. .user_action Reissue the SET TERMINAL command with an acceptable width. .name INVWILDSPEC .message invalid wildcard specification in script selector: .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 (*); 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. .user_action Reissue the command with an acceptable wildcard specification. .name LIBNOTSET .message library not set; no VDE database found in directory .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.) .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. .name LOGNAMUNDEF .message logical name undefined; operation cannot complete .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. .user_action Exit the VDE kept process with the EXIT/KEPT_PROCESS command, define the required logical name, restart VDE, and retry the operation. .name MAXIDVAL .message maximum allowed Id value in database exceeded: .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. .user_action Please contact VDE support for assistance. Most likely the VDE database has been damaged by an internal error. .name MISCONTSCRP .message missing continuation line in script .explanation The current script specified that the last line should be continued but no such continuation line exists. A hyphen (-) at the end of a line indicates that the line should be continued. .user_action Either remove the hyphen at the end of the last line or supply a continuation line, whichever is appropriate. .name MISHISPARM .message missing history parameter in string "" .explanation A history string was specified which does not contain a history parameter. A history parameter is required as part of the history string. .user_action Reenter the VDE command with a valid history string. .name MISTYPNAM .message missing type name for module ; type name required .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. .name MODALRQUEREP .message module already queued for replacement .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. .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. .name MODALRRES .message module already reserved; reservation has failed .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. .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. .name MODLOCKED .message module locked for replacement by another user .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. .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. .name MODNOTINSTRM .message generation not in stream .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. .user_action Use the /NOPROPAGATE qualifier for the command or populate the specified stream with the specified generation and try the command again. .name MODNOTRES .message module is not currently reserved .explanation You are trying to replace the indicated module but that module is not currently reserved in the current stream development stream. .user_action Reserve the module before trying to replace it. .name MODNOTREV .message module not found in review list .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. .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. .name NAMTOOLONG .message name is too long: ; maximum length is .explanation A name entered as a command parameter is too long because it exceeds the maximum length indicated in the message. .user_action Reissue the command with a shorter name. .name NEEDMOD .message module must be specified on command .explanation You have failed to specify a module name on a command that requires it. .user_action Enter the module name you want on the command. .name NEEDSTEP .message build step must be specified on command .explanation You have failed to specify a build step on a command that requires it. .user_action Enter a module name on the command to select the build step you want. .name NOACCLIB .message no access to library allowed for user .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. .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. .name NOARCHSPEC .message no architecture specified for operation .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. .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. .name NOATTACH .message failed to attach to process PID !XL .explanation The ATTACH command has failed to attach to the requested process. .user_action Verify that the requested process exists. Check spelling of the process name. .name NOBLDSTEPS .message build job contains no build steps; build job is not created .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. .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. .name NOCANRES .message cannot cancel reservation to create first generation of .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. .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. .name ARCHNOTDEL .message architecture not deleted .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. .user_action Resolve the problem(s) flagged by the other error messages, and reenter the DELETE ARCHITECTURE command. .name FACNOTDEL .message facility not deleted .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. .user_action Resolve the problem(s) flagged by the other error messages, and reenter the DELETE FACILITY command. .name FACNOTMT .message facility contains modules .explanation The specified facility contains modules. .user_action The requested operation is prohibited due to the presence of modules in the facility. .name MODNOTDEL .message module not deleted .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. .user_action Resolve the problem(s) flagged by the other error messages, and reenter the DELETE MODULE command. .destination message .name SPARE_4 .message was STRMNOTDEL .explanation message superceded (was STRMNOTDEL) .user_action Contact VDE support for assistance .destination both .name NODELTAROOT .message no delta-file root directory exists for library .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. .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. .name NODIRDELTA .message no delta-file directory found for facility .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. .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. .name NODIRMARKER .message no marker-file directory found for facility .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. .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. .name NOFACSPEC .message no facility specified for operation .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. .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. .name NOFREE .message no free storage available .explanation VDE has run out of virtual memory. .user_action Use less complex commands, raise the virtual-address quota, or submit a problem report. .name NOGENSTRM .message generation not found in stream .explanation The indicated module generation was entered on a command, but no such generation was found in the specified stream. .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. .name NOLIBDEF .message no VDE library defined .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. .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. .name NOMEMGRP .message no members specified for group .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.) .user_action Reenter the CREATE GROUP command, specifying the names of the modules that you want to be the members of the new group. .name NOMOREMOD .message no more modules in review list .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. .user_action Review build steps in the other direction or exit from the REVIEW REPLACEMENT subsystem. .name NOMORESTEP .message no more build steps in review list .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. .user_action Review build steps in the other direction or exit from the REVIEW BUILD_JOB subsystem. .name NOPARSTRM .message no parent stream specified for new stream .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. .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. .name NOPRIVQUAL .message insufficient privilege to use qualifier .explanation You attempted to use a command qualifier that requires a privilege, and you did not have that privilege set. .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. .name NOPRIVS .message insufficient VDE privilege(s) for attempted operation .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. .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. .name NOSCRIPTYP .message no script type specified on command .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. .user_action Reenter the command with a qualifier to specify the script type of the script. .name NOSTRMSPEC .message no stream specified for operation .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. .user_action Renter the command, specifying the stream name as required. .name NOSUCHARCH .message architecture not found in database .explanation The indicated architecture name was entered on a command, but no such architecture was found in the VDE database. .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. .name NOSUCHCTX .message context not found in database .explanation The indicated context name was entered on a command, but no such context was found in the VDE database. .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. .name NOSUCHDIRSYM .message directory symbol not found in database .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. .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. .name NOSUCHFAC .message facility not found in database .explanation The indicated facility name was entered on a command, but no such facility was found in the VDE database. .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. .name NOSUCHFOLD .message fold record not found for module and stream .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. .user_action Specify a valid fold record and reenter the command. .name NOSUCHFUNC .message no such script function exists: .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. .user_action Correct the spelling of the function name or select a directory symbol name that does not begin with a dollar sign. .name NOSUCHGEN .message generation not found in database .explanation The indicated module generation was entered on a command, but no such generation was found in the VDE database. .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. .name NOSUCHGRP .message group not found in database .explanation The indicated group name was entered on a command, but no such group was found in the VDE database. .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. .name NOSUCHMOD .message module not found in database .explanation The indicated module name was entered on a command, but no such module was found in the VDE database. .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. .name NOSUCHPRIV .message no such privilege name exists: .explanation An invalid privilege name was specified on a VDE command. .user_action Check the spelling of the privilege name and reenter the command with a correct privilege name. .name NOSUCHREP .message replacement not found in database .explanation The indicated replacement name was entered on a command, but no such replacement was found in the VDE database. .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. .name NOSUCHRES .message reservation for module not found .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. .user_action Specify the correct reservation identifier and reissue the command. .name NOSUCHSCRP .message script not found in database .explanation The indicated script was specified on a command, but no such script is found in the VDE database. .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. .name NOSUCHSES .message session not found in database .explanation The indicated session name was entered on a command, but no such session was found in the VDE database. .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. .name NOSUCHUSER .message user not found in database .explanation The indicated username was entered on a command, but no such user was found in the VDE database. .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. .name NOSUCHSTRM .message stream not found in database .explanation The indicated stream name was entered on a command, but no such stream was found in the VDE database. .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. .name NOSPAWN .message spawn command failed .explanation A process cannot be spawned by VDE. .user_action Check your process's quotas. .name NOSTAGROOT .message no staging area root directory exists for library .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 (staging)) the files to be replaced. .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. .name NOSTRMROOT .message no stream root directory exists for stream .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. .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. .name NOTREVREP .message you are not a reviewer for replacement .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. .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. .name NOTCONNLIB .message you are not connected to a VDE library; command not performed .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. .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. .name NOTRESINSTRM .message module not reserved in stream .explanation You are trying to unreserve or replace a module in the indicated stream, but the module is not reserved in that stream. .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. .name NULSTRNOT .message a null string is not allowed .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. .user_action Reenter the command providing a string with this qualifier, or no value at all. .name PREFIXNOTALL .message prefix VDE$ not allowed in facility or stream names .explanation You have tried to create or rename a facility or stream with a name that begins with the prefix (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. .user_action Reenter the command with a facility or stream name that does not begin with VDE$. .name QUALDISALL .message qualifier is disallowed for the command .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. .user_action Reenter the command without the offending qualifier or change the library attribute that disallows it, if applicable. .name QUALNOTALL .message qualifier is not allowed when a parameter is specified .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. .user_action Reenter the command with either the indicated qualifier or with command parameters, but not both. .name QUALTOOMANY .message qualifier has been specified too many times .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. .user_action Reenter the command with the indicated qualifier specified no more than once for each parameter. .name REPBELUSER .message replacement belongs to another user .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. .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. .name RESIDREQ .message reservation identifier required for module .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. .user_action Reissue the command with the /IDENTIFICATION qualifier to indicate the specific reservation to which you want the command to apply. .name RESIDUSED .message reservation Id already used for module <,!/> attempt to reserve module has failed .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. .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. .name RIGIDNOTFOU .message required rights identifier not found in rights database .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. .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. .name RIGIDNOTHELD .message you do not hold required rights identifier .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. .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. .name SCRPCMDTOOLONG .message script command is too long; it exceeds characters .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. .user_action Change the script command so that it is not so long. .name SCRPFACFAIL .message script for facility terminated with errors .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. .user_action Correct the error in the script and reenter the command. .name SCRPFUNCUNDEF .message script function is undefined in the current script .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. .user_action Do not use the indicated function in the script. .name SCRPMODFAIL .message script for module terminated with errors .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. .user_action Correct the error in the script and reenter the command. .name SESBELUSER .message session belongs to another user .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. .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. .name SETUNAUTH .message attempt to set unauthorized privileges; privileges not set .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. .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. .name SNDJBCERR .message job controller error status for queue .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. .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. .name SRCNOTOUT .message source module cannot be an output from build step .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. .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. .name STATNOTSPEC .message the kind of statistics to display was not specified .explanation This qualifier requires a keyword specifying what kind of statistics to display. .user_action Reenter the command providing a keyword specifying what kind of statistics to display. .name STEPNOTCRE .message build step not created; module not found in database .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. .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. .name STEPNOTFOUND .message build step for module not found in database .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. .user_action Reenter the command specifying an existing build step or create the desired build step with the CREATE STEP command. .name STEPNOTMOD .message build step not modified; module not found in database .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. .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. .name STEPNOTREV .message build step for module not found in review list .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. .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. .name STKOVF .message command procedures too deeply nested; limit is 16 levels .explanation VDE allows only 16 levels of nesting of command procedures. .user_action Embed some of the command procedures within others to decrease the level of nesting to fewer than 16. .name STRMEXISTS .message stream already exists in database .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. .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. .name STRMNOTCLOSED .message stream can not be deleted because it is not closed .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. .user_action If appropriate, change the state of the stream to closed and repeat the delete stream command. .name STRMNOTOPEN .message stream is not open; operation not allowed .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. .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. .name STRMNOTPOP .message stream is not allowed to be populated .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. .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. .name SUCGENEXIST .message successor generation for already exists in library .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 (owns) the whole-number successor generation with the /MAIN_STREAM qualifier to the MODIFY GENERATION command. .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. .name TRANTOODEEP .message translation of logical name more than 7 deep .explanation The indicated logical name is either too deeply nested, or is defined incorrectly to point back to itself causing an infinite translation loop. .user_action Reenter the command without using the logical name. .name TOOMANPARM .message too many poundsign parameters in history or notes string<,!/>invalid string is: .explanation The history or notes string specified contains more than one history or notes parameter. This is not allowed. .user_action Reenter the command with a valid history or notes string. .name UNACLOFIL .message unable to close file .explanation An error occurred when trying to close the indicated text file. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name UNACLOLOG .message unable to close log file .explanation The SYS$CLOSE system service was not performed successfully in closing the log file. .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. .name UNACONLOG .message unable to connect log file .explanation The SYS$CONNECT system service was not performed successfully in connecting the log file's RAB and FAB. .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. .name UNACONVDBFORM .message unable to convert database format due to access conflict with another user .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. .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. .name UNACREFIL .message unable to create file .explanation An error occurred when trying to create or open a new text file. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name UNACRELOG .message unable to create log file .explanation The SYS$CREATE system service was not performed successfully in creating the output file. .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. .name UNACREMBX .message unable to create temporary mailbox .explanation An error occurred when trying to create a mailbox for sending text between processes. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name UNADELFIL .message unable to delete file .explanation An error occurred when trying to delete the indicated file. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name UNAOPEFIL .message unable to open file .explanation An error occurred when trying to open an existing text file for reading. A more specific error message follows this message. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name UNAPARFIL .message unable to parse file name with default string .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. .user_action Examine the error message that follows to diagnose the reason for the error. Then correct the problem accordingly. .name UNKFILEXT .message Unknown file extension in analysis file; the complete file<,!/>specification found was .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. .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. .name USERNOTUAF .message user not found in system User Authorization File .explanation The indicated username is your username, but it was not found in the system User Authorization File. .user_action This error should not happen except to VDE developers who redefine the current user during testing. Submit a problem report. .name WILDGENNUM .message wildcarded generation number not allowed in .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. .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. .name WILDNOTALL .message wildcard characters not allowed in name: .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. .user_action Specify the name without a wildcard character and resubmit the command. .name INCNOTVAL .message INPUT not valid on streams marked for queued replacement .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. .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.] .name CREDIRFAI .message create directory failed .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. .user_action Reenter the VDE command with a valid directory specification or define the logical name to be bound to a valid directory specification. .name NOSCRATCH .message no SYS$SCRATCH translation .explanation The translation of the SYS$SCRATCH logical name is not valid. .user_action Reenter the VDE command after redefining SYS$SCRATCH to a valid directory specification. .name BADSCRATCH .message bad SYS$SCRATCH directory .explanation The directory specification associated with the SYS$SCRATCH logical name is not syntactically correct. Associated with the VDE$_INVDIRSPEC error. .user_action Reenter the VDE command after redefining SYS$SCRATCH to a valid directory specification. .name SPEMERFAI .message specification merge failure .explanation internal state information for VDE$_INVDIRSPEC error. .user_action Correct the cause of the VDE$_INVDIRSPEC error. .name SECMERFAI .message secondary merge failure .explanation internal state information for VDE$_INVDIRSPEC error. .user_action Correct the cause of the VDE$_INVDIRSPEC error. .name DIRTREFAI .message directory tree conversion failed .explanation internal state information for VDE$_INVDIRSPEC error. .user_action Correct the cause of the VDE$_INVDIRSPEC error. .name DIRFILFAI .message directory filename conversion failed .explanation internal state information for VDE$_INVDIRSPEC error. .user_action Correct the cause of the VDE$_INVDIRSPEC error. .name DIREXPFAI .message directory filename expansion failed .explanation internal state information for VDE$_INVDIRSPEC error. .user_action Correct the cause of the VDE$_INVDIRSPEC error. .name DIREXPBAD .message directory filename expansion bad .explanation internal state information for VDE$_INVDIRSPEC error. .user_action Correct the cause of the VDE$_INVDIRSPEC error. .name INVDATLNM .message invalid VDE$DATE_TIME; use DD-MMM-YYYY:HH:MM:SS.CC format: .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. .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. .name LOCKED .message library write access is disabled .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. .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. .name NOSETLIB .message the SET LIBRARY command is locked out .explanation The SET LIBRARY command is disabled when executing a beta version of VDE. .user_action Contact VDE support for assistance, as the version of VDE in use contains beta-only images. .name INVIPMTNAM .message invalid IPMT/CLD number syntax .explanation The format for the CLD number is not valid. .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. .name INVQARDB .message invalid QAR database name syntax .explanation The format for the QAR database name is not valid. .user_action Respecify the QAR database name using only alphanumeric, underscore, dollar sign or hyphen characters. .name INVQARNO .message invalid QAR entry number syntax .explanation The format of the QAR entry number is not valid. .user_action Respecify the QAR entry number using only numeric characters. .name ITEMLIST .message unable to parse itemlist list entry at offset .explanation VDE has detected a size, type code or buffer address error at the specified entry offset in the itemlist. .user_action Please evaluate the specified entry offset in the itemlist, and rework it as appropriate. .name ARCHSYNTAX .message invalid architecture name syntax: .explanation The name or format specified for the architecture name is not using valid syntax. .user_action Respecify the architecture name using only alphanumeric, underscore, dollar sign and hyphen characters. .name TRYSYNTAX .message invalid syntax: .explanation The name or format specified for the problem report is not using valid syntax. .user_action Respecify the problem report using correct syntax for the specific problem subsystem. .name CTXSYNTAX .message invalid context name syntax: .explanation The name or format specified for the context name is not using valid syntax. .user_action Respecify the context name using only alphanumeric, underscore, dollar sign and hyphen characters. .name FACSYNTAX .message invalid facility name syntax: .explanation The name or format specified for the facility name is not using valid syntax. .user_action Respecify the facility name using only alphanumeric, underscore, dollar sign and hyphen characters. .name GRPSYNTAX .message invalid group name syntax: .explanation The name or format specified for the group name is not using valid syntax. .user_action Respecify the group name using only alphanumeric, underscore, dollar sign and hyphen characters. .name REPSYNTAX .message invalid replacement name syntax: .explanation The name or format specified for the replacement name is not using valid syntax. .user_action Respecify the replacement name using only alphanumeric, underscore, dollar sign and hyphen characters. .name QARDBSYNTAX .message invalid QAR database name syntax: .explanation The name or format specified for the QAR database name is not using valid syntax. .user_action Respecify the QAR database name using only alphanumeric, underscore, dollar sign and hyphen characters. .name NOTIMPL .message this feature is not currently implemented .explanation This message informs you that the indicated feature or callback is not currently implemented. .user_action Please contact VDE support for assistance. .name NETERROR .message network error; component: , code: .explanation Something deep within the bowels of the VDE network layer has returned an error. .user_action Please check the status of the local network, and then contact VDE support for further assistance. .name FAMILY .message unable to deallocate: siblings or children present .explanation Something deep within VDE has attempted to deallocate a data structure that has siblings or children. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name NOLIBROOM .message too many libraries in default file .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. .user_action If you are unable to reduce the number of libraries in the default file, please contact VDE support for assistance. .name SCRQUOERR .message no closing quotation mark in script command:!/ .explanation VDE has detected a missing quote in the specified command for the script. The script command must be respecified using correct syntax. .user_action The script command must be respecified using correct syntax. .name CRELNMFAI .message failed to define logical name .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. .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. .name MODEXISTS .message module already exists in database; module not changed .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. .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. .name INTFUNCERR .message internal script function error .explanation The script function encountered an error during the parsing, and cannot be processed. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name INVALANS .message is an invalid answer .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. .user_action Reenter either YES or NO (or Y or N) in response to the confirmation message. .name INVSOURCE .message Invalid source of information specified: .explanation The source of information -- typically the SCT, FOLD or OTHER -- is not valid. .user_action Reenter a valid source of information on this change. .name MNETOOLONG .message library mnemonic too long; maximium length: .explanation One (or more) of the VDE$LIBRARY_DEFAULTS_MNEMONICS library mnemonic name translations are too long. .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. ! was FOLDNOTFOUND, then SPARE_7, now reincarnated as FOLDNOTFOUND with `warning' severity .severity warning .name FOLDNOTFOUND .message fold record not found for module and stream .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. .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. .severity error .name NOSCTSRC .message source file for SCT note not found .explanation VDE is not able to locate the source file for the SCT note. .user_action Respecify the command, using a file that exists. .name NOTESERR .message error from DEC Notes at .explanation VDE has encountered an error while using the notes callable interface. .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. .name UNKEPT .message unable to to kept subprocess section .explanation VDE has encountered an error while attempting to create or connect to the global section used to communicate with the kept subprocess. .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. .name BADSTATUS .message bad status returned from .explanation VDE got an unexpected error status from a system service or RTL routine (routine-name) that it called. .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. .name NOTESID .message unable to parse DEC Notes topic .explanation VDE has encountered an error while using the notes callable interface. .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. .name UNKPROJ .message unable to locate a project name .explanation VDE has encountered an error while using the notes callable interface. .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. .name LIBREQ .message specification of library mnemonic required .explanation VDE/LOCATIONS is unable to locate the target for the location translation operation. .user_action Specify the target via VDE/LOCATIONS/MNEMONIC=mnemonic. .name NOAUTOCONV .message automatic conversion to current database format disabled .explanation The VDE database does not have the proper format, and the automatic conversion of the database has been disabled. .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. .name SEECONLIB .message see the VDE CONVERT LIBRARY command .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. .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. .name BADVMSVERS .message unable to interpret OpenVMS version string: .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. .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. Only executive-mode translations in executive-mode logical name tables will be accepted. .name NOMAILSENT .message failure to send mail message to user .explanation VDE has failed in an attempt to send a mail message to the indicated user notifying that user of your action. .user_action Attempt to resolve the problem based on any other error messages included with this one, and contact VDE support for assistance. .name NONOTESENT .message note NOT posted to conference .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. .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. .name NOBASENOTE .message no base note found for replacement .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. .user_action Resolve the basic error. If unable to resolve the error, please contact the project leader or VDE support for assistance. .name INVPARAM .message invalid parameter passed to .explanation VDE has detected in internal inconsistency, namely that an illegal value has been passed as a parameter to an internal routine. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name NOCONFNAM .message no notes conference name specified in call to .explanation VDE has detected an inconsistency within an internal routine which uses the notes callable interface. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name NOTEXTSTR .message text string argument missing in call to .explanation VDE has detected an inconsistency within an internal routine which uses the notes callable interface. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name MAILERR .message error from MAIL routine .explanation VDE has encountered an error while using the VMS MAIL callable interface. .user_action Attempt to resolve the problem based on any other error messages included with this one and contact VDE support for assistance. .name NOTREQGET .message cgi request_method GET required .explanation The CGI request method as determined by the value set in REQUEST_METHOD symbol by the webserver must be GET, other forms of obtaining CGI data are not supported. .user_action Check for a valid value in the REQUEST_METHOD symbol from the current webserver. Reconfigure the current webserver to pass GET data to this image, or obtain a webserver that provides GET data. .name GETTOOBIG .message cgi get returned more than character limit .explanation The CGI get request returned a token that was larger than the application image can tolerate. .user_action Reduce the size of the name token or the value token in the CGI data to the specified limit, or less. .name GOTTOOMANY .message cgi get returned more than parameters .explanation The CGI get request returned more parameter tokens than the application image can tolerate. .user_action Reduce the number of cgi parameter tokens to the specified limit, or less. .name ADRTOOLONG .message email address too long; maximium length: .explanation One (or more) of the specified email addresses is just too long. .user_action Just shorten it. .name NOWAYOUT .message target for command output was not specified .explanation No output path was selected. Command output is normally written to the selected log file, or to users via mail messages, or via CGI output, etc. .user_action Specify where the output should be written. .name DEMENTIA .message VDE has lost its mind .explanation There is an internal error that cannot be resolved. .user_action Attempt to resolve the problem based on any other error messages included with this one, and contact VDE support for assistance. .name WHEREAMI .message VDE is unable to identify the local node .explanation VDE uses a variety of mechanisms to try to identify the local node, and has been unable to determine the local node name through any of the various checks. .user_action Install and start a supported network package, or define one of the VDE node name logical names. .name BADNODENAME .message the length of the node name is too long, or too weird .explanation VDE limits the total length of the node name, and enforces a few benign node name syntax requirements. .user_action Something is really weird with your local node name. Your job, Mr Phelps, is to find the cause and resolve the weirdness. .name PTRSYNTAX .message invalid PTR syntax .explanation The name or format specified for the PTR number is not using valid PTR syntax. .user_action The PTR name should be specified using three leading alphabetic characters PTR, a hyphen, and three sets of numeric characters delimited by hypens. Respecify the correct PTR number using the PTR-nnn-nnn-nnnn format, where n is a numeric character. ! ! Fatal messages go here. DO NOT REORDER. Very few messages should ! be of fatal severity. ! .base 2000 .severity fatal .destination both .name INTERR .message internal VDE error in .explanation VDE has detected an internal inconsistency. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name INTMEMERR .message internal memory-pool error at .explanation VDE has detected an inconsistency in its internal memory pool. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name UIDSKEW .message possible UID skew detected; check for correct UID file. .explanation VDE has detected an internal inconsistency with the UID file. .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. .name UIDSKEWCODE .message UID skew code .explanation This is the code for the particular internal inconsistency detected within the UID file. .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. .name UNKQARCLD .message internal VDE coding error .explanation VDE has detected an internal inconsistency. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name BADASSUMPTION .message bad assumption, , , .explanation VDE has detected an inconsistency in its internal memory pool. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name OFFLINE .message source code control system offline, try again later .explanation The VDE system is offline for maintenance or upgrade, please try your request again later. .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. .name FCBERR .message internal VDE FCB error in .explanation VDE has detected an internal inconsistency. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name FCBWRONG .message internal error; access failed in .explanation VDE has detected an internal inconsistency. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name INTERR_AZ .message internal VDE error in .explanation VDE has detected an internal inconsistency. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name DIEDOLDAGE .message internal consistency error in aging at .explanation VDE has detected an internal inconsistency. .user_action Please contact VDE support for assistance. Please include any information that may be useful or relevent in duplicating the problem. .name BUGPLUGVER .message incompatible statistics shareable image found .explanation VDE has activated an incompatible version of a shareable image .user_action Verify that the proper statistics shareable image has been activated. Verify that the shareable image uses a callable interface that is compatible with the current VDE version. .end