Exactly how long files may remain unprocessed and exactly how large these transient files may be is a local administrative or implementation decision. UFT commands then become parameters to the Content-Type field and the data file is carried as the mail body. UFT supports several representation types. The receiving host should accept any file type sent. An example of this is the job entry queue available as a pseudo-user on many NJE networked hosts.
Commands consist of command words, possibly followed by tokens delimited by white space.
While a data burst is being received, command interpretation is suspended. EOF causes the server to close the file at the receiving end and return to normal command processing. QUIT closes any open file, closes the connection, and can appear anywhere in the job. If the burst-size token is omitted from the DATA command, processing switches to data mode and the stream is read until the client closes the connection. A server accepts a command by sending a single packet back to the client that starts with a NULL character, decimal 0.