       INSTALLATION INSTRUCTIONS      DM Version 7.1A      (Directory Management Utility)     April, 1987    Installation  F 0.  You must select a system default Editor, Viewer, and Printer.  (A D "Viewer" is something with the functions of an editor, but which is , read-only [i.e., will not change the file]).  E      oo  You will note that we use a TPU-based editor which we call   "WPE".  H      oo  The "Viewer" can actually be any editor (thus eliminating the E difference).  We use a read-only version of WPE called "MORE".  TYPE  ' would also work, but isn't too elegant.   F      oo  If "PRINT" works at your site, you won't have to change the  default printer.  J      oo  There are two ways to change the defaults - you may put them in F DM.COM or DM.FOR; I recommend putting them in DM.FOR, and this is the  procedure outlined below.   F      oo  Before you adapt this to your site, please read the section 0 "Integration of Editors" later in this document.   1.  Edit the following files:   E      oo  DM.COM - Change the line indicated "LOCAL" to point to the  , directory where you will place these files.   G      oo  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).   C      oo  DM.FOR - At the start of the program (there are a lot of  I comments before you get there), edit the information for Default_Editor,  A Default_Viewer, and Default_Print_Command to the values you have  B selected.  Note that you probably have to change the sizes of the + Character variables with these names, also.   C 2.  Do @DM_Install.  This will compile DM.FOR and link a new image.   G 3.  Place the files in the appropriate place.  The files necessary for   running DM are: 
      DM.COM   0      DM.EXE  (This may be installed if you wish)2      DM$ATPRINT.COM  (Attached Printer Controller)1      DM.HLB  (this is usually placed in SYS$HELP) #      DM_USER_DOC.TXT  (in SYS$HELP)   E 4.  Point appropriate system symbols.  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  F 5.  You can check that you did it correctly by typing DM.  Then, when D the DM screen comes up, type <Gold> A (or PF1 followed by A).  This 3 should show you the default settings you have made.   G 6.  You will probably want to publish the user's guide.  It is present  G in three forms: a .WPL file if you have WPS+, a .LN03 file if you have  ! an LN03 printer, and a .TXT file.   E 7.  If you wish to add help to your help library, the file DM.HLP is  
 available.    % Installing 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 viewer4      DM$Print_Command :== your default print command    3.  Follow steps 3 thru 7 above.     Integration with Editors  J DM considers WPE and MORE to be "special" symbols for Editor and Viewer.  B If these are the default values, DM will use callable TPU for its G interface.  If you use a TPU-based editor on your system, you will not ,I have to change these symbols.  However, you must have the logical symbol b TPUSECINI defined correctly:  ? If TPUSECINI is undefined	DM uses the default interface to TPU  %                                 (EVE)E  @ TPUSECINI defined as EDTSECINI	DM uses the EDT interface to TPU.  * TPUSECINI defined for WPE	(Something like I                                 DISK:[DIRECTORY]WPE.TPU$SECTION)  If the tG                                 logical contains the characters 'WPE', hH                                 DM assumes that the interface is really ;                                 'WPE' (contained with this n.                                 distribution).  = TPUSECINI defined otherwise	DM uses your defined .TPU$SECTIONl  ; MORE is always set up for read-only editing in these cases.d  I If these options don't suit, you may either use names other than WPE and i9 MORE, or edit the logic in ENVOKE.FOR to meet your needs.      Integration with VMS Mail   E Pressing <Gold> M runs VMS Mail (VAXMail) in the DM subprocess.  The r@ action taken depends on the definition of the logical MAIL$EDIT.  I If MAIL$EDIT is defined (as anything), DM initializes for callable TPU.  fF If MAIL$EDIT is undefined, DM initializes for the user's default mail  mode.   I The comand passed to the subprocess is MAIL.  Since symbols are known to  B the subprocess, this command may equate to anything you wish (for  instance, MAIL/EDIT).m     Integration with SDI  @ If you install both DM and SD on your system, DM will integrate F 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.r     Re-Compiling  G There are command procedures for re-compiling and linking the whole of YA DM.  There are separate files for compiling with and without the aF limits-checking.  The version submitted to DECUS was compiled without 	 checking:s;      CPL and CPL_CHECK         compile/assemble everything.I'      DM_LINK                   links DMo5      DOALL and DOALL_CHECK     compile and then link.      Additional Information  I See the files DM_USER_DOC and DM_PROGRAMMER_DOC for details of usage and   adding functions.l    
 Test Files  6 In the .DM$SD directory, there are several .DIR files:  D      A_JUST_LONGENOUGH.DIR and A_LONGER_DIRECTORY_NAME_TEST.DIR are &      there to check the DM * function.  I      A_FAKE.DIR and B_FAKE.DIR are there to check the capabilities of DM gE      to detect and handle .DIR files which really aren't directories.a  E      TEST_FILES.DIR actually contains some files we used for testing.     
 Known Bugs     Attribution=  E Directory Manager was initially submitted in January 1983 by John C. oB Hayre, Texas Instruments (later with Veeco Integrated Automation,  Dallas).  D Additional extensive improvements and submissions were made by Rich A Gregory, Pharmaceutical Research Associates, Charlottesville, VA.l  G The version spun-off in 1986 (now Version 7.1A), which incorporated an mF All-In-1-like user interface and use of the SMG$ utilities for screen B management is by Dale E. Coy, Los Alamos National Laboratory, Los   Alamos, NM 87545. (505) 667-7159  