KB Article #178697

cft send failed with CFTH11E and CFTT75E error messages

Problem

CFT to IBM Express (Connect:Express)


PeSIT SSL


No issue receiving a file from IBM Express to CFT


CFTH11E Error Opening session <PART=MYPARTNER EV=VNRELI ST=CN0022>

CFTT75E connect reject <IDTU=A0000001 PART= MYPARTNER IDF=TEST IDT=E1417322 302 R 0 2f2>


CFTH11E stand for “Problem opening a PeSIT session with a remote partner after establishing the network session.”


CFTT75E stand for “The connection request was rejected by the partner.”


The remote identify an error with the length of the PeSIT logon string 28 chars instead of the expected 24 ?

Resolution

the SSL handshake is ok, then, starts the PeSIT session,where indeed,

the logon string (sent when logon=yes is set into the CFTPROT) is

normalized to 24 chars long.


If the remote partner gets a 28 chars long logon string, it may be due to the TCP Headers when in PeSIT SSL.


An option exists to add or not the length bytes indicators L1 & L2.


This option is related in CFT to the suffix COMP in the parameter VERSION of the macro CFTSSL.


You should give it another try after having changed VERSION = 'TLSV1COMP' to VERSION = 'TLSV1'.


In the reported issue, the connection request is rejected by the partner at the PeSIT logon string checking that is too long because L1, L2 indicators bytes are not expected.


Note: that option exists also on the IBM Express (Connect:Express), it is known as the TCP/IP Headers (probably in the session table).