Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Not under consideration
Created by Guest
Created on Sep 18, 2013

Treat CPUTIME and COUNT in PROCLIM independent of each other in determining U240 Tran abend

Currently, a transaction can have a max time equal to the product of
CPU-time-per-transaction and count as specified in the PROCLIM parm. This means that if the count needs to be adjusted for tuning purposes, it will have an impact to how long a looping transaction will have before it gets abended.

It would be ideal to have CPUTIME behave the same way for FF as it does for FP where COUNT and CPUTIME are independent of each other. This means that if there are 10 trans on that particular schedule with a 1 sec time, instead of allowing 1 tran a max of 10 sec, it can only go up to 1 sec before it gets terminated.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 3, 2018

    Hi Michael Tutor,

    Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

    When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

    At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. The reason we are rejecting RFE ID 39364 is because it is not our product direction to provide this function. The requested requirement will affect the current behavior on how the CPU time is calculated which might have undesired effect for the existing clients.

    Thank you for your continue support with IMS.
    Haley Fung - hfung@us.ibm.com