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 Planned for future release
Created by Guest
Created on Mar 17, 2022

Sequence number for event submited jobs

I have lately set up some event triggered jobs. It is a predefined job that will be submitted each time another job matching a certain name pattern is submitted.


The event action looks like this:

SBJ P1OPS003#DBO_U_BUYPASS_PRIZE_PAYOUT_CONTROL AS DBO_U_BUYPASS_PRIZE_CONTROL_SB INTO P1OPS001#DBA_DAY_NO_GS_02


This event will trigger multiple times within the daily plan. When submitted the job name will be DBO_U{long number}, i.e. DBO_U2323131011. When only 5 characters is kept from the actual name (DBO_U_BUYPASS_PRIZE_CONTROL_SB) it will be difficult for our operations to see what kind of job that is running. To me a shorter sequence number would have been much better. I.e.

DBO_U_BUYPASS_PRIZE_CONTROL_SB_1

DBO_U_BUYPASS_PRIZE_CONTROL_SB_2

DBO_U_BUYPASS_PRIZE_CONTROL_SB_99


I have not found a way to do this. I have tried to add some of the available variables in the event rule page to the job name but many of them does not give a legal job name or are too long or unfit for the purpose.


Maybe a sequence number could be a future enhancement to event submitted jobs?

Idea priority Medium