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 Apr 26, 2017

PHASEIN Support for JAVA programs running under Liberty Profile

The versioning and alias processing options that are presently available for deploying new Liberty Profile JAVA bundles in CICS require changes to the pre-existing CICS RDO definitions, this is not something that is desired when promoting a new version of a Liberty Profile JAVA program already defined in an existing CICS BUNDLE. There should be no requirement to update the RDO definitions.
Currently if a new version of a Liberty Profile JAVA program is redeployed under the same CICS BUNDLE name the JVM must be disabled and subsequently enabled to bring in the new version, this is a disruption to continuous operation which is a requirement in a 24 x 7 operating environment. A process is needed such as the CEMT SET PROGRAM()PHASEIN which addressed similar operational issues that the NEWCOPY process had with LOAD HOLD or resident programs by its introduction of LDEs and APEs to handle program versioning behind the scenes.

Idea priority High
  • Guest
    Reply
    |
    May 27, 2021

    This requirement has been re-assessed. It is not likely that this will be implemented in the next 12-24 months and so it 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.

    The follow article describes an approach to create a high availability cluster of CICS JVM servers. In this approach Liberty is configured to start with HTTP endpoint(s) in a disabled state, and once all the application components are ready, to automate setting the endpoint(s) enabled via a CICS policy, MBean, Liberty command line, or CICS SPI.

    Avoiding HTTP outages by managing Liberty endpoints
    https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/philip-wakelin1/2020/08/10/avoiding-http-outages

    Using the above setup, an alternative solution to this RFE would be for an automation script to deploy new CICS bundles with the following steps:
    1. disable the Liberty endpoint - new connection requests will resolve to remaining Liberty instances in the cluster, persistent connections should terminate normally
    2. wait for existing work to complete normally
    3. disable and discard the old BUNDLE
    4. install new BUNDLE, and wait for it to be enabled
    5. enable the Liberty endpoint.

  • Guest
    Reply
    |
    Oct 31, 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.