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.
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 a duplicate of RFE 22094
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=22094
This is a duplicate of RFE 22094
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=22094
Comments from the IBM CTP (Régis David)
On this specific installation the CTGs route the requests to TORs from DFHXCURM. Then the TORs route the requests to AORs from DFHDYP.
The CTGs are on different LPARs so are the TORs and the AORs. Any to any links are defined.
Customer has to maintain two different routing programs; they are technical and written in assembler, and so require skills difficult to find today.
They know that the CTG offers the Java request exit. But again this requires 2 different routing implementations and there is no reason to invest in a project to move from DFHXCURM to a request exit. Also the scope of the simple CTG request exit routing is too simple here.
From an architecture point of view, we may consider the CTGs as CICS TORs.
We are looking at implementing CPSM to solve the DFHDYP issues and benefit from the CPSM set of functions. This will not solve the two routing exits they have to maintain.
The value proposition of CPSM would benefit from including CTG routing integration: one single routing function for the CICS 'cloud'. Also this would allow architecture simplification by removing the TORs.
The answer to this RFE can be to deploy the CTG deamons into the CICS TOR JVMSERVERs...LINKs issued from the CTG daemons are therefor CPSM enabled...