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 Not under consideration
Workspace IBM Developer for z/OS
Created by Guest
Created on Mar 7, 2022

RELATED IDEAS

Dependency Based Build - Userbuild: suppress messages in Remote Error List

When we perform a user build of a Cobol program in IDz, we want the compile errors and warnings to be visible in the 'Remote Error List' view.

To get this working we added the following DD's in the
if (props.errPrefix) {} part of our Cobol.groovy script:
//The following DD name WSEDSF1-4 are needed to get the feedback of the compile in the Remote Error List
//we need to allocate it explicitly because by default these files are allocated with hlq userid
//but this is not allowed in KBC.
compile.dd(new DDStatement().name("WSEDSF1").options(props.cobol_compileErrorFeedbackXmlOptions))
compile.dd(new DDStatement().name("WSEDSF2").options(props.cobol_compileErrorFeedbackXmlOptions))
compile.dd(new DDStatement().name("WSEDSF3").options(props.cobol_compileErrorFeedbackXmlOptions))
compile.dd(new DDStatement().name("WSEDSF4").options(props.cobol_compileErrorFeedbackXmlOptions))

And in our preferences in IDz under 'Dependency Based Build' we also checked the 'Support Error Feedback' and 'Overwrite temporary logfile' options.

This worked and the errors and messages are now visible in the 'Remote Error List'.
However, because we always compile during user build with the NOLXPRF rule compile option, we always get the follwing warnings in our list:
IGYSC2259-W **RULES(NOLAXPERF)** Compiler option "NUMCHECK(ZON or PAC or BIN)" ...
IGYSC2256-W **RULES(NOLAXPERF)** Compiler option "TRUNC(BIN)" ...
IGYSC2252-W **RULES(NOLAXPERF)** Compiler option "OPTIMIZE(0)" ...
IGYSC2251-W **RULES(NOLAXPERF)** Compiler option "NUMPROC(NOPFD)"...

And since our developers have no impact on these options, we wanted to hide them from the 'Remote Error List'.
To do this we created a DXF03 Cobol program to suppress these messages and added this as an exit to our compile parameters: EXIT(MSGEXIT(DXF03)).

When we now look in the build log of the user build, we see that the exit works, because we see:
Messages suppressed by MSGEXIT: 4

However, the messages are still present in our 'Remote Error List' view.

Idea priority Medium
  • Guest
    Reply
    |     Jun 2, 2022
    This is definitely an interesting use of the product and we agree your idea has value but we don't think that we will be able to address this in the next two years. We thank you for taking the time to suggest an enhancement, many of our product enhancements result from feedback from our customers, so your input is always very important to us. Please feel free to resubmit in the next year or so for our consideration. Again, thank you for your suggestion and continued support.
  • Guest
    Reply
    |     May 17, 2022

    It is part of the quality awareness we want to enforce for our developers during testing.
    The use of NOLAXPERF will can cause additional messages in our listings, which we do want to keep for our developers to be aware of potential issues.
    We use different compile options for our development environment than for our acceptance/production environment.
    For development we normally use: OPT(0),INITCHECK(STRICT),RULES(NOENDP,NOEVENP,NOLXPRF,NOLAXREDEF,NOUNRA,NOOOM),TEST(EJPD),SSR(ZLEN),PARMCHECK(ABD),NUMCHECK(ZON,PAC,BIN,ABD)
    Some of these option will cause possible interesting compile messages and others will even cause the program to abend at runtime on development.



  • Guest
    Reply
    |     May 16, 2022
    We are curious why you use those compile options, if you have no intention of having developers take action on the results, and even go so far as to try and hide the messages produced from those compile options. Why not stop using those options?
  • Guest
    Reply
    |     Apr 25, 2022 
    Hello, this RFE is about IBM Developer For Z/OS which manages the connection plugin with DBB

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.