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 Nov 25, 2015

RELATED IDEAS

Compiler options enhancements

Virtually every release of Enterprise PL/I adds new compiler options. It would be useful if the full list could be included in a member (pxoptXXX?) in the ' IELxxx.SIBMZSAM' sample library in a format that can be directly used by a PARM=('+DD:PLISUPP +DD:PLIUSER') parameter upon invocation of the compiler.

Adding both the options for the current and (some/all) previous versions of the compiler would also enable a SuperC compare to quickly find the new and/or changed options.

To make SuperC compares easy to read, options with multiple values should be included as one line per value, i.e. for the "DEFAULT()" compiler option they should be presented as

default(ibm)
default(aligned)
default(assignable)
default(byaddr)
default(connected)

rather than as

default(ibm aligned assignable ...)

Additionally, it would be useful if a '*process /*' option could be added that allows commenting compiler options, or for compiler options in a '+DD:ddname' format, allowing to specify /* comments, either with */ end-of-comment delimiter, or as end-of-line comment.

Idea priority Medium
  • Guest
    Reply
    |     Jun 29, 2016

    Delivered as part of version 5.1

  • Guest
    Reply
    |     Jan 6, 2016

    thanks for the feedback - we will probably adopt the PXOPTVRM notation

  • Guest
    Reply
    |     Dec 9, 2015

    In the RFE I've suggested PXOPTxxx for the membername, so for EPLI 4.5.0, the member would be called PXOPT450.

    Personally, I use two members, PXOPT43 and PXOPT43Z, the former contain the options as "*process xxx..." statements to be included "in-line", the latter as naked "xxx...", to be included via the "+DD" option.

    I can imagine that the PL/I developers could (potentially) include two sets, either as "*process xxx..." or as naked "xxx..." statements (or both) that provides

    1) an environment where every option is set to its default, possibly with comments as to why using the default for some options may not be the best thing to do - I'm specifically talking about many of the rules() options, such as the (no)lax... ones, and to do so, members could be named PxxxDEFp/PxxxDEFn (defaults, *process/naked),

    2) and a set, PxxxIBMp/PxxxIBMn, with suggested better values for some options, in order to generate better code and provide more information about possible problems at compile time.

    I would respectfully suggest, in line with the fact that z/OS can be upgraded in a skip one cycle, that SIBMZSAM contains the such members for EPLI Vn, EPLI Vn--1 and EPLI Vn-2, although due to the small size of these members, it probably would not harm to keep older versions until a particular version of the compiler is no longer supported.

    And for what it's worth, having had a look at the 4.5 manuals, I mustn't have looked well enough, but I cannot find a way to enter comments in *process or "naked" +DD options.

  • Guest
    Reply
    |     Dec 8, 2015

    this is a good idea, but do you have a suggestion for what you would like the member of SIBMZSAM to be called?

    and comments are already allowed in *PROCESS statements and in +DD options files

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.