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.

Add a new idea Subscribe
Status Delivered
Workspace PL/I Compilers
Created by Guest
Created on Apr 21, 2021

RELATED IDEAS

Overflow exception in operations with floating-point data not raised

Due to the fact that, while using the compiler option ARCH(12), an overflow exception was not trapped at run-time, resulting in a wrong output, where the most significant digits are lost, we would like to have an enhancement to cope with this problem.
This issue didn't exist when running with ARCH(11) or before. The overflow exception was raised.
Peter Elderon, is aware of this problem, and came up with a possible solution to solve this issue. In his own words and I quote:
“One thing we might be able to do that could help you here is to offer a compiler option that would enable SIZE only for some assignments. To explain what I mean:

there already is an option DECIMAL( FOFLONASGN ) vs DECIMAL (NOFOFLONASGN ) that specifies that FOFL should be raised when assigning a FIXED DEC to a FIXED DEC and significant digits are lost

We could add a suboption to the DECIMAL option, say SIZEONASGN, that would specify that SIZE should be raised when assigning any other type (such as FLOAT in your example) and significant digits are lost. This would have less performance cost than using the PREFIX( SIZE ) option since this would not cause SIZE checking to be generated for assignments to FIXED BIN or to FLOAT.”

Idea priority Medium
  • Guest
    Reply
    |     May 7, 2021

    This has been delivered via a PTF to 5.3

  • Guest
    Reply
    |     Apr 23, 2021

    This would reduce the cost of raising SIZE for all assignments

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.