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.
No response from the raiser of the RFE. Closing this RFE.
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
The PIPELINE SCAN mechanism is used to create URIMAPs of type USAGE(PIPE). The SOCKETCLOSE attribute is only eligible for URIMAPs with USAGE(CLIENT) - it's only for outbound connections. The TCPIPSERVICE resource has a SOCKETCLOSE attribute. Is this requirement reporting a need for the SOCKETCLOSE TCPIPSERVICE parameter to be individually configurable for each URIMAP? Would having multiple TCPIPSERVICE resources installed be an acceptable work-around for that need?
In addition to prior post, The model could be an existing URI MAP rather than a new resource, just a pointer in the bind file to say use that URI MAP as a model, and a message saying URI MAP xxxxxxxxxx used as Model for URI MAP in pipeline scan build.
SOCKETCLOSE was the parameter of interest, was thinking if could have a model could specify a model and pull all the parms from the model,
Steve.
We'd like to ask for more information. You described a solution but not the problem you are trying to solve. For example which URIMAP attributes are you wanting to change? Once we know that we can consider the best solution: that might be better default values, storing more configuration in the WSBind, additional configuration in the Pipeline, or (as requested) an entire new RDO resource with associated SPI, CPSM, CMCI and Explorer changes.