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 Delivered
Workspace PL/I Compilers
Created by Guest
Created on Jan 12, 2017

Add support of NULL() under LP(64) to get a pointer value for read and/or write protection

We would to get NULL() under LP(64) returning a value that would be unusable in 64-bit.

Idea priority Low
  • Guest
    Reply
    |
    Aug 22, 2017

    This was delivered as part of 5.2

  • Guest
    Reply
    |
    Jan 20, 2017

    Hi Patrick, that is a misunderstand - we prefer NULL() to SYSNULL(), as a NULL() value is protected to any access (read & write) while SYSNULL() allows reading. That's why we want the same behavior under LP(64).

  • Guest
    Reply
    |
    Jan 18, 2017

    We also don't like NULL(). So we try to eliminate this on all sources. But there are some PL/I macros (like from MQ Series) that "uses" NULL() - they changed to SYSNULL() by our request.

    I would like to deprecate NULL().
    For any invalid Pointer, POINTERVALUE(-1) may be better ?
    Or a new BIF INVALIDPTR()...

  • Guest
    Reply
    |
    Jan 16, 2017

    this would be good to have