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
Categories C/C++
Created by Guest
Created on May 16, 2018

Inline __asm() to communicate ARCHLVL to HLASM for system macros

When a z/OS system macro is embedded in a __asm() block, HLASM assumes ARCHLVL=1 which means the macro will use base+displacement branching, which fails in an inline __asm() block due to "no active USING". Most macros implement a MF=E form which gets around this problem, but many important macros (e.g. STORAGE) do not, or do not support other parameters on the MF=E form, requiring a separate MF=L declaration, which is less convenient in LE C due to lack of #pragma insert_asm support (which is understandable). IMHO, it is desirable that LE C implicitly embed a "SYSSTATE ARCHLVL=n" (where n is the applicable ARCHLVL for the compile) or take some other action to communicate the ARCHLVL to HLASM, so system macros (or any other macro) has an opportunity to generate code which leverages the machine architecture.

Idea priority Low
  • Guest
    Reply
    |
    Dec 15, 2020

    IBM XL C/C++ for z/OS is a continuous delivery offering, and aims to satisfy the needs of a rapidly evolving market segment.
    Product strategy evolves and requirements are continuously evaluated against that strategy. This RFE has recently been reappraised against the wider product strategy and does not fall into IBMs delivery plans for the next 12 month. Whilst this RFE might be valid and we might look to deliver it longer term, this RFE is being rejected at this time. The requirement will be kept in our internal RFE backlog and might be reassessed in the future.

  • Guest
    Reply
    |
    Oct 12, 2018

    This RFE is being accepted and will be updated once put into plan.

  • Guest
    Reply
    |
    Jun 20, 2018

    This RFE is being investigated further and will be updated accordingly.