FTP Communications Profile with *SSL as the Secure Connection Type is not converted when upgrading to 3.6 Release, the default of *DFT is moved into the value on this parameter.
During upgrade to 3.6 release the FTP communication porfile with *SSL as the Secure Connect Type is not converted, the default of *DFT is moved into the value on this parameter.
Installation/Upgrade conversion issues
Ensure the Secure Connection Type is *SSL (rather than *DFT).
If you are using a FTP Communication Profile with *SSL as the Secure Connection Type after upgrading to 3.6 release.
From the main menu
- navigate to "Work with Communication"
- position to that Communication Profile,
- Enter 2 (revise), Second Screen, and change the Secure Connection Type to *SSL (rather than *DFT).
NOTE: ONLY do this if you are using *SSL in your older release that you converted from.
This will be fixed in a higher cumulative fix point release of v3.6