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
Workspace COBOL Compilers
Created by Guest
Created on Jul 5, 2018

Enterprise Cobol - Get the actual address of the entry point of a dynamically loaded program

When using the "SET function/procedure-pointer TO ENTRY program" instruction, we get the address of a routine that is not the actual entry point of the program, but a routine that allows calling the program.

The routine seems to be different depending on the Cobol version used to compile the program that use the SET TO ENTRY (not the Cobol version used to compile the program loaded by SET TO ENTRY).

For the same program loaded by SET TO ENTRY:
- in Cobol V4 we get an address above the 16 megs (simple branch to the entry point of the loaded program)
- in Cobol V6 we get an address below 16 megs (more complicated code)
The code of the routines corresponding to these addresses is different.

How to get the real entry point of a program loaded by SET TO ENTRY?

Idea priority Low
  • Guest
    Reply
    |
    Jun 22, 2020

    Hi, since we have not received any feedback, this RFE is being cancelled. Feel free to open a new one if you are able to answer the previous questions. Thanks.

  • Guest
    Reply
    |
    Jun 3, 2020

    May we know if you got a chance to review our April 14th, 2020 update?

    We shall keep this RFE open till June 17th, 2020 after which we shall close it if no response by then. Thanks.

  • Guest
    Reply
    |
    May 27, 2020

    May I know if you got a chance to review our previous update?

  • Guest
    Reply
    |
    Apr 14, 2020

    Hi,

    We would still like to know what business problem/usage scenario you are trying to solve? ie what would the user do if we were to provide the entry points?

    Thanks.

  • Guest
    Reply
    |
    Apr 17, 2019

    We accept any solution allowing us to find the real address of the entry point of a program loaded in memory, even if to adapt our code for that.

    To date, we are looking for the entry point of the main program in a loadmodule. We would also like to be able to obtain the list of modules (CSEST) composing a loadmodule (main program and subroutines) and the addresses of the entry points of each module (CSECT).

  • Guest
    Reply
    |
    Apr 11, 2019

    "SET function/procedure-pointer TO ENTRY entry-point" was actually meant for internal COBOL usage only. Our docs need to be updated for that.

    However, may we know if you would be willing to change your program if we externalized such an intrinsic function to find the entry point?

  • Guest
    Reply
    |
    Sep 15, 2018

    We want to develop introspection tools for our Cobol programs, such as recovering the "Signature Information Bytes" structure. This requires to navigate in different structures (PPA1, PPA2 ...) from the actual entry point of the program concerned.
    Some system routines or LE routines also need to provide the actual entry point of a program, such as some functions of the IGZXAPI routine.

    Regardless of these needs, if the "SET function/procedure-pointer TO ENTRY entry-point" statement indicates that it returns the address of an entry point in a program, it must return that address, and not return the address of another routine to call this entry point.
    If the current situation answers a problem to handle the call to an external entry point, then this problem must be handled at the "CALL" statement and not at the "SET" statement.

  • Guest
    Reply
    |
    Aug 31, 2018

    As part of our investigation, we would like to know what sort of business problem are you trying to resolve with this RFE? Thanks.

  • Guest
    Reply
    |
    Aug 2, 2018

    This RFE is still under consideration

  • Guest
    Reply
    |
    Jul 9, 2018

    The code generated by the instruction "SET / TO ENTRY" is not managed by the same routine according to the version of the compiler Cobol :
    - Enterprise Cobol V4 uses the IGZCPPL routine
    - Enterprise Cobol V6 uses the IGZXPPL routine

    We need an equivalent to the LOAD assembler macro (SVC 8) that returns the true entry point of a program.