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.

Add new parameter for REORG to designate different access behavior when REORG is in LOG/SWITCH phase

Let's say we have zparm IRLMRWT=15, and we have large tablespace REORG with SHRLEVEL(CHANGE) or (REFERENCE), the elapse time of LOG/SWITCH phase is greater than 15 seconds, this causes a lot of online workload timeout with -911. At that time the tablespace status is UTUT.

We know if we start the tablespace with ACCESS(UT), the online workload will receive -904 right away, but with UTUT, the online transaction will be forced to wait 15 seconds then timeout with -911.

The pain point is the users experience. They have to wait IRLMRWT before timeout otherwise application can return to users with more proper message right away.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 6 2020
  • Submitted
Why is it useful?
Who would benefit from this IDEA? all DB2 z/OS users can benefit this by providing better end user experience
How should it work?

1) the suggestion is to have a new REORG parameter to designate the new behavior to UTUT, so access to tablespace during LOG/SWITCH could be rejected immediately with -904

2)in this new behavior, application can respond to to -904 right away, eliminate the wait time(IRLMRWT), current wait time due to -911 behavior is unnecessary.

3) current option is either start tablespace with ACCESS(UT) or endure the wait time.

Idea Priority Medium
Priority Justification this request is from our banking application development and user experience improvement team
Customer Name TD Bank Canada
  • Attach files

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