IBM Z Software
Hide about this portal


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.

Add a new idea Subscribe
Status Delivered
Workspace COBOL Compilers
Created by Guest
Created on Dec 16, 2015

RELATED IDEAS

SSRANGE with Warning Option

See this idea on ideas.ibm.com

With RFE 78190 SSRANGE was enhanced for ZeroLength-Moves (SubOption ZLEN).
The Problem of an ABEND is: The Test is immediately stopped.
Would it be an option for giving a Message at Runtime (Not the default option),
so after a whole test run we could see how many Table Range Trouble we get. If there are 50 Messages it seems to be a harder problem than two Messages. So if i get an ABEND, fix it, get an ABEND again (other place in program) and so on, my enthusiasm reduces radically.
With Warning i have the option to see there are only (for example) three places to correct my program and i will stay active to do this.
In Combination with RFE 61388 (SSRANGE for a Table in a Table) it would enable to clean up your code with the knowing of time and effort to do this.

Idea priority Medium
  • Guest
    Reply
    |     Oct 2, 2017

    Delivered in V6.1 February 2017 PTF

  • Guest
    Reply
    |     Jan 13, 2016

    This RFE has been accepted and will be updated once put into plan.

  • Guest
    Reply
    |     Dec 23, 2015

    Hmhm. Hans-Peter's comment has to be thought about.

    Assuming the following situation: With executing an "uncorrect" statement you overwrite a field with the maximum range of a table ("hoops"). Afterwards you run into the next "hoops". But this "hoops" wouldn't happen if you have corrected the first "hoops" before. ;-))

  • Guest
    Reply
    |     Dec 21, 2015

    Hello Hans-Peter,
    the Statement should be executed.
    Normally you run without SSRANGE, to the logic flow after violation always is unpredictable.
    The Warning mode is to check programs, in the last times run without SSRANGE, now the first time with TableRange-Checking.
    And if you get one ABEND, you don't know how much work you have to spent to the source code.
    So, giving the chance to get all bad statements with just one run helps to estimate the amount of work to do.
    Guenter

  • Guest
    Reply
    |     Dec 20, 2015

    I would vote against this RFE. What is expected to happen, if a SSRANGE violation is detected: Should the corresponding statement be executed or bypassed? In both cases the logic flow after the violation will be unpredictable.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.