This is an IBM Automation portal for Digital Business Automation 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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Automation Decision Services (ADS) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Specific links you will want to bookmark for future use
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.