|
|
|
Indicates the file on the remote computer to which the transferred data is being written. If you are creating the file (FILE_OPTION=CREATE), the file name must be consistent with the file naming conventions of the remote system. The local CA XCOM Data Transport system does not validate this name. The remote I/O system determines whether the file name is valid.
For wildcard transfers, use an asterisk (*) as a file name to indicate and to inform the receiving partner that multiple files will be sent.
Example
REMOTE_FILE=/PAYROLL/*.
If multiple files are sent and the user specifies a file name, all files received by the partner are written to that specified file as one single file.
An asterisk used to send files to an IBM mainframe system shows that all files are to be transferred to a partitioned data set (PDS).
For platforms that support it, you can specify a common file extension to append to each file name.
Example
REMOTE_FILE=/PAYROLL/*.TXT.
Note: For send file transfers only.
Range: 1 to 256 characters
Default: None
The name of the remote system that receives a file, job, report, or ping request.
For SNA/APPC protocols, the name is as specified in the SNA/APPC configuration of the local system. For RS/6000, the name is the LU6.2 Side Information record.
For TCP/IP protocols, the value can be the remote systems IP address, host name, or domain name.
Range: 1 to 256 characters
Default: None
Note: You can use symbolic variables with this parameter. For more information, see Symbolic Parameters in Configuration Files.
| Copyright © [set copyright date variable] CA. All rights reserved. |
|