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).
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.
See this idea on ideas.ibm.com
Add support for stateful/stateless properties in the EGL WebServices wizards.
At the moment the wizard only supports stateful for REST services. If I specify not stateful, it uses the outdated default call interface that requires QEGL on IBM i and the EGL specific CL program in the library containing the called program. It also doesn't adhere to the library list that is set for the job by the system with job descriptions.
The SOAP services only supports the outdated call interface which is even worse.
Customers could use the RDi web service wizard, but the EGL web services wizard is doing a great job in translating the data structures from Program call interfaces into records in EGL. The EGL webServices wizard is brilliant in making it easy to get the parameters right for EGL consumption, which the RDi webServices wizard doesn't do.
We need support for these properties to fully support calling IBM i programs from RUI thru services. I already had a couple of customers running into this wondering why they needed QEGL on the system when calling their programs. The properties are already implemented in the EGL call to IBM i program.,
I think we can make this a lot easier for EGL customers and minimize the hurdles to get to their IBM i programs.
Idea priority | High |
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.
IBM Business Developer is a continuous delivery offering, and aims to satisfy the needs of a rapidly evolving market segment. Product strategy evolves and requirements are continuously evaluated against that strategy. This RFE has recently been reappraised against the wider product strategy and does not fall into IBMs delivery plans for the next 12 month. Whilst this RFE might be valid and we might look to deliver longer term, this RFE is being rejected at this time.
This RFE is more than a decade old. It might not be relevant now. Please create a new RFE if this requirement is not yet addressed in the product and it still exists.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - Business Developer
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - Business Developer
This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.
The status for this requirement has been down graded from In Plan to Candidate. Development still agrees that it would be a good feature, but it is not currently in our near-term plans.
Thank you for this input. We agree with this requirement, and hope to implement it in the near term.