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.

Add a new idea Subscribe
Status Delivered
Workspace PL/I Compilers
Created by Guest
Created on Jan 30, 2017

RELATED IDEAS

New sub-option LOOSEFORWARD for RULES(NOGOTO) to allow to jump forward only

We would like to get a new sub-option such as LOOSEFORWARD for RULES(NOGOTO) to allow to jump forward only:
- LOOSEFORWARD is a amendment to LOOSE, that allows to jump forward only - but not backward.

Idea priority Low
  • Guest
    Reply
    |     Aug 22, 2017

    This was delivered as part of the June 2017 continuous delivery

  • Guest
    Reply
    |     Mar 14, 2017

    I doubt that this is of general interest. Either you're in the GOTO camp or your out :-).
    Regarding all the various exceptions from various code-style-checks: i suggest to implement exceptions via SUPPRESS(...) stmts rather than via general compiler options. Like PCLINT and all it's derivates it allowes the developer to mark an exception from the rule on a per-occurency base. In this case ~ SUPPRESS(NOGOTO).
    br johann

  • Guest
    Reply
    |     Feb 16, 2017

    This could be useful since forward goto's might be ok, but backward goto's are probably never a good idea

  • Guest
    Reply
    |     Jan 31, 2017

    In general forward jumping GOTO's are frowned upon, as the target may be 42 pages away, and the next RFE will probably be for a LOOSEBACKWARD. Other than an exit from an ON-UNIT there is absolutely no reason to use GOTO in PL/I!

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.