This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
"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.