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 COBOL Compilers
Created by Guest
Created on Dec 8, 2014

Need a vendor interface to access working storage length from an Assembler program

We have some (non-LE conforming) assembler code that is called by COBOL programs. The assembler code would save the TGT address, subsequently used to extract the COBOL Working Storage address and length. COBOL 5.1 has eliminated the TGT, replaced by the COBDSACB. As the TGT no longer exists, we are unable to obtain this information.

We are aware of IGZXAPI which can be used to query the WORKING-STORAGE area address. However, we also require the length, and may not have all the required IGZXAPI input parameters, such as the COBOL program's entry point address.

We are requesting a vendor interface for the missing information.

Idea priority High
  • Guest
    Reply
    |
    Jan 6, 2016

    This feature has been delivered in V5.2 November 2015 PTF.

  • Guest
    Reply
    |
    Sep 15, 2015

    Hi, any idea yet of which release this will go in? It would be great if we can get this sooner rather than later.

    Thanks,
    Laura

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - COBOL Compilers

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - COBOL Compilers

  • Guest
    Reply
    |
    Jun 3, 2015

    The feature has been put into plan for a future release.
    We may consider back-porting this to a service release. If we do, this RFE will be updated to reflect that.

  • Guest
    Reply
    |
    May 21, 2015

    Hi, since this will be in a future release will we have to wait until the release comes out or can we get it sooner?

    Thanks,
    Laura

  • Guest
    Reply
    |
    Feb 4, 2015

    Thanks for the reply. This is a valid feature request. We will be accepting this RFE; and will be updating it once we put it into plan for a future release.

  • Guest
    Reply
    |
    Jan 28, 2015

    Hi, This issue has become rather urgent for us so please let us know at your earliest convenience what the status is.

    Thanks!
    Laura

  • Guest
    Reply
    |
    Jan 9, 2015

    Yes, the missing information is the length of the COBOL Working Storage. The current IGZXAPI implementation returns only the WS address, and we require the length as well.

    As the length was not provided I haven't actually tried to do this. However, I guess we should be able to obtain the COBOL program's entry point by following the save area chain. Ditto for the LE CAA. It would be greatly appreciated if IBM would provide sample assembler code, preferably reentrant, which is called from a COBOL program and invokes IGZXAPI to obtain COBOL Working Storage.

    I also don't think the "extra" compiler generated variables would be an issue.

  • Guest
    Reply
    |
    Jan 8, 2015

    Hi, we would like to confirm a few things. Does 'missing information' strictly refer to the length of the Working Storage? also, are you able to get the entry point addresses? What other information is required (if any) in the 'missing information'? Also, just an FYI, in V5.1 Working Storage and certain compiler generated variables might be intermingled. The size that we give is the combination of the two.