Application data is data that is associated with a connection through the use of the SIOCSAPPLDATA ioctl socket command. The SIOCSAPPLDATA IOCTL enables applications to associate 40 bytes of application-specific information with TCP sockets the applications own. This application data can also be used to identify socket endpoints in interfaces such as Netstat, SMF, or network management applications. See the Application data appendix in z/OS Communications Server: IP Programmer's Guide and Reference for detailed information about all supported application data.
Table 1 lists new and changed application data.
| Record type | Record field | Release | Description | Reason for change |
|---|---|---|---|---|
| FTP client application data for the control connection | Bytes 24-25: Security level | V2R1 | A new value, 12, indicates the TLS protocol is TLSV1.2. | AT-TLS support for TLS v1.2 and related features |
| Bytes 26-27: Cipher | V2R1 | A new cipher value of 4X indicates that the cipher is four bytes and must be obtained from offset 30. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 26-27: Cipher | V2R1 | A new cipher value of 4X indicates that the cipher is four bytes and must be obtained from offset 35. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 30-33: Four byte cipher | V2R1 | The four byte cipher value. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 35-38: Four byte cipher | V2R1 | The four byte cipher value. | AT-TLS support for TLS v1.2 and related features | |
| FTP server application data for the control connection | Bytes 24-25: Security level | V2R1 | A new value, 12, indicates that the TLS protocol is TLSV1.2. | AT-TLS support for TLS v1.2 and related features |
| Bytes 26-27: Cipher | V2R1 | A new cipher value of 4X indicates that the cipher is four bytes and must be obtained from offset 29. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 26-27: Cipher | V2R1 | A new cipher value of 4X indicates that the cipher is four bytes and must be obtained from offset 33. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 29-33: Four byte cipher | V2R1 | The four byte cipher value. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 33-36: Four byte cipher | V2R1 | The four byte cipher value. | AT-TLS support for TLS v1.2 and related features | |
| Application data format for Telnet | Bytes 32-33: Security level | V2R1 | A new value, 12, indicates that the TLS protocol is TLSV1.2. | AT-TLS support for TLS v1.2 and related features |
| Bytes 34-35: Cipher | V2R1 | A new cipher value of 4X indicates that the cipher is four bytes and must be obtained from offset 33. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 37-40: Four byte cipher | V2R1 | The four byte cipher value. | AT-TLS support for TLS v1.2 and related features | |
| Application data format for CSSMTP | Bytes 21-22: Security level | V2R1 | A new value, 12, indicates that the TLS protocol is TLSV1.2. | AT-TLS support for TLS v1.2 and related features |
| Bytes 23-24: Cipher | V2R1 | A new cipher value of 4X indicates that the cipher is four bytes and must be obtained from offset 33. | AT-TLS support for TLS v1.2 and related features | |
| Bytes 26-29: Four byte cipher | V2R1 | The four byte cipher value. | AT-TLS support for TLS v1.2 and related features |