Skip to Main Content
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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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


Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on May 30, 2022

QUERY_HASH strangeness

Hi!

I am starting to use the new column in SYSPACKSTMT called QUERY_HASH and I have noticed that for different SQL Statement texts I am getting the same hash. I am aware that there is no guarantee of uniqueness but what worries me is that my SQL is short and simple with one character plainly different. As the hash is 16 bytes hex I was surprised to see the same HASH being generated. Here are the two statements in their entirety:

DELETE FROM MDB2VRSA WHERE DATABASE = : H AND TABLESPACE = : H AND PARTITION = : H AND DBID = : H AND PSID = : H

and

DELETE FROM MDB2DRSA WHERE DATABASE = : H AND TABLESPACE = : H AND PARTITION = : H AND DBID = : H AND PSID = : H


I see that the table names are different, but both of these hash to

x'61760D695245353837532743555F4D22'


My idea would be to make the hash process a little bit more "robust"...or at least document which type of hash method is being used.

Thanks

Roy

Needed By Not sure -- Just thought it was cool