Skip to Main Content
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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Delivered
Components Q Replication for Z
Created by Guest
Created on Mar 1, 2021

Add CAPTUREUPTO as Q Capture startup parameter

We need an emergency mechanism to control the capturing of a limited and dedicated amount of time. Today, Q Capture can be stopped when a dedicated timestamp is reached using CAPSTOP CAPTUREUPTO=<ts>. But that is not useful when Capture is down and when Capture has to be started for a limited amount of log space. It is not practical to start Capture and to issue a separate stop command thereafter. Instead, the additional startup parameter CAPTUREUPTO=<ts> would be required. Various use cases for the CAPTUREUPTO startup parameter exist. One would be to proceed capturing until a dedicated log timestamp has been reached before a new subscription is activated (New sub with STATE='N').

Needed by Date May 31, 2021