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

DLI

Showing 28 of 8231

Run OLR through job batch

It would be useful to have the possibility to run OLR directly by job batch. The job has to be active during the whole reorganization.
about 10 years ago in IMS Database Manager / DLI 3 Not under consideration

Backout with GSAM file

To avoid the abend of a bmp, a program can do a rollback to cancel the unit of work that caused the problem. But today, it's not possible with gsam file.
about 10 years ago in IMS Database Manager / DLI 2 Not under consideration

CPU time by OLR in records 29xx of IMS log

We need to have the CPU time of OLR in record “2990” of IMS log (the start is 2910).
about 10 years ago in IMS Database Manager / DLI 1 Not under consideration

Dynamic allocation of Full Function databases from Recon

IMS Fast Path database datasets are dynamically allocated using the information registered in the Recon datasets. We would like the same to apply to Full Function databases.
about 10 years ago in IMS Database Manager / DLI 0 Not under consideration

Initial READ-Intent for a PCB until a DLI GET-HOLD call or ISRT call is issued

All PCBs in a PSB should have an initial Read-Intent regardless which PROCOPT is coded. If an Update-Intent is coded for a PCB it only should become active when the first GET-HOLD call or ISRT call is issued against that PCB. This will cause fewer...
about 10 years ago in IMS Database Manager / DLI 0 Not under consideration

Increase OSAM subpools from current limit of 255 to 1024 or 2048

As our BMP workload increases coupled with recent mergers we are fast approaching the limit of 255 OSAM subpool buffers. In our environment we have seen a slow down in BMP processing when too many BMPs are accesssing the same OSAM subpool due to l...
over 10 years ago in IMS Database Manager / DLI 1 Not under consideration

Please remove the latch requirement for DMB obtained during DB compression

We had some IMS BMP performance related issues that showed the more jobs we ran on an LPAR against the same database/partition the slower the jobs would run. Upon review of the IMS Monitor reports and IMS latching log records we noticed a rather s...
almost 11 years ago in IMS Database Manager / DLI 2 Not under consideration

HALDB Indicator/flag for PST

Inside DFSPECA customer need an indicator/flag, indicating whether, for example, the PST is BMP or MPP. They also need an indicator for the IMSID.
about 11 years ago in IMS Database Manager / DLI 1 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.