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
Workspace Debug for z/OS
Created by Guest
Created on Mar 29, 2017

IDz Code Coverage Enhancement: Number of times a statement was executed

years ago there was a tool that was very similar to RDz Code Coverage. One thing it had that would be good to add to RDz code coverage would be a count of the number of times a statement was executed. This would be helpful in fine tuning if/then/else and evaluate statements.

For example:

Evaluate POLICY-TYPE
WHEN ‘01'
Statements 1
WHEN ‘02'
Statements 3
WHEN ‘03'
Statements 20
WHEN ‘04'
Statements 90
WHEN OTHER
Statements 0
End-evaluate.


Although logically you would code it this way, but based on the counts you may want to change the order to check for 04 first (90), then 03 (20) to be more efficient.

It may only be a few extra lines of code executed but if you multiply these few lines times the millions of policies it is checking it could impact the total run time.

Or something like this:

Evaluate POLICY-TYPE
WHEN ‘01'
Statements 1
WHEN ‘02'
Statements 3
WHEN ‘03'
Statements 20
WHEN ‘04'
Statements 90
WHEN OTHER
Statements 200
End-evaluate.

Based on these counts, you may want to add a SYNCSORT step to the job to filter the input and eliminate all but a few policy type. I used this fix for one job that an input file of several 100,000's records to less than 50,000 and the overall run time by several hours.

Idea priority Medium
  • Guest
    Reply
    |
    May 20, 2021

    Frequency or Hit counter is a valid request, however based on our current plans and priorities, it is not likely that this could be implemented in the next year, or in the next Debug for z/OS release. Thus, this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    May 19, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Debug for z/OS
    Component - z/OS Debugger
    Operating system - IBM z/OS
    Source - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - IBM Developer for z/OS, including Enterprise Edition
    Component - z/OS Application Development
    Operating system - IBM z/OS
    Source - Client

  • Guest
    Reply
    |
    Jul 10, 2017

    Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. The requirement to capture the number of times a statement is executed is accepted. For performance reasons the implementation may not be tied to code coverage capture but the implementation will allow the merge of the number of times a statement is executed with the code coverage data so that they can be displayed together.