




DM Installation Instructions


Directory Management Utility


DM Version 8.0A


October, 1988


** If you are using VMS Version 5.x **

DM Version 8.0 is the first version which works correctly with VMS V5.0.  
Changes to SMG$ caused some problems (particularly with the "tree" 
function) which have been corrected.


** If you are using VMS Version 4.x **

DM Version 8.0 has been thoroughly tested on VMS V5.0.  The .EXE file 
supplied was linked on VMS V5.0 - but you can use DM_LINK.COM to re-link 
for VMS V4.x.  Then re-link under VMS V5.0 when you upgrade VMS.

If you have access to DM Version 7.3A, it is recommended that you 
continue to use it until you upgrade to VMS V5.0, at which time you 
should install DM Version 8.0.  Although our testing did not show any 
problems using DM V8.0 with VMS V4.x, you should be aware that this 
testing was less thorough than with VMS V5.0.


Installation using Defaults

If you use a TPU-based editor (EVE, WPE, etc.), and if the command PRINT 
is appropriate for the default printer on your system, you should not 
need to do any customization to DM.  You may wish to read the section 
"Integration with Editors".

To install non-customized DM:

     oo  Edit DM.COM - Change the line indicated "LOCAL" to point to the 
directory where you will place the file DM.EXE.

     oo  Follow Steps 3 through 7 in Installation (with FORTRAN Compiler) 
below.


Installation (with FORTRAN Compiler)

0.  You must select a system default Editor, Viewer, and Printer.  (A 
"Viewer" is something with the functions of an editor, but which is 
read-only [i.e., will not change the file]).

     oo  The as-built default editor is "TPU".  We use a TPU-based editor 
which we call "WPE", but any TPU-based editor (such as EVE) will work 
with this default.  If that is satisfactory, you won't have to change 
this default.

     oo  The as-build default "Viewer" is "TPU".  The "Viewer" can 
actually be any editor (thus eliminating the difference).  We use a 
read-only version of WPE called "MORE".  TYPE would also work, but isn't 
too elegant.  If you are using WPE (or EDW), the editor will be called 
correctly.  Other TPU-based editors (including the EVE editor) will be 
called with the /READ_ONLY qualifier.  If that is satisfactory, you 
won't have to change this default.

     oo  If "PRINT" works at your site, you won't have to change the 
default printer.

     oo  There are two ways to change the defaults (if necessary) - you 
may put them in DM.COM or DM.FOR; I recommend putting them in DM.FOR, 
and this is the procedure outlined below.

     oo  Before you adapt this to your site, please read the section 
"Integration of Editors" later in this document.

1.  Edit the following files:

     oo  DM.COM - Change the line indicated "LOCAL" to point to the 
directory where you will place these files. 

     oo  COMMON.DAT - Edit the information marked "LOCAL" to indicate 
where you will put the DM Help Library (if it will not be 
SYS$HELP:DM.HLB).

     oo  DM.FOR - At the start of the program (there are a lot of 
comments before you get there), edit the information for Default_Editor, 
Default_Viewer, and Default_Print_Command to the values you have 
selected.  Note that you probably have to change the sizes of the 
Character variables with these names, also.

2.  Do @DM_Install.  This will compile DM.FOR and link a new image.

3.  Place the files in the appropriate place.  The files necessary for 
running DM are:
     DM.COM  
     DM.EXE  (This may be installed if you wish)
     DM$ATPRINT.COM  (Attached Printer Controller)
     DM.HLB  (this is usually placed in SYS$HELP)
     DM_USER_DOC.TXT  (in SYS$HELP)

4.  Point appropriate system symbols.  This is usually done in your 
system-wide login procedure.  Note that these are both .COM files.  On 
our system, we use the following:
     DM	      :==  @Sys$Utils:[DM$SD]DM
     DM$ATP   :==  @Sys$Utils:[DM$SD]DM$ATPRINT

5.  You can check that you did it correctly by typing DM.  Then, when 
the DM screen comes up, type <Gold> A (or PF1 followed by A).  This 
should show you the default settings you have made.

6.  You will probably want to publish the user's guide.  It is present 
in three forms: a .WPL file if you have WPS+, a .LN03 file if you have 
an LN03 printer, and a .TXT file.

7.  If you wish to add help to your help library, the file DM.HLP is 
available.


Installing (customized) without a FORTRAN compiler

1.  Edit DM.COM as indicated in Step 1 above.

2.  Either in your SYLOGIN.COM (best) or in DM.COM, define (if 
necessary):
     DM$Editor :== your editor
     DM$Viewer :== your viewer
     DM$Print_Command :== your default print command

3.  Follow steps 3 thru 7 above.


Integration with Editors

DM considers TPU, WPE, EDW, and MORE to be "special" symbols for Editor 
and Viewer.  If these are the default values, DM will use callable TPU 
for its interface.  If you use a TPU-based editor on your system, you 
will not have to change these symbols.  However, you must have the 
logical symbol TPU$SECTION defined correctly:

If TPU$SECTION is undefined	  DM uses the default interface to TPU 
                                  (EVE).

TPU$SECTION defined for WPE	  If the logical contains the characters 
                                  'WPE' or 'EDW', DM assumes that the 
                                  interface is really 'WPE' (contained 
                                  with this distribution).

TPU$SECTION defined otherwise	  DM uses your defined .TPU$SECTION

 The logic for "Editor" is:
   If "Editor" = TPU or WPE or EDW then
     Edit/TPU
   Else
     Spawn 'Editor'
   EndIf

 The logic for "Viewer" is:
   If "Viewer" = TPU or MORE then
     If TPU$SECTION = WPE or EDW then
	Edit/TPU/NoJournal 
     Else
	Edit/TPU/Read_Only
     EndIf
   Else
     Spawn 'Viewer'
   EndIf

If these options don't suit, you may either use names other than those 
shown, or edit the logic in ENVOKE.FOR to meet your needs.


Integration with VMS Mail

Pressing <Gold> M runs VMS Mail (VAXMail) in the DM subprocess.  The 
action taken depends on the definition of the logical MAIL$EDIT.

Using VMS V5.0, MAIL$EDIT is not normally defined - therefore, the user 
has full choice of mail editor.

If MAIL$EDIT is defined (as anything), DM requires that it be a callable 
editor.  If the logical symbol MAIL$EDIT does not contain the characters 
'CALLABLE', DM defines MAIL$EDIT in the subprocess to be 'CALLABLE_TPU'.

The comand passed to the subprocess is MAIL.  Since symbols are known to 
the subprocess, this command may equate to anything you wish (for 
instance, MAIL/EDIT=(SEND,REPLY=EXTRACT).


Integration with SD

If you install both DM and SD on your system, DM will integrate 
automatically with SD.  You do not have to take any special actions.  
Exiting from DM will update SD's stack, so you will not get the 
"Unexpected Stack Environment" message from SD.


Re-Compiling

There are command procedures for re-compiling and linking the whole of 
DM.  There are separate files for compiling with and without the 
limits-checking.  The version submitted to DECUS was compiled without 
checking:
     CPL and CPL_CHECK         compile/assemble everything.
     DM_LINK                   links DM
     DOALL and DOALL_CHECK     compile and then link.


Additional Information

See the files DM_USER_DOC and DM_PROGRAMMER_DOC for details of usage and 
adding functions.


New Features in V7.3A and 8.0A

The <Gold>-A menu in DM now provides for saving the user's default 
Editor, Viewer, Print_Command, and Printer_Type in 
SYS$LOGIN:DM_DEFAULTS.COM.  This file (if it exists) is used by DM to 
establish defaults.  It is a fixed-field file, and should not normally 
be edited.  DM first looks for DM_DEFAULTS.COM.  If that fails, DM 
examines defined symbols.

Tree print now uses DEC's line-drawing character set if the printer 
supports it.  You may add additional printer types in DM_TREE.FOR, if 
you have other requirements.

In addition to correcting for "features" of VMS 5.0, DM V8.0 adds the 
ability to efficiently use any TPU-based editor.  It is particularly 
well integrated with the WPE editor.


Highlighting

The DM Main and Tree displays normally highlight (bold) entries as your 
cursor moves through the display.  In certain circumstances, you may 
wish to disable this feature.  You might want to do this if your 
terminals do not support highlighting, or if you are using a slow baud 
rate (highlighting does take time).  To eliminate dynamic highlighting, 
define a symbol:

     $ DM$HIGHLIGHT :== N


Test Files

In the .DM$SD directory, there are several .DIR files:

     A_JUST_LONGENOUGH.DIR and A_LONGER_DIRECTORY_NAME_TEST.DIR are 
     there to check the DM * function.

     A_FAKE.DIR and B_FAKE.DIR are there to check the capabilities of DM 
     to detect and handle .DIR files which really aren't directories.

     TEST_FILES.DIR actually contains some files we used for testing.


Feature for System Managers

The <Gold> D (new device) has an additional option which is useful for 
system managers.

At the "Enter New Device or Directory" prompt, editing the supplied 
response to @Username will place you in the login directory for the 
specified user.  This facility of DM is not documented in the Users' 
Guide.

The capability is normally implemented by accessing SYSUAF.DAT, and 
therefore only certain users will be able to use it.

There is an optional alternative provided - to use the file 
SYS$SYSTEM:SYSUAF.LIS, which can be created using the LIST/BRIEF command 
from the Authorize utility.  The file will usually not have world read 
access.  If you want normal users to have access to the @ facility of 
DM, you can change the protection on the file, edit it to delete 
critical entries, etc.

To implement this alternative, locate (in STACK.FOR) the line "Call 
DM_UserName_UAF ()" and exchange it for the adjacent line, which is 
"Call DM_UserName_List ()".  Then rebuild DM.  


Known Bugs


Attribution

Directory Manager was initially submitted in January 1983 by John C. 
Hayre, Texas Instruments (later with Veeco Integrated Automation, 
Dallas).

Additional extensive improvements and submissions were made by Rich 
Gregory, Pharmaceutical Research Associates, Charlottesville, VA.

The version spun-off in 1986 (now Version 8.0A), which incorporated an 
All-In-1-like user interface and use of the SMG$ utilities for screen 
management is by Dale E. Coy, Los Alamos National Laboratory, Los 
Alamos, NM 87545. (505) 667-3270/665-0145


