With introduction of APARs PH08708 and PH08431, messages DSNT376I are suppressed.
These are the sentences:
PH08708 -> When Timeout Exit is called, IRLM may flag that no DSNT376I message should be issued. In this situation IFCID 196 records will still be written but there will be no DSNT376I message on the console for these additional waiters being timed out.
PH08431 -> During this time period, the msgDSN376I will be suppressed while the IFC196
continues to be cut.
Now the db2 DB2MSTR joblog no longer reports all DSNT376I messages that correlate a timeout / deadlock with the contender and therefore it is difficult to quickly identify the origin of the contention.
The QM, in section 2 (View SQLCODE) implements the display of these but also in v330 (expanded with respect to v320) there is no reference with respect to the contender.
Is it possible to expand this function to get this information?
|Who would benefit from this IDEA?||All DB/2 QM administrators involved in problem analysis.|
How should it work?
Introduce in QM section 2 (View SQLCODE) the display of contender.
|Priority Justification||Because it is a very important help for customers.|
|Customer Name||SGS BancoBPM|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions