IBM Z Software
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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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 RFE raiser. Closing this RFE.
There are various options for working with CCSIDs. The best option is to use the UTF-16 support that was added in TS V5.2, but that can involve significant application rework, so isn't a solution for everyone. Another option, if the CCSID is determined on a per-region basis, is to configure the encoding using the LOCALCCSID system initialisation parameter. A third option is to deploy multiple WSBind files, each configured for a different target CCSID, and each associated with a different URI.
If there's a requirement to support multiple application encodings within a single region, for the same URI, then there has to be some way for: a) CICS to know which encoding to use; and b) the application to know which encoding to use. Should CICS decide the encoding to use based on the value of an HTTP Header, a SOAP Header, the TCP/IP address of the client, the query string of the URI, an indicator somewhere in the application data, something else? Is the requirement that a Handler program can decide the encoding to use? CICS could indicate the actual encoding that was selected to the application using a control container, but that would limit the scenario to Channel interfaces only - no commareas - is that a problem?
How compatible are the target encodings expected to be? The copybooks will have to be the same as they rely on fixed length/offset fields.
Please could you supply a bit more detail about the business problem for which dynamically changing the CCSID is the technical solution, and how the selection of a target encoding can be made.