This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
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.
Idea priority | High |
RFE ID | 69917 |
RFE URL | |
RFE Product | IBM Workload Scheduler (IWS) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Delivered with V10.1.0.1 (V10 FP1).
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Workload Automation and Control Desk
Product - IBM Workload Scheduler (IWS)
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - IBM Workload Scheduler (IWS)
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - IBM Workload Scheduler (IWS)
Component - Product functionality
Source - Other
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Automation
Product - Tivoli Workload Scheduler (TWS)
Component - Product functionality
Source -
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Tivoli
Product family - Automation
Product - Tivoli Workload Scheduler (TWS)
Component - Product functionality
Source - Other
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli Workload Scheduler for Applications
Component - Product functionality
Source -
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli Workload Scheduler for Applications
Component - Product functionality
Source - Other
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - IBM Workload Scheduler (IWS)
Component - Product functionality
Source -
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli Workload Scheduler for Distributed (TWSd)
Component - Product functionality
Operating system - Windows
Source - None
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli Workload Scheduler for Applications
Component - Product functionality
Operating system - Windows
Source - None
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli Workload Scheduler for Applications
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Automation
Product - Tivoli Workload Scheduler for Applications