How do you activate DBCTL monitoring in the CICS Analyzer so that the CICS data elements derived from the CMF DBCTL user area are populated?
Environment
Release: Component: MCIC
Resolution
CICGENIN provides the OPTION statement to indicate which groups of data elemnets are to be kept in the database. Inspect the CICGENIN OPTION statment for the keyword NODBCTL (default value). This indicates to the CICS Analyzer to not keep DB2 Data Base Control (DBCTL) data elements. Change the keyword to DBCTL and run a sp.CNTL(CICCGEN). The CGEN adds the element(s) to the sp.MACAUTOS(fffKEEP) members so after running the CGEN you can check CSUKEEP to verify that the database control data elements are present (CSUDBTOT for example). If after the CGEN you are finding that the new elements are present but they are empty after the next daily cycle then check with your CICS group as they will need to activate DBCTL on the CICS side by adding it to the MCT (Monitor Control Table).
If the DBCTL user area has not yet been defined by the CICS systems programmer, then it will not be in the input records.
To determine whether DBCTL exists on input, one could check the data dictionary file DETAIL.CICCDC01 to see whether there are entries that enable the readup of DBCTL. A quick check could be done by the following:
//S1 EXEC MICSSHRx //SYSIN DD * DATA DBCTL; SET DETAIL.CICCDC01; IF SUBSTR(CDCENTRY,1,5) EQ 'DBCTL' THEN OUTPUT; PROC PRINT;
If this job does not select any entries, it would indicate that DBCTL needs to be activated on the CICS side.