Note on usage
Function: Asynchronous file transfer
User group: FT user
Alias name: ftacopy
Functional description
The ft command is used to issue asynchronous file transfer requests for sending a file or a directory to a remote system or for fetching a file or a directory from a remote system. In addition, you can use the preprocessing, postprocessing or follow-up processing capabilities to execute operating system commands in the local or remote system. Once openFT has stored the request in the request queue, your user process will be available again. openFT performs the actual transfer operation asynchronously to your user process at the earliest opportunity or at a time you specify, provided resources are free and the partner is available.
openFT acknowledges receipt of the request by default, with the output of the following message on the screen (stderr) of the user who issued the request
ft: Request request ID accepted.
request ID
is replaced by the transfer identification of the transfer request.
After acknowledgment of the request, the user process continues to run.
Note for Unix systems
If you want, you can use the -m option to tell openFT to send a result notification to the initiator's mail box if the request is processed successfully and/or unsuccessfully.
Note for Windows systems
The ft command usually cannot be executed in PowerShell because it is overwritten by the system command ft (Format Table). It is recommended to use the alias name ftacopy.
If openFT rejects your request, an error message will be displayed explaining why it was rejected (see chapter “Messages” ).
The maximum number of requests that can be stored in the request queue is specified in the operating parameters. You can raise the default value of 2000 up to a maximum of 32000 (see the ftmodo command). Any further requests are rejected.
You can also obtain the result of an ft request by using the log function (see ftshwl command).
Only one file can be fetched from a remote system for each ft command. If you want to fetch several files asynchronously, use the ft_mget command.
Format
ft -h | | |
[ -t | -u | -b ] [ -x ] |
*) The options -N and -m are only available on Unix systems
Description
-h
Displays the command syntax on the screen. Entries after the -h are ignored.
[ -t | -u | -b ] [ -x ]
Identifies the type of file in the local operating system.
If you send a file to an FTAM partner without specifying a file type, the file type is determined by the structure entries of the send file. The structure entries can be displayed by outputting the local FT attributes (ftshwf file name -l). If there are no structure entries, the default value is -t. If you fetch a file from an FTAM partner without specifying a file type, the file type is determined by the file attributes in the FTAM partner. For more detailed information about file types when dealing with FTAM partners, see the openFT manual "Concepts and Functions".
-t (default value with openFT partners)
The file contains text with variable-length records.
Records end with the linefeed character \n on Unix systems.
On Windows systems, records end with the following characters:
CRLF (X'0D0A') when sending and/or fetching a file
LF (X'0A'), only possible when sending a file
-u
The file contains user-structured binary data with variable-length records. Each record starts with 2 bytes which contain the length data of the record.
-b
The file contains user-structured binary data with variable-length records.
If you specify the -b switch together with -r (maximum record length), the file contains binary data with record length specified for -r. The size of the send file must be a multiple of this record length.
-x
The send file is transferred in a transparent file format and is stored in the destination system, i.e. this is a file whose attributes are transparent for the local system.
The local system here acts as a storage and/or transport medium.
If a file is transparently retrieved with -x for local buffering, then it must be sent again to the remote system in binary form (i.e. with -b).
-o | -e | -n
Indicates whether a destination file is to be newly created, overwritten or extended.
-o (default value)
The destination file will be overwritten or newly created if it does not already exist.
In case of directory transfer (-d option), the target files are overwritten if the specified directory and the files in this directory already exist. Otherwise, the target directory, subdirectories (if they may exist) and the files are newly created. Files and subdirectories which only exist in the target directory remain unchanged.
-e
The transferred file will be appended to an existing destination file. If this destination file does not exist, it will be newly created.
-e is not permitted in case of directory transfer (-d option).
-n
The destination file will be newly created and written. If the destination file already exists, the request will be rejected. In this way, you can protect a file from being overwritten inadvertently.
In case of directory transfer (-d option), the target directory and the files are newly created. If the target directory already exists, the request is rejected.
-k
Indicates that identical characters repeated consecutively are to be transferred in compressed form (byte compression). In the case of connections to partners which do not support this type of compression, no compression are used automatically.
-z
Indicates that zip compression is used. In the case of connections to partners which do not support this type of compression, byte compression (corresponds to the option -k) or no compression are used automatically.
-c
Indicates that the data are also encrypted for file transfer. To do this, the openFT-CR module must have been be installed. The encryption of the request description data is not affected by this option. If the partner system does not support data encryption, the request is rejected.
-N
(only on Unix systems) Suppresses result messages being deposited in the mailbox of the user who issued the request. -N is the same as -m=n, but is still supported for compatibility reasons.
-S
Suppresses file transfer messages to stderr.
-m=n | -m=f | -m=a
(only on Unix systems) This indicates whether the result message is to be deposited in the mailbox of the user who issued the request.
With some systems, the mail cannot be delivered if the login name is longer that 8 bytes.
n
(default value) The result message is not deposited in the mailbox (identical to the -N option).
f
The result message is only deposited in the mailbox in the event of errors.
a
The result message is always deposited in the mailbox.
-d
Indicates a directory transfer.
Local and remote file names are interpreted as directory names.
-d is only supported for openFT partners (not for FTAM or FTP partners). Preprocessing and postprocessing are not supported.
If you are using the -d option together with other options (e.g overwrite (-o) or follow-up processing (-ls, -rs,...)) then these options apply to the individual files in the directory to be transferred.
file name partner![file name] | partner![file name] file name
specifies the source and destination. The syntax depends on the direction of transfer selected and whether pre- or postprocessing commands are used or whether a directory is transferred. If you are using the option -d (directory transfer) then the source and destination file name are considered as directory names.
Sending without pre-/postprocessing
Sending a file
Source | Destination |
local file name | partner![remote file name] |
Sending a directory
Source | Destination |
local directoy name | partner! remote directoy name |
If you transfer a directory (-d) then you specify the directory you want to transfer in local directory name. For remote directory name, you specify the directory under which the transferred directory is stored with identical file names and subdirectory names if applicable. The specification for the remote directory may not be omitted.
Fetching without pre-/postprocessing
Fetching a file
Source | Destination |
partner![remote file name] | local file name |
Fetching a directory
Source | Destination |
partner![remote directory name] | local directory name |
Sending and fetching a file with pre- or postprocessing
If you want to perform pre- or postprocessing, then you must enter an operating system command instead of the local or remote file name (in the syntax of the corresponding system).
Sending with preprocessing
Source | Destination |
"| local command" | partner![remote file name] |
Sending with post-processing
Source | Destination |
local file name | Partner!"| remote command" |
Fetching with preprocessing
Source | Destination |
Partner!"| remote command" | local file name |
Fetching with post-processing
Source | Destination |
Partner![remote file name] | "| local command" |
You can also combine preprocessing and postprocessing in the same request.
A maximum of 712 bytes may be specified both for source and destination (maximum 512 bytes for the file name and maximum 200 for the partner). Please note that the maximum lengths of file names are system-dependent; for example, in Unix systems it is 512 and in Windows systems a maximum of 256 bytes (for the representation in UTF- 8, see section “Entering commands” ).
local file name
local directory name
Sending: Name of the local file or directory (option -d). The name may include an absolute or relative path name.
Fetching: Name of the receiving local file or directory (option -d). The name may include an absolute or relative path name.
However, the ft command will not create a directory which does not already exist. If the name ends with %unique or %UNIQUE, this string is replaced by a string which changes for each new call, see section “Entering commands”.
partner
partner is the name of the partner system in the partner list or the address of the partner system. For details concerning address specification, see section “Specifying partner addresses”.
remote file name
remote directory name
remote file name and remote directory name (option -d) can be either absolute or relative to the remote login authorization. If the file name or directory name in the remote system has been predefined in an FT profile, it must not be specified here. If the name contains blanks, it must be enclosed in double quotes (e.g. "file name").
If the name ends with %unique or %UNIQUE, this string is replaced by a string which changes for each new call, see section “Entering commands”.
If the partner system is running openFT(BS2000), elements from PLAM libraries may also be specified here (Syntax: Libname/Element type/Element name).
|command for file name
command is any command on the local or remote system (not permitted in case of directory transfer). The "|" character (pipe character) must always be placed before the command. Since the "|" character is a special character "|command" should always be enclosed in double quotes.
Please note that, as of openFT V12, pre- or postprocessing commands are converted to the UTF-8 character set in remote Windows systems and that more characters may therefore be required in the remote system see also section“Entering commands”.
In the case of preprocessing, openFT transfers the data output at the standard output by the command as a file. You can also output the data created by preprocessing in a temporary file created by openFT.
During postprocessing, you can have the transferred data stored in a temporary file created by openFT.
You can find out the name of this temporary file and pass it to preprocessing or postprocessing with the variable %TEMPFILE. See the section “Preprocessing and postprocessing” .
If command execution takes longer than ten minutes, a timeout occurs on partners using versions of openFT prior to V8.1 and command execution is regarded as having failed. This restriction no longer applies to partners using openFT V8.1 or later.
Remote command execution in Unix and Windows systems starts in the user's $HOME directory or home directory respectively.
Note for Unix systems
The PATH variable is used as follows in the search path for preprocessing and postprocessing commands in Unix systems:
Standard instance: :/opt/openFT/bin:/bin:/usr/bin:/opt/bin
Other instance: :/var/openFT/instance/openFT/bin:/bin:/usr/bin:/opt/bin where instance is the name of the relevant instance.
This means that the system first searches in the current directory (first ":").
Before calling a "real" preprocessing or postprocessing command you can switch to another directory as follows:
cd path-name;command
path-name is then used as the current directory. There must not be a blank between the semicolon and the command.
Note for local and remote Windows systems
path-name must not be a directory which is addressed using a UNC name. Exception: The UNC checking is deactivated on the system on which the command is to be executed. To do this, the registry value described under https://support.microsoft.com/de-de/kb/156276 has to be generated.
If the string "|&" comes before the preprocessing/postprocessing command instead of the character "|", the openFT request is restartable (see the section “Preprocessing and postprocessing” .).
transfer admission | @d | @n |
user ID[,[account][,password]]]
To be able to send a file to a remote system or to fetch one from it, you must furnish the remote system with proof of identity. For this purpose, you will need login authorization in the syntax valid for the remote system. You can specify transfer admission
as an FTAC transfer admission if FTAC is used in the remote system,
or as a login/LOGON authorization in the syntax used by the remote system (user ID, possibly together with account or password).
For details, see section “Entering the authorization data for the partner system” .
@d for transfer admission
Specifying @d (blanked transfer admission) causes openFT to query the transfer admission on the screen after the command is entered. Your entry is not displayed to prevent unauthorized persons from seeing the transfer admission.
@n for transfer admission
By entering @n, you specify that the remote system requires no login authorization.
A binary password and a binary transfer admission must be entered in hexadecimal format, see section “Entering commands”.
password not specified
Omitting the password necessary for admission causes openFT to query the password on the screen after the command is entered. Your entry is not displayed to prevent unauthorized persons from seeing the password.
Nevertheless, you have to specify the commas, e.g.:
ft file partner!file user-id,,
or
ft file partner!file user-id,account,
neither transfer admission nor user ID specified
causes the same as @d, i.e. openFT queries the transfer admission on the screen after the command is entered. Your (blanked) entry is always interpreted as transfer admission and not as user ID.
-p=[password]
If the file in the remote system is protected by a write password, you must enter this password when sending a file. If the file is protected by a read password, then this password must be specified when fetching a file from the remote system.
A binary password must be entered in hexadecimal format, see section “Entering commands”. This is of relevance for links to openFT on a BS2000 system, because BS2000 supports the definition of hexadecimal passwords.
password not specified
Specifying -p= causes openFT to query the write or read password on the screen after the command is entered. Your entry is not displayed to prevent unauthorized persons from seeing the password.
-di
is specified, if the data integrity of the transferred file is to be checked by cryptographic means. With it, harmful data manipulations on the transmission network are identified. In case of an error openFT performs an error recovery for asynchronous transfer requests.
If the partner system does not support the check of data integrity (e.g. openFT < V8.1), the request is denied.
For requests with data encryption (option -c), data integrity is automatically checked. Testing mechanisms of the transfer protocols in use automatically identify transfer errors in the network. For this purpose you do not have to specify the -di option.
-lc=CCS name
(local coding) specifies the type of coding (character set) to be used to read or write the local file. CCS name must be known in the local system.
The default value is the character set defined by the FT administrator.
Details about the CCS name and the associated code tables can be found in the manual "openFT (Unix and Windows systems) - Installation and Operation".
-rc=CCS name
(remote coding) specifies the type of coding to be used to read or write the remote file. CCS name must be known in the remote system.
The default value is the character set defined in the remote system via XHCS (BS2000 system) or the openFT operating parameters (other platforms).
The option -rc is supported only by the openFT protocol and partners with openFT V10.0 or higher. Please note that not all partner systems support all the character sets that are possible in the local system.
Details about the CCS name and the associated code tables can be found in the manual "openFT (Unix and Windows systems) - Installation and Operation".
-ls=follow-up processing
Here you can specify a command which will be executed in the local system following a successful transfer operation.
Further information is given in the section “Commands for follow-up processing” .
-lf=follow-up processing
Here you can specify a command which will be executed in the local system if a transfer operation is terminated as a result of an error.
Further information is given in the section “Commands for follow-up processing” .
-rs=follow-up processing
Here you can specify a command in the syntax of the remote system. Following a successful transfer operation, this command is executed in the remote system under the specified login.
Further information is given in the section “Commands for follow-up processing” .
-rf=follow-up processing
Here you can specify a command in the syntax of the remote system. This command will be executed in the remote system under the specified login if a transfer operation that has already started is terminated as a result of an error.
Further information is given in the section “Commands for follow-up processing” .
-r=v[record length] | -r=f[record length] | -r=u[record length] | -r=record length
Specifies the record format and the record length. This also enables records that are longer than the default value to be transferred. However, you must bear in mind that not every record length can be processed in all partner systems.
If you have selected the file type b (binary), record length it the value for all records of the send file.
Maximum value for record length: 65535 bytes.
With FTAM partners, the maximum record length specification is not valid unless the file type is set explicitly to t, b or u.
It is also possible to output the record format, see also ftmodf command, option -rf:
v | variable record length, record length defines the maximum value |
f | fixed record length, record length then applies to all records |
u | undefined record length |
The combinations -u -r=frecordlength and -u -r=urecordlength are not permitted.
If -r is omitted then the following default values apply for the record format:
Option | Default value | Corresponds to |
-b | u (undefined) | -r=u... |
-t | v (variable) | -r=v... |
-u | v (variable) | -r=v... |
-tff=b | -tff=s
Specifies the format of the destination file.
b
The destination file is to be saved as a block-structured file. This means, for example, that a file can be transferred to BS2000 and stored there as a PAM file. If you specify -tff=b, you must also specify the option -b (binary).
s
The destination file is to be saved as a sequential file and the record format is to be retained. This allows an ISAM file or PAM file to be fetched from BS2000, for instance.
-tff=b must not be specified at the same time as -trf=u.
-trf=u
Specifies that the file is to be transferred as a sequential file and that the record format of the destination file is to be undefined, i.e. the record structure of the send file is lost. If the file is being transferred to a BS2000 or z/OS system, one block is written per transfer unit.
-trf=u must not be specified at the same time as -tff=b.
neither -tff nor -trf specified
The destination file is to be stored in the same format as the send file.
-tb=n | -tb=f | -tb=a
Activates/deactivates tabulator expansion and the conversion of blank lines into lines with one character for non-FTAM partners for a single output send request.
The following parameters are provided:
n (on)
Tabulator expansion and blank line conversion are activated.
f (off)
Tabulator expansion and blank line conversion are deactivated.
a (automatic, default value)
Tabulator expansion and blank line conversion are activated if a file is sent to a BS2000, OS/390, or z/OS system.
No tabulator expansion or blank line conversion is performed for outbound receive requests.
If ft is used as a preprocessing command, then tabulator expansion and blank line conversion are always deactivated.
The following parameters -av, -ac, -am, -lq and -cp are provided exclusively for communication with FTAM partners. openFT thus supports the parameters defined in the FTAM standard. These parameters enable you to define the attributes of the destination file while issuing a file transfer request.
These parameters are ignored for requests involving openFT and FTP partners, but the file transfer is still carried out.
-av=i | -av=d
Indicates the availability of the destination file. This parameter can have one of two values: immediate or deferred. A file may be deferred if it has been archived, for example. The partner is responsible for interpreting the term deferred. The FTAM partner conventions must therefore be observed here.
The following values are possible:
i
The destination file attribute is set to immediate.
d
The destination file attribute is set to deferred.
-av is not available for requests involving FTAM partners that do not support the storage group. In this case, the request is executed, but the entry for -av is ignored.
-av not specified
The availability file attribute is set to a system-specific default value. In this case, this is the value immediate.
-ac=new account
With FTAM partners, this indicates the number of the account to which file storage fees are to be charged. This parameter must be set in accordance with partner system conventions.
-ac is not available for requests involving FTAM partners that do not support the storage group. In this case, the request is executed, but the entry for -ac is ignored.
-am=[r][i][p][x][e][a][c][d] | -am=@rw | -am=@ro
This sets the access rights of the destination file, provided the security group is available. The security group is defined in the manual "openFT (Unix and Windows systems) - Installation and Operation".
The following values can be specified for access mode:
r, i, p, x, e, a, c, d, any combination of these values, @rw, or @ro.
r
means that the file can be read.
r not specified
The file cannot be read.
i
means that data units, such as records, can be inserted in the file.
i not specified
No data units can be inserted in the file.
p
means that the file can be overwritten.
p not specified
The file cannot be overwritten.
x
means that data can be appended to the file.
x not specified
The file cannot be extended.
e
means that data units, such as records, can be deleted from the file.
e not specified
No data units can be deleted from the file.
a
means that the file attributes can be read.
a not specified
The file attributes cannot be read.
c
means that the file attributes can be changed.
c not specified
The file attributes cannot be changed.
d
means that the file can be deleted.
d not specified
The file cannot be deleted.
@rw
is the short form of the common access rights read-write (rpxeacd), and thus simplifies input.
@ro
is the short form for the common access rights read-only (rac), and thus simplifies input.
If the partner system is a Windows system, you cannot change the access rights of the destination file.
In Unix systems or in BS2000, the following access rights can be set for a file:
Access mode | Short | Unix | BS2000 | Access rights |
rpxeacd | @rw | rw* | ACCESS=WRITE | read-write |
rac | @ro | r-* | ACCESS=READ | read-only |
pxeacd | -w* | Only with BASIC-ACL (Access | write-only | |
ac | --* | Only with BASIC-ACL (Access | none |
-am is not available for requests involving FTAM partners that do not support the security group. In this case, the request is executed, but the entry for -am is ignored.
-am not specified
The default values of the FTAM partner system apply.
-lq=legal qualification
This specifies a legal qualification for the destination file (similar to a copyright). This may not exceed 80 characters.
-lq is not available for requests involving FTAM partners that do not support the security group. The request is executed, but the entry for -lq is ignored.
-cp=[password]
If a password is required in order to create a file on a remote system, this password must be specified here. It can be up to 64 characters long.
A binary password must be specified in hexadecimal format, see section “Entering commands”. If you do not specify a file creation password, but you do enter a file access password for -p=password, the file creation password is identical to the file access password. The file creation password is of no significance when retrieving a file.
password not specified
Specifying -cp= causes openFT to query the file creation password on the screen after the command is entered. Your entry is not displayed to prevent unauthorized persons from seeing the password.
-pr=n | -pr=l
indicates the priority of the request:
n (normal)
the request has the priority "normal" (default value).
l (low)
the request has the priority "low".
-sd=start date
indicates the earliest date at which the file transfer is to be started.
Possible values:
yyyymmdd
e.g. 20170331 for the start transfer on March 31, 2017. The largest possible value for the date is 20380119 (January 19, 2038).
+ddddd
e.g. +2 for start of transfer 2 days after issuing the request. You can delay file transfer by 999 days at the most. You can specify at most five figures for the delayed date. The value is limited by the number of days up to 19.01.2038.
-st=start time
specifies the earliest time at which file transfer is to be started (due to the nature of the system, the start time may deviate 5 minutes from the specified time). Possible values:
hhmm
e.g. 1430 for start of transfer at 14:30 hrs.
+hhmm
e.g. +0230 for start of transfer 2 hours and 30 minutes after issue of the request. The maximum delay you may specify is 99 hours and 59 minutes.
The start time must not be specified as relative if the start date has been specified as absolute. For a relative start date and start time, the start time is calculated from the total of the two entries, i.e. if a request is issued at 10.07. at 15:00 hrs. with -sd=+1 and -st=+1000, the request is not started until 12.07. at 01:00 hrs.
If you enter a start date without a start time, transfer is started at 00:00 hrs. on the date specified. If you enter a start time without a start date, the time applies to the current date. If you specify a request with -st=1000 at 15:00 hrs then the request is run immediately.
-cd=cancel date
Specifies the date on which the request is to be deleted. If the request is active at the time specified, it is aborted. Possible values:
yyyymmdd
e.g. 20170531 for cancellation of the request on May 31, 2017. The specified time must not lie in the past. The largest possible value for the date is 20380119 (January 19, 2038).
+ddddd
e.g. +2 for cancellation of the request 2 days after its issue. The maximum delay you may specify is 999 days. You can specify at most five figures for the delayed date. The value is limited by the number of days up to 19.01.2038.
-ct=cancel time
Specifies the time at which the request is to be deleted (due to the nature of the system, the start time may deviate 5 minutes from the specified time). The specified time must not lie in the past. If the request is active at the time specified, it is aborted. Possible values:
hhmm
e.g. 1430 for cancellation of the request at 14:30 hrs. The specified time must not lie in the past.
+hhmm
e.g. +0230 for cancellation of the request 2 hours and 30 minutes after its issue. The maximum delay you may specify is 99 hours and 59 minutes.
If you enter a cancel date without a cancel time, the file transfer is canceled at 23:59 hrs on the date specified. If you specify a cancel time without a cancel date, the time applies to the current date.
The cancel time must not be specified as relative if the cancel date has been specified as absolute. For a relative delete date and delete time, the delete time is calculated from the total of the two entries, i.e. if a request is issued at 10.07. at 15:00 hrs. with -cd=+1 and -ct=+1000, the request is not deleted until 12.07. at 01:00 hrs.
Requests also have a limited lifetime, even if no values are specified for -cd and -ct. This lifetime is set by the FT administrator. You may query the value using the command ftshwo. The entry stands for MAX-RQ-LIFE. Specifying -cd and -ct disables the MAX-RQ-LIFE entry.
-fnc=t | -fnc=c (file name coding)
specifies the encoding mode for file name and follow-up processing.
t (transparent, default value)
Specification of the remote file name and follow-up processing for the remote system in transparent mode (compatible to the previous versions).
c (character)
Specification of the remote file name and follow-up processing for the remote system in character mode. They are interpreted according to the character code of the remote system, i.e. for Unix partners according to the openFT operating parameter option (ftmodo -fnccs) that has been set there.
-fnc=c is only permitted for openFT partners as of openFT V12.1.
-md
(modification date)The modification date of the send file is taken over for the destination file provided that the destination system supports this. If the destination system does not support this function then the request is rejected. The use of this function is only of value for requests via the openFT protocol to BS2000 with OSD V8.0 or higher.
-md not specified
The behavior is the same as in openFT V11.0 or earlier: On Unix and Windows systems as well as under POSIX (BS2000), the modification date of the send file is taken over. On BS2000 with DMS, the current time is taken over as the modification date.
Examples
The text file doc.one is sent by user jack to the BS2000 computer with the symbolic name bs2r1. Here, it is stored under the login name jim with account number a1234ft and password C'pwd'. The file should then be printed.
Unix systems:
ft doc.one bs2r1!doc.one jim,a1234ft,C\'pwd\'\ -rs="/PRINT-FILE %FILENAME,LAYOUT-CONTROL=*PARAMETERS\ (,CONTROL-CHARACTERS=EBCDIC)"
Windows systems:
ft doc.one bs2r1!doc.one jim,a1234ft,C'pwd'-rs="/PRINT-FILE %FILENAME,LAYOUT-CONTROL=*PARAMETERS(,CONTROL-CHARACTERS=EBCDIC)"A file is to be fetched from BS2000, where openFT-AC is running, to the local system. The file name has been predefined in an FT profile, which can be accessed with the access authorization 'fortheRM6'. In the local system, the file is to be stored in the test directory under the name track.f as a type u file (user format).
ft -u bs2! test/track.f 'fortheRM6'(Unix systems)ft -u bs2! test\track.f 'fortheRM6' (Windows systems)Note: Windows also accepts '/' in file names.
The file source.lst is sent to the BS2000 computer bs2r1. Here, it is stored under the login name jim with account number a1234ft and password C'pwd' under the file name lst. Then, as follow-up processing, the file is to be printed out in BS2000 and then deleted. The source file in the local system is likewise deleted.
Unix systems:
ft source.lst bs2r1!lst jim,a1234ft,C\'pwd\'\ -ls='rm source.lst'\ -rs='/PRINT lst,DELETE-FILE=YES'
Windows systems (with using the %FILENAME variable):
ft D:\home\source.lst bs2r1!lst jim,a1234ft,C'pwd'-ls="cmd /c erase %FILENAME"-rs="/PRINT %FILENAME,DELETE-FILE=YES"The text file
letter is sent to the login name jim with the password jimspass in the FTAM partner with the symbolic name ftampart.
ft letter ftampart!letter jim,,jimspassThe file
data is sent from a Windows computer pc123 to a Windows computer pc234 with the transfer admission topsecret and stored there under the name dat.txt . Then, as follow-up processing, the procedure evaluate is started in the remote system if transferred successfully. The procedure contains the file name dat.txt , the partner pc123 and the message number (0 for successful file transfer) as parameters. The parameters are specified using variables. If transfer is successful, the file is to be deleted in the local system.
ft data pc234!dat.txt topsecret-rs="evaluate.cmd %FILENAME %PARTNER %RESULT"-ls=*DELETEThe text file
locfile is to be sent to the Unix computer ux1. Here, it is to be stored under the login name charles with the password secret under the file name remfile. Then, as follow-up processing, the file is to be printed out if transferred successfully; if not, the prog program is to be started in the remote system. As parameters, the program receives the name of the source file and the message number. The parameters are specified using variables. If the request is not completed after 5 hours, it is deleted from the request queue. If a data connection already existed then error follow-up processing, i.e. the command prog %FILENAME %RESULT, is started in the remote system.
Unix systems:
ft locfile ux1!remfile charles,,secret -r=100\ -rs='lpr remfile' \ -rf='prog %FILENAME %RESULT' \ -ct=+0500
Windows systems:
ft locfile ux1!remfile charles,,secret -r=100 -rs='lpr remfile' -rf='prog %FILENAME %RESULT' -ct=+0500
If file transfer is not successful, e.g. because the record length was greater than 100 bytes, follow-up processing is executed as follows:
prog remfile 2210The file locfile is sent to the z/OS partner zospart. Here, the script PT (e.g. with a print job) is to be executed as follow-up processing under the user ID OPUSER.
Unix systems:
ft locfile zospart!remfile OPUSER,account,password \-rs="alloc dsname('OPUSER.PT')"Windows systems:
ft locfile zospart!remfile OPUSER,account,password-rs="alloc dsname('OPUSER.PT')"Example of specifying UNC names on Windows systems:
ft \\Win01\dir\file ux2!file sendfileExample of specifying domain user IDs in a remote Windows system:
ft file2 Win01!file2 mydomain\\miller,,secret(local Unix system)ft file2 Win01!file2 mydomain\miller,,secret (local Windows system)This example shows the use of restartable pre- and postprocessing commands. The
local directory dir, along with all its files, is to be transferred to a remote Unix computer using the symbolic name ftunix. The current version of openFT should also be running on the remote computer. After the transfer, dir should be available on the remote system under the ID to which the access admission copydir1 belongs. The directory dir must be located on the local computer in the home directory (on Unix systems: value of the $HOME variable). Please note that no file name prefix is allowed to be defined in the profile. Details on ft_tar are located in the section “ft_tar” .
ft "|&ft_tar -cf - dir" ftunix!"|&ft_tar -xf - " copydir1 -bThe directory
Docs is sent to the Windows system ftwin:
ft -d Docs ftwin!C:\Software\Docscopy miller,,secretThe remote directory C:\Software must exist. The directory Docscopy is created if it does not yet exist, otherwise it is overwritten (-o (overwrite) is default).