Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
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