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.
[DUP81511] Change the structure of the shared SSM history folder, to allow secure use bu different execution users and groups
Platform Symphony (Spectrum Symphony) SSMs keep the sessions history files in a shared location, for example /gpfs/platform/soam/work/history
Before PS 7, all apps SSMs were filling history/ folder directly, causing it to store 1000s of files and making it unmanageable. In PS 7.1 there layout was updated, so that now we have .../history/00000/NNN/MMM folder structure, where NNN and MMM - are some numeric and numeric_ combinations without clear correspondence with the consumers/apps/groups/users related to the sessions, which histories are stored there.
Crucially, it happens that in some cases (for example when a session is aborted), that an .../NNN/MMM folder created previously by one SSM is then accessed by another SSM trying to save histories in the same folder. Then we observe a clash of ACLs, preventing session history being written. (when two SSMs have different execution user unix groups)
Do not place IBM confidential, company confidential, or personal information into any field.