IBM Data and AI Ideas Portal for Customers
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Additional Information
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
IBM Employees:
The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io
Hi, Janet.
Thank you very much for letting me that this idea is in fact a defect. I saw APAR PH45560 was opened. We'll keep waiting for its closure and we'll apply final PTF when available.
Regards,
Paulo R Petrachini
Dear Paulo, Our Db2 for z/os development team reviewed this idea again and determined this is a defect. Some one from our client success team will be contacting you soon to request that a new case be created, with our intent to resolve with a Db2 APAR.
Thank you,
Db2 for z/OS team
Dear Paulo, Thank you. Our Db2 for z/OS development team has reviewed your questions and provided the following feedback:
Q1: Is there any other impact using DDF_COMPATIBILITY= DISABLE_CLIENTAPPLNAME_TRUNCATION beyond that ones you've mentioned here
A1: This would impact the special register CURRENT CLIENT_APPLNAME so anything that references that special register will get impacted
Q2: One more question: do you think a value like DISABLE_CLIENTAPPLNAME_TRUNCATION for DDF_COMPATIBILITY could be retrofitted to DB2 12 or only would be available in a next DB2 version ?
A2: We may implement this as a V12 APAR.
Dear Janet,
One more question: do you think a value like DISABLE_CLIENTAPPLNAME_TRUNCATION for DDF_COMPATIBILITY could be retrofitted to DB2 12 or only would be available in a next DB2 version ?
Regards,
Paulo R Petrachini
Dear Janet,
Thank you for last comment.
At first sight, it sounds good, OK and enough to me have a new value for zPARM parameter DDF_COMPATIBILITY that makes possible to have CLIENT APPLNAME preserved WITH embedded blanks (DISABLE_CLIENTAPPLNAME_TRUNCATION).
Nowadays our use of RLF and system profiling monitoring is based on AUTHID. The situation related on this Aha-Idea is the first case where we would like to control amount of resources allowed based on Client application name.
Is there any other impact using DDF_COMPATIBILITY= DISABLE_CLIENTAPPLNAME_TRUNCATION beyond that ones you've mentioned here ?
Regards,
Paulo R Petrachini
Dear Paulo,
Our concern is making changes which impact existing users dependent on the current behavior, not only those who use RLF but also profile monitoring functions. To avoid affecting existing users we propose adding behavior where the CLIENT APPLNAME is preserved WITH embedded blanks and is activated by setting the existing Db2 system parameter DDF_COMPATIBILITY to a new value such as DISABLE_CLIENTAPPLNAME_TRUNCATION. This way existing users can keep the default first blank truncation behavior, while users that want the new behavior need to set DDF_COMPATIBILITY= DISABLE_CLIENTAPPLNAME_TRUNCATION. Note again this will affect both RLF and any system profiling monitoring behavior that use CLIENT_APPLNAME filters.
Can you please provide your comment on this proposal?
Thank you,
The Db2 for z/OS Development team
Dear Janet, thank you very much for analyzing our Aha! Idea. Sometimes we have offensor applications reaching Db2 on z/OS coming from distributed platform and we need to stop processing them as soon as possible. After avoiding that these applications reach Db2 for z/OS, we can identify who is in charge of them and understand what exactly is the problem, how to solve it and also asked them to use the API datasource.setClientProgramName to better identify with Db2 z/OS.
But we'd like some way to block them even when they are not using se the API datasource.setClientProgramName yet.
So we asked to RLFEUAN to be compared to QMDAAPPL that we believe has the complete CLIENT APPLANAME, containing blanks, always.
Thanks.
Dear Paulo, Thank you for submitting this Aha! Idea. Our development team has reviewed it and determined that they will not be modifying Db2 code. Instead, they are updating product documentation to suggest that applications having the client application name with embedded blanks use the API datasource.setClientProgramName to set the complete name (with embedded blanks). Then the same name can be used in the RLFEUAN column.
We do hope you find this helpful and hope that you will continue to submit your product enhancement ideas to us for thoughtful consideration.
Sincerely,
The Db2 for z/OS team