How to interpret the CICS Transaction Gateway response time fields "In CICS Time" and "In CTG Time" in MainView for CICS Performance Reporter Language (PRL) output

Version 2
    Share:|

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


    PRODUCT:

    MainView for CICS


    APPLIES TO:

    MainView for CICS



    QUESTION:

    MainView for CICS - all supported versions

    Question about response time fields in CTG history records.

    We run a CMRPRL to list the CICS Transaction Gateway (CTG) response time fields CTGGTWT, CTGGT001, CTGCICST and CTGCT001. CTGGT001 and CTGCT001 are fields in sub-segments of the record.

    IN CTG IN CTG IN CICS IN CICS
    TIME TIME TIME TIME
    -------------- -------------- -------------- --------------

    0.015000 0.009000 0.542000 0.542000
    0.005000 0.001000 0.083000 0.083000
    0.005000 0.001000 0.067000 0.067000
    0.006000 0.001000 0.117000 0.117000
    0.003000 0.000000 0.001000 0.001000
    0.002000 0.002000 0.275000 0.275000
    0.002000 0.002000 0.215000 0.215000
    0.002000 0.002000 0.056000 0.056000
    0.001000 0.001000 0.219000 0.219000
    0.000000 0.000000 0.114000 0.114000


    We thought that, as we only have one sub-segment , CTGGTWT and CTGGT001 must match (as CTGCICST and CTGCT001 do) , but that’s not happening . Why?
    How do we interpret these fields?


    ANSWER:

     

    Legacy ID:KA422988

      

    The figures you are seeing can be explained by an overhead introduced during the final call of an Extended LUW or an XA task. For Sync-on Return tasks, this overhead should not appear.

    To explain further, for Extended LUW and XA tasks (which may enter CICS several times), there is final call to the gateway when the ‘transaction’ ends. This call terminates the transaction with a kind of two-phase commit.

    But note that there is no program associated with the request. That’s because the gateway isn’t really going to CICS to perform another piece of work. When we account for calls to CICS from the gateway, we group them based upon a pair, the region/program.

    Additionally, since we use floating point numbers, there may be some minor differences due to rounding.

      
    Related Products:  
       
    1. MainView for CICS

     


    Article Number:

    000023595


    Article Type:

    FAQ/Procedural



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