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 Jan 26, 2017

RELATED IDEAS

Add ASSERT ( ENTRY | CONDITION ) compiler option to use new ASSERTION condition and built-in functions

We do not like that part of the ASSERT statement with the ibmpas* procedures, as they are mandatory on one hand and having it more than once led to BINDER or runtime issues on the other hand.

So we like to get a new implementation based on the PL/I condition handling:
- Under ASSERT(ENTRY) code will be generated to call ibmpas* as today.
- Under ASSERT(CONDITION) code will be generated for the new PL/I condition handling.
- IGNORE(ASSERT) have to work for both as today.

ASSERT(CONDITION) will do the following if the assertion failed:
- The new ASSERTION condition will be raised.
- "Normal return" will be done after the END of the ON ASSERTION block and the program will continue with the next statement but we are free to use STOP, SIGNAL ERROR, RESIGNAL etc. instead
- As "implicit action" the ERROR condition will be raised, If there is no active ON ASSERTION block.

To handle this inside the ASSERTION and/or ERROR condition we need the following built-in functions:
- New ONPACKAGE()
- New ONPROCEDURE() and ONPROC() - as a synonym and its abbreviation of existing ONLOC()
- Existing ONLINE()
- New ONTEXT()
- New ONACTUAL and ONEXPECTED - for new ASSERT COMPARE (RFE 100153)

In addition new oncodes will be required for that.

Idea priority Low
  • Guest
    Reply
    |     Feb 15, 2017

    This is available via APAR PI76421 / PTF UI44689

  • Guest
    Reply
    |     Jan 27, 2017

    We probably should have done this originally although there are pluses to having user-supplied routines to handle failed assertions

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.