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.
Allow CECD0015E to inform user where error was found
CECD0015E error message is cryptic at best. It does not allow the customer (user) to make any determination as to the cause of the error or the ability to fix the error. In order to currently fix the error, the user MUST contact IBM with JESLOG and TRACE information. This information sent is usually not enough and other information is needed which requires a recreate of the issue. Also, a system dump is normally required as additional documentation. In my brief encounters with CECD0015E, it seems that they are issued when storage is unavailable for the function being performed. If this is the case, then indicate in the error message where the storage shortage is. This way, the customer can effectively change parameters to allow for a storage increase. If the issuing of the CECD0015E error message can't determine the exact nature of the error, and the documentation needed by IBM to determine the error is a dump - take it then (don't force a recreate with a slip set).
Do not place IBM confidential, company confidential, or personal information into any field.