IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

DSNT376I messages reintroduced

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?

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 29 2019
  • Will not implement
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.

Idea Priority High
Priority Justification Because it is a very important help for customers.
Customer Name SGS BancoBPM
  • Attach files
  • Admin
    May Chu commented
    17 Jul 01:10am

    This feature is in OMPE and will not be implemented.

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 "anonymous@euprivacy.out" 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