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 Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Feb 14, 2016

RELATED IDEAS

Offer CBL option for Binder control statment

In some situation, it may be necessary to manage specific options when running the Binder.

These options can be the consequence of choice at the level of the Cobol program: by example using the EXCI interface that require to include a specific module in the program.

To simplify/unify compilation procedures, it would be interesting to be able to give some control statments for the Binder at the source level of the Cobol by CBL options.
This would also have the advantage to identify the needs of Cobol programs by analysis of source Cobol programs.

Idea priority Low
  • Guest
    Reply
    |     Mar 10, 2016

    It's also worth noting that COBOL ALREADY does (as an option) insert at least one binder/linkedit control statement. If you compile with the "NAME" option it will insert a "NAME (R)" after the END statement.

    z/OS V1 R13 BINDER 15:37:08 THURSDAY MARCH 10, 2016
    BATCH EMULATOR JOB(DVFJSC ) STEP(STEP1 ) PGM= IEWBLINK PROCEDURE(LKED )
    IEW2278I B352 INVOCATION PARAMETERS - LIST,MAP,XREF,LET=0,TERM,
    IEW2322I 1220 1 NAME COB5X(R)

  • Guest
    Reply
    |     Mar 10, 2016

    I was going to submit a similar RFE and I totally disagree with the reason for rejection. In HLASM its very simply to interact with the program binder using the "PUNCH" directive. This simply places the punched string in to the object module. So for example one can do the following:

    PUNCH ' INCLUDE MQSTUB'
    PUNCH ' INCLUDE CICSSTUB'
    PUNCH ' SETOPT PARM(REUS=RENT)'
    SYSSTATE ARCHLVL=2,OSREL=SYSSTATE
    MQASM CSECT ,
    MQASM RMODE ANY
    CALL MQCONN
    CALL MQPUT
    END MQASM

    This can be assembled and linked/bound with the following JCL PROC:
    //ASM PROC
    //ASM EXEC PGM=ASMA90
    //SYSIN DD DUMMY (OVERRIDE IN CALLER TO POINT TO SOURCE)
    //SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB
    //SYSLIN DD DSN=&&OBJMOD,DISP=(,PASS,DELETE),
    // SPACE=(400,(100,50))
    //SYSPRINT DD SYSOUT=*
    //*
    //LKEDBIND EXEC PGM=IEWBLINK,COND=(4,LT),PARM='MAP,XREF'
    //SYSLIN DD DSN=&&OBJMOD,DISP=(OLD,DELETE)
    //SYSPRINT DD SYSOUT=*
    //SYSLMOD DD DSN=DVFJS.APPLIB.LOAD(MQASM),DISP=SHR
    //MQSTUB DD *
    INCLUDE CICSLOAD(CSQCSTUB)
    //CICSSTUB DD *
    INCLUDE CICSLOAD(DFHEAI0)
    //CICSLOAD DD DISP=SHR,DSN=CICS.SDFHLOAD
    // PEND

    The output from the binder being:
    z/OS V1 R13 BINDER 14:47:30 THURSDAY MARCH 10, 2016
    BATCH EMULATOR JOB(ASMPUN ) STEP(ASSEMBLE) PGM= IEWBLINK PROCEDURE(LKEDBIND)
    IEW2322I 1220 1 INCLUDE MQSTUB
    IEW2322I 1220 2 INCLUDE CICSLOAD(CSQCSTUB)
    IEW2322I 1220 3 INCLUDE CICSSTUB
    IEW2322I 1220 4 INCLUDE CICSLOAD(DFHEAI0)
    IEW2322I 1220 5 SETOPT PARM(REUS=RENT)

    ---------------
    CLASS B_TEXT LENGTH = E46 ATTRIBUTES = CAT, LOAD, RMODE=ANY
    OFFSET = 0 IN SEGMENT 001 ALIGN = DBLWORD
    ---------------

    SECTION CLASS ------- SOURCE --------
    OFFSET OFFSET NAME TYPE LENGTH DDNAME SEQ MEMBER

    0 DFHMQSTB CSECT E10 CICSLOAD 01 CSQCSTUB
    11C 11C CSQCSTUB LABEL
    11C 11C MQCONN LABEL
    [...]
    E10 DFHEAI0 CSECT 18 CICSLOAD 01 DFHEAI0

    E28 MQASM CSECT 1E SYSLIN 01 **NULL**
    *** DATA SET SUMMARY ***

    DDNAME CONCAT FILE IDENTIFICATION

    CICSLOAD 01 CICS.V420.T1CICS.SDFHLOAD
    SYSLIN 01 SYS16070.T145230.RA000.ASMPUN.OBJMOD.H02

    I also absolutely disagree with the assertion "most people don't want this flexibility". What is this assertion based on? I would think most people WOULD want this flexibility in COBOL to include modules only when required.

    I urge IBM to reconsider.

  • Guest
    Reply
    |     Mar 2, 2016

    This would require interaction between the compiler and binder. As a result, this may impose some design issues between the compiler and binder interface.

    In addition, most people won't want this flexibility. There could be some security related issues. Hence, rejecting.

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.