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

Phasein of Java bundles in an environment with different bundles and dependencies between these bundles

FI is going to modernize its backend application, that means it will migrate its programs step by step to Java. As runtime Environment we use CICS TS. CICS TS supports the Integration of Cobol and Java. Currently we deploy our Java part in one CICS bundle but the more applications we migrate to Java the more difficult is it to handle this. One crucial aspect in our installation is that we need the possibility to exchange new application versions without any interruption. This is possible with Cobol programs (phasein) and one Java bundle but not with different Java bundles which have dependencies. This currently prohibits that we separate our Java applications on different bundles. The Details: CICS uses CICS bundles for managing OSGi bundles in JVM-Server. When a CICS bundle is enabling or disabling the associated OSGi bundles are starting or stopping.
With CICS version 5.3 the system supports the deployment of new versions of OSGi bundles without service outages and CICS resource changes with the command "SET BUNDLE (data-value) COPY (PHASEIN)". It results in setting a new OSGi Bundle into ACTIVE state and the old one into RESOLVED state. The command acts for all OSGi bundles in the CICS bundle.

When stopping an OSGi bundle that exports packages the package wiring of dependant OSGi bundles remains to the old OSGi bundle. Actually there is no way to refresh the wiring of dependant OSGi bundles, because CICS does not support this part of the OSGi bundle lifecycle anywhere.

It is clear that the refresh method on a stopped OSGi bundle can produce undesireable effects, because the dependant OSGi bundles are determined just in time and then stopped, new resolved and started frequently. So service outage would occur.
On the other hand in a strong designed application it would be requested to deploy a new version of an OSGi bundle with service outage accepted or well handled.

Proposal:

SET BUNDLE (data-value-1) REFRESH (data-value-2)

data-value-1 specifies the CICS bundle
data-value-2 specifies the OSGi bundle in RESOLVED state

The command does operate on a specified OSGi bundle in a CICS bundle. It executes the refresh method on an OSGi bundle, which has to be in the RESOLVED state.

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.