FTP-B as implemented on the ERCC DECsystem-10

It has been modified for interworking with FTP-80


The ERCC DECsystem-10  now  supports  an  implementation  of
FTP-B  as  described  in  the  document (1).  The facilities
offered in this implementation are listed below.

TRANSPORT SERVICE

Has timeout facilities.  Does not have Transport  Reset  but
does  a  clear  down  and re-initialise.  Synchronisation at
startup is done by exchanging node id's.

ATTRIBUTES                    Comment

[00] Protocol id              yes, =0 and accepts 0 - FF
[01] Mode of access
    [0001]Make only           yes,default for writing
    [0002]Replace only        yes
    [0003]Replace or Make     yes
    [0004]Append              yes
    [0005]Append or Make      yes
    [2001]Take Job Input      yes, default for device IBM:
    [4001]Take Job Output     yes, default for device LPT:
    [8001]Read and Remove     yes
    [8002]Read only           yes, default for reading
    [8004]Destructive read    no, meaningless on DEC-10
    [A001]Give Job Input      yes, default for device IBM:
    [C001]Give Job Output     yes, default for device LPT:
[02]Codes
    [0001]IA5                 yes
    [0002]Binary              yes
    [0004]EBCDIC              no
    [0008]Private             no
    [0FF0]reserved            no
    [1000]Any parity          yes, parity ignored
    [2000]Odd parity          no
    [4000]Even parity         no
    [8000]Parity Bit Zero     no
[03]Format Effectors
    [0001]End of Record       yes
    [0002]Fortran Contol      yes
    [0010] CR                 yes
    [0020] LF                 yes
    [0040] NL                 yes
    [0080] FF                 yes
    [0100] VT                 yes
    [0200] HT                 yes
    [0400] BS                 yes
    [1000] CR->LF             yes
    [2000] LF->CR             yes
[04]Binary Mapping            yes, [0024] - aligned  packing
                              into 36-bit word - only
                                                      Page 2


[05]Max Record Size           yes, =252
[06]Max Transfer Size         yes, no effect
[08]Transfer id               yes, no effect
[0A]Ack Window                no, ignored
[0B]Initial Restart Mark      no, ignored
[0D]Min Time-out              yes
[0E]Facilities
    [0001]Compression         yes
    [0002]Retry later         no
    [0004]Restart Requests    no
    [0008]Restart Acks        no
    [0010]Hold                no
    [0020]GO Params.          no
    [FFC0]Reserved
[0F]State of Transfer         yes
[40]Filename                  yes,  full   DEC-10   filespec
                              allowed
                              dev:name.ext[ppn,sfds]<prot>
[42]Username                  yes, PPN as an octal string of
                              the  area on Q to be read from
                              or written to
[44]Username pass             yes, FTP password for the area
                              on   Q  to  be  read  from  or
                              written to
[45]File pass                 yes, ignored
[46]Kinship                   yes, ignored
[4A]Account                   yes, PPN as an octal string of
                              the submitter of the request
[4B]Account pass              yes, ignored
[50]Output Device Type        yes
[60]File Size                 yes,
[70]Operator message          yes
[71]Monitor Message           yes, kept in log file
[80]Special Options           no, not allowed


DATA TRANSFER PHASE

[40] SS                       yes
[41] MS                       yes, ignored
[42] CS                       no, not allowed
[43] ES                       yes
[44] RR                       no, not allowed
[45] MR                       no, not allowed
[46] QR                       yes
[47] ER                       yes


IMPLEMENTATION

It is implemented as a spooling system using network  tasks,
transfer  requests  being generated by a program like QUEUE.
See documents  (2)  and  (3)  for  a  description  of  these
programs.
                                                      Page 3


REFERENCES

1. A Network Independent File Transfer Protocol prepared  by
the High level Protocol Group

2. Section 3A55B of the Edinburgh Installation Manual -  SRC
DECsytem-10 Installation ERCC

3. Operators Guide to FTP -  SRC  DECsystem-10  Installation
ERCC.