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 Not under consideration
Workspace PL/I Compilers
Created by Guest
Created on May 22, 2018

Simplify left/right

I know you wanted to have all possibilites in left / right, but I think the 2 parameter in the functions should be optional, because no programmer wants to spezify the length of the target. If I have an "=" the left side is the target, the length of the result is clear, if I don't need this length, then ok spezify parameter number 2.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 15, 2018

    A built-in function has to be able to define its returned attributes independent of how it is used, and instead based solely on its arguments' values (just as any user function must do). This is especially true when it is used outside of an assignment and "jsut" in an expression, as, for example, in PUT SKIP LIST( left(x) ). What attributes would LEFT(X) return here?

    If you want to assign S to T and pad with something other than a blank, you could use T = S || COPY( '*', n ) where n is big enough. If you to do this more cleanly, we could have a built-in subroutine (not a function), say PLIAssignWithPad, that would take a target, a source and a fill character as its argument, as, for example

    Call PliAssignWithPad( target, source, '*' );

    But that would be a different RFE