This is an IBM Automation portal for Cloud Management and AIOps 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, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Building 64 bit datachannel code to build 64 bit pv_analytics.jar file
In case TS004896360 "LOGW Java process core dumped on out of memory", the customer faced problems when LOGW Java process core dumped on out of memory. Later in this case IBM support team told "For 64bit logw process, there is no scope to build 64 bit pv_analytics.jar file as it will be incompatible with datachannel code. So, the entire code needs to be changed." The error stops work of proviso.log and crontab cannot restart that process. The customer needs this system enchancement, because there is no point in restarting this process once/twice a week by hand, nor the customer cannot lower logging level of components, otherwise it will affect debugging any upcoming issues.
Do not place IBM confidential, company confidential, or personal information into any field.