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.
This requirement has been evaluated. Looking at current plans, 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 twelve months time if you wish it to be considered then.
The requirement is for CICS calling a Web Service out site CICS. We add Web Service Call to existing CICS application. Our shop use both cobol and PL/1 in CICS application. We need both a Cobol and a PL/1 interface to the Web Service. In our solution it has been necessary to add an P/C to the Web Service Name in CICS to distinct between the two. I still see the need for 2 bind files we just would like to pass the language code as a parm on the EXEC CICS INVOKE SERVICE.
Wouldn't a better option be to just implement the Web Service client in one language (e.g. COBOL), and to link to that client from both COBOL and PL/I?
If we were to implement this requirement, we'd have to limit the generated interfaces to a lowest-common-denominator of compatible data-types across the supported languages: COBOL, PL/I and C/C++. Even something as simple as a String would be complicated: C/C++ tends to use null terminated strings (with an extra character for the terminator), COBOL tends to use space padding, and PL/I can use varying strings. We'd have to pick a single mapping option, and force developers across all languages to use that specific binding, regardless of what they might prefer. I imagine most would see that as a step backwards.
Please can you supply more information about the business requirement. Why is it better to have 1 WSBind, 2 driver programs, and 2 callers (the proposed solution), compared to 1 WSBind, 1 driver program, and 2 callers (the suggested solution using current technology)?