The API trace data set might contain trace entries for more than one conversation; because entries are arranged by time stamp, entries for the conversations are probably interleaved. Because most API trace entries contain the conversation ID, which is unique for each conversation, you can sort the trace entries by conversation ID to consolidate all the entries for a particular conversation. The only trace entries that do not contain such IDs are those for:

• APPC/MVS allocate queue services, and
• Services that do not directly affect the conversation, such as the APPC/MVS Get_TP_Properties service.