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 May 13, 2022

Error message improvement when failing to convert tablespace to UTS PBG

Recently we are converting our old segmented and simple tablespaces to UTS PBG.

When converting one of these tablespaces we got an abend and a DUMP showing reason code 00C90101.

We opended a case (TS009249828) and analyzing the DUMP DB2 lab concluded that "DM Trace shows a resource not available during the allocation of space for system segment. ".

SECQTY was defined as 0 and PRIQTY was only defined with 240.

We changed SECQTY to -1 and REORG tablespace succesfully converting it to UTS PBG.

We'd like to ask that in cases like these messages indicating space shortage, like REASON CODE 00D70027, was issued to advise us that there's no space available during conversion to UTS.That would provide a better diagnose for the problem, so it would be possible to quickly understand and fix the allocation parameters in order to convert those objects to UTS.

Needed By Not sure -- Just thought it was cool