IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 (https://ideas.ibm.com).


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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

ADD A NEW IDEA

General DB

Showing 73

IMS LOCKMAX USERMOD to disallow or restrict the use of the value '0' and provide a min to max range for LOCKMAX values

Wellpoint needs a LOCKMAX parm usermod to allow us to restrict or disallow the use of the value '0' in BMP EXEC parms or in a PSBGEN. Also would like to have the option to specify a minimum and maximum range of values for LOCKMAX
over 9 years ago in IMS Database Manager / General DB 2 Not under consideration

CLEANUP.RECON keyword to not delete ALLOC records with no DEALLOC time

It would be useful to have a keyword for the CLEANUP.RECON DBRC command that would cause it *not* to delete ALLOC records that don't have a DEALLOC time, even if the ALLOC record is older than the RETPRD specified. Similar to how there currently i...
almost 10 years ago in IMS Database Manager / General DB 1 Not under consideration

IMS code in CICS checks for level mis-match

Add checking to ensure the IMS code loaded in CICS via the DRA table and the server it has connected to match.
about 10 years ago in IMS Database Manager / General DB 1 Not under consideration

HALDB ALTER for CI change only

V13 HALDB ALTER. I would like to be able to use the HALDB ALTER to change the DB CI size without having to make a DBD change as well. This will allow for DB tuning without down time for the application.
about 11 years ago in IMS Database Manager / General DB 2 Not under consideration

Automatic detection of current RRDS by RDDS Extraction utility. (old MR092111406 )

Customer would like to create a copy of the old IMSGEN macro based on the latest information contained in his IMS sistem and stored into DRD RDDS Data set; these will be used in case of problems to recover the subsystem.The IMS RDDS Extraction uti...
over 11 years ago in IMS Database Manager / General DB 4 Not under consideration

HALDB partition keys should not be deleted when changing from PARTSEL to HIKEY

When changing from PARTSEL to HIKEY any partition keys already defined in RECON should either generally be left as they are or there should at least be an option to determine whether they should be left or deleted.
over 11 years ago in IMS Database Manager / General DB 3 Not under consideration

FDBR should not abend as a result of temporary loss of the lock structure.

1. Prevent FDBR from abending due to loss of the lock structure.or2. Make it possible to restart FDBR.or3. Provide an ERE light for IMS which would do backout, release locks, resolve DB2 in-doubt threads and then end immediately (or controlled by ...
over 11 years ago in IMS Database Manager / General DB 1 Not under consideration

FDBR regions should keep LOG buffers in Extended Private instead of ECSA

Fast Database Recovery regions currently use ECSA for log buffers. As these are not typically used during normal tracking, and only needed during a backout scenario, they should be allocated as Extended Private to allow additional ECSA contraint r...
almost 10 years ago in IMS Database Manager / General DB 1 Not under consideration

IJPMC0314-1682 Improve Delete.DB processing for Parallel Recon Access

SUBMITTER SECTIONSubmitted by: J002306Submitters Company: JPMorgan Chase PUBLICRequirement Number and Title: IJPMC0314-1682 Improve Delete.DB processing for Parallel Recon AccessHomework Assigned: NoRequirement Category: Information ManagementCurr...
over 9 years ago in IMS Database Manager / General DB 2 Not under consideration

ISF0614-1711 - AUTH tables for IMS Data

SUBMITTER SECTIONSubmitted by: gregory.debo.bipd@statefarm.comSubmitters Company: State Farm PUBLICRequirement Number and Title: ISF0614-1711 - AUTH tables for IMS DataHomework Assigned: NoRequirement Category: Information ManagementCurrent Status...
over 9 years ago in IMS Database Manager / General DB 2 Not under consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.