IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 (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

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 (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.

IBM Employees should enter Ideas at https://ideas.ibm.com



ADD A NEW IDEA

Clear

Ideas

    Showing 144 of 18262

    Enable option for hardcoding GPU memory request like its available for CPU memory request

    At this moment IBM offers features of hardcoding CPU memory. We have implemented this feature in our cluster with esub scripting. Similarly we want to have same feature available for GPU memmory (gmem) to be hardcoded. I have raised ticket to our ...
    almost 3 years ago in Spectrum LSF / Scheduling 2 Not under consideration

    In SQL replication, do not re-execute signals that have already been executed.

    In SQL replication, as in Q Capture, add a reprocess_signals to the parameters of the capture and set the default to N. Do not re-execute a signal that has already been executed if the minimum LSN is less than the last signal LSN at the start of t...
    over 1 year ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Submitted

    truncated hostnames in bjobs output

    For a debug where hosts are available but jobs are not landing on them - I need to run bjobs -UF (or -l) -p2 This command generates below like data structure Slots are reserved for guarantees: xxx3-sim-d18-081, xxx-sim-d18-077, xxx- sim-d30-065, x...
    over 1 year ago in Spectrum LSF / Scheduling 0 Planned for future release

    IIDR STOPQ/STARTQ request should be executed in parallel beyond the queue

    IIDR STOPQ/STARTQ command is isssued from customer created automated process. They are isssued for 5 queues in parallel.Customer's STARTQ will be isssued without minitoring if the previous STOPQ queue is complete through MSGASN7176I. If STOPQ proc...
    almost 8 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

    New age patchinstall tool

    With IBM moved away from Quarterly fixpacks to Yearly release – we often see bunch of patches for install as backlog. Current patchinstall tool does this job efficiently for a single patch and if I’ve to install 5 patches on top of a fixpack (inde...
    over 1 year ago in Spectrum LSF / Scheduling 1 Future consideration

    Db2 LUW - SQL replication should optionally use TRUNCATE when performing a Full Refresh of large tables

    Db2 LUW SQL Replication (10.2.1) When you run a Full Refresh of a subscription set, the asnapply utility issues a DELETE FROM <target table> prior to the refresh of the data. For large tables this has a significant and unnecessary overhead -...
    over 6 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

    Enhance GSLA to enable in-queue preemption

    The Guaranteed SLA system allows sharing of Resources defined by ServiceClasses. We would like to use that to allow two or more groups to pool and share compute slots, wherein they typically unused slots would be available to all of the groups. Th...
    about 5 years ago in Spectrum LSF / Scheduling 1 Not under consideration

    Multiple queues request for job - consider taking in account queue limitations and lsf.resources for better job dispatching.

    Today, when we submit a job with multiple queues (bsub "high risk") The job will be dispatched to a relevant queue by examine parameters such as queue status(open/closed), queue hosts, time-limit. In a situation, where a queue "high" have a ujob_l...
    over 1 year ago in Spectrum LSF / Scheduling 1 Not under consideration

    The customer would like to know all the related tables associated with an uncommitted Unit of Recovery (UR).

    If there is an uncommitted UR (a.k.a transaction) on the Capture side, is there a method for QREP to quickly locate the tables related to the uncommitted UR?
    almost 2 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 1 Future consideration

    Request for supporting MQ automatic client reconnect

    As we know, IBM MQ supports multi-instance configuration and automatic client reconnect since version 7.0.1. Recently we found the latest Q-Relication (11.4.0) even not support such a basic function( automatic client reconnect with multi-instance ...
    over 3 years ago in Data Replication: Q-Replication & Availability / Replication for Availability (LUW, Db2 Warehouse) 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.