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 notifications 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 that cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - incl Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - incl BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - incl Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
zRES logging behaviour - integration with z/OS Console
ODM must be highly available (no outages allowed) and we must be able to react on very short notice (real-time) if a problem occurs. If ODM is not responding for whatever reason, all transactions will be blocked/cannot be executed.
Current situation: At current state, the error messages, warnings and information are only written and stored in the USS log files. For mainframe standard software, it is common that the program exchanges information through the zOS console. This would enable us to react on short notice to a problem and ensures that the business impact can be reduced. At least the critical situations must be reported also in the zOS console (not only to the Unix log files). For example: No connection between ODM and DB2 (rules cannot be accessed by ODM) Notification Server Outage (already happened more than once) Abend of ODM In general: all situations which will cause an unexpected behavior of ODM (for e.g., rule calls cant be answered properly, a memory error, mismatch of copybook and etc.). Ideally, the warnings should also be included as it could lead to an error/outage. As already mentioned, we are actually not able to recognize such problems fast, which could end in an outage with big business impact .
Future state: Error messages, warnings (and may be also information) are available in the zOS console.
Do not place IBM confidential, company confidential, or personal information into any field.