Skip to Main Content
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.

Status Not under consideration
Categories Runtime
Created by Guest
Created on Jul 14, 2022

Option to isolate and end (looping) transactions in the JVM-Environment

We want to have the opportunity to isolate and end looping transactions in the JVM-Environment to avoid risking a JVM-Restart caused by the loop. We want to ensure the availability of the JVM for the rest of the transactions. We dont want to run in the following phaseout, just because we cant isolate/purge the looping transaction: DFHSJ1009 W CJSL 00098 JVMSERVER JVDYNS01 IS BEING DISABLED AND RESTARTED BY CICS BECAUSE A TASK RUNNING IN A JVMSERVER HAS TRIGGERED A RUNAWAY CONDITION, LEAVING THE JVMSERVER IN AN INCONSISTENT STATE. DFHSJ0918 JVMSERVER JVDYNS01 IS BEING DISABLED DUE TO A PHASEOUT REQUEST. It would be very good, if we get a runaway parameter for Java-transactions like the ICVR.
Idea priority Medium
  • Guest
    Reply
    |
    Sep 20, 2022
    To fully implement what is being asked for is simply beyond our ability and control of the Java language, so this requirement is being declined.