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.
currently SSM holds page files once they are created and does not release the file handles or shrink the page files until SSM terminates. we think an enhancement is required so that the page files can be either released or actively cleaned up once...
Citi external-hosted AWS Grid is based on Citi RHEL 7.9 + IBM Symphony 184.108.40.206. In Citi RHEL 7.9 2021b image, openssl package is in version 1.0.2k: openssl-libs-1.0.2k-21.el7_9.x86_64openssl-1.0.2k-21.el7_9.x86_64 which is not supported by Symphon...
SymphonyDE 220.127.116.11 doesn't work with axis2 1.6.2 version of Axis2
We need to upgarde axis2 used by SymphonyDE 18.104.22.168 to remidiate our internal security finding related to older version of axis2 (axis2-0.93.jar) used by SymphonyDE 22.214.171.124. I tested our code with publicly available version of Axis2 ( I tried 0.9,...
Change VEMKD Behavior when unable to access vemkd/container/event file
After receiving RFE 145547 (patch build 563255), there was an occurrence where VEMKD continually restarted due to not being able to access the $EGO_CONFDIR/../../kernel/work/vemkd/container/event file. I'm requesting a similar patch to RFE 145547 ...
[Security and Access Control] /etc/init.d/ego status overiding default behavior - not according to standard, breaks monitoring and automation tool chain
The init.d script being rolled out with Symphony 7.1.0 is the same across all compute and management hosts. Running the script in its intended way with the status flag always results in the same message: -bash-4.1$ sudo service ego statusego servi...
Do not place IBM confidential, company confidential, or personal information into any field.