Skip to Main Content
Cloud Management and AIOps


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

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

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.

Status Delivered
Created by Guest
Created on Aug 8, 2017

maxdur "event" should write an event to BmEvents.conf log file

While we like the new 9.3 feature of MAXDUR, we want to be able to alert when it hits. With only options of kill or continue, it forces an abend, but that will mislead folks to think the job abended versus got killed. We would like to see a new event in BmEvents.conf. In that way, we could use our OMi (like TEC) solution to see the event and apply automated notification to the interested party, we could also automate cutting an Incident Management ticket. It would enable much more value from the simple detection that something happened. For now, we are writing event rules to see the condition and applying our homegrown way to create an event to OMi and notify via our notification system. Consider this my urgent plea to make the feature richer by enabling more things to happen.

Idea priority Medium
RFE ID 108864
RFE URL
RFE Product IBM Workload Scheduler (IWS)
  • Guest
    Reply
    |
    Nov 18, 2021

    Hello Rick,

    two events are currently available for this scenario that should resolve the issue:

    mstJobMaxDurationExceededContinue

    123

    Job maximum duration exceeded, job continues to run

    mstJobMaxDurationExceededKill

    124

    Job maximum duration exceeded, Kill action triggered

  • Guest
    Reply
    |
    Nov 6, 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 - 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)