IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Apr 27, 2018

LOAD with COPY=YES and TSM needs similar resilience feature like log archiving with VENDOR_ARCHIVE_TIMEOUT

FI has set of LOAD jobs (with COPY=YES and use of TSM) which run in parallel against the Db2 data warehouse.
FI experienced failing LOAD jobs in the LAN-free TSM backup environment for the Db2.

FI sees risk for the LOAD jobs when TSM is not available or TSM not processing. In this situation the LOAD jobs will fail and the entire batch processing will stop.

To prevent this, FI like to have a similar behavior for LOAD jobs with COPY=YES like Db2 has with Fixpack 3 for LOGARCHIVING (--VENDOR_ARCHIVE_TIMEOUT + FAILARCHPATH).

For example, if TSM is not available or not responsive, Db2 should store the LOAD files in a local file directory without stopping the LOAD job and store them automatically in TSM when TSM is back again.