Communications tracing
Communications tracing during TCP/IP initialization is controlled by the KDC_DEBUG environment variable.
To obtain the level of tracing required for the TCP/IP initialization
messages to be recorded in the RAS1 log, add the string KDC_DEBUG=Y to &rhilev.&rte.RKANPARU(KppENV).
You can also set the KDC_DEBUG variable dynamically by using the Service
Console bss1 command.
Possible values for KDC_DEBUG are:
- Y
- The data flow between the monitoring agent and the monitoring
server during TCP/IP initialization is recorded, including data packages sent
and received. When KDC_DEBUG=Y is active in the
environment during initialization of TCP/IP services for this address
space, you can confirm successful initialization of TCP/IP by looking
for one of the following messages in RKLVLOG:
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.tcp "KDE1I_OpenTransportProvider") Transport opened: socket/ip.pipe "KDE1I_OpenTransportProvider") Transport opened: socket/ip.udp - N
- The data flow between the monitoring agent and the monitoring server during TCP/IP initialization is not recorded. This is the default and the recommended setting for normal operation.
- D
- Full packet tracing plus STATE and FLOW tracing.
- M
- D plus INPUT and OUTPUT Help tracing.