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

Q Replication for Z

Showing 59

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 5 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

Prompt customer need to reduce prune interval

In a busy Q Rep env with many bi-di Q subs, there may lots of P2PNORECAPTURE signal insert into IBMQREP_SIGNAL control table by Q Apply program. As per design, Q Capture delete up to 10000 rows at a time for one prune interval. When the average P2...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Is a defect

Fully replication support of Db2 data type XML with IDR Queue Replication especially for the case the Queue message size is limited because of using Shared Queues based on Coupling Facility structures

We replicate a lot of changes of our operational zDb2 data to a Db2 LUW (BLU) via IDR Queue Replication. The Db2 BLU is used as the data base of our datawarehouse processes. The Queue Replication uses Shared Queues which are mapped on Coupling Fac...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Sequence Number management in a replicated DB2 system

Today sequence numbering in a DB2 subsystem that is being replicated to a secondary site needs to be managed outside of the replication support manually by the customer. Guidance has been given to use odd/even numbering on one side and the other. ...
almost 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

ASNCLP PROMOTE to generate SQL rather than another ASNCLP Script

When using the ASNCLP PROMOTE function the output is another ASNCLP Script. We would like the PROMOTE option to generate the target SQL instead of another ASNCLP Script - applying any name changes defined in the PROMOTE command.
over 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Not under consideration

V12-CERT-2017 - Support for replication of REORG DISCARD events

When a REORG discard is run on the source side in a replication relationship / event relationship we want to be able to replay this event on the target side somehow. We do not want to do this by logging the discards in the REORG, of course. One su...
over 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Ignore log records for a dedicated subscription in IGNORETRANS

In very rare cases Db2 cannot provide log records for Q Capture, e.g. in case of a version mismatch, a compression dictionary error, etc. Removing the subscription and reloading the target is a practical approach. But in some situations (e.g., non...
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Latency Threshold Setting by Duration in ASNMON

Transaction volume is different between business time and non-business time. Different threshold should be set for QCAPTURE_LATENCY， QAPPLY_EELATENCY， QAPPLY_LATENCY, e.g. 08:00 - 21:59, 22:00-07:59, etc.
almost 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

ASNCLP Error Message Enhancement

For error code ASN1952E, the reason maybe ASNCLP script grammar error, QMGR setting is wrong of missed in PARM table of CAPTURE or APPLY, password of z/OS user is wrong, etc. That makes operation maintenance very hard for trouble shooting. The det...
almost 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

zIIP Eligible Q-APPLY

QREP is increasingly become to a key infrastructure component for customers z Systems platform resilience. However, the QREP did need quite a lot MIPS to support. This requirement is for QREP to change some part to be zIIP eligible, specifically f...
over 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 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.