[comp.text.tex] Update regarding FILESERV

bed_gdg@SHSU.BITNET ("George D. Greenwade") (04/25/91)

Wanted to point out two update topics on FILESERV.  First, I have updated
the HELP file to include a broader list of synonyms and a discussion of the
use of wildcards in requests.  This should clarify FILESERV's commands a
little better than previously.  Second, I have added a package named
ADDITIONS, which lists the most recently updated or created files on
FILESERV's directory structure.  This allows for a check on when a file was
put up -- for example, the STY.ULEM file I put up today is named the same
as its predecessors; without dating information, you may might miss it.
 
Attached are the revised help file and the description file for ADDITIONS.
 
Regards,   George
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
George D. Greenwade, Ph.D.                            Bitnet:  BED_GDG@SHSU
Department of Economics and Business Analysis         THEnet: SHSU::BED_GDG
P. O. Box 2118                                        Voice: (409) 294-1266
Sam Houston State University                          FAX:   (409) 294-3612
Huntsville, TX 77341            Internet: bed_gdg%shsu.decnet@relay.the.net
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
                              FILESERV Help
                              -------------
FILESERV is Sam Houston State University's automated file distribution
service which uses electronic mail facilities to deliver files.  To
communicate with FILESERV, send a MAIL message to:
                           FILESERV@SHSU.BITNET
Commands are included in the body of the message you send to FILESERV.
Several commands may be sent at one time in one message, so long as each
command resides on a unique line of the message.  Please do not include any
text other than that associated with the commands listed below.
 
FILESERV Commands:
------------------
    SENDME package       Sends all parts of the specified package.
    SENDME package.n     Sends part 'n' of the specified package.
    GET package          SENDME and GET are synonyms.
    GET package.n
 
    LIST [pattern]       Gives brief description of all packages
    DIRECTORY [pattern]  matching "pattern".  If pattern is omitted,
    INDEX [pattern]      a description of all packages is sent.
                         LIST, DIRECTORY, and INDEX are all synonyms.
 
    HELP                 Sends this file.
Commands may be abbreviated to their shortest unique length (so SEND can be
used for SENDME and DIR for DIRECTORY, if desired).
 
For each request you make, a transaction log is returned to you indicating
the status of the request.  The transaction log will indicate whether the
request was successfully completed, and if the file was sent immediately or
when it is queued for transmission.
 
Use of wildcards in commands:
-----------------------------
Valid VMS-style wildcards are allowed in commands.  Recognized wildcard
specifications are '*' and '%'.  The '*' character represents an
alphanumeric string of any length.  Thus, the command:
  SENDME package.a*
would send all parts of the specified package with the first letter of its
extension equal to the letter 'a', regardless of the length of the
extension (if any; the * wildcard allows for a length of zero).
 
The '%' character represents any alphanumeric character in precisely the
location of the wildcard.  Thus, the command:
  SENDME package.a%
would send all parts of the specified package with the first letter in the
two-character extension equal to the letter 'a' and the command:
  SENDME package.a%%
would send all parts of the specified package with the first letter in the
three-character extension equal to the letter 'a'.
 
Note that when using the 'a*' wildcard, the file 'package.a' would be
returned as '*' can represent any length of characters, including a length
of zero.  However, when using the 'a%' wildcard, the file 'package.a' would
*not* be returned as the '%' specifies that exactly one character must be
present following the initial character 'a'.
========================================================================
Problems, questions, and comments about FILESERV service on this system
should be directed to File-Mgr@SHSU.BITNET.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                                ADDITIONS
                                ---------
ADDITIONS includes two listings of files recently added to the FILESERV
directories, indicating date and time of when the files were added or
updated.  This listing includes all files which have been added or updated,
whether they can be sent from FILESERV or not, so that the listings can be
utilized by anonymous ftp users of NIORD.SHSU.EDU [195.95.115.8] as well.
 
Files retrievable on FILESERV via the SENDME command must meet the
following conditions:
  1. The directory is MX_ROOT:[FILESERV.A_NAME], and
  2. The filename structure is A_NAME.EXTENSION
If these conditions are met and you want the file, include the command:
SENDME A_NAME.EXTENSION
in the body of a mail message to FILESERV@SHSU.BITNET and FILESERV will
process the request and forward you the file.  If the conditions are not
met, then the file is not mailable by FILESERV, but are available for ftp.
 
For ftp users, the default directory is MX_ROOT:[FILESERV], so you can
change directory to the appropriate directory and retrieve whatever you
wish.  Any file residing in anything other than a first-level subdirectory
are not available for access except by ftp.
 
The two files in the ADDITIONS package are ADDITIONS.7DAYS and
ADDITIONS.30DAYS, which contains listings for the most recent seven and
thirty day period, respectively.  To receive both lists, please include the
command:
SENDME ADDITIONS
in the body of a mail message to FILESERV@SHSU.BITNET.  To receive a
specific ADDITIONS file, include whichever of the two following commands
are appropriate in the body of a mail message to FILESERV@SHSU.BITNET:
SENDME ADDITIONS.7DAYS
SENDME ADDITIONS.30DAYS