CA Top Secret

Tuesday Tip: Debugging problems with Chorus Metrics.

  • 1.  Tuesday Tip: Debugging problems with Chorus Metrics.

    Broadcom Employee
    Posted 10-28-2014 11:34 AM

    If a site is experiences problems with the Chorus metrics such as from the Chorus UI, Metircs, 'Add New Metrics' is not showing 
    any 'Available Resources' for the system.


    This is related to the ESM and TSF(Time Series Facility).  The Time Series Facility (TSF) displays security performance data in CA

    Chorus. Statistics gathering is the process of collecting system statistics and sending data to TSF for a specific time frame, which is measured in

    seconds. Before you can view this data using TSF, statistics gathering(Real-Time STATG) in CA ACF2 or CA Top Secret must be started.

    The Real-Time STATG is a sub-task of the external security manager, not a stand-alone STC.


    For ACF2 the debug for CHORUS STATG can be set via the modify ACF2 CHRDEBG operator command ie. F ACF2,CHRDEBG(0|1|2|3|4). Details can be found in  the ACF2 Systems Programmer Guide.


    0:      Turn off all debugging
    1,2,3: Gather trace activity of the TCPIP calls from slightly detailed
              (1) to extremely detailed (3)
    4:      Write debugging messages in the syslog and write the STATG records
             in a pre-created and initialized (edited) data set ACF2.CHORUS.DATA
             PS,LRECL=140,BLKSIZE= 7000


    Details can be found in the CA ACF2 for z/OS Systems Programmer Guide in Appendix C: Console Operator Commands Summary, section 'Console Operator Commands Summary'.


    For Top Secret the CHORUSTSFDB control option starts or stops Time Series Facility (TSF) API debug tracing. Once you turn on the DEBUG option, CA Top Secret sends trace records to the DD of SYSPRINT under the CA Top Secret address space. Three levels of trace detail exist. This control option has the following format: CHORUSTSFDB(n)

    Debug level number
         0 = The debug tracing if off.
         1 = First level trace records written.
         2 = Second level trace records written.
         3 = Third level trace records written.

    Details can be found in the r15 CA Top Secret for z/OS Control Options Guide in Chapter 2: Specific Control Options section 'CHORUSTSFDB—Specify CA Chorus Time Series Facility (TSF) Debug Option'.