Determining the Level of TP Traced

Your installation can customize a TP's processing for different audiences by defining different TP profiles for the same TP, and assigning a different level in each TP profile key. On an ATBTRACE START request, you cannot specify the level of TP to be traced, so the API trace data set might contain a mix of trace entries from various levels of the TP. You might be able to restrict tracing activity to specific users through the USERID keyword on ATBTRACE; but, depending on how your installation defines different audiences, that might not be enough to ensure that you are collecting trace data for only one level of the TP. If you need to distinguish the TP's processing by determining the TP level, use the following information together to match trace data with the correct TP level:

• The LU, TP, user ID, and FMH-5 information from the API trace entries, and
• The GROUPID and USERID values in the appropriate TP profiles.