1 10/11/88 unified_file_transfer, uft
2
3 Syntax as a command:
4 uft path1 path2 -to DEST | -from DEST -control_args
5
6
7 Function:
8 The unified_file_transfer uft request lets you submit an
9 interactive file transfer request to a remote host.
10
11
12 Arguments:
13 path1
14 String path1 specifies the source file to be used for the
15 transfer. It must be preceded by -name or -nm if the file
16 name begins with a "-". <source_file> can be a "star" name if
17 the file being transferred resides on the host. Star
18 convention is allowed, and as much requests as found files
19 will be entered.
20 path2
21 String path2 specifies pathname of destination file, and has
22 the same syntax and restrictions as path1. path2 accepts
23 equal conventions. When omitted, equals path1 Default. If
24 path1 uses star convention, equal convention is mandatory.
25
26
27 Control arguments:
28 -to STR
29 to be used when file is to be sent from HOST to REMOTE.
30 String STR is correspondent name given in the NIT Network
31 Information Table to the remote UFT application. The NIT
32 associates the UFT correspondent name to its DSA network
33 address session_id and mailbox. STR can be given by active
34 function "list_uft_correspondent" refer to command "luc" for
35 details.
36
37
38 -from STR, -fm STR
39 to be used when file is to be received onto the HOST. String
40 STR is correspondent name given in the NIT Network
41 Information Table to the remote UFT application. The NIT
42 associates the UFT correspondent name to its DSA network
43 address session_id and mailbox. STR can be given by active
44 function "list_uft_correspondent" refer to command "luc" for
45 details.
46
47 See "Notes" below for referral of remaining control arguments.
48
49
50 Notes:
51 The syntax of the unified_file_transfer request is the same as
52 the enter_uft_request command. All control arguments used to
53 define the file characteristics and other request options are
54 described in the enter_uft_request.info info segment. Type
55 "help eur" for a description of these control arguments.
56
57 Between two Multics systems, data is read and written without
58 consideration of the file organization. The bit count of each
59 segment of the destination file is adjusted at the end of the
60 transfer to the same value as the bit count of the corresponding
61 segment in the source file. There is no data_type translation.
62
63 Between a Multics system and a non-Multics system, the file
64 transfer is a "record" transfer; Multics reads or writes the file
65 transferred on a record basis using the vfile access methods.
66
67
68 Multics DSA UFT does not support tape files. Tape files must be
69 stored in a Multics disk file before being sent by Multics
70 DSA UFT. Multics DSA UFT can receive a file only in a Multics
71 disk file.
72
73 The Multics requestor accepts transfers between different file
74 organizations but it does not change the format of the record.
75 It is your responsibility to ensure that the record format used
76 is appropriate for the destination file.
77
78
79 When specifying control arguments to the unified_file_transfer
80 request, the control arguments used to define the characteristics
81 of the destination file are used to request the creation of the
82 remote file. Those control arguments that affect the
83 characteristics of the destination file are prefaced by "-d"
84 for example -d_status. Those control arguments that affect
85 the source file are prefaced by "-s" for example
86 -s_record_format.
87
88 Some systems do not retain file attributes after file creation
89 such as data_type on Multics. For these systems, it may be
90 necessary to define the missing file attributes in the transfer
91 request.