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 Jan 4, 2017

Add RULES(NOLAXFILEIO)

We want to avoid I/O-errors and -problems with the standard that user-defined files have to be explicitly opened before and closed after processing but not system-defined files:

Therefore we would like to get a new RULES suboption such as [NO]LAXFILEIO:
- With LAXFILEIO as default

NOLAXFILEIO means that
- OPEN or CLOSE of SYSIN or SYSPRINT will be flagged with a message
- For any file other than SYSIN or SYSPRINT, if there is no OPEN or no CLOSE of that, then its usage will be flagged with another message

Idea priority Low
  • Guest
    Reply
    |
    May 6, 2020

    This is not something we can do reliably at compile-time - even if there are no OPEN statements in the current compilation units, a file may have been opened in the calling routine. And if there are OPEN statements, they may be conditional and so ...

    We could have an option that would lead the code to raise a condition if an implicit OPEN were attempted, but that should probably be a new RFE

  • Guest
    Reply
    |
    Jan 7, 2017

    This would be helpful