See information about the latest product version
Initiating a managed file transfer using IBM Sterling Connect:Direct
Use a CDOutput node to send a file from a specified directory on your primary Connect:Direct® server (PNODE) to a filename and directory on a secondary Connect:Direct server (SNODE).
Multiple CDOutput nodes can be deployed to the same execution group, or to different execution groups in the same broker. CDOutput nodes can send one file per transfer. Each file can have multiple records; each record can have multiple elements. Transfers from the CDOutput node are non-blocking.
Complete the following steps:
- The file is constructed in accordance with the values set in the properties of the CDOutput node.
- The file is staged in the local file system and then a command is sent to the Connect:Direct server to cause the transfer to occur.
- If a file of the same name exists in the selected directory on
the secondary Connect:Direct server, the
processing of the existing file is determined by the value of the Disposition property;
in this example, the file is replaced.
Once the transfer has completed the local, staged file is deleted.
- Secondary Connect:Direct server (SNODE)
- Process name
- Accounting data
- Destination file directory
- Destination file name
- Copy from options
- Copy to options
You have complete control of the Copy statements.
LocalEnvironment.Destination.CD.Copy.To.Option.PERMISS = '777'
causes IBM® Sterling Connect:Direct to set the permissions on the
destination file to 777 (or RWX RWX RWX)
if the destination file is on a UNIX operating
system, or within Unix System Services on z/OS®. However, if you enter an incorrect format, a syntax error is detected when the process script is submitted and this causes an error to be thrown in the node.
LocalEnvironment.Destination.CD.Copy.To.Option.PERMISS = '7xddd'
causes a syntax error because '7xddd' is
not of the format nnn. When an error occurs the process
script is available in the exception thrown and the user trace.