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
Customer did some tests with the IPCONN autoinstall program (DFHISAIP). He noted that the "receivecount" of the autoinstalled IPCONN had the same value of the "sendcount" from the "partner" IPCONN, but the "sendcount" has assumed the default value "1", i.e., it did not use the value of "receivecount" from the "partner" IPCONN. Customer knows that he can use a template to define the number of "receivecount" and "sendcount", but it's not useful to him because the number of sessions between the CICS regions is very heterogeneous, these values vary according to the CICS regions. As a template is not defined and it is not possible to interfere in this parameter via DFHISAIP, the autoinstall assigns a default value "1" to "sendcount", which prevents the use of this facility. Customer suggests that the "sendcount" of the autoinstalled IPCONN uses the value of the "receivecount" from the IPCONN "partner" as the "receivecount" uses the value of "sendcount" set in the IPCONN "partner."
Idea priority | High |
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.
This RFE is satisfied by CICS TS 5.3 which is generally available from December 11th 2015.
The SENDCOUNT attribute on the autoinstalled IPCONN resource is set to the same value as RECEIVECOUNT, or the SENDCOUNT value from the template, if a template is specified.
his RFE is satisfied by CICS TS 5.3 which is generally available from December 11th 2015.
The SENDCOUNT attribute on the autoinstalled IPCONN resource is set to the same value as RECEIVECOUNT, or the SENDCOUNT value from the template, if a template is specified.
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
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.