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
We have no plans to change CICS-DB2 group attach in this way.
I am not in favour of making such a change, as it will just add confusion. In hindsight we should have implemented group attach with just one parameter, like we did later for CICS-MQ. For MQ, the mqname parameter specifies either the name of a QMGR or the name of a QSG. If the name is a QMGR it will always connect to a QMGR of that name, if it is a QSG it will always use group attach to a QSG of that name.
The customer could easily use a system event for this.
For example the DB2CONN definition could be set up to use DB2ID and specify standbymode(noconnect).
If the connect to the member fails, then a system event could fire off a CICS task which could do
EXEC CICS SET DB2CONN DB2GROUPID(gggg) CONNECTED - change to use group attach and issue connect.
The logic in the started task could be coded to cope with subsequent failures. It could for example try the member first and if not try the group
Regards,
John tilling