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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
4GL - INPUT statement - Ability to EXIT INPUT but still execute the AFTER INPUT control block
It would be handy to be able to exit from an INPUT statement and (conditionally) trigger the AFTER INPUT control block. Currently if you execute and EXIT INPUT, the thread will continue after the END INPUT statement. What I am requesting is a new syntax/command/option/directive that would direct the execution of the thread to (execute) the AFTER INPUT control block AS you "Exit Input". Alternatively, the ability to simulate the ACCEPT KEY being pressed/triggered/initiated would also work to accomplish this same task - but in my opinion it would be the less desirable approach to resolving the problem.
Do not place IBM confidential, company confidential, or personal information into any field.