Skip to Main Content
Cloud Management and AIOps

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Created by Guest
Created on Nov 18, 2014

src stops too early at system shutdown / reboot

during shutdown a linux server we want to exclude the node using /etc/init.d/rcx.. scripts but src was killed as soon as shutdown begins so we have no chance to stop our applications before.

Idea priority High
RFE ID 62214
RFE URL
RFE Product Tivoli System Automation for Multiplatforms (SA MP)
  • Guest
    Apr 12, 2019

    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 - Tivoli System Automation for Multiplatforms (SA MP)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli System Automation for Multiplatforms (SA MP)

  • Guest
    Feb 26, 2016

    Hi Josi,
    it depends on how this command should be issued. Our Linux admins doesn't distinguish between server with SAMP installed / not installed. So I would say that shutdown / reboot of all our Linux Servers must be idendical. Seperating the procedure would not be accepted. But we are testing with SLES12. There it seems to be possible to implement an additional service (script) where the samctrl -u a .. command can be included. Then you can define "dependencies" between the services so that samctrl.. will be issued before the resource controller will be stopped. In SLES11 the implementation in the init,d / inittab must be changed if possible. But here my skill of Linux is insufficient.
    regards Rüdiger

  • Guest
    Feb 25, 2016

    Hi Rüdiger,
    when I look at your comment "...this tool should assist during planned actions...." - I have one question: "Would your be satisfied with a command "SAMP_reboot" to be used instead of the ordinary "reboot" command of the operating system?

  • Guest
    Feb 18, 2016

    Hello again,
    I want to know what IBM think about this. In a "Data Center's real life" it is not possible to stop the applications manually before rebooting a (Linux-) Server because we have to reboot hundreds of then in one night. We use an Automation tool, so this tool should also assist during planned actions like maintenance / reboots. It should be a part of an automation tool like TSAMP! Dear IBM, the status of this RFE "under consideration" doesn' t help. It must be a MUST HAVE.
    Regards
    Ruediger Dahlke

  • Guest
    Oct 10, 2015

    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 System Automation for Multiplatforms (SA MP)

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli System Automation for Multiplatforms (SA MP)