        Skeletal instructions for using the contents of this tar file
		(for defgb 2.9.  WJS.  Apr 97)

	1)  All files are text.

	2)  The "switch" documentation discusses compilation options.
The "param1" documentation discusses run-time options.  Some are duplicated,
so they can be set either way.
	    In particular, if your node does not have the JGOFS "jdb"
routines (or the http routines they call), you may need to set the
READ_OBJECTS compilation switch to FALSE.  The jdb routines are normally
found in the library file /jgofs_root/lib/jgofs.a.  (On IBM & HP systems,
the jdbxxx_ routines are named jdbxxx in jgofs.a.  This will require
attention of some kind if you need to use the READ_OBJECTS feature)

	3)  The makefile should be a useful template for building a defgb
variant.  It does not interface with the jgofs system's build command and must
be edited to define the local c compiler options, as well as to define
the locations of various files (please see the makefile).  Alternatively,
the -e switch may be used to take variables from the environment instead of
the make file itself.  The makefile may need a target of "all" on the
command line.
	    Care must be taken during the first make to ensure that
existing object files are not replaced unintentionally.  If you do not
want existing object files replaced, make's path search should be restricted
and/or dummy object files should be place in the distribution directory
and/or existing object files should be temporarily renamed.

	3)  Documentation:
	There are presently no "user", "new feature", or "bug/incompatibilty"
documents-sorry.  Also, "JGOFS system" documentation is not present, and
familiarity with the JGOFS system is assumed.  JGOFS system documentation
may be available via a WWW interface.
        User, new feature and some incompatibility information can be
found in the param1.doc file.  It is organized as a reference document,
but has some description that may be useful as a user document.
	Incompatibility information can also be found in the defgb_switches.doc
file.  The ultimate source of information about how things have changed
is the revision section of the code of each module.  Old revision sections
are in the defgb_revision.doc file.
	The defgb_bugs.txt file describes some known problems as well
as a "wish list", which by implication can explain some less-than-optimal
behavior of the program

	4)  Debugging suggestions:
a) The defgb_errs.txt file contains the text of various error messages.  Some
   messages have more information with them about what might cause the problem
   and/or which code module the message comes from.
b) Try running the method interactively.  The parameters on the command
   line are the parameters from the .objects file (but not comma separated).
   To see the text of what the html code will be, set the last 5
   characters of the environment variable PATH_INFO to .html0 (the 0 is the 
   level to display).  You may need to quote some parameters on the command
   line that you do not need to quote in the .objects file.
c) If the method works interactively but dies when run by the httpd server
   (and jgofs program serv), check for file access problems due to the switch
   between "you" running the interactive program and whatever username is
   running the httpd server.  Scripts need the appropriate x access.  If
   you have no luck, try setting up an error sink (see diagnostics optional
   file info in the .doc file-an appropriate command in an indirect file might
   be		diagnostics = \ error_sink = defgb.err		)
   Some error information is produced before the .html environment is
   set up to receive it, so the error sink might contain information lost other-
   wise (this situation is being repaired-our apologies)
