IT13168: (FTPS) GETTING TLS SECURITY MECHANISM NEGOTIATION FAILED WHEN SENDING 0 BYTE FILE

3.4.1.8-SterlingSecureProxy-Windows-if0009
3.4.1.8-SterlingSecureProxy-SolarisSPARC-if0009
3.4.1.8-SterlingSecureProxy-Linux-if0009
3.4.1.8-SterlingSecureProxy-Linux_S390-if0009
3.4.1.8-SterlingSecureProxy-HP-if0009
3.4.1.8-SterlingSecureProxy-HP-IA-if0009
3.4.1.8-SterlingSecureProxy-AIX-if0009

APAR status

• Closed as program error.

Error description

• - SSP sends the RETR command back to SI and a data channel is
  established with SI. But because there is no data to send SI
  just closes the data channel.
  - SSP then closes the control channel socket back to the
  mainframe with no information (not even a zero byte file) when
  it should open a data channel back to the mainframe but it
  doesn't.
  Even though there isn't any data SSP should complete the data
  channel connection back to the mainframe client instead of just
  closing the control channel socket.
  

Local fix

• STRRTC - 479958
  RJ/RJ
  Circumvention:
  Update to latest SSP Build
  

Problem summary

• When executing an FTP command that results in no data being
  returned on the data channel (such as retrieving an empty
  file), it is possible that a TLS handshake error will occur
  while trying to secure the data stream connection.
  

Problem conclusion

• Added code to ensure the handshake completes before closing the
  data stream connection.
  

Temporary fix

• Fix for RTC 479958.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR SECURE PROX

• Fixed component ID

  5725D0300

Applicable component levels