Skip to Main Content
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 Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Mar 8, 2022

Provide capability for SLB Utility to timeout when HSM does not respond to backup request.

Currently the SLB utility sits in a wait state until ackowledgement of the backup request is returned from HSM. During this time a lock SYS_PITR is is held that prevents any DFDSS activity by Db2. This can lead to Db2 thread failures and data inconsistencies requiring recovery.

This impact can be severe leading to production outages.

There seems to be a fixed 20 minute timeout before the SYS_PITR will cause a timeout. This is too long to wait in a system, normally the request to HSM is very short.

Currently the workaround is to respond to error message and timeout messages but this is has already impacted the system.

We would like to suggest that a timeout parm is available for the Db2 SLB utiliy such that the utility can be terminated sooner if there is no response from HSM.

We would be looking for the Recover Expert Tool to provide this support as well.

Needed By Yesterday (Let's go already!)
  • Guest
    Mar 8, 2022

    This A-Ha is submitted on behalf of Services Australia, who have requested this function. It is related to Case # TS008461011.