This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Note that the RDi use of this new support is being tracked with RFE 78817: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=78817
.The feature of "Generate an event file when executing CRTCMD" was delivered via PTF SI67683 of 7.3 by 2018/05/31.
The feature of "Generate an event file when executing CRTCMD" was delivered via PTF SI67683 of 7.3 by 2018/05/31.
Yes. Adding the OPTION parameter makes sense. I would almost prefer to have the default be OPTION(*EVENTF). If the default is *NOEVENTF, it would take modifying everyone's compile commands in RDi (that is all the developers in our shop) once the option is available. But I think that would be required anyway since OPTION(*EVENTF) is required to get the error list loaded.
As long as the ability to generate the file is there I would be a happy camper. So I don't mind either way whether it defaults to *EVENTF or *NOEVENTF.
I like your idea to add event file when create CL Command.
I agree with that it is inconvenience when the CRTCMD run from RDi and with no detailed compile errors come back to the RDi client.
Thank you for your suggestion, it is a valuable feature for us to develop in the future release.
To implement this, I think one additional parameter need to add to CRTCMD command like CRTCLPGM, which is OPTION(*EVENTF), and *NOEVENTF will be the default value.
Any further discussions are welcome.
Creating a new RFE based on Community RFE #88111 in product IBM i.