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.
Eliminate Reorgs failing with S513 & IEC146I 513-04 when reorging LOBs
The cause of the S513 error is due to the DB2 reorg utility trying to write two image copies in parallel (one for BASE and one for LOB) when a BASE UTS with LOB TS is being REORG’d and the specified template for image copy datasets has the STACK YES parameter. We understand that in order to allow parallel writes to image copy datasets for BASE and LOB table space, the template to use should have the STACK NO parameter.
However, since we image copy to tape it causes the DB2 utility to acquire multiple tape drive units all at once on REORG of UTS for each partition, especially on PBRs with high number of partitions. In our shop we cannot do this and would like not to have to break our reorg jcl into pieces. One step should handle all objects without failure. the utility should be smart enough not to cause S513 abends
Do not place IBM confidential, company confidential, or personal information into any field.