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.

Add a new idea Subscribe
Status Delivered
Workspace COBOL Compilers
Created by Guest
Created on Aug 5, 2015

RELATED IDEAS

Cobol V5 - Evolution for TEST option - TEST(EJPD,NODWARF) for non IBM debuging tools

Cobol V5 brings support of DWARF information for debugging programs.

The TEST compiler option has evolved accordingly.

Cobol V5 optimizer is much more "aggressive" in binary code that Cobol V4 optimizer. To trace the execution of a program, regardless of the tool used, the TEST(EJPD) option is almost inevitable (and even to analyze dumps without undergoing some edge effects created by the Cobol V5 optimizer).

However, option TEST(EJPD) requires the presence of DWARF debug information in the program object, even with TEST(EJPD, NOSOURCE).

These DWARF informations are not used in our context since we do not use the IBM debug products (our tools exploit the compilation Listing) : we just need a binary code within certain constraints common to all debug tools, namely respect for correspondence 1 to 1 between Cobol source and binary code sequence instruction.

Would it be possible to add an option "TEST(EJPD, NODWARF)" meet this need (EJPD kind binary code without source or debug information) ?

Idea priority Medium
  • Guest
    Reply
    |     Sep 28, 2017

    This has been delivered in V6.2

  • Guest
    Reply
    |     Nov 4, 2015

    We will be considering this feature as a request for TEST(NODWARF) without modifying the EJPD setting; for a future compiler version. The RFE will be updated once this item has been put into plan.

  • Guest
    Reply
    |     Oct 22, 2015

    For your information, we compile only one time at unitary test step and don't recompile after : what is tested is exactlly what will go in production.
    So we need performance ( OPTIMIZE(1|2) ) and "testability" ( TEST(EJPD,xxxxx) ) at the same time.
    We notice also that OPTIMIZE(1|2) without TEST(EJPD,xxxx) can introduce strange effect and false information in dump analysys : erroneous value in table indice, execution not in sequence....

  • 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
    |     Sep 2, 2015

    Thanks for the info. This is being investigated internally. The RFE will be updated once we have more news.

  • Guest
    Reply
    |     Aug 26, 2015

    EJPD maintains the one to one correspondence between the source and binary instruction sequences : a source instruction corresponds to one and only one interrupted binary sequence.
    This is an essential condition to allow source-level debugging .

  • Guest
    Reply
    |     Aug 25, 2015

    EJPD is needed for debuging (trace and also dump and performance analysis) when binary code is optimized.
    Optimize(1|2) without EJPD produce binary code that is not debugable at source level, and is only debugable with LIST option to view each binary instruction with reference to source statment.
    Our debug tools use directly the listing produced by compiler and no not use DWARF info, so DWARF info can be suppressed from program object for us, but binary code produced by EJPD is needed.
    Our debug tools are compatible with code produced with OPTIMIZE (1|2) only with EJPD, (our debug tools need also XREF or LIST option to establish correspondance between source statment and binary instrction).

  • Guest
    Reply
    |     Aug 25, 2015

    May we know why EJPD is needed?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.