| PreviousZ | Contents\ | Index |
=VDE provides an X Windows Motif graphical user interface, as @well as a World Wide Web (WWW) interface accessable via Mosaic. .This section is under construction...V
.This section is under construction...F
9The VDE is heirarchical; the display shows, in decending <order, the VDE library, the streams within the library, the Cfacilities within the stream, and the modules within each facility.
iFigure 10-1 is an example of the facility-level display.
7Figure 10-1 VDE Motif Facility Display
1This is the VDE Motif interface for V1.5-0. This interface is Copyright 1997.
.This section is under construction...D
.This section is under construction...
<Initial VDE library selection is based on the definition of the logical name VDE$LIBRARY.=If the VDE$LIBRARY logical name is not defined, VDE searches Ffor the file Motif data file DECW$USER_INCLUDE:VDE.DAT. An example of VDE.DAT follows:
|
" # # VDE.DAT # VDE Motif configuration 5# file created by: VDE for OpenVMS VAX Version V1.5-0+# file created at: Wed Jan 4 13:32:47 1997 # values: DEFAULT SETTINGS # 1VDE.title: VDE: OpenVMS Development Environment VDE.x: 100 VDE.y: 100 VDE.remarksVisible: true AVDE.fontList: *-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1 +VDE.libraryVDE: VSC$ROOTDISK:[VMS.DBROOT] !VDE.libraryVDEDebug: VDED$:[VDE] +VDE.libraryVSC: VSC$ROOTDISK:[VMS.DBROOT] !VDE.libraryVSCDebug: VDED$:[VDE] VDE.libraryLabel: VDE.libraryList: VDE.sctNotesPrefix: SCT- VDE.sctNotesNode: NODE:: VDE*borderColor: #545445450000 # end VDE.DAT |
.This section is under construction...
<VDE provides support for multiple default library selection =lists. These selection lists allow a VDE user an easy way to Havoid memorizing all the various "interesting" libraries that Bmight be around, and they provide an easy way for a user and/or a Fsystem manager to change the default library list, and they provide a Gshorthand reference to individual libraries. Multiple lists of library Edefaults are supported and can be created for individual users, user Hgroups, all system users, all cluster users, and for eclectic groups of Fusers based on a shared logical name table. Note that each individual 2user has access to only a single list of defaults.
BThere are three parts to each default library specification---the Glibrary database device and directory specification, the display value Dshown to the user for each database, and the shorthand mnemonic for Geach library. These values are used to access the library on disk, for >the text used to display the library, and as a nickname for a !particular library, respectively.
=VDE reads and uses values from logical name search lists, or @from the VDE.DAT Motif resource file, as the default values for Fvarious library selection operations. The logical names used for this ?purpose are VDE$LIBRARY_DEFAULTS, VDE$LIBRARY_DEFAULTS_LABELS, =VDE$LIBRARY_DEFAULTS_CMS, and VDE$LIBRARY_DEFAULTS_MNEMONICS.
<VDE translates the list of default libraries from the above @logical names, or (if the logicals are absent) from the VDE.DAT Motif resource file.
BA null VDE$LIBRARY_DEFAULTS logical name definition, or a missing <VDE$LIBRARY_DEFAULTS logical name definition will cause VDE Bto access the default Motif resource file looking for the list of Ddefaults. The null definition logic allows a non-privileged user to Foverride a system-wide or group-wide logical name definition (using a Enull logical name in a searched-before logical name table) and use a Aset of default library definitions located in a user-specific or "system-wide resource file. |
:An example of the definition of the VDE$LIBRARY_DEFAULTS, ;VDE$LIBRARY_DEFAULTS_LABELS, VDE$LIBRARY_DEFAULTS_CMS, and VDE$LIBRARY_DEFAULTS_MNEMONICSlogical names follows:
|
" $$ DEFINE/JOB VDE$LIBRARY_DEFAULTS - _$ SYS$SYSDEVICE:[LIB1], - _$ XYZZY$:[LIB2], - _$ PLUGH$:[MASTERLIB] +$ DEFINE/JOB VDE$LIBRARY_DEFAULTS_LABELS - _$ "Library One", - _$ "Library Two", - _$ "Master Library" .$ DEFINE/JOB VDE$LIBRARY_DEFAULTS_MNEMONICS - _$ "L1", - _$ "L2", - _$ "ML" ($ DEFINE/JOB VDE$LIBRARY_DEFAULTS_CMS - _$ "L1CMS", - _$ "L2CMS", - _$ "MLCMS" |
FThe mnemonic names for the libraries are also accepted by the command .(non-graphical) interface SET LIBRARY command.GThe following two commands, based on the aforementioned logical names, are valid and equivalent:
|
" VDEä SET LIBRARY ML#VDEä SET LIBRARY PLUGH$:[MASTERLIB] |
.This section is under construction...
ESee the Save Options entry on the Options pulldown for information.\
.This section is under construction...
CThe following sections contain troubleshooting information. And in 'addition, see the VDE Reference Manual.
.This section is under construction...U
6VDE has a few tasks that will need to be performed at periodic intervals.
.This section is under construction...=
BThe following example shows an CMS CMS$_TRYAGNLAT interlock error.
|
" Q%VDE-I-GENDEL, generation [KITTING]STARTUP.UP3;38(38) deleted from stream DRAGON O%VDE-I-GENRETAINED, generation [KITTING]STARTUP.UP3;38(38) retained in library :%CMS-E-NOREF, error referencing VMS$:[000000.KITTING.CMS] 2-CMS-E-TRYAGNLAT, library locked; try again later 2-RMS-E-FLK, file currently locked by another user ]%VDE-E-CMSINSGEN, CMS error inserting generation 37 of element STARTUP.UP3 into class DRAGON $-CMS-E-NOREF, error referencing !AS ;%VDE-I-ROLLBACK, database transaction has been rolled back |
|
" $ Run Sys$System:SysMan -SYSMAN> DO SHOW DEVICE/FILE/NOSYSTEM VMS$ 3%SYSMAN-I-OUTPUT, command execution on node HELENA ;Files accessed on device DSA69: on 21-MAR-1997 17:50:22.21 3%SYSMAN-I-OUTPUT, command execution on node GALAXY ;Files accessed on device DSA69: on 21-MAR-1997 17:50:24.10 3%SYSMAN-I-OUTPUT, command execution on node DIMOND ;Files accessed on device DSA69: on 21-MAR-1997 17:50:25.23 $Process name PID File name 7DRAGONBLD 6081487F [VMS.KITTING.CMS]00CMS.CMS;1 3%SYSMAN-I-OUTPUT, command execution on node EDISON ;Files accessed on device DSA69: on 21-MAR-1997 17:50:27.65 2%SYSMAN-I-OUTPUT, command execution on node BRYTT ;Files accessed on device DSA69: on 21-MAR-1997 17:50:43.58 SYSMAN> ^Z $ SET PROCESS/PRIVILEGE=WORLD $ STOP/ID=6081487F |
DUnder certain circumstances, CMS 3.8-2 cannot correctly retrieve an Cindexed file stored in the CMS library. The file remains valid and +remains uncorrupted within the CMS library.
|
" .%CMS-E-NOFETCH, error fetching element [name] --CMS-E-OPENOUT, error opening !AS for output 0-CMS-E-OPENOUT, error opening [name] for output 4-RMS-E-NPK, no primary key defined for indexed file J%CMS-F-BADBUG, there is an unrecoverable bug in CMS or something it calls 7-CMS-F-RBKNOTOPEN, File passed to rollback is not open |
;If the delta files (the CMS libraries) in your VDE library Care damaged or lost due to a disk failure or other cause, you must 1recover as much of its lost contents as possible.
ySee Section 7.4.10 for details on how to perform this task.I
FThis section describes how to move the CMS library to different---and usually larger---disks.
qSee Section 7.4.11 for one procedure used to get to larger disks.Y
.This section is under construction...
:VMS_MENU displays generated VDE commands the logical name VDE$$DBG_SCRIPT is defined.f
.This section is under construction...
<Like VMS_MENU, VDE uses logical names to enable the display Fof DCL commands executed in spawned subprocesses. If the logical name is VDE$$DBG_SENDMSG;is defined, the DCL code generated by various VDE routines #will be displayed during execution.O
CProcess-level deadlocks occur infrequently, and they often involve Ehigh-traffic applications such as database backups or they involve a :VDE command that was paused via [XOFF] command.
[To resolve these deadlocks, see Section 7.3.1.:
=It is possible for Rdb processes to deadlock waiting for the Rdb "freeze" resource.
ZTo resolve this deadlock, see Section 7.3.2.G
;Rdb generates a dump file when it encounters an unexpected ;condition. Under typical circumstances, Rdb will display a -message indicating a dump is being generated.
cTo determine the cause of the dump, see Section 7.3.3.E
8The run-unit journal area is a key component of the Rdb 5processing, and allows Rdb to rollback incomplete or Gerroneous database operations. And when an unexpected condition occurs =with the run-unit journal, Rdb tends to generate a dump file.
VTo resolve these errors, see Section 7.3.4.K
FIf the run-unit journal area is entirely messing, one can potentially #see an Rdb bugcheck dump generated.
]To resolve these errors, see Section A.5.5.X
9Rdb requires the creation of a run-unit journal file. By >default, this is in the user's login device, in the directory C[RDM$RUJ], and this location can be altered using the logical name RDMS$RUJ.
aTo resolve these errors, see Section 7.3.4.2.N
4Rdb generates a dump file when the recovery process oencounters an unexpected condition. Also see Section A.5.7.1.
bTo resolve these errors, see Section 7.3.4.3.N
A recovery-process dump similar to Section A.5.7 can also be seen when the RUJ file is missing.
\To resolve these errors, see Section 7.3.4.4.]
6If the after-image journal file for your VDE database Fbecomes unavailable due to a disk failure or other cause, nobody will 9be able to use the database and VDE operations will fail.
oTo recover from these errors, see Section 7.4.8.F
ESometimes, one just runs out of storage space on the disk(s) holding the Rdb database.
}See Section A.5.9, and Section 7.8.
9Certain VSC installations have three command interfaces: VDE, VSC, and VTSC.
*As mentioned previously, the VDE, VSC and =VTSC command interfaces all use the same command syntax, all Guse the same message prefix, and all perform the same basic functions. kTable B-1 contains a high-level comparison of the differences !among the command interfaces.
| VDE | VSC | VTSC | Operation |
|---|---|---|---|
| No | Yes | No | 5 Defaults to referencing the OpenVMS VAX library |
| No | No | Yes | 9 Defaults to referencing the OpenVMS testing library |
| Yes | No | No | H Defaults to the library referenced by the VDE$LIBRARY logical name |
| Yes | No | No | @ Defaults to processing the command in the current process. |
| No | Yes | Yes | K Defaults to spawning a kept subprocess and processing commands there. |
| Yes | Yes | Yes | 7 Can operate correctly on the OpenVMS VAX library. |
| Yes | Yes | Yes | J Can SET LIBRARY and can operate correctly on user-specified private source code libraries. |
<While this document generally refers to the VDE utility and 7sometimes to VSC utility, the information here is also 6directly applicable to the VTSC utility. And in a few ?places---where information related to libraries other than the ;OpenVMS VAX source code control library is presented---the =VDE utility is specifically used. For additional information on VSC and VDE, please see the VDE Reference Manual.
GWhy are there three interfaces? Simple: each was tailored to the needs @of specific parts of the OpenVMS community. However, due to the Ecreation of various additional libraries and the common use of these Alibraries for various purposes, the use of the "stock" *VDE image has generally become preferable.
| IndexZ | Contents |