SD -- INSTALLATION INSTRUCTIONS Set/Show Default Utility SD Version 5.0A October, 1988 NOTE: VMS Versions 4.x and 5.0 The supplied SDMAIN.EXE was linked under VMS V5.0, and will not run under VMS 4.x. If you are still running VMS V4.x, use the procedure LINK_SD.COM to re-link SD. When you move to VMS V5.0, use the same procedure to again re-link SD. No code changes are necessary. Installation using a FORTRAN compiler 1. Edit the following file to fit your site: oo SD_COMMON.DAT - The required changes are parameter statements at the top of the file, and are delimited by lines "LOCAL" and "END LOCAL". Local decisions are: (a). The location of the help library, and (b). Definition of SD_TRANS, which can be set up to encourage (force?) people to use logical names for devices. Device logical names in SD_TRANS will not be translated into their physical names. A prototype and explanation are in the file. 2. Do @REBUILD_SD. This will rebuild SD. A new SDMAIN.EXE will be created. 3. Place the files in the appropriate place. The files necessary for running SD are: SDMAIN.EXE - this file should be put in SYSEXE. NOTE: It is logical to re-name this file SD.EXE. It may be installed if you wish. If you have skipped steps 1 and 2, AND if you are still using VMS V4.x, execute the file LINK_SD.COM to re-link before you move this file. SD.HLB (this is usually placed in SYS$HELP) SD_USER_DOC.TXT (in SYS$HELP) The file INSTALL_SD.COM is the way we do it. Of course, you will have to edit INSTALL_SD.COM for your site. 4. Point the system symbol SD. On our system, we use the following: SD :== $SD 5. You can check that you did it correctly by typing SD. The name of your current directory should be displayed. 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 which prints nicely on an LN03 printer, and a .TXT file. 7. If you wish to add help to your help library, the file SD.HLP is available. 8 (Purely optional) Predefined directories (for SD n) can be defined in several ways: a. In the System-wide Login Command File (same for all users) b. In each users' Login Command File (unique for each user) c. Manually, by the user Note that definitions in (c) override definitions in (b), and (b) overrides (a). Installing without a FORTRAN compiler Follow steps 3 thru 8 above. You must put the files where indicated, and you will not be able to change the SD_TRANS parameters, but SD should still work correctly. Re-Compiling There are command procedures for re-compiling and linking the whole of SD: BUILD_SD.COM (Full Build) INSTALL_SD.COM (Install Prototype) LINK_SD.COM REBUILD_SD.COM (Partial Build) Feature for System Managers Typing SD @Username will place you in the login directory for the specified user. This facility of SD 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 SD, you can change the protection on the file, edit it to delete critical entries, etc. To implement this alternative, locate (in SDSUBS.FOR) the line "Call SD_UserName_UAF (AtStat)" and exchange it for the adjacent line, which is "Call SD_UserName_List (AtStat)". Then rebuild SD. New Features in V4.4A and V5.0A The -A menu in DM (but not in SD) 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 SD (in the Print Tree section) to establish defaults. It is a fixed-field file, and should not normally be edited. Tree print now uses DEC's line-drawing character set if the printer supports it. You may add additional printer types in SDTREE.FOR, if you have other requirements. V5.0A corrects SD to conform to the way VMS 5.0 SMG$ functions differ from the previous implementation. One "bug fix" is also included. Documentation You should read SD_USER_DOC for a description of SD's functions. Other notes: You can go up to the [000000] level if you have SETPRV. If you want to allow any user to go there (or add other privs), it's easy to do following the model in SD.FOR. The incremental version number and link date of SD are available using the command SD $ What's in this directory: In addition to AAAREADME.DOC, you will find in this Directory the following: Documentation: SD_USER_DOC (User documentation) SD_INSTALLER_DOC (This file) (These are available in .TXT, in .WPL if you have the WPS+ editor on your system, and in .LN03 which prints nicely on an LN03 printer. The LN03 files are formatted for 7" x 9" binders.) SD.HLP (Source for Help Library) SD.HLB Command Files: BUILD_SD.COM (Full Build) INSTALL_SD.COM (Install Prototype) LINK_SD.COM REBUILD_SD.COM (Partial Build) Sources: Common block definitions (include files): SD_COMMON.DAT SD_SMG.DAT Code Source (with associated .OBJ) SDMain.FOR SD_Common.FOR (Block Data Subroutine) SD.FOR SDTree.FOR SDTree_Subs.FOR SDSubs.FOR IS_Dir.FOR (Checks .DIR files) SDMacros.MAR Read_Header.MAR Known Bugs Attribution This is a revision to the NSWC-SD package which has appeared on previous VAX SIG Symposium tapes. It provides enhancements to the older SD packages. SD was initially submitted in 1984 (we think) by Alan L. Zirkle, Naval Surface Weapons Center, and had been improved (and submitted to DECUS) by him since that time. This version is a spin-off from his submission to the Spring 1986 Symposium Tape, done by Dale E. Coy, Los Alamos National Laboratory. Why another SD? Previous versions of SD have used DCL for some portion of the task. This modification is entirely in FORTRAN and MACRO, giving about 25% speed improvement. What's new? The SD Stack is now 20 directories. Most exciting is the user may interactively select a "destination" directory from either the Stack or Tree displays. Comments, suggestions, etc. are welcome. Bug fix requests will also be considered. Dale E. Coy Los Alamos National Laboratory CRM-2, MS/B270, PO Box 1663 Los Alamos, NM 87545 (505) 667-3270 or 665-0145