; File:  LB:[1,5]VDTABLE.TXT    Last Edit: 3-OCT-1986 10:14:39 
;
;  Use the following header line to line up columns...
;
;VD DESCPRIPTIONxxxxxxxx FILESPECxxxxxxxxxxxxxxxxxxxxxx VOLUMEIDxxxx B P V
;
 AP General applications LB:[7,111]AMAPPS.DSK;1                      X   X
 MK Mplus kit            LB:[7,54]MPLUSKIT.DSK;1        MPLUSKIT       X X
 DE DECUS dist workdisk  LB:[7,300]DECUS.DSK;1          DECUSDIST        X
 PR PRO applications     LB:[7,113]PRODIST.DSK;1        PRODIST          X
 NO NORFOLK DEVELOPMENT  LB:[7,130]NORFOLK.DSK;1        NORFOLK          X
 TO TOLEDO DEVELOPMENT   LB:[7,150]TOLEDO.DSK;1         TOLEDO           
;
;VD DESCPRIPTIONxxxxxxxx FILESPECxxxxxxxxxxxxxxxxxxxxxx VOLUMEIDxxxx B P V
;
% END OF TABLE DATA
;
; INSTRUCTIONS:
;
;  The VD table is a fixed column table of Virtual disk names and 
;  associated information.  Each column is a fixed.  Note that
;  Lines beginning with a ";" are comments and are ignored by VD.CMD.
;  Lines without a leading ";" are the actual VD information lines.
;  Use the header line to line up information in the correct order and
;  the correct field length.  A leading "%" in a line indicates the end
;  of table data.  This permits us to put all these instructions here,
;  while not degrading the runtime of VD.CMD.
;
;  VD is a two letter code for the virtual disk, such as HZ or TB.  This
;  code will be used as the pseudodevice assignment also.  For this reason,
;  make sure it does not conflict with an existing global pseudo device, or
;  some real device (like DU: or DL: or MU:).
;
;  DESCRIPTION is a 20 character free format description used to describe
;  the disk and its contents.
;
;  FILESPEC is a 30 character DEC file specification.  Include whatever
;  is necessary to access the DSK container file from any possible 
;  environment that may be encountered by users of VD.CMD.  Normally,
;  this will mean the complete file specification.
;
;  VOLUMEID is a 12 character volume name.  It is the exact same name
;  that would be used to mount the disk with the MOU command.  This means
;  that you can use "/OVR/VI" as a volume name allowing a privledged user
;  to mount a disk with a variable volume name.
;
;  B is a one character "public mounted" field.  A letter "X" denotes 
;  that the disk is public mounted on the system.  Any other letter,
;  normally a blank, denotes that the disk should be locally mounted.
;
;  P is a one character "privledged access" field.  A letter "X" denotes
;  that the disk is available to privledged users only.  This screens
;  out disks that non-privledged users need not know exist.  Any other
;  letter, normally a blank, denotes that the disk is available to anyone.
;  Note that a non-privledged user could still mount such a disk using AVD 
;  and MOU without VD.CMD.  So absolute protection must be built into the file
;  protection of the .DSK container file if desired.
; 
;  V is a one character "available" field.  A letter "X" denotes that the
;  disk is "loaded" and available for use.  Any other letter, normally a
;  blank, denotes that the disk is "unloaded" and not available for access.
;  This is used when a disk is to be made unavailable to all users while
;  it is unloaded to tape (and not on the system) or when it is undergoing
;  maintenance by the system manager.
;
;  
;  Column alignment is IMPORTANT.  There is one space between each column.
;  DO NOT user TABs, only spaces.  TAB will not result in correct alignment.
;  Lower case is converted to upper case where required, so you may use
;  both upper and lower case where desired.
;