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.
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.
|Priority Justification||this request is from our banking application development and user experience improvement team|
|Customer Name||TD Bank Canada|
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 "firstname.lastname@example.org" 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