Identifying application data

User-defined application data is comprised of 40 bytes of data that is used to identify the endpoint with the macro API sockets application. The application data can be obtained from the following resources:

Netstat reports

The information is displayed conditionally by using the modifier APPLDATA on the ALLConn/-a and COnn/-c reports, and unconditionally on the ALL/-A report. For more information about the Netstat ALL/-A report, Netstat ALLConn/-a report, and the Netstat COnn/-c report, see z/OS Communications Server: IP System Administrator's Commands

SMF 119 TCP connection termination record

For more information about the application data written on the SMF 119 record, see Type 119 SMF records.

Network management interfaces

The following network management interfaces (NMIs) support application data:

The SYSTCPCN service of the Real-time TCP/IP network monitoring NMI provides application data in SMF 119 TCP connection termination records.
The GetTCPListeners and GetConnectionDetail requests of the TCP/IP callable NMI (EZBNMIFR) provide application data and enable callers to filter on application data.

Guidelines:

The application is responsible for documenting the content, format, and meaning of the ApplData string that associates it with sockets that it owns.
The application should uniquely identify itself with printable EBCDIC characters at the beginning of the string. Strings beginning with 3-character IBM® product identifiers, such as TCP/IP EZA or EZB are reserved for IBM use. IBM product identifiers begin with a letter in the range A - I.
Use printable EBCDIC characters for the entire string to enable searching with Netstat filters.

Tip: Separate application data elements with a blank space for easier reading.

The following z/OS® applications support application data registration for their connections:

The z/OS IP CICS® socket interface and listener
The z/OS TN3270 server application data