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.

Table 1. Communications trace messages

MSG ID	Description
CPF3E80	DDM data stream syntax error.
CPF91xx	DDM protocol error.
CPF3E83	Invalid FD0:CA descriptor.
CPF3E84	Data mismatch error.

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.

 

Parent topic:

Getting data to report a failure

 

Related concepts

Connection security protocols for DDM and DRDA
Job tracing

 

Related tasks

TCP/IP communications trace