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:

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:

Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on Mar 17, 2022

TABLESPACE LOGGED NO-integrity available even Rollback

We wonder a new type LOGGED tablespace attribute, similar to LOGGED NO but without any consequences at Rollback processes.

Currently TABLESPACE LOGGED NO doesn´t log Row changes, but:

  • TS change to Icopy state at first Row change

  • TS change to RecPending, LPL at any Rollback operation

We suggest a new LOGGED NO-INTEGRITY tablespace option with assume Lose of data integrity for that TS, so it can remain operative (RW, Icopy) even at Rollback event.

We understand this is quite a controversial idea, but it would let in some few specific tables:

  • Avoid LOG-cost

  • Provide the chance to remain that row in the table even if the Unit-of-work is Rolled-back

Example of use: typical Log-Applications tables containing which transactions had been executed (date, user, data entrance). Currently is achieved controlling message-errors, by application programming but it generates huge Db2-LOG activity.

Thank’s for letting us contribute to Db2

Needed By Not sure -- Just thought it was cool