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 message don't supply total information to solve the problem analisys

I found that as soon as the DB2 Lock Escalation message occurred (DSNI031I), DB2 seems to begin rejecting the ESS SQL calls against this tablespace, *immediately* without waiting the DB2 lock timeout interval.            
This probably explains why there is no DSNT376I message.                
The queuing is caused by IMS abending the transaction U0777 and then putting it back on queue to be reprocessed, where the same sequence will certainly happen again.
Actually, immediate rejection is better than waiting the timeout interval, but the lack of any DB2 message to indicate what's going on makes it hard operationally, to determine corrective action.  

 

This action will get benefits on problem detection, MIPS reduction and business disponibility.

 

Itau Unibanco S/A 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 14 2019
  • Needs more information
Idea Priority High
  • Attach files
  • Admin
    Janet Figone commented
    14 Aug 04:57pm

    Hi Paulo, Thank you. I have asked the Db2 developer assessing this Idea if there is any further clarification needed.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    14 Aug 02:32pm

    Hi, Janet.

    Did you see and analyze/understand our last comment (posted in 20 Feb) ?

    Our focus is on the lack of messages that could link the timeouts occurring on IMS and abnormal EOTs (DSN3201I) occuring on DB2 to the lock escalation. We would appreciate if we had messages that could link these events.

    What is the further information you need once this IDEA is NEED MORE INFORMATION status.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    20 Feb 10:13pm

    Janet, the message DSNT376I doesn't come up at all. The issue is that we don't have a DSNT376I or DSNT501I message so we don't see any timeouts on our side even though IMS gets a timeout (SQLCODE -911). The only message we get is DSN3201I (abnormal EOT) wich makes it difficult to link the lock escalation with a timeout on IMS.

    This RFE was opened because of the PMR 29472,228,631.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    10 Jul, 2019 07:24am

    Hi
    I thought that this is fixed or I confuse something

    PMR 89589

    Messages DSNT408I with SQLCODE -911, Reason 00C9008E and resource type 00000210 but no timeout message in MSTR Joblog
    Hi Mr Hagmann,
    The PTF (v12) UI63124 is now available.
    I think the actions on this pmr are now completed, but please let me know if I miss something?
    Thanks very much.
    Best regards, Karen

    Von: cae4c35ac7ce10f1f7c9625e-bigblue@iad-prod1.mailer.aha.io
    Gesendet: Mittwoch, 10. Juli 2019 01:01
    An: HAGMANN Manfred
    Betreff: Janet Figone responded to idea DB24ZOS-I-919 DSNT376I message don't supply total information to solve the problem analisys

  • Admin
    Janet Figone commented
    9 Jul, 2019 11:00pm

    Db2 for z/OS development has begun reviewing this Idea, and would like to request some additional information.

    1. Is the problem that the T376I message does not provide enough information for problem determination?

    2. Or is that it does not come up fast enough?

    It seems the customer systems see the DSNI031I message and wait for the T376I message to come up. Some clarification on the scenario and what would help with the problem determination would be helpful.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Mar, 2019 01:02pm

    I agree with Nelson Duval comment, this implementation will help us.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    18 Mar, 2019 11:12am

    This implementation is very important for problem determination and correction.

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