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.
Correct issue with soam work history file and directory ownership
We have an issue with the Symphony Spectrum product where user jobs are submitted using different "run-as" IDs. The IDs are different than the cluster admin ID. Therefore the sessions are failing to write their work history under ego-shared/kernel/conf/../../soam/work/history. This is causing many errors in the SD log as well.
1. The permission of soam/work/history, 775 or 1775? The history parent directory is 775. But the child directories '000***' are currently 777, which is a violation. 2. Is egoadmin the "root" user or just another user, please confirm. The 'egoadmin' ID is the cluster admin ID. Not a root or privileged Linux account. 3. For the app workload execution users, are they in different user groups? Yes, they are in different groups. 4. If "777" is not allowed, is "1777" OK? If "1777" can be used, we can workaround this issue with it. 1777 is not allowed. The issue is both IBM security policy and Federal accounts are not permitted to have world writeable files and directories.
Do not place IBM confidential, company confidential, or personal information into any field.