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  Protocol id yes, =0 and accepts 0 - FF  Mode of access Make only yes,default for writing Replace only yes Replace or Make yes Append yes Append or Make yes Take Job Input yes, default for device IBM: Take Job Output yes, default for device LPT: Read and Remove yes Read only yes, default for reading 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: Codes IA5 yes Binary yes EBCDIC no Private no [0FF0]reserved no Any parity yes, parity ignored Odd parity no Even parity no Parity Bit Zero no Format Effectors End of Record yes Fortran Contol yes  CR yes  LF yes  NL yes  FF yes  VT yes  HT yes  BS yes  CR->LF yes  LF->CR yes Binary Mapping yes,  - aligned packing into 36-bit word - only
Page 2 Max Record Size yes, =252 Max Transfer Size yes, no effect Transfer id yes, no effect [0A]Ack Window no, ignored [0B]Initial Restart Mark no, ignored [0D]Min Time-out yes [0E]Facilities Compression yes Retry later no Restart Requests no Restart Acks no Hold no GO Params. no [FFC0]Reserved [0F]State of Transfer yes Filename yes, full DEC-10 filespec allowed dev:name.ext[ppn,sfds]<prot> Username yes, PPN as an octal string of the area on Q to be read from or written to Username pass yes, FTP password for the area on Q to be read from or written to File pass yes, ignored Kinship yes, ignored [4A]Account yes, PPN as an octal string of the submitter of the request [4B]Account pass yes, ignored Output Device Type yes File Size yes, Operator message yes Monitor Message yes, kept in log file Special Options no, not allowed DATA TRANSFER PHASE  SS yes  MS yes, ignored  CS no, not allowed  ES yes  RR no, not allowed  MR no, not allowed  QR yes  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.