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


Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on Aug 14, 2024

RESTORE SYSTEM should support log apply across DSN1COPY and vendor utilities

RESTORE SYSTEM can fail in log apply when there was a DSN1COPY or vendor utility within the log apply range. This occurs because RESTORE SYSTEM uses pageset control log records to determine that a LOG NO utility had been run, and neither DSN1COPY nor vendor utilities write this log record.

RESTORE SYSTEM should detect when DSN1COPY (or any other offline / vendor utility) was run during the log apply range so that log apply errors can be avoided.


Vendor utilities create a sequential copy which is posted to the SYSIBM.SYSCOPY table as a LOG(NO) copy. RESTORE SYSTEM with LOG APPLY may encounter problems related to these copy files. The RESTORE SYSTEM processing relies on Db2 log records to identify system activity fitting the desired restore time frame. Third party processing can cause data location changes which can impact the RESTORE SYSTEM processing in unpredictable ways.

The creation of the LOG(NO) copy files is not made available to the Db2 log. The RESTORE SYSTEM processing cannot rely on header page fields in an object to detect LOGNO activity. The processing involves a wider scope of utility processing and system activity, requiring a more robust and reliable solution. Vendor utilities need to write non-recoverable LOGNO PAGE SET CONTROL log records to the Db2 log.

Doing so will enable RESTORE SYSTEM processing to distinctly detect the LOGNO utility files, allowing these objects to be put in RECP. Putting the object in RECP will avoid the problems seen by customers when using RESTORE SYSTEM for cloned environments.

Vendor utilities need a way to write the LOGNO PAGE SET CONTROL LOG records to the Db2 log. An interface to write the desired record to the Db2 log is needed. The interface will need to supply a response for each write request, indicating its success or failure. We will need a complete breakdown of the format and content of the log record that needs to be written. We will need to be aware of any system settings or variables that may impact what is represented or reflected in the log record being written.

Needed By Month