RFC 133 (rfc133) - Page 2 of 4

File Transfer and Error Recovery

RFC 133             File Transfer and Error Recovery          April 1971


1B  Extensions to the file transfer protocol

   The file transfer protocol needs a mechanism for accessing individual
   records of a file.  This will be particularly useful when very large
   data bases appear on the network.  The following definitions should
   be added to the protocol:

   The store(S) and retrieve(R) requests have the data field format
   , where  has the syntax:

    ::=RSUS | US.
                           --          --                      --

   The  syntax is changed to:

       ::= |  | RS.
                                                          --
   If a retrieve(R) request is given with a data field with 
   syntax rather than  syntax, then the returned data will
   consist of the record following the matching .  If a store(S)
   request is given with a data field of  syntax, then the
   supplied data will replace the record following the matching
   .  If the keyname does not exist, the record will be
   appended to the named file.  The individual installation must
   provide the linkage between the  and the record it
   references.

   In addition, the lookup(L) request will provide a list of keynames
   into a file (or the name of a file which contains the keynames).

   Transaction code F (request File directory) requests a listing of
   available files.  The data field of the F transaction is of the
   form:  GSGS...  All files in the server system
                    --          --
   which match one or more of the given  specifiers are
   listed in a return file.  The format of the data fields of this
   file is:  GSGS...  If a  field in
                       --          --
   the request transaction does not include a  field, the
   default is all files on the given device.  Some examples are given:

       
           ---             --








Sunberg