DB2 - L

Expand all | Collapse all

at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting record.

  • 1.  at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting record.

    Posted Sep 23, 2021 02:13 PM

    This is a question about at what point does CICS signal Db2 that the thread is to be closed.  
    Db2 will close the thread and write the accounting record. 

     

    Situation:

     

    DB2 SMF accounting records are showing subsecond Db2 time, and elapsed time of 30-50 seconds. 

    The caller is CICS, on the same LPAR. 

     

    Db2 is waiting for something before the thread is closed. 

     

    The possible candidates for the latency are:

    VSAM

    I/O subsystem

    Network

     

    DB2 systems programmer is trying to diagnose with the assistance of CICS Systems programmer. 



    ------------------------------
    williamgiannelliMe
    ------------------------------


  • 2.  RE: at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting record.

    Posted Sep 24, 2021 09:05 AM
    Do you have protected threads defined (DB2ENTRY)? I think that could skew the elapsed time since the threads are reused. I'm not a cics guy but we have protected threads in all our cics regions and they can skew some data.

    ------------------------------
    RussellPetersCentral Technology Services
    ------------------------------



  • 3.  RE: at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting record.

    Posted Oct 01, 2021 07:00 AM

    Hi William,

     

    sorry for being late here.

    If its CICS with thread reuse you are talking about, the DB2 accounting record is not written at the end of transaction – as it should be – but at thread reuse.

    Therefor you can't trust the content of field QWACESC or class1 elapsed time, respectively.

     

    HTH

    Thomas

     

    Thomas Weber

    IT.NRW

    An den Speichern 9

    48157 Muenster

    Phone: +49 211 9449 4089

    Mail: thomas.weber@it.nrw.de

     

     

     

     

     

    This is a question about at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting...

    DB2 - L

    Post New Message

     

    at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting record.

    Das Bild wurde vom Absender entfernt. william giannelli

    Sep 23, 2021 2:13 PM

    william giannelli

    This is a question about at what point does CICS signal Db2 that the thread is to be closed.  
    Db2 will close the thread and write the accounting record. 

     

    Situation:

     

    DB2 SMF accounting records are showing subsecond Db2 time, and elapsed time of 30-50 seconds. 

    The caller is CICS, on the same LPAR. 

     

    Db2 is waiting for something before the thread is closed. 

     

    The possible candidates for the latency are:

    VSAM

    I/O subsystem

    Network

     

    DB2 systems programmer is trying to diagnose with the assistance of CICS Systems programmer. 



    ------------------------------
    williamgiannelliMe
    ------------------------------

      Reply to Group Online   View Thread   Recommend   Forward  



     

     

    You are subscribed to "DB2 - L" as thomas.weber@it.nrw.de. To change your subscriptions, go to My Subscriptions. To unsubscribe from this community discussion, go to Unsubscribe.






  • 4.  RE: at what point does CICS signal Db2 that the thread is to be closed.   Db2 will close the thread and write the accounting record.

    Posted Oct 13, 2021 11:06 AM
    If CICS is not showing any delays, and this is solely a Db2 accounting thing, you may want to have your CICS admin take a look at the ACCOUNTREC parameter on your DB2ENTRY threads in the RCT.

    With protected threads, using a value such as NONE or TXID can cause all transactions on that thread to be cumulatively wrapped up into a single accounting record. Setting this to TASK will cause a record to be cut for each CICS task, whereas UOW will cut a record for each UOW (presumably each COMMIT).

    Note that if you're pushing a lot of work through, switching this value could cause major increases in the number of SMF 101s you're cutting, but you'll get more granularity.

    If there is a genuine processing delay, this won't help...but if that's the case, you'd see the delay in CICS records, as well as have screaming users.

    ------------------------------
    MarkWieczorkowskiUS Social Security Admin
    ------------------------------