Manager examples

This document provides an example of an EDA installation for a group of students. It is intended as an aid for EDA administrators, but remember, it is an example.

The examples are from a VAX/VMS machine, therefore you will need to adapt file names to your system and translate some of the terms into your own systems way of describing these things.

For non VAX users: File names are of the form:

node::disk:[directory]name.extension

A user sees file names of the form:

                     mytext.doc
      or             [MYDIR.TEXTS]mytext.doc
      or sometimes   SAVE:[MYDIR.TEXTS]mytext.doc
      or             SAV:mytext.doc

<disk> is nearly always some logical name (translated by the system into a physical name) defined either by the system for all users, a group of users or by a single user.

For this group I define a logical name EDALIB pointing to the place where essential files are to be found for this group; in fact the system component (sysenv) points to a file EDALIB:PROFILE.EDA. Therefore when changing the location or having other locations for other users I need not recompile, but only redefine the logical name which might be different for different groups of users

By the way this is the only reference to a file within the EDA code. In my example EDALIB translates into PCK:[EDA.edamanager], where I keep among other files PROFILE.EDA, which is the EDA profile file.

  1.  $EDAPRO$AT         profile.eda
  2.  USF$=SDISK:[eda.edamanager]userlist.eda
  3.  MAP=PCK:[EDA.edamanager]MAPLIB.EDA
  4.  UCF=PCK:[eda.log]
  5.  MSG$pck:[eda.edamanager]news.file
  6.  //

  and a userlist.eda file:

  1.  EDA       ALZ     PCK:[EDA.edamanager]INIT.EDA_EDAXX
  2.  HORBER    SLA     PCK:[EDA.edamanager]INIT.EDA
  3.  SCHNEIDER SL  SPO3PCK:[EDA.edamanager]spo3.EDA
  4.  GALLAND   SL  SPO3PCK:[EDA.edamanager]spo3.EDA
  <more>

The first file contains user information, as well as 3 global records (MAP= etc). i.e. these are defined for all users, regardless their second profile file. No EGL$ is present, therefore all records are copied first to the active profile.

Users SCHNEIDER and GALLAND are in a group called SPO3, i.e. a student group. The file name pck:[eda.edamanager]spo3.eda points to the group profile for these users; the contents of this file are:

  1.  $EDAPRO$
  2.  DIR=SHARE   LPCK:[EDA.STUDAT]EDAEDA.EDR
  3.  DIR=SPO3    LPCK:[EDA.STUDAT]SPO3.EDR
  4.  DIR=USER    USYS$LOGIN:EDAEDA.EDR
  4.  DIP=USER    USYS$LOGIN:EDAEDA.EDR
  5.  MAN=pck:[eda.edaman]
  6.  TAR=pck:[eda.edaman]TARC0.TAR
  7.  MAC=pck:[eda.edaman]macros.library
  8.  BEF=.blank
  9.  BEF=.no fill
  10. BEF=.tp 15
  11. AFT=.blank
  12. AFT=.justify
  13. //

This second file contains specific information for that group, namely three WA directory references (the first two are libraries, the third is a user directory, i.e. may or may not exist(depending whether the user did a PUT or not. The following three records point to information libraries/locations. The MAN= points to a directory only, e.g. whenever a user issues say MAN PLOT; EDA will look for a file named PLOT.DAT [Non VAX:users .DAT is the default file extension here] and show its contents. TAR=/MAC= point to eda text-archives. Finally the BEF/AFTs contain RUNOFF commands, i.e. the VAX text formatter.