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 Feb 12, 2019

Ability to track older version of compiled cobol code

My customer is interested in tracking other versions of Cobol below 5.2. They have a utility to run against there cobol loadlibs that produces the different levels and counts but they have no way of determining when and how often they are used. They would like to be able to track usage of the different versions and be able to convert the highly used Cobol programs to the current compiler use ARCH(12) as they run on z14's to get the biggest bang for the buck. Is there anything available or in the plans to track more then OS/VS Cobol? I understand why it is tracked as eventually support from the Language Environment will go away.

Idea priority Low
  • Guest
    Reply
    |
    Jul 14, 2020

    Hi, since we have not heard back from you, we shall assume its ok to close this RFE. Feel free to open a new one once you have the required information. Thanks.

  • Guest
    Reply
    |
    Jul 2, 2020

    Hi, following-up again to see if you got a chance to review our previous question? We shall keep this RFE open till Tuesday, July 14th after which we shall go ahead and close it due to lack of reply. Thanks.

  • Guest
    Reply
    |
    Jun 22, 2020

    Hi, follow-up to see if you got a chance to review our previous question? Thanks

  • Guest
    Reply
    |
    May 27, 2020

    May we know if you got a chance to look into using existing IBM products such OMEGAMON and IBM Tivoli Application Manager?

    Thanks.

  • Guest
    Reply
    |
    May 7, 2020

    Same as previous update.

  • Guest
    Reply
    |
    May 6, 2020

    Hi, Thank you for your response.

    Yes, your understanding is correct, ie we would only be able to track older code if it is dynamically called by a V5+ Cobol program.

    One other question that came up while triaging this RFE:
    Have you considered using some of the already existing IBM products such OMEGAMON and IBM Tivoli Application Manager? These products provide a more complete solution to your issue.

    We look forward to your reply. Thanks.

  • Guest
    Reply
    |
    Apr 30, 2020

    It sounds like you can provide a solution but the last statement confuses me: "Note that we can only track dynamic call events after a V5+ COBOL program has been executed in the run." Does this mean you would only be able to track older code if it is dynamically called by a V5+ Cobol program? Meaning if older code was executed but not dynamically called by a V5+ Cobol program you would not be able to track? If this is the case then this would only be a partial solution, which would be better then what is available now which is nothing. The customer documented 80+ percent of the written code is older then V4.2, they truly want a way to determine if any of this older code is highly used and go after those first to convert to V5+

  • Guest
    Reply
    |
    Apr 29, 2020

    We can provide a new capability in the COBOL V5+ runtime library to keep track of older programs (V4 and previous release) in the application. This is to help an application when it is in the process of migrating to V5+. Note that the runtime has information about dynamic calls in an application, but not static calls. (As in the later case, execution control is passed directly from the caller to the subprogram, and there is no code logic in the COBOL program to record the call information.)

    At the end of an application run (in a JOB step), the COBOL runtime can display a list of COBOL program names called by dynamic call, and the number of times these programs are called within that run. Note that we can only track dynamic call events after a V5+ COBOL program has been executed in the run.

    Would something like this satisfy your requirement ?

  • Guest
    Reply
    |
    Apr 24, 2020

    Thank you for your latest response. We are reviewing it and will get back to you shortly.

  • Guest
    Reply
    |
    Jun 10, 2019

    American Express is not tracking by cobol program name rather by counts, so the information asked is not available

    Total Cobol program count 160,440 - 100%
    Cobol 4.2 and older count 131,529 - 82%
    Cobol 5.2 count 11,701 - 7%
    Cobol 6.1 count 17,210 - 11%

    As you can see they want to determine the high used 4.2 and older cobol programs to target for conversion to version 6
    Many of the 4.2 and older count includes programs that are no longer in use but there is not an easy way to determine which ones

  • Guest
    Reply
    |
    Jun 5, 2019

    Hi,

    We see that different non-compiler tools were suggested via the initial PMR for this topic.

    May we know if its sufficient to print the list of legacy program names that are dynamic called within the run at the end of the COBOL run unit? Optionally we can also provide control to suppress the list (if it is not needed in production, for example).

    Feel free to let us know.

  • Guest
    Reply
    |
    Mar 18, 2019

    This RFE is being investigated further.