Special considerations when using SSL encryption support
Because data flowing across the connection between the client and the server is encrypted, the data field in the packet trace is also encrypted after SSL handshaking is completed. If problem determination requires seeing Telnet handshake or user data, you also need to run Component Trace to see the decrypted data field. When starting Component Trace, specify options=(TELNET) and use IPCS to format the Component Trace. For more information about Component Trace, see TCP/IP services traces and IPCS support.
The Telnet Component Trace records contain the connection ID in the CID field. The connection ID in the trace corresponds to the connection ID output of the connection display command. Use this field to locate records related to the client in question. After an LUname has been assigned, the Component Trace User field shows the LUname, providing additional data for locating your client.
- SKSCINIT Succeeded
- SSL handshaking completed and subsequent data on this connection is encrypted.
- Receive Data from Client
- The Data from Client field of this record contains the decrypted data coming from the client.
- Send Data to Client
- The Data to Client field of this record contains the decrypted data going to the client.
MVS181 TELNET 70010004 12:49:06.354966 Send Data to Client
HASID..002A PASID...002A SASID..002A MODID..EZBTTSND
TCB....00000000 REG14...89D37F40 USER...TCPM1011 DUCB...0000000D
CID....092552C4 SEQ.....000024BE
...
...
ADDR...00000000 08167AB0 LEN....00000004 Number of Bytes Sent
+0000 0000002C │ .... │
ADDR...00000000 7F687950 LEN....0000002C Data to Client
+0000 F5C1115D 7F1D4011 40401DC8 C9D2D1F5 │ 5A.)". . .HIKJ5 │
+0010 F6F7F0F0 C140C5D5 E3C5D940 E4E2C5D9 │ 6700A ENTER USER │
+0020 C9C44060 1D4011C1 5013FFEF │ ID -. .A&... │