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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
We just installed a Platform in the System Aproval Test Environment. Afterwards we tried to make some changes and this was not really funny.
First we had to disable all Applicaiton, then we had to disable the platform and other not really nice things.
We realised, that at the moment it is not possible to do changes on the running system withou a downtime window, what is realy not nice.
The second big problem for is that we have to define the platform withou running cics regions at at beginng. After a snapshot of the Production LPAR we add Regions to this platform. Unfortunately you have at least one time to run a platform with regions otherwise the platform is not detecting the regions after adding them to the platform.
After some thinking a landed at the same point I had some months ago.
We need a platform versioning and the possibility that applications running on a platform with the same name are automaticly defined on the new version of this platform.
This would allow the system programmer to change the definition enable the new platform. At the same time the old platform is not longer active and every is running different.
The same thing you implemented for applications.
The second thing is that we need the possibility for a platform to make a refresh or lets say that the platform automaticly realises a change of regions below it. We want that an adding and removing of regions is possible in the running system.
We also would need the possibility to define the minimum cics level on a platform. This would give an interesting oportunity for the cics upgrade. You are running under 5.2 with a 5.3 CPSM. You are adding 5.3 regions to the platform definition. As you activate the new platform with cics minimum level 5.3 all applications will run on this regions. Now you can remove the 5.2 regions safely or if you need to fall back just disable the platform and everything runs on 5.2 again.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
We have assessed this requirement. We have no current plans for this to be implemented and so 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.
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
I think there are 3-4 separate requirements here:
1. We are certainly considering separating the lifecycle of a platform from the underlying CICS regions; the current restriction is not a deliberate architecture constraint but a question of priorities.
2. We are investigating how to better support upgrades and also for a platform to declare a minimum CICS level
3. Allowing multiple platforms to be installed into the same regions
4. However, moving an application from one platform to another is more problematic
A better approach to 4 might be to treat each CICS region as a sort of VM. Install platform P version 1.0.0 and add the applications. Then install P version 1.1.0 and again add applications one at a time to ensure everything is OK before making the applications on P version 1.0.0 UNAVAILABLE and removing the platform itself. Switching all the applications together could be problematic.