There are three types of traces in the DB2 DISPLAY TRACE command from MainView for DB2.

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView for DB2


    APPLIES TO:

    MainView for DB2



    PROBLEM:

     

    MainView for DB2 11.1.00
    MainView for DB2 10.1.00
    MainView for DB2 9.2.00

      

     

      

    When a user issues the DB2 DISPLAY TRACE command as follows, there are 3 types of traces from MainView for DB2:

    -DIS TRACE(*)
    DSNW127I + CURRENT TRACE ACTIVITY IS -
    TNO TYPE CLASS DEST QUAL IFCID
    01 MON 01 OP1 NO 001,002,003,090,172,196,239,402
    02 MON 01,30 OP7 NO 001,002,003,031,090,102,103,104,105
    02 106,107,125,140,172,173,196,199,202
    02 203,204,205,206,207,208,209,210,225
    02 230,239,330
    03 ACCTG 01,02,03,05, OP7 NO 003
    03 07,08,10
    *********END OF DISPLAY TRACE SUMMARY DATA*********
    DSN9022I + DSNWVCM1 '-DIS TRACE' NORMAL COMPLETION
    DSN
    END



    The traces are the same, except the Destination and  a few IFCID entries are different.

    Why not consolidate the three types of traces into just one ACCTG trace type?




     

     


    SOLUTION:

     

    Legacy ID:KA417451

      

    These three types of traces come from different started tasks for MainView for DB2.

    DSNW127I + CURRENT TRACE ACTIVITY IS -
    TNO TYPE CLASS DEST QUAL IFCID
    01 MON 01 OP1 NO 001,002,003,090,172,196,239,402
    02 MON 01,30 OP7 NO 001,002,003,031,090,102,103,104,105
    02 106,107,125,140,172,173,196,199,202
    02 203,204,205,206,207,208,209,210,225
    02 230,239,330
    03 ACCTG 01,02,03,05, OP7 NO 003
    03 07,08,10
    *********END OF DISPLAY TRACE SUMMARY DATA*********
    DSN9022I + DSNWVCM1 '-DIS TRACE' NORMAL COMPLETION
    DSN
    END


    Trace number 01 is started by the MainView for DB2 BBI-SS PAS and uses Destination Buffer OP1. The data collected is used for the various MainView for DB2 views and the data you see in the MVDB2 Summary Traces..

      

    Trace numbers 02 and 03 are started by MVDB2/DC (Data Collector component of MainView for DB2) and both utilize the same DB2 Destination Buffer OP7. The data collected is displayed in the MVDB2/DC trace and views on the EZDEVENT Menu.

      

     

      

     

      

     

      

     MainView for DB2 and MVDB2/DC run in different started tasks and this requires the use of different Destination Buffers.

      

    Note that the OPx for MON trace started by the MainView for DB2 BBI-SS PAS connection and theMVDB2/DC can vary, dependent on which OPx  buffers are available for the DB2 Subsystem that is being monitored.  MainView for DB2 attempts to use OP1 but if it is not available, it checks the next available Destination Buffer: OP2, OP3 , etc. until it finds one that can be used. The similar procedure will be used for MVDB2/DC as well. However, in this case the MVDB2/DC tries to start the MON/Accounting Trace with the OP7 Destination Buffer and goes to the next lower Destination Buffer if OP7 is not available at the time the MVDB2/DC is started.

      

    You have the option to turn on/off ACCTG classes only.  

      

    For MVDB/DC, you can turn off accounting trace for MVDB2/DC by setting the following to N:

    - DOMPLEX Parameters Parameters that apply to entire DOMPLEX

      

     

      

    Collect IFCID 3 in accounting trace. . . N (Y=Yes,N=No)

    Or you can turn off the following accounting classes. Accounting class 01 will be on.

    - DB2 Monitor List (3) DB2 Sub-systems to be monitored

    Class 2-In-DB2 elapsed timing info. . N (Y=Yes,N=No)
    Class 3-DB2 suspend timing info . . . N (Y=Yes,N=No)
    Class 5-Time spent doing IFI requests N (Y=Yes,N=No)
    Class 7-DB2 events (packages, DBRMs). N (Y=Yes,N=No)
    Class 8-Wait time for packages. . . . N (Y=Yes,N=No)
    Class 10-Optional package detail data. N (Y=Yes,N=No)

      
    Related Products:  
       
    1. MainView for DB2

     


    Article Number:

    000096810


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles