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.
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
Whether a DB2CONN definition is public or private to an application does not alter the fact that CICS can only connect to one DB2 subsystem at a time using the DB2 architected cross memory interface that the CICS-DB2 interface uses. We have no plans in this area, it is not likely that this would be implemented in the next two CICS TS releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in eighteen months time if you wish it to be considered then.
Private DB2ENTRYs on the other hand is something we want to investigate as a way of supporting application versioning and the choosing of the right DB2 schema within a DB2 subsystem, as requested in RFE 42229
Making a DB2CONN a private resource would not remove the restriction that CICS can only connect to one DB2 at a time. It is a CICS-DB2 Attachment Facility and DB2 issue, not the fact the DB2CONN resource is private or public. The architected interface between CICS and DB2 allows CICS to attach to one and only one DB2 subsystem at a time. Even if it were possible to connect to 2 DB2 at a time, when an application issued an EXEC SQL request, how does CICS know which DB2 to send the request to ?
Correct. DB2CONN is a region level resource and CICS can only connecto to one DB2 at a time. The RFE proposes to remove that restriction through a private resource. The default DB2CONN would still be there for all legacy applications. Additional DB2CONNs can be utilized as a private resource for applications. This would greatly help with region consolidation.
Example:
Minimum for redunancy is two CICS regions even though the workload is well within the bounds of a single region. Each region pair is connected with its own DB2 subsystem. This is one logical group. When this logical group is multiplied by double digits sprawl becomes a concern.
With multiple DB2CONNs utilized as a private resource, the environment could be collapsed down to four CICS regions. Each CICS region would have multiple DB2CONNs; one DB2CONN for each logical group.
The benefits would be limited to only those shops with many DB2 subsystems.
In CICS TS 5.2 you can define a CICS Bundle to contain a set of resources that is included in an application bundle. In the CICS bundle you can specify imported resources on which the bundle depends. One of these can be a DB2CONN resource. Is this what you are requiring? Bear in mind a DB2CONN is a region level resource, ie a CICS can only connect to one DB2 system at a time.