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

  • Control Desk

  • 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 Under review
Created by Guest
Created on Sep 19, 2021

In case of Timeout JRExecAction is retrying to execute the command. We need to disable Retry behavior

Dear IBM Support Team, Please find below description about the scenario we have executed in IBM Tivoli Netcool/Impact 7.1 1) We executed below code in our Impact Policy and our observation from nci_jrexec.log file is, when Timeout occurs (based on configured Timeout value), it's retrying again the same operation again that is defined in the parameter/argument "Command_To_Fire". Sample Policy Code TimeOut = 4; JRExecActionResult = JRExecAction(Script_To_Run, Command_To_Fire, false, TimeOut); 2) Script_To_Run is a shell script that does SSH connection to Customer HPNA Custom Linux Appliance Server. Command to execute on Customer server is passed to the script in the parameter Command_To_Fire 3) After triggering the Command_To_Fire, if Timeout occurs we are receiving below error message in Impact Policy Log 08 Sep 2021 00:26:15,240: [Ngen_Framework_Alarm_Notif_CIC][MessageProcessor-Dog#4756]!(Module: Log): 0 ms 08 Sep 2021 00:26:23,352: [Ngen_Framework_Alarm_Notif_CIC][MessageProcessor-Dog#4756]Parser log: LangException ERROR: Exception in policy: RunRemoteCommand at line: 183.JRExecAction: Error while executing external action {/home/netcool/ssh_hpna_connect_failover.sh, deploy change plan -ip 192.168.96.112 -name "Cisco_S ingle_Homed_Device_ReportV2" -parameters "" -variables "stc_inputhosts=RTPE1-Khu-107-3\nCoreNCS-Maa-108-1,stc_ticket_num=PR00022535653" -comment "Auto task by netcool" -priority 1 -postsnapshot false} ExceptionMessage: com.micromuse.common.parser.PolicyException: JRExecAction: Error while executing external action { /home/netcool/ssh_hpna_connect_failover.sh, deploy change plan -ip 192.168.96.112 -name "Cisco_Single_Homed_Device_ReportV2" -parameters "" -variables "stc_inp uthosts=RTPE1-Khu-107-3\nCoreNCS-Maa-108-1,stc_ticket_num=PR00022535653" -comment "Auto task by netcool" -priority 1 -postsnapshot false}. getCause: java.rmi. ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: External command did not return within 4 seconds. Edit the Timeout value in the policy to change this value.; nested exceptio n is: java.util.concurrent.TimeoutException 4) In nci_jrexec.log file we are receiving error message representing the Timeout behavior 09 Sep 2021 10:40:19,037 ERROR [JRExecServer] External command did not return within 4 seconds. Edit the Timeout value in the policy to change this value. java.util.concurrent.TimeoutException: null 5) After Timeout, same command in "Command_To_Fire" gets triggered again. This is against to what we need. Requirement is stop/disable retry behavior in case of timeout. Note: Kindly provide a configurable way to stop/disable retry behavior in case of Timeout while using JRExecAction .
Idea Priority Urgent