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,
Post an idea
Upvote ideas that matter most to you
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.
Log offload task needs to be manually cancelled restarted after outage to tape
We are seeing situations when tape processing is down and a DB2 request to offload logs to tape is initiated using dynamic allocation, that offload task will hang and never be satisfied until the offload task is cancelled and re-driven manually.
This poses serious and critical risks when we are performing maintenance on our tape infrastructure, or any other planned or unplanned outage. If an offload request occurs during the tape outage, the request is not satisfied. DB2 appears to wait indefinitely for the request to be satisfied. Since SMC is down while when the offload request is made, it is unaware that it needs to fulfill the request. In the meantime, logging continues on DB2 and subsequent offload requests stack up behind the first unfulfilled offload request. Many times, we are not aware of an issue until the active logs become full, waiting to be offloaded.
Is there a way to make DB2 re-drive the offload automatically? HSM, for example, has the ability to automatically re-drive tape mounts. Is there a way to make DB2 behave in a similar fashion?
Let me know if there is any information I can provide. I will attach a test scenario.
Do not place IBM confidential, company confidential, or personal information into any field.