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
Start by posting 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 offering manager 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 notifications 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.
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 - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Dynamic Agents should behave same way as FTA in regads to non-interactive session
On 9.1 FP1 and PMR 78443,010,678 changes was made to the way jobs were started on the FTA. We then created PMR 16192,010,678 since we found that the Dynamic agent behaved in a different manner and got the following response: let me clarify some points: - the apars IV60621 and IV41929 (and in general all the changes impacting interactive jobs and the availability of active user sessions/desktops to allow the job to start) apply to FTAs only. Also the attribute in localopts to force the FTA to behave in old fashion style, jm interactive old, is for FTA only.
- Dynamic agents always behave like FTA old style: the active session for the streamlogon user is not necessary
We need the dynamic agent to behave the same way as the FTA. So that we can specify in a configuration file if the jobs should start in the old manner or in the new manner.
Do not place IBM confidential, company confidential, or personal information into any field.