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 RFE has been evaluated by development, and is being rejected as the requested capability already exists.
Today the IMS service creator can remove LL, ZZ, and trancode from the service interface. The service creator is required to provide the trancode and there is no way around this for any type of message size.
However, the service creator can choose what is exposed (or not), and as such can remove the LL, ZZ, and trancode fields entirely and they will be handled/set internally by the zCEE service provider at runtime.
IMS message metadata LL, ZZ would ever need to be exposed from zCEE, and choosing to do so would be unintuitive to a REST API consumer.
This requirements matches ours.
We have made the same experience during the Beta tests, i.e. an undesired difference in behaviour, depending on whether data smaller or bigger than 32k is used.