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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
This RFE is satisfied by CICS TS 5.3 which is generally available from December 11th 2015.
The new PHASEIN support for the SET BUNDLE command enables the registration of a new version of an OSGi bundle with the OSGi framework, to replace any version currently registered. The new version of any OSGi services that are implemented by the new version of an OSGi bundle are then used by any new invocation of a Java program that is defined to use this OSGi service. Existing requests will continue to use the old version until the request completes.
This RFE is satisfied by CICS TS 5.3 which was announced on October 5th 2015 with a planned general availability date of December 11th 2015.
For more information see the announcement letter http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS215-363
Support is provided for phasein of Java programs running in an OSGI JVM Server.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Thank you for your response.
The priority would be for a CEMT operator command although an SPI would work as well. The main requirements are for a zero outage window during deployment (many of our CICS regions only come down for IPLs) as well as a more simplified process for handling versioning, the current options to handle versioning for JAVA programs in CICS require modifying the CICS CSD definitions, this is not desireable for us. We are looking for a more simplified process similar to how COBOL and ASSEMBLER programs are handled that doesn't involve the need to modify resource definitions in CICS. Presently when a new version of a COBOL or ASSEMBLER program is moved to a load library all that is necessary in the CICS region(s) is to issue the CEMT SET PROGRAM() PHASEIN and CICS handles loading and using the new load module behind the scenes. Having to modify definitions within CICS complicates the promotion process for application changes and will make it cumbersome for anything other than a small implementation. We sometimes have application releases where many application programs are moved into the system at one time. We presently utilize an in-house batch utility that identifies the CICS regions where the application programs reside and issues the SET PROGRAM () PHASEIN commands in them.
No CSD access and not recycling the JVM as you stated are the main requirements we are requesting.
Thanks for raising, firstly it would be good to clarify some issues;
- There is no need to restart a JVM when deploying a new version of a OSGi bundle, instead you can use OSGi versioning or aliasing to deploy a versioned bundle, or you can drive the bundle discard/enable lifecycle
-There is also no need to modify pre-existing definitions when deploying a new version of a OSGi bundle, as you can either use a new CSD bundle definition, or use the EXEC CICS CREATE spi to dynamically create a bundle resource on the fly.
Secondly there are a few other questions which would be useful to clarify
- Is the priority for operator usage (i.e CEMT or Explorer) or an SPI for deployment automation (EXEC CICS or CMCI)
- Is the requirement to have a zero outage window during redeployment?
- Bearing in mind the comments above.... are there any other hard requirements about the design for a redployment process, other than no CSD access and not recycling the JVM?