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
Created by Guest
Created on Jul 5, 2016

Undiagnosed implicit returns from functions, PLI 4.5

In the below code, the problem is with the Otherwise.

In PLI 4.3, it does not give the correct output and also it does not give any Runt time error.

But in PLI 4.5, it gives the runtime error. Applications which were running smoothly in PLI 4.3 are failing with PLI 4.5, because of this.

It would be great if, we get a compile time error instead of a runtime. So that applications don't fail at runtime.

Output = Funciotn_A();

Funciotn_A: Proc returns(char(1));

Select(input);
when ('A')
return('A');
when ('B')
return('B');
when ('C')
return('C');
Otherwise ;
End;

End Funciotn_A;

Idea priority High
  • Guest
    Reply
    |
    Aug 29, 2017

    this was delivered as part of 5.2

  • Guest
    Reply
    |
    Nov 17, 2016

    Ideally, functions should have one point of return:

    Output = Funciotn_A();

    Funciotn_A: Proc returns(char(1));

    Declare
    return_value char(1) init(' ');

    Select(input);
    when ('A')
    return_value = 'A';
    when ('B')
    return_value = 'B';
    when ('C')
    return_value = 'C';
    Otherwise ;
    End;

    return(return_value);

    End Funciotn_A;

  • Guest
    Reply
    |
    Sep 26, 2016

    we can do this with little cost to compile time, and it will help detect erroneous and/or dead code

  • Guest
    Reply
    |
    Jul 21, 2016

    this would be good, but could potentially have a significant impact on compile time. We will investigate its feasibility