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 General System
Created by Guest
Created on Jun 3, 2021

Allow user to provide output area for DFSGVRM call

The DFSGVRM macro gives us a way to get the real IMS level. We are having issues with the FUNC=REL (addressability; our code and way it's written) using MVS STORAGE macro and having inline DC statements.

DFSGVRM FUNC=CALL requires caller to allocate working storage for the PARM list to be passed. However, the output area (DFSGVRMO) storage is obtained by DFSGVRM code. This requires FUNC=REL call after this.

Since we are required to provide storage for the PARM list: GVRM_PARMS DS CL(GVRMP_LN), we would like to know if we can also provide storage for the OUTPUT area – already in the DFSGVRMO MAC:
GVRMO_LN EQU *-DFSGVRMO Length, dw boundary

This would eliminate the allocation (saves CPU) as well as the RELEASE (saves CPU) allowing us to use the MAC with minimal code changes ? Possibly a new keyword, USERAREA (instead of AREA=). This would be a huge benefit in that calling would be much more streamlined and resolve a host of addressability options.

To get the FUNC=CALL to work in our code, we had to use IEABRCX DEFINE, ENABLE and DISABLE to generate relative branch instructions. We can't get FUNC=REL to assemble.

Note, we have code that obtains the installable IMS level millions of times/day at one of our customer sites. Having to make multiple calls to get data and then release storage adversely affects performance.

Alternatives would be:
1) expand DFSVC000 to include installable IMS level (currently only includes

Idea priority Urgent
  • Guest
    Reply
    |
    Jul 8, 2021

    Hi,

    Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

    When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

    At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. The reason we are rejecting this item is we have not had many clients ask for this enhancement. There doesn’t seem to be much interest from other clients. We would rather invest in high priority items that bring the most value to many clients.

    We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

    Thank you.