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.
"Reorg force all" should kill all existing (active or inactive) threads which belong to the object which would be reorganized
we have many tables which are changed and selected 24 hours a day - 7 days a week. So this tables need more reorgs than other not so much changed tables but it is not possible to make a reorg (force all) because there are Spufi User with autocommit off which are inactive on the table. Also we are in the changing process from whatever to UTS which is also done by a reorg.
And here the biggest thing about (imho) the badest solution we have. We shut down the whole Company (not only z/OS) start one member make all the roergs which are needed after a while and for UTS and start the Company again. The shutdown is about 1,5 hour also the start. So thats real pain. Also if we kill a thread which is not directly on the object it would be better than this massive outtake of the whole IT infrastructure.
Do not place IBM confidential, company confidential, or personal information into any field.