Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Delivered
Workspace PL/I Compilers
Categories z/OS
Created by Guest
Created on Jan 10, 2024

Add new warning message for misuse of a literal as output argument

We would like to get warning messages issued, when a literal is passed as argument, which was explicitly declared as inOut or outOnly. The compiler handles this correct, but of course, the output value is lost. From our point of view, such code is wrong for outOnly as well as for inOut, if explicitly declared with it. 

So for the given example code in the attached LIT2OUT.txt compiler listing, we like to get the following:

- New warning issued for the literal used for outOnly at statement 14 on line 17.0.
- New warning issued for the literal used for explicitly declared inOut at statement 12 on line 15.0
- Nothing for the literal used for inOut by default at statement 10 on line 13.0

Please provide that in version 6.1.

Idea priority Low
  • Guest
    Reply
    |
    Apr 2, 2024
    This would be useful in detecting possibly erroneous code. This has been delivered via an APAR/PTF to the 6.1 compiler.
  • Guest
    Reply
    |
    Jan 11, 2024
    This would be useful in detecting possibly erroneous code