VI.d.4 Command searching
------------------------
Command searching is a way to incorporate OS-specific file selection tools
into the gopher facilities, using generic keywords which should be
interpretable on any OS.  Like GREP searching, Command searching locates
files, but not necessarily based upon content; date of last modification was
the inspiration for this kind of searching.  Files which match the criteria of
the search are returned in a menu to the client for possible retreival.  To
define a Command search, the path must specify a keyword and a (possibly
wildcarded) filespec, as in:

	Path=7$since gopher_root1:[gopher.vms.server]

The "$" is required to indicate this is a command search.  The valid keywords
for Command searching are, at present:

since		Client's search term must specify a date; server
                   locates files matching the filespec which have been
                   modified since that date using DCL Directory/SINCE.
before		Same as "since" except DCL Directory/BEFORE is
		   used.
search		Client's search term(s) specify character strings;
                   server locates files matching the filespec which contain
                   one or more of those strings.
search&		Same as "search" except /MATCH=AND is applied to
		   the DCL search.
search|		Same as "search" except /MATCH=OR is *explicitly*
		   applied to the DCL search.
search~&	Same as "search" except /MATCH=NAND is applied to
		   the DCL search.
search~|	Same as "search" except /MATCH=NOR is applied to
		   the DCL search.
version		Does *not* require a filespec; ignores any client-supplied
                   search terms; returns a menu of entries describing the
                   image of the server honoring the search, the same
                   information as supplied in the "Image Identification
                   Information" segment of an ANAL/IMAGE on the server.
                   Configuration file fields are also reported, as is the
                   host hardware and software version.
kaboom 		Does *not* require a filespec; ignores any client-supplied
                   search terms; normally returns a menu of one entry indicating
		   the request was denied.  In the specific cirumstance that
		   the server's host name matches exactly with a system
		   logical on the server's node, GOPHERD_KABOOM_HOST, and the
		   requesting client's host name matches exactly with a system
		   logical on the server's node. GOPHERD_KABOOM_CLIENT, the
		   server will force itself into an Access Violation.  This
		   facility is present only for validating server abend
		   procedures, and the logicals which enable it should not
		   exist on a production system.
ftplink		Does *not* require a filespec.  The client's search term
                   must specify the Internet address of an anonymous ftp
                   host (e.g., Niord.SHSU.edu). This pseudo-search function
                   returns a link with the name "Link to aFTP host <site>/"
                   and the path for accessing that site via the gopher
                   server's aFTP gateway (see Section VI.f).  If the client
                   shoots at this item, the gateway will return the aFTP
                   host's top directory listing as a gopher menu.
go4link		Does *not* require a filespec.  The client's search term
                   must specify the Internet address of a gopher host
                   (e.g., psulias.psu.edu).  It may also as a 2nd term
                   specify a port other than 70 (the default).  This
                   pseudo-search  function returns a link with the name
                   "Link to  Gopher host <site> on port <port>/" and host,
                   port and path for accessing that site's gopher server
                   (see Section VII.a).  If the  client shoots at this
                   item, the gopher server  at that host will respond
                   (assuming that host  *has* a gopher server) with its
                   top-level menu.
exelink		Does require a filespec.  The client's search term
                   must specify parameter(s) which are to be supplied to
		   the filespec, which should be a suitable execution script.
		   This pseudo-search  function returns a link with the name
                   "Execute script with arguments <param><param>.../" and host,
                   port and path for executing that script with those para-
		   meters (see Section VI.e.2).  If the  client shoots at this
                   item, the gopher server will respond with the output of the
		   link-specified exec script using the client-specified argu-
		   ments.

.