1 
 2 09/23/87  IMFT
 3 Known errors in the current release of IMFT.
 4 #         Associated TR's
 5 Description
 6 
 7 0022  phx16848
 8 If an error occurs reading the acknowledgement of a "pull" request,
 9 the request is deferred, and therefore resubmitted later.  Meanwhile,
10 the foreign site has actrually succeeded in queueing the request, so
11 the file ultimately gets transferred twice.
12 
13 0021  phx15250
14  If a pull request is successfully queued, but then the output driver
15  on the source site finds an access problem, the user is not notified
16  on the target (i.e.  originating) system.  Fixing this probably means
17  always sending a message to the target site whenever a request is
18  rejected by the driver, no matter where the request originated.
19 
20 0016  phx15007
21  When the input driver terminates reception of an object at the
22  operator's request (ie:  QUIT/release), it should inform the remote
23  system's output driver.  Otherwise, the remote system will continue
24  to transmit the object; the input driver, however, will ignore all
25  data and control records until the BOF record that indicates the
26  start of the next object.  As a result, the output driver will
27  believe that the object was successfully transmitted when, in fact,
28  it was thrown into the bit-bucket.