IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Add a new idea Subscribe
Status Not under consideration
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on May 13, 2022

RELATED IDEAS

Allow to interrupt before automatic restart. (DFHSJ1009)

We need an indicator before the JVM restarts (80% of runaway time), to allow us to shift the workload, before the JVM restarts. This topic was already discussed in a meeting with Hursley and the German CICS Tech Sales.
Idea priority Medium
  • Guest
    Reply
    |     Jul 27, 2022
    Closing Idea with customer agreement
  • Guest
    Reply
    |     Jul 27, 2022
    When a task running Java experiences a runaway interval condition, the JVMSERVER intercepts the condition and initially triggers a DISABLE PHASEOUT. New work is prevented from entering the JVM and existing work is left to drain.

    To prevent further work from being rejected you can check the JVMSERVER status - if it is not 'ENABLED', don't send work to it. Conversely, you could trigger off the SJ1010 message which informs a user that the JVMSERVER is beginning to quiesce (due to runaway in a task nnnn). If the task continues to run for further runaway intervals, the JVMSERVER shutdown sequence will escalate through the PURGE, FORCE, KILL stages (each runaway internal) until all workload is terminated and the JVMSERVER recycles.

    Does this behaviour resolve the issue? If not please elaborate on the problem you want to solve and the behaviours experienced by the JVMSERVER. Thanks.

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.