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 Oct 24, 2023

NOLAXNESTED behavior modification

The NOLAXNESTED compiler option should just prevent code in a proc and nested procs to be intermixed.
The rule should be that the code in a proc forms a single 'block'.

Case 1 : All nested procs AFTER the code => Acceptable

 

    a: proc;

      dcl (x,y,z) fixed bin;

      x = 1;

      y = 2;

      z = 3;

      b: proc;

      end b;

      c: proc;

      end c;

    end a;             

 

 

Case 2 : All nested procs BEFORE the code => Acceptable

 

    a: proc;

      dcl (x,y,z) fixed bin;

      b: proc;

      end b;

      c: proc;

      end c;

      x = 1;

      y = 2;

      z = 3;

    end a;             

 

Case 3 : All nested procs BEFORE or AFTER the code (which is still a single block) => Acceptable

 

    a: proc;

      dcl (x,y,z) fixed bin;

      b: proc;

      end b;

      x = 1;

      y = 2;

      z = 3;

      c: proc;

      end c;

    end a;             

 

Case 4: Code is not a single ‘block’ => Not acceptable under NOLAXNESTED

 

    a: proc;

      dcl (x,y,z) fixed bin;

      x = 1;

      b: proc;

      end b;

      y = 2; => Should be flagged

      c: proc;

      end c;

      z = 3; => Should be flagged

    end a;             

 

Instead of flagging each statement individually, the 'block' should be flagged as a whole (to avoid a long list of identical messages if the 'block' contains lots of statements).

 

Idea priority Medium
  • Guest
    Reply
    |
    Nov 3, 2023
    This will flag code unless all the subprocedures come either before or all after the code