IBM Data and AI Ideas Portal for Customers


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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Nov 8, 2019

RELATED IDEAS

Add a STOP DB2 mode that cancels connected threads, but not internal processes.

We have struggled with getting a "clean" shutdown of Db2 for years.

If we try to use STOP DB2 MODE(QUIESCE), Db2 will not stop. Persistent threads from STCs such as CICS regions, WAS Z servants, and ARS CMOD servers do not "end", so they never allow Db2 to shut down.

We had considered writing some kind of REXX to loop through a -DIS THREAD output and issue -CANCEL THREAD for all persistent threads, but in some cases, persistent threads are inactive and don't even have an associated token.

 

We have been resorting to STOP DB2 MODE(FORCE) to get Db2 to stop, but often Db2 comes up with objects in GRECP status, including critical objects like SYSLGRNX and its indexes. We IPL our entire Production sysplex, so delays in accessibility of SYSLGRNX can cause errors to be thrown to other started tasks, which vary in their ability to handle/recover from them. (WMQ queue-sharing is particularly sensitive to -904s when attempting to start)

 

Ideally, we would be able to shut down ALL tasks connected to Db2 before attempting shutdown of DB2 itself. This is not practical, however, in a large, heterogeneous environment, where different operational personnel and system administrators are responsible for hundreds of different regions connected to Db2. We do our best, but it often is not good enough.

Needed by Date Nov 8, 2019
  • Admin
    Janet Figone
    Reply
    |     Jun 3, 2022

    Dear Mark, Thank you for submitting this enhancement request. The Db2 for z/OS team has reviewed it and determined the following:

    It is thought that -STOP DB2 MODE(FORCE) should be doing exactly what Mark wants:

    1. Terminate all active connections to Db2 (this is what FORCE does rather than QUIESCE, which waits for active connections to go away.)

    2. Shut down Db2 address spaces normally (Force option does not change the Db2 address space shutdown process.)

    If the Db2 address space termination does not go well that should be addressed as a problem to be fixed. I don't think that there is an alternate shut down method for the Db2 subsystem.

    Db2 does record the MODE option in the SCOM as SCOMSTPQ (QUIESCE) or SCOMSTPF (FORCE). So if Mark wants any particular Db2 component to behave differently depending on the MODE option, then that could be addressed.

    All of the subsystems that use Db2 implement the TERM ECB and if they do not terminate when they receive the the TERM ECB then Db2 can not do much about that other than terminate them which is what it does -STOP DB2 MODE(FORCE). The middle ground of trying to implement FORCE for allied jobs and subsystems without stopping Db2 is an infinitely complicated issue.

    Please let us know if you have any additional questions or comments, and please do continue to submit enhancement requests to us for consideration in the Db2 for z/OS product.

    Sincerely,

    The Db2 for z/OS team

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.