To create configuration files of your own for different types of transfers
The file xcom.cnf is renamed to configfilename.cnf and resides in your local directory
Note: The file name configfilename.cnf is used only as an example here.
The configfilename.cnf file is loaded in the editor.
It is not necessary to list all available parameters in a configuration file, because any unspecified parameters will use the defaults that are set in xcom.glb or the CA XCOM Data Transport daemon.
If you specify a configuration file, then xcom.cnf is not used. If you do not specify a configuration file, then CA XCOM Data Transport looks in xcom.cnf for parameter values.
Example 1
In the following example, CA XCOM Data Transport is invoked from the command line and a configuration file is specified.
xcom62 [ -cnumber] [ -f [configfilename]
[PARAMETER_NAME=value ...] ]
Replace number, configfilename, and PARAMETER_NAME=value with the desired transfer value, configuration file name and/or parameter name and values.
For the complete syntax and options for using xcom62 or xcomtcp, see Transferring Files in this chapter.
Example 2
In the following example, a regional office transfers its accounting records daily to the mainframe headquarters.
For this transfer, create a configuration file named account.cnf that contains the following parameter values:
FILEOPTION=REPLACE LOCAL_FILE=/usr/bills/july REMOTE_FILE=BILLS.JULY
Then specify this configuration file to use for the transfer as follows:
xcom62 -c1 -f account.cnf
| Copyright © [set copyright date variable] CA. All rights reserved. |
|