This is an example for transfers between UNIX and Windows Nodes.
Sysopts are specific for each platform as the name "sysopts" already indicates. Connect:Direct UNIX supports different sysopts than Connect:Direct Windows does.
This leads to the point, that the FROM node can only evaluate the sysopts specified on the FROM side of a COPY step, whereas the TO node only reads the TO sysopts.
When copying a file from Connect:Direct UNIX to Connect:Direct Windows, both platforms are ASCII platforms and can do text conversion. The datatype (and xlate) sysopts parameter can be used, to enable or disable text conversion on each platform.
Specifying sysopts=":datatype=binary:" on the FROM side of the COPY step tells Connect:Direct UNIX not to translate the file before sending to the remote node.
Specifying sysopts="datatype(binary)" on the TO side of the COPY step tells Connect:Direct Windows not to translate the received file before writing to disk.
Connect:Direct's way of sysopts is very flexible and allows various combinations. For example some customers want the file to be converted from ASCII to EBCDIC or vice versa during the COPY step. They can achieve this by specifying datatype binary on one side and datatype text on the other side of the COPY step.
If you want to send a file from UNIX to Windows in binary mode and not rely on any defaults, then you should specify datatype binary on both sides of the COPY step, like:
*** It is recommended to specify sysopts, i.e. datatype, on both sides if you do copy between ASCII platforms. ***
Connect:Direct, All Releases
Sterling Integrator, Connect Direct interoperability, All Releases