Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Future consideration
Workspace IBM i
Created by Guest
Created on Nov 11, 2016

CL Parsing in LPEX Editor not using Line Length Preference Setting

The CL Parser in the LPEX Editor does not use the "Line Length" preference setting (for splitting a formatted command into multiple lines) when the "Automatic formatting" preference is turned off -- even though the "Line Length" preference shows as available as if it applies. Instead, when the "Automatic formatting" preference is turned off, the CL Parser always splits and wraps a formatted command at around column 70 by default. This means that although IBM left the "Line Length" preference unprotected (at my RDi release level) when "Automatic formatting" is turned off, the value there is ignored unless "Automatic formatting" is turned back on.


Use Case:

I have gotten used to keeping "Automatic indent" and "Automatic formatting" turned off because I don't like the CL Parser to keep changing my choice of line splits and line indents. Some commands are much easier to read if I can split them and indent them as I see fit. But, I still need to be able to prompt commands and get formatted output when I press ENTER from the prompt window. The resulting formatted output needs to incorporate the current "Line Length" preference setting and not use the default split and wrap at around column 70.


Idea priority High
  • Guest
    Reply
    |
    Jul 26, 2022

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. One should not have to fight the editor to make changes in CL!


    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.


    For more information about CAAC, see www.common.org/caac


    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Nov 24, 2020

    We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

  • Guest
    Reply
    |
    Apr 20, 2017

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Reply
    |
    Feb 17, 2017

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.

  • Guest
    Reply
    |
    Feb 17, 2017

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for Power Systems
    Component - Other
    Operating system - IBM i
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Application Platform
    Product - Rational Application Developer
    Component - Other
    Operating system - IBM i
    Source - Other

  • Guest
    Reply
    |
    Nov 11, 2016

    Attachment (Description)