Impacts with changes of the START TRACE command.

book

Article ID: 127902

calendar_today

Updated On:

Products

CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

***** the info from the IBM *****
If the CLASS keyword is omitted from the START TRACE command when the monitor trace is started, the class 1 and 11 are activated. (In the DB2 V10, only the class 1 is activated if the CLASS keyword is omitted.) So, a IFI application may be affected with this change, because the trace records will be increased in the IFI application with such TRACE command.
********* end *********************

I will upgrade their DB2 from V10 to V11. We got the following info on the DB2 V11 upgrade, from the IBM Japan.
***** the info from the IBM *****
If the CLASS keyword is omitted from the START TRACE command when the monitor trace is started, the class 1 and 11 are activated. (In the DB2 V10, only the class 1 is activated if the CLASS keyword is omitted.) So, a IFI application may be affected with this change, because the trace records will be increased in the IFI application with such TRACE command.
********* end *********************
I want to know whether the CA-DB2 tools can be affected by this change.

 

Environment

MF, Mainframe, DB2, CA-DB2 tools,

Resolution

You can read how DB2 work with Monitor Classes in the following link for CA SYSVIEW for DB2 Release 19.0 manual:
DB2 Trace Type
https://docops.ca.com/ca-sysview-db2/19/en/configuring/data-collector-dc/how-dc-uses-db2#HowDCUsesDB2-AboutTraces

Monitor Trace is always started with MON CLASS 1.

We have checked in our D11A (DB2 11 NFM) env with several CA SYSVIEW for DB2 Data Collectors started the output for the
-DISPLAY TRACE (*) command and in all of them Traces were started with MON CLASS 01.