From: K.S. B. <ks....@fn...> - 2005-08-04 20:09:47
|
On Thu, 2005-08-04 at 14:51 -0500, Nancy Anthracite wrote: > I would love to jump in here, but , as you know, I usually do my own > thing > when I set up my machine so let me give this a whirl: > > The actual location of the standard routines that are VistA > is /usr/local/FOIAVistA and that there are nothing but links to > files > in /usr/local/OpenVistA that point to the source > files /usr/local/FOIAVistA. > > gtm is up in /usr/local/gtm_V5.0-000 and it acts like it is > in /usr/local/gtm > because of links. [KSB] Correct. With the use of links, we can create procedures and scripts that count on VistA and GT.M being in a standard place (/usr/local/OpenVistA and /usr/local/gtm) and continue to work when new versions replace old ones - all one would do is change /usr/local/OpenVistA and /usr/local/gtm to point to the new directories. > > I am assuming that in /home/vista/ r and o are the users local > routines that > they may have written or are testing, and that maybe g contains that > users > globals, which are "the" only globals in this instance, which is the > data and > supporting configuration information, not global variables like > programmers > often think is what globals must be. [KSB] Yes, /home/vista/r and /home/vista/o are intended for the users local routines. /home/vista/g/mumps.dat is the database file for the global variables (of course, all MUMPS programmers think of global variables are residing in a database, but what C programmers call global variables are what M programmers call local variables). > > All of these links were put there to make the scripts run uniformly > from > release to release. [KSB] Exactly. > > How did I do? Did I finally have an email about this without saying > something > wrong? [KSB] What do you mean "finally"? You almost always get it right! -- Bhaskar |