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.
There could be substantial cost to do this which would delay doing other work that would bring broader benefit. Also the MSGSUMMARY option can be used to get a quick view of all the messages produced without having to look at each one
I have mixed feelings about this, as this kind of code is unlikely to occur frequently, so
Given that these two messages are in 99.9% (if not five-nines) of the cases pretty much harmless, and they're 'I' anyway, why don't you use the compiler exit to suppress them?
In fact it might be more useful to open a new RFE to ask for a
15655-PL5 IBM(R) Enterprise PL/I for z/OS /*
- Summary of ***Suppressed*** Messages
0 Component Message Total Default Message Description
0 MACRO
that would cater for this situation.
Attachment (Description): It is an example code of issuing same messages for a line performing arithmetic operations of FIXED DEC using structure name.
Attachment (Description): It is an example code of issuing same messages for a line performing arithmetic operations of FIXED DEC using structure name.