|
|
|
A store and forward transfer can be used to transfer a file indirectly when a destination system is not available. You can send a file to the mainframe, where it is stored temporarily. When the destination system becomes available, the file is automatically forwarded from the mainframe to the destination system.
This method is also used when you have two PU 2.0 devices that cannot communicate directly. They must use the mainframe as an intermediate device, because a UNIX or Linux system is not an intermediate device.
Note: A PU 2.1 device can handle direct transfers with another PU 2.1 device.
Example 1
In the following example, the xcom62 command is used. The file mytest.tst is sent to the intermediate z/OS node XCOMMVS2, which forwards the transfer to the remote Windows system defined in the endest destination member and into the file named MYTEST.TST.
xcom62 -c1 -f XIDEST=XCOMMVS2 REMOTE_SYSTEM=endest LOCAL_FILE=mytest.tst REMOTE_FILE=MYTEST.TST
There must be a destination member created and enabled for the remote system in the z/OS Dynamic Control Library in order for CA XCOM Data Transport to forward the transfer successfully.
Example 2
In the following example, the xcomtcp command is used. The file mytest.tst is sent to the intermediate z/OS node XCOMMVS2, which forwards the transfer to the remote Windows system defined in the endest destination member and into the file named MYTEST.TST..
xcomtcp -c1 -f XIDEST=XCOMMVS2 REMOTE_SYSTEM=endest LOCAL_FILE=mytest.tst REMOTE_FILE=MYTEST.TST
There must be a destination member created and enabled for the remote system in the z/OS Dynamic Control Library in order for CA XCOM Data Transport to forward the transfer successfully.
| Copyright © [set copyright date variable] CA. All rights reserved. |
|