Communications trace

If you get a message in the CPF3Exx range or the CPF91xx range when using Distributed Relational Database Architecture™ (DRDA^®) to access a distributed relational database, you should run a communications trace.

The following list shows common messages you might see in these ranges.

You can perform two types of communications traces. The first is the standard communications trace. The second is the TRCTCPAPP function. The TRCTCPAPP function provides for intelligible traces where IPSec or the secure sockets protocol has encrypted the data streams. It captures the data before encryption and after decryption. However, it also works well for getting traces of unencrypted data streams. It is required for getting traces of intra-system DRDA flows where LOOPBACK is used.

• Standard communications trace
  The communications trace function lets you start or stop a trace of data on communications configuration objects. After you have run a trace of data, you can format the data for printing or viewing. You can view the printer file only in the output queue.