Using the KDC_DEBUG environment variable

Communications tracing during TCP/IP initialization is controlled by the KDC_DEBUG environment variable.

To obtain the level of tracing required to have these TCP/IP initialization messages echoed to RKLVLOG, the string KDC_DEBUG=Y must be added to member KDSENV of RKANPARU (or the appropriate initialization member named KppENV, where pp is the two-letter prefix associated with the monitoring agent, such as S3 for OMEGAMON® for Storage).

Possible values for KDC_DEBUG are:

Value Description
Y

When this variable is set to Y, then the data flow between the monitoring agent and IBM® Tivoli® Management Services components (such as Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server ) during TCP/IP initialization is recorded, including data packages send and received. When KDC_DEBUG=Y is active in the environment during initialization of TCP/IP services for this address space and any of the following messages are present, then TCP/IP initialization was successful. If KDC_DEBUG is set to Y and none of these messages appear in RKLVLOG, then initialization of the TCP/IP service failed:

"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 Tivoli Management Services components during TCP/IP initialization is not recorded. This is the default and the recommended setting for normal operation.

For OMEGAMON Monitoring Agent on z/OS, you can use this environment variable during the TCP/IP service initialization to diagnose connectivity problems with application layers such as telnet and FTP, and with the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and the Tivoli Enterprise Monitoring Agent or Agents.

The KDC_DEBUG environment variable controls all DCS communications tracing. Use the KDC_DEBUG parameter to track DCS errors or activity between the agent and the Tivoli Enterprise Monitoring Server. These usage notes apply:
  • You cannot dynamically alter KDC_DEBUG tracing.
  • Place the KDC_DEBUG environment variable statement immediately after the KDC_FAMILIES environment variable.