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
Start by posting 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 offering manager 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 a 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
With the Perl MJC, when the job runs all the steps are displayed, and you have the ability to select "pause" on any one of the to pause execution of the job at that point. This RFE requests the same functionality for Java MJC jobs.
I didn't realize how much this feature is used until it disappeard and my users complained.
Right now the only option is to cancel the job in the middle of whatever step it happens to be in.
It is useful to be able to interrupt a job at a step boundry in order to be able to cancel the job at "clean" point. cancelling a job in the middle of a step will often leave the build results in an incomplete and unusable state since files are partially written etc. Stopping at a boundry allows us to use the paritial results, or even restart the job at a later time to complete the task.
Sometimes we discover we are overloading a system or other resource and want to reduce the load until the backlog is cleared out, pausing the job does this task
When creating and debugging projects this is a very useful tool to "single step" through the running job.
Do not place IBM confidential, company confidential, or personal information into any field.