The conversion from IBM Sterling Connect:Direct (C:D) is based on having input C:D process files that contain all the file transfer logic (such as source host, target host , file to transfer etc.) and reside in your file system.
If C:D file transfers are triggered within scripts, obtains file transfer parameters from outside scripts, and dynamically creates C:D process files you need to replace all the jobs that calls those scripts with the File transfer job template that use those parameters.
The following table describes how the Conversion Tool converts job types, files, statements and parameters from IBM Sterling Connect:Direct to Control-M:
IBM Sterling Connect:Direct |
Control-M |
|---|---|
Process Files |
SMART folders containing Managed File Transfer (MFT) jobs (and Dummy jobs) |
COPY statements |
MFT jobs |
RUN statements |
Dummy jobs |
SUBMIT statements |
Dummy jobs |
GOTO, IF, EIF, EXIT, SYMBOL statements |
Not converted and must be manually handled. The Conversion Tool issues a warning message if those statements exist in the Process files. |
COPY FROM and TO parameters |
MFT FTP-LPATH1 and FTP-RPATH1 job parameters (the source and destination locations on the host computers) corresponding to which one is defined as the PNODE (Primary node) and SNODE (Secondary node) in IBM Sterling Connect:Direct. |
PNODE (Primary node) and SNODE (Secondary node) |
The conversion specifies a connection profile name consisting of a combination of a PNODE and SNODE separated by a dash. The user needs to create the Connection profiles in the Control-M Configuration Manger and chose them manually from the MFT jobs created by the Conversion Tool. |
Parent Topic |