FAQ

Verify that z/OS clients stream supported SMF records streamed to the Kafka cluster.

Note that several load-balancing mechanisms on the mainframe may distribute the work among different LPARs, CICS regions, etc.

Configure z/IRIS OpenTelemetry Java Instrumentation Extension

• For information on how to configure z/IRIS integration with OpenTelemetry, refer to Configuring IronTap OpenTelemetry integration

• Refer to Configure IronTap to find out more about EBCDIC code page configuration in IronTap is correct

z/OS applications might use code pages that differ from the system default code page.

• Refer to Troubleshooting OpenTelemetry integration for instructions on debugging OTEL integration issues

• Ensure agent logs are active

• Ensure IronTap logs are active

• Run the relevant business applications for which tracing or metrics are needed

• Attach the following files to your support ticket:

  • APM agent logs (regular log file as well as the metrics/traces log)

  • IronTap logs

• If IronTap receives SMF records via TCP, enable IronTap's 'SMF dumps' capability as described in Configure IronTap

• If IronTap streams SMF records via Kafka, use the Kafka Record Extractor tool to collect and archive SMF records

Answer: The mainframe administrator has to activate class 2 & 3 like in the following Db2 transaction trace-set:

-START TRACE(ACCTG) CLASS(1,2,3) IFCID(3) DEST(SMF) TDATA(CORRELATION)