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 z/TPF
Created by Guest
Created on Feb 18, 2015

Need awareness in Abstracts to macro/header updates that affect current displacements

I originally reported this in PMR 14604,004,000, and was asked to move it to an RFE instead.

Description:
If IBM changes a macro or header in such a way that it moves displacements of existing fields, and/or removes existing fields, that information needs to be stated in the APAR abstract. It would simply have to state the fields involved in such changes, so we could be alerted to it for further review, scanning for impacts, etc. By having that information up front, we can be aware in the early stages of the project to the potential need for reassembly and/or updates to local software.
For example, PJ41092 is hitting tens of macros and headers, changing the displacements of some fields in DCTMFS.mac, and removing a CINFC tag (CMMFS2). The changes to DCTMIO.mac affected some of our local segments, but the impact didn't surface until testing.
It is not practical to always assemble every component involving a macro that was touched by an APAR, nor is it necessary if the change doesn't involve any differences to current fields and/or displacements. We are asking IBM to advise us of the more intrusive macro changes such as was described above.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 21, 2020

    IBM considered writing some tooling to identify displacement changes. However, we determined this could not be 100% reliable and based on priorities and resources we have decided not to write any tooling. If customers are using our dsects and headers, then it is recommended to recompile/reassemble the programs that use those dsects and headers when they are listed as changed in the APEDITs.

  • Guest
    Reply
    |
    Oct 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF

  • Guest
    Reply
    |
    Mar 3, 2015

    IBM does not intend to do this in the foreseeable future.