As the use of sockets and secure sockets continues to grow to accommodate e-business applications and servers, the current serviceability tools need to keep up with this demand.
Enhanced serviceability tools allow you to complete traces on socket programs to find solutions to errors within socket and SSL-enabled applications. These tools help you and support center personnel to determine where socket problems are by selecting socket traits, such as IP address or port information.
The following table gives an overview for the each of these service tools.
| Serviceability tool | Description |
|---|---|
| Licensed Internal Code trace filtering (TRCINT and TRCCNN) | Provides selective trace on sockets. You can now restrict sockets trace on address family, socket type, protocol, IP address, and port information. You can also limit traces to only certain categories of socket APIs and also to only those sockets that have the SO_DEBUG socket option set. A Licensed Internal Code trace can be filtered by thread, task, user profile, job name, or server name. |
| Trace job with STRTRC SSNID(*GEN) JOBTRCTYPE(*TRCTYPE) TRCTYPE((*SOCKETS *ERROR)) | STRTRC command provides additional parameters that generate output that is separated from all other non-socket related trace points. This output contains return code and errno information when an error is encountered during a socket operation. |
| Flight recorder tracing | Sockets Licensed Internal Code component traces now include a dump of the flight recorder entries for each socket operation performed. |
| Associated job information | Allows service personnel and programmers to find all jobs that are associated to a connected or listening socket. This information can be viewed using NETSTAT for those socket applications using an address family of AF_INET or AF_INET6. |
| NETSTAT connection status(option 3) to enable SO_DEBUG | Provides enhanced low-level debug information when the SO_DEBUG socket option is set on a socket application. |
| Secure socket return code and message processing | Presents standardized secure socket return code messages through two SSL_ APIs. These APIs are SSL_Strerror() and SSL_Perror(). In addition, the gsk_strerror() provides similar function for GSKit APIs. There is also the hstrerror() API that provides return code information from resolver routines. |
| Performance data collection tracepoints | Provides a trace for the data flow from an application through sockets and the TCP/IP stack. |