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 Jun 30, 2017

Activating new versions of java applications without any outage in a CICS with different OSI bundles and dependencies

The motivation is equal to the RFE 107228. We are looking for a solution to handle the LifeCycle of Java applications in an CICS Environment with different OSGI Bundles and dependencies between these bundles. Goal is an activation of new Versions without any outage as it is possible with Cobol programs. The proposal in this RFE is to handle this with different JVMs. Today one Attribute of the program definition of a Java program is the JVMServer, but you can define only a single JVMServer. If it would be possible to define at least two JVMServer and the workload is distributed on the two as long as they are enabled, then we can activate new versions by disable/enable the two JVMServer wraparound so that at least one server is active during the whole time. If there is an exit point for this as a first step this would be also helpful. Another Advantage of this is, that you can distribute the workload on different JVMServers in one CICS Region if there is a bottleneck in the JVMServer for some reason.

Idea priority Urgent
  • Guest
    Reply
    |
    Nov 1, 2017

    Whilst this requirement is valid, based on our current plans and priorities, it is not likely that this could be implemented in the next 12 months, or in the next CICS TS release. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.