VDE
VDE
Reference Manual


Previous Contents Index

This example verifies all generations created since last midnight in all facilities. Because the /RECOVER qualifier is specified, VDE recovers all missing generations from their queued-replacement staging areas and inserts them into their CMS libraries. In this example, generation 2 of module B.REQ was successfully recovered from its staging directory. However, generation 1 of C.B32 could not be recovered because no staging area exists for the replacement that created that generation. This example illustrates a typical recovery operation after the disk containing your VDE library has been restored from back-up tapes and the VDE database has been recovered from its back-up and journal files.
#3

VDE„ VERIFY GENERATION [SYS]FOO.MAR/GENERATION=10A2/RECOVER=DISK$:[MYDIR]
%VDE-I-ELENOTFOUNDCMS, element [SYS]FOO.MAR;12(10A2) not found in CMS library
%VDE-I-GENRECOVERED, generation [SYS]FOO.MAR;12(10A2) successfully recovered
from DISK$:[MYDIR]FOO.MAR;
 
Summary statistics:
   Number of generations successfully verified:       0
   Number of CMS elements not found:                  1
   Number of CMS generations not found:               0
   Total number of generations scanned:               1
   Number of generations recovered:                   1
   Number of generations not recovered:               0
 
VDE„
      

This example verifies generation 10A2 of module FOO.MAR in facility SYS. Because that generation is missing from the CMS library in this example, VDE recovers its text from file DISK$:[MYDIR]FOO.MAR and inserts it into the CMS library for facility SYS. This example thus illustrates how you can recover a specific missing generation when the generation is not found in any VDE staging area but happens to be available elsewhere.


WAIT BUILD_JOB

Waits for an existing build job to complete.

Format

WAIT BUILD_JOB [stream-name]


Parameter

stream-name

The name of a development stream. VDE waits for the most recent build job in this stream to complete. If you omit the stream-name parameter, VDE waits for the completion of the most recent build job in the default stream.

Description

The WAIT BUILD_JOB command waits for the most recently created build job in the specified stream to complete. The command checks the status of the build job in the database every 15 seconds until the build job is marked as completed. A build job is marked as completed in any of the following circumstances:

Use the WAIT BUILD_JOB command in batch jobs that must wait for the completion of a build job before another task can begin, for example, before printing the status of the job.

The WAIT BUILD_JOB command stops waiting automatically if the build job does not complete within a certain interval. You can specify that interval with the /TIMEOUT qualifier. The default timeout interval is 12 hours.

If you use the WAIT BUILD_JOB command interactively, you can abort the wait by pressing CTRL/C. Expect a delay of up to 15 seconds before CTRL/C takes effect.


Qualifiers

/LOG (default)

/NOLOG

Controls whether log messages are printed when VDE begins and ends the waiting period. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. The log message at the beginning of the waiting period indicates what build job VDE is waiting for. The log message at the end of the wait indicates that the build job completed or that the wait exceeded the timeout interval.

/TIMEOUT=time-interval

Specifies the timeout interval for the wait. If the build job does not complete in this interval, VDE ends the waiting period and prints a log message to that effect. Specify the timeout interval using the following syntax to denote the number of hours, minutes, and seconds in the interval:

hh:mm:ss.ss 

If this qualifier is not specified, the command ends after 12 hours.


Examples

#1

VDE„ WAIT BUILD_JOB
Waiting until build job 34 for stream MAIN completes...
Build job 34 for stream MAIN has successfully completed
VDE„
      

This command waits for the most recent build job for the default stream to complete, in this case, build job 34 for stream MAIN. The second log message, printed after the job finished, indicates that the job completed successfully.

#2

VDE„ WAIT BUILD_JOB/TIMEOUT=5:00 V5.3
Waiting until build job 33 for stream V5.3 completes...
Timeout interval has expired (interval:    0 00:05:00.00)
VDE„
      

This command waits for the most recent build job for stream V5.3. The timeout interval is 5 minutes. In this case, the timeout interval expired before the build job completed, as indicated by the second log message.


Appendix A
Associated Logical Names

This appendix describes various logical names used within the VDE package. A partial list of these logical names is present in Table A-1.

Note

This interface is under development and is subject to change. Please contact VDE support for further information.)

This logical name is write-only; VDE does not translate it and users should not modify the contents.)

This logical is intended for use within command procedures calling VDE. This logical name is write-only; VDE does not translate it and users should not modify the contents.) not translate it and users should not modify the contents. For further information on prompting for SCT notes, see the documentation on the REPLACE command.)
Table A-1 Logical Names
Logical Name Description
VDE$LIBRARY
  References the device and directory of a VDE library.
VDE$LIBRARY_DEFAULTS
  A search list logical name that contains zero or more VDE libraries available by default. Used in conjunction with VDE$LIBRARY_DEFAULTS_LABELS and VDE$LIBRARY_DEFAULTS_MNEMONICS, and the number of translations must match the number of translations present in VDE$LIBRARY_DEFAULTS_LABELS and VDE$LIBRARY_DEFAULTS_MNEMONICS.

If not defined or defined without translations, an attempt is made to access a list of default library labels located in the X Windows resource file.

VDE$LIBRARY_DEFAULTS_LABELS
  A search list logical name that contains zero or more labels for VDE libraries. Used in conjunction with VDE$LIBRARY_DEFAULTS, and the number of translations must match the number of translations present in VDE$LIBRARY_DEFAULTS.

If not defined or defined without translations, an attempt is made to access a list of default library labels in the X Windows resource file.

To avoid user confusion, one should configure the remark in each library to match the associated translation(s) of the VDE$LIBRARY_DEFAULTS_LABELS logical name. See the SET LIBRARY/REMARK command.

VDE$LIBRARY_DEFAULTS_CMS
  A search list logical name that contains zero or more root locations for the VDE CMS libraries. This logical is used in conjunction with the other VDE$LIBRARY_DEFAULTS logical names, and the number of translations must match the number of translations present in VDE$LIBRARY_DEFAULTS.

If not defined or defined without translations, an attempt is made to access a list of default library labels in the X Windows resource file.

This logical is used by a VDE manager to provide the location of the CMS libraries to programs and procedures associated with VDE, but this logical name is not used within VDE.

VDE$LIBRARY_DEFAULTS_MNEMONICS
  A search list logical name that contains zero or more mnemomic names for VDE libraries. Can be used in the SET LIBRARY command. This logical name is used in conjunction with VDE$LIBRARY_DEFAULTS, and the number of translations must match the number of translations present in VDE$LIBRARY_DEFAULTS.

Mnemonics are not utilitized under the X Windows interfaces.

To avoid user confusion, one should configure the name in each library to match the associated translation(s) of the VDE$LIBRARY_DEFAULTS_MNEMONICS logical name. See the SET LIBRARY/NAME command.

VDE$LIBRARY_LABEL
  Contains the remark associated with the last VDE library accessed. This logical is intended for use within command procedures calling VDE.

To avoid user confusion, one should configure the remark in each library to match the associated translation(s) of the VDE$LIBRARY_DEFAULTS_LABELS logical name. See the SET LIBRARY/REMARK command.

VDE$LIBRARY_MNEMONIC
  Contains the mnemonic, when known, or the specification associated with the last VDE library accessed.

To avoid user confusion, one should configure the name in each library to match the associated translation(s) of the VDE$LIBRARY_DEFAULTS_MNEMONICS logical name. See the SET LIBRARY/NAME command.

VDE$NOTES_LIBRARY
  When defined, the translation of this logical name is used to override the default SCT notes conference specification of NOTES$LIBRARY:.NOTE. Among the obvious use in relocating the SCT notes conferences to a remote node or remote cluster, this logical name can be defined as 0::NOTES$LIBRARY:.NOTE to force all SCT note entries to made via the notes server process(es). Only one notes conference default specification is possible per node.
VDE$OFFLINE
  When defined, disables VDE. The translation is assumed to contain the reason why the VDE environment is offline, and is displayed to all VDE users. Only fully-privileged definitions of this logical name are accepted and processed.
VDE$REPLACE_DEFAULT
  If defined, this logical contains "EDIT", "FILE", or "NOTE", and selects the default processing for the location of the SCT note. If undefined or defined to an invalid value, VDE defaults to "EDIT", as indicated by the brackets in the "Enter file to load into SCT: (filename/[EDIT]/NOTE)" prompt. The brackets will indicate the default for the prompt.
VDE$SCRATCH
  A logical name that translates into the directory specification for the VDE scratch directory. If this logical name is not specified, a [.VDE$SCRATCH] subdirectory will be created underneath the SYS$SCRATCH: directory, and the logical name VDE$SCRATCH will be defined to reference it.
VDE$TEMPLATES
  References the device and directory that contains the predefined SCT template files SCT-NEW.TEMPLATE, and SCT-BUG.TEMPLATE. This logical name is used during the REPLACE command. This logical name definition is optional---no default SCT template is available if this logical name is not defined, or if the two template files are not located. In either case, the user is placed in the chosen text editor and must include the appropriate template file manually.
VDE$WHEREIS_BACKUPS_AFTER_IMAGE
  Output from the VDE/WHEREIS command. Allows a command procedure to locate the after-image BACKUP files.
VDE$WHEREIS_BACKUPS_ARCHIVE
  Output from the VDE/WHEREIS command. Allows a command procedure to locate the database backup archival directory.
VDE$WHEREIS_BACKUPS_CURRENT
  Output from the VDE/WHEREIS command. Allows a command procedure to locate the database backup directory containing the most recent backups.
VDE$WHEREIS_BACKUP_FULL
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the filename used for the full backups.
VDE$WHEREIS_BACKUP_INCR
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the filename used for incremental backups.
VDE$WHEREIS_BUILD
  Output from the VDE/WHEREIS command. This logical is not fully implemented.
VDE$WHEREIS_CMS
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the root specification of the CMS library.
VDE$WHEREIS_DATABASE
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the specification of the directory containing the root database file.
VDE$WHEREIS_LABEL
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the text label associated with a particular database.
VDE$WHEREIS_MNEMONIC
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the mnemonic name associated with a particular database.
VDE$WHEREIS_STAGING
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the root specification of the staging area for a VDE database.
VDE$WHEREIS_STATISTICS
  Output from the VDE/WHEREIS command. Allows a command procedure to retrieve the specification of the statistics database file for a VDE database.


Previous Next Contents Index